idnits 2.17.1 draft-weil-shared-transition-space-request-04.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: ---------------------------------------------------------------------------- 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 (August 30, 2011) is 4622 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-03) exists of draft-bdgks-arin-shared-transition-space-01 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Weil 3 Internet-Draft Time Warner Cable 4 Intended status: Informational V. Kuarsingh 5 Expires: March 2, 2012 Rogers Communications 6 C. Donley 7 CableLabs 8 C. Liljenstolpe 9 Telstra Corp 10 M. Azinger 11 Frontier Communications 12 August 30, 2011 14 IANA Reserved IPv4 Prefix for Shared Transition Space 15 draft-weil-shared-transition-space-request-04 17 Abstract 19 This document requests a reserved IANA IPv4 address allocation as 20 Shared Transition Space to support the deployment of IPv4 address 21 sharing technologies post IPv4 exhaustion 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on March 2, 2012. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 59 3. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 5 60 4. Shared Transition Space . . . . . . . . . . . . . . . . . . . 6 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 62 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 63 7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 64 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 10 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 67 1. Introduction 69 Many operators are currently implementing their IPv6 transition 70 plans. During the transition, continued support for heritage IPv4- 71 only devices will be required. In order to facilitate the deployment 72 of transition technologies to support such heritage IPv4-only devices 73 and services, Service Providers require IPv4 address space that is 74 separate from the range of IPv4 addresses used by subscribers. This 75 address space need not be unique to each provider, but should be 76 outside of [RFC1918] space. This document requests that an IPv4 /10 77 be reserved as Shared Transition Space solely to facilitate 78 deployment of IPv6 transition/IPv4 coexistence technologies. 80 2. Requirements Language 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in RFC 2119 [RFC2119]. 86 3. Applicability 88 The Internet community is rapidly consuming the remaining supply of 89 unallocated IPv4 addresses. During the transition period to IPv6, it 90 is imperative that Service Providers maintain IPv4 service for 91 devices and networks that are currently incapable of upgrading to 92 IPv6. 94 The applicability of and justification for Shared Transition Space is 95 described in [I-D.bdgks-arin-shared-transition-space]. 97 4. Shared Transition Space 99 This document proposes the assignment of a /10 as Shared Transition 100 Space. Shared Transition Space is IPv4 address space reserved for 101 Infrastructure Provider use with the purpose of facilitating IPv6 102 transition and IPv4 coexistence deployment. The requested block 103 SHOULD NOT be utilized for any purpose other than as "inside" 104 addresses in a carrier NAT environment (e.g., between the CGN and 105 customer CPE devices) or for other IPv4 to IPv6 transition 106 infrastructure. Network equipment manufacturers MUST NOT use the 107 assigned block in default or example device configurations. 109 Because Shared Transition addresses have no meaning outside of the 110 Infrastructure Provider, routing information about shared transition 111 space networks MUST NOT be propagated on interdomain links, and 112 packets with shared transition source or destination addresses SHOULD 113 NOT be forwarded across such links. Internet service providers 114 SHOULD filter out routing information about shared transition space 115 networks on ingress links. 117 5. Security Considerations 119 This memo does not define any protocol, and raises no security 120 issues. Any addresses allocated as Shared Transition Space would not 121 be routable on the Internet. 123 6. IANA Considerations 125 IANA is asked to record the allocation of an IPv4 /10 for use as 126 Shared Transition Space. 128 7. Normative References 130 [I-D.bdgks-arin-shared-transition-space] 131 Barber, S., Delong, O., Grundemann, C., Kuarsingh, V., and 132 B. Schliesser, "ARIN Draft Policy 2011-5: Shared 133 Transition Space", 134 draft-bdgks-arin-shared-transition-space-01 (work in 135 progress), July 2011. 137 [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and 138 E. Lear, "Address Allocation for Private Internets", 139 BCP 5, RFC 1918, February 1996. 141 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 142 Requirement Levels", BCP 14, RFC 2119, March 1997. 144 Appendix A. Acknowledgments 146 Thanks to the following people (in alphabetical order) for their 147 guidance and feedback: 149 John Brzozowski 151 Isaiah Connell 153 Greg Davies 155 Kirk Erichsen 157 Wes George 159 Tony Hain 161 Philip Matthews 163 John Pomeroy 165 Barbara Stark 167 Jean-Francois Tremblay 169 Leo Vegoda 171 Steven Wright 173 Ikuhei Yamagata 175 Authors' Addresses 177 Jason Weil 178 Time Warner Cable 179 13820 Sunrise Valley Drive 180 Herndon, VA 20171 181 USA 183 Email: jason.weil@twcable.com 185 Victor Kuarsingh 186 Rogers Communications 187 8200 Dixie Road 188 Brampton, ON L6T 0C1 189 Canada 191 Email: victor.kuarsingh@rci.rogers.com 193 Chris Donley 194 CableLabs 195 858 Coal Creek Circle 196 Louisville, CO 80027 197 USA 199 Email: c.donley@cablelabs.com 201 Christopher Liljenstolpe 202 Telstra Corp 203 7/242 Exhibition Street 204 Melbourne, VIC 316 205 Australia 207 Phone: +61 3 8647 6389 208 Email: cdl@asgaard.org 210 Marla Azinger 211 Frontier Communications 212 Vancouver, WA 213 USA 215 Phone: +1.360.513.2293 216 Email: marla.azinger@frontiercorp.com