IETF Logo Mail Archive

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

Thamer Al-Harbash <tmh@whitefang.com> Tue, 08 July 2003 12:51 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19902; Tue, 8 Jul 2003 08:51:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zrvx-0008Oe-2k; Tue, 08 Jul 2003 08:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZaH3-0000sV-0B for dhcwg@optimus.ietf.org; Mon, 07 Jul 2003 13:59:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05454 for <dhcwg@ietf.org>; Mon, 7 Jul 2003 13:59:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZaH0-0007f3-00 for dhcwg@ietf.org; Mon, 07 Jul 2003 13:59:34 -0400
Received: from helena.whitefang.com ([216.254.175.50] ident=0xdeadbeef) by ietf-mx with smtp (Exim 4.12) id 19ZaGz-0007ew-00 for dhcwg@ietf.org; Mon, 07 Jul 2003 13:59:33 -0400
Received: (qmail 84388 invoked from network); 7 Jul 2003 17:59:45 -0000
Received: from helena.whitefang.com (216.254.175.50) by 0 with SMTP; 7 Jul 2003 17:59:45 -0000
Date: Mon, 07 Jul 2003 13:59:45 -0400
From: Thamer Al-Harbash <tmh@whitefang.com>
X-X-Sender: shadows@helena.whitefang.com
To: narasimha.nelakuditi@nokia.com
cc: dhcwg@ietf.org
Subject: Re: [dhcwg] "client identifier" in server replies
In-Reply-To: <79A2DB53BC51BD448F0D19A86FB1DB637F1AA2@siebe002.apac.nokia.com>
Message-ID: <Pine.BSF.4.51.0307071357310.84296@helena.whitefang.com>
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1AA2@siebe002.apac.nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

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

v2.23.0 | Report a Bug | By Email