idnits 2.17.1 draft-delong-ula-example-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([RFC4193], [RFC3489]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 2013) is 4060 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC 4193' is mentioned on line 76, but not defined == Missing Reference: 'RFC3489' is mentioned on line 27, but not defined ** Obsolete undefined reference: RFC 3489 (Obsoleted by RFC 5389) == Missing Reference: 'RFC 3849' is mentioned on line 102, but not defined == Unused Reference: 'RFC3849' is defined on line 142, but no explicit reference was found in the text == Unused Reference: 'RFC4193' is defined on line 146, but no explicit reference was found in the text Summary: 3 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group O. DeLong 2 Internet-Draft DeLong Consulting 3 Category: Informational 4 March 2013 6 ULA IPv6 Address Prefix Reserved for Documentation 7 draft-delong-ula-example-00 9 Status of this Memo 11 This memo provides information for the Internet community. It does 12 not specify an Internet standard of any kind. Distribution of this 13 memo is unlimited. 15 Abstract 17 To reduce the likelihood of conflict and confusion when relating 18 documented examples to deployed systems, an IPv6 Unicast Address 19 prefix is reserved for use in examples in RFCs, books, documentation, 20 and the like. 22 Since the publication of [RFC 4193] (ULA), it is necessary to 23 provide examples of ULA addresses in various documents, including 24 some Internet-Drafts currently under consideration. 26 This draft seeks to add ULA prefixes reserved for documentation 27 purposes similar to the GUA reservation specified in [RFC3489] 29 Status of this Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on September 29, 2013. 46 Copyright Notice 48 Copyright (c) 2013 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents. 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction.....................................................2 64 2. Acknowledgements.................................................2 65 3. Documentation IPv6 Unique Local Address Prefix...................3 66 4. Operational Implications.........................................3 67 5. IANA Considerations..............................................3 68 6. Security Considerations..........................................3 69 7. References.......................................................4 70 7.1. Normative References.........................................4 71 7.2. Informative References.......................................4 72 Authors' Addresses..................................................4 74 1. Introduction 76 [RFC 4193] does not specify a ULA prefix to be used for 77 documentation purposes. For the same reasons an IPv6 Global 78 Unicast Prefix (GUA) is needed for documentation in [RFC 3849], 79 there is also need for a ULA prefix. 81 Whereas [RFC 3849] delegates 2001:db8::/32 to be used for 82 documentation purposes where an IPv6 GUA prefix or address 83 is needed, this memo proposes designating two /48s from 84 ULA space for that purpose when an example of ULA is needed. 86 2. Acknowledgements 88 This draft is a logical extension of the work in [RFC 3849] and 89 I wish to thank and acknowledge the contributions of its authors 90 Geoff Huston, Anne Lord, and Phil Smith. 92 3. Documentation IPv6 ULA Prefix 94 To allow documentation to accurately describe deployment examples, 95 the use of site local or link local addresses is inappropriate, and a 96 unicast address block is required. While there is Global Unicast 97 space designated for Documentation in [RFC 3849], no such provision 98 exists within the ULA prefix (fc00::/7) for either random (fd00::/8) 99 or registered (fc00::/8). 101 Since 2001:db8::/32 was designated for documentation purposes in 102 [RFC 3849] and is widely and readily recognized as such throughout 103 the networking community, this memo suggests the use of similar 104 ranges within the ULA prefixes for that same purpose. The proposed 105 prefixes are fc00:2001:db8::/48 (ULA Registered) and 106 fd00:2001:db8::/48 (ULA Random), respectively. 108 In the case of fc00:2001:db8::/48 this would serve only as a 109 statement of intent until such time as the use of fc00::/8 is 110 documented by the IETF. 112 4. Operational Implications 114 This assignment implies that IPv6 network operators should not 115 use these prefixes in their actual deployments of IPv6 ULA. 117 Further it implies that these prefixes should be specifically 118 filtered in any situation where overlapping ULA prefixes may be 119 otherwise permitted by route or packet filters. 121 This is not a local-use prefix, and the filters may be used in 122 both local and public contexts, though in the public context, a 123 more general filter of all ULA space (fc00::/7) may be more 124 desirable. In general, the combination of the specific and more 125 generic filter together should, while unnecessary, not have 126 any harmful effects. 128 5. IANA Considerations 130 IANA is to record the allocation of the IPv6 ULA prefixes 131 fc00:2001:db8::/48 and fd00:2001:db8::/48 as additional 132 documentation-only prefixes in the IPv6 address registry. 133 No end party is to be assigned these addresses. 135 6. Security Considerations 137 IPv6 addressing documents do not have any direct impact on Internet 138 infrastructure security. 140 7. References 141 7.1. Normative References 142 [RFC3849] Huston, G., Lord, A., and Smith, P., "IPv6 Address Prefix 143 Reserved for Documentation", RFC 3849, July 2004. 145 7.2. Informative References 146 [RFC4193] Hinden, R. and Haberman, B., "Unique Local IPv6 Unicast 147 Addresses", RFC 4193, October 2005. 149 Authors' Addresses 151 Owen DeLong 152 DeLong Consulting 154 EMail: owen@delong.com 156 Full Copyright Statement 158 Copyright (c) 2013 IETF Trust and the persons identified as the 159 document authors. All rights reserved. 161 This document is subject to BCP 78 and the IETF Trust's Legal 162 Provisions Relating to IETF Documents 163 (http://trustee.ietf.org/license-info) in effect on the date of 164 publication of this document. Please review these documents carefully, 165 as they describe your rights and restrictions with respect to this 166 document. Code Components extracted from this document must include 167 Simplified BSD License text as described in Section 4.e of the Trust 168 Legal Provisions and are provided without warranty as described in the 169 Simplified BSD License. 171 Acknowledgement 173 Funding for the RFC Editor function is currently provided by the 174 Internet Society.