One document matched: draft-ietf-idr-as-private-reservation-03.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="no"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc submissionType="IETF" category="bcp" docName="draft-ietf-idr-as-private-reservation-03" ipr="trust200902" updates="1930">

  <front>
    <title abbrev="Private Use AS Reservation">Autonomous System (AS) Reservation for Private Use</title>
    <author fullname="Jon Mitchell" initials="J.M." surname="Mitchell">
      <organization>Microsoft Corporation</organization>
      <address>
        <postal>
          <street>1 Microsoft Way</street>
          <city>Redmond</city>
          <region>WA</region>
          <code>98052</code>
          <country>USA</country>
        </postal>
        <email>Jon.Mitchell@microsoft.com</email>
      </address>
    </author>
    <date year="2013" />
    <area>Routing</area>
    <keyword>Internet Draft</keyword>
    <abstract>
	    <t>This document describes the reservation of Autonomous System numbers (ASNs) that are for Private Use only and MUST NOT be advertised to the Internet, known as Private Use ASNs.  This document enlarges the total space available for Private Use ASNs by documenting the reservation of a second, larger range and updates RFC 1930 by replacing Section 10.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
	    <t>The original IANA reservation of Autonomous System Numbers (ASNs) for Private Use was a block of 1023 ASNs.  This was also documented by IETF in Section 10 of <xref target="RFC1930" />.  Since the time when that range was reserved, BGP has seen much wider deployment in service provider, enterprise, and datacenter networks.  The places in these networks where Private Use ASNs are in use include networks that are attached to the Internet, utilizing implementation specific features to remove them upon advertisement to Internet peers, and networks that are not attached to the Internet.</t>
	    <t>The limited size of the current range of Private Use ASNs has led to the re-use of the same ASN within a single organization, requiring the use of a number of implementation specific features that manipulate the AS_PATH or remove AS_PATH based loop prevention described in Section 9 of <xref target="RFC4271" />.  These workarounds have increased the operational complexity of the networks since the implementations of these functions vary and are not defined in existing BGP standards.</t>
	    <t>Since the introduction of BGP Support for Four-octet AS Number Space <xref target="RFC6793" />, the total size of the ASN space has increased dramatically, and a larger subset of the space should be available to network operators to deploy in Private Use cases.  The existing range of Private Use ASNs is widely deployed and the ability to renumber this resource in existing networks cannot be coordinated given these ASNs by definition are not registered.  Therefore this documents the existing Private Use ASN reservation, while also introducing a second, larger range that can also be utilized.</t>
    </section>
     <section title="Requirements Language">
       <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119">RFC 2119</xref>.</t>
     </section>
    <section anchor="addr" title="Private Use ASNs">
	    <t>To allow the continued growth of usage of the BGP protocol in networks that utilize Private Use ASNs, two ranges of ASNs are reserved by this document in <xref target="IANA" />.  The first which was previously defined in <xref target="RFC1930" /> out of the original 16-bit Autonomous System range and a second, larger range out of the higher part of the Four-Octet AS Number Space <xref target="RFC6793" />.</t>
    </section>
    <section anchor="ops" title="Operational Considerations">
	    <t>If Private Use ASNs are used and prefixes are originated from these ASNs which are destined to the Internet, Private Use ASNs MUST be removed from the AS_PATH before being advertised to the global Internet.  Operators are cautioned to ensure any implementation specific features that recognize Private Use ASNs have been updated to recognize both ranges prior to making use of the newer, numerically higher range of Private Use ASNs.  Some existing implementations that remove Private Use ASNs from the AS_PATH may fail to remove Private Use ASNs if the AS_PATH contains a mixture of Private Use and Non-Private Use ASNs.  If such implementations have not been updated to recognize the new range of ASNs in this document and a mix of old and new range Private Use ASNs exist in the path, these implementations may cease to remove any Private Use ASNs from the AS_PATH.  Normal AS_PATH filtering may be used to prevent prefixes originating from Private Use ASNs from being advertised to the global Internet.  Using AS_PATH filtering to filter the new range of Private Use ASNs on a network may also mitigate the leaking of Private Use ASNs to the global Internet in certain cases. These cases include the case where a network is reliant on AS_PATH manipulation features that have not been updated to recognize the new range as described above.</t>
    </section>
    <section anchor="Acknowledgements" title="Acknowledgements">
	   <t>The author would like to acknowledge Christopher Morrow, Jason Schiller, and John Scudder for their advice on how to pursue this change.  The author would also like to thank Brian Dickson, David Farmer, Jeffrey Haas, Nick Hilliard, Warren Kumari, and Jeff Wheeler for their comments and suggestions.</t>
   </section>
   <section anchor="IANA" title="IANA Considerations">
	   <t>[Note to IANA, NOT for publication: The IANA should update the "16-bit Autonomous System Numbers" registry to reference this RFC (when published) for the existing Private Use reservation.  Further, to maintain consistency from an operator standpoint, it is suggested that the end of the "32-bit Autonomous System Numbers" range be reserved for Private Use, and a size of 94,967,295 (value to replace TBD1 below) is suggested corresponding to the range of 4200000000 (value to replace TBD2 below) to 4294967294 (value to replace TBD3 below).]</t>
	   <t>IANA has reserved, for Private Use, a contiguous block of 1023 Autonomous System numbers from the "16-bit Autonomous System Numbers" registry, namely 64512 - 65534 inclusive.</t>
	   <t>IANA has also reserved, for Private Use, a contiguous block of TBD1 Autonomous System numbers from the "32-bit Autonomous System Numbers" registry, namely TBD2 - TBD3 inclusive.</t>
	   <t>These reservations have been documented in the IANA Autonomous System Numbers Registry <xref target="IANA.AS"/>.</t>
   </section>
   <section anchor="Security" title="Security Considerations">
	   <t>This document does not introduce any additional security concerns in regards to Private Use ASNs.</t>
   </section>
   </middle>

   <back>
	   <references title="Normative References">
		   <?rfc include="reference.RFC.2119.xml"?>
		   <?rfc include="reference.RFC.4271.xml"?>
		   <?rfc include="reference.RFC.6793.xml"?>
    </references>
    <references title="Informative References">
	    <reference anchor="IANA.AS" target="http://www.iana.org/assignments/as-numbers/">
		    <front>
			    <title>Autonomous System (AS) Numbers</title>
			    <author surname="IANA" fullname="IANA"><organization/></author>
			    <date month="February" year="2013"/>
		    </front>
	    </reference>
		   <?rfc include="reference.RFC.1930.xml"?>
    </references>
  </back>

</rfc>