Network Working Group R. Droms
Request for Comments: 3679 Cisco Systems
Category: Informational January 2004
Network Working Group R. Droms
Request for Comments: 3679 Cisco Systems
Category: Informational January 2004
Unused Dynamic Host Configuration Protocol (DHCP) Option Codes
未使用的动态主机配置协议（DHCP）选项代码
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
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.
在发布RFC 2489（由RFC 2939更新）之前，为提议的动态主机配置协议（DHCP）选项分配了几个选项代码，这些选项后来从未使用过。本文档列出了这些未使用的选项代码，并指示IANA使这些选项代码可用于将来分配给其他DHCP选项。
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.
本文件还列出了几个选项代码，这些代码目前未记录在RFC中，但不应提供给将来的DHCP选项重新分配。
Section 2 of this document lists the unused DHCP option codes from the IANA list of BOOTP and DHCP option codes [1]. Each option code includes any known documentation and contact information from the IANA list. IANA will make these option codes available for assignment to other DHCP options in the future.
本文件第2节列出了IANA BOOTP和DHCP选项代码列表中未使用的DHCP选项代码[1]。每个选项代码包括IANA列表中的任何已知文档和联系信息。IANA将在将来将这些选项代码分配给其他DHCP选项。
Section 3 lists several DHCP option codes that are not currently documented in an RFC but should not be made available for reassignment to future DHCP options.
第3节列出了几个DHCP选项代码，这些代码目前未记录在RFC中，但不应提供给将来的DHCP选项重新分配。
The option codes listed in this section are to be returned to IANA for reassignment to new options. Responses from associated contact persons are noted where they have been received.
本节中列出的选项代码将返回给IANA，以便重新分配给新选项。相关联系人的回复记录在收到的地方。
Code: 80 Name: Service Location Protocol Naming Authority Defined in: (expired Internet-Draft) Contact: Charlie Perkins Reason to recover: Never published as standard and not in general use
代码：80名称：服务位置协议命名机构定义于：（过期的Internet草稿）联系人：Charlie Perkins恢复原因：从未作为标准发布，也未在一般使用中
Codes: 83, 84 Name: Relay Agent Options Defined in: Early draft of RFC 3046 [2] Contact: (none) Reason to recover: Not defined in RFC 3046 as published
代码：83，84名称：中定义的中继代理选项：RFC 3046早期草案[2]联系人：（无）恢复原因：未在发布的RFC 3046中定义
Code: 88 Name: IEEE 1003.1 POSIX Timezone Defined in: (expired Internet-Draft) Contact: Mike Carney Reason to recover: Never published as standard and not in general use
代码：88名称：IEEE 1003.1 POSIX时区定义于：（过期的互联网草案）联系人：Mike Carney恢复原因：从未作为标准发布，也未普遍使用
Code: 89 Name: FQDNs in DHCP Options Defined in: (expired Internet-Draft) Contact: Ralph Droms; agrees that option code should be reassigned Reason to recover: Never published as standard and not in general use
代码：89名称：DHCP选项中的FQDNs定义于：（过期的Internet草稿）联系人：Ralph Droms；同意应重新分配选项代码恢复的原因：从未作为标准发布，也未在通用中发布
Code: 91 Name: VINES TCP/IP Server Defined in: (none) Contact: (none) Reason to recover: Never published as Internet-Draft
代码：91名称：VINES TCP/IP服务器在中定义：（无）联系人：（无）恢复原因：从未作为Internet草稿发布
Code: 92 Name: Server Selection Defined in: (none) Contact: (none) Reason to recover: Never published as Internet-Draft
代码：92名称：在中定义的服务器选择：（无）联系人：（无）恢复原因：从未作为Internet草稿发布
Code: 96 Name: IPv6 Transition Defined in: (expired Internet-Draft) Contact: Dan Harrington; agrees that option code should be reassigned Reason to recover: Never published as standard and not in general use
代码：96名称：IPv6过渡定义于：（过期的互联网草案）联系人：Dan Harrington；同意应重新分配选项代码恢复的原因：从未作为标准发布，也未在通用中发布
Code: 100 Name: Printer Name Defined in: (none) Contact: (none) Reason to recover: Never published as Internet-Draft
代码：100名称：在中定义的打印机名称：（无）联系人：（无）恢复原因：从未作为Internet草稿发布
Code: 101 Name: Multicast Assignment through DHCP Defined in: (expired Internet-Draft) Contact: Baiju Patel, Munil Shah Reason to recover: Never published as standard and not in general use
代码：101名称：通过DHCP的多播分配定义于：（过期的互联网草案）联系人：Baiju Patel，Munil Shah恢复原因：从未作为标准发布，也未在一般使用中
Code: 108 Name: Swap Path Defined in: (none) Contact: (none) Reason to recover: Never published as Internet-Draft
代码：108名称：在中定义的交换路径：（无）联系人：（无）恢复原因：从未作为Internet草稿发布
Code: 110 Name: IPX Compatibility Defined in: (none) Contact: Juan Luciani; agrees that option code should be reassigned Reason to recover: Never published as Internet-Draft
代码：110名称：IPX兼容性定义于：（无）联系人：Juan Luciani；同意应重新分配选项代码恢复原因：从未作为互联网草稿发布
Code: 115 Name: Failover Defined in: Early revisions of "DHCP Failover Protocol" [3] Contact: Kim Kinnear Reason to recover: Current version of "DHCP Failover Protocol" does not use a DHCP option
代码：115名称：中定义的故障转移：早期版本的“DHCP故障转移协议”[3]联系人：Kim Kinnear恢复原因：当前版本的“DHCP故障转移协议”未使用DHCP选项
The option codes listed in this section are the subject of ongoing work in the DHC Working Group (WG). These option codes should remain on the IANA list of assigned option codes [1] until the DHC WG has made a final decision about their disposition.
本节中列出的选项代码是DHC工作组（WG）正在进行的工作的主题。这些选项代码应保留在IANA指定选项代码列表[1]中，直到DHC工作组就其处置做出最终决定。
The following option codes are used in the "Preboot Execution Environment (PXE) Specification, Version 2.1" [4]. However, although these options are in widespread use by devices that use PXE, none of these option codes have been described in a published RFC.
以下选项代码用于“预引导执行环境（PXE）规范，版本2.1”[4]。然而，尽管这些选项被使用PXE的设备广泛使用，但这些选项代码都没有在已发布的RFC中描述。
The DHC WG will endeavor to have specifications for these options published.
DHC工作组将努力发布这些选项的规范。
Code: 93 Name: Client System Defined in: "Preboot Execution Environment (PXE) Specification, Version 2.1" [4] Contact: Michael Johnston (frenchy@quiet-like-a-panther.org)
代码：93名称：在“预引导执行环境（PXE）规范，版本2.1”中定义的客户端系统[4]联系人：Michael Johnston(frenchy@quiet-like-a-panther.org）
Code: 94 Name: Client NDI Defined in: "Preboot Execution Environment (PXE) Specification, Version 2.1" [4] Contact: Michael Johnston (frenchy@quiet-like-a-panther.org)
代码：94名称：在“预引导执行环境（PXE）规范，版本2.1”中定义的客户端NDI[4]联系人：Michael Johnston(frenchy@quiet-like-a-panther.org）
Code: 97 Name: UUID/GUID Client Identifier Defined in: "Preboot Execution Environment (PXE) Specification, Version 2.1" [4] (and an expired Internet-Draft) Contact: Dan Harrington, Michael Johnston (frenchy@quiet-like-a-panther.org)
代码：97名称：UUID/GUID客户端标识符定义于：“预引导执行环境（PXE）规范，版本2.1”[4]（和过期的Internet草稿）联系人：Dan Harrington，Michael Johnston(frenchy@quiet-like-a-panther.org）
The following option codes are used by devices from Apple Computer. However, none of these option codes have been described in a published RFC.
以下选项代码由Apple Computer的设备使用。但是，这些选项代码均未在已发布的RFC中描述。
The DHC WG will endeavor to have specifications for these options published.
DHC工作组将努力发布这些选项的规范。
Code: 95 Name: LDAP Servers Defined in: (none) Contact: Dieter Siegmund, dieter@apple.com Reason to recover: Never published in an RFC
代码：95名称：中定义的LDAP服务器：（无）联系人：Dieter Siegmund，dieter@apple.com恢复原因：从未在RFC中发布
Codes: 112, 113 Name: Netinfo Address, Netinfo Tag Defined in: (none) Contact: Dieter Siegmund, dieter@apple.com Reason to recover: Never published in an RFC
代码：112113姓名：Netinfo地址，Netinfo标记定义于：（无）联系人：Dieter Siegmund，dieter@apple.com恢复原因：从未在RFC中发布
Code: 114 Name: URL Defined in: (none) Contact: Dieter Siegmund, dieter@apple.com Reason to recover: Never published in an RFC
代码：114姓名：URL在中定义：（无）联系人：Dieter Siegmund，dieter@apple.com恢复原因：从未在RFC中发布
Note that these option codes are identified in "Extending DHCP Options Codes" [5] as part of a mechanism for extending the set of option codes available to DHCP. If these option codes are not used for DHCP option code extension, they will be returned to IANA for reassignment to other DHCP options.
请注意，这些选项代码在“扩展DHCP选项代码”[5]中标识，作为扩展DHCP可用选项代码集机制的一部分。如果这些选项代码未用于DHCP选项代码扩展，它们将返回给IANA，以便重新分配给其他DHCP选项。
Codes: 126, 127 Name: Option Code Extensions Defined in: (expired Internet-Draft) Contact: Ralph Droms
代码：126127名称：选项代码扩展定义于：（过期的互联网草稿）联系人：Ralph Droms
The option codes 99, 102-107, 109 and 111 have already been returned for reassignment to future DHCP options.
选项代码99、102-107、109和111已返回，以便重新分配给未来的DHCP选项。
This document has no known security implications, as none of the reclaimed options are known to be in use.
本文档没有已知的安全含义，因为已知回收的选项中没有一个正在使用。
IANA has returned the DHCP option codes listed in Section 2 to the list of available option codes. These option codes may be reassigned to new DHCP options, according to the procedures in RFC 2939 [6]. IANA is requested to reassign these option codes after the list of option codes that have never been assigned or have previously been returned has been exhausted.
IANA已将第2节中列出的DHCP选项代码返回到可用选项代码列表中。根据RFC 2939[6]中的程序，这些选项代码可以重新分配给新的DHCP选项。在从未分配或之前已返回的选项代码列表用尽后，IANA被要求重新分配这些选项代码。
Informative References
资料性引用
[1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", http://www.iana.org/assignments/bootp-dhcp-parameters, February 2003.
[1] 分配号码编辑器，IANA.，“BOOTP和DHCP参数”，http://www.iana.org/assignments/bootp-dhcp-parameters，2003年2月。
[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, January 2001.
[2] Patrick，M.，“DHCP中继代理信息选项”，RFC 3046，2001年1月。
[3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", Work in Progress.
[3] Droms，R.，Kinnear，K.，Stapp，M.，Volz，B.，Gonczi，S.，Rabil，G.，Dooley，M.和A.Kapur，“DHCP故障切换协议”，工作正在进行中。
[4] Intel Corporation, "Preboot Execution Environment (PXE) Specification Version 2.1", http://www.pix.net/software/pxeboot/ archive/pxespec.pdf, September 1999.
[4] 英特尔公司，“预引导执行环境（PXE）规范版本2.1”，http://www.pix.net/software/pxeboot/ 存档/pxepc.pdf，1999年9月。
[5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options Codes", Work in Progress.
[5] Volz，B.，Droms，R.和T.Lemon，“扩展DHCP选项代码”，工作正在进行中。
[6] Droms, R., "Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types", BCP 43, RFC 2939, September 2000.
[6] Droms，R.，“新DHCP选项和消息类型定义的程序和IANA指南”，BCP 43，RFC 2939，2000年9月。
Intellectual Property Statement
知识产权声明
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Author's Address
作者地址
Ralph Droms Cisco Systems 1414 Massachusetts Avenue Boxborough, MA 01719 USA
Ralph Droms Cisco Systems美国马萨诸塞州Boxborough马萨诸塞大道1414号，邮编01719
Phone: +1 978 936 1674
EMail: rdroms@cisco.com
Phone: +1 978 936 1674
EMail: rdroms@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。