To: Request-for-Comments-List:;
Subject: RFC1265, RFC1266 on BGP Protocol Analysis & Experience with the BGP Protocol 
Cc: jkrey@ISI.EDU
Reply-To: jkrey@ISI.EDU
Date: Fri, 25 Oct 91 17:39:57 PDT
From: "Joyce K. Reynolds" <jkrey@ISI.EDU>


New Request for Comments are now available from the Network
Information Center in the online library at NIC@NIC.DDN.MIL.


	RFC 1265:

        Title:      BGP Protocol Analysis    
	Author:     Y. Rekhter, Editor
	Mailbox:    yakov@watson.ibm.com
	Pages:      8
	Characters: 20,728
	Obsoletes/Updates: none

		pathname: rfc/rfc1265.txt


The purpose of this report is to document how the requirements for
advancing a routing protocol to Draft Standard have been satisfied by
the Border Gateway Protocol (BGP). This report summarizes the key
feature of BGP, and analyzes the protocol with respect to scaling and
performance. This is the first of two reports on the BGP protocol.
The BGP protocol has been developed by the BGP Working Group of the
Internet Engineering Task Force.  Please send comments to
iwg@rice.edu.

This memo provides information for the Internet community. It does not
specify an Internet standard. Distribution of this memo is unlimited.


        RFC 1266:

        Title:      Experience with the BGP Protocol
	Author:     Y. Rekhter, Editor
	Mailbox:    yakov@watson.ibm.com
	Pages:      9
	Characters: 21,938
	Obsoletes/Updates: none

		pathname: rfc/rfc1266.txt


The purpose of this memo is to document how the requirements for
advancing a routing protocol to Draft Standard have been satisfied by
Border Gateway Protocol (BGP). This report documents experience with
BGP.  This is the second of two reports on the BGP protocol.  As
required by the Internet Activities Board (IAB) and the Internet
Engineering Steering Group (IESG), the first report will present a
performance analysis of the BGP protocol.  The BGP protocol has been
developed by the BGP Working Group of the Internet Engineering Task
Force.  Please send comments to iwg@rice.edu.

This memo provides information for the Internet community.  It does
not specify an Internet standard. Distribution of this memo is
unlimited.

RFCs can also be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, or WUARCHIVE.WUSTL.EDU.

Instructions for retrieving RFCs may be found in the file
"in-notes/rfc-retrieval.txt" on VENERA.ISI.EDU.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.

Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.


Joyce K. Reynolds
USC/Information Sciences Institute


----- End Included Message -----