draft-ietf-idr-rfc3065bis-04.txt   draft-ietf-idr-rfc3065bis-05.txt 
INTERNET-DRAFT Paul Traina INTERNET-DRAFT Paul Traina
Danny McPherson Danny McPherson
Arbor Networks, Inc. Arbor Networks, Inc.
John Scudder John Scudder
Cisco Systems, Inc. Cisco Systems, Inc.
Expires: October 2005 April 2005 Expires: April 2006 October 2005
Autonomous System Confederations for BGP Autonomous System Confederations for BGP
<draft-ietf-idr-rfc3065bis-04.txt> <draft-ietf-idr-rfc3065bis-05.txt>
Status of this Memo
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware have
author represents that any applicable patent or other IPR claims of been or will be disclosed, and any of which he or she becomes aware
which he or she is aware have been or will be disclosed, and any of will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as groups may also distribute working documents as Internet-Drafts.
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other documents
time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 28, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
The Border Gateway Protocol (BGP) is an inter-autonomous system The Border Gateway Protocol (BGP) is an inter-autonomous system
routing protocol designed for Transmission Control Protocol/Internet routing protocol designed for Transmission Control Protocol/Internet
Protocol (TCP/IP) networks. BGP requires that all BGP speakers Protocol (TCP/IP) networks. BGP requires that all BGP speakers
within a single autonomous system (AS) must be fully meshed. This within a single autonomous system (AS) must be fully meshed. This
skipping to change at page 13, line 12 skipping to change at page 13, line 12
providing constructive and valuable feedback on earlier versions of providing constructive and valuable feedback on earlier versions of
this specification. this specification.
10. References 10. References
10.1. Normative References 10.1. Normative References
[BGP-4] Rekhter, Y., Li, T., and Hares, S., "A Border Gateway [BGP-4] Rekhter, Y., Li, T., and Hares, S., "A Border Gateway
Protocol 4", Internet-Draft, "Work in Progress". Protocol 4", Internet-Draft, "Work in Progress".
[RFC 1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 1771, March 1995.
[RFC 1965] Traina, P. "Autonomous System Confederations for BGP", [RFC 1965] Traina, P. "Autonomous System Confederations for BGP",
RFC 1965, June 1996. RFC 1965, June 1996.
[RFC 3065] Traina, P., McPherson, D. and Scudder, J., "Autonomous [RFC 3065] Traina, P., McPherson, D. and Scudder, J., "Autonomous
System Confederations for BGP", RFC 3065, February 2001. System Confederations for BGP", RFC 3065, February 2001.
10.2. Informative References 10.2. Informative References
[ISO 10747] Kunzinger, C., Editor, "Inter-Domain Routing Protocol", [ISO 10747] Kunzinger, C., Editor, "Inter-Domain Routing Protocol",
ISO/IEC 10747, October 1993. ISO/IEC 10747, October 1993.
[RFC 1771] Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 1771, March 1995.
[RFC 1863] Haskin, D., "A BGP/IDRP Route Server alternative to a [RFC 1863] Haskin, D., "A BGP/IDRP Route Server alternative to a
full mesh routing", RFC 1863, October 1995. full mesh routing", RFC 1863, October 1995.
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC 2385] Heffernan, A., "Protection of BGP Sessions via the TCP [RFC 2385] Heffernan, A., "Protection of BGP Sessions via the TCP
MD5 Signature Option", RFC 2385, August 1998. MD5 Signature Option", RFC 2385, August 1998.
[RFC 2796] Bates, T., Chandra, R. and E. Chen, "BGP Route Reflection [RFC 2796] Bates, T., Chandra, R. and E. Chen, "BGP Route Reflection
 End of changes. 10 change blocks. 
24 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/