RE: [dhcwg] "client identifier" in server replies

Hi Thamer, I was discussing the case in which client fills "Client ID" field but NOT "Client Hardware addr(MAC)". This is possible as servers identify clients using EITHER "Client ID" OR "Client HW addr".  
Coming back to 'xid', I think checking 'xid' alone is not a good idea, considering erroneous servers, multiple clients using same xids etc. 

regards,
swamy.

> -----Original Message-----
> From: ext Thamer Al-Harbash [mailto:tmh@whitefang.com]
> Sent: Monday, July 07, 2003 11:30 PM
> To: Nelakuditi Narasimha (NET/Bangalore)
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] "client identifier" in server replies
> 
> 
> On Mon, 7 Jul 2003 narasimha.nelakuditi@nokia.com wrote:
> 
> > Hi, If the client is setting "client identifier" but not 
> "client hardware addr" in the messages that it is sending to 
> server, server is supposed to identify it with "client 
> identifier". But as per RFC2131, server MUST NOT fill "client 
> identifier" option in OFFER and ACK messages. If this is the 
> case, how is client supposed to validate the response (as 
> 'xid' alone is not sufficient)???
> 
> Why? An xid is a 32-bit unsigned integer. That's about as many IP
> addresses as are possibly with IPv4. Unless you're picking your
> xid badly, this shouldn't be a problem.
> 
> Also, unless the client requests broadcasts with the broadcast
> bit, the server will be unicasting replies to it. The MAC
> addresses with the xid should be sufficient.
> 
> -- 
> Thamer Al-Harbash
> 

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