draft-ietf-bmwg-igp-dataplane-conv-app-05.txt   draft-ietf-bmwg-igp-dataplane-conv-app-06.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: October 2005 Expires in: December 2005
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
February 2005 June 2005
Considerations for Benchmarking Considerations for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-app-05.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-06.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, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, or applicable patent or other IPR claims of which he or she is aware
will be disclosed, and any of which I become aware will be disclosed, have been or will be disclosed, and any of which he or she becomes
in accordance with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups June also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and June be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." 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.
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. Normative References........................................4 8. Normative References........................................5
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 40 skipping to change at page 2, line 40
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
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 this "SHOULD", "SHOULD NOT", "RECOMMENDED", "JUNE", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, 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 [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 intent of standards track documents as clear as possible. While this
document uses these keywords, this document is not a standards track document uses these keywords, this document is not a standards track
document. 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],
skipping to change at page 4, line 40 skipping to change at page 4, line 40
Documents of this type do not directly effect the security of Documents of this type do not directly effect the security of
the Internet or of corporate networks as long as benchmarking the Internet or of corporate networks as long as benchmarking
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 benchmarking.
IGP Data Plane Route Convergence
8. Normative 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-06,
work in progress, February 2005. work in progress, June 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-06,
work in progress, February 2005. work in progress, June 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
[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, October 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, October 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. October 2002.
skipping to change at page 5, line 31 skipping to change at page 6, line 4
9. Author's Address 9. Author's Address
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 781 395 5090 Phone: + 1 781 395 5090
EMail: sporetsky@quarrytech.com EMail: sporetsky@quarrytech.com
IGP Data Plane Route Convergence
Intellectual Property Statement Full Copyright Statement
The IETF takes no position regarding the validity or scope of any Intel- Copyright (C) The Internet Society (2005).
lectual Property Rights or other rights that might be claimed to pertain
to the implementation or use of the technology described in this docu- This document is subject to the rights, licenses and restrictions
ment or the extent to which any license under such rights might or might contained in BCP 78, and except as set forth therein, the authors
not be available; nor does it represent that it has made any independent retain all their rights.
effort to identify any such rights. Information on the procedures with
respect to rights in RFC documents can be found in BCP 78 and BCP 79. This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an attempt assurances of licenses to be made available, or the result of an
made to obtain a general license or permission for the use of such attempt made to obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification can be such proprietary rights by implementers or users of this
obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
that may cover technology that may be required to implement this stan- rights that June cover technology that June be required to implement
dard. Please address the information to the IETF at ietf-ipr@ietf.org. this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Disclaimer of Warranty
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
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
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Acknowledgement
Copyright (C) The Internet Society (2005). This document is subject to Funding for the RFC Editor function is currently provided by the
the rights, licenses and restrictions contained in BCP 78, and except as Internet Society.
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/