Captive-Portal Identification in DHCP and Router Advertisements (RAs)
RFC 8910

Received changes through RFC Editor sync (created alias RFC 8910, changed title to 'Captive-Portal Identification in DHCP and Router Advertisements (RAs)', changed abstract to 'In many environments offering short-term or temporary Internet access (such as coffee shops), it is common to start new connections in a captive portal mode. This highly restricts what the user can do until the user has satisfied the captive portal conditions.

This document describes a DHCPv4 and DHCPv6 option and a Router Advertisement (RA) option to inform clients that they are behind some sort of captive portal enforcement device, and that they will need to satisfy the Captive Portal conditions to get Internet access. It is not a full solution to address all of the issues that clients may have with captive portals; it is designed to be one component of a standardized approach for hosts to interact with such portals. While this document defines how the network operator may convey the captive portal API endpoint to hosts, the specific methods of satisfying and interacting with the captive portal are out of scope of this document.

This document replaces RFC 7710, which used DHCP code point 160. Due to a conflict, this document specifies 114. Consequently, this document also updates RFC 3679.', changed pages to 11, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-09-21, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-capport-rfc7710bis and RFC 7710, created updates relation between draft-ietf-capport-rfc7710bis and RFC 3679)