[rfc-dist] RFC 3392 on Capabilities Advertisement with BGP-4
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Wed, 13 November 2002 20:45 UTC
From: rfc-editor@rfc-editor.org
Date: Wed, 13 Nov 2002 12:45:49 -0800
Subject: [rfc-dist] RFC 3392 on Capabilities Advertisement with BGP-4
Message-ID: <200211132045.gADKjnD15033@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3392 Title: Capabilities Advertisement with BGP-4 Author(s): R. Chandra, J. Scudder Status: Standards Track Date: November 2002 Mailbox: rchandra@redback.com, jgs@cisco.com Pages: 6 Characters: 9885 Obsoletes: 2842 I-D Tag: draft-ietf-idr-rfc2842bis-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3392.txt This document defines a new Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated. This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Draft 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021113124404.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3392 --OtherAccess Content-Type: Message/External-body; name="rfc3392.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021113124404.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3392 on Capabilities Advertisement… rfc-editor@rfc-editor.org