IETF Logo Mail Archive

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

Thamer Al-Harbash <tmh@whitefang.com> Thu, 10 July 2003 17:36 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 NAA13617; Thu, 10 Jul 2003 13:36:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afKt-00056u-3P; Thu, 10 Jul 2003 13:36:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aal9-0003wQ-V0 for dhcwg@optimus.ietf.org; Thu, 10 Jul 2003 08:42:52 -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 IAA29315 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 08:42:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aal8-0002NB-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 08:42:50 -0400
Received: from helena.whitefang.com ([216.254.175.50] ident=0xdeadbeef) by ietf-mx with smtp (Exim 4.12) id 19aal7-0002N8-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 08:42:49 -0400
Received: (qmail 5933 invoked from network); 10 Jul 2003 12:43:02 -0000
Received: from helena.whitefang.com (216.254.175.50) by 0 with SMTP; 10 Jul 2003 12:43:02 -0000
Date: Thu, 10 Jul 2003 08:42:59 -0400
From: Thamer Al-Harbash <tmh@whitefang.com>
X-X-Sender: shadows@helena.whitefang.com
To: narasimha.nelakuditi@nokia.com
cc: budm@weird-solutions.com, mellon@nominum.com, dhcwg@ietf.org
Subject: RE: [dhcwg] "client identifier" in server replies
In-Reply-To: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@siebe002.apac.nokia.com>
Message-ID: <Pine.BSF.4.51.0307100841230.3483@helena.whitefang.com>
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@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 Thu, 10 Jul 2003 narasimha.nelakuditi@nokia.com wrote:

> After discussing several alternatives to solve the problem, servers
> including "client id" field in their replies seems to be the clean
> solution to it.
> If this is agreed upon, next thing is how to fix this in the protocol??

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?

-- 
Thamer Al-Harbash

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

v2.23.0 | Report a Bug | By Email