idnits 2.17.1 draft-huston-ipv6-documentation-prefix-03.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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 108 has weird spacing: '... prefix in th...' -- 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 (January 31, 2004) is 7384 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) ** Obsolete normative reference: RFC 3513 (ref. '1') (Obsoleted by RFC 4291) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Individual Submission G. Huston 3 Internet-Draft Telstra 4 Expires: July 31, 2004 A. Lord 5 APNIC 6 P. Smith 7 Cisco 8 January 31, 2004 10 IPv6 Address Prefix reserved for Documentation 11 draft-huston-ipv6-documentation-prefix-03.txt 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC2026. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that other 20 groups may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at http:// 28 www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on July 31, 2004. 35 Copyright Notice 37 Copyright (C) The Internet Society (2004). All Rights Reserved. 39 Abstract 41 To reduce the likelihood of conflict and confusion when relating 42 documented examples to deployed systems, an IPv6 unicast address 43 prefix is reserved for use in examples in RFCs, books, documentation, 44 and the like. Since site-local and link- local unicast addresses have 45 special meaning in IPv6, these addresses cannot be used in many 46 example situations. The document describes the use of the IPv6 47 address prefix 2001:DB8::/32 as a reserved prefix for use in 48 documentation. 50 1. Introduction 52 The address architecture for IPv6 [1] does not specifically allocate 53 an IPv6 address prefix for use for documentation purposes. 54 Documentation material is currently using address prefixes drawn from 55 address blocks already allocated or assigned to existing 56 organizations or to well known ISPs, or drawn from the currently 57 unallocated address pool. Such use conflicts with existing or future 58 allocations or assignments of IPv6 address space. 60 The problems such conflicts may cause have already been encountered 61 with IPv4 where literal use of documented examples in a production 62 environment causes address and routing conflicts with existing 63 services. In making an explicit allocation of a documentation address 64 prefix, it is intended that such operational problems may be avoided 65 for IPv6. 67 Similar, but different, discussion also applies to top level domain 68 names and some have been reserved for similar purposes. [2] 70 2. Documentation IPv6 Address Prefix 72 To allow documentation to accurately describe deployment examples, 73 the use of site local or link local addresses is inappropriate, and a 74 unicast address block is required. All IPv6 unicast address space is 75 currently marked as reserved, unassigned or has been assigned to the 76 Internet Assigned Numbers Authority (IANA) for further redistribution 77 to the Regional Internet Registries (RIRs) [1], but no unicast 78 address space has been specifically nominated for the purposes of use 79 in documented examples. 81 Following acceptance within the Asia Pacific regional addressing 82 community of a proposal for a block of IPv6 address space to be 83 reserved for documentation purposes, the Asia Pacific Network 84 Information Centre (APNIC) allocated a unicast address prefix for 85 documentation purposes. The address block is within the range of a 86 conventional allocation size, so that documentation can accurately 87 match deployment scenarios. 89 The documentation prefix described in this memo can also be used to 90 generate multicast addresses for documentation, using the Unicast 91 prefix-based proposal [3]. Representing other kinds of multicast 92 addresses in documentation is outside the scope of this memo. 94 The prefix allocated for documentation purposes is 2001:DB8::/32 96 3. Operational Implications 97 This assignment implies that IPv6 network operators should add this 98 address prefix to the list of non-routeable IPv6 address space, and 99 if packet filters are deployed, then this address prefix should be 100 added to packet filters. 102 This not a local-use address prefix, and the filters may be used in 103 both local and public contexts. 105 4. IANA Considerations 107 IANA is to record the allocation of the IPv6 global unicast address 108 prefix 2001:DB8::/32 as a documentation-only prefix in the IPv6 109 address registry. No end party is to be assigned this address. 111 5. Security Considerations 113 IPv6 addressing documents do not have any direct impact on Internet 114 infrastructure security. 116 6. Acknowledgements 118 The authors acknowledge the work of Marc Blanchet, assisted by Alain 119 Durand, Robert Elz, Bob Fink and Dave Thaler, in authoring a previous 120 proposal for a V6 documentation prefix. 122 Normative References 124 [1] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) 125 Addressing Architecture", RFC 3513, April 2003. 127 Informative References 129 [2] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 130 32, RFC 2606, June 1999. 132 [3] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast 133 Addresses", RFC 3306, August 2002. 135 Authors' Addresses 137 Geoff Huston 138 Telstra 140 Anne Lord 141 Asia Pacific Network Information Centre 142 Philip Smith 143 Cisco Systems 145 Intellectual Property Statement 147 The IETF takes no position regarding the validity or scope of any 148 intellectual property or other rights that might be claimed to 149 pertain to the implementation or use of the technology described in 150 this document or the extent to which any license under such rights 151 might or might not be available; neither does it represent that it 152 has made any effort to identify any such rights. Information on the 153 IETF's procedures with respect to rights in standards-track and 154 standards-related documentation can be found in BCP-11. Copies of 155 claims of rights made available for publication and any assurances of 156 licenses to be made available, or the result of an attempt made to 157 obtain a general license or permission for the use of such 158 proprietary rights by implementors or users of this specification can 159 be obtained from the IETF Secretariat. 161 The IETF invites any interested party to bring to its attention any 162 copyrights, patents or patent applications, or other proprietary 163 rights which may cover technology that may be required to practice 164 this standard. Please address the information to the IETF Executive 165 Director. 167 Full Copyright Statement 169 Copyright (C) The Internet Society (2004). All Rights Reserved. 171 This document and translations of it may be copied and furnished to 172 others, and derivative works that comment on or otherwise explain it 173 or assist in its implementation may be prepared, copied, published 174 and distributed, in whole or in part, without restriction of any 175 kind, provided that the above copyright notice and this paragraph are 176 included on all such copies and derivative works. However, this 177 document itself may not be modified in any way, such as by removing 178 the copyright notice or references to the Internet Society or other 179 Internet organizations, except as needed for the purpose of 180 developing Internet standards in which case the procedures for 181 copyrights defined in the Internet Standards process must be 182 followed, or as required to translate it into languages other than 183 English. 185 The limited permissions granted above are perpetual and will not be 186 revoked by the Internet Society or its successors or assignees. 188 This document and the information contained herein is provided on an 189 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 190 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 191 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 192 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 193 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 195 Acknowledgment 197 Funding for the RFC Editor function is currently provided by the 198 Internet Society.