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

Internet-Drafts@ietf.org Tue, 16 September 2003 18:53 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01830 for <idr-archive@ietf.org>; Tue, 16 Sep 2003 14:53:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19zKxV-0007cp-00 for idr-archive@ietf.org; Tue, 16 Sep 2003 14:53:53 -0400
Received: from trapdoor.merit.edu ([198.108.1.26] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19zKxU-0007ca-00 for idr-archive@ietf.org; Tue, 16 Sep 2003 14:53:52 -0400
Received: by trapdoor.merit.edu (Postfix) id 245C3912CE; Tue, 16 Sep 2003 14:53:34 -0400 (EDT)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id E5D9B912D3; Tue, 16 Sep 2003 14:53:33 -0400 (EDT)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 9E3CF912CE for <idr@trapdoor.merit.edu>; Tue, 16 Sep 2003 14:53:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 5EFED5DDCB; Tue, 16 Sep 2003 14:53:30 -0400 (EDT)
Delivered-To: idr@merit.edu
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by segue.merit.edu (Postfix) with ESMTP id 3456D5DDB5 for <idr@merit.edu>; Tue, 16 Sep 2003 14:53:29 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01741; Tue, 16 Sep 2003 14:53:22 -0400 (EDT)
Message-Id: <200309161853.OAA01741@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: idr@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idr-bgp4-experience-protocol-02.txt
Date: Tue, 16 Sep 2003 14:53:22 -0400
Sender: owner-idr@merit.edu
Precedence: bulk

A New 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		: Experience with the BGP-4 Protocol
	Author(s)	: D. McPherson, K. Patel
	Filename	: draft-ietf-idr-bgp4-experience-protocol-02.txt
	Pages		: 20
	Date		: 2003-9-16
	
The purpose of this memo is to document how the requirements for
advancing a routing protocol from Draft Standard to full Standard
have been satisfied by Border Gateway Protocol version 4 (BGP-4).
This report satisfies the requirement for 'the second report', as
described in Section 6.0 of RFC 1264.  In order to fulfill the
requirement, this report augments RFC 1773 and describes additional
knowledge and understanding gained in the time between when the
protocol was made a Draft Standard and when it was submitted for
Standard.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-experience-protocol-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also 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-experience-protocol-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idr-bgp4-experience-protocol-02.txt".
	
NOTE:	The mail server at ietf.org 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.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-bgp4-experience-protocol-02.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-idr-bgp4-experience-protocol-02.txt>