Re: [dhcwg] Assigning DHCPv6 option codes
Ted Lemon <mellon@nominum.com> Wed, 23 January 2002 18:11 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18960 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Jan 2002 13:11:38 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA09211 for dhcwg-archive@odin.ietf.org; Wed, 23 Jan 2002 13:11:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08433; Wed, 23 Jan 2002 13:00:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08408 for <dhcwg@optimus.ietf.org>; Wed, 23 Jan 2002 13:00:26 -0500 (EST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18643 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 13:00:24 -0500 (EST)
Received: from green.bisbee.fugue.com (dhcp45.summer.secret-wg.org [193.0.5.45]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g0NHvPa24561; Wed, 23 Jan 2002 09:57:25 -0800 (PST)
Received: from dechen (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g0NI0Q001764; Wed, 23 Jan 2002 19:00:26 +0100 (CET)
Date: Wed, 23 Jan 2002 19:00:26 +0100
Subject: Re: [dhcwg] Assigning DHCPv6 option codes
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v480)
Cc: dhcwg@ietf.org
To: Ralph Droms <rdroms@cisco.com>
From: Ted Lemon <mellon@nominum.com>
In-Reply-To: <4.3.2.7.2.20020123123638.03826d80@funnel.cisco.com>
Message-Id: <14409793-102B-11D6-AF3C-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.480)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit
> There's a little more to it than just the scarcity of option codes in > DHCPv4. Just before we instituted the new policy of assigning an option > code after acceptance to PS, there were several (10-15 or so) that were > proposed, had option codes assigned, and then were never followed up on. > Those option codes are now in limbo. > > Even though we have plenty of options code in DHCPv6, I don't think it's > a good idea to have option codes in an uncertain state - assigned to > options that never went to PS. Perhaps we need some sort of sunsetting to > establish a process for marking option codes as "unused - do not reassign" > ... Sounds fine. However, I don't think it's a particularly serious problem. Perhaps we should issue leases on options - if you don't have a current draft or RFC, your option code gets reclaimed. I'd say that the draft should have wg sponsorship before a code gets issued, but OTOH it might be nice if, someday, the DHCwg were obsolete... :') _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Assigning DHCPv6 option codes Ralph Droms
- RE: [dhcwg] Assigning DHCPv6 option codes Bernie Volz (EUD)
- RE: [dhcwg] Assigning DHCPv6 option codes Bernie Volz (EUD)
- Re: [dhcwg] Assigning DHCPv6 option codes Ted Lemon
- RE: [dhcwg] Assigning DHCPv6 option codes Ralph Droms
- Re: [dhcwg] Assigning DHCPv6 option codes Ted Lemon
- Re: [dhcwg] Assigning DHCPv6 option codes Vernon Schryver
- RE: [dhcwg] Assigning DHCPv6 option codes Bernie Volz (EUD)
- Re: [dhcwg] Assigning DHCPv6 option codes Ted Lemon
- Re: [dhcwg] Assigning DHCPv6 option codes Ted Lemon
- RE: [dhcwg] Assigning DHCPv6 option codes Richard Barr Hibbs
- RE: [dhcwg] Assigning DHCPv6 option codes Richard Barr Hibbs
- RE: [dhcwg] Assigning DHCPv6 option codes Vernon Schryver
- RE: [dhcwg] Assigning DHCPv6 option codes Richard Barr Hibbs
- RE: [dhcwg] Assigning DHCPv6 option codes Vernon Schryver
- RE: [dhcwg] Assigning DHCPv6 option codes Ralph Droms