RFC 7710
Captive-Portal Identification Using DHCP or Router Advertisements (RAs), December 2015
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 8910
- Authors:
- W. Kumari
O. Gudmundsson
P. Ebersman
S. Sheng - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7710
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7710
Abstract
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 customer can do until the customer has authenticated.
This document describes a DHCP option (and a Router Advertisement (RA) extension) to inform clients that they are behind some sort of captive-portal device and that they will need to authenticate 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 used in larger solutions. The method of authenticating to and interacting with the captive portal is out of scope for this document.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.