RE: [dhcwg] Client behavior with Parameter Request List

> -----Original Message-----
> From: Ted Lemon
>
> On May 18, 2004, at 8:05 PM, Kevin A. Noll wrote:
>
> > I can't find any statement as to what should
> > happen if the client *does not* include the list.
> > Clearly it would be a protocol violation
> > and therefore a broken client if it didn't, but
> > what should the server do about it? I assume it
> > should drop the message.
> >
>
> The intent was that the client must do this if it
> expects to get a consistent response from the DHCP
> server.  Of course you should not drop the packet
> if it doesn't follow this.  The point is that you
> don't have to bend over backwards to be
> consistent if the client violates this restriction.
>

Ted--

while I agree that servers should be "liberal in what they
accept, strict in what they send," this is a good example of
the questions that arise [and must be settled by agreements
outside the text of RFCs] when the protocol behavior is not
tightly specified.  One shouldn't have to mandate absolutely
every behavior in an RFC, but I think your summary of the
point would make an excellent correction for RFC2131bis....

"A client MUST send a consistent Parameter Request List if
it expects the DHCP server to provide consistent responses
to DHCPDISCOVER and DHCPREQUEST messages.  If a client does
not send a consistent Parameter Request List, the server MAY
choose to resolve any conflicts according to [local]
implementation policy, which is not specified by this memo."

--Barr

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