Multicast VPN Scalability Benchmarking draft-sdry-bmwg-mvpnscale-03.txt

1. Multicast VPN Scalability Benchmarkingdraft-sdry-bmwg-mvpnscale-03.txt Silvija Dry (sdry@cisco.com) Fernando Calabria (fcalabri@cisco.com) Maria Napierala (mnapierala@att.com) Yuji Kamite (y.kamite@ntt.com) IETF 70, December 6th 2007 Vancouver, Canada draft-sdry-bmwg-mvpnscale-03.txt

2. Agenda • Goal and Open Issues • Timing • Scope Proposal • Next Steps draft-sdry-bmwg-mvpnscale-03.txt

3. Goal @ IETF70 • Achieve agreement on document scope • Document adoption by BMWG Open Issues from IETF68 • Document scope • Document timing draft-sdry-bmwg-mvpnscale-03.txt

4. Why we need this document NOW? • MVPN is widely deployed technology today • Scalability is one of its most discussed aspects among operators, vendors and IETF • PE capacity planning is of critical and immediate importance to operators today draft-sdry-bmwg-mvpnscale-03.txt

5. What are the consequences of delaying? • Vendors and operators are currently spending time developing and executing their own metric and methodology • Lack of comparable results reduces the value of testing efforts by various organizations • Delays in scaling up existing deployments • Lack of comparable practical data that could help with direction of further MVPN solution enhancements draft-sdry-bmwg-mvpnscale-03.txt

6. What is the revised document scope? • It consists of two distinct and complementary pieces: • Generic metric and methodology, agnostic of MVPN architecture • Additional test cases specific to widely deployed architecture draft-sdry-bmwg-mvpnscale-03.txt

7. Why the proposed scope meets industry needs? • Satisfies immediate needs of operators to benchmark already deployed and stable architecture • Ensures longevity of the document and WG investment regardless of future architecture preferences draft-sdry-bmwg-mvpnscale-03.txt

8. Proposed Next Steps: • Finalize adoptionof the document as a BMWG work item • At IETF68 document received 7 supporting and 3 dissenting votes (due to its original scope) • Continue working with operators to consolidate requirements • Addressfuture comments and suggestions from BM, L3VPN and MBONED WGs draft-sdry-bmwg-mvpnscale-03.txt

9. draft-sdry-bmwg-mvpnscale-03.txt THANK YOU! draft-sdry-bmwg-mvpnscale-03.txt

10. Document Goals: • Goal of this draft is to: • Define MVPN metric SET and a standard test methodology to describe, measure and report MVPN scalability benchmarks of PE devices in such a way that: • Results for distinct implementations of the same MVPN architecture can be compared • Results are useful to operators when sizing their network designs draft-sdry-bmwg-mvpnscale-03.txt

11. Key Revision -03 Changes: • Scope is modified to include both generic sections applicable to all MVPN architectures specified in “draft-ietf- l3vpn-2547bis-mcast” and sections specific to widely deployed “rosen-8” architecture • Metric have been redefined to be architecture agnostic • Text is rewritten to address changed scope of the document draft-sdry-bmwg-mvpnscale-03.txt

12. Document Scope - Background • “Draft-ietf- l3vpn-2547bis-mcast” is specification developed by L3VPN WG that defines multiple architectures to implement MVPN • From scalability perspective there are many common variables and benchmarking methods among proposed architectures. • However, some architectures also have some architecture specific variables that impact overall MVPN scale of PE device. draft-sdry-bmwg-mvpnscale-03.txt

13. Metric • 1.Num_mVPN: Number of multicast VPN routing instances configured on DUT that have MI-PMSI (default MDT) active and forwarding • 2. Num_PE: Number of PE routers per multicast VPN • 3. Num_MC_C_ints: Number of PIM C-interfaces on DUT • 4. Num_PIM_C_neigh: Total number of PIM neighbors in PIM C-instances across all mVPNs on DUT • 5. Num_*G_C: Total number of (*,G) multicast routes across all MVPNs on DUT capable of forwarding and created by PIM C-instances. • 6. Num_SG_C: Total number of (S,G) multicast routes across all MVPNs on DUT capable of forwarding and created by PIM C-instances. • 7. Num_OIF_C: Total number of OIFs on DUT across all multicast routes created by PIM C-instances. • 8. Num_SPMSI_Src: Total number of S-PMSIs (data MDTs) across all mVPNs on DUT that are sourced by DUT. • 9. Num_SPMSI_Rx: Total number of S-PMSIs (data MDTs) across all mVPNs on DUT for which DUT is a receiver. draft-sdry-bmwg-mvpnscale-03.txt

14. Architecture agnostic test cases • 9.1 "Empty" MVPNs Scale • 9.2 PIM Enabled VPN C-Interfaces Scale • 9.3 PIM C-instances Mroutes Scale • 9.4 PIM C-Instances OIF Scale • 9.5 Joined S-PMSI (Data MDT) Scale • 9.6 Sourced S-PMSI (Data MDT) Scale • 9.7 S-PMSI (Data MDT) Reuse • 9.8 Scale of mVPNs spanning large number of PEs • 9.9 Scale of mVPNs with larger amount of state • 9.10 Scale of "average" size mVPNs • 9.11 S-PMSI Switching Delay • 9.12 Convergence of C-Instance PIM Joins • 9.13 Effect of Co-locating C-RPs on a PE draft-sdry-bmwg-mvpnscale-03.txt

15. Architecture specific test cases Test Cases Specific to PIM PE-PE signaling • 10.1 PIM Neighborships Scale • 10.2 PIM C-instances J/P Suppression Effectiveness Test Cases Specific to PIM MI-PMSI trees • 11.1 Default MDT's (MI-PMSI's) PIM P-Instance mroutes Scale draft-sdry-bmwg-mvpnscale-03.txt