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

Sanjeev Verma <sverma@redback.com> Mon, 14 July 2003 17:41 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 NAA07616; Mon, 14 Jul 2003 13:41:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7Jt-0004H1-99; Mon, 14 Jul 2003 13:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7JS-0004Gd-Gg for dhcwg@optimus.ietf.org; Mon, 14 Jul 2003 13:40:34 -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 NAA07590 for <dhcwg@ietf.org>; Mon, 14 Jul 2003 13:40:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19c7JQ-0003ni-00 for dhcwg@ietf.org; Mon, 14 Jul 2003 13:40:32 -0400
Received: from prattle.redback.com ([155.53.12.9]) by ietf-mx with esmtp (Exim 4.12) id 19c7JP-0003nf-00 for dhcwg@ietf.org; Mon, 14 Jul 2003 13:40:31 -0400
Received: from redback.com (asia.redback.com [155.53.42.122]) by prattle.redback.com (Postfix) with ESMTP id 3FB729B67C1; Mon, 14 Jul 2003 10:40:30 -0700 (PDT)
Message-ID: <3F12EB0E.7020700@redback.com>
Date: Mon, 14 Jul 2003 10:40:30 -0700
From: Sanjeev Verma <sverma@redback.com>
Organization: Redback networks Inc.
User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.1) Gecko/20020829
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: narasimha.nelakuditi@nokia.com
Cc: budm@weird-solutions.com, mellon@nominum.com, dhcwg@ietf.org
Subject: Re: [dhcwg] "client identifier" in server replies
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FFB@siebe002.apac.nokia.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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

Since the problem is faced by the clients that apparently have no h/w 
address, sending parameter request list that includes client id should 
work for them.
- Sanjeev.



narasimha.nelakuditi@nokia.com wrote:
> If client-id is stored in h/w addr field, we can't store client-id of more than 16-bytes as you pointed out. 
> If servers check for the validity of h/w type and corresponding h/w length, then one has to pad client-id to next valid length (by the way, is server supposed to validate h/w type and h/w len values?).
> 
> Apart from firewire case, another case in which valid h/w value is not available for clients is if DHCP is used to allocate IP addresses for mobiles. 
>  
> regards,
> swamy.
> 
> 
> 
>>-----Original Message-----
>>From: ext Bud Millwood [mailto:budm@weird-solutions.com]
>>Sent: Thursday, July 10, 2003 8:27 PM
>>To: Nelakuditi Narasimha (NET/Bangalore); mellon@nominum.com
>>Cc: dhcwg@ietf.org
>>Subject: Re: [dhcwg] "client identifier" in server replies
>>
>>
>>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
> 


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