dhcpcd-discuss

On 15/02/17 15:42, Shahid Mahmood wrote:
>>>> At this point, I just wanted to confirm if the behavior is in accordance
>>>> with the RFC.
>>> Section 17.1.3 says the client MAY select a better server, not MUST.
>>> So yes, in the strict sense dhcpcd is in compliance even though it
>>> ignores the option.
>>>
>>> Making dhcpcd react to a more preferred server right away would be quite
>>> easy.
>>> Storing the adverts for a period of time and then choosing the more
>>> preferred one to bind to would be trickier.
>>> Right now, I'm not sure which is the better solution.
>> Or maybe something in the middle. Save the first advert received. Then for 2-5 seconds, receive an advert, compare it with the saved advert, and save the 'better' one. At timeout, use the saved advert. Of course, determining 'better' may be the real challenge.
>>
>> Does it make sense to choose a route now, then later change if a better offer comes along?
>>
>> N
> As per RFC section quoted above:
> 
>     -	Those Advertise messages with the highest server preference
>         	valueThose Advertise messages with the highest server preference
>         	value
> 
> Is this a *must* or *may* ?

Neither word is present, so it's more of a recommendation.

Roy