draft-ietf-bmwg-igp-dataplane-conv-meth-08.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-09.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: April 2006 Expires in: June 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
Juniper Networks
October 2005 January 2006
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-08.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-09.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 42 skipping to change at page 1, line 43
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2006).
ABSTRACT ABSTRACT
This draft describes the methodology for benchmarking IGP Route This dpcument describes the methodology for benchmarking IGP
Convergence as described in Applicability document [1] and Route Convergence as described in Applicability document [1] and
Terminology document [2]. The methodology and terminology are Terminology document [2]. The methodology and terminology are
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 terms to any link-state IGP such as ISIS [3] and OSPF [4]. The terms
used in the procedures provided within this document are used in the procedures provided within this document are
defined in [2]. defined in [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Table of Contents Table of Contents
1. Introduction ...............................................2 1. Introduction ...............................................2
skipping to change at page 2, line 28 skipping to change at page 2, line 28
4.1.3 Convergence Due to Remote Interface Failure..............8 4.1.3 Convergence Due to Remote Interface Failure..............8
4.2 Convergence Due to Layer 2 Session Failure.................9 4.2 Convergence Due to Layer 2 Session Failure.................9
4.3 Convergence Due to IGP Adjacency Failure...................10 4.3 Convergence Due to IGP Adjacency Failure...................10
4.4 Convergence Due to Route Withdrawal........................10 4.4 Convergence Due to Route Withdrawal........................10
4.5 Convergence Due to Cost Change.............................11 4.5 Convergence Due to Cost Change.............................11
4.6 Convergence Due to ECMP Member Interface Failure...........12 4.6 Convergence Due to ECMP Member Interface Failure...........12
4.7 Convergence Due to Parallel Link Interface Failure.........12 4.7 Convergence Due to Parallel Link Interface Failure.........12
5. IANA Considerations.........................................13 5. IANA Considerations.........................................13
6. Security Considerations.....................................13 6. Security Considerations.....................................13
7. Normative References........................................13 7. Normative References........................................13
8. Author's Address............................................13 8. Author's Address............................................14
1. Introduction 1. Introduction
This draft describes the methodology for benchmarking IGP Route This draft describes the methodology for benchmarking IGP Route
Convergence. The applicability of this testing is described in Convergence. The applicability of this testing is described in
[1] and the new terminology that it introduces is defined in [2]. [1] and the new terminology that it introduces is defined in [2].
Service Providers use IGP Convergence time as a key metric of Service Providers use IGP Convergence time as a key metric of
router design and architecture. Customers of Service Providers router design and architecture. Customers of Service Providers
observe convergence time by packet loss, so IGP Route Convergence observe convergence time by packet loss, so IGP Route Convergence
is considered a Direct Measure of Quality (DMOQ). The test cases is considered a Direct Measure of Quality (DMOQ). The test cases
in this document are black-box tests that emulate the network in this document are black-box tests that emulate the network
events that cause route convergence, as described in [1]. The events that cause route convergence, as described in [1]. The
black-box test designs benchmark the data plane accounting for black-box test designs benchmark the data plane and account for
all of the factors contributing to convergence time, as discussed all of the factors contributing to convergence time, as discussed
in [1]. The methodology (and terminology) for benchmarking route in [1]. The methodology (and terminology) for benchmarking route
convergence can be applied to any link-state IGP such as ISIS [3] convergence can be applied to any link-state IGP such as ISIS [3]
and OSPF [4]. These methodologies apply to IPv4 and IPv6 traffic and OSPF [4]. These methodologies apply to IPv4 and IPv6 traffic
as well as IPv4 and IPv6 IGPs. as well as IPv4 and IPv6 IGPs.
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 [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. The term Throughput is defined in RFC 2544.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Test Setup 3. Test Setup
3.1 Test Topologies 3.1 Test Topologies
Figure 1 shows the test topology to measure IGP Route Convergence due Figure 1 shows the test topology to measure IGP Route Convergence due
to local Convergence Events such as SONET Link Failure, Layer 2 to local Convergence Events such as SONET Link Failure, Layer 2
Session Failure, IGP Adjacency Failure, Route Withdrawal, and route Session Failure, IGP Adjacency Failure, Route Withdrawal, and route
cost change. These test cases discussed in section 4 provide route cost change. These test cases discussed in section 4 provide route
convergence times that account for the Event Detection time, SPF convergence times that account for the Event Detection time, SPF
skipping to change at page 5, line 9 skipping to change at page 5, line 9
3.2.2 BGP Configuration 3.2.2 BGP Configuration
The obtained results for IGP Route Convergence may vary if The obtained results for IGP Route Convergence may vary if
BGP routes are installed. It is recommended that the IGP BGP routes are installed. It is recommended that the IGP
Convergence times be benchmarked without BGP routes installed. Convergence times be benchmarked without BGP routes installed.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.3 IGP Route Scaling 3.2.3 IGP Route Scaling
The number of IGP routes will impact the measured IGP Route The number of IGP routes will impact the measured IGP Route
Convergence because convergence for the entire IGP route table is Convergence because convergence for the entire IGP route table
measured. For results similar to those that would be observed in is measured. To obtain results similar to those that would be
an operational network it is recommended that the number of observed in an operational network, it is recommended that the
installed routes closely approximate that for routers in the number of installed routes closely approximate that for routers
network. The number of areas (for OSPF) and levels (for ISIS) can in the network. The number of areas (for OSPF) and levels (for
impact the benchmark results. ISIS) can impact the benchmark results.
3.2.4 Timers 3.2.4 Timers
There are some timers that will impact the measured IGP Convergence There are some timers that will impact the measured IGP Convergence
time. The following timers should be configured to the minimum value time. The following timers should be configured to the minimum value
prior to beginning execution of the test cases: prior to beginning execution of the test cases:
Timer Recommended Value Timer Recommended Value
----- ----------------- ----- -----------------
Failure Indication Delay <10milliseconds Link Failure Indication Delay <10milliseconds
IGP Hello Timer 1 second IGP Hello Timer 1 second
IGP Dead-Interval 3 seconds IGP Dead-Interval 3 seconds
LSA Generation Delay 0 LSA Generation Delay 0
LSA Flood Packet Pacing 0 LSA Flood Packet Pacing 0
LSA Retransmission Packet Pacing 0 LSA Retransmission Packet Pacing 0
SPF Delay 0 SPF Delay 0
3.2.5 Convergence Time Metrics 3.2.5 Convergence Time Metrics
The recommended value for the Packet Sampling Interval [2] is The recommended value for the Packet Sampling Interval [2] is
100 milliseconds. Rate-Derived Convergence Time [2] is the 100 milliseconds. Rate-Derived Convergence Time [2] is the
preferred benchmark for IGP Route Convergence. This benchmark preferred benchmark for IGP Route Convergence. This benchmark
must always be reported when the Packet Sampling Interval [2] must always be reported when the Packet Sampling Interval [2]
<= 100 milliseconds. If the test equipment does not permit <= 100 milliseconds. If the test equipment does not permit
the Packet Sampling Interval to be set as low as 100 msec, the Packet Sampling Interval to be set as low as 100 msec,
then both the Rate-Derived Convergence Time and Loss-Derived then both the Rate-Derived Convergence Time and Loss-Derived
Convergence Time [2] must be reported. The Packet Sampling Convergence Time [2] must be reported. The Packet Sampling
Interval value MUST be the smallest measurable convergence Interval value MUST be reported as the smallest measurable
time. convergence time.
3.2.6 Interface Types 3.2.6 Interface Types
All test cases in this methodology document may be executed with All test cases in this methodology document may be executed with
any interface type. All interfaces MUST be the same media and any interface type. All interfaces MUST be the same media and
Throughout [5,6] for each test case. Media and protocols MUST Throughput [5,6] for each test case. Media and protocols MUST
be configured for minimum failure detection delay to minimize be configured for minimum failure detection delay to minimize
the contribution to the measured Convergence time. For example, the contribution to the measured Convergence time. For example,
configure SONET with minimum carrier-loss-delay or Bi-directional configure SONET with minimum carrier-loss-delay or Bi-directional
Forwarding Detection (BFD) [7]. Forwarding Detection (BFD).
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.7 Offered Load 3.2.7 Offered Load
The offered Load MUST be the Throughput of the device as defined The offered Load MUST be the Throughput of the device as defined
in [5] and benchmarked in [6] at a fixed packet size. The packet in [5] and benchmarked in [6] at a fixed packet size.
size is selectable and MUST be recorded. The Throughput MUST be Packet size is measured in bytes and includes the IP header and
measured at the Preferred Egress Interface and the Next-Best payload. The packet size is selectable and MUST be recorded.
Egress Interface. The duration of offered load MUST be greater The Throughput MUST be measured at the Preferred Egress Interface
than the convergence time. The destination addresses for the and the Next-Best Egress Interface. The duration of offered load
offered load MUST be distributed such that all routes are matched. MUST be greater than the convergence time. The destination
This enables Full Convergence [2] to be observed. addresses for the offered load MUST be distributed such that all
routes are matched. This enables Full Convergence [2] to be
observed.
3.3 Reporting Format 3.3 Reporting Format
For each test case, it is recommended that the following reporting For each test case, it is recommended that the following reporting
format be completed: format be completed:
Parameter Units Parameter Units
--------- ----- --------- -----
IGP (ISIS or OSPF) IGP (ISIS or OSPF)
Interface Type (GigE, POS, ATM, etc.) Interface Type (GigE, POS, ATM, etc.)
Packet Size offered to DUT bytes Packet Size offered to DUT bytes
skipping to change at page 7, line 16 skipping to change at page 7, line 16
4. Test Cases 4. Test Cases
4.1 Convergence Due to Link Failure 4.1 Convergence Due to Link Failure
4.1.1 Convergence Due to Local Interface Failure 4.1.1 Convergence Due to Local Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event at the DUT's Local Interface. failure event at the DUT's Local Interface.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of the [2] using the topology shown in Figure 1. Set the cost of
routes so that the Preferred Egress Interface is the preferred the routes so that the Preferred Egress Interface is the
next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove link on DUT's Local Interface [2] by performing an 4. Remove Preferred Egress link on DUT's Local Interface [2] by
administrative shutdown of the interface. performing an administrative shutdown of the interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the Next-Best Egress Interface. the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore link on DUT's Local Interface by administratively 7. Restore Preferred Egress link on DUT's Local Interface by
enabling the interface. administratively enabling the interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back link up event and converges all IGP routes and traffic back
to the Preferred Egress Interface. to the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
link failure indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
4.1.2 Convergence Due to Neighbor Interface Failure 4.1.2 Convergence Due to Neighbor Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event at the Tester's Neighbor Interface. failure event at the Tester's Neighbor Interface.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove link on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [2] connected to
DUT' s Preferred Egress Interface. DUT' s Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the Next-Best Egress Interface. the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore link on Tester's Neighbor Interface connected to 7. Restore link on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface. DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back to link up event and converges all IGP routes and traffic back
the Preferred Egress Interface. to the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
link failure indication, SPF delay, SPF Holdtime, SPF Execution link failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
4.1.3 Convergence Due to Remote Interface Failure 4.1.3 Convergence Due to Remote Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a Remote Interface To obtain the IGP Route Convergence due to a Remote Interface
Failure event. Failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to SUT on 1. Advertise matching IGP routes from Tester to SUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 2. Set the cost of the [2] using the topology shown in Figure 2. Set the cost of
routes so that the Preferred Egress Interface is the preferred the routes so that the Preferred Egress Interface is the
next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
3. Verify traffic is routed over Preferred Egress Interface. 3. Verify traffic is routed over Preferred Egress Interface.
4. Remove link on Tester's Neighbor Interface [2] connected to 4. Remove link on Tester's Neighbor Interface [2] connected to
SUT' s Preferred Egress Interface. SUT' s Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as SUT detects 5. Measure Rate-Derived Convergence Time [2] as SUT detects
the link down event and converges all IGP routes and traffic the link down event and converges all IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore link on Tester's Neighbor Interface connected to 7. Restore link on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface. DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back to link up event and converges all IGP routes and traffic back
the Preferred Egress Interface. to the Preferred Egress Interface.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Results Results
The measured IGP Convergence time is influenced by the The measured IGP Convergence time is influenced by the
link failure failure indication, LSA/LSP Flood Packet Pacing, link failure failure indication, LSA/LSP Flood Packet Pacing,
LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation LSA/LSP Retransmission Packet Pacing, LSA/LSP Generation
time, SPF delay, SPF Holdtime, SPF Execution Time, Tree time, SPF delay, SPF Holdtime, SPF Execution Time, Tree
Build Time, and Hardware Update Time. The additional Build Time, and Hardware Update Time. The additional
convergence time contributed by LSP Propagation can be convergence time contributed by LSP Propagation can be
obtained by subtracting the Rate-Derived Convergence Time obtained by subtracting the Rate-Derived Convergence Time
measured in 4.1.2 (Convergence Due to Neighbor Interface measured in 4.1.2 (Convergence Due to Neighbor Interface
Failure) from the Rate-Derived Convergence Time measured in Failure) from the Rate-Derived Convergence Time measured in
this test case. this test case.
4.2 Convergence Due to Layer 2 Session Failure 4.2 Convergence Due to Layer 2 Session Failure
Objective Objective
To obtain the IGP Route Convergence due to a Local Layer 2 Session To obtain the IGP Route Convergence due to a Local Layer 2
failure event. Session failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the IGP routes along the Preferred Egress the routes so that the IGP routes along the Preferred Egress
Interface is the preferred next-hop. Interface is the preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove Layer 2 session from Tester's Neighbor Interface [2] 4. Remove Layer 2 session from Tester's Neighbor Interface [2]
connected to Preferred Egress Interface. connected to Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
Layer 2 session down event and converges all IGP routes and Layer 2 session down event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Restore Layer 2 session on DUT's Preferred Egress Interface. 6. Restore Layer 2 session on DUT's Preferred Egress Interface.
7. Measure Restoration Convergence Time [2] as DUT detects the 7. Measure Restoration Convergence Time [2] as DUT detects the
session up event and converges all IGP routes and traffic over session up event and converges all IGP routes and traffic
the Preferred Egress Interface. over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the Layer 2 The measured IGP Convergence time is influenced by the Layer 2
failure indication, SPF delay, SPF Holdtime, SPF Execution failure indication, SPF delay, SPF Holdtime, SPF Execution
Time, Tree Build Time, and Hardware Update Time. Time, Tree Build Time, and Hardware Update Time.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
4.3 Convergence Due to IGP Adjacency Failure 4.3 Convergence Due to IGP Adjacency Failure
Objective Objective
To obtain the IGP Route Convergence due to a Local IGP Adjacency To obtain the IGP Route Convergence due to a Local IGP Adjacency
failure event. failure event.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove IGP adjacency from Tester's Neighbor Interface [2] 4. Remove IGP adjacency from Tester's Neighbor Interface [2]
connected to Preferred Egress Interface. connected to Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
IGP session failure event and converges all IGP routes and IGP session failure event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Restore IGP session on DUT's Preferred Egress Interface. 7. Restore IGP session on DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the 8. Measure Restoration Convergence Time [2] as DUT detects the
session up event and converges all IGP routes and traffic over session up event and converges all IGP routes and traffic
the Preferred Egress Interface. over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the IGP The measured IGP Convergence time is influenced by the IGP
Hello Interval, IGP Dead Interval, SPF delay, SPF Holdtime, Hello Interval, IGP Dead Interval, SPF delay, SPF Holdtime,
SPF Execution Time, Tree Build Time, and Hardware Update Time. SPF Execution Time, Tree Build Time, and Hardware Update Time.
4.4 Convergence Due to Route Withdrawal 4.4 Convergence Due to Route Withdrawal
Objective Objective
To obtain the IGP Route Convergence due to Route Withdrawal. To obtain the IGP Route Convergence due to Route Withdrawal.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Tester withdraws all IGP routes from DUT's Local Interface 4. Tester withdraws all IGP routes from DUT's Local Interface
on Preferred Egress Interface. on Preferred Egress Interface.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
Layer 2 session down event and converges all IGP routes and Layer 2 session down event and converges all IGP routes and
traffic over the Next-Best Egress Interface. traffic over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
skipping to change at page 11, line 35 skipping to change at page 11, line 35
Objective Objective
To obtain the IGP Route Convergence due to route cost change. To obtain the IGP Route Convergence due to route cost change.
Procedure Procedure
1. Advertise matching IGP routes from Tester to DUT on 1. Advertise matching IGP routes from Tester to DUT on
Preferred Egress Interface [2] and Next-Best Egress Interface Preferred Egress Interface [2] and Next-Best Egress Interface
[2] using the topology shown in Figure 1. Set the cost of [2] using the topology shown in Figure 1. Set the cost of
the routes so that the Preferred Egress Interface is the the routes so that the Preferred Egress Interface is the
preferred next-hop. preferred next-hop.
2. Send offered load at measured Throughput with fixed packet size 2. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT size to destinations matching all IGP routes from Tester to
on Ingress Interface [2]. DUT on Ingress Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Tester increases cost for all IGP routes at DUT's Preferred 4. Tester increases cost for all IGP routes at DUT's Preferred
Egress Interface so that the Next-Best Egress Interface Egress Interface so that the Next-Best Egress Interface
has lower cost and becomes preferred path. has lower cost and becomes preferred path.
5. Measure Rate-Derived Convergence Time [2] as DUT detects the 5. Measure Rate-Derived Convergence Time [2] as DUT detects the
cost change event and converges all IGP routes and traffic cost change event and converges all IGP routes and traffic
over the Next-Best Egress Interface. over the Next-Best Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain. 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface 7. Re-advertise IGP routes to DUT's Preferred Egress Interface
skipping to change at page 12, line 16 skipping to change at page 12, line 16
4.6 Convergence Due to ECMP Member Interface Failure 4.6 Convergence Due to ECMP Member Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link To obtain the IGP Route Convergence due to a local link
failure event of an ECMP Member. failure event of an ECMP Member.
Procedure Procedure
1. Configure ECMP Set as shown in Figure 3. 1. Configure ECMP Set as shown in Figure 3.
2. Advertise matching IGP routes from Tester to DUT on 2. Advertise matching IGP routes from Tester to DUT on
each ECMP member. each ECMP member.
3. Send offered load at measured Throughput with fixed packet size 3. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic routed over all members of ECMP Set.
5. Remove link on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [2] connected to
one of the DUT's ECMP member interfaces. one of the DUT's ECMP member interfaces.
6. Measure Rate-Derived Convergence Time [2] as DUT detects the 6. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic link down event and converges all IGP routes and traffic
over the other ECMP members. over the other ECMP members.
7. Stop offered load. Wait 30 seconds for queues to drain. 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
8. Restore link on Tester's Neighbor Interface connected to 8. Restore link on Tester's Neighbor Interface connected to
DUT's ECMP member interface. DUT's ECMP member interface.
9. Measure Restoration Convergence Time [2] as DUT detects the 9. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges IGP routes and some distribution link up event and converges IGP routes and some distribution
of traffic over the restored ECMP member. of traffic over the restored ECMP member.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by Local link
link failure indication, Tree Build Time, and Hardware Update Time. failure indication, Tree Build Time, and Hardware Update Time.
4.7 Convergence Due to Parallel Link Interface Failure 4.7 Convergence Due to Parallel Link Interface Failure
Objective Objective
To obtain the IGP Route Convergence due to a local link failure To obtain the IGP Route Convergence due to a local link failure
event for a Member of a Parallel Link. The links can be used for event for a Member of a Parallel Link. The links can be used
data Load Balancing for data Load Balancing
Procedure Procedure
1. Configure Parallel Link as shown in Figure 4. 1. Configure Parallel Link as shown in Figure 4.
2. Advertise matching IGP routes from Tester to DUT on 2. Advertise matching IGP routes from Tester to DUT on
each Parallel Link member. each Parallel Link member.
3. Send offered load at measured Throughput with fixed packet size 3. Send offered load at measured Throughput with fixed packet
to destinations matching all IGP routes from Tester to DUT on size to destinations matching all IGP routes from Tester to
Ingress Interface [2]. DUT on Ingress Interface [2].
4. Verify traffic routed over all members of Parallel Link. 4. Verify traffic routed over all members of Parallel Link.
5. Remove link on Tester's Neighbor Interface [2] connected to 5. Remove link on Tester's Neighbor Interface [2] connected to
one of the DUT's Parallel Link member interfaces. one of the DUT's Parallel Link member interfaces.
6. Measure Rate-Derived Convergence Time [2] as DUT detects the 6. Measure Rate-Derived Convergence Time [2] as DUT detects the
link down event and converges all IGP routes and traffic over link down event and converges all IGP routes and traffic over
the other Parallel Link members. the other Parallel Link members.
7. Stop offered load. Wait 30 seconds for queues to drain. 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load. Restart Offered Load.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
skipping to change at page 13, line 28 skipping to change at page 13, line 28
5. IANA Considerations 5. IANA Considerations
This document requires no IANA considerations. This document requires no IANA considerations.
6. Security Considerations 6. Security Considerations
Documents of this type do not directly affect the security of Documents of this type do not directly affect the security of
the Internet or corporate networks as long as benchmarking the 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 operating
networks. networks.
7. Normative References 7. References
7.1 Normative References
[1] Poretsky, S., "Benchmarking Applicability for IGP [1] Poretsky, S., "Benchmarking Applicability for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-08, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-09,
in progress, October 2005. work in progress, January 2006.
[2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-08, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-09,
in progress, October 2005 work in progress, January 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, IETF, December 1990. Environments", RFC 1195, IETF, 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] Bradner, S., "Benchmarking Terminology for Network [5] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, IETF, October 1991. Interconnection Devices", RFC 1242, IETF, January 1991.
[6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999. Network Interconnect Devices", RFC 2544, IETF, March 1999.
[7] Katz, D. and Ward, D., "Bidirectional Forwarding Detection", 7.2 Informative References
draft-ietf-bfd-base-02.txt, work in progress, IETF, None
March 2005. 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
IGP Data Plane Route Convergence
Phone: + 1 508 439 9008 Phone: + 1 508 439 9008
EMail: sporetsky@reefpoint.com EMail: sporetsky@reefpoint.com
Brent Imhoff Brent Imhoff
Juniper Networks
1194 North Mathilda Ave
Sunnyvale, CA 94089
USA USA
Phone: + 1 314 378 2571
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
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
skipping to change at page 14, line 47 skipping to change at page 15, line 5
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.
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 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 attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be 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.
IGP Data Plane Route Convergence
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 copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 43 change blocks. 
90 lines changed or deleted 98 lines changed or added

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