idnits 2.17.00 (12 Aug 2021) /tmp/idnits53349/draft-volz-dhc-dhcpv6-site-options-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([DHCPv6]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 4, 2003) is 6980 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) == Outdated reference: draft-ietf-dhc-dhcpv6 has been published as RFC 3315 Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force B. Volz 2 INTERNET DRAFT Ericsson 3 Expires: August 2003 April 4, 2003 5 Site Specific Options for DHCP for IPv6 6 draft-volz-dhc-dhcpv6-site-options-00.txt 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as Internet- 16 Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This Internet-Draft will expire on October 4, 2003. 31 Copyright Notice 33 Copyright (C) The Internet Society (2003). All Rights Reserved. 35 Abstract 37 This document specifies that a portion of the DHCP for IPv6 [DHCPv6] 38 16-bit option space is reserved for site-specific options. Site- 39 specific options are to be used for site specific needs and MUST NOT 40 be used for public (IANA assigned) or vendor specific options. 42 1. Introduction 44 The DHCP for IPv6 base specification [DHCPv6] did not reserve a 45 range of option numbers for private use within sites, as was defined 46 for DHCP for IPv4 [RFC2132]. 48 This document specifies that a portion of the DHCP for IPv6 16-bit 49 option space is reserved for site-specific options. Site-specific 50 options are to be used for site specific needs and MUST NOT be used 51 for public (IANA assigned) or vendor specific options. 53 2. Requirements 55 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 56 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this 57 document, are to be interpreted as described in RFC 2119 [RFC2119]. 59 3. Site-Specific Options 61 The DHCP for IPv6 option codes from 65,280 to 65,534 are to be 62 reserved for use by site-specific options. This reserves 254 option 63 values for site-specific use. 65 This range of option codes MUST NOT be assigned by IANA to any public 66 options. 68 This document does not define the behavior of clients, servers, and 69 relay agents with respect to site-specific options, as these are 70 site issues. However, it is recommended that client implementations: 72 a. allow the list of site-specific options to be included in an 73 Option Request Option (DHCPv6) to be configured, 75 b. allow the list of site-specific options and the corresponding 76 values to be sent in client request messages to be configured, and 78 c. allow application software to obtain the data returned for site- 79 specific options. 81 4. IANA Recommendations 83 IANA is requested to reserve the DHCP for IPv6 options from 65,280 84 to 65,534 (decimal), inclusive, for site-specific options. IANA will 85 not manage these options; sites will manage this space. 87 5. Security Considerations 89 This document in and by itself provides no security, nor does it 90 impact existing security. 92 Acknowledgements 94 Thanks to Ralph Droms for his input into this document. 96 References 98 [DHCPv6] Droms (ed.), R, Bound, J., Volz, B., Lemon, T., Perkins, 99 C., Carney, M., "Dynamic Host Configuration Protocol for IPv6 100 (DHCPv6)", draft-ietf-dhc-dhcpv6-28 (work in progress), November 101 2002. 103 [RFC2132] Alexander, S. and R. Droms, "DHCP options and BOOTP Vendor 104 Extensions", RFC 2132, March 1997. 106 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 107 Requirement Levels", BCP 14, RFC 2119, March 1997. 109 Author's Address 111 Bernie Volz 112 Ericsson 113 959 Concord Street 114 Framingham, MA 01701 115 Phone: +1 508 875 3162 116 EMail: bernie.volz@ericsson.com 118 Full Copyright Statement 120 Copyright (C) The Internet Society (2003). All Rights Reserved. 122 This document and translations of it may be copied and furnished to 123 others, and derivative works that comment on or otherwise explain it 124 or assist in its implementation may be prepared, copied, published 125 and distributed, in whole or in part, without restriction of any 126 kind, provided that the above copyright notice and this paragraph are 127 included on all such copies and derivative works. However, this 128 document itself may not be modified in any way, such as by removing 129 the copyright notice or references to the Internet Society or other 130 Internet organizations, except as needed for the purpose of 131 developing Internet standards in which case the procedures for 132 copyrights defined in the Internet Standards process must be 133 followed, or as required to translate it into languages other than 134 English. 136 The limited permissions granted above are perpetual and will not be 137 revoked by the Internet Society or its successors or assigns. 139 This document and the information contained herein is provided on an 140 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 141 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 142 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 143 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 144 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 146 Acknowledgement 148 Funding for the RFC Editor function is currently provided by the 149 Internet Society.