RFC 7710: Captive-Portal Identification Using DHCP or Router Advertisements (RAs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8910.
Current version: 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 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.
Document record
- Document ID
- RFC7710
- Published
- December 2015
- Authors
- W. Kumari; O. Gudmundsson; P. Ebersman; S. Sheng
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
- Obsoleted by:
- RFC 8910
Referenced by
One later RFC formally updates or obsoletes part of this document.
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?