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 <[email protected]> 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/captive-portals
>
_______________________________________________
Captive-portals mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/captive-portals
