Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

[Mark Smith <[e-mail]>]

Hi David, Brian,

On Mon, 6 May 2019 at 09:29, Brian E Carpenter
<[e-mail]> wrote:
>

<snip>


> > Finally how about some additional non-normative discussion about taking precautions to prevent unsuspecting WiFi users from accidentally connecting IPv4-Only WiFi hosts to IPv6-Only WiFi links.

I don't think we have to worry about that. An IPv4 only host attached
to an IPv6 only network should already be generating informative
enough error messages for its users to indicate that network
connectivity is not working (such as those we already see in web
browsers when our Internet goes down, or network connectivity problem
popup alerts in window manager notification areas).


> Possibly by including "IPv6" or "IPv6-Only" in the name of open SSIDs to help inform unsuspecting WiFi users,

I'd generally try to avoid providing that advice. It is overloading
SSIDs with information they're not intending to carry, and also is
assuming that the end-users know what the terms "IPv4" or "IPv6" mean.
Most end-users don't. It's only really valid when the end-users are
networking technology aware (IETF and other network engineering
conferences, technical labs, but not many other situations).


> using secured SSIDs to prevent unsuspecting WiFi users from connecting all, or using 802.11u Access Network Query Protocol (ANQP) with "Address type available" for IPv6 and "Address type not available" for IPv4 to inform the connecting WiFi host instead of the user. Putting this in an appendix would be fine with me.
>

It sounds like ANQP is the theoretically correct way to solve this
problem, as it is a network layer agnostic protocol.

However, it seems it is limited to 802.11, where as the issue of
excessive link-layer IPv4 broadcasts can also occur on wired networks
(c.f., RFC6820 - "Address Resolution Problems in Large Data Center
Networks", and I saw link-layer broadcast traffic being a potential
issue on large wired LANs (1200+ PCs in one instance, 4000+ in
another) in large enterprises in the late 1990s (this latter
experience is why I support this ID).

The other thing about using RAs for this is that all IPv6 enabled
hosts are going to understand them because it is a underpinning
requirement for an IPv6 implementation. Hosts that can attach
successfully to an IPv6 Only link are already assured to be able to
receive and process RAs, they just need to be updated to support this
flag, verses having an entirely new ANQP protocol implementation.


Regards,
Mark.


> Yes, this got lost on the editing room floor. I still think it's useful.
>
> Thanks
>    Brian
>
> > Remember the IETF's own discussions regarding this issue. If the IETF isn't willing to have its default WiFi be IPv6-only, maybe some caution is warranted for the general population of the earth. :)
> >
> > Thanks
> >
> >
> >
> > On Mon, Apr 29, 2019 at 5:02 AM Ole Troan <[e-mail] <mailto:[e-mail]>> wrote:
> >
> >     At the 6man meeting at IETF 104 in Prague there was support to close the working group last call and advance
> >     draft-ietf-6man-ipv6only-flag-05 to the IESG.
> >
> >     This call is to confirm that decision on the mailing list.
> >
> >     Please give objections and comments to this decision to the mailing list, by 2019-05-13.
> >
> >     Best regards,
> >     Ole, 6man co-chair
> >     --------------------------------------------------------------------
> >     IETF IPv6 working group mailing list
> >     [e-mail] <mailto:[e-mail]>
> >     Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >     --------------------------------------------------------------------
> >
> >
> >
> > --
> > ===============================================
> > David Farmer               Email:farmer@umn..edu <mailto:[e-mail]>
> > Networking & Telecommunication Services
> > Office of Information Technology
> > University of Minnesota
> > 2218 University Ave SE        Phone: [phone]
> > Minneapolis, MN 55414-3029   Cell: 612-812-9952
> > ===============================================
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > [e-mail]
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------