draft-ietf-bmwg-igp-dataplane-conv-app-09.txt   draft-ietf-bmwg-igp-dataplane-conv-app-10.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: June 2006 Expires in: September 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
January 2006 March 2006
Considerations for Benchmarking Considerations for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-09.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-10.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 3, line 38 skipping to change at page 3, line 38
It is therefore necessary to design a convergence test that It is therefore necessary to design a convergence test that
considers all of these components, not just one or a few of these considers all of these components, not just one or a few of these
components. The additional benefit of designing a test for all components. The additional benefit of designing a test for all
components is that it enables black-box testing in which knowledge components is that it enables black-box testing in which knowledge
of the routers' internal implementations is not required. It is of the routers' internal implementations is not required. It is
then possible to make valid use of the convergence benchmarking then possible to make valid use of the convergence benchmarking
metrics when comparing routers from different vendors. metrics when 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 administrative link convergence. These network events are as follow:
removal, unplanned link failure, line card failure, and route * administrative link removal
changes such as withdrawal, flap, next-hop change, and cost * unplanned link failure
change. When benchmarking a router it is important to measure * line card failure
convergence time for local and remote occurrence of these network * route changes such as withdrawal, flap, next-hop change,
events. The convergence time measured will vary whether the and cost change.
network event occurred locally or remotely due to varying
combinations of factors listed in the previous sections. This When benchmarking a router it is important to measure convergence
behavior makes it possible to design purely black-box tests that time for local and remote occurrence of these network events.
isolate measurements for each of the components of convergence The convergence time measured will vary whether the network event
time. occurred locally or remotely due to varying combinations of
factors listed in the previous sections. This behavior makes it
possible to design purely black-box tests that isolate
measurements for each of the components of convergence time.
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 [1] and [2].
IGP Data Plane Route Convergence
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 11 skipping to change at page 5, line 11
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 [1] Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence", Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-meth-09, work in progress, draft-ietf-bmwg-igp-dataplane-conv-meth-10, work in progress,
January 2006. March 2006.
[2] Poretsky, S., "Benchmarking Terminology for IGP Data Plane [2] Poretsky, S., "Benchmarking Terminology for IGP Data Plane
Route Convergence", Route Convergence",
draft-ietf-bmwg-igp-dataplane-conv-term-09, work in progress, draft-ietf-bmwg-igp-dataplane-conv-term-10, work in progress,
January 2006. March 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 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, January 2002. ISP Interior Routing", NANOG 25, March 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, January 2002. Stability", NANOG 25, March 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, January 2002. Design (tutorial)", NANOG 25, March 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,
January 2002. March 2002.
[9] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards [9] Alaettinoglu, C., Jacobson, V., and Yu, H., "Towards
Millisecond IGP Convergence", NANOG 20, January 2000. Millisecond IGP Convergence", NANOG 20, March 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
 End of changes. 12 change blocks. 
25 lines changed or deleted 28 lines changed or added

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