Re: [dhcwg] Comment on a couple of option drafts that have gone by...

On Aug 3, 2004, at 4:55 PM, Kim Kinnear wrote:
> I strongly believe that saying that a DHCP server MUST
>         NOT send this option unless a client requests it is very
>         much not the way to achieve this end.  This will require
>         special case code in every DHCP server which wants to be
>         compliant with this draft (and future RFC).  I see this
>         as a "cure worse than the disease".

How about making it a SHOULD NOT?   I don't really want to add a 
special case to my server to do this either, but I do want there to be 
strong language there about it.   I agree that it's really a client 
requirement, and that we should say what we really want, but I have 
found that client implementors quite frequently only skim the spec, so 
it'd be nice if there were two places where they could read something 
that would make them want to do the right thing, and not just one such 
place.

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