References
For more information about the BGP protocol, consult the following resources:
- Address Prefix Based Outbound Route Filter for BGP-4—draft-chen-bgp-prefix-orf-07.txt (March 2004 expiration)
- BGP Extended Communities Attribute—draft-ietf-idr-bgp-ext-communities-07.txt (February 2004 expiration)
- BGP/MPLS IP VPNs—draft-ietf-l3vpn-rfc2547bis-03.txt (April 2005 expiration)
- BGP support for four-octet AS number space—draft-ietf-idr-as4bytes-08.txt (February 2004 expiration)
- Connecting IPv6 Islands across IPv4 Clouds with BGP—draft-ietf-ngtrans-bgp-tunnel-04.txt (July 2002 expiration)
- Cooperative Route Filtering Capability for BGP-4—draft-ietf-idr-route-filter-09.txt (February 2003 expiration)
- Dynamic Capability for BGP-4—draft-ietf-idr-dynamic-cap-04.txt (February 2004 expiration)
- JUNOSe Release Notes, Appendix A, System Maximums—Refer to the Release Notes corresponding to your software release for information about maximum values.
- Graceful Restart Mechanism for BGP—draft-ietf-idr-restart-10.txt (March 2004 expiration)
- RFC 1657—Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 (July 1997)
- RFC 1745—BGP4/IDRP for IP—OSPF Interaction (December 1994)
- RFC 1771—A Border Gateway Protocol 4 (BGP-4) (March 1995)
- RFC 1772—Application of the Border Gateway Protocol in the Internet (March 1995)
- RFC 1773—Experience with the BGP-4 protocol (March 1995)
- RFC 1774—BGP-4 Protocol Analysis (March 1995)
- RFC 1863—A BGP/IDRP Route Server alternative to a full mesh routing (October 1995)
- RFC 1930—Guidelines for creation, selection, and registration of an Autonomous System (AS) (March 1996)
- RFC 1965—Autonomous System Confederations for BGP (June 1996)
- RFC 1966—BGP Route Reflection An alternative to full mesh IBGP (June 1996)
- RFC 1997—BGP Communities Attribute (August 1996)
- RFC 1998—An Application of the BGP Community Attribute in Multi-home Routing (August 1996)
- RFC 2858—Multiprotocol Extensions for BGP-4 (June 2000)
- RFC 2270—Using a Dedicated AS for Sites Homed to a Single Provider (January 1998)
- 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 2547—BGP/MPLS VPNs (March 1999)
- RFC 2796—BGP Route Reflection—An Alternative to Full Mesh IBGP (April 2000)
- RFC 2842—Capabilities Advertisement with BGP-4 (May 2000)
- 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)
- 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.