Re: [dhcwg] Failover: transition out of potential-conflict.

>
>         But, I think the primary would not actually assign the IP
>         address to anyone after it goes into NORMAL state.  Part
>         of the work of the primary processing the secondary's
>         lease database is for the primary to resolve conflicts in
>         real time while receiving the BNDUPD's.  The secondary
>         cannot send the UPDDONE until the primary has processed
>         all of the BNDUPD's in some way.

I misspoke slightly there - I said "NORMAL" when I meant "CONFLICT-DONE."   
The primary will think that the address is in the free state until it gets 
the update from the secondary telling it that the secondary assigned it to 
a client.   So there's a window, potentially fairly long at a large 
installation, in which the primary can allocate that address, thinking it 
is free.   If it does so, the problem will be discovered during the 
resolution process, but it'll be too late at that point - two clients will 
have been assigned the same IP address.

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg