draft-ietf-bmwg-igp-dataplane-conv-app-04.txt   draft-ietf-bmwg-igp-dataplane-conv-app-05.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: April 2005 Expires in: October 2005
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
October 2004 February 2005
Considerations for Benchmarking Considerations for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-04.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-05.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or 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, will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668. 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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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. Security Considerations.....................................4 6. Security Considerations.....................................4
7. Acknowledgements............................................4 7. Acknowledgements............................................4
8. References..................................................4 8. Normative References........................................4
9. Author's Address............................................5 9. Author's Address............................................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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
IGP Route Convergence is a Direct Measure of Quality (DMOQ) when IGP Route Convergence is a Direct Measure of Quality (DMOQ) when
benchmarking the data plane. For this reason it is important to benchmarking the data plane. For this reason it is important to
develop a standard router benchmarking methodology and terminology develop a standard router benchmarking methodology and terminology
for measuring IGP convergence that uses the data plane as described for measuring IGP convergence that uses the data plane as described
in [1] and [2]. This document describes all of the factors that in [1] and [2]. This document describes all of the factors that
influence a convergence measurement and how a purely black box test influence a convergence measurement and how a purely black box test
can be designed to account for all of these factors. This enables can be designed to account for all of these factors. This enables
accurate benchmarking and evaluation for route convergence time. accurate benchmarking and evaluation for route convergence time.
2. Existing definitions 2. Existing definitions
For the sake of clarity and continuity this RFC adopts the template
for definitions set out in Section 2 of RFC 1242. Definitions are
indexed and grouped together in sections for ease of reference.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
this document are to be interpreted as described in RFC 2119. document are to be interpreted as described in BCP 14, RFC 2119
[Br97]. RFC 2119 defines the use of these key words to help make the
intent of standards track documents as clear as possible. While this
document uses these keywords, this document is not a standards track
document.
3. Factors for IGP Route Convergence Time 3. Factors for IGP Route Convergence Time
There are four major categories of factors contributing to the There are four major categories of factors contributing to the
measured Router IGP Convergence Time. As discussed in [5], [6], measured Router IGP Convergence Time. As discussed in [5], [6],
[7], [8] and [9], these categories are Event Detection, SPF [7], [8] and [9], these categories are Event Detection, SPF
Processing, IGP Advertisement, and FIB Update. These have numerous Processing, IGP Advertisement, and FIB Update. These have numerous
components that influence the convergence time. These are listed components that influence the convergence time. These are listed
as follow: as follow:
skipping to change at page 4, line 42 skipping to change at page 4, line 42
is not performed on devices or systems connected to operating is not performed on devices or systems connected to operating
networks. networks.
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. 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-04, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-04,
work in progress, October 2004. work in progress, February 2005.
[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-04, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-04,
work in progress, October 2004. work in progress, February 2005.
[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.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
skipping to change at page 6, line 17 skipping to change at page 6, line 17
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 OR "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 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 INFORMA- 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 TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject to Copyright (C) The Internet Society (2005). This document is subject to
the rights, licenses and restrictions contained in BCP 78, and except as the rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights. 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/