draft-ietf-dhc-unused-optioncodes-06.txt | draft-ietf-dhc-unused-optioncodes-07.txt | |||
---|---|---|---|---|
Network Working Group R. Droms | IPv6 Group R. Droms | |||
Internet-Draft Cisco Systems | Internet-Draft Cisco Systems | |||
Expires: February 10, 2004 August 12, 2003 | Expires: April 2, 2004 October 3, 2003 | |||
Unused DHCP Option Codes | Unused DHCP Option Codes | |||
draft-ietf-dhc-unused-optioncodes-06 | draft-ietf-dhc-unused-optioncodes-07 | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
all provisions of Section 10 of RFC2026. | all provisions of Section 10 of RFC2026. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that other | |||
other groups may also distribute working documents as Internet- | groups may also distribute working documents as Internet-Drafts. | |||
Drafts. | ||||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at http:// | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on February 10, 2004. | This Internet-Draft will expire on April 2, 2004. | |||
Copyright Notice | Copyright Notice | |||
Copyright (C) The Internet Society (2003). All Rights Reserved. | Copyright (C) The Internet Society (2003). All Rights Reserved. | |||
Abstract | Abstract | |||
Prior to the publication of RFC2489 (which was updated by RFC2939), | Prior to the publication of RFC2489 (which was updated by RFC2939), | |||
several option codes were assigned to proposed DHCP options that were | several option codes were assigned to proposed DHCP options that were | |||
subsequently never used. This document lists those unused option | subsequently never used. This document lists those unused option | |||
skipping to change at page 3, line 4 | skipping to change at page 2, line 46 | |||
Defined in: Early draft of RFC3046 [2] | Defined in: Early draft of RFC3046 [2] | |||
Contact: (none) | Contact: (none) | |||
Reason to recover: Not defined in RFC3046 as published | Reason to recover: Not defined in RFC3046 as published | |||
2.3 IEEE 1003.1 POSIX Timezone | 2.3 IEEE 1003.1 POSIX Timezone | |||
Code: 88 | Code: 88 | |||
Name: IEEE 1003.1 POSIX Timezone | ||||
Name: IEEE 1003.1 POSIX Timezone | ||||
Defined in: (expired Internet-Draft) | Defined in: (expired Internet-Draft) | |||
Contact: Mike Carney | Contact: Mike Carney | |||
Reason to recover: Never published as standard and not in general use | Reason to recover: Never published as standard and not in general use | |||
2.4 FQDNs in DHCP Options | 2.4 FQDNs in DHCP Options | |||
Code: 89 | Code: 89 | |||
skipping to change at page 4, line 5 | skipping to change at page 4, line 5 | |||
Code: 92 | Code: 92 | |||
Name: Server Selection | Name: Server Selection | |||
Defined in: (none) | Defined in: (none) | |||
Contact: (none) | Contact: (none) | |||
Reason to recover: Never published as Internet-Draft | Reason to recover: Never published as Internet-Draft | |||
2.7 LDAP Servers | 2.7 IPv6 Transition | |||
Code: 95 | ||||
Name: LDAP Servers | ||||
Defined in: (none) | ||||
Contact: (none) | ||||
Reason to recover: Never published as Internet-Draft | ||||
2.8 IPv6 Transition | ||||
Code: 96 | Code: 96 | |||
Name: IPv6 Transition | Name: IPv6 Transition | |||
Defined in: (expired Internet-Draft) | Defined in: (expired Internet-Draft) | |||
Contact: Dan Harrington; agrees that option code should be | Contact: Dan Harrington; agrees that option code should be | |||
reassigned | reassigned | |||
Reason to recover: Never published as standard and not in general use | Reason to recover: Never published as standard and not in general use | |||
2.9 Printer Name | 2.8 Printer Name | |||
Code: 100 | Code: 100 | |||
Name: Printer Name | Name: Printer Name | |||
Defined in: (none) | Defined in: (none) | |||
Contact: (none) | Contact: (none) | |||
Reason to recover: Never published as Internet-Draft | Reason to recover: Never published as Internet-Draft | |||
2.10 Multicast Assignment through DHCP | 2.9 Multicast Assignment through DHCP | |||
Code: 101 | Code: 101 | |||
Name: Multicast Assignment through DHCP | Name: Multicast Assignment through DHCP | |||
Defined in: (expired Internet-Draft) | Defined in: (expired Internet-Draft) | |||
Contact: Baiju Patel, Munil Shah | Contact: Baiju Patel, Munil Shah | |||
Reason to recover: Never published as standard and not in general use | Reason to recover: Never published as standard and not in general use | |||
2.11 Swap Path | 2.10 Swap Path | |||
Code: 108 | Code: 108 | |||
Name: Swap Path | Name: Swap Path | |||
Defined in: (none) | Defined in: (none) | |||
Contact: (none) | Contact: (none) | |||
Reason to recover: Never published as Internet-Draft | Reason to recover: Never published as Internet-Draft | |||
2.12 IPX Compatibility | 2.11 IPX Compatibility | |||
Code: 110 | Code: 110 | |||
Name: IPX Compatibility | Name: IPX Compatibility | |||
Defined in: (none) | Defined in: (none) | |||
Contact: Juan Luciani; agrees that option code should be | Contact: Juan Luciani; agrees that option code should be | |||
reassigned | reassigned | |||
Reason to recover: Never published as Internet-Draft | Reason to recover: Never published as Internet-Draft | |||
2.13 Netinfo Parameters | 2.12 Failover | |||
Codes: 112, 113 | ||||
Name: Netinfo Address, Netinfo Tag | ||||
Defined in: (none) | ||||
Contact: Marc Majka | ||||
Reason to recover: Never published as Internet-Draft | ||||
2.14 URL | ||||
Code: 114 | ||||
Name: URL | ||||
Defined in: (none) | ||||
Contact: Vinod Valloppillil | ||||
Reason to recover: Never published as Internet-Draft | ||||
2.15 Failover | ||||
Code: 115 | Code: 115 | |||
Name: Failover | Name: Failover | |||
Defined in: Early revisions of "DHCP Failover Protocol" [3] | Defined in: Early revisions of "DHCP Failover Protocol" [3] | |||
Contact: Kim Kinnear | Contact: Kim Kinnear | |||
Reason to recover: Current version of "DHCP Failover Protocol" does | Reason to recover: Current version of "DHCP Failover Protocol" does | |||
skipping to change at page 7, line 4 | skipping to change at page 6, line 11 | |||
Environment (PXE) Specification, Version 2.1" [4]. However, although | Environment (PXE) Specification, Version 2.1" [4]. However, although | |||
these options are in widespread use by devices that use PXE, none of | these options are in widespread use by devices that use PXE, none of | |||
these option codes have been described in a published RFC. | these option codes have been described in a published RFC. | |||
The dhc WG will endeavor to have specifications for these options | The dhc WG will endeavor to have specifications for these options | |||
published. | published. | |||
3.1.1 Client System | 3.1.1 Client System | |||
Code: 93 | Code: 93 | |||
Name: Client System | Name: Client System | |||
Defined in: "Preboot Execution Environment (PXE) | Defined in: "Preboot Execution Environment (PXE) | |||
Specification, Version 2.1" [4] | Specification, Version 2.1" [4] | |||
Contact: Michael Johnston (frenchy@quiet-like-a- | Contact: Michael Johnston | |||
panther.org) | (frenchy@quiet-like-a-panther.org) | |||
3.1.2 Client NDI | 3.1.2 Client NDI | |||
Code: 94 | Code: 94 | |||
Name: Client NDI | Name: Client NDI | |||
Defined in: "Preboot Execution Environment (PXE) | Defined in: "Preboot Execution Environment (PXE) | |||
Specification, Version 2.1" [4] | Specification, Version 2.1" [4] | |||
Contact: Michael Johnston (frenchy@quiet-like-a- | Contact: Michael Johnston | |||
panther.org) | (frenchy@quiet-like-a-panther.org) | |||
3.1.3 UUID/GUID Client Identifier | 3.1.3 UUID/GUID Client Identifier | |||
Code: 97 | Code: 97 | |||
Name: UUID/GUID Client Identifier | Name: UUID/GUID Client Identifier | |||
Defined in: "Preboot Execution Environment (PXE) | Defined in: "Preboot Execution Environment (PXE) | |||
Specification, Version 2.1" [4] (and an expired Internet-Draft) | Specification, Version 2.1" [4] (and an expired Internet-Draft) | |||
Contact: Dan Harrington, Michael Johnston (frenchy@quiet- | Contact: Dan Harrington, Michael Johnston | |||
like-a-panther.org) | (frenchy@quiet-like-a-panther.org) | |||
3.2 Option Code Extensions | 3.2 In Use by Apple | |||
The following option codes are used by devices from Apple Computer. | ||||
However, none of these option codes have been described in a | ||||
published RFC. | ||||
The dhc WG will endeavor to have specifications for these options | ||||
published. | ||||
3.2.1 LDAP Servers | ||||
Code: 95 | ||||
Name: LDAP Servers | ||||
Defined in: (none) | ||||
Contact: Dieter Siegmund, dieter@apple.com | ||||
Reason to recover: Never published in an RFC | ||||
3.2.2 Netinfo Parameters | ||||
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 | ||||
3.2.3 URL | ||||
Code: 114 | ||||
Name: URL | ||||
Defined in: (none) | ||||
Contact: Dieter Siegmund, dieter@apple.com | ||||
Reason to recover: Never published in an RFC | ||||
3.3 Option Code Extensions | ||||
Note that these option codes are identified in "Extending DHCP | Note that these option codes are identified in "Extending DHCP | |||
Options Codes" [5] as part of a mechanism for extending the set of | 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 | option codes available to DHCP. If these option codes are not used | |||
for DHCP option code extension, they will be returned to IANA for | for DHCP option code extension, they will be returned to IANA for | |||
reassignment to other DHCP options. | reassignment to other DHCP options. | |||
Codes: 126, 127 | Codes: 126, 127 | |||
Name: Option Code Extensions | Name: Option Code Extensions | |||
skipping to change at page 8, line 21 | skipping to change at page 8, line 29 | |||
5. Security Considerations | 5. Security Considerations | |||
This document has no known security implications, as none of the | This document has no known security implications, as none of the | |||
reclaimed options are known to be in use. | reclaimed options are known to be in use. | |||
6. IANA Considerations | 6. IANA Considerations | |||
IANA has returned the DHCP option codes listed in Section 2 to the | IANA has returned the DHCP option codes listed in Section 2 to the | |||
list of available option codes. These option codes may be reassigned | list of available option codes. These option codes may be reassigned | |||
to new DHCP options, according to the procedures in RFC 2939 [6]. | 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. | ||||
Informative References | Informative References | |||
[1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", | [1] Assigned Numbers Editor, IANA., "BOOTP and DHCP Parameters", | |||
http://www.iana.org/assignments/bootp-dhcp-parameters, | http://www.iana.org/assignments/bootp-dhcp-parameters, | |||
February 2003. | February 2003. | |||
[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, | [2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, | |||
January 2001. | January 2001. | |||
[3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, | [3] Droms, R., Kinnear, K., Stapp, M., Volz, B., Gonczi, S., Rabil, | |||
G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", draft- | G., Dooley, M. and A. Kapur, "DHCP Failover Protocol", | |||
ietf-dhc-failover-12.txt (work in progress), November 2002. | draft-ietf-dhc-failover-12.txt (work in progress), November | |||
2002. | ||||
[4] Intel Corporation, , "Preboot Execution Environment (PXE) | [4] Intel Corporation, "Preboot Execution Environment (PXE) | |||
Specification Version 2.1", | Specification Version 2.1", http://www.pix.net/software/pxeboot/ | |||
http://www.pix.net/software/pxeboot/archive/pxespec.pdf, | archive/pxespec.pdf, September 1999. | |||
September 1999. | ||||
[5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options | [5] Volz, B., Droms, R. and T. Lemon, "Extending DHCP Options | |||
Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in | Codes", draft-volz-dhc-extended-optioncodes-00.txt (work in | |||
progress), February 2003. | progress), February 2003. | |||
[6] Droms, R., "Procedures and IANA Guidelines for Definition of New | [6] Droms, R., "Procedures and IANA Guidelines for Definition of New | |||
DHCP Options and Message Types", BCP 43, RFC 2939, September | DHCP Options and Message Types", BCP 43, RFC 2939, September | |||
2000. | 2000. | |||
Author's Address | Author's Address | |||
Ralph Droms | Ralph Droms | |||
Cisco Systems | Cisco Systems | |||
1414 Massachusetts Avenue | 1414 Massachusetts Avenue | |||
Boxborough, MA 01719 | Boxborough, MA 01719 | |||
USA | USA | |||
Phone: +1 978 936 1674 | Phone: +1 978 936 1674 | |||
EMail: rdroms@cisco.com | EMail: rdroms@cisco.com | |||
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. | ||||
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. | ||||
Full Copyright Statement | Full Copyright Statement | |||
Copyright (C) The Internet Society (2003). All Rights Reserved. | Copyright (C) The Internet Society (2003). All Rights Reserved. | |||
This document and translations of it may be copied and furnished to | This document and translations of it may be copied and furnished to | |||
others, and derivative works that comment on or otherwise explain it | others, and derivative works that comment on or otherwise explain it | |||
or assist in its implementation may be prepared, copied, published | or assist in its implementation may be prepared, copied, published | |||
and distributed, in whole or in part, without restriction of any | and distributed, in whole or in part, without restriction of any | |||
kind, provided that the above copyright notice and this paragraph are | kind, provided that the above copyright notice and this paragraph are | |||
included on all such copies and derivative works. However, this | included on all such copies and derivative works. However, this | |||
document itself may not be modified in any way, such as by removing | document itself may not be modified in any way, such as by removing | |||
the copyright notice or references to the Internet Society or other | the copyright notice or references to the Internet Society or other | |||
Internet organizations, except as needed for the purpose of | Internet organizations, except as needed for the purpose of | |||
developing Internet standards in which case the procedures for | developing Internet standards in which case the procedures for | |||
copyrights defined in the Internet Standards process must be | copyrights defined in the Internet Standards process must be | |||
followed, or as required to translate it into languages other than | followed, or as required to translate it into languages other than | |||
English. | English. | |||
The limited permissions granted above are perpetual and will not be | The limited permissions granted above are perpetual and will not be | |||
revoked by the Internet Society or its successors or assigns. | revoked by the Internet Society or its successors or assignees. | |||
This document and the information contained herein is provided on an | This document and the information contained herein is provided on an | |||
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | |||
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | |||
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | |||
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | |||
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
Acknowledgement | Acknowledgment | |||
Funding for the RFC Editor function is currently provided by the | Funding for the RFC Editor function is currently provided by the | |||
Internet Society. | Internet Society. | |||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |