draft-ietf-bmwg-igp-dataplane-conv-app-16.txt   draft-ietf-bmwg-igp-dataplane-conv-app-17.txt 
Network Working Group S. Poretsky Network Working Group S. Poretsky
Internet Draft Allot Communications Internet Draft Allot Communications
Intended Status: Informational October 15, 2008 Expires: September 08, 2009
Intended Status: Informational March 08, 2009
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-16.txt> <draft-ietf-bmwg-igp-dataplane-conv-app-17.txt>
Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
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 other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
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.
This Internet-Draft will expire on September 8, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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.
skipping to change at page 4, line 51 skipping to change at page 4, line 51
diverse traffic flows to destinations matching every route in diverse traffic flows to destinations matching every route in
the FIB so that the time it takes for the router to converge an the FIB so that the time it takes for the router to converge an
entire route table can be benchmarked. entire route table can be benchmarked.
6. IANA Considerations 6. IANA Considerations
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 affect the security of
of the Internet or of corporate networks as long as Internet or corporate networks as long as benchmarking is not
benchmarking is not performed on devices or systems performed on devices or systems connected to production networks.
connected to production networks. Security threats and how to counter these in SIP and the media
layer is discussed in RFC3261, RFC3550, and RFC3711 and various
other drafts. This document attempts to formalize a set of
common methodology for benchmarking IGP convergence performance
in a lab environment.
Link-State 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-16, work in draft-ietf-bmwg-igp-dataplane-conv-meth-17, work in
progress, October 2008. progress, March 2009.
[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-16, work in draft-ietf-bmwg-igp-dataplane-conv-term-17, work in
progress, October 2008. progress, March 2009.
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 6 skipping to change at page 6, line 6
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.
Link-State IGP Data Plane Route Convergence Link-State IGP Data Plane Route Convergence
10. Author's Address 10. Author's Address
Scott Poretsky Scott Poretsky
Allot Communications Allot Communications
67 South Bedford Street, Suite 400 67 South Bedford Street, Suite 400
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 508 309 2179 Phone: + 1 508 309 2179
Email: sporetsky@allot.com Email: sporetsky@allot.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
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, THE
IETF TRUST 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
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 12 change blocks. 
20 lines changed or deleted 30 lines changed or added

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