Captive Portal API
draft-ietf-capport-api-05
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (capport WG)
|
|
Authors |
|
Tommy Pauly
,
Darshak Thakore
|
|
Last updated |
|
2020-02-04
(latest revision 2020-01-02)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Captive Portal Interaction T. Pauly, Ed.
Internet-Draft Apple Inc.
Intended status: Standards Track D. Thakore, Ed.
Expires: 7 August 2020 CableLabs
4 February 2020
Captive Portal API
draft-ietf-capport-api-05
Abstract
This document describes an HTTP API that allows clients to interact
with a Captive Portal system.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 7 August 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Pauly & Thakore Expires 7 August 2020 [Page 1]
Internet-Draft Captive Portal API February 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. API Details . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. URI of Captive Portal API endpoint . . . . . . . . . . . 3
4.1.1. Server Authentication . . . . . . . . . . . . . . . . 4
4.2. JSON Keys . . . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Example Interaction . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5.1. Privacy Considerations . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6.1. Captive Portal API JSON Media Type Registration . . . . . 7
6.2. Captive Portal API Keys Registry . . . . . . . . . . . . 8
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document describes a HyperText Transfer Protocol (HTTP)
Application Program Interface (API) that allows clients to interact
with a Captive Portal system. The API defined in this document has
been designed to meet the requirements in the Captive Portal
Architecture [I-D.ietf-capport-architecture]. Specifically, the API
provides:
* The state of captivity (whether or not the client has access to
the Internet)
* A URI that a client browser can present to a user to get out of
captivity
* An encrypted connection (TLS for both the API and portal URI)
2. Terminology
This document leverages the terminology and components described in
[I-D.ietf-capport-architecture] and additionally uses the following
association:
* Captive Portal Client: The client that interacts with the Captive
Portal API is typically some application running on the User
Equipment that is connected to the Captive Network. This is also
referred to as the "client" in this document.
Pauly & Thakore Expires 7 August 2020 [Page 2]
Internet-Draft Captive Portal API February 2020
* Captive Portal API Server: The server exposing the API's defined
in this document to the client. This is also referred to as the
"API server" in this document.
3. Workflow
The Captive Portal Architecture defines several categories of
interaction between clients and Captive Portal systems:
Show full document text