Re: [v6ops] [dhcwg] IPv6-Only Preferred DHCPv4 option

[Jen Linkova <[e-mail]>]

On Thu, Dec 5, 2019 at 4:29 AM Ted Lemon <[e-mail]> wrote:
>
> This is good in principle. The client behavior section should require the client to send a parameter request list and to specify the option code of the new option in the list along with any other options it expects to get.


Thanks Ted! A clarifying question: the draft currently say
(https://tools.ietf.org/html/draft-link-dhc-v6only-00#section-3.2)

"IPv6-only capable clients SHOULD include the IPv6-only Preferred
option in the Parameter Request List in DHCPDISCOVER and DHCPREQUEST
messages."

Do you think smth else should be required here?

> > On Dec 4, 2019, at 04:09, 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
> >
> > _______________________________________________
> > dhcwg mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/dhcwg



-- 
SY, Jen Linkova aka Furry