Re: [dhcwg] REMINDER - Notice - DHCPv4 options 128-223 soon to be IANA assignable(RFC 3942)
Theodore Vojnovich <tbvojnov@us.ibm.com> Thu, 10 March 2005 21:37 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 QAA09664 for <dhcwg-web-archive@ietf.org>; Thu, 10 Mar 2005 16:37:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9VOM-0000oY-TQ for dhcwg-web-archive@ietf.org; Thu, 10 Mar 2005 16:40:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9VIS-0000Ay-Qv; Thu, 10 Mar 2005 16:34:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9VIR-0000Am-HE; Thu, 10 Mar 2005 16:34:19 -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 QAA09260; Thu, 10 Mar 2005 16:34:16 -0500 (EST)
Received: from e34.co.us.ibm.com ([32.97.110.132]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9VLH-0000ec-VC; Thu, 10 Mar 2005 16:37:18 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j2ALY6KN259918; Thu, 10 Mar 2005 16:34:06 -0500
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j2ALY3K7130054; Thu, 10 Mar 2005 14:34:04 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j2ALY3O6010552; Thu, 10 Mar 2005 14:34:03 -0700
Received: from d03nm690.boulder.ibm.com (d03nm690.boulder.ibm.com [9.17.195.59]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j2ALY3Yv010527; Thu, 10 Mar 2005 14:34:03 -0700
In-Reply-To: <200503100329.APR79895@flask.cisco.com>
To: Bernie Volz <volz@cisco.com>
MIME-Version: 1.0
Subject: Re: [dhcwg] REMINDER - Notice - DHCPv4 options 128-223 soon to be IANA assignable(RFC 3942)
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
From: Theodore Vojnovich <tbvojnov@us.ibm.com>
Message-ID: <OFDAD7F53E.2B7461CB-ON85256FC0.006D8D2D-85256FC0.007678C4@us.ibm.com>
Date: Thu, 10 Mar 2005 14:35:28 -0700
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 6.53HF294 | January 28, 2005) at 03/10/2005 14:35:29, Serialize complete at 03/10/2005 14:35:29
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Cc: dhcwg@ietf.org, dhcwg-bounces@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============0088985772=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
We are using 201 thru 205 as vendor options in an upcoming product set/solution. Can I get clarifcation on the site vs vendor. Specifically, we are using option 60 to identify the client as a client that works in our solution. Server response 43 would have the 201-205 stuff. Does this fall into "having to move or go to iana" or is this an except to the usage...not clear to me Thanks Ted Vojnovich Blade Center Storage Solutions L205 / B205 3039 Cornwallis Dr RTP NC, 27709 Voice: 919-254-0730 (T/L 444-0730) Fax: 919-543-2820 Cell Phone: 919-656-5061 Email: tbvojnov@us.ibm.com "Bernie Volz" <volz@cisco.com> Sent by: dhcwg-bounces@ietf.org 03/09/2005 10:29 PM To <dhcwg@ietf.org> cc Subject [dhcwg] REMINDER - Notice - DHCPv4 options 128-223 soon to be IANA assignable(RFC 3942) 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 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