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

Re: [dhcwg] Pre-determining DUID

To: Jarrod Johnson <jarrod.b.johnson at gmail.com>
Subject: Re: [dhcwg] Pre-determining DUID
From: Ted Lemon <Ted.Lemon at nominum.com>
Date: Sat, 10 Oct 2009 15:48:25 -0700
Cc: "dhcwg at ietf.org" <dhcwg at ietf.org>
Delivered-to: dhcwg at core3.amsl.com
In-reply-to: <fab4e42a0910091810j71fcabd8h12d992be6d28d320 at mail.gmail.com>
List-archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-help: <mailto:dhcwg-request@ietf.org?subject=help>
List-id: <dhcwg.ietf.org>
List-post: <mailto:dhcwg@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
References: <fab4e42a0910091810j71fcabd8h12d992be6d28d320 at mail.gmail.com>

It seems that you want to use the client id as a token to identify aparticular piece of hardware for some purpose, but you haven't saidwhat the purpose is. It also seems that you are (perhaps withoutrealizing it) proposing that we break a bunch of protocolfunctionality for everyone in order to solve a problem that isspecific to your application.

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

Follow-Ups:
- Re: [dhcwg] Pre-determining DUID
  - From: Chuck Anderson

References:
- [dhcwg] Pre-determining DUID
  - From: Jarrod Johnson

Prev by Date: Re: [dhcwg] Pre-determining DUID
Next by Date: Re: [dhcwg] Pre-determining DUID
Previous by thread: Re: [dhcwg] Pre-determining DUID
Next by thread: Re: [dhcwg] Pre-determining DUID
Index(es):
- Date
- Thread