•
RFC 2385—Protection of BGP Sessions via the TCP MD5 Signature Option (August
1998)
•
RFC 2439—BGP Route Flap Damping (November 1998)
•
RFC 2519—A Framework for Inter-Domain Route Aggregation (February 1999)
•
RFC 2545—Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
(March 1999)
•
RFC 2796—BGP Route Reflection—An Alternative to Full Mesh IBGP (April 2000)
•
RFC 3392—Capabilities Advertisement with BGP-4 (November 2002)
•
RFC 2858—Multiprotocol Extensions for BGP-4 (June 2000)
•
RFC 2918—Route Refresh Capability for BGP-4 (September 2000)
•
RFC 3032—MPLS Label Stack Encoding (January 2001)
•
RFC 3065—Autonomous System Confederations for BGP (February 2001)
•
RFC 3392—Capabilities Advertisement with BGP-4 (November 2002)
•
RFC 4271—A Border Gateway Protocol (BGP-4) (January 2006)
•
RFC 4364—BGP/MPLS IP Virtual Private Networks (VPNs) (February 2006)
•
RFC 4721—Graceful Restart Mechanism for BGP (January 2007)
•
RFC 4893—BGP Support for Four-octet AS Number Space (May 2007)
•
Subcodes for BGP Cease Notification Message—draft-ietf-idr-cease-subcode-05.txt
(March 2004 expiration)
NOTE: IETF drafts are valid for only 6 months from the date of issuance. They must be
considered as works in progress. Please refer to the IETF Web site at http://www.ietf.org
for the latest drafts.
Features
Some of the more important BGP features supported by the E Series router are the
following:
•
Access lists
•
Advertisement intervals
•
Aggregation
•
BGP/MPLS VPNs
•
Communities
•
Confederations
•
EBGP multihop
•
IBGP single hop
Copyright © 2010, Juniper Networks, Inc.16
JunosE 11.2.x BGP and MPLS Configuration Guide