draft-ietf-bmwg-igp-dataplane-conv-app-08.txt   draft-ietf-bmwg-igp-dataplane-conv-app-09.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: April 2006 Expires in: June 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
October 2005 January 2006
Considerations for Benchmarking Considerations for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-08.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-09.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 40 skipping to change at page 1, line 40
time. It is inappropriate to use Internet-Drafts as reference 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/ietf/1id-abstracts.txt.
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
ABSTRACT ABSTRACT
This draft provides considerations for IGP Route Convergence This document provides considerations for IGP Route Convergence
benchmarking methodology [1] and IGP Route Convergence benchmarking benchmarking methodology [1] and IGP Route Convergence benchmarking
terminology [2]. The methodology and terminology is to be used terminology [2]. The methodology and terminology are to be used
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].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
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 Plane for IGP Route Convergence Benchmarking....3 5. Use of Data Plane for IGP Route Convergence Benchmarking....3
6. IANA Considerations.........................................4 6. IANA Considerations.........................................4
7. Security Considerations.....................................4 7. Security Considerations.....................................4
8. Acknowledgements............................................4 8. Acknowledgements............................................4
9. Normative References........................................5 9. Normative References........................................5
10. Author's Address...........................................5 10. Author's Address...........................................5
1. Introduction 1. Introduction
IGP Convergence is a critical performance parameter. Customers Convergence Time 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
direct impact on their application performance. direct impact on their application performance.
IGP Route Convergence is a Direct Measure of Quality (DMOQ) when IGP Route Convergence is a Direct Measure of Quality (DMOQ) when
skipping to change at page 5, line 7 skipping to change at page 5, line 7
8. Acknowledgements 8. 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 benchmarking. Route Convergence benchmarking.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
9. Normative References 9. References
9.1 Normative 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-08, Route Convergence",
work in progress, October 2005. draft-ietf-bmwg-igp-dataplane-conv-meth-09, work in progress,
January 2006.
[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-08, Route Convergence",
work in progress, October 2005. draft-ietf-bmwg-igp-dataplane-conv-term-09, work in progress,
January 2006.
[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.
9.2 Informative References
[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, January 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
Stability", NANOG 25, October 2002. Stability", NANOG 25, January 2002.
[7] Filsfils, C., "Deploying Tight-SLA Services on an Internet [7] Filsfils, C., "Deploying Tight-SLA Services on an Internet
Backbone: ISIS Fast Convergence and Differentiated Services Backbone: ISIS Fast Convergence and Differentiated Services
Design (tutorial)", NANOG 25, October 2002. Design (tutorial)", NANOG 25, January 2002.
[8] Alaettinoglu, C. and Casner, S., "ISIS Routing on the Qwest [8] Alaettinoglu, C. and Casner, S., "ISIS Routing on the Qwest
Backbone: a Recipe for Subsecond ISIS Convergence", NANOG 24, Backbone: a Recipe for Subsecond ISIS Convergence", NANOG 24,
October 2002. January 2002.
[9] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards [9] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards
Millisecond IGP Convergence", NANOG 20, October 2000. Millisecond IGP Convergence", NANOG 20, January 2000.
10. Author's Address 10. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 508 439 9008 Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com EMail: sporetsky@reefpoint.com
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
 End of changes. 17 change blocks. 
18 lines changed or deleted 22 lines changed or added

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