RE: [dhcwg] Client behavior with Parameter Request List

That makes sense. Thanks!

Now, I wonder if any server implementations actually check this.

--kan--

> -----Original Message-----
> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of Ted
> Lemon
> Sent: Wednesday, 19 May, 2004 5:59 PM
> To: Kevin A. Noll
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] Client behavior with Parameter Request List
> 
> 
> 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.
> >
> > Taking this to a different level of discussion - I question the
> > purpose of making this requirement. I can understand why you
> > would want to require options like "Client Identifier" to always
> > be sent, I'm not sure why the parameter request list must always
> > be included.
> 
> 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.
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 

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