Use of Wildcard in SPMSI AutoDiscovery Routes draftrekhtermvpnwildcardspmsi

1
Use of Wildcard in S-PMSI Auto-Discovery
Routesdraft-rekhter-mvpn-wildcard-spmsi

• Rahul Aggarwal (Juniper)
• Wim Henderickx (Alcatel-Lucent)
• Praveen Muley (Alcatel-Lucent)
• Ray Qiu (Alcatel-Lucent)
• Yakov Rekhter (Juniper)

2
Background (1)

• draft-ietf-l3vpn-2547bis-mcast-bgp (already)
  defines S-PMSI encoding/procedures for
  aggregating multiple C-multicast flows onto a
  single P-Multicast tree
• A PE MAY aggregate two or more S-PMSIs
  originated by the PE onto the same P-Multicast
  tree (Section 12.1 of draft-ietf-l3vpn-2547bis-mc
  ast-bgp)
• C-multicast flows may belong to either the same,
  or different MVPNs
• Aggregation is controlled by the PE that is the
  root of the P-Multicast tree
• This is accomplished by PE advertising the same
  P-Multicast tree in all the S-PMSI A-D routes for
  these C-flows
• draft-ietf-l3vpn-2547bis-mcast-bgp procedures for
  aggregating S-PMSIs improve control AND data
  plane scalability on P routers
• By reducing the number of P-Multicast trees
• draft-ietf-l3vpn-2547bis-mcast-bgp procedures for
  aggregating S-PMSIs also improve data plane
  scalability on PE routers
• By reducing the number of P-Multicast trees

3
Background (2)

• However, encoding/procedures specified in
  draft-ietf-l3vpn-2547bis-mcast-bgp limit the
  granularity of a single S-PMSI A-D route to a
  single (C-S, C-G) C-multicast flow
• Removing this limitation could improve control
  plane scalability on PE routers and Route
  Reflectors
• By reducing the number of S-PMSI A-D routes
• Removing this limitation will have no impact on P
  routers, and no impact on the data plane of PE
  routers
• draft-rekhter-mvpn-wildcard-spmsi specifies
  extensions to the encoding/procedures (already)
  specified in draft-ietf-l3vpn-2547bis-mcast-bgp
  that remove this limitation
• Extensions to sections 4.3, 12.1, and 12.3 of
  draft-ietf-l3vpn-2547bis-mcast-bgp
• Extensions are OPTIONAL

4
Possible applications (1)

• (C-, C-G) applications
• C-G is in the ASM range
• PE connected to a site that contains C-RP uses a
  single (C-, C-G) S-PMSI A-D route to advertise
  aggregation onto a single P-Multicast tree of all
  (C-Ss, C-G) flows for the same C-G traveling
  along the customers RPT tree
• PE uses a single (C-, C-G) S-PMSI A-D route to
  advertise aggregation onto a single P-Multicast
  tree of all (C-Ss, C-G) flows for the same C-G
  traveling along customers SPT trees for all the
  C-Ss within the MVPN sites connected to that PE
• C-G is in the PIM-Bidir range
• PE uses a single (C-, C-G) S-PMSI A-D route to
  advertise aggregation onto a single P-Multicast
  tree of all (C-Ss, C-G) flows for the same C-G
  for all the C-Ss within the MVPN sites connected
  to a given PE

5
Possible applications (2)

• (C-S, C-) applications
• C-S originates (multiple) PIM-SM in SSM mode
  (multicast) streams
• PE uses a single (C-S, C-) S-PMSI A-D route to
  advertise aggregation onto a single P-Multicast
  tree of all (C-S, C-Gs) SSM flows originated by
  the same C-S
• C-S is within a site connected to that PE

6
Possible applications (3)

• (C-, C-) applications
• MVPN runs in S-PMSI only mode
• PE uses a single (C-, C-) S-PMSI A-D route to
  advertise aggregation onto a single P-Multicast
  tree of all (C-S, C-G)s flows originated within
  the MVPN sites connected to that PE
• Except for the flows that the PE already
  advertises in either (C-S, C-G) S-PMSI A-D
  routes, or (C-, C-G) S-PMSI A-D routes, or (C-S,
  C-) S-PMSI A-D routes