IETF Logo Mail Archive

Re: [dhcwg] FW: RFC3315 question

Ted Lemon <Ted.Lemon@nominum.com> Sat, 17 February 2007 22:34 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HIY8F-0000KZ-L4; Sat, 17 Feb 2007 17:34:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HIY8F-0000KU-B3 for dhcwg@ietf.org; Sat, 17 Feb 2007 17:34:15 -0500
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HIY8E-0004zU-2Q for dhcwg@ietf.org; Sat, 17 Feb 2007 17:34:15 -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 B2FED5688E; Sat, 17 Feb 2007 14:34:13 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4 tests=AWL: -0.230,BAYES_99: 4.07,CUSTOM_RULE_FROM: ALLOW, TOTAL_SCORE: 3.840
X-Spam-Level:
Received: from [10.10.10.127] ([207.114.177.82]) (authenticated user mellon@nominum.com) by mail.nominum.com (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Sat, 17 Feb 2007 14:34:12 -0800
In-Reply-To: <8E296595B6471A4689555D5D725EBB2103467C84@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2103467C84@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <53EB64D1-7093-4C62-B063-BCF4571874D4@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] FW: RFC3315 question
Date: Sat, 17 Feb 2007 15:34:09 -0700
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Ralph Droms (rdroms)" <rdroms@cisco.com>
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 17, 2007, at 3:25 PM, Bernie Volz ((volz)) wrote:
> Just to get this idea out, how does one go about getting a new
> DUID type defined? In particular, it might be useful to define
> a new DUID type that includes a client's public key such as
> required by RFC3972. The actual format of the DUID type is for
> further study, e.g., in addition to the public key it might be
> desireable to include a link-layer address, a timestamp, etc.

How big is this key going to be?   I don't think a 1k identifier is a  
good idea.



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

v2.23.0 | Report a Bug | By Email