draft-ietf-idr-rfc2842bis

Last Version:	draft-ietf-idr-rfc2842bis-02.txt		Tracker Entry
Date:	03-Mar-2006
Disposition:	non-current
Previous Versions:	draft-ietf-idr-rfc2842bis-02.txt (diff)    - 29-Mar-2004
	draft-ietf-idr-rfc2842bis-02.txt (diff)    - 22-Nov-2002
	draft-ietf-idr-rfc2842bis-01.txt (diff)    - 06-May-2002
	draft-ietf-idr-rfc2842bis-00.txt (diff)    - 18-Apr-2002

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:    [email protected], [email protected]
        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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.