IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Thu, 10 July 2003 19:10 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 PAA17404; Thu, 10 Jul 2003 15:10:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agnp-0005RW-10; Thu, 10 Jul 2003 15:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agUM-0003dz-GP for dhcwg@optimus.ietf.org; Thu, 10 Jul 2003 14:49:54 -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 OAA16198 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 14:49:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19agUJ-00069m-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 14:49:51 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 19agUI-00069h-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 14:49:50 -0400
Received: from depa.dmes.org (dsl093-187-232.chi2.dsl.speakeasy.net [66.93.187.232]) by toccata.fugue.com (Postfix) with ESMTP id 9D3491B227B; Thu, 10 Jul 2003 13:44:46 -0500 (CDT)
From: Ted Lemon <mellon@fugue.com>
To: Thamer Al-Harbash <tmh@whitefang.com>, narasimha.nelakuditi@nokia.com
Subject: Re: [dhcwg] "client identifier" in server replies
Date: Thu, 10 Jul 2003 13:49:55 -0500
User-Agent: KMail/1.5
Cc: budm@weird-solutions.com, Ted.Lemon@nominum.com, dhcwg@ietf.org
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@siebe002.apac.nokia.com> <Pine.BSF.4.51.0307100841230.3483@helena.whitefang.com>
In-Reply-To: <Pine.BSF.4.51.0307100841230.3483@helena.whitefang.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307101349.55262.mellon@fugue.com>
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

On Thursday 10 July 2003 07:42, Thamer Al-Harbash wrote:
> I think Mr. Lemon already mentioned this, but if he didn't, how
> does this solve the problem of two DHCP DISCOVER messages being
> sent out from two clients with the same xid? How does the server
> differentiate between them?

The server probably doesn't even look at the xid - it just looks at the client 
identifier.   The xid is for the client.   (A server might use the xid as an 
efficiency hack to avoid responding to a retransmission of a message to which 
it's already responding, but it will behave correctly even if it never checks 
xid).


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

v2.23.0 | Report a Bug | By Email