draft-ietf-bmwg-igp-dataplane-conv-meth-03.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-04.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: January 2005 Expires in: April 2005
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
Brent Imhoff Brent Imhoff
LightCore
July 2004 October 2004
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-03.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-04.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or patent or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be disclosed, will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668. in accordance with RFC 3668.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3.2.4 Timers...................................................5 3.2.4 Timers...................................................5
3.2.5 Convergence Time Metrics.................................5 3.2.5 Convergence Time Metrics.................................5
3.2.6 Offered Load.............................................5 3.2.6 Offered Load.............................................5
3.2.7 Interface Types..........................................5 3.2.7 Interface Types..........................................5
3.3 Reporting Format...........................................6 3.3 Reporting Format...........................................6
4. Test Cases..................................................6 4. Test Cases..................................................6
4.1 Convergence Due to Link Failure............................6 4.1 Convergence Due to Link Failure............................6
4.1.1 Convergence Due to Local Interface Failure...............6 4.1.1 Convergence Due to Local Interface Failure...............6
4.1.2 Convergence Due to Neighbor Interface Failure............7 4.1.2 Convergence Due to Neighbor Interface Failure............7
4.1.3 Convergence Due to Remote Interface Failure..............7 4.1.3 Convergence Due to Remote Interface Failure..............7
4.2 Convergence Due to PPP Session Failure.....................8 4.2 Convergence Due to Layer 2 Session Failure.................8
4.3 Convergence Due to IGP Adjacency Failure...................9 4.3 Convergence Due to IGP Adjacency Failure...................9
4.4 Convergence Due to Route Withdrawal........................9 4.4 Convergence Due to Route Withdrawal........................9
4.5 Convergence Due to Cost Change.............................10 4.5 Convergence Due to Cost Change.............................10
4.6 Convergence Due to ECMP Member Interface Failure...........10 4.6 Convergence Due to ECMP Member Interface Failure...........10
4.7 Convergence Due to Parallel Link Interface Failure.........11 4.7 Convergence Due to Parallel Link Interface Failure.........11
5. Security Considerations.....................................12 5. Security Considerations.....................................12
6. References..................................................12 6. References..................................................12
7. Author's Address............................................12 7. Author's Address............................................12
1. Introduction 1. Introduction
skipping to change at page 3, line 9 skipping to change at page 3, line 9
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 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119. this document are to be interpreted as described in RFC 2119.
Terms related to IGP Convergence are defined in [2]. Terms related to IGP Convergence are defined in [2].
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, PPP Session to local Convergence Events such as SONET Link Failure, Layer 2 Session
Failure, IGP Adjacency Failure, Route Withdrawal, and route cost Failure, IGP Adjacency Failure, Route Withdrawal, and route cost
change. These test cases discussed in section 4 provide route 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
Processing time, and FIB Update time. These times are measured Processing time, and FIB Update time. These times are measured
by observing packet loss in the data plane. by observing packet loss in the data plane.
--------- Ingress Interface --------- --------- Ingress Interface ---------
| |<------------------------------| | | |<------------------------------| |
| | | | | | | |
| | Preferred Egress Interface | | | | Preferred Egress Interface | |
skipping to change at page 6, line 53 skipping to change at page 6, line 53
next-hop. next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress Interface matching all IGP routes from Tester to DUT on Ingress Interface
[2]. [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove SONET on DUT's Local Interface [2] by performing an 4. Remove SONET on DUT's Local Interface [2] by performing an
administrative shutdown of the interface. 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. Restore SONET on DUT's Local Interface by administratively 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
7. Restore SONET on DUT's Local Interface by administratively
enabling the interface. enabling the interface.
7. Measure Restoration Convergence Time [2] as DUT detects the link
IGP Data Plane Route Convergence
8. Measure Restoration Convergence Time [2] as DUT detects the link
up event and converges all IGP routes and traffic back to the up event and converges all IGP routes and traffic back to the
Preferred Egress Interface. Preferred Egress Interface.
IGP Data Plane Route Convergence
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, SPF delay, SPF Holdtime, SPF Execution SONET 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 traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations matching
matching all IGP routes from Tester to DUT on Ingress all IGP routes from Tester to DUT on Ingress Interface [2].
Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove SONET on Tester's Neighbor Interface [2] connected to 4. Remove SONET 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. Restore SONET on Tester's Neighbor Interface connected to 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
7. Restore SONET on Tester's Neighbor Interface connected to
DUT's Preferred Egress Interface. DUT's Preferred Egress Interface.
7. 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 to
the Preferred Egress Interface. 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
SONET indication, SPF delay, SPF Holdtime, SPF Execution SONET 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 To obtain the IGP Route Convergence due to a Remote Interface
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 the
routes so that the Preferred Egress Interface is the preferred routes so that the Preferred Egress Interface is the preferred
next-hop. next-hop.
2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress Interface
[2].
3. Verify traffic is routed over Preferred Egress Interface.
4. Remove SONET on Tester's Neighbor Interface [2] connected to
SUT' s Preferred Egress Interface.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
2. Send traffic at maximum forwarding rate to destinations matching
all IGP routes from Tester to DUT on Ingress Interface [2].
3. Verify traffic is routed over Preferred Egress Interface.
4. Remove SONET on Tester's Neighbor Interface [2] connected to
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. Restore SONET on Tester's Neighbor Interface connected to 6. Stop offered load. Wait 30 seconds for queues to drain.
SUT's Preferred Egress Interface. Restart Offered Load.
7. Measure Restoration Convergence Time [2] as SUT detects the 7. Restore SONET on Tester's Neighbor Interface connected to
link up event and converges all IGP routes and traffic over DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT detects the
link up event and converges all IGP routes and traffic back to
the Preferred Egress Interface. the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is influenced by the The measured IGP Convergence time is influenced by the
SONET failure indication, LSA/LSP Flood Packet Pacing, SONET 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 PPP Session Failure 4.2 Convergence Due to Layer 2 Session Failure
Objective Objective
To obtain the IGP Route Convergence due to a Local PPP Session To obtain the IGP Route Convergence due to a Local Layer 2 Session
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 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 traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. Interface [2].
3. Verify traffic routed over Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
4. Remove PPP 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
PPP 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 PPP 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 over
the Preferred Egress Interface. the Preferred Egress Interface.
IGP Data Plane Route Convergence
Results Results
The measured IGP Convergence time is influenced by the PPP 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
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
skipping to change at page 9, line 28 skipping to change at page 9, line 32
preferred next-hop. preferred next-hop.
2. Send traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. 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. Restore IGP session on DUT's Preferred Egress Interface. 6. Stop offered load. Wait 30 seconds for queues to drain.
7. Measure Restoration Convergence Time [2] as DUT detects the Restart Offered Load.
7. Restore IGP session on DUT's Preferred Egress Interface.
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 over
the Preferred Egress Interface. 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 SPF Execution Time, Tree Build Time, and Hardware Update
Time. Time.
4.4 Convergence Due to Route Withdrawal 4.4 Convergence Due to Route Withdrawal
skipping to change at page 9, line 53 skipping to change at page 10, line 4
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 traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. Interface [2].
3. Verify traffic routed over Preferred Egress Interface.
4. Tester withdraws all IGP routes from DUT's Local Interface
on Preferred Egress Interface.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
6. Re-advertise IGP routes to DUT's Preferred Egress Interface. 3. Verify traffic routed over Preferred Egress Interface.
7. Measure Restoration Convergence Time [2] as DUT converges all 4. Tester withdraws all IGP routes from DUT's Local Interface
on Preferred Egress Interface.
6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface.
8. Measure Restoration Convergence Time [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
The measured IGP Convergence time is the SPF Processing and FIB The measured IGP Convergence time is the SPF Processing and FIB
Update time as influenced by the SPF delay, SPF Holdtime, Update time as influenced by the 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.5 Convergence Due to Cost Change 4.5 Convergence Due to Cost Change
Objective Objective
skipping to change at page 10, line 37 skipping to change at page 10, line 42
2. Send traffic at maximum forwarding rate to destinations 2. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. 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. Re-advertise IGP routes to DUT's Preferred Egress Interface 6. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
7. Re-advertise IGP routes to DUT's Preferred Egress Interface
with original lower cost metric. with original lower cost metric.
7. Measure Restoration Convergence Time [2] as DUT converges all 8. Measure Restoration Convergence Time [2] as DUT converges all
IGP routes and traffic over the Preferred Egress Interface. IGP routes and traffic over the Preferred Egress Interface.
Results Results
There should be no measured packet loss for this case. There should be no measured packet loss for this case.
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.
IGP Data Plane Route Convergence
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.
IGP Data Plane Route Convergence
3. Send traffic at maximum forwarding rate to destinations 3. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. Interface [2].
4. Verify traffic routed over all members of ECMP Set. 4. Verify traffic routed over all members of ECMP Set.
5. Remove SONET on Tester's Neighbor Interface [2] connected to 5. Remove SONET 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. Restore SONET on Tester's Neighbor Interface connected to 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
8. Restore SONET on Tester's Neighbor Interface connected to
DUT's ECMP member interface. DUT's ECMP member interface.
8. 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 the Local
SONET indication, Tree Build Time, and Hardware Update Time. SONET 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 To obtain the IGP Route Convergence due to a local link failure
failure event for a Member of a Parallel Link. event for a Member of a Parallel Link. The links can be used 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 traffic at maximum forwarding rate to destinations 3. Send traffic at maximum forwarding rate to destinations
matching all IGP routes from Tester to DUT on Ingress matching all IGP routes from Tester to DUT on Ingress
Interface [2]. Interface [2].
4. Verify traffic routed over all members of Parallel Link. 4. Verify traffic routed over all members of Parallel Link.
5. Remove SONET on Tester's Neighbor Interface [2] connected to 5. Remove SONET 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. Restore SONET on Tester's Neighbor Interface connected to 7. Stop offered load. Wait 30 seconds for queues to drain.
Restart Offered Load.
8. Restore SONET on Tester's Neighbor Interface connected to
DUT's Parallel Link member interface. DUT's Parallel Link member interface.
8. Measure Restoration Convergence Time [2] as DUT detects the
IGP Data Plane Route Convergence
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 Parallel Link member. of traffic over the restored Parallel Link member.
Results Results
The measured IGP Convergence time is influenced by the Local The measured IGP Convergence time is influenced by the Local
SONET indication, Tree Build Time, and Hardware Update Time. SONET indication, Tree Build Time, and Hardware Update Time.
IGP Data Plane Route Convergence
5. Security Considerations 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
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.
6. References 6. References
[1] Poretsky, S., "Benchmarking Applicability for IGP [1] Poretsky, S., "Benchmarking Applicability for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-03, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-04, work
in progress, July 2004. in progress, October 2004.
[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-03, work Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-04, work
in progress, July 2004 in progress, October 2004
[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.
7. Author's Address 7. Author's Address
Scott Poretsky Scott Poretsky
Quarry Technologies Quarry Technologies
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 781 395 5090 Phone: + 1 781 395 5090
EMail: sporetsky@quarrytech.com EMail: sporetsky@quarrytech.com
Brent Imhoff Brent Imhoff
LightCore
USA USA
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any Intel- The IETF takes no position regarding the validity or scope of any Intel-
lectual Property Rights or other rights that might be claimed to pertain lectual Property Rights or other rights that might be claimed to pertain
to the implementation or use of the technology described in this docu- 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 ment or the extent to which any license under such rights might or might
 End of changes. 

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