[dhcwg] REMINDER - Notice - DHCPv4 options 128-223 soon to be IANA assignable(RFC 3942)
"Bernie Volz" <volz@cisco.com> Thu, 10 March 2005 03:34 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24847 for <dhcwg-web-archive@ietf.org>; Wed, 9 Mar 2005 22:34:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9EUC-0002eF-0W for dhcwg-web-archive@ietf.org; Wed, 09 Mar 2005 22:37:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9ENY-0001bF-MA; Wed, 09 Mar 2005 22:30:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9ENX-0001b6-Gp for dhcwg@megatron.ietf.org; Wed, 09 Mar 2005 22:30:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24546 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 22:30:25 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9EQG-0002YI-D1 for dhcwg@ietf.org; Wed, 09 Mar 2005 22:33:16 -0500
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 09 Mar 2005 19:29:47 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,152,1107763200"; d="scan'208"; a="166328963:sNHT371775628"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j2A3TfTM020479 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 19:29:42 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-169.cisco.com [10.86.242.169]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APR79895; Wed, 9 Mar 2005 22:29:29 -0500 (EST)
Message-Id: <200503100329.APR79895@flask.cisco.com>
From: Bernie Volz <volz@cisco.com>
To: dhcwg@ietf.org
Date: Wed, 09 Mar 2005 22:29:17 -0500
Organization: Cisco
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcT4+CaxGHELjFIeQ46opJGfKOWRvwsKPx9g
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] REMINDER - Notice - DHCPv4 options 128-223 soon to be IANA assignable(RFC 3942)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Just a friendly reminder ... Hi: A new RFC was recently issued, RFC 3942 (http://www.ietf.org/rfc/rfc3942.txt): "Reclassifying DHCPv4 Options". The document is a product of the IETF DHC WG and expands the range of DHCPv4 option numbers that are in the IETF/IANA assignable range. The expanded public range reduces the site-specific options range that was originally defined in RFC 2132.. Old ranges New ranges IETF/IANA assignable: 1-127 1-223 Site-specific: 128-254 224-254 So, why might you care about this? Many vendors have used "site-specific" options in the range 128-254 for vendor-specific purposes in shipping products. And, now that IANA can assign options numbers in the range 128-223 to future Internet Standard options, we need your assistance to prevent potential conflicts in the use of option codes in the newly expanded range. RFC 3942 has a mechanism whereby IANA will not assign any option codes in the newly expanded range, 128-223, for 6 months (this period will end in May 2005). During this 6 month period, vendors using options in the 128-223 range should come forward to let IANA and the DHC WG know of their use. IANA can be contacted at mailto:iana@iana.org and the IETF DHC WG can be contacted at mailto:dhcwg@ietf.org. The vendor will also need to write an Internet Draft documenting that usage and advance that draft to an RFC. The Internet Draft can either be written by the vendor or by the vendor providing the material for documenting their usage to Bernie Volz (mailto:volz@cisco.com) for inclusion in a general draft documenting several options. Once the Internet Draft has been published, it will be, at the vendor's discretion, published as an Informational RFC or entered into standards track for publication as an Internet Standard RFC. Therefore, please pass this email on as appropriate and contact Bernie Volz for more information. - Bernie Volz _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] REMINDER - Notice - DHCPv4 options 128-22… Bernie Volz
- Re: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Theodore Vojnovich
- RE: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Bernie Volz
- Re: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Timothy Legge
- RE: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Bernie Volz
- RE: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Kostur, Andre
- RE: [dhcwg] REMINDER - Notice - DHCPv4 options 12… Bernie Volz