draft-ietf-bmwg-igp-dataplane-conv-term-07.txt   draft-ietf-bmwg-igp-dataplane-conv-term-08.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: January 2006 Expires in: April 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
LightCore
July 2005 October 2005
Terminology for Benchmarking Terminology for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-term-07.txt> <draft-ietf-bmwg-igp-dataplane-conv-term-08.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
This document is an Internet-Draft and is in full conformance with
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 may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other and may be updated, replaced, or obsoleted by other documents at any
documents at any time. It is inappropriate to use Internet-Drafts time. It is inappropriate to use Internet-Drafts as reference
as reference material or to cite them other than as "work in 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.
Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved.
ABSTRACT ABSTRACT
This draft describes the terminology for benchmarking IGP Route This draft describes the terminology for benchmarking IGP Route
Convergence as described in Applicability document [1] and Convergence as described in Applicability document [1] and
Methodology document [2]. The methodology and terminology is to Methodology document [2]. The methodology and terminology is to
be used for benchmarking Route Convergence and can be applied to be used for benchmarking Route Convergence and can be applied to
any link-state IGP such as ISIS [3] and OSPF [4]. The data plane any link-state IGP such as ISIS [3] and OSPF [4]. The data plane
is measured to obtain the convergence benchmarking metrics is measured to obtain the convergence benchmarking metrics
described in [2]. described in [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
skipping to change at page 2, line 33 skipping to change at page 2, line 33
3.12 Sustained Forwarding Convergence Time....................9 3.12 Sustained Forwarding Convergence Time....................9
3.13 Restoration Convergence Time.............................9 3.13 Restoration Convergence Time.............................9
3.14 Packet Sampling Interval.................................10 3.14 Packet Sampling Interval.................................10
3.15 Local Interface..........................................11 3.15 Local Interface..........................................11
3.16 Neighbor Interface.......................................11 3.16 Neighbor Interface.......................................11
3.17 Remote Interface.........................................11 3.17 Remote Interface.........................................11
3.18 Preferred Egress Interface...............................12 3.18 Preferred Egress Interface...............................12
3.19 Next-Best Egress Interface...............................12 3.19 Next-Best Egress Interface...............................12
3.20 Stale Forwarding.........................................13 3.20 Stale Forwarding.........................................13
3.21 Nested Convergence Events................................13 3.21 Nested Convergence Events................................13
4. Security Considerations.......................................13 4. IANA Considerations...........................................13
5. Normative References..........................................14 5. Security Considerations.......................................14
6. Author's Address..............................................14 6. Normative References..........................................14
7. Author's Address..............................................14
1. Introduction 1. Introduction
This draft describes the terminology for benchmarking IGP Route This draft describes the terminology for benchmarking IGP Route
Convergence. The motivation and applicability for this Convergence. The motivation and applicability for this
benchmarking is provided in [1]. The methodology to be used for benchmarking is provided in [1]. The methodology to be used for
this benchmarking is described in [2]. The methodology and this benchmarking is described in [2]. The methodology and
terminology to be used for benchmarking Route Convergence can be terminology to be used for benchmarking Route Convergence can be
applied to any link-state IGP such as ISIS [3] and OSPF [4]. The applied to any link-state IGP such as ISIS [3] and OSPF [4]. The
data plane is measured to obtain black-box (externally observable) data plane is measured to obtain black-box (externally observable)
convergence benchmarking metrics. The purpose of this document is convergence benchmarking metrics. The purpose of this document is
skipping to change at page 3, line 11 skipping to change at page 3, line 11
Forwarding Rate versus Time. Time 0 on the X-axis is on the far Forwarding Rate versus Time. Time 0 on the X-axis is on the far
right of the graph. The components of the graph and metrics are right of the graph. The components of the graph and metrics are
defined in the Term Definitions section. defined in the Term Definitions section.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Convergence Convergence Convergence Convergence
Recovery Event Recovery Event
Instant Instant Time = 0sec Instant Instant Time = 0sec
Maximum ^ ^ ^ Maximum ^ ^ ^
Forwarding Rate--> ----\ Packet /--------------- Forwarding Rate--> ------\ Packet /---------------
\ Loss /<----Convergence \ Loss /<----Convergence
Convergence------->\ / Event Transition Convergence------->\ / Event Transition
Recovery Transition \ / Recovery Transition \ /
\_____/<------Packet Loss \_____/<------Maximum Packet Loss
X-axis = Time X-axis = Time
Y-axis = Forwarding Rate Y-axis = Forwarding Rate
Figure 1. Convergence Graph Figure 1. Convergence Graph
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", "MAY", 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 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. Term Definitions 3. Term Definitions
3.1 Convergence Event 3.1 Convergence Event
Definition: Definition:
The occurrence of a planned or unplanned action in the network The occurrence of a planned or unplanned action in the network
that results in a change in the egress interface of the DUT for that results in a change in the egress interface of the DUT for
skipping to change at page 5, line 16 skipping to change at page 5, line 16
3.4 Full Convergence 3.4 Full Convergence
Definition: Definition:
Route Convergence for an entire FIB. Route Convergence for an entire FIB.
Discussion: Discussion:
When benchmarking convergence it is useful to measure When benchmarking convergence it is useful to measure
the time to converge an entire FIB. For example, the time to converge an entire FIB. For example,
a Convergence Event can be produced for an OSPF table of a Convergence Event can be produced for an OSPF table of
5000 routes so that the time to converge routes 1 through 5000 routes so that the time to converge routes 1 through
5000 is measured. Full Convergence is externally observable 5000 is measured. Full Convergence is externally observable
from the data plane when the forwarding rate on the Next-Best from the data plane when the forwarding rate of the data
Egress Interface equals the offered load. plane traffic on the Next-Best Egress Interface equals the
offered load.
Measurement Units: Measurement Units:
N/A N/A
Issues: Issues:
None None
See Also: See Also:
Network Convergence Network Convergence
Route Convergence Route Convergence
skipping to change at page 9, line 26 skipping to change at page 9, line 26
See Also: See Also:
Route Convergence Route Convergence
Convergence Packet Loss Convergence Packet Loss
Rate-Derived Convergence Time Rate-Derived Convergence Time
Convergence Event Transition Convergence Event Transition
Convergence Recovery Transition Convergence Recovery Transition
3.12 Sustained Forwarding Convergence Time 3.12 Sustained Forwarding Convergence Time
Definition: Definition:
The amount of time for which Full Convergence is maintained without The amount of time for which Full Convergence is maintained
additional packet loss. without additional packet loss.
Discussion: Discussion:
The purpose of the Sustained Forwarding Convergence Time is to produce The purpose of the Sustained Forwarding Convergence Time is to
Convergence Time benchmarks protected against fluctuation in Forwarding produce Convergence Time benchmarks protected against fluctuation
Rate after Full Convergence is observed. The Sustained Forwarding in Forwarding Rate after Full Convergence is observed. The
Convergence Time to be used is calculated as shown in Equation 3. Sustained Forwarding Convergence Time to be used is calculated
as shown in Equation 3.
(eq 3) (eq 3)
Sustained Forwarding Convergence Time = Sustained Forwarding Convergence Time =
5 x (# routes in FIB) / (Offered Load) 5 x (# routes in FIB) / (Offered Load)
for which at least one packet per destination MUST be received at for which at least one packet per destination MUST be received
the DUT. at the DUT.
Measurement Units: Measurement Units:
seconds or milliseconds seconds or milliseconds
Issues: None Issues: None
See Also: See Also:
Full Convergence Full Convergence
Convergence Recovery Instant Convergence Recovery Instant
skipping to change at page 13, line 48 skipping to change at page 13, line 48
Measurement Units: Measurement Units:
N/A N/A
Issues: Issues:
None None
See Also: See Also:
Convergence Event Convergence Event
4. Security Considerations 4. IANA Considerations
This document requires no IANA considerations.
IGP Data Plane Route Convergence
5. Security Considerations
Documents of this type do not directly affect the security of Documents of this type do not directly affect the security of
Internet or corporate networks as long as benchmarking Internet or 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 production
networks. networks.
IGP Data Plane Route Convergence 6. Normative References
5. Normative References
[1] Poretsky, S., "Benchmarking Applicability for IGP Data Plane [1] Poretsky, S., "Benchmarking Applicability for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-07, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-08,
work in progress, July 2005. work in progress, October 2005.
[2] Poretsky, S., "Benchmarking Methodology for IGP Data Plane [2] Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-07, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-08,
work in progress, July 2005. work in progress, October 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] S. Casner, C. Alaettinoglu, and C. Kuan, "A Fine-Grained View [5] S. Casner, C. Alaettinoglu, and C. Kuan, "A Fine-Grained View
of High Performance Networking", NANOG 22, June 2001. of High Performance Networking", NANOG 22, June 2001.
[6] L. Ciavattone, A. Morton, and G. Ramachandran, "Standardized [6] L. Ciavattone, A. Morton, and G. Ramachandran, "Standardized
Active Measurements on a Tier 1 IP Backbone", IEEE Communications Active Measurements on a Tier 1 IP Backbone", IEEE
Magazine, pp90-97, may, 2003. Communications Magazine, pp90-97, May 2003.
6. Author's Address 7. 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 781 395 5090
EMail: sporetsky@quarrytech.com Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com
Brent Imhoff Brent Imhoff
USA USA
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.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-
ment 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.
IGP Data Plane Route Convergence 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 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 may cover technology that may 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. 33 change blocks. 
73 lines changed or deleted 86 lines changed or added

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