draft-ietf-bmwg-igp-dataplane-conv-app-11.txt   draft-ietf-bmwg-igp-dataplane-conv-app-12.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: November 2006 Expires in: August 2007
Intended Status: Informational
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
February 2007
Considerations for Benchmarking Considerations for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-11.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-12.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 37 skipping to change at page 1, line 42
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 (2006). Copyright (C) The IETF Trust (2007).
ABSTRACT ABSTRACT
This document provides considerations for IGP Route Convergence This document discusses considerations for benchmarking Interior
benchmarking methodology [1] and IGP Route Convergence benchmarking Gateway Protocol (IGP) Route Convergence for any link-state IGP, such
terminology [2]. The methodology and terminology are to be used as Intermediate System-Intermediate System (ISIS) and Open-Shorted
for benchmarking route convergence and can be applied to any Path first (OSPF). A companion methodology document is to
link-state IGP such as ISIS [3] and OSPF [4]. The data plane is be used for benchmarking IGP convergence time through externally
measured to obtain the convergence benchmarking metrics described observable (black box) data plane measurements. A companion
in [1]. terminology document is to be referenced to support the benchmarking.
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
Convergence Time 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 convergence packet loss [Po07t] due to
key metric of their network service quality. Service Providers Interior Gateway Protocol (IGP) Convergence as a key metric of
use IGP Convergence time as a key metric of router design and their network service quality. Service Providers use IGP
architecture. Fast network convergence can be optimally achieved Convergence time as a key metric of router design and architecture
through deployment of fast converging routers. The fundamental for any IGP such as Intermediate System - Intermediate System
basis by which network users and operators benchmark convergence (ISIS) [Ca90] and Open-Shorted Path first (OSPF) [Mo98]. Fast
is packet loss, which is an externally observable event having network convergence can be optimally achieved through deployment
direct impact on their application performance. of fast converging routers. The fundamental basis by which network
users and operators benchmark convergence is packet loss, which is
an externally observable event having 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
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 [Po07m] and [Po07t]. This document describes all of the factors
influence a convergence measurement and how a purely black box test that influence a convergence measurement and how a purely black box
can be designed to account for all of these factors. This enables test can be designed to account for all of these factors. This
accurate benchmarking and evaluation for route convergence time. enables accurate benchmarking and evaluation for route convergence
time.
2. Existing definitions 2. Existing definitions
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 document are to be interpreted as described in BCP 14, RFC this document are to be interpreted as described in BCP 14, RFC
2119. RFC 2119 defines the use of these key words to help make the 2119 [Br97]. RFC 2119 defines the use of these key words to help
intent of standards track documents as clear as possible. While make the intent of standards track documents as clear as possible.
this document uses these keywords, this document is not a standards While this document uses these keywords, this document is not a
track document. 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 [Vi02],
[7], [8] and [9], these categories are Event Detection, SPF [Ka02], [Fi02], [Al02] and [Al00], these categories are Event
Processing, IGP Advertisement, and FIB Update. These have Detection, Shortest Path First (SPF) Processing, IGP Advertisement,
numerous components that influence the convergence time. These and Forwarding Information Base (FIB) Update. These have numerous
are listed as follow: components that influence the convergence time. These are listed
as follow:
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
-Event Detection- -Event Detection-
SONET failure indication time Physical Layer failure indication time
PPP failure indication time Layer 2 failure indication time
IGP Hello Dead Interval IGP Hello Dead Interval
-SPF Processing- -SPF Processing-
SPF Delay Time SPF Delay Time
SPF Hold time SPF Hold time
SPF Execution time SPF Execution time
-IGP Advertisement- -IGP Advertisement-
LSA/LSP Flood Packet Pacing LSA/LSP Flood Packet Pacing
LSA/LSP Retransmission Packet Pacing LSA/LSP Retransmission Packet Pacing
skipping to change at page 4, line 14 skipping to change at page 4, line 14
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
5. Use of Data Plane for IGP Route Convergence Benchmarking 5. Use of Data Plane for IGP Route Convergence Benchmarking
Customers of service providers use packet loss as the metric to Customers of service providers use packet loss as the metric to
calculate convergence time. Packet loss is an externally calculate convergence time. Packet loss is an externally
observable event having direct impact on customers' application observable event having direct impact on customers' application
performance. For this reason it is important to develop a performance. For this reason it is important to develop a
standard router benchmarking methodology and terminology that is standard router benchmarking methodology and terminology that is
a Direct Measure of Quality (DMOQ) for measuring IGP convergence. a Direct Measure of Quality (DMOQ) for measuring IGP convergence.
Such a methodology uses the data plane as described in [1] and [2]. Such a methodology uses the data plane as described in [Po07m]
using the terminology provided in [Po07t].
An additional benefit of using packet loss for calculation of An additional benefit of using packet loss for calculation of
IGP Route Convergence time is that it enables black-box tests to IGP Route Convergence time is that it enables black-box tests to
be designed. Data traffic can be offered to the be designed. Data traffic can be offered to the
device under test (DUT), an emulated network event can be forced device under test (DUT), an emulated network event can be forced
to occur, and packet loss can be externally measured to calculate to occur, and packet loss can be externally measured to calculate
the convergence time. Knowledge of the DUT architecture and IGP the convergence time. Knowledge of the DUT architecture and IGP
implementation is not required. There is no need to rely on the implementation is not required. There is no need to rely on the
DUT to produce the test results. There is no need to build DUT to produce the test results. There is no need to build
intrusive test harnesses for the DUT. intrusive test harnesses for the DUT.
skipping to change at page 5, line 9 skipping to change at page 5, line 9
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. References 9. References
9.1 Normative References 9.1 Normative References
[1] Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-meth-11, work in progress,
May 2006.
[2] Poretsky, S., "Benchmarking Terminology for IGP Data Plane [Br97] Bradner, S., "Key words for use in RFCs to Indicate
Route Convergence", [Ca90] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP
draft-ietf-bmwg-igp-dataplane-conv-term-11, work in progress, and Dual Environments", RFC 1195, December 1990.
May 2006.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
Environments", RFC 1195, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [Po07m] Poretsky, S., "Benchmarking Methodology for IGP Data
Plane Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-meth-12, work in
progress, February 2007.
[Po07t] Poretsky, S., "Benchmarking Terminology for IGP Data
Plane Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-term-12, work in
progress, February 2007.
9.2 Informative References 9.2 Informative References
[5] Villamizar, C., "Convergence and Restoration Techniques for
ISP Interior Routing", NANOG 25, March 2002.
[6] Katz, D., "Why are we Scared of SPF? IGP Scaling and [Al00] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards
Stability", NANOG 25, March 2002. Millisecond IGP Convergence", NANOG 20, March 2000.
[7] Filsfils, C., "Deploying Tight-SLA Services on an Internet [Al02] Alaettinoglu, C. and Casner, S., "ISIS Routing on the
Backbone: ISIS Fast Convergence and Differentiated Services Qwest Backbone: a Recipe for Subsecond ISIS Convergence",
Design (tutorial)", NANOG 25, March 2002. NANOG 24, March 2002.
[8] Alaettinoglu, C. and Casner, S., "ISIS Routing on the Qwest [Fi02] Filsfils, C., "Deploying Tight-SLA Services on an
Backbone: a Recipe for Subsecond ISIS Convergence", NANOG 24, Internet Backbone: ISIS Fast Convergence and
Differentiated Services Design (tutorial)", NANOG 25,
March 2002. March 2002.
[9] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards [Ka02] Katz, D., "Why are we Scared of SPF? IGP Scaling and
Millisecond IGP Convergence", NANOG 20, March 2000. Stability", NANOG 25, March 2002.
[Vi02] Villamizar, C., "Convergence and Restoration Techniques
for ISP Interior Routing", NANOG 25, March 2002.
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 (2006). Copyright (C) The IETF Trust (2007).
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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 23 change blocks. 
65 lines changed or deleted 80 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/