[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Captive-portals] Feedback requested: Charter text.
> On Jul 1, 2015, at 1:55 AM, 🔓Dan Wing <[email protected]> wrote:
> On 30-Jun-2015 02:50 pm, Dave Dolson <[email protected]> wrote:
>> Hyperbole aside, the techniques in use today can be deployed in any network gear along the path, even theoretically in a core router, and also to present any kind of alert. Yet the internet has not degraded into chaos.
>> I know that some captive portal enforcement points reside at locations other than WiFi access points. Sometimes the networks aren't even WiFi networks. So failing to provide for those would mean mobile devices would need to continue with proprietary methods and new methods as well.
>> So I think this group could try to solve the general problem, or just address the "WiFi at hotels and airports" problem. The former is what I'd expect from IETF.
> Joining a network (the captive portal problem) is different from injecting content hours or days after an endpoint has joined a network.
I agree and I think the latter should be out of scope.
But we may need a loose definition of “joining a network”. Many airports allow you to join the network and browse some internal sites (departures, arrivals, airport map, stores in the airport), but you get the captive portal as soon as you try to browse to something else.