RFC 3065 on Autonomous System Confederations for BGP

RFC Editor <rfc-ed@ISI.EDU> Fri, 09 February 2001 01:19 UTC

Message-Id: <200102090030.QAA07182@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3065 on Autonomous System Confederations for BGP
Cc: rfc-ed@ISI.EDU, idr@merit.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 08 Feb 2001 16:30:38 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 3065

        Title:	    Autonomous System Confederations for BGP
        Author(s):  P. Traina, D. McPherson, J. Scudder
        Status:     Standards Track
	Date:       February 2001
        Mailbox:    pst@juniper.net, danny@ambernetworks.com,
                    jgs@cisco.com 
        Pages:      11
        Characters: 20529
        Obsoletes:  1965

        I-D Tag:    draft-ietf-idr-bgp-confed-rfc1965bis-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3065.txt


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 which 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 "full mesh" 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 is a product of the Inter-Domain Routing Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3065.txt"><ftp://ftp.isi.edu/in-notes/rfc3065.txt>

RFC 3065 on Autonomous System Confederations for … RFC Editor