Re: [dhcwg] Mail regarding draft-ietf-dhc-addr-notification

[Jen Linkova <[e-mail]>]

Hi Aditi,

On Fri, Jan 5, 2024 at 3:31 AM Aditi Patange
<Aditi.Patange=[e-mail]> wrote:
> I am Aditi Patange from Microsoft. I recently came across ‘Registering Self-generated IPv6 Addresses using DHCPv6’ draft and I would like to surface some questions on behalf of the Windows DHCP client team.

> Section 4.6 “Whenever the client creates an address or receives a PIO which changes the Valid Lifetime of an existing address by more than 1%”
>
> The Prefix Information Option aspect of the above statement requires the client to listen to the state of every address on every adapter, and store significant additional state. The client needs to track every address on every adapter, lifetime of each address, and has to store both the existing time as well as the newly-received time. Needless to say, this could lead to race conditions. Also, as the draft briefly acknowledged, this refresh logic would have significant power implications especially for devices running in low power mode. Can we please simplify the renewal logic to reduce computation required by the client?

I'd like to thank you for pointing this out. While discussing your
point we realized that the algorithm does have an issue: if an RA
arrives soon after the scheduled registratration event, it would cause
another packet to be sent, so it's suboptimal.

We have just submitted -09 which contains an updated algorithm which
ensures that for each address the client sends just one (well, if you
do not count retransmits) registration per the PIO lifetime, and that
updates for the addresses with same lifetimes are happening at the
same time.

-- 
Cheers, Jen Linkova