1. IGP Data Plane Convergence draft-ietf-bmwg-dataplane-conv-meth-15.txt draft-ietf-bmwg-dataplane-conv-term-15.txt draft-ietf-bmwg-dataplane-conv-app-15.txt BMWG, IETF-71 Philadelphia March 2008 Scott Poretsky, NextPoint Networks Brent Imhoff, Juniper Networks

2. Work Item Status -9 completed 2 cross-area reviews -10 completed second BMWG WGLC -11 and -12 completed AD Reviews -13 went to IESG and DISCUSS items received (IETF 69 agenda) Design Team formed -14 closed out DISCUSS items (IETF 70 agenda) -15 addressed additional input from Design Team (IETF 71 agenda)

3. -15 Terminology Changes Updated Convergence Timeline Full Convergence, Convergence Convergence Recovery Event Instant Instant Time = 0sec Forwarding Rate = ^ ^ ^ Offered Load = Offered Load --> ------ Packet -------------- <---Max Throughput \ Loss /<----Convergence Convergence------->\ / Event Transition Recovery Transition \ / \_____/<------Maximum Packet Loss ^ First Route Convergence Instant Y-axis = Forwarding Rate X-axis = Time (increases right to left to match commercial test equipment displays) Figure 1. Convergence Graph

4. -15 Terminology Changes Term Changes Renamed 3 Terms: –First Route Convergence Instant = First Prefix Convergence Instant –First Route Convergence Time = First Prefix Convergence Instant –Sustained Convergence Validation Time= Sustained Forwarding Convergence Time Added 2 New Terms: –Route-Specific Convergence –Route-Specific Convergence Time

5. Terminology Benchmarks Route-Specific Convergence Time = Convergence Packets Loss / Offered Load where units are packets / packets/second = seconds Loss-Derived Convergence Time = Convergence Packets Loss / Offered Load where units are packets / packets/second = seconds Rate-Derived Convergence Time = Convergence Recovery Instant – Convergence Event Instant First Route Convergence Time = First Route Convergence Instant - Convergence Event Instant Or min(Route-Specific Convergence Time) Can be used to benchmark Full Convergence RECOMMENDED to benchmark Full Convergence Used to benchmark Route-Specific Convergence

6. Methodology Changes Removed test case for Convergence Due to Neighbor Interface Failure Renamed two test cases –Convergence Due to Layer 2 Session Loss = Convergence Due to Layer 2 Session Failure –Convergence Due to IGP Adjacency Failure= Convergence Due to Loss of IGP Adjacency Expanded Reporting Format

7. Reporting Format Parameter Units --------- ----- Test Case test case number Test Topology (1, 2, 3, or 4) IGP (ISIS, OSPF, other) Interface Type (GigE, POS, ATM, other) Packet Size offered to DUT bytes IGP Routes advertised to DUT number of IGP routes Nodes in emulated network number of nodes Packet Sampling Interval on Tester milliseconds IGP Timer Values configured on DUT: Interface Failure Indication Delay seconds IGP Hello Timer seconds IGP Dead-Interval seconds LSA Generation Delay seconds LSA Flood Packet Pacing seconds LSA Retransmission Packet Pacing seconds SPF Delay seconds Forwarding Metrics Total Packets Offered to DUT number of Packets Total Packets Routed by DUT number of Packets Convergence Packet Loss number of Packets Out-of-Order Packets number of Packets Duplicate Packets number of Packets Parameter Units --------- ----- Convergence Benchmarks Full Convergence First Route Convergence Time seconds Rate-Derived Convergence Time seconds Loss-Derived Convergence Time seconds Route-Specific Convergence Number of Routes Measured number of flows Route-Specific Convergence Time[n] array of seconds Minimum R-S Convergence Time seconds Maximum R-S Convergence Time seconds Median R-S Convergence Time seconds Average R-S Convergence Time seconds Reversion Reversion Convergence Time seconds First Route Convergence Time seconds Route-Specific Convergence Number of Routes Measured number of flows Route-Specific Convergence Time[n] array of seconds Minimum R-S Convergence Time seconds Maximum R-S Convergence Time seconds Median R-S Convergence Time seconds Average R-S Convergence Time seconds

8. Updated General Methodology Test Cases updated to follow this general methodology: 1. Establish DUT configuration and install routes 2. Send offered load with traffic traversing Preferred Egress Interface 3. Introduce Convergence Event to force traffic to Next-Best Egress Interface 4. Measure First Route Convergence Time 5. Measure Loss-Derived Convergence Time, Rate-Derived Convergence Time, and optionally the Route-Specific Convergence Times 6. Wait the Sustained Convergence Validation Time to ensure there no residual packet loss 7. Recover from Convergence Event 8. Measure Reversion Convergence Time, and optionally the First Route Convergence Time and Route-Specific Convergence Times

9. Outstanding Issues? Allow Full Convergence to be benchmarked by max(Route-Specific Convergence Time)? Make Route Withdrawal test case more white-box in setup and measurement? Remove the test case?

10. Next Steps Issues? / Comments? Close DISCUSS Items on IESG page? Ready to go back to IESG?