Capabilities Advertisement with BGP-4
RFC 5492

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    idr mailing list <>, 
    idr chair <>
Subject: Protocol Action: 'Capabilities Advertisement with 
         BGP-4' to Draft Standard 

The IESG has approved the following document:

- 'Capabilities Advertisement with BGP-4 '
   <draft-ietf-idr-rfc3392bis-06.txt> as a Draft Standard

This document is the product of the Inter-Domain Routing Working Group. 

The IESG contact persons are David Ward and Ross Callon.

A URL of this Internet-Draft is:

Technical Summary

   This document defines an 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 obsoletes RFC 3392.

Working Group Summary

   There were no objections to this document within the IDR WG during
the IDR WG Last Call.

Document Quality

  There are multiple, interoperable implementations of this technology.


   Dave Ward

RFC-Editor Note

Please add this to the IANA Considerations section:

IANA is requested to create and maintain a registry for OPEN message
optional parameters called "BGP OPEN Optional Parameter Types". Optional
parameters are identified by the Parameter Type, which is a one-octet
unsigned integer. Values (0 reserved, 1-255) are to
be allocated according to the "IETF Review" policy as defined in

The registry should be populated with the two Parameter Type codes 
that are currently defined:

   o  Parameter Type 1: Authentication (deprecated).

   o  Parameter Type 2: Capabilities ([RFC3392bis])


See RFC-Editor note for instructions on the new registry.