idnits 2.17.1 draft-ietf-idr-as-private-reservation-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: ---------------------------------------------------------------------------- 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 (Using the creation date from RFC1930, updated by this document, for RFC5378 checks: 1996-03-01) -- 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 (October 11, 2012) is 4205 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Mitchell 3 Internet-Draft Microsoft Corporation 4 Updates: 1930 (if approved) October 11, 2012 5 Intended status: Informational 6 Expires: April 14, 2013 8 Autonomous System (AS) Reservation for Private Use 9 draft-ietf-idr-as-private-reservation-00 11 Abstract 13 This document describes the reservation of Autonomous System numbers 14 (ASNs) that are for private use only and should not be advertised to 15 the Internet, known as private use ASNs. This document enlarges the 16 total space available for private use ASNs by documenting the 17 reservation of a second, larger range and updates RFC 1930. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 14, 2013. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 1. Introduction 53 The original IANA reservation of Autonomous System Numbers (ASNs) for 54 private use was a block of 1023 ASNs. This was also documented by 55 IETF in Section 10 of [RFC1930]. Since the time when that range was 56 reserved, BGP has seen much wider deployment in service provider, 57 enterprise and content provider networks. The places in these 58 networks where private use ASNs are in use include networks that are 59 attached to the Internet, utilizing implementation specific features 60 to remove them upon advertisement to Internet peers, and networks 61 that are not attached to the Internet. The displacement of Frame 62 Relay and ATM based VPNs by BGP/MPLS IP VPNs [RFC4364] has also 63 increased the deployment of BGP to a larger number of sites, 64 especially in networks with requirements for multi-homing or provider 65 redundancy. 67 The limited size of the current range of private use ASNs has led to 68 the re-use of private use ASNs within a single organization, 69 requiring the use of a number of implementation specific features 70 that manipulate the AS_PATH or remove AS_PATH based loop prevention 71 described in Section 9 of [RFC4271]. These workarounds have 72 increased the operational complexity of the networks since the 73 implementations of these functions vary and are not defined in 74 existing BGP standards. 76 Since the introduction of BGP Support for Four-octet AS Number Space 77 [I-D.ietf-idr-rfc4893bis], the total size of the ASN space has 78 increased dramatically, and a larger subset of the space should be 79 available to network operators to deploy in private use cases. The 80 existing range of private use ASNs is widely deployed and the ability 81 to renumber this resource in existing networks cannot be coordinated 82 given these ASNs by definition are not registered. Therefore this 83 documents the existing private use ASN reservation, while also 84 introducing a second, larger range that can also be utilized. 86 2. Private Use ASNs 88 To allow the continued growth of usage of the BGP protocol in 89 networks that utilize private ASNs, two ranges of ASNs are reserved 90 by this document in Section 5. The first which was previously 91 defined in [RFC1930] out of the original 16-bit Autonomous System 92 range and a second, larger range out of the higher part of the Four- 93 Octet AS Number Space [I-D.ietf-idr-rfc4893bis]. 95 3. Operational Considerations 97 If private use ASNs are used and prefixes are originated from these 98 private use ASNs which are destined to the Internet, private use ASNs 99 must be removed from the AS_PATH before being advertised to the 100 global Internet. Operators are cautioned to ensure any filters or 101 implementation specific features that recognize private use ASNs have 102 been updated to recognize both ranges prior to making use of the 103 newer, numerically higher range of private use ASNs. 105 4. Acknowledgements 107 The author would like to acknowledge Christopher Morrow and Jason 108 Schiller for their advice on how to pursue this change. The author 109 also thanks Brian Dickson, David Farmer, and Jeffrey Haas for their 110 comments and suggestions. 112 5. IANA Considerations 114 [Note to IANA, NOT for publication: The IANA should update the "16- 115 bit Autonomous System Numbers" registry to reference this RFC (when 116 published) for the existing private use reservation. Further, to 117 maintain consistency from an operator standpoint, it is suggested 118 that the end of the "32-bit Autonomous System Numbers" range be 119 reserved for Private Use, and a size of 16777215 (value to replace 120 TBD1 below) is suggested corresponding to the range of 4278190080 121 (value to replace TBD2 below) to 4294967294 (value to replace TBD3 122 below).] 124 IANA has reserved, for Private Use, a contiguous block of 1023 125 Autonomous System numbers from the "16-bit Autonomous System Numbers" 126 registry, namely 64512 - 65534 inclusive. 128 IANA has also reserved, for Private Use, a contiguous block of TBD1 129 Autonomous System numbers from the "32-bit Autonomous System Numbers" 130 registry, namely TBD2 - TBD3 inclusive. 132 These reservations have been documented in the IANA Autonomous System 133 Numbers Registry [IANA.AS]. 135 6. Security Considerations 137 This document does not introduce any additional security concerns in 138 regards to private use ASNs. 140 7. References 142 7.1. Normative References 144 [I-D.ietf-idr-rfc4893bis] 145 Vohra, Q. and E. Chen, "BGP Support for Four-octet AS 146 Number Space", draft-ietf-idr-rfc4893bis-07 (work in 147 progress), June 2012. 149 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 150 Protocol 4 (BGP-4)", RFC 4271, January 2006. 152 7.2. Informative References 154 [IANA.AS] IANA, "Autonomous System (AS) Numbers", October 2012, 155 . 157 [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, 158 selection, and registration of an Autonomous System (AS)", 159 BCP 6, RFC 1930, March 1996. 161 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 162 Networks (VPNs)", RFC 4364, February 2006. 164 Author's Address 166 Jon Mitchell 167 Microsoft Corporation 168 12012 Sunset Hills Road 169 Reston, VA 20190 170 USA 172 Email: Jon.Mitchell@microsoft.com