{
  "number": 7710,
  "title": "Captive-Portal Identification Using DHCP or Router Advertisements (RAs)",
  "authors": [
    "W. Kumari",
    "O. Gudmundsson",
    "P. Ebersman",
    "S. Sheng"
  ],
  "published": "2015-12",
  "status": "Proposed Standard",
  "stream": "IETF",
  "pages": 8,
  "formats": [
    "TXT",
    "HTML"
  ],
  "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.\n\nThis 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.",
  "draft": "draft-wkumari-dhc-capport-16",
  "doi": "10.17487/RFC7710",
  "obsoleted_by": [
    "RFC8910"
  ],
  "urls": {
    "html": "https://rfc.dk/rfc7710/",
    "text": "https://rfc.dk/rfc7710.txt",
    "rfc_editor": "https://www.rfc-editor.org/rfc/rfc7710",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7710/"
  },
  "text_modified": "2015-12-08T00:33:50Z"
}