RFC 8910: Captive-Portal Identification in DHCP and Router Advertisements (RAs)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8910
- Published
- September 2020
- Authors
- W. Kumari; E. Kline
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8952Captive Portal ArchitectureCurrent
November 2020
- RFC 8908Captive Portal APICurrent
September 2020
- RFC 8898Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)Current
September 2020
- RFC 8887A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocketCurrent
August 2020
- RFC 8943Concise Binary Object Representation (CBOR) Tags for DateCurrent
November 2020
- RFC 8876Non-interactive Emergency CallsCurrent
September 2020
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8873Message Session Relay Protocol (MSRP) over Data ChannelsCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?