draft-ietf-dhc-vendor-02.txt   draft-ietf-dhc-vendor-03.txt 
DHC Working Group J. Littlefield DHC Working Group J. Littlefield
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: November 17, 2004 May 17, 2004 Expires: December 21, 2004 June 21, 2004
Vendor-Identifying Vendor Options for DHCPv4 Vendor-Identifying Vendor Options for DHCPv4
draft-ietf-dhc-vendor-02.txt draft-ietf-dhc-vendor-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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://www.ietf.org/ietf/1id-abstracts.txt. http://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 November 17, 2004. This Internet-Draft will expire on December 21, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). 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 limiting or ambiguous when a DHCP client represents multiple be limiting or ambiguous when a DHCP client represents multiple
vendors. This document defines two new options, modeled on the IPv6 vendors. This document defines two new options, modeled on the IPv6
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Supporting Multiple Vendor Instances . . . . . . . . . . . . . 3 2. Supporting Multiple Vendor Instances . . . . . . . . . . . . . 3
3. Vendor-Identifying Vendor Class Option . . . . . . . . . . . . 4 3. Vendor-Identifying Vendor Class Option . . . . . . . . . . . . 4
4. Vendor-Identifying Vendor-Specific Information Option . . . . 5 4. Vendor-Identifying Vendor-Specific Information Option . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1 Normative References . . . . . . . . . . . . . . . . . . . . 8 7.1 Normative References . . . . . . . . . . . . . . . . . . . . 8
7.2 Informative References . . . . . . . . . . . . . . . . . . . 8 7.2 Informative References . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . 10
1. Introduction 1. Introduction
The DHCP protocol for IPv4, RFC 2131 [2], defines options that allow The DHCP protocol for IPv4, RFC 2131 [2], defines options that allow
a client to indicate its vendor type (option 60), and to allow the a client to indicate its vendor type (option 60), and to allow the
DHCP client and server to exchange vendor-specific information DHCP client and server to exchange vendor-specific information
(option 43) [5]. While there is no prohibition against passing (option 43) [5]. While there is no prohibition against passing
multiple copies of these options in a single packet, doing so would multiple copies of these options in a single packet, doing so would
introduce ambiguity of interpretation, particularly if conveying introduce ambiguity of interpretation, particularly if conveying
vendor-specific information for multiple vendors. The vendor vendor-specific information for multiple vendors. The vendor
skipping to change at page 3, line 34 skipping to change at page 3, line 34
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 [9] standards, such as DOCSIS, CableHome, and supporting CableLabs [9] 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 defined in RFC 3315 for vendor class and vendor-specific information defined in RFC 3315
[6], which contain Enterprise Numbers to remove ambiguity about the [6], which contain IANA-assigned Enterprise Numbers [3] to remove
interpretation of their contents. If desired, these new options can ambiguity about the interpretation of their contents. If desired,
be used in addition to the current vendor class and vendor these new options can be used in addition to the current vendor class
information options, whose definition is unaffected by this document. and vendor information options, whose definition is unaffected by
this document.
2. Supporting Multiple Vendor Instances 2. Supporting Multiple Vendor Instances
The options defined in this document may each contain data The options defined in this document may each contain data
corresponding to more than one vendor. The data portion of each corresponding to more than one vendor. The data portion of each
option defined here contains an enterprise number, followed by an option defined here contains an enterprise number (assigned by IANA
internal data length, followed by vendor-specific data. This [3]), followed by an internal data length, followed by
sequence may be repeated multiple times within each option. Because vendor-specific data. This sequence may be repeated multiple times
of the possibility that the aggregate of the vendor-specific data for within each option. Because of the possibility that the aggregate of
either option will exceed 255 octets, these options are hereby the vendor-specific data for either option will exceed 255 octets,
declared to be "concatenation-requiring", as defined by RFC 3396 [4]. these options are hereby declared to be "concatenation-requiring", as
As such, the aggregate of all instances of vendor-specific data is to defined by RFC 3396 [4]. As such, the aggregate of all instances of
be considered one long option, for each of the two options defined vendor-specific data is to be considered one long option, for each of
here. These long options can be divided into smaller options for the two options defined here. These long options can be divided into
packet encoding in conformance with RFC 3396, on whatever octet smaller options for packet encoding in conformance with RFC 3396, on
boundaries are convenient to the implementation. Dividing on the whatever octet boundaries are convenient to the implementation.
boundaries between vendor instances is not required, but may be Dividing on the boundaries between vendor instances is not required,
convenient for encoding or packet tracing. but may be convenient for encoding or packet tracing.
3. Vendor-Identifying Vendor Class Option 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,
the software in use, or an industry consortium to which the vendor the software in use, or an industry consortium to which the vendor
belongs. The information contained in the per-vendor data area of belongs. The information contained in the per-vendor data area of
this option is contained in one or more opaque fields that may this option is contained in one or more opaque fields that may
identify details of the hardware configuration. identify details of the hardware configuration.
skipping to change at page 4, line 46 skipping to change at page 5, line 4
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ----
| enterprise-number2 | ^ | enterprise-number2 | ^
| | | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| data-len2 | | optional | data-len2 | | optional
+-+-+-+-+-+-+-+-+ | | +-+-+-+-+-+-+-+-+ | |
/ vendor-class-data2 / | / vendor-class-data2 / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
~ ... ~ V ~ ... ~ V
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ----
option-code OPTION_V-I_VENDOR_CLASS (to be assigned by IANA) option-code OPTION_V-I_VENDOR_CLASS (to be assigned by IANA)
option-len 5 + length of vendor class data field
option-len total length of all following option data in
octets
enterprise-numberN The vendor's 32-bit Enterprise Number as enterprise-numberN The vendor's 32-bit Enterprise Number as
registered with IANA [3] registered with IANA [3]
data-lenN Length of vendor-class-data field data-lenN Length of vendor-class-data field
vendor-class-dataN Details of the hardware configuration of the vendor-class-dataN Details of the hardware configuration of the
host on which the client is running, or of host on which the client is running, or of
industry consortium compliance industry consortium compliance
skipping to change at page 6, line 35 skipping to change at page 6, line 37
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| data-len2 | | optional | data-len2 | | optional
+-+-+-+-+-+-+-+-+ option-data2 | | +-+-+-+-+-+-+-+-+ option-data2 | |
/ / | / / |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
~ ... ~ V ~ ... ~ V
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ---- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ----
option-code OPTION_V-I_VENDOR_OPTS (to be assigned by IANA) option-code OPTION_V-I_VENDOR_OPTS (to be assigned by IANA)
option-len 5 + length of option-data field option-len total length of all following option data in
octets
enterprise-numberN The vendor's registered 32-bit Enterprise Number enterprise-numberN The vendor's registered 32-bit Enterprise Number
as registered with IANA [3] as registered with IANA [3]
data-lenN Length of option-data field data-lenN Length of option-data field
option-dataN Vendor-specific options, described below. option-dataN 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.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/