IETF Logo Mail Archive

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

Bud Millwood <budm@weird-solutions.com> Thu, 10 July 2003 14:56 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 KAA05772; Thu, 10 Jul 2003 10:56: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 19acq1-0006pb-PO; Thu, 10 Jul 2003 10:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acp8-0006k5-0c for dhcwg@optimus.ietf.org; Thu, 10 Jul 2003 10:55:06 -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 KAA05698 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 10:55:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acp5-0003bU-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 10:55:03 -0400
Received: from webmail.mail.se.dataphone.net ([212.37.1.50] helo=intermail.se.dataphone.net) by ietf-mx with esmtp (Exim 4.12) id 19acp4-0003bR-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 10:55:02 -0400
Received: from [193.12.201.10] (account budm@weird-solutions.com HELO offset.weird.se) by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.0.5) with ESMTP id 1535553; Thu, 10 Jul 2003 16:54:54 +0200
Content-Type: text/plain; charset="iso-8859-1"
From: Bud Millwood <budm@weird-solutions.com>
Reply-To: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: narasimha.nelakuditi@nokia.com, mellon@nominum.com
Subject: Re: [dhcwg] "client identifier" in server replies
Date: Thu, 10 Jul 2003 16:56:50 +0200
User-Agent: KMail/1.4.3
Cc: dhcwg@ietf.org
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@siebe002.apac.nokia.com>
In-Reply-To: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@siebe002.apac.nokia.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200307101656.50160.budm@weird-solutions.com>
Content-Transfer-Encoding: quoted-printable
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: quoted-printable

On Thursday 10 July 2003 08.38, 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??

How many clients are going to discard valid server responses if they contain 
the clientid field? (i.e. how many working implementations will break?)

If your wire protocol has absolutely no way of identifying nodes on that wire, 
the only way to use DHCP is for each node to be able to uniquely identify 
itself. Whether your node or your wire-level protocol generates the unique 
identifier, that identifier should serve as your hw address, IMHO. Is there 
anything wrong with this line of thought?

If you can't cram it into 16 bytes, that's another issue. :)

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687
mailto:budm@weird-solutions.com


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

v2.23.0 | Report a Bug | By Email