Captive Portal API
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- 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.
- Publication Date
- 2020-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8908- Link
- https://doi.org/10.17487/RFC8908
- Author(s)
- Tommy PaulyDarshak Thakore
Latest version of IETF RFC 8908
Document Versions — IETF RFC 8908
-
▶ IETF RFC 8908 (2020-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5905 [Active*]
- IETF RFC 6066 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6960 [Active*]
- IETF RFC 7234 [Superseded*]
- IETF RFC 8126 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8259 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-capport-architecture-08 — I-D.ietf-capport-architecture EXTERNAL
- IETF RFC 7525 [Superseded*]
- IETF RFC 8264 [Active*]
- IETF RFC 8910 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8908.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8908, Captive Portal API. Available at https://doi.org/10.17487/RFC8908
Snippet:
IETF RFC 8908, Captive Portal API. Available at https://doi.org/10.17487/RFC8908
HTML (ISO 690 compliant)
Preview:
IETF RFC 8908, Captive Portal API. Available at https://doi.org/10.17487/RFC8908
Snippet:
<span class="citation"><cite>IETF RFC 8908</cite>, Captive Portal API. Available at <a href="https://doi.org/10.17487/RFC8908" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8908</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc8908">IETF RFC 8908</cite>, Captive Portal API <span class="doi">10.17487/RFC8908</span> </li>
Referenced By
- IETF RFC 8910 [Active*]
- IETF RFC 8952 [Active*]