[dhcwg] Desynchronization in DHCPv6

[Christian Vogt <chvogt at tm.uka.de>]

DHCP folks,

I might be missing something, but I am wondering how DHCPv6 realizes
desynchronization between the Advertise messages of multiple servers:

When a DHCPv6 client initiates a 4-way handshake, it sends a Solicit
message and waits for responding Advertise messages for a period of 1.0
to 1.1 s.

At first glance, it seems that the purpose of this delay is to allow
multiple on-link DHCPv6 servers to randomly delay their Advertise
messages a bit in an effort to avoid collisions with the Advertise
messages of neighboring servers.

OTOH, according to RFC 3315, a DHCPv6 server sends its Advertise message
promptly upon receiving a Solicit message.  Hence my questions:

(1)  Why does a client have to wait for between 1.0 and 1.1 s after
sending the Solicit message?

(2)  And if not through randomly delaying Advertise messages, how does
DHCPv6 guarantee desynchronization between the Advertise messages of
multiple servers?

Thanks a lot in advance!

- Christian

-- 
Christian Vogt, Institute of Telematics, Universitaet Karlsruhe (TH)
www.tm.uka.de/~chvogt/pubkey/



_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg