Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 2023

[Ole Troan <[e-mail]>]

Jen,

>>>>> This really needs to be validated by enterprise operators before proceeding.
>>> 
>>> That's why we have asked for early allocation and WGLC. At least one
>>> enterprise operator is very much interested in deploying this.
>>> 
>>>> I’ll leave it at that. But I would strongly suggest we hear from the Enterprise operator community.
>>> 
>>> As an enterprise operator I support that proposal (as you can probably
>>> tell from the 'authors' section ;-P)
>> 
>> Yeah, as you probably would guess I would like to see input from someone different than Google IT.
>> The vendor who is also the main culprit for why the address assignment situation is as hopeless as it is.
> 
> This is becoming more like a topic for v6ops, but...My point is that
> even if all enterprise devices support DHCPv6 IA_NA (let's say there
> are no Android devices on the network), that it's not possible to
> build an DHCPv6-only enterprise network. SLAAC is required and will be
> required at least for some time. So it's not a matter of supporting
> DHCPv6 IA_NA or not.

I don’t think that statement is correct in the general case.
For your statement to be true, you would have to assume IPv6 only on the link and you would have to assume 464XLAT.

464XLAT isn’t the only way to bring IPv4 connectivity to IPv4 only applications.
I would imagine you could also build a 464CLAT that can share address with the host address.
You could even give out two addresses in DHCP IA_NA if that was required.

I think you can run a network with DHCPv6 only.
In face I’m sitting on such a network right now. Albeit with IPv4 also enabled.

O.