Professional Documents
Culture Documents
Traina
Request for Comments: 3065 Juniper Networks, Inc.
Obsoletes: 1965 D. McPherson
Category: Standards Track Amber Networks, Inc.
J. Scudder
Cisco Systems, Inc.
February 2001
Copyright Notice
Abstract
1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC 2119].
2. Introduction
AS Confederation
AS Confederation Identifier
Member-AS
Member-AS Number
4. Discussion
AS_PATH attribute. For example, one may choose to consider all BGP
speakers in a geographic region as a single entity. In addition to
potential improvements in routing policy control, if techniques such
as those presented here or in [5] are not employed, [1] requires BGP
speakers in the same autonomous system to establish a full mesh of
TCP connections among all speakers for the purpose of exchanging
exterior routing information. In autonomous systems the number of
intra-domain connections that need to be maintained by each border
router can become significant.
In [1], the path segment type is a 1-octet long field with the two
following values defined:
6. Operation
8. Compatability Considerations
9. Deployment Considerations
This extension to BGP does not change the underlying security issues
inherent in the existing BGP, such as those defined in [6].
11. Acknowledgments
Finally, we'd like to acknowledge Ravi Chandra and Yakov Rekhter for
providing constructive and valuable feedback on earlier versions of
this document.
12. References
[1] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 (BGP-4)", RFC
1771, March 1995.
[3] Haskin, D., "A BGP/IDRP Route Server alternative to a full mesh
routing", RFC 1863, October 1995.
[6] Heffernan, A., "Protection of BGP Sessions via the TCP MD5
Signature Option", RFC 2385, August 1998.
Paul Traina
Juniper Networks, Inc.
1194 N. Mathilda Ave.
Sunnyvale, CA 94089 USA
Danny McPherson
Amber Networks, Inc.
48664 Milmont Drive
Fremont, CA 94538
Phone: +1 510.687.5226
EMail: danny@ambernetworks.com
John G. Scudder
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134
Phone: +1 734.669.8800
EMail: jgs@cisco.com
The most notable change from [1] is that of reversing the values
AS_CONFED_SEQUENCE(4) and AS_CONFED_SET(3) to those defined in
section "AS_CONFED Segment Type Extension". The reasoning for this
is that in the initial implementation, which was already widely
deployed, they were implemented backwards from [4], and as such,
subsequent implementations implemented them backwards as well. In
order to foster interoperability and compliance with deployed
implementations, they've therefore been changed here as well.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
Acknowledgement