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

Ted Lemon <mellon@fugue.com> Tue, 08 July 2003 21:29 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 RAA11238; Tue, 8 Jul 2003 17:29:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19a01F-0007wi-Kf; Tue, 08 Jul 2003 17:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZzrU-0007ZK-D4 for dhcwg@optimus.ietf.org; Tue, 08 Jul 2003 17:18:56 -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 RAA10953 for <dhcwg@ietf.org>; Tue, 8 Jul 2003 17:18:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZzrR-0006g4-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 17:18:53 -0400
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 19ZzrQ-0006g1-00 for dhcwg@ietf.org; Tue, 08 Jul 2003 17:18:52 -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 0CB8F1B21EC; Tue, 8 Jul 2003 16:14:07 -0500 (CDT)
From: Ted Lemon <mellon@fugue.com>
To: Thamer Al-Harbash <tmh@whitefang.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] "client identifier" in server replies
Date: Tue, 08 Jul 2003 16:18:52 -0500
User-Agent: KMail/1.5
Cc: Bud Millwood <budm@weird-solutions.com>, narasimha.nelakuditi@nokia.com, dhcwg@ietf.org
References: <79A2DB53BC51BD448F0D19A86FB1DB637F1FF7@siebe002.apac.nokia.com> <200307081344.02867.mellon@nominum.com> <Pine.BSF.4.51.0307081519180.92951@helena.whitefang.com>
In-Reply-To: <Pine.BSF.4.51.0307081519180.92951@helena.whitefang.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307081618.52722.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 Tuesday 08 July 2003 14:28, Thamer Al-Harbash wrote:
> We already have the DHCP Hostname option. Clients can be
> configured to pass this option when the admnistrator expects high
> xid collisions.

This isn't a standard use of the DHCP host-name option, and not all DHCP 
clients support it.

>  The DHCP server can also be configured to assign
> leases per the DHCP Hostname option.

A DHCP server that uses the host-name option as an identifier is out of spec 
with the standard.   Furthermore, since host-name option values aren't 
guaranteed to be unique, this is a very risky proposition even with clients 
that _do_ support this non-standard use of the host-name option.

> We just need to promote the
> use of the DHCP Hostname option to be used to counter this
> problem.

This doesn't solve the problem anyway.   The only difference here is that 
we're now using the host-name option as if it were a client-identifier 
option.   So we have the same problem, but with a different option.

> Is this too kludgy?

It's not so much that as that I think it won't work.   :'/


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