Using Provisioning Domains for Captive Portal Discovery
draft-pfister-capport-pvd-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-01-01 (latest revision 2018-06-30) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-pfister-capport-pvd-00.txt
Abstract
Devices that connect to Captive Portals need a way to identify that the network is restricted and discover a method for opening up access. This document defines how to use Provisioning Domain Additional Information to discover a Captive Portal API URI.
Authors
Pierre Pfister
(pierre.pfister@darou.fr)
Tommy Pauly
(tpauly@apple.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)