draft-ietf-dhc-vendor-00.txt   draft-ietf-dhc-vendor-01.txt 
DHC Working Group Josh Littlefield DHC Working Group J. Littlefield
INTERNET-DRAFT Cisco Systems Internet-Draft Cisco Systems, Inc.
Expires: March 2004 September 2003 Expires: August 5, 2004 February 5, 2004
Vendor-Identifying Vendor Options for DHCPv4 Vendor-Identifying Vendor Options for DHCPv4
draft-ietf-dhc-vendor-00.txt draft-ietf-dhc-vendor-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is in full conformance with
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/1id-abstracts.html 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 August 5, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
The DHCP options for Vendor Class and Vendor-Specific Information can The DHCP options for Vendor Class and Vendor-Specific Information can
be ambiguous when a DHCP client represents multiple vendors. This be ambiguous when a DHCP client represents multiple vendors. This
document defines two new options, modeled on the IPv6 options for document defines two new options, modeled on the IPv6 options for
vendor class and vendor-specific information, which contain vendor class and vendor-specific information, which contain
Enterprise Numbers to remove ambiguity. Enterprise Numbers to remove ambiguity.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1]. document are to be interpreted as described in RFC 2119 [1].
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Vendor-Identifying Vendor Class Option.........................2 2. Multiple Instances of Options . . . . . . . . . . . . . . . . . 3
3. Vendor-Identifying Vendor-Specific Information Option..........3 3. Vendor-Identifying Vendor Class Option . . . . . . . . . . . . . 3
4. IANA Considerations............................................5 4. Vendor-Identifying Vendor-Specific Information Option . . . . . 5
5. Security Considerations........................................5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
References........................................................5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
Author's Address..................................................6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Acknowledgement...................................................7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . 8
1. Introduction 1. Introduction
The DHCP protocol for IPv4 defines options to allow a client to The DHCP protocol for IPv4 defines options to allow a client to
indicate its vendor type (option 60), and to allow the DHCP client indicate its vendor type (option 60), and to allow the DHCP client
and server to exchange vendor-specific information (option 43) [2]. and server to exchange vendor-specific information (option 43) [3].
While there is no prohibition against passing multiple copies of While there is no prohibition against passing multiple copies of
these options in a single packet, doing so would introduce ambiguity these options in a single packet, doing so would introduce ambiguity
of interpretation, particularly if conveying vendor-specific of interpretation, particularly if conveying vendor-specific
information for multiple vendors. The vendor identified by option 60 information for multiple vendors. The vendor identified by option 60
defines the interpretation of option 43, which itself carries no defines the interpretation of option 43, which itself carries no
vendor identifier. vendor identifier.
There are circumstances where an implementation may need to support There are circumstances where an implementation may need to support
multiple, independently defined forms of vendor-specific information. multiple, independently defined forms of vendor-specific information.
For example, implementations that must conform to an industry- For example, implementations that must conform to an industry-
standard use of DHCPv4, to allow interoperability in a particular standard use of DHCPv4, to allow interoperability in a particular
technology space, may be required to support the vendor-specific technology space, may be required to support the vendor-specific
options of that industry group. But the same implementation may also options of that industry group. But the same implementation may also
require support for vendor-specific options defined by the require support for vendor-specific options defined by the
manufacturer. In particular, this is an issue for vendors of devices manufacturer. In particular, this is an issue for vendors of devices
supporting CableLabs standards, such as DOCSIS, CableHome, and supporting CableLabs standards, such as DOCSIS, CableHome, and
PacketCable, since those standards define an industry-specific use PacketCable, since those standards define an industry-specific use
for options 60 and 43. for options 60 and 43.
This document defines two new options, modeled on the IPv6 options This document defines two new options, modeled on the IPv6 options
for vendor class and vendor-specific information [3], which contain for vendor class and vendor-specific information defined in RFC 3315
Enterprise Numbers to remove ambiguity. If desired, these new [4], which contain Enterprise Numbers to remove ambiguity. If
options can be used in addition to the current vendor class and desired, these new options can be used in addition to the current
vendor information options, whose definition is unaffected by this vendor class and vendor information options, whose definition is
document. unaffected by this document.
2. Vendor-Identifying Vendor Class Option 2. Multiple Instances of Options
The options defined in this document are intended to occur multiple
times in a DHCP packet, as may be required. To provide support for
long option values, RFC 3396 [2] requires that all multiply instanced
options be contatenated into one long instance. Because of this, the
format of these new vendor options includes extra length fields to
allow concatenation of multiple instances, while preserving the
integrity of each. Support for RFC 3396 is not widespread at the
time of this writing, so implementations SHOULD attempt to format
instances of these new vendor options such that they can be
interpreted without concatenation, if support for RFC 3396 is in
doubt.
3. Vendor-Identifying Vendor Class Option
A DHCP client may use this option to unambiguously identify the A DHCP client may use this option to unambiguously identify the
vendor that manufactured the hardware on which the client is running, vendor that manufactured the hardware on which the client is running,
or an industry consortium to which the vendor belongs. The or an industry consortium to which the vendor belongs. The
information contained in the data area of this option is contained in information contained in the data area of this option is contained in
one or more opaque fields that identify details of the hardware one or more opaque fields that may identify details of the hardware
configuration. configuration.
The format of the V-I Vendor Class option is: The format of the V-I Vendor Class option is:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 1 1 1 1 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
| OPTION_V-I VENDOR_CLASS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | option-code | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise-number | | enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
. . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. vendor-class-data . | data-len | |
. . . . . +-+-+-+-+-+-+-+-+ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / vendor-class-data /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_V-I VENDOR_CLASS (to be assigned by option-code OPTION_V-I VENDOR_CLASS (to be assigned by IANA)
IANA)
option-len 4 + length of vendor class data field option-len 5 + length of vendor class data field
enterprise-number The vendor's registered Enterprise Number as enterprise-number The vendor's 32-bit Enterprise Number as
registered with IANA [4]. registered with IANA [5].
vendor-class-data The hardware configuration of the host on data-len Length of vendor-class-data field
which the client is running.
Each instance of this option contains information corresponding to a vendor-class-data Details of the hardware configuration of the host
single Enterprise Number. Multiple instances of this option may be on which the client is running, or of industry
present, and each is treated independently. consortium compliance
Each instance of this option contains information corresponding to
one or more Enterprise Numbers. Multiple instances of this option
may be present, and may be concatenated in accordance with RFC 3396.
An Enterprise Number SHOULD only occur once among all instances of
this option. Behavior is undefined if an Enterprise Number occurs
multiple times. The information for each Enterprise Number is
treated independently, regardless or whether it occurs in an option
with other Enterprise Numbers, or in a separate option.
The vendor-class-data is composed of a series of separate items, each The vendor-class-data is composed of a series of separate items, each
of which describes some characteristic of the client's hardware of which describes some characteristic of the client's hardware
configuration or capabilities. Examples of vendor-class-data configuration or capabilities. Examples of vendor-class-data
instances might include the version of the operating system the instances might include the version of the operating system the
client is running or the amount of memory installed on the client. client is running or the amount of memory installed on the client.
Each instance of the vendor-class-data is formatted as follows: Each instance of the vendor-class-data is formatted as follows:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+ 1 1 1 1 1 1
| vendor-class-len | opaque-data | 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| data-len | |
+-+-+-+-+-+-+-+-+ opaque-data |
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The vendor-class-len is two octets long and specifies the length of The data-len is one octet long and specifies the length of the opaque
the opaque vendor class data in network byte order. vendor class data in network byte order.
3. Vendor-Identifying Vendor-Specific Information Option 4. Vendor-Identifying Vendor-Specific Information Option
DHCP Clients and servers may use this option to exchange vendor- DHCP clients and servers may use this option to exchange vendor-
specific information. specific information.
The format of the V-I Vendor-specific Information option is: The format of the V-I Vendor-specific Information option is:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 1 1 1 1 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
| OPTION_V-I VENDOR_OPTS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | option-code | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise-number | | enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
. . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. option-data . | data-len | |
. . +-+-+-+-+-+-+-+-+ option-data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_V-I VENDOR_OPTS (to be assigned by option-code OPTION_V-I VENDOR_OPTS (to be assigned by IANA)
IANA)
option-len 4 + length of option-data field option-len 5 + length of option-data field
enterprise-number The vendor's registered Enterprise Number as enterprise-number The vendor's registered 32-bit Enterprise Number
registered with IANA [4]. as registered with IANA [5].
option-data Encapsulated vendor-specific options, data-len Length of option-data field
described below.
option-data Vendor-specific options, described below.
The definition of the information carried in this option is vendor The definition of the information carried in this option is vendor
specific. The vendor is indicated in the enterprise-number field. specific. The vendor is indicated in the enterprise-number field.
Each instance of this option contains information corresponding to a Each instance of this option contains information corresponding to
single Enterprise Number. Multiple instances of this option may be one or more Enterprise Numbers. Multiple instances of this option
present, and each is treated independently. may be present, and may be concatenated in accordance with RFC 3396.
An Enterprise Numbers SHOULD only occur once among all instances of
this option. Behavior is undefined if an Enterprise Number occurs
multiple times. The information for each Enterprise Number is
treated independently, regardless or whether it occurs in an option
with other Enterprise Numbers, or in a separate option.
Use of vendor-specific information allows enhanced operation, Use of vendor-specific information allows enhanced operation,
utilizing additional features in a vendor's DHCP implementation. utilizing additional features in a vendor's DHCP implementation.
Servers not equipped to interpret the vendor-specific information Servers not equipped to interpret the vendor-specific information
sent by a client MUST ignore it. Clients that do not receive desired sent by a client MUST ignore it. Clients that do not receive desired
vendor-specific information SHOULD make an attempt to operate without vendor-specific information SHOULD make an attempt to operate without
it. it.
The encapsulated vendor-specific options field MUST be encoded as a The encapsulated vendor-specific options field MUST be encoded as a
sequence of code/length/value fields of identical format to the DHCP sequence of code/length/value fields of identical format to the DHCP
options field. The option codes are defined by the vendor identified options field. The option codes are defined by the vendor identified
in the enterprise-number field and are not managed by IANA. Option in the enterprise-number field and are not managed by IANA. Option
codes 0 and 255 have no pre-defined interpretation or format. Each codes 0 and 255 have no pre-defined interpretation or format. Each
of the encapsulated options is formatted as follows: of the encapsulated options is formatted as follows:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1 1 1 1 1 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
| opt-code | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | subopt-code | subopt-len |
. . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. option-data . / sub-option-data /
. . / /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
opt-code The code for the encapsulated option
option-len An unsigned integer giving the length of the subopt-code The code for the encapsulated option
option-data field in this encapsulated option
in octets.
option-data The data area for the encapsulated option subopt-len An unsigned integer giving the length of the
option-data field in this encapsulated option in
octets.
Multiple instances of the Vendor-specific Information option may sub-option-data Data area for the encapsulated option
appear in a DHCP message. Each instance of the option is interpreted
according to the option codes defined by the vendor identified by the
Enterprise Number in that option.
4. IANA Considerations 5. IANA Considerations
The values for the V-I VENDOR CLASS and V-I VENDOR OPTS option codes The values for the V-I VENDOR CLASS and V-I VENDOR OPTS option codes
must be assigned from the numbering space defined for public DHCP must be assigned from the numbering space defined for public DHCP
Options in RFC 2939 [5]. Options in RFC 2939 [6].
5. Security Considerations 6. Security Considerations
This document in and by itself provides no security, nor does it This document in and by itself provides no security, nor does it
impact existing security. DHCP provides an authentication and impact existing security. DHCP provides an authentication and
message integrity mechanism, as described in RFC 3118 [6], which may message integrity mechanism, as described in RFC 3118 [7], which may
be used if authenticity is required for data carried by the options be used if authenticity is required for data carried by the options
defined in this document. defined in this document.
References References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] S. Alexander and R. Droms. "DHCP Options and BOOTP Vendor [2] Lemon, T. and S. Chesire, "Encoding Long Options in the Dynamic
Host Configuration Protocol (DHCPv4)", RFC 3396, November 2002.
[3] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 2132, March 1997. Extensions", RFC 2132, March 1997.
[3] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and [4] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and M.
Carney, M., "Dynamic Host Configuration Protocol for IPv6 Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
(DHCPv6)", RFC 3315, July 2003. RFC 3315, July 2003.
[4] IANA. Private Enterprise Numbers. [5] IANA, "Private Enterprise Numbers", <http://www.iana.org/
http://www.iana.org/assignments/enterprise-numbers.html. assignments/enterprise-numbers.html>.
[5] 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.
[6] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages", RFC [7] Droms, R. and W. Arbaugh, "Authentication for DHCP Message", RFC
3118, June 2001. 3118, June 2001.
Author's Address Author's Address
Josh Littlefield Josh Littlefield
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 USA Boxborough, MA 01719
USA
Phone: 978-936-1379 Phone: +1 978-936-1379
Email: joshl@cisco.com EMail: joshl@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 (2004). 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 Acknowledgement
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/