Skip to main content

Captive-Portal Identification Using DHCP or Router Advertisements (RAs)
RFC 7710

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed author "S. Sheng": changed name from "Steve Sheng" to "S. Sheng", cleared country (was "United States"), changed order from "3" to "4"
2026-05-20
(System) Changed author "P. Ebersman": changed name from "P Ebersman" to "P. Ebersman", changed order from "2" to "3"
2026-05-20
(System)
Changed author "O. Gudmundsson": changed name from "Ólafur Guðmundsson" to "O. Gudmundsson", changed affiliation from "CloudFlare" to "Couldflare", cleared country (was "United States"), changed order …
Changed author "O. Gudmundsson": changed name from "Ólafur Guðmundsson" to "O. Gudmundsson", changed affiliation from "CloudFlare" to "Couldflare", cleared country (was "United States"), changed order from "1" to "2"
2026-05-20
(System) Changed author "W. Kumari": changed name from "Warren Kumari" to "W. Kumari", cleared country (was "United States"), changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2025-02-14
(System) Received changes through RFC Editor sync (removed Errata tag)
2025-02-11
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'In many environments offering short-term or temporary Internet access (such as coffee shops), it is common …
Received changes through RFC Editor sync (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 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.')
2015-12-07
(System) RFC published