Re: [dhcwg] DUID on a Virtual Host

Ted Lemon <Ted.Lemon@nominum.com> Tue, 20 February 2007 21:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJcxr-0004ST-2B; Tue, 20 Feb 2007 16:55:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJcxp-0004RO-Ae for dhcwg@ietf.org; Tue, 20 Feb 2007 16:55:57 -0500
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJcxo-0001Fv-0p for dhcwg@ietf.org; Tue, 20 Feb 2007 16:55:57 -0500
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id A149156821; Tue, 20 Feb 2007 13:55:55 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4 tests=AWL: -0.728,BAYES_99: 4.07,CUSTOM_RULE_FROM: ALLOW, TOTAL_SCORE: 3.342
X-Spam-Level:
Received: from [10.0.0.190] ([66.93.162.128]) (authenticated user mellon@nominum.com) by mail.nominum.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 20 Feb 2007 13:55:53 -0800
In-Reply-To: <200702201347.l1KDlMPX002189@cichlid.raleigh.ibm.com>
References: <45D61560.4080103@us.ibm.com> <F609A924-B391-4135-92F3-F6E527549C09@nominum.com> <200702201347.l1KDlMPX002189@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <3F152A18-E9BE-4B39-9777-57F16089C924@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DUID on a Virtual Host
Date: Tue, 20 Feb 2007 14:55:49 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 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 Feb 20, 2007, at 6:47 AM, Thomas Narten wrote:
>> This could be a one-time ID, and you could form a DUID-LLT-like
>> identifier from it, except that instead of being (link-layer, time)
>> it would be (link-layer, time, uid).
>
> To be clear, Do you think you can reuse the existing DUID-LLT type, or
> do you think you need to define a new one?

We would have to define a new one.   I don't think it makes sense to  
use the same format, because the documentation doesn't really match  
the proposed new use, and I would expect that to lead to needless  
confusion.

> In looking at the IANA considerations for DUIDs (see RFC3315), it says
> new DUIDS are created (only) through Standards Action. I wonder if
> that bar is too high. I'd think it would be sufficient to grant them
> under other types of RFCs. I.e., is it appropriate/necessary to
> _standardize_ all DUID types? I would imagine there will be special
> cases that fairly unique to specific scenarios which don't justify
> standardization.

I think relaxing it to "documented in an RFC" might be okay - someone  
might define a private use and publish an informational RFC.   I'm  
not sure how important this is, though - it seems like a fairly  
unlikely scenario.

> That said, in this case (virtualized hosts), I suspect there is
> utility/value in having a standardized approach, as it seems the
> scenario is somewhat general.

Agreed.




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