Please refer to the current edition of the "Internet Official Protocol Standards" STD 1 for the standardization state and status of this protocol. Distribution of this memo is unlimited. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, that contain Enterprise Numbers to remove ambiguity. Table of Contents 1.
Conventions Used in This Document. Supporting Multiple Vendor Instances. Vendor-Identifying Vendor Class Option.
IANA Considerations. Security Considerations. Normative References. Informative References.
Subscribe to RSS
Author's Address. Full Copyright Statement.
Although there is no prohibition against passing multiple copies of these options in a single packet, doing so would introduce ambiguity of interpretation, particularly if conveying vendor-specific information for multiple vendors.
The vendor identified by option 60 defines the interpretation of option 43, which itself carries no vendor identifier. Furthermore, the concatenation of multiple instances options reviews 2020 the same option, required by RFC and specified by RFC [ 4 ], means that multiple copies of options 60 or 43 would not remain independent.
In some circumstances, an implementation may need to support multiple, independently defined forms of vendor-specific information. For example, implementations that must conform to an industry- standard use of DHCPv4, to allow interoperability in a particular technology space, may be required to support the vendor-specific options of that industry group. But the same implementation may also require support for vendor-specific options defined by the manufacturer.
This document defines two new options, modeled on the IPv6 options for vendor class what is a vendor option vendor-specific information defined in RFC [ 6 ], that contain IANA-assigned Enterprise Numbers [ 3 ] to remove ambiguity about the interpretation of their contents. If desired, these new options can be used in addition to the current vendor class and vendor information options, whose definition is unaffected by this document.
Supporting Multiple Vendor Instances The options defined in this document may each contain data corresponding to more than one vendor.
The data portion of each option defined here contains an enterprise number assigned by IANA [ 3 ]followed by an internal data length, followed by vendor- specific data. This sequence may be repeated multiple times within each option.
Vendor-specific option (Option 43)
Because the aggregate of the vendor-specific data for either option may exceed octets, these options are hereby declared to be "concatenation-requiring", as defined by RFC [ 4 ]. As such, for binary options how to figure it out of the what is a vendor option options defined here, the aggregate of all instances of vendor-specific data is to be considered one long option.
These long options can be divided into smaller options for packet encoding in conformance with RFCon whatever octet boundaries are convenient to the implementation.
Dividing on the boundaries between vendor instances is not required but may be convenient for encoding or packet tracing. Vendor-Identifying Vendor Class Option A DHCP client may use this option to unambiguously identify the vendor that manufactured the hardware on which the client is running, the software in use, or an industry consortium to which the vendor belongs.
User and Vendor Class Options
The information contained in the per-vendor data area of this option is contained in one or more what is a vendor option fields that may identify details of the hardware configuration. 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. Littlefield Standards Track [Page 4] RFC Vendor-Identifying Vendor Options October The vendor-class-data comprises a series of separate items, each of which describes some characteristic of the client's hardware configuration or capabilities.
Examples of what is a vendor option instances might include the version of the operating system the client is running or the amount of memory installed on the client.
Either party may send this option, as needed. Although a typical case might be for a client to send the Vendor- Identifying Vendor Class option, to elicit a useful Vendor- Identifying Vendor-Specific Information Option, there is no requirement for such a flow.
Vendor Specific Options
The vendor is indicated in the enterprise-number field. This option contains information corresponding to one or more Enterprise Numbers.
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. Servers not equipped to interpret the vendor-specific information sent by a client MUST ignore it. The option codes are defined by the vendor identified in the enterprise-number field and are not managed by IANA.
Dynamic Host Configuration Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters
Option codes 0 and have no pre-defined interpretation or format. Security Considerations This document in and by itself provides no security, nor does it impact existing security. DHCP provides an authentication and message integrity mechanism, as described in RFC [ 8 ], which may be used if authenticity is required for data carried by the options defined in this document. References 7. Normative References [ 1 ] Bradner, S.
Informative References [ 5 ] Alexander, S. This document is subject to the rights, licenses and restrictions contained in BCP 78and except as set forth therein, the authors retain all their rights.
Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard.
Please address the information to the IETF at ietf- ipr ietf.
Littlefield Standards Track [Page 9] Html markup produced by rfcmarkup 1.