RFC 3679 on Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
rfc-editor@rfc-editor.org Sat, 24 January 2004 00:37 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04914 for <ietf-announce-web-archive@odin.ietf.org>; Fri, 23 Jan 2004 19:37:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AkBTA-0004C3-Gj for ietf-announce-list@asgard.ietf.org; Fri, 23 Jan 2004 19:16:12 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AkBSx-0004Aa-Vi for all-ietf@asgard.ietf.org; Fri, 23 Jan 2004 19:16:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04441 for <all-ietf@ietf.org>; Fri, 23 Jan 2004 19:15:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AkBSw-00077E-00 for all-ietf@ietf.org; Fri, 23 Jan 2004 19:15:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AkBS4-00076G-00 for all-ietf@ietf.org; Fri, 23 Jan 2004 19:15:05 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AkBRi-00074d-00; Fri, 23 Jan 2004 19:14:42 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i0O0Egk13988; Fri, 23 Jan 2004 16:14:42 -0800 (PST)
Message-Id: <200401240014.i0O0Egk13988@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3679 on Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
Cc: rfc-editor@rfc-editor.org, dhcwg@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 23 Jan 2004 16:14:42 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3679 Title: Unused Dynamic Host Configuration Protocol (DHCP) Option Codes Author(s): R. Droms Status: Informational Date: January 2004 Mailbox: rdroms@cisco.com Pages: 8 Characters: 13804 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-unused-optioncodes-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3679.txt Prior to the publication of RFC 2489 (which was updated by RFC 2939), several option codes were assigned to proposed Dynamic Host Configuration Protocol (DHCP) options that were subsequently never used. This document lists those unused option codes and directs IANA to make these option codes available for assignment to other DHCP options in the future. The document also lists several option codes that are not currently documented in an RFC but should not be made available for reassignment to future DHCP options. This document is a product of the Dynamic Host Configuration Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.