idnits 2.17.1 draft-ietf-dhc-dhcpv4-vendor-message-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? -- It seems you're using the 'non-IETF stream' Licence Notice instead Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 12, 2009) is 5575 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'EID' Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DHC B. Volz 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track January 12, 2009 5 Expires: July 16, 2009 7 DHCPv4 Vendor-specific Message 8 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on July 16, 2009. 33 Copyright Notice 35 Copyright (c) 2009 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. 45 Abstract 47 This document requests a vendor-specific DHCPv4 message assignment. 48 This message can be used for vendor specific and experimental 49 purposes. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Vendor-specific Message . . . . . . . . . . . . . . . . . . . . 3 56 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 59 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 60 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 1. Introduction 65 The DHCPv4 [RFC2131] protocol specifies a mechanism for the 66 assignment of addresses and configuration information to nodes. The 67 protocol provides for 256 possible message codes, of which a small 68 number are assigned ([DHCPv4Params]). Each of the assigned message 69 codes have specific purposes. New message codes are assigned through 70 IETF Standards Action. 72 There may be a need for vendors of DHCPv4 clients, relay agents, or 73 servers to experiment with new capabilities that require new messages 74 to be exchanged between these elements. Thus, this document defines 75 the format for and requests that a new message code be reserved for 76 vendor-specific and experimental purposes. 78 2. Terminology 80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 82 document are to be interpreted as described in [RFC2119]. 84 3. Vendor-specific Message 86 The vendor-specific message may be exchanged between clients, relay 87 agents, and/or servers and allows multiple vendors to make use of the 88 message for completely different and independent purposes. 90 Clients and servers MAY chose to support this message; those that do 91 not, MUST discard the message. Relay agents SHOULD relay these 92 messages as they would other DHCPv4 messages unless the relay agent 93 understands the specific message and knows that the message was 94 directed at it. 96 Applications using these messages MUST NOT assume that all DHCPv4 97 clients, relay agents, and servers support them and MUST use good 98 networking practices when transmitting and retransmitting these 99 messages. For some applications, it may be appropriate to use 100 Vendor-Identifying Vendor Options [RFC3925] in a standard DHCPv4 101 exchange to negotiate whether the end-points support the vendor- 102 specific message. 104 A vendor-specifc message is constructed by placing the Vendor- 105 Specific Message number (254) into the DHCP Message Type option 106 [RFC2132] and including the Vendor Message Option defined below. A 107 Vendor-Specific Message that does not contain the Vendor Message 108 Option MUST be ignored. A Vendor Message Option in a DHCPv4 message 109 other than the Vendor-Specific Message MUST be ignored. 111 The format of the Vendor Message Option is shown below: 113 1 1 1 1 1 1 114 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 | option-code | option-len | 117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 | | 119 + enterprise-number + 120 | | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | vendor | | 123 | msg-type | | 124 +-+-+-+-+-+-+-+-+ | 125 / vendor-option-data / 126 ~ ... ~ 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 option-code OPTION_VENDOR_MESSAGE (TBD) 131 option-len 5 plus the length of the vendor-option-data. 133 enterprise-number The vendor's 32-bit Enterprise Number as 134 registered with [EID], in network octet order. 136 vendor-msg-type The vendor's message-type. The values are 137 defined by the vendor identified in the 138 enterprise-number field and are not managed by 139 IANA. 141 vendor-option-data Vendor specific data (of length option-len 142 minus 5 octets). This is optional. 144 The vendor-option-data field MUST be encoded as a sequence of code/ 145 length/value fields of identical format to the DHCP options field. 146 The option codes are defined by the vendor identified in the 147 enterprise-number field and are not managed by IANA. Option codes 0 148 and 255 have no pre-defined interpretation or format. Each of the 149 encapsulated options is formatted as follows: 151 1 1 1 1 1 1 152 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | subopt-code | subopt-len | 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 / sub-option-data / 157 ~ ... ~ 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 subopt-code The code for the encapsulated option. 162 subopt-len An unsigned integer giving the length of the 163 option-data field in this encapsulated option in 164 octets. 166 sub-option-data Data area for the encapsulated option. 168 Clients, relay agents, and/or servers supporting the Vendor Message 169 Option MUST support [RFC3396]. 171 Note: Vendor-Identifying Vendor Options [RFC3925] are not used to 172 convey the vendor identification (enterprise-number) for the vendor- 173 specific message as the message may contain instances of those 174 options for other reasons. 176 4. Security Considerations 178 The Security Considerations of [RFC2131] apply. 180 This new message does potentially open up new avenues of attacking 181 clients, relay agents, or servers. The exact nature of these attacks 182 will depend on what functions and capabilities the message exposes 183 and are thus not possible to describe in this document. Clients and 184 servers that have no use for these messages SHOULD discard them and 185 thus the threat is no different than before this message was 186 assigned. 188 Vendors using this new message should use the DHCPv4 security 189 mechanisms (such as [RFC3118] as appropriate) and carefully consider 190 the security implications of the functions and capabilities exposed. 192 5. IANA Considerations 194 IANA is requested to assign DHCPv4 Message type 254 to the Vendor- 195 specific Message in the registry maintained in [DHCPv4Params]: 197 254 VENDOR-SPECIFIC 199 IANA is requested to assign a DHCPv4 option number to the Vendor 200 Message Option in the registry maintained in [DHCPv4Params]: 202 TBD OPTION_VENDOR_MESSAGE 204 6. References 206 6.1. Normative References 208 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 209 Requirement Levels", BCP 14, RFC 2119, March 1997. 211 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 212 RFC 2131, March 1997. 214 [EID] IANA, "Private Enterprise Numbers. 215 http://www.iana.org/assignments/enterprise-numbers". 217 6.2. Informative References 219 [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor 220 Extensions", RFC 2132, March 1997. 222 [RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP 223 Messages", RFC 3118, June 2001. 225 [RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the 226 Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396, 227 November 2002. 229 [RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for 230 Dynamic Host Configuration Protocol version 4 (DHCPv4)", 231 RFC 3925, October 2004. 233 [DHCPv4Params] 234 IANA, "Dynamic Host Configuration Protocol (DHCP) and 235 Bootstrap Protocol (BOOTP) Parameters. 236 http://www.iana.org/assignments/bootp-dhcp-parameters". 238 Author's Address 240 Bernard Volz 241 Cisco Systems, Inc. 242 1414 Massachusetts Ave. 243 Boxborough, MA 01719 244 USA 246 Phone: +1 978 936 0000 247 Email: volz@cisco.com