Lorenzo Colitti wrote:
> Over the years on this list we have seen many use-cases come
> through, I recall:
> - A school/library network that allows most of the Internet,
> but captures and redirects for certain networks / sites
> - A network allows all
On Tue, Feb 6, 2018 at 12:07 PM, David Bird wrote:
>> I'd say that the amount of information provided here is rich enough
>> that you want to talk to a human. Very few networks permit sending of
>> arbitrary packets to arbitrary hosts and the receipt of similar. The
>> point
> On Feb 5, 2018, at 4:54 PM, Martin Thomson wrote:
>
> On Tue, Feb 6, 2018 at 8:41 AM, David Bird wrote:
>>> I have heard UE vendors express a strong desire to be able to know
>>> about status before they attempt to use the network.
>>>
>>
>> Hm,
On Tue, Feb 6, 2018 at 8:41 AM, David Bird wrote:
>> I have heard UE vendors express a strong desire to be able to know
>> about status before they attempt to use the network.
>>
>
> Hm, but (assuming you are using the provided network for DNS, CRL checks,
> and the API itself),
On Tue, Feb 6, 2018 at 5:03 AM, David Bird wrote:
> Thanks Darshak and Tommy, this is really helpful.
Yes, thank you both.
> Some comments:
>
> In 2. Workflow: Does it make sense to reorder 2) and 3)? It would seem
> 'Enforcement' should come before determining status (of said
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Captive Portal Interaction WG of the IETF.
Title : Captive Portal API
Authors : Tommy Pauly
Darshak Thakore