RFC 8908: Captive Portal API
In plain English — editorial summary, not part of the RFC
This document describes an HTTP API that allows clients to interact with a Captive Portal system. With this API, clients can discover how to get out of captivity and fetch state about their Captive Portal sessions.
Document record
- Document ID
- RFC8908
- Published
- September 2020
- Authors
- T. Pauly; D. Thakore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8910Captive-Portal Identification in DHCP and Router Advertisements (RAs)Current
September 2020
- RFC 8898Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)Current
September 2020
- RFC 8887A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocketCurrent
August 2020
- RFC 8876Non-interactive Emergency CallsCurrent
September 2020
- RFC 8873Message Session Relay Protocol (MSRP) over Data ChannelsCurrent
January 2021
- RFC 8943Concise Binary Object Representation (CBOR) Tags for DateCurrent
November 2020
- RFC 8871A Solution Framework for Private Media in Privacy-Enhanced RTP Conferencing (PERC)Current
January 2021
- RFC 8870Encrypted Key Transport for DTLS and Secure RTPCurrent
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?