draft-ietf-bmwg-igp-dataplane-conv-app-14.txt   draft-ietf-bmwg-igp-dataplane-conv-app-15.txt 
Network Working Group Network Working Group S. Poretsky
INTERNET-DRAFT Internet Draft NextPoint Networks
Intended Status: Informational Expires: August 2008
Intended Status: Informational February 25, 2008
Scott Poretsky
Reef Point Systems
November 2007
Considerations for Benchmarking Considerations for Benchmarking
Link-State IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-14.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-15.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 41 skipping to change at page 1, line 37
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 IETF Trust (2007). Copyright (C) The IETF Trust (2008).
ABSTRACT ABSTRACT
This document discusses considerations for benchmarking Interior This document discusses considerations for benchmarking Interior
Gateway Protocol (IGP) Route Convergence for any link-state IGP, such Gateway Protocol (IGP) Route Convergence for any link-state IGP, such
as Intermediate System-Intermediate System (ISIS) and Open-Shorted as Intermediate System-Intermediate System (ISIS) and Open-Shorted
Path first (OSPF). A companion methodology document is to Path first (OSPF). A companion methodology document is to
be used for benchmarking IGP convergence time through externally be used for benchmarking IGP convergence time through externally
observable (black box) data plane measurements. A companion observable (black box) data plane measurements. A companion
terminology document is to be referenced to support the benchmarking. terminology document is to be referenced to support the benchmarking.
IGP Data Plane Route Convergence Link-State 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....4 5. Use of Data Plane for IGP Route Convergence Benchmarking....4
6. IANA Considerations.........................................4 6. IANA Considerations.........................................4
7. Security Considerations.....................................4 7. Security Considerations.....................................4
8. Acknowledgements............................................5 8. Acknowledgements............................................5
skipping to change at page 3, line 5 skipping to change at page 3, line 5
standards 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 [Vi02], measured Router IGP Convergence Time. As discussed in [Vi02],
[Ka02], [Fi02], [Al02] and [Al00], these categories are Event [Ka02], [Fi02], [Al02] and [Al00], these categories are Event
Detection, Shortest Path First (SPF) Processing, IGP Advertisement, Detection, Shortest Path First (SPF) Processing, IGP Advertisement,
and Forwarding Information Base (FIB) Update. These have numerous and Forwarding Information Base (FIB) Update. These have numerous
components that influence the convergence time, as listed below: components that influence the convergence time, as listed below:
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
-Event Detection- -Event Detection-
Physical Layer failure/recovery indication time Physical Layer failure/recovery indication time
Layer 2 failure/recovery indication time Layer 2 failure/recovery 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
skipping to change at page 3, line 54 skipping to change at page 3, line 54
comparing routers from different vendors. comparing routers from different vendors.
4. Network Events that Cause Convergence 4. Network Events that Cause Convergence
There are different types of network events that can cause IGP There are different types of network events that can cause IGP
convergence. These network events are as follow: convergence. These network events are as follow:
* administrative link removal * administrative link removal
* unplanned link failure * unplanned link failure
* line card failure * line card failure
* route changes such as withdrawal, flap, next-hop change, * route changes such as withdrawal, flap, next-hop change,
and cost change. and cost change.
* session loss due to loss of peer or adjancency * session loss due to loss of peer or adjacency
* link recovery * link recovery
* link insertion * link insertion
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
When benchmarking a router it is important to measure convergence When benchmarking a router it is important to measure convergence
time for local and remote occurrence of these network events. time for local and remote occurrence of these network events.
The convergence time measured will vary whether the network event The convergence time measured will vary whether the network event
occurred locally or remotely due to varying combinations of occurred locally or remotely due to varying combinations of
factors listed in the previous sections. This behavior makes it factors listed in the previous sections. This behavior makes it
possible to design purely black-box tests that isolate possible to design purely black-box tests that isolate
measurements for each of the components of convergence time. measurements for each of the components of convergence time.
5. Use of Data Plane for IGP Route Convergence Benchmarking 5. Use of Data Plane for IGP Route Convergence Benchmarking
skipping to change at page 5, line 5 skipping to change at page 5, line 5
This document requires no IANA considerations. This document requires no IANA considerations.
7. Security Considerations 7. Security Considerations
Documents of this type do not directly effect the security Documents of this type do not directly effect the security
of the Internet or of corporate networks as long as of the Internet or of corporate networks as long as
benchmarking is not performed on devices or systems benchmarking is not performed on devices or systems
connected to production networks. connected to production networks.
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
8. Acknowledgements 8. Acknowledgements
Thanks to Curtis Villamizar for sharing so much of his knowledge Thanks to Curtis Villamizar for sharing so much of his knowledge
and experience through the years. Thanks to Ron Bonica, Al Morton, and experience through the years. Thanks to Ron Bonica, Al Morton,
David Ward, and the BMWG for their reviews and comments. David Ward, and the BMWG for their reviews and comments.
9. References 9. References
9.1 Normative References 9.1 Normative References
[Br97] Bradner, S., "Key words for use in RFCs to Indicate [Br97] Bradner, S., "Key words for use in RFCs to Indicate
[Ca90] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP [Ca90] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP
and Dual Environments", RFC 1195, December 1990. and Dual Environments", RFC 1195, December 1990.
[Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [Mo98] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[Po07m] Poretsky, S., "Benchmarking Methodology for [Po07m] Poretsky, S., "Benchmarking Methodology for
Link-State IGP Data Plane Route Convergence", Link-State IGP Data Plane Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-meth-14, work in draft-ietf-bmwg-igp-dataplane-conv-meth-15, work in
progress, November 2007. progress, February 2008.
[Po07t] Poretsky, S., "Benchmarking Terminology for [Po07t] Poretsky, S., "Benchmarking Terminology for
Link-State IGP Data Plane Route Convergence", Link-State IGP Data Plane Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-term-14, work in draft-ietf-bmwg-igp-dataplane-conv-term-15, work in
progress, November 2007. progress, February 2008.
9.2 Informative References 9.2 Informative References
[Al00] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards [Al00] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards
Millisecond IGP Convergence", NANOG 20, March 2000. Millisecond IGP Convergence", NANOG 20, March 2000.
[Al02] Alaettinoglu, C. and Casner, S., "ISIS Routing on the [Al02] Alaettinoglu, C. and Casner, S., "ISIS Routing on the
Qwest Backbone: a Recipe for Subsecond ISIS Convergence", Qwest Backbone: a Recipe for Subsecond ISIS Convergence",
NANOG 24, March 2002. NANOG 24, March 2002.
skipping to change at page 6, line 5 skipping to change at page 6, line 5
Internet Backbone: ISIS Fast Convergence and Internet Backbone: ISIS Fast Convergence and
Differentiated Services Design (tutorial)", NANOG 25, Differentiated Services Design (tutorial)", NANOG 25,
March 2002. March 2002.
[Ka02] Katz, D., "Why are we Scared of SPF? IGP Scaling and [Ka02] Katz, D., "Why are we Scared of SPF? IGP Scaling and
Stability", NANOG 25, March 2002. Stability", NANOG 25, March 2002.
[Vi02] Villamizar, C., "Convergence and Restoration Techniques [Vi02] Villamizar, C., "Convergence and Restoration Techniques
for ISP Interior Routing", NANOG 25, March 2002. for ISP Interior Routing", NANOG 25, March 2002.
IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
10. Author's Address 10. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems NextPoint Networks
3 Federal Street 3 Federal Street
Billerica, MA 01821 USA Billerica, MA 01821 USA
Phone: + 1 508 439 9008 Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com EMail: sporetsky@nextpointnetworks.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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 This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
 End of changes. 14 change blocks. 
24 lines changed or deleted 19 lines changed or added

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