> >> Wasn't aware of that need. One way to make this happen would be for
> the CPE to reset its DUID. But it's no longer smooth renumbering, the prefix
> will simply change. In this case however, this is a user-triggered action, so
> immediate renumbering might be acceptable. Support for RFC7084 L-13
> would be desirable.
> > Ideally the DHCP client generates a new DUID and does not send the old
> DUID. This allows for graceful renumbering, since the old prefix is still
> valid
> until it expires.
>
> Ideally it could use the same DUID and just switch to a different IAID for its
> IA_PD or even keep asking for two IA_PDs with different IAIDs at the same
> time.
FYI. RFC 7084 has the following:
W-5: The IPv6 CE router MUST use a persistent DHCP Unique Identifier
(DUID) for DHCPv6 messages. The DUID MUST NOT change between
network-interface resets or IPv6 CE router reboots.
This requirement exists because CE routers that changed their DUIDs experienced
issues in certain access architectures.
Barbara
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
