I-D ACTION:draft-ietf-idr-bgp4-stdreport1-02.txt

Internet-Drafts@CNRI.Reston.VA.US Wed, 15 May 1996 13:50 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17145; 15 May 96 9:50 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17141; 15 May 96 9:50 EDT
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa14969; 15 May 96 9:50 EDT
Received: (from majordom@localhost) by p-o.ans.net (8.7.5/8.7.3) id NAA28033 for bgp-outgoing; Wed, 15 May 1996 13:39:30 GMT
X-Authentication-Warning: p-o.ans.net: majordom set sender to bgp-owner using -f
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: bgp@ans.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Internet-Drafts@CNRI.Reston.VA.US
Subject: I-D ACTION:draft-ietf-idr-bgp4-stdreport1-02.txt
Date: Wed, 15 May 1996 09:39:06 -0400
Message-Id: <9605150939.aa16619@IETF.CNRI.Reston.VA.US>
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net

A Revised Internet-Draft is available from the on-line Internet-Drafts 
directories. This draft is a work item of the Inter-Domain Routing Working 
Group of the IETF.                                                         

       Title     : BGP-4 Requirement Satisfaction Report                   
       Author(s) : P. Traina
       Filename  : draft-ietf-idr-bgp4-stdreport1-02.txt
       Pages     : 3
       Date      : 05/14/1996

The purpose of this memo is to document how the requirements for advancing 
a routing protocol to Full Standard have been satisfied by Border Gateway 
Protocol version 4 (BGP-4) (and create needless busywork).  This report 
provides a roadmap to all information necessary to move BGP-4 to Standard. 
This is the first of two final reports on the BGP protocol.  As required by
the Internet Activities Board (IAB) and the Internet Engineering Steering 
Group (IESG), the second report will present additional knowledge and 
understanding gained in the time when the protocol was mada a Draft 
standard and when it was submitted for Standard.            
               
The remaining sections of this memo document how BGP satisfies General 
Requirements specified in Section 3.0, as well as Requirements for Standard
specified in Section 6.0 of the "Internet Routing Protocol Standardization 
Criteria" document [1].                                    

Please send comments to bgp@ans.net.                                                   

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
     "get draft-ietf-idr-bgp4-stdreport1-02.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-idr-bgp4-stdreport1-02.txt
 
Internet-Drafts directories are located at:	
	                                                
     o  Africa                                   
        Address:  ftp.is.co.za (196.4.160.8)	
	                                                
     o  Europe                                   
        Address:  nic.nordu.net (192.36.148.17)	
        Address:  ftp.nis.garr.it (193.205.245.10)
	                                                
     o  Pacific Rim                              
        Address:  munnari.oz.au (128.250.1.21)	
	                                                
     o  US East Coast                            
        Address:  ds.internic.net (198.49.45.10)	
	                                                
     o  US West Coast                            
        Address:  ftp.isi.edu (128.9.0.32)  	
	                                                
Internet-Drafts are also available by mail.	
	                                                
Send a message to:  mailserv@ds.internic.net. In the body type: 
     "FILE /internet-drafts/draft-ietf-idr-bgp4-stdreport1-02.txt".
							
NOTE: The mail server at ds.internic.net can return the document in
      MIME-encoded form by using the "mpack" utility.  To use this
      feature, insert the command "ENCODING mime" before the "FILE"
      command.  To decode the response(s), you will need "munpack" or
      a MIME-compliant mail reader.  Different MIME-compliant mail readers
      exhibit different behavior, especially when dealing with
      "multipart" MIME messages (i.e., documents which have been split
      up into multiple messages), so check your local documentation on
      how to manipulate these messages.
							
For questions, please mail to Internet-Drafts@cnri.reston.va.us.
							

Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version
of the Internet-Draft.
ftp://ds.internic.net/internet-drafts/draft-ietf-idr-bgp4-stdreport1-02.txt"><ftp://ds.internic.net/internet-drafts/draft-ietf-idr-bgp4-stdreport1-02.txt>