RFC 8952: Captive Portal Architecture
In plain English — editorial summary, not part of the RFC
This document describes a captive portal architecture. Network provisioning protocols such as DHCP or Router Advertisements (RAs), an optional signaling protocol, and an HTTP API are used to provide the solution.
Document record
- Document ID
- RFC8952
- Published
- November 2020
- Authors
- K. Larose; D. Dolson; H. Liu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
- RFC 9467Relaxed Packet Counter Verification for Babel MAC AuthenticationCurrent
January 2024
- RFC 8910Captive-Portal Identification in DHCP and Router Advertisements (RAs)Current
September 2020
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
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?