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

Michael Johnston <frenchy@quiet-like-a-panther.org> Sat, 19 January 2002 20:07 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 PAA22487 for <dhcwg-archive@odin.ietf.org>; Sat, 19 Jan 2002 15:07:34 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id PAA16384 for dhcwg-archive@odin.ietf.org; Sat, 19 Jan 2002 15:07:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA16051; Sat, 19 Jan 2002 15:00:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA16012 for <dhcwg@optimus.ietf.org>; Sat, 19 Jan 2002 15:00:11 -0500 (EST)
Received: from quiet-like-a-panther.org (r140-248-dsl.sea.lightrealm.net [209.203.248.140]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22378 for <dhcwg@ietf.org>; Sat, 19 Jan 2002 15:00:07 -0500 (EST)
Received: (qmail 4561 invoked by uid 511); 19 Jan 2002 19:59:38 -0000
Message-ID: <20020119195938.4560.qmail@quiet-like-a-panther.org>
From: Michael Johnston <frenchy@quiet-like-a-panther.org>
To: "dhcwg" <dhcwg@ietf.org>
Date: Sat, 19 Jan 2002 19:59:38 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] 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

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