Re: [v6ops] IPv6-Only Preferred DHCPv4 option

[Tommy Pauly <[e-mail]>]

Hi Jen,

Thanks for posting this draft! I find it to be both a well-written document, and a great solution.

This will be particularly critical for networks that want to adopt IPv6-only (read, NAT64), but can't easily ensure that *all* devices on the network upgrade to support that. This concept of IPv6-mostly networks is a good stepping stone! =) What we've seen in cellular networks for NAT64 rollout has had hiccups, and an option like this to smooth the transition would have been useful there. But without an option like this, I don't see a good way for less-managed networks (enterprise Wi-Fis, public Wi-Fis) to make the transition since they can't guarantee what devices are on their networks.

As a client OS vendor, I think this would be easy for the client hosts to implement, and we'd likely see a scenario in which pretty quickly, most modern mobile devices and laptops would support this, and we'd end up with using v4 on networks only for more "legacy" devices.

I'd certainly support this document going forward and being adopted.

Best,
Tommy

> On Dec 4, 2019, at 4:09 AM, Jen Linkova <[e-mail]> wrote:
> 
> Hello,
> 
> One of the biggest issue in deploying IPv6-only LANs is how to do it
> incrementally, when some hosts work just fine in NAT64 environment
> while some legacy devices still need IPv4. Doubling the number of
> network segments (having an IPv6-only and dual-stack segments of each
> type) is an operational nightmare. So it would be just awesome if all
> devices can co-exist in the same network segment and hosts capable of
> operating in IPv6-only environment do not consume IPv4 addresses.
> So here is the draft proposing a new DHCPv4 option to help saving IPv4
> addresses and deploying IPv4-as-a-service:
> 
> Name:           draft-link-dhc-v6only
> Revision:       00
> Title:          IPv6-Only-Preferred Option for DHCP
> Document date:  2019-12-04
> Group:          Individual Submission
> Pages:          9
> URL:
> https://www.ietf.org/internet-drafts/draft-link-dhc-v6only-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-link-dhc-v6only/
> Htmlized:       https://tools.ietf.org/html/draft-link-dhc-v6only-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-link-dhc-v6only
> 
> 
> Abstract:
>   This document specifies a DHCP option to indicate that a host
>   supports an IPv6-only mode and willing to forgo obtaining a IPv4
>   address if the network provides IPv6 access.
> 
> Any comments/suggestions/reviews are highly appreciated!
> 
> Adding v6ops@ to Cc: as the problem is related to operating IPv6-only networks.
> 
> Thank you!
> -- 
> SY, Jen Linkova aka Furry
> 
> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops