[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Captive-portals] Proposals to discover Provisioning Domains (& Captive Portals)

HI Tommy,

I agree, there is synergy, particularly as it relates to our desire to have a HTTP API like the one in your I-D.

A few high-level comments:

- Could RFC 7710 be used to identify the PvD?

- Do you envision this API being implemented in NAS devices (by vendors) or portals (by hotspot web/portal developers)? 

- In section 5.3 Reachability, would the client be learning all the available resources (e.g. the walled garden)? As a hotspot operator, I would probably prefer only giving this information on a need-to-know basis and not expose all my partners (advertisers, roaming partners, etc) to every visitor upon arrival. 

- I believe we could improve (real-time) signaling with capport ICMP (and the overall capport architecture

On Sun, Mar 12, 2017 at 12:34 PM, Tommy Pauly <[email protected]> wrote:

I wanted to give the CAPPORT group a heads up about some related work in the explicit discovery of Provisioning Domains (PvDs), that provides one way of discovering and interacting with Captive Portals and other features of a network:

Proposals to discover Provisioning Domains

PvDs are a concept from MIF, and before that group closed, one of the open questions was how to discover and communicate explicit information about networks and prefix ranges to a device. We've been working on this with Cisco, Apple, and Google contributors, and we think that there is a lot of potential synergy with the captive portal discovery.

The document also goes into various tradeoffs of approaches to getting this information, which is a relevant conversation for how we discover and contact captive portals as well.

Please take a read through and let us know your thoughts!

Tommy Pauly

Captive-portals mailing list
[email protected]