IETF Logo Mail Archive

Re: [dhcwg] Pre-determining DUID

Ted Lemon <Ted.Lemon@nominum.com> Sat, 10 October 2009 22:46 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6847A3A67F4 for <dhcwg@core3.amsl.com>; Sat, 10 Oct 2009 15:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.373
X-Spam-Level:
X-Spam-Status: No, score=-6.373 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsc23RQfpIGY for <dhcwg@core3.amsl.com>; Sat, 10 Oct 2009 15:46:42 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 63A543A6887 for <dhcwg@ietf.org>; Sat, 10 Oct 2009 15:46:42 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKStEPPZhgjpOgU7ra3+I6OXkA5JPehGUf@postini.com; Sat, 10 Oct 2009 15:48:30 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0E4901B8296; Sat, 10 Oct 2009 15:48:37 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.393.1; Sat, 10 Oct 2009 15:48:27 -0700
MIME-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <fab4e42a0910091810j71fcabd8h12d992be6d28d320@mail.gmail.com>
Date: Sat, 10 Oct 2009 15:48:25 -0700
Content-Transfer-Encoding: 7bit
Message-ID: <FFE5030C-7341-471F-9731-EC069F857A01@nominum.com>
References: <fab4e42a0910091810j71fcabd8h12d992be6d28d320@mail.gmail.com>
To: Jarrod Johnson <jarrod.b.johnson@gmail.com>
X-Mailer: Apple Mail (2.1076)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Pre-determining DUID
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Oct 2009 22:46:43 -0000

It seems that you want to use the client id as a token to identify a  
particular piece of hardware for some purpose, but you haven't said  
what the purpose is.   It also seems that you are (perhaps without  
realizing it) proposing that we break a bunch of protocol  
functionality for everyone in order to solve a problem that is  
specific to your application.

Rather than starting out with the solution, could you please clearly  
state the problem you are trying to solve?

v2.23.0 | Report a Bug | By Email