[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dhcwg] Pre-determining DUID



You might want to look at what Cablelabs did with DOCSIS 3.0 ... in
particular the Cablelabs device identifier vendor-specific option. This
works because there is a single mac-address for the CM and the CMTS
(relay) can insert this data in the flow between client and server
(whether client here is CM or CPE).

See
http://www.cablelabs.com/specifications/CL-SP-CANN-DHCP-Reg-I03-090811.p
df, section 5.2.15 Device Identifier Option.

At the time Cablelabs was working on this, we were discussing a "device
identifier" option that would be a standard DHC WG (IETF/IANA) assigned
option to provide a device identifier (most likely a mac-address, but it
was to be defined to support other identifiers) but it wasn't clear how
this would be used and how it would handle situations such as the case
of a device with multiple interfaces and hence multiple device
identifiers. One possibility is that as DHCPv6 requests would occur on
each interface separately, the Client Identifier (DUID) would contain
the same identifier for all requests but this "device identifier" would
specify that interface's mac-address. The DHCPv6 server could then use
the two values in different ways.

- Bernie

-----Original Message-----
From: dhcwg-bounces at ietf.org [mailto:dhcwg-bounces at ietf.org] On Behalf
Of Tim Chown
Sent: Sunday, October 11, 2009 6:17 AM
To: dhcwg at ietf.org
Subject: Re: [dhcwg] Pre-determining DUID

On Sat, Oct 10, 2009 at 08:25:22PM -0400, Chuck Anderson wrote:
> 
> Here are the problems we have that I'm sure many others share:

I would echo these general comments for our site.  It's a very nice
summary of the issues.

It's a notable stumbling block for deploying DHCPv6 for our campus
enterprise.   There's some well-established processes in place for
DHCPv4 which become problematic with the introduction of DUIDs.

I'd certainly encourage Chuck to submit the 'problem statement' as
a draft before the Hiroshima cutoff.

-- 
Tim
_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg