<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-rfc3065bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc3065bis-06">
   <front>
      <title>Autonomous System Confederations for BGP</title>
      <author initials="P. S." surname="Traina" fullname="Paul S. Traina">
         <organization>Blissfully Retired</organization>
      </author>
      <author initials="J." surname="Scudder" fullname="John Scudder">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="D. R." surname="McPherson" fullname="Danny R. McPherson">
         <organization>Arbor Networks</organization>
      </author>
      <date month="February" day="2" year="2007" />
      <abstract>
	 <t>The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP speakers within a single autonomous system (AS) must be fully meshed. This represents a serious scaling problem that has been well documented in a number of proposals.

 This document describes an extension to BGP that may be used to create a confederation of autonomous systems that is represented as a single autonomous system to BGP peers external to the confederation, thereby removing the &quot;full mesh&quot; requirement. The intention of this extension is to aid in policy administration and reduce the management complexity of maintaining a large autonomous system.

 This document obsoletes RFC 3065. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-rfc3065bis-06" />
   
</reference>
