draft-ietf-bmwg-igp-dataplane-conv-app-02.txt   draft-ietf-bmwg-igp-dataplane-conv-app-03.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: July 2004 Expires in: January 2005
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
January 2004 July 2004
Benchmarking Applicability for Benchmarking Applicability for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-02.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-03.txt>
Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668.
Status of this Memo Status of this Memo
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 1, line 52 skipping to change at page 1, line 58
for benchmarking route convergence and can be applied to any for benchmarking route convergence and can be applied to any
link-state IGP such as ISIS [3] and OSPF [4]. The data plane is link-state IGP such as ISIS [3] and OSPF [4]. The data plane is
measured to obtain the convergence benchmarking metrics described measured to obtain the convergence benchmarking metrics described
in [1]. in [1].
Table of Contents Table of Contents
1. Introduction ...............................................2 1. Introduction ...............................................2
2. Existing definitions .......................................2 2. Existing definitions .......................................2
3. Factors for IGP Route Convergence Time......................2 3. Factors for IGP Route Convergence Time......................2
4. Network Events that Cause Route Convergence.................3 4. Network Events that Cause Route Convergence.................3
5. Use of Data Traffic for IGP Route Convergence Benchmarking..3 5. Use of Data Plane for IGP Route Convergence Benchmarking....3
6. Security Considerations.....................................4 6. Security Considerations.....................................4
7. Acknowledgements............................................4 7. Acknowledgements............................................4
8. References..................................................4 8. References..................................................4
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
9. Author's Address............................................5 9. Author's Address............................................5
10. Full Copyright Statement...................................5
1. Introduction 1. Introduction
IGP Convergence is a critical performance parameter. Customers IGP Convergence is a critical performance parameter. Customers
of Service Providers use packet loss due to IGP Convergence as a of Service Providers use packet loss due to IGP Convergence as a
key metric of their network service quality. Service Providers key metric of their network service quality. Service Providers
use IGP Convergence time as a key metric of router design and use IGP Convergence time as a key metric of router design and
architecture. Fast network convergence can be optimally achieved architecture. Fast network convergence can be optimally achieved
through deployment of fast converging routers. The fundamental through deployment of fast converging routers. The fundamental
basis by which network users and operators benchmark convergence basis by which network users and operators benchmark convergence
is packet loss, which is an externally observable event having is packet loss, which is an externally observable event having
skipping to change at page 4, line 35 skipping to change at page 4, line 35
7. Acknowledgements 7. Acknowledgements
Thanks to Curtis Villamizar for sharing so much of his Thanks to Curtis Villamizar for sharing so much of his
knowledge and experience through the years. Also, special knowledge and experience through the years. Also, special
thanks to the many Network Engineers and Network Architects thanks to the many Network Engineers and Network Architects
at the Service Providers who are always eager to discuss at the Service Providers who are always eager to discuss
Route Convergence. Route Convergence.
8. References 8. References
[1] Poretsky, S., "Benchmarking Methodology for IGP Data Plane [1] Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-01, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-03,
work in progress, October 2004. work in progress, July 2004.
[2] Poretsky, S., "Benchmarking Terminology for IGP Data Plane [2] Poretsky, S., "Benchmarking Terminology for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-01, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-03,
work in progress, October 2004. work in progress, July 2004.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments", RFC 1195, December 1990. Environments", RFC 1195, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[5] Villamizar, C., "Convergence and Restoration Techniques for [5] Villamizar, C., "Convergence and Restoration Techniques for
ISP Interior Routing", NANOG 25, October 2002. ISP Interior Routing", NANOG 25, October 2002.
[6] Katz, D., "Why are we Scared of SPF? IGP Scaling and [6] Katz, D., "Why are we Scared of SPF? IGP Scaling and
skipping to change at page 5, line 25 skipping to change at page 5, line 25
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 781 395 5090 Phone: + 1 781 395 5090
EMail: sporetsky@quarrytech.com EMail: sporetsky@quarrytech.com
10. Full Copyright Statement Intellectual Property Statement
Copyright (C) The Internet Society (1998). All Rights The IETF takes no position regarding the validity or scope of any Intel-
Reserved. lectual Property Rights or other rights that might be claimed to pertain
to the implementation or use of the technology described in this docu-
ment or the extent to which any license under such rights might or might
not be available; nor does it represent that it has made any independent
effort to identify any such rights. Information on the procedures with
respect to rights in RFC documents can be found in BCP 78 and BCP 79.
This document and translations of it may be copied and Copies of IPR disclosures made to the IETF Secretariat and any
furnished to others, and derivative works that comment on or assurances of licenses to be made available, or the result of an attempt
otherwise explain it or assist in its implementation may be made to obtain a general license or permission for the use of such
prepared, copied, published and distributed, in whole or in proprietary rights by implementers or users of this specification can be
part, without restriction of any kind, provided that the above obtained from the IETF on-line IPR repository at
copyright notice and this paragraph are included on all such http://www.ietf.org/ipr.
copies and derivative works. However, this document itself may
not be modified in any way, such as by removing the copyright
notice or references to the Internet Society or other Internet
organizations, except as needed for the purpose of developing
Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or
as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will The IETF invites any interested party to bring to its attention any
not be revoked by the Internet Society or its successors or copyrights, patents or patent applications, or other proprietary rights
assigns. This document and the information contained herein is that may cover technology that may be required to implement this stan-
provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE dard. Please address the information to the IETF at ietf-ipr@ietf.org.
INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY Disclaimer of Warranty
THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS This document and the information contained herein are provided on an
FOR A PARTICULAR PURPOSE. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA-
TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject to
the rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights.
 End of changes. 

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