Re: [dhcwg] Assigning DHCPv6 option codes
Vernon Schryver <vjs@calcite.rhyolite.com> Wed, 23 January 2002 15:01 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 KAA11223 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Jan 2002 10:01:18 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA29398 for dhcwg-archive@odin.ietf.org; Wed, 23 Jan 2002 10:01:19 -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 JAA28986; Wed, 23 Jan 2002 09:54:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28969 for <dhcwg@optimus.ietf.org>; Wed, 23 Jan 2002 09:54:34 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [192.188.61.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10945 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 09:54:32 -0500 (EST)
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.2.Beta4/8.12.2.Beta4) id g0NEsXfc004521 for dhcwg@ietf.org env-from <vjs>; Wed, 23 Jan 2002 07:54:33 -0700 (MST)
Date: Wed, 23 Jan 2002 07:54:33 -0700
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200201231454.g0NEsXfc004521@calcite.rhyolite.com>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Assigning DHCPv6 option codes
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
> To: Ralph Droms <rdroms@cisco.com> > I am unaware of a single example where site-specific options have ever been > used. This is why I think it's better not to put language about reserved > portions of the option space in the base draft - I think we need to figure > out what we want to do carefully. Is it really site-specific that we want? > What about vendor-specific? What about user-defined? If you want to > reserve any space in the draft, I would just call the reserved space > "experimental" rather than being specific about who can use it. Reserving > 4096 codes is probably plenty, though, as you say - I don't think we need > 32k. Microsoft is using more than one "site-specific" IPv4 DHCP options. Their web pages talk about 252 and you can see 251 if you snoop on Window ME packets. Which is to support the observation that site-specific options are not used as site specific options. Vernon Schryver vjs@rhyolite.com _______________________________________________ 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