[dhcwg] Re: dhcpv6-22 DUID/VUID questions/comments

Michael Johnston <frenchy@quiet-like-a-panther.org> Sun, 20 January 2002 02:50 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26232 for <dhcwg-archive@odin.ietf.org>; Sat, 19 Jan 2002 21:50:51 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA24505 for dhcwg-archive@odin.ietf.org; Sat, 19 Jan 2002 21:50:54 -0500 (EST)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24440; Sat, 19 Jan 2002 21:42:52 -0500 (EST)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24420 for <dhcwg@optimus.ietf.org>; Sat, 19 Jan 2002 21:42:51 -0500 (EST)
Received: from quiet-like-a-panther.org (r140-248-dsl.sea.lightrealm.net []) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26056 for <dhcwg@ietf.org>; Sat, 19 Jan 2002 21:42:46 -0500 (EST)
Received: (qmail 5919 invoked by uid 511); 20 Jan 2002 02:42:18 -0000
Message-ID: <20020120024218.5918.qmail@quiet-like-a-panther.org>
References: <66F66129A77AD411B76200508B65AC69B4CDC5@EAMBUNT705>
In-Reply-To: <66F66129A77AD411B76200508B65AC69B4CDC5@EAMBUNT705>
From: Michael Johnston <frenchy@quiet-like-a-panther.org>
To: "Bernie Volz \(EUD\)" <Bernie.Volz@am1.ericsson.se>
Cc: dhcwg <dhcwg@ietf.org>
Date: Sun, 20 Jan 2002 02:42:18 GMT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Re: dhcpv6-22 DUID/VUID questions/comments
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit


Intel-ish systems are what I use the most, so my information is skewed in 
that direction. 

The UUIDs being used today are derived from the algorithm in this document:

Mechanisms for retrieving (and in many cases storing) the platform UUID from 
(to) non-volatile storage are included in (or with) most x86PC compatible 
laptop and desktop systems and all Intel Itanium workstations and servers. 

In order to get Microsoft WHQL or Intel WfM certification all systems with 
network boot support must contain or generate a valid platform UUID. 

EFI (Extensible Firmware Interface) also requires a platform UUID. 


Bernie Volz (EUD) writes: 

> Hi: 
> If there is good evidence that a 128-bit identifier makes much more sense than using the 64-bit identifier currently defined for type 2 (section 11.3), perhaps we should just use the 128-bits (a vendor that only has 64-bit identifier, could simply use 0's in the rest of the bits). 
> Do you or does anyone else have some good information about the what new systems are using for UUIDs? 
> - Bernie Volz 
> -----Original Message-----
> From: Michael Johnston [mailto:frenchy@quiet-like-a-panther.org]
> Sent: Saturday, January 19, 2002 3:00 PM
> To: dhcwg
> Subject: [dhcwg] dhcpv6-22 DUID/VUID questions/comments 
> Gentles, 
> For the DUID contents definition (Section 11):  
> Would you be adverse to expanding the size of the VUID to 128 bits or 
> creating an additional type (4) for a 128 bit UUID?  
> Reasoning:  
> According to the dhcpv6-22 draft, "... the DUID used by a client SHOULD NOT 
> change over time...".  From what I have seen, most new laptops, desktops & 
> workstations (especially those that come with network installed) already 
> contain, or have space reserved for, a 128 bit UUID that is intended to be 
> used to manage/track the system identity.  Why have a vendor or IT assign 
> yet another ID number to the system.  
> Using the link-layer address is also not a unique solution.  Consider the 
> two cases of (1) laptops connecting to docking stations that contain network 
> adapters and (2) replacing defective or upgrading to new network adapters.  
> %%michael  
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

dhcwg mailing list