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

narasimha.nelakuditi@nokia.com Thu, 10 July 2003 06:39 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 CAA19680; Thu, 10 Jul 2003 02:39:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aV53-0002uJ-To; Thu, 10 Jul 2003 02:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aV4Y-0002qb-4u for dhcwg@optimus.ietf.org; Thu, 10 Jul 2003 02:38:30 -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 CAA19636 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 02:38:25 -0400 (EDT)
From: narasimha.nelakuditi@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aV4U-0007bl-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 02:38:26 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 19aV4T-0007bh-00 for dhcwg@ietf.org; Thu, 10 Jul 2003 02:38:25 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h6A6cPa15070 for <dhcwg@ietf.org>; Thu, 10 Jul 2003 09:38:25 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6357fc1f04ac158f21084@esvir01nok.ntc.nokia.com>; Thu, 10 Jul 2003 09:38:23 +0300
Received: from siebh001.NOE.Nokia.com ([172.30.195.15]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 10 Jul 2003 09:38:23 +0300
Received: from siebe002.NOE.Nokia.com ([172.30.195.13]) by siebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139); Thu, 10 Jul 2003 14:38:13 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] "client identifier" in server replies
Date: Thu, 10 Jul 2003 14:38:12 +0800
Message-ID: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF9@siebe002.apac.nokia.com>
Thread-Topic: [dhcwg] "client identifier" in server replies
Thread-Index: AcNF9sOZzeReMqKtR3mmTm0Vfc8nNQAtGw1A
To: budm@weird-solutions.com, mellon@nominum.com
Cc: dhcwg@ietf.org
X-OriginalArrivalTime: 10 Jul 2003 06:38:13.0204 (UTC) FILETIME=[D61D5940:01C346AD]
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

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??

regards,
swamy.


> -----Original Message-----
> From: ext Bud Millwood [mailto:budm@weird-solutions.com]
> Sent: Wednesday, July 09, 2003 2:19 PM
> To: Ted Lemon
> Cc: dhcwg@ietf.org; Nelakuditi Narasimha (NET/Bangalore)
> Subject: Re: [dhcwg] "client identifier" in server replies
> 
> 
> On Tuesday 08 July 2003 20.44, Ted Lemon wrote:
> > On Tuesday 08 July 2003 07:49, Bud Millwood wrote:
> > > Filling out chaddr and htype *will* eliminate the 
> problem. As long as
> > > client id is also present, the device will be identified 
> with client id
> > > (which is the preferred identifier).
> >
> > Bud, there are some cases, particularly with firewire, 
> where there is no
> > way to fill out the hardware address.   Of course it needs 
> to be filled out
> > in other cases - the protocol requires it.
> 
> It would seem that if you do not have a hardware address, the 
> only way to 
> guarantee that a response is for you is if your client 
> identifier is in the 
> packet, since that's guaranteed to be unique on the "subnet" 
> ("segment" seems 
> a better word choice - 2131.2p5). And XID then only needs to 
> be unique across 
> DHCP transactions on the specific client.
> 
> I don't recall seeing anything that stated that chaddr *must* 
> be globally 
> unique for a given htype, so is it not possible to assume 
> that if your client 
> identifier is unique for your segment, that it could also 
> qualify as a 
> chaddr?
> 
> I can hear the groans now. :) 16 bytes is arbitrary, and this 
> makes a direct 
> link between chaddr and clientid, but only at the client 
> side, and only for 
> packet identification.
> 
> If not, Narasimha's proposal is the only solution I can see.
> 
> 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