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

Re: [Captive-portals] Fixing RFC 7710

On Sat, Mar 3, 2018 at 8:58 AM, Ólafur Guðmundsson
<[email protected]> wrote:
> Fixing or make RFC7710 more useful ?

Both, I hope.

Thanks for your reply.

>> Erik and I would like to propose a plan for that work.  We would keep
>> this to addressing the issues that we have identified thus far.
>> Namely:
>> 1. The purpose of the URI is not well defined.  We would reference the
>> capport architecture and API documents for that.  The group would need
>> to decide between:
>>   a. point to the API
>>   b. point to a login page
> Our (or at least my thought) was in the beginning,
> just send the device to the location of the portal, as I hate having
> connections intercepted.
> Then the USER could just see that page and decide what to do.

I think that the idea is this:

If the URI is the special one, then the process is done and the
network good to use.
If the URI is special, find the API and check status.  If the portal
says OK, then the network is good to use.
If the API returns captive, open the login page in a browser.

We don't have any more automation than this, but you will observe that
there isn't any probing.  The network can make a clear statement
quickly an unambiguously about access.  If the situation is more
complex (as we have seen that it often is, then it can use the login
page to convey that additional information).