draft-ietf-idr-bgp-analysis-02.txt   draft-ietf-idr-bgp-analysis-03.txt 
INTERNET-DRAFT David Meyer INTERNET-DRAFT David Meyer
draft-ietf-idr-bgp-analysis-02.txt Keyur Patel draft-ietf-idr-bgp-analysis-03.txt Keyur Patel
Category Informational Category Informational
Expires: October 2003 April 2003 Expires: November 2003 May 2003
BGP-4 Protocol Analysis BGP-4 Protocol Analysis
<draft-ietf-idr-bgp-analysis-02.txt> <draft-ietf-idr-bgp-analysis-03.txt>
Status of this Document Status of this Document
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 3, line 22 skipping to change at page 3, line 22
3. BGP Capabilities . . . . . . . . . . . . . . . . . . . . . . . 7 3. BGP Capabilities . . . . . . . . . . . . . . . . . . . . . . . 7
4. BGP Persistent Peer Oscillations . . . . . . . . . . . . . . . 8 4. BGP Persistent Peer Oscillations . . . . . . . . . . . . . . . 8
5. BGP Performance characteristics and Scalability. . . . . . . . 8 5. BGP Performance characteristics and Scalability. . . . . . . . 8
5.1. Link bandwidth and CPU utilization. . . . . . . . . . . . . 8 5.1. Link bandwidth and CPU utilization. . . . . . . . . . . . . 8
5.1.1. CPU utilization. . . . . . . . . . . . . . . . . . . . . 9 5.1.1. CPU utilization. . . . . . . . . . . . . . . . . . . . . 9
5.1.2. Memory requirements. . . . . . . . . . . . . . . . . . . 11 5.1.2. Memory requirements. . . . . . . . . . . . . . . . . . . 11
6. BGP Policy Expressiveness and its Implications . . . . . . . . 12 6. BGP Policy Expressiveness and its Implications . . . . . . . . 12
6.1. Existence of Unique Stable Routings . . . . . . . . . . . . 13 6.1. Existence of Unique Stable Routings . . . . . . . . . . . . 13
6.2. Existence of Stable Routings. . . . . . . . . . . . . . . . 14 6.2. Existence of Stable Routings. . . . . . . . . . . . . . . . 14
7. Applicability. . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Applicability. . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 16 8. Intellectual Property. . . . . . . . . . . . . . . . . . . . . 16
9. Informative References . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 16
10. Author's Addresses. . . . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 17
11. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 18 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
12. References. . . . . . . . . . . . . . . . . . . . . . . . . . 17
12.1. Informative References . . . . . . . . . . . . . . . . . . 17
13. Author's Addresses. . . . . . . . . . . . . . . . . . . . . . 18
14. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
BGP-4 is an inter-autonomous system routing protocol designed for BGP-4 is an inter-autonomous system routing protocol designed for
TCP/IP internets. Version 1 of the BGP protocol was published in RFC TCP/IP internets. Version 1 of the BGP protocol was published in RFC
1105 [RFC1105]. Since then BGP versions 2, 3, and 4 have been 1105 [RFC1105]. Since then BGP versions 2, 3, and 4 have been
developed. Version 2 was documented in RFC 1163 [RFC1163]. Version 3 developed. Version 2 was documented in RFC 1163 [RFC1163]. Version 3
is documented in RFC 1267 [RFC1267]. Version 4 is documented in the is documented in RFC 1267 [RFC1267]. Version 4 is documented in the
[BGP4] (version 4 of BGP will hereafter be referred to as BGP). The [BGP4] (version 4 of BGP will hereafter be referred to as BGP). The
changes between versions are explained in Appendix A of [BGP4]. changes between versions are explained in Appendix A of [BGP4].
skipping to change at page 16, line 11 skipping to change at page 16, line 11
easy and flexible way to introduce new features within the protocol. easy and flexible way to introduce new features within the protocol.
Finally, since BGP was designed with flexibility and extensibility in Finally, since BGP was designed with flexibility and extensibility in
mind, new and/or evolving requirements can be addressed via existing mind, new and/or evolving requirements can be addressed via existing
mechanisms. mechanisms.
To summarize, BGP is well suitable as an inter-autonomous system To summarize, BGP is well suitable as an inter-autonomous system
routing protocol for the IPv4 Internet that is based on IP [RFC791] routing protocol for the IPv4 Internet that is based on IP [RFC791]
as the Internet Protocol and "hop-by-hop" routing paradigm. Finally, as the Internet Protocol and "hop-by-hop" routing paradigm. Finally,
BGP is equally applicable to IPv6 [RFC2460] internets. BGP is equally applicable to IPv6 [RFC2460] internets.
8. Acknowledgments 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
9. Acknowledgments
We would like to thank Paul Traina for authoring previous versions of We would like to thank Paul Traina for authoring previous versions of
this document. Tim Griffin and Randy Presuhn also provided many this document. Tim Griffin and Randy Presuhn also provided many
insightful comments on earlier versions of this document. insightful comments on earlier versions of this document.
9. Informative References 10. Security Considerations
This document presents an analysis of the BGP protocol and as such
presents no new security implications for BGP.
11. IANA Considerations
This document presents an analysis of the BGP protocol and hence
presents no new IANA considerations.
12. References
12.1. Informative References
[BGP4] Rekhter, Y., T. Li., and S. Hares, Editors, "A [BGP4] Rekhter, Y., T. Li., and S. Hares, Editors, "A
Border Gateway Protocol 4 (BGP-4)", Border Gateway Protocol 4 (BGP-4)",
draft-ietf-idr-bgp4-19.txt. Work in progress. draft-ietf-idr-bgp4-20.txt. Work in progress.
[RFC791] "INTERNET PROTOCOL", DARPA INTERNET PROGRAM [RFC791] "INTERNET PROTOCOL", DARPA INTERNET PROGRAM
PROTOCOL SPECIFICATION, RFC 791, September, PROTOCOL SPECIFICATION, RFC 791, September,
1981. 1981.
[RFC854] Postel, J. and J. Reynolds, "TELNET PROTOCOL [RFC854] Postel, J. and J. Reynolds, "TELNET PROTOCOL
SPECIFICATION", RFC 854, May, 1983. SPECIFICATION", RFC 854, May, 1983.
[RFC1105] Lougheed, K., and Y. Rekhter, "Border Gateway [RFC1105] Lougheed, K., and Y. Rekhter, "Border Gateway
Protocol BGP", RFC 1105, June 1989. Protocol BGP", RFC 1105, June 1989.
skipping to change at page 18, line 24 skipping to change at page 18, line 38
Advertisement with BGP-4", RFC 2842, May 2000. Advertisement with BGP-4", RFC 2842, May 2000.
[RFC3345] McPherson, D., Gill, V., Walton, D., and [RFC3345] McPherson, D., Gill, V., Walton, D., and
A. Retana, "Border Gateway Protocol (BGP) Persistent A. Retana, "Border Gateway Protocol (BGP) Persistent
Route Oscillation Condition", RFC 3345, Route Oscillation Condition", RFC 3345,
August, 2002. August, 2002.
[ROUTEVIEWS] Meyer, D., "The Route Views Project", [ROUTEVIEWS] Meyer, D., "The Route Views Project",
http://www.routeviews.org http://www.routeviews.org
10. Author's Addresses 13. Author's Addresses
David Meyer David Meyer
Email: dmm@maoz.com Email: dmm@maoz.com
Keyur Patel Keyur Patel
Cisco Systems Cisco Systems
Email: keyupate@cisco.com Email: keyupate@cisco.com
11. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

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