I am curious why section 3.4 does not consider the MAC Address as a possible identifier?
--
Bob Harold
On Mon, May 11, 2020 at 12:56 PM The IESG <iesg-secretary@xxxxxxxx> wrote:
The IESG has received a request from the Captive Portal Interaction WG
(capport) to consider the following document: - 'CAPPORT Architecture'
<draft-ietf-capport-architecture-08.txt> as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2020-05-25. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
This document describes a CAPPORT architecture. DHCP or Router
Advertisements, an optional signaling protocol, and an HTTP API are
used to provide the solution. The role of Provisioning Domains
(PvDs) is described.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-capport-architecture/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
Captive-portals mailing list
Captive-portals@xxxxxxxx
https://www.ietf.org/mailman/listinfo/captive-portals
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
