draft-ietf-bmwg-igp-dataplane-conv-term-10.txt   draft-ietf-bmwg-igp-dataplane-conv-term-11.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: September 2006 Expires in: November 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
Terminology for Benchmarking Terminology for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-term-10.txt> <draft-ietf-bmwg-igp-dataplane-conv-term-11.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 44 skipping to change at page 1, line 44
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 Internet Society (2006). Copyright (C) The Internet Society (2006).
ABSTRACT ABSTRACT
This document describes the terminology for benchmarking IGP This document describes the terminology for benchmarking IGP
Route Convergence as described in Applicability document [1] and Route Convergence as described in Applicability document [Po061] and
Methodology document [2]. The methodology and terminology are to Methodology document [Po062]. The methodology and terminology are to
be used for benchmarking Convergence Time and can be applied to be used for benchmarking Convergence Time 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 [Ca90] and OSPF [Mo98]. The data plane
is measured to obtain the convergence benchmarking metrics is measured to obtain the convergence benchmarking metrics
described in [2]. described in [Po062].
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 .........................................3 2. Existing definitions .........................................3
3. Term definitions..............................................3 3. Term definitions..............................................3
3.1 Convergence Event.........................................3 3.1 Convergence Event.........................................3
3.2 Route Convergence.........................................4 3.2 Route Convergence.........................................4
3.3 Network Convergence.......................................4 3.3 Network Convergence.......................................4
3.4 Full Convergence..........................................5 3.4 Full Convergence..........................................5
3.5 Convergence Packet Loss...................................5 3.5 Convergence Packet Loss...................................5
3.6 Convergence Event Instant.................................6 3.6 Convergence Event Instant.................................6
3.7 Convergence Recovery Instant..............................6 3.7 Convergence Recovery Instant..............................6
skipping to change at page 2, line 37 skipping to change at page 2, line 36
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. IANA Considerations...........................................13 4. IANA Considerations...........................................13
5. Security Considerations.......................................14 5. Security Considerations.......................................14
6. Acknowledgements..............................................14 6. Acknowledgements..............................................14
7. Normative References..........................................14 7. Normative References..........................................14
8. Author's Address..............................................14 8. Author's Address..............................................15
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 [Po061]. The methodology to be used for
this benchmarking is described in [2]. The methodology and this benchmarking is described in [Po062]. 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 [Ca90] and OSPF [Mo98]. 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
to introduce new terms required to complete execution of the IGP to introduce new terms required to complete execution of the IGP
Route Convergence Methodology [2]. These terms apply to IPv4 and Route Convergence Methodology [Po062]. These terms apply to IPv4 and
IPv6 traffic as well as IPv4 and IPv6 IGPs. IPv6 traffic as well as IPv4 and IPv6 IGPs.
An example of Route Convergence as observed and measured from the An example of Route Convergence as observed and measured from the
data plane is shown in Figure 1. The graph in Figure 1 shows data plane is shown in Figure 1. The graph in Figure 1 shows
Throughput 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 Offered Load to the ingress interface of
defined in the Term Definitions section. the DUT SHOULD equal the measured maximum Throughput [5,6] of the DUT
and the Forwarding Rate [Ma98] is measured at the egress interfaces
of the DUT. The components of the graph and the metrics are 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 ^ ^ ^ Forwarding Rate = ^ ^ ^ Offered Load =
Throughput--> ------\ Packet /--------------- Offered Load --> ------\ Packet /-------- <---Max Throughput
\ Loss /<----Convergence \ Loss /<----Convergence
Convergence------->\ / Event Transition Convergence------->\ / Event Transition
Recovery Transition \ / Recovery Transition \ /
\_____/<------Maximum Packet Loss \_____/<------Maximum Packet Loss
X-axis = Time X-axis = Time
Y-axis = Throughput 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.
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. The term Throughput is defined in RFC 2544. document. The term Throughput is defined in [Ba91] and [Ba99].
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 Device that results in a change in the egress interface of the Device
Under Test (DUT) for Under Test (DUT) for
routed packets. routed packets.
skipping to change at page 4, line 41 skipping to change at page 4, line 41
3.3 Network Convergence 3.3 Network Convergence
Definition: Definition:
The completion of updating of all routing tables, including the The completion of updating of all routing tables, including the
FIB, in all routers throughout the network. FIB, in all routers throughout the network.
Discussion: Discussion:
Network Convergence is bounded by the sum of Route Convergence Network Convergence is bounded by the sum of Route Convergence
for all routers in the network. Network Convergence can be for all routers in the network. Network Convergence can be
determined by recovery of the Throughput to equal the determined by recovery of the Throughput to equal the
offered load, with no Stale Forwarding, and no blenders[5][6]. offered load, with no Stale Forwarding, and no blenders[Ca01][Ci03].
Measurement Units: Measurement Units:
N/A N/A
Issues: Issues:
None None
See Also: See Also:
Route Convergence Route Convergence
Stale Forwarding Stale Forwarding
skipping to change at page 9, line 8 skipping to change at page 9, line 8
Ideally, the Convergence Event Transition and Convergence Ideally, the Convergence Event Transition and Convergence
Recovery Transition are instantaneous so that the Recovery Transition are instantaneous so that the
Rate-Derived Convergence Time = Loss-Derived Convergence Time. Rate-Derived Convergence Time = Loss-Derived Convergence Time.
However, router implementations are less than ideal. However, router implementations are less than ideal.
For these reasons the preferred reporting benchmark for IGP For these reasons the preferred reporting benchmark for IGP
Route Convergence is the Rate-Derived Convergence Time. Route Convergence is the Rate-Derived Convergence Time.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Guidelines for reporting Loss-Derived Convergence Time are Guidelines for reporting Loss-Derived Convergence Time are
provided in [2]. provided in [Po062].
Measurement Units: Measurement Units:
seconds/milliseconds seconds/milliseconds
Issues: Issues:
None None
See Also: See Also:
Route Convergence Route Convergence
Convergence Packet Loss Convergence Packet Loss
skipping to change at page 9, line 37 skipping to change at page 9, line 37
without additional packet loss. without additional packet loss.
Discussion: Discussion:
The purpose of the Sustained Forwarding Convergence Time is to The purpose of the Sustained Forwarding Convergence Time is to
produce Convergence benchmarks protected against fluctuation produce Convergence benchmarks protected against fluctuation
in Throughput after Full Convergence is observed. The in Throughput after Full Convergence is observed. The
Sustained Forwarding Convergence Time to be used is calculated Sustained Forwarding Convergence Time to be used is calculated
as shown in Equation 3. as shown in Equation 3.
(eq 3) (eq 3)
Sustained Forwarding Convergence Time = 5 packets/Offered Load Sustained Forwarding Convergence Time =
5*(Convergence Packet Loss/Offered Load)
units are packets/pps = sec units are packets/pps = sec
for which at least one packet per route in the FIB for all for which at least one packet per route in the FIB for all
routes in the FIB MUST be offered to the DUT per second. routes in the FIB MUST be offered to the DUT per second.
Measurement Units: Measurement Units:
seconds or milliseconds seconds or milliseconds
Issues: None Issues: None
skipping to change at page 10, line 33 skipping to change at page 10, line 33
See Also: See Also:
Convergence Event Convergence Event
Rate-Derived Convergence Time Rate-Derived Convergence Time
3.14 Packet Sampling Interval 3.14 Packet Sampling Interval
Definition: Definition:
The interval at which the tester (test equipment) polls to make The interval at which the tester (test equipment) polls to make
measurements for arriving packet flows. measurements for arriving packet flows.
Discussion: Discussion:
Metrics measured at the Packet Sampling Interval may include Metrics measured at the Packet Sampling Interval MUST include
Throughput and Convergence Packet Loss. Forwarding Rate and Convergence Packet Loss.
Measurement Units: Measurement Units:
seconds or milliseconds seconds or milliseconds
Issues: Issues:
Packet Sampling Interval can influence the Convergence Graph. Packet Sampling Interval can influence the Convergence Graph.
This is particularly true when implementations achieve Full This is particularly true when implementations achieve Full
Convergence in less than 1 second. The Convergence Event Convergence in less than 1 second. The Convergence Event
Transition and Convergence Recovery Transition can become Transition and Convergence Recovery Transition can become
exaggerated when the Packet Sampling Interval is too long. exaggerated when the Packet Sampling Interval is too long.
This will produce a larger than actual Rate-Derived This will produce a larger than actual Rate-Derived
Convergence Time. The recommended value for configuration Convergence Time. The recommended value for configuration
of the Packet Sampling Interval is provided in [2]. of the Packet Sampling Interval is provided in [Po062].
See Also: See Also:
Convergence Packet Loss Convergence Packet Loss
Convergence Event Transition Convergence Event Transition
Convergence Recovery Transition Convergence Recovery Transition
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.15 Local Interface 3.15 Local Interface
Definition: Definition:
An interface on the DUT. An interface on the DUT.
skipping to change at page 14, line 21 skipping to change at page 14, line 21
is not performed on devices or systems connected to production is not performed on devices or systems connected to production
networks. networks.
6. Acknowledgements 6. Acknowledgements
Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of
the BMWG for their contributions to this work. the BMWG for their contributions to this work.
7. References 7. References
7.1 Normative References 7.1 Normative References
[1] Poretsky, S., "Benchmarking Applicability for IGP Data Plane [Ba91]Bradner, S. "Benchmarking Terminology for Network
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-10, Interconnection Devices", RFC1242, July 1991.
work in progress, March 2006.
[2] Poretsky, S., "Benchmarking Methodology for IGP Data Plane [Ba99]Bradner, S. and McQuaid, J., "Benchmarking
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-10, Methodology for Network Interconnect Devices",
work in progress, March 2006. RFC 2544, March 1999.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [Ca90]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. [Ma98]Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, February 1998.
[Mo98]Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[Po061]Poretsky, S., "Benchmarking Applicability for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-11,
work in progress, May 2006.
[Po062]Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-11,
work in progress, May 2006.
7.2 Informative References 7.2 Informative References
[5] S. Casner, C. Alaettinoglu, and C. Kuan, "A Fine-Grained View [Ca01]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 [Ci03]L. Ciavattone, A. Morton, and G. Ramachandran, "Standardized
Active Measurements on a Tier 1 IP Backbone", IEEE Active Measurements on a Tier 1 IP Backbone", IEEE
Communications Magazine, pp90-97, May 2003. Communications Magazine, pp90-97, May 2003.
IGP Data Plane Route Convergence
8. Author's Address 8. 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
EMail: sporetsky@reefpoint.com EMail: sporetsky@reefpoint.com
IGP Data Plane Route Convergence
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
1194 North Mathilda Ave 1194 North Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
Phone: + 1 314 378 2571 Phone: + 1 314 378 2571
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
skipping to change at page 15, line 31 skipping to change at page 16, line 5
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IGP Data Plane Route Convergence
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
 End of changes. 29 change blocks. 
37 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/