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

Re: [Captive-portals] Improve the user experience of captive portals as they're commonly understood and currently deployed



Do the architectural elements in the capport-architecture draft accurately capture "captive portals as they're commonly understood and currently deployed"?

I have no experience with which to easily distinguish between elements that are present and common in existing implementations and those that exist in the draft solely for the purpose of meeting the proposed solution behaviour outlined in section 3.

On 14 April 2017 at 21:37, David Bird <[email protected]> wrote:
Can we get back on track and focus on our goal of improving the user experience of captive portals as they're commonly understood and currently deployed? 

_______________________________________________
Captive-portals mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/captive-portals


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature