Network Working Group R. Hibbs INTERNET-DRAFT Richard Barr Hibbs, P.E. Category: Informational June 13, 2006 Expires: December 15, 2006 Requirements for Proposed Changes to the Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Saved Tuesday, June 13, 2006, 13:13:00 Intellectual Property Rights By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Status of this Memo Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Comments are solicited and should be addressed to the working group's mailing list at dhcwg@ietf.org and/or the author(s). Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo describes the requirements of Internet-Drafts proposing changes to the Dynamic Host Configuration Protocol for IPv4 (DHCPv4). These requirements specifically cover documentation expected whenever message formats or client state transitions are modified. R. Hibbs Expires: December 15, 2006 [Page 1] Internet-Draft DHCPv4 Change Requirements June 13, 2006 1 Introduction During the lifetime of the Dynamic Host Configuration Protocol (DHCPv4) it has been the subject of 30 Requests for Comments (RFCs) regarding the base protocol (five of which added new DHCPv4 message types or extended the protocol in some way) and 18 RFCs concerning other DHCPv4 options. Seven RFCs covered procedures and definition of base options. Additionally, there are constantly a number of Internet-Drafts under consideration for DHCPv4. There has been no standard documentation required to date for new Internet-Drafts concerning DHCPv4, even when proposed changes altered message formats, the client state machine, or processing required of servers, relay agents, or clients. This memo proposes a common-sense minimum standard for documentation required in any new Internet-Draft that will ensure consistency among the various IETF documents and improve the clarity of proposed changes. 2 Use of Key Words The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3 Applicability 3.1 Assumptions This document assumes that the reader is familiar with the base DHCPv4 protocol as defined in [RFC2131]. 3.2 Scope of this Memo This document explicitly restricts itself to DHCPv4, as defined in [RFC2131] and [RFC2132]. The same document change requirements could apply as well to DHCPv6 [RFC3315], although the RFC numbers and document section and page references would be different. 4 Minimum Documentation Requirements It SHALL be the policy of the Dynamic Host Configuration (DHC) Working Group that new Internet-Drafts concerning DHCPv4 conform to each of the following requirements: 4.1 Description of Message Format Changes An Internet-Draft that proposes any changes to the DHCPv4 message format MUST fully describe the proposed change, and MUST modify or add entries to the message format figures and message requirements tables as appropriate. These include: 1. RFC 2131, Figure 1, "Format of a DHCP message" 2. RFC 2131, Figure 2, "Format of the 'flags' field" 3. RFC 2131, Table 1, "Description of fields in a DHCP message" 4. RFC 2131, Table 2, "DHCP Messages" R. Hibbs Expires: December 15, 2006 [Page 2] Internet-Draft DHCPv4 Change Requirements June 13, 2006 5. RFC 2131, Table 3, "Fields and options used by DHCP servers" 6. RFC 2131, Table 4, "Client messages from different states" 7. RFC 2131, Table 5, "Fields and options used by DHCP clients" Figures and tables appearing in other, relevant RFCs MUST also be updated as appropriate. 4.2 Description of Client State Machine Changes An Internet-Draft that proposes changes to the DHCPv4 client state machine MUST supply an updated version of the client state transition diagram (RFC 2131, Figure 5) showing event triggers, states, and client actions. State transition diagrams appearing in other, relevant RFCs MUST also is updated as appropriate. 4.3 Description of Behavior Changes An Internet-Draft that proposes changes to the behavior of DHCPv4 servers, clients, or relay agents MUST supply an updated description of the modified behavior. For example, see [RFC2131], Sections 4.3 and 4.4, for the description of DHCPv4 server and client behavior, respectively. Relay Agent behavior is described [as "gateway"] in [RFC951]. 5 IANA Considerations None. This memo does not include any numbering requirements requiring IANA activity. 6 Security Considerations None. This memo does not itself specify behavior or functionality. 7 References 7.1 Normative References [RFC951] Croft, B., and Gilmore, J., "Bootstrap Protocol (BOOTP)," RFC 951, September 1985. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol," RFC 2131, March 1997. 7.2 Informative References [BCP-11] Hovey, R., and Bradner, S., "The Organizations Involved in the IETF Standards Process," RFC 2028, October 1996. [RFC1534] Droms, R., "Interoperation Between DHCP and BOOTP," RFC 1534, October 1993. [RFC1542] Wimer, W., "Clarifications and Extensions for the Bootstrap Protocol," RFC 1542, October 1993. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3," RFC 2026, BCP 9, October 1996. R. Hibbs Expires: December 15, 2006 [Page 3] Internet-Draft DHCPv4 Change Requirements June 13, 2006 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2132] Alexander, S., and Droms, R., "DHCP Options and BOOTP Vendor Extensions," March 1997. [RFC2241] Provan, D., "DHCP Options for Novell Directory Services," November 1997. [RFC2242] Droms, R., and Fong, K., "NetWare/IP Domain Name and Information," November 1997. [RFC2322] van den Hout, K., Koopal, A., and van Mook, R., "Management of IP numbers by peg-dhcp," April 1998. [RFC2485] Drach, S., "DHCP Option for The Open Group's User Authentication Protocol," January 1999. [RFC2563] Troll, R., "DHCP Option to Disable Stateless Auto- Configuration in IPv4 Clients," May 1999. [RFC2610] Perkins, C., and Guttman, E., "DHCP Options for Service Location Protocol," June 1999. [RFC2855] Fujisawa, K., "DHCP for IEEE 1394," June 2000. [RFC2937] Smith, C., "The Name Service Search Option for DHCP, September 2000. [RFC2939] Droms, R., "Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types," September 2000. [RFC3004] Stump, G., Droms, R., Gu, Y., Vyaghrapuri, R., Demirtjis, A., Beser, B., and Privat, J., "The User Class Option for DHCP," November 2000. [RFC3011] Waters, G., "The IPv4 Subnet Selection Option for DHCP," November 2000. [RFC3046] Patrick, M., "DHCP Relay Agent Information Option," January 2001. [RFC3074] Volz, B., Gonczi, S., Lemon, T., and Stevens, R., "DHC Load Balancing Algorithm," February 2001. [RFC3118] Droms, R., and Arbaugh, W., "Authentication for DHCP Messages," June 2001. [RFC3203] T'Joens, Y., Hublet, C., and De Schrijver, P., "DHCP reconfigure extension," December 2001. [RFC3256] Jones, D., and Woundy, R., "The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub- option," April 2002. [RFC3361] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers," August 2002. R. Hibbs Expires: December 15, 2006 [Page 4] Internet-Draft DHCPv4 Change Requirements June 13, 2006 [RFC3396] Lemon, T., and Cheshire, S., "Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)," November 2002. [RFC3397] Aboba, B., Cheshire, S., "Dynamic Host Configuration Protocol (DHCP) Domain Search Option," November 2002. [RFC3442] Lemon, T., Cheshire, S., and Volz, B., "The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4," December 2002. [RFC3456] Patel, B., Aboba, B., Kelly, S., Gupta, V., "Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode," January 2003. [RFC3495] Beser, B., and Duffy, P., "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration," March 2003. [RFC3527] Kinnear, K., Stapp, M., Johnson, R., and Kumarasamy, J., "Link Selection sub-option for the Relay Agent Information Option for DHCPv4," April 2003. [RFC3594] Duffy, P., "PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option," September 2003. [RFC3634] Luehrs, K., Woundy, R., Bevilacqua, J., and Dovoust, N., "Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option," December 2003. [RFC3679] Droms, R., "Unused Dynamic Host Configuration Protocol (DHCP) Option Codes," January 2004. [RFC3925] Littlefield, J., "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)," October 2004. [RFC3942] Volz, B., "Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options," November 2004. [RFC3993] Johnson, R., Palaniappan, T., and Stapp, M., "Subscriber- ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option," March 2005. [RFC4014] Droms, R., and Schnizlein, J., "Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option," February 2005. [RFC4030] Stapp, M., and Lemon, T., "The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option," March 2005. [RFC4039] Park, S., Kim, P., and Volz, B., "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)," March 2005. R. Hibbs Expires: December 15, 2006 [Page 5] Internet-Draft DHCPv4 Change Requirements June 13, 2006 [RFC4174] Monia, C., Tseng, J., and Gibbons, K., "The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service," September 2005. {RFC4243} Stapp., M., Johnson, R., and Palaniappan, T., "Vendor- Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option," December 2005. [RFC4280] Chowdhury, K., Yegani, P., and Madour, L., "Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers," November 2005. [RFC4361] Lemon, T., and Sommerfield, B., "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)," February 2006. [RFC4388] Woundy, R., and Kinnear, K., "Dynamic Host Configuration Protocol (DHCP) Leasequery," February 2006. [RFC4436] Aboba, B., Carlson, J., and Cheshire, S., "Detecting Network Attachment in IPv4 (DNAv4)," March 2006. Author's Address Richard Barr Hibbs 952 Sanchez Street San Francisco, California 94114-3362 United States Phone: +1-(415)-648-3920 Fax: +1-(415)-648-9017 Email: rbhibbs@pacbell.net Full Copyright Statement Copyright (C) The Internet Society (2006). All rights reserved. This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. R. Hibbs Expires: December 15, 2006 [Page 6] Internet-Draft DHCPv4 Change Requirements June 13, 2006 Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. 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.org. Acknowledgement Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). R. Hibbs Expires: December 15, 2006 [Page 7]