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

1
Multicast VPN Scalability Benchmarkingdraft-sdry-
bmwg-mvpnscale-01.txt

• Silvija Dry (sdry_at_cisco.com)
• Fernando Calabria (fcalabri_at_cisco.com)
• Maria Napierala (mnapierala_at_att.com)
• Yuji Kamite (y.kamite_at_ntt.com)

IETF 68, March 20th 2007 Prague, Czech Republic
2

• Agenda
• Document Goals
• Revision -01 Changes
• Scope Background
• Next Steps

3

• 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 for rosen-8 MVPN
  architecture in such a way that
• Distinct implementations of the same MVPN
  architecture can be compared
• Results are useful to SPs when sizing their
  network designs

4

• Key Revision -01 Changes
• Based on received feedback number of changes were
  made in -01 revision
• Added Maria Napierala and Yuji Kamite as
  co-authors
• Reorganized Introduction and Scope sections
• Identified areas of text that can be leveraged by
  MVPN architectures other than rosen-8
  (draft-rosen-vpn-mcast-08)
• Made terminology consistent with both
  draft-ietf- l3vpn-2547bis-mcast and rosen-8

5

• Key Revision -01 Changes
• Added test cases addressing
• C-RP outsourced model
• S-PMSI switching delay
• Convergence of C-instance PIM Joins
• For ease of reading added
• Relationships between metric and test setup
  variables
• Relationships between metric variables for each
  test case
• Section reviewing key terms

6

• Key Revision -01 Changes
• Added requirement to test cases 9.12-9.17 to be
  executed for all MI-PMSI PIM modes supported by
  implementation under test
• Added recommendations for addressing impact of
  data forwarding on control plane scalability
• Removed any text implying pass/fail type of
  testing
• Reduced requirements to allow for
• IGMP receivers connected to PE routers

7

• Document Scope - Background
• draft-rosen-vpn-mcast (rosen-8) history
• Proposed MVPN architecture that use PIM protocol
  for both PE-PE signaling and creation of core
  transport multicast trees
• Was submitted to L3VPN WG in 2000
• Multiple vendor implementations occurred
• Now it is widely deployed by operators and
  scalability benchmarking is needed
• It is incorporated in broader draft adopted by
  L3VPN WG (Draft-ietf- l3vpn-2547bis-mcast)

8

• Document Scope - Background
• Draft-ietf- l3vpn-2547bis-mcast l3vpn-mcast
  Background
• Proposes multiple architectures and protocols as
  a possibility to implement MVPN functionality,
  among them rosen-8 architecture
  (draft-rosen-vpn-mcast-08)
• rosen-8 architecture is only MVPN architecture
  that is deployed today
• Some of proposed mechanisms in l3vpn-mcast do
  not have practical implementations yet and it is
  not yet clear which other architectures (besides
  rosen-8) will end up being deployed and what
  best practices will be

9

• Document Scope - Background
• There are some common scale impacting variables
  among all architectures.
• However, each architecture has specific variables
  that impact overall MVPN scale.
• Without accounting for architecture specific
  variables one can neither compare different
  implementations (of the same architecture) or
  provide data needed by operators for sizing
  deployments

10

• Document Scope - Background
• Given multiple architectures and protocols
  providing same functionality there are two
  possible scalability benchmarking goals
• Comparing implementations of the same specific
  architecture/protocols and providing benchmarks
  needed for deployments of each specific
  architecture
• Comparing different architectures/protocols
• Benchmarks for both goals are useful
• But, the same benchmarks can not address both
  goals

11

• Document Scope - Proposal
• Complete current draft, which achieves goal 1
  for widely deployed rosen-8 architecture and
  thus satisfy immediate need of operators that
  deployed it
• If deemed needed, begin work on new document that
  is agnostic of architecture used, which achieves
  goal 2
• In future as other architectures get defined and
  implemented there may be need for benchmarking
  drafts addressing their specifics

12

• Proposed Next Steps
• Adopt the document as a BMWG work item
• Address future comments and suggestions

13

• draft-sdry-bmwg-mvpnscale-01.txt
• THANK YOU!