Re: [dhcwg] dhc WG last callon draft-ietf-dhc-relay-id-suboption-00.txt
"David W. Hankins" <David_Hankins@isc.org> Wed, 10 September 2008 15:25 UTC
Return-Path: <dhcwg-bounces@ietf.org>
X-Original-To: dhcwg-archive@megatron.ietf.org
Delivered-To: ietfarch-dhcwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E33843A6A47; Wed, 10 Sep 2008 08:25:30 -0700 (PDT)
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 D7E283A67D8 for <dhcwg@core3.amsl.com>; Wed, 10 Sep 2008 08:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level:
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, 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 oJOixV5VgGZR for <dhcwg@core3.amsl.com>; Wed, 10 Sep 2008 08:25:28 -0700 (PDT)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 7E37A28C0EF for <dhcwg@ietf.org>; Wed, 10 Sep 2008 08:25:28 -0700 (PDT)
Received: from dhcp-144.sql1.isc.org (c-24-6-53-214.hsd1.ca.comcast.net [24.6.53.214]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id m8AFPXZN001285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dhcwg@ietf.org>; Wed, 10 Sep 2008 08:25:34 -0700
Received: by dhcp-144.sql1.isc.org (Postfix, from userid 10200) id 4B6CD16E1B3; Wed, 10 Sep 2008 08:25:33 -0700 (PDT)
Date: Wed, 10 Sep 2008 08:25:32 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20080910152531.GA5360@isc.org>
References: <2CB8863C-65FA-4C7E-A764-82C951AF8137@cisco.com> <8E296595B6471A4689555D5D725EBB2108B1CEB4@xmb-rtp-20a.amer.cisco.com> <31D55C4D55BEED48A4459EB64567589A0C8852BBB5@BLRKECMBX02.ad.infosys.com> <48C7CE51.9070708@cisco.com>
MIME-Version: 1.0
In-Reply-To: <48C7CE51.9070708@cisco.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: Re: [dhcwg] dhc WG last callon draft-ietf-dhc-relay-id-suboption-00.txt
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: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============1719231759=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
On Wed, Sep 10, 2008 at 09:40:33AM -0400, Mark Stapp wrote: > David: this isn't about cons'ing up new ids for clients. don't let an > example from the text mislead you about what the data in the suboption is: > it's just another relay suboption. I'll reorganize the examples to try to > make the distinction between what the info is and how it might be used > clerrer. OK, that makes more sense. My concern there right now is that the draft only says a relay agent might format this new option as equal to a DUID, but gives no directions for stable storage of that DUID or what context should be driven to manufacture it (from packet contents or from the relay's internal context such as its own interface addresses). We've had problems with clients manufacturing a new DUID-LLT every time they restart, and 3315 was pretty clear on this issue I thought. I'm fairly concerned what we'll see if we're not clear. :) It might make some sense, from Bernie's comments, to stick to DUID types entirely and make "vendor or administratively supplied" id's live under the vendor-identified DUID type, explicitly describing the field contents as being the relay's DUID and subject to the same rules that clients and servers use to generate their own. If we need a "manually configured NVT-ASCII string" DUID type, we could assign one I think. I got the idea somehow from the introduction and the later sections that an admin might expect to see "sw5.etc:5/19" as the field contents, being a switch identity concatenated with a port number, and using that to form an identity with a lease. I gather I'm mistaken, and concat(relay-DUID, relay-interface-id) seems much more reliable and extensible. But this is a commonly requested and very useful feature, so if this field is intended to be used in concert with other fields (relay agent interface-id) to form an identity relationsihp with a lease, I think we still have a RENEWING problem (maybe solved by referring to RFC5107)? -- Ash bugud-gul durbatuluk agh burzum-ishi krimpatul. Why settle for the lesser evil? https://secure.isc.org/store/t-shirt/ -- David W. Hankins "If you don't do it right the first time, Software Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins
_______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhc WG last call on draft-ietf-dhc-relay-… Ralph Droms
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-re… David W. Hankins
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-re… David W. Hankins
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-re… Bernie Volz (volz)
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… Bernie Volz (volz)
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… Bharat Joshi
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… Mark Stapp
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… Bharat Joshi
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… David W. Hankins
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-re… Mark Stapp
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… Mark Stapp
- Re: [dhcwg] dhc WG last call on draft-ietf-dhc-re… Bernie Volz (volz)
- Re: [dhcwg] dhc WG last callon draft-ietf-dhc-rel… David W. Hankins