Re: [Captive-portals] Ben Campbell's Yes on charter-ietf-capport-00-01: (with COMMENT)

[David Illsley <davidillsley@gmail.com>]

<snip>

- While I agree that roaming and federated solutions are out of scope, it might be too strong to outright exclude HS2.0/Passpoint, iPass, Boingo, and the like. In HS2.0 release 2, for example, an OSU network can have a captive portal (and I think capport work could apply here) - likewise, I think iPass and Boingo (apps) could benefit form the simplifying of captive portal interactions. (Additionally, even if a network uses 802.1x or an application to authenticate, that doesn't necessarily mean it will be and remain captive portal free -- consider the scenario where a user is being required to top-up their account balance to continue using the 802.1x network).

I'm far from an expert, but my reading of the Hotspot 2.0 OSU buts suggest that it 'fixes' the captive portal problem by giving the client the sign-up/portal address in the OSU handshake (ANQP). Have I misunderstood this?

 

Suggested text:

Out of scope are "roaming" (federation of credentials), network selection, or the on-boarding/provisioning of clients onto secure (or any alternate) networks. These are not captive portal specific problems and have largely been solved in other ways.

On Thu, Oct 15, 2015 at 8:20 PM, John Mann <john.mann@monash.edu> wrote:

Hi,

On a slight tangent, I would like to mention that most client computers are now capable of using IPv6,

with many preferring it because e.g. Facebook reportedly loads 15% faster.

Hopefully, sometime, some networks managed by Captive Portals will become dual-stack.

Lets not set the standard for all future captive portal networks to be IPv4-only forever.

Hopefully, it may even be possible for clients to operate IPv6-only if they choose.

Suggested text:

insert after "- allow endpoints to learn about the parameters of their confinement,"

---

- allow endpoints to learn about and interact with the Captive Portal over IPv6,

  and allow endpoints to access the IPv6 Internet,

---

Thanks,

    John

On 16 October 2015 at 13:04, Barry Leiba <barryleiba@computer.org> wrote:

> Sorry just a typo correction and maybe too late for the comments but
> eduroam should not be eduRoam but eduroam.
>
> It would be great if this typo could be fixed.

And so it is.
Thanks for pointing it out.

Barry

_______________________________________________
Captive-portals mailing list
Captive-portals@ietf.org
https://www.ietf.org/mailman/listinfo/captive-portals

_______________________________________________
Captive-portals mailing list
Captive-portals@ietf.org
https://www.ietf.org/mailman/listinfo/captive-portals

_______________________________________________
Captive-portals mailing list
Captive-portals@ietf.org
https://www.ietf.org/mailman/listinfo/captive-portals