RE: [dhcwg] DUID on a Virtual Host

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 02 March 2007 15:36 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HN9oI-00085t-Lv; Fri, 02 Mar 2007 10:36:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HN9oH-000855-Qg for dhcwg@ietf.org; Fri, 02 Mar 2007 10:36:41 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48] helo=slb-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HN9oC-0005QQ-FK for dhcwg@ietf.org; Fri, 02 Mar 2007 10:36:41 -0500
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id l22FaVkT009370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 2 Mar 2007 07:36:32 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id l22FaVVf015825; Fri, 2 Mar 2007 07:36:31 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id l22FaUTk015800; Fri, 2 Mar 2007 07:36:31 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 07:36:27 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] DUID on a Virtual Host
Date: Fri, 02 Mar 2007 07:36:26 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A101774784@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <37AA4D8B-BA12-434A-83D0-FBFE4C709C07@nominum.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] DUID on a Virtual Host
Thread-Index: AcdcZilHTrUg00opRNCkAJwGsDRe0gAeEyIA
References: <8E296595B6471A4689555D5D725EBB21035095C8@xmb-rtp-20a.amer.cisco.com><200702201524.l1KFOQO4026527@cichlid.raleigh.ibm.com><39C363776A4E8C4A94691D2BD9D1C9A101774702@XCH-NW-7V2.nw.nos.boeing.com><45DB65B8.7080107@us.ibm.com><E8F789A0-772A-4B56-9AFF-D0925A0FF5EC@nominum.com><20070301234628.GD20815@isc.org><986E53D9-2A76-480E-8098-8F7466378E87@nominum.com><20070302004546.GF20815@isc.org> <37AA4D8B-BA12-434A-83D0-FBFE4C709C07@nominum.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, "David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 02 Mar 2007 15:36:27.0588 (UTC) FILETIME=[8AE28840:01C75CE0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: DHC WG <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

> On Mar 1, 2007, at 5:45 PM, David W. Hankins wrote:
> > It would be perfectly acceptable to use a derivative of a key as a
> > DUID.  If you actually wanted to make use of the key of course,
> > in authentication or encryption or what have you, there would need
> > to be some additional mechanism to transfer its content.
> 
> No, we didn't agree on that.   You assert that the key is 
> unique, and  
> that therefore the fingerprint (derivative) is unique, but in fact  
> nothing of the sort is true - the only reason the fingerprint works  
> as an identifier is that there are additional disambiguation  
> mechanisms that (a) make the likelihood of an undetected collision  
> acceptably small and (b) provide a path for both detecting and  
> dealing with a collision.   Unfortunately, these mechanisms require  
> the intervention of an intelligent agent (a person) and can't really  
> be automated in the way you're suggesting.

Forgive me if I am missing the point completely, but is't
handing out unique pieces of information to clients exactly
the reason why we have DHCP servers in the first place? For
example, why can't it be such that a client could walk up
to the server and say:

 "My name is James Horatio Blankenship Esquire the Third."

and the server replies:

 "That's great; we'll just call you "Jim" from now on."

So, as long as the server accepts the client's (long) public
key as an identifier and gives it back a (short) nickname to
be used in subsequent transactions it should be OK - right?

Fred
fred.l.templin@boeing.com 

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