MulticastVPNs (Compatibility Mode)

Model for Multiservice Network
Private IP
Multicast VPNs
ATM/FR Emulation
PSTN Bearer
and Signalling
Ethernet Services
Internet
L3VPN
(unicast only)
L2VPN
VPLS
Signalling and Auto-Discovery (BGP)
Transport Infrastructure (MPLS LSPs)
Note: Legacy draft-Rosen L3VPN multicast scheme does not conform to this model.
2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net
www.juniper.net | 2
2010 Juniper Networks, Inc. All rights reserved.
Legacy Model for MVPN (draft-Rosen)
Legacy Multicast Topology (draft-Rosen)

Providers PIM domain
Customer PIM domain
Customer PIM domain
Source
Provider Core
P-RP
1.1.1.1
P2
C-RP/DR
CE
A
L3VPN
(multicast)
PE-1
lo0: 192.168.16.1
1.1.1.1 224.7.7.7 M-cast Data

SA
AS 65412
Receiver
192.168.16.1 239.1.1.1 1.1.1.1 224.7.7.7 M-cast Data

GRE-SA
DA
GRE-DA
SA
DA
1.1.1.1 224.7.7.7 M-cast Data

SA
DA
PE routers must participate in both customers and

providers multicast domain
PIM/multicast traffic from customer instance of PIM
encapsulated in GRE using configured vpn-groupaddress on PE router (example uses 239.1.1.1)
Signalling and Auto-discovery (PIM)
Transport Infrastructure (multicast GRE tunnels)
Multicast data, hellos, join/prunes, Bootstrap, Auto-RP, etc.

PE-1 and PE-2 join configured vpn-group-address
within providers domain using the provider RP
Multicast trees across the core signalled by PIM running in

main routing instance
OSPF Area 0
P1
PIM adjacencies between PEs (per-VRF) to

exchange info about multicast receivers
CE
B
PE-2
lo0: 192.168.24.1
www.juniper.net | 3
www.juniper.net | 4
Motivations Behind NG-MVPN
Model for Next-Generation MVPN

Private IP
IETF motivations for a new MVPN scheme called

next-generation MVPN
ATM/FR emulation
PSTN bearer +
signalling
Ethernet Services
Internet
Increasing interest from customers of Layer 3 VPN services

in having multicast capability, in addition to unicast
New mission-critical MVPN applications such as IPTV
IPTV
L3VPN
(unicast and
multicast)
Point to multipoint MPLS LSPs provide multicast-like

forwarding
Realization that existing Rosen scheme for MVPN has
fundamental architectural limitations
L2VPN
VPLS
Signalling and Auto-discovery (BGP)
Transport Infrastructure (MPLS LSPs)
Traffic Engineering, bandwidth guarantees, fast-reroute
www.juniper.net | 5
www.juniper.net | 6
Replacing PIM with BGP
Next-Generation MVPN Terms
BGP for PE-PE signaling
Terms
Seven MP-BGP NLRI for

MVPN signaling
PMSI : Type of tunnel to use to transport multicast data

across the provider core (also called provider tunnel)
PE1
MVPN membership
autodiscovery
RSVP point to multipoint LSPs
Autodiscovery for selective

provider tunnels
Customer PIM join message
conversion
RR
RR
Provider instance PIM distribution trees (similar to draft-Rosen)

MLDP
PE5
PE2
Multidirectional: All PEs in a MVPN can transmit multicast packets

to all other PEs participating in MVPN
Active sources
PE routers might need only

a couple of BGP sessions
to route-reflectors
PE3
PE4
I-PMSI
Unidirectional: Enables only a particular PE to transmit multicast

packets to other PEs
S-PMSI
Can be the same as Layer 3

VPN unicast scheme
A particular PE can transmit multicast packets to a subset of PEs

www.juniper.net | 7
Next-Generation MVPN BGP

Advertisements
www.juniper.net | 8
Next-Generation MVPN BGP NLRI Types

(1 of 4)
Next-generation MVPN routes use the MCAST-VPN NLRI

format
AFI 1/SAFI 5
Routes tagged with correct route target community are
placed into the bgp.mvpn.0 and
Type routingLength Route Type Specific
instance.mvpn.0 table (1 bytes) (1 bytes) (variable length)
Type 1: Intra-AS Inclusive MVPN Membership Discovery

Sent by all PE routers participating in MVPN
In the case of I-PMSI using RSVP-TE, these routes determine
where to automatically build the point to multipoint LSPs
Routes are tagged with PMSI Tunnel attribute
1:10.1.1.1:1:10.1.1.1
Type
Next-generation MVPN draft specifies new attributes

P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute
Tunnel
Type
MPLS Label
Flags
(1 bytes) (1 bytes)
Tunnel ID
(3 bytes)
(variable length)
MPLS label that receiving PE should

expect as an inner label for incoming
MVPN traffic (0 = No label)

(2 of 4)
C-S using SPMSI
C-G
Mask
C-G using
S-PMSI
Sending PEs
lo0
Sent by receiver PE upon receiving a Type 3 with the leaf

information bit set
4:3:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3:10.255.170.100:10.255.170.98
Received Type
3 Route
Learned through PIM register messages (RP), MSDP source active

messages, or a locally connected source
Sending PEs
lo0
Type
www.juniper.net | 11
Sending
PEs RD
C-S
Mask
C-S
C-G
Mask
C-G
Type 6: Shared Tree Join Route

Sent by receiver PE that receives PIM join (C-*,C-G) on VRF
interface
6:10.255.170.100:1:65000:32:10.12.53.12:32:224.1.2.3
Type
5:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3
Type 4: Selective MVPN Autodiscovery Route for Leaf
Type
Sending
PEs AS
Sent by PE router that discovers an active multicast source
3:10.255.170.100:1:32:192.168.194.2:32:224.1.2.3:10.255.170.100
C-S
Mask
Sending
PEs RD
Type 5: Source Active Autodiscovery Route
Sent by the PE that initiates an S-PMSI

Sending
PEs RD
2:10.1.1.1:1:65412
Type

(3 of 4)
Type 3: Selective MVPN Autodiscovery Route
Type
Used for membership discovery between PE routers in

different ASs
Not covered in this material
www.juniper.net | 9
Sending
PEs lo0
Type 2: Inter-AS Inclusive MVPN Membership Discovery
RSVP Session ID for RSVP point to

multipoint LSPs
Sending
PEs RD
RD of upstream
PE (towards C-RP)
C-RP
AS of
upstream Mask
PE
C-RP Address
C-G
Mask
C-G

(4 of 4)
Point-to-Multipoint LSP Concept
Type 7: Source Tree Join Route

Sent by receiver PE that receives PIM join (C-S,C-G) on VRF
interface
RSVP point-to-multipoint LSPs can be used as the

transport mechanism for next-generation MVPN traffic
across the core
Traffic can be protected using standard methods like fast reroute and
link protection
7:10.255.170.100:1:65000:32:192.168.194.2:32:224.1.2.3
Type
RD of upstream
PE (towards C-RP)
C-S
AS of
upstream Mask
PE
C-S
C-G
Mask
PE1
C-G
Can use MPLS FRR, Traffic

Engineering, Bandwidth
Reservations
Core routers only need IGP plus

MPLS, no PIM needed!
P2
P1
PE5
PE2
PE3
PE4
Next-Generation MVPN Inclusive Trees
Next-Generation MVPN Selective Trees
Inclusive trees
Selective trees
Each tree serves one MVPN

only
All the multicast traffic in
that MVPN arriving at an
ingress PE is mapped to
that same tree to get from
the ingress PE to all the
PE5
other PEs in the same
MVPN
Analogous to default-MDT
in draft-Rosen
Serves particular selected

multicast group(s) from a
given MVPN
Similar to data-MDT in
draft-Rosen
PE1
Selective Tree
PE5
PE2
PE2
PE3
PE4
PE3
PE4
I-PMSI Signalling Example (2 of 4)

Example with show the use of inclusive trees with RSVP
point to multipoint LSPs
With no source or receivers for multicast traffic, an

MVPN is enabled on the PE routers
Each PE router:
Prior to enabling an MVPN, the PE routers have an existing

L3VPN established using LDP to signal LSPs
The provider core does not have PIM enabled
Customer PIM domain
PE1
Customer PIM domain
Advertises a Inclusive MVPN A-D route to each other tagged with

Route Target and PMSI Tunnel Attribute
Automatically builds a point to multipoint LSP to other PEs with itself
as root and no PHP (virtual tunnel interface or vrf-table-label)
Customer PIM domain
1:192.168.6.1:1:192.168.6.1
PMSI RSVP Session ID, Label = 0
Customer PIM domain
Source
PE-2
Provider Core
lo0: 192.168.2.1
OSPF Area 0
10.0.101.2
C-DR
CE
A
PE-2
Provider Core
lo0: 192.168.2.1
OSPF Area 0
P1
P2
CE
B
P2
C-DR
PE-1
1
P1
CE
B
lo0: 192.168.6.1
C-RP
CE
A
AS 65512
PE-3
lo0: 192.168.2.2
CE
C
PE-1
1
lo0: 192.168.6.1
C-RP
AS 65512
PE-3
lo0: 192.168.2.2
CE
C
Source begins sending multicast traffic
Using IGMP, receivers join source specific group
CE-A sends register messages to PE-1
Receiver CEs send PIM (S,G) join upstream to PE-2 and PE-3
Receiver PEs convert PIM join to MVPN Source Tree Join
Source PE convert MVPN Source Tree Join to PIM (S,G) Join
and sends it to the DR to complete the multicast tree
PE-1 is now aware of an active source
PE-1 sends SA Autodiscovery Route to remote PEs

5:192.168.6.1:1:32:10.0.101.2:32:224.7.7.7
Customer PIM domain
lo0: 192.168.2.1
OSPF Area 0
10.0.101.2
P1
10.0.101.2
P2
CE
A
AS 65512
lo0: 192.168.6.1
P1
lo0: 192.168.2.2
I-PMSI Forwarding
P2
Receivers
S-IP
SA
lo0: 192.168.2.2
CE
C
Prior to enabling an MVPN, the PE routers have an existing

L3VPN established using LDP to signal LSPs
The provider core does not have PIM enabled
P2 sends copies of packets to both PE-2 and PE-3

Receiver PEs pop outer label and send traffic based on VRF
MPLS
PE-3
C-RP
Outbound MPLS label is derived from the point to multipoint LSP
Label
AS 65512
Example with show the use of selective trees with RSVP

point to multipoint LSPs
CE-A sends native multicast packets to PE-1

PE-1 encapsulates packets in a single MPLS header
DA
CE
B
S-PMSI Signalling Example (1 of 5)
After multicast forwarding tree is built
224.7.7.7 M-cast Data
PE-1
lo0: 192.168.6.1
CE
C
PE-3
C-RP
SA
PE-2
lo0: 192.168.2.1
OSPF Area 0
C-DR
PE-1
PIM Registers
S-IP
Customer PIM domain
Provider Core
C-DR
CE
A
PIM (S,G) Join
Customer PIM domain
CE
B
PE-2
Provider Core
7:192.168.6.1:1:65512:32:10.0.101.2:32:224.7.7.7
PIM (S,G) Join
Customer PIM domain
224.7.7.7 M-cast Data
S-IP 224.7.7.7 M-cast Data
SA
DA
Customer PIM domain
DA
Customer PIM domain
Customer PIM domain
Customer PIM domain
Source
lo0: 192.168.2.1
OSPF Area 0
S-IP=10.0.101.2
P1
PE-1
1
lo0: 192.168.6.1
PE-1
P2
AS 65512
lo0: 192.168.6.1
CE
C
PE-3
lo0: 192.168.2.2
P1
CE
B
C-DR
CE
A
C-RP
lo0: 192.168.2.1
OSPF Area 0
Receivers
AS 65512
PE-2
Provider Core
10.0.101.2
P2
C-DR
CE
A
CE
B
PE-2
Provider Core
PE-3
C-RP
lo0: 192.168.2.2
CE
C

Source begins sending multicast traffic
With no source or receivers for multicast traffic, an

MVPN is enabled on the PE routers
CE-A sends register messages to PE-1

PE-1 is now aware of an active source
Each PE router:
PE-1 sends SA Autodiscovery Route to remote PEs
Advertises a Inclusive MVPN A-D route to each other tagged with

Route Target
5:192.168.6.1:1:32:10.0.101.2:32:224.7.7.7
No point to multipoint LSPs are built between PEs at this point

Customer PIM domain
Customer PIM domain
1:192.168.6.1:1:192.168.6.1
Provider Core
PE-2
lo0: 192.168.2.1
OSPF Area 0
P1
Customer PIM domain
lo0: 192.168.2.1
OSPF Area 0
P2
P1
CE
B
P2
C-DR
PE-1
1
PE-2
Provider Core
10.0.101.2
C-DR
CE
A
Customer PIM domain
CE
B
lo0: 192.168.6.1
C-RP
CE
A
AS 65512
PE-3
lo0: 192.168.2.2
CE
C
PE-1
1
lo0: 192.168.6.1
C-RP
PIM Registers
AS 65512
PE-3
lo0: 192.168.2.2
CE
C

PE-1 completes the multicast forwarding tree
Using IGMP, receivers join source specific group
PE-1 sends S-PMSI Autodiscovery route remote PEs

Only PE-2 responds with a Leaf Autodiscovery route
PE-1 builds point to multipoint LSP to responding leaf PEs
and sends PIM join towards the DR
Receiver CE-B sends PIM (S,G) join upstream to

Receiver PE-2 converts PIM join to MVPN Source Tree Join
No receiver attached to CE-C
1
7:192.168.6.1:1:65512:32:10.0.101.2:32:224.7.7.7
PIM (S,G) Join

4
Customer PIM domain
Customer PIM domain
PE-2
Provider Core
lo0: 192.168.2.1
OSPF Area 0
10.0.101.2
P1
P2
AS 65512
lo0: 192.168.6.1
PE-3
C-RP
Customer PIM domain
lo0: 192.168.2.2
CE
C
lo0: 192.168.2.1
OSPF Area 0
P1
P2
Receiver
C-DR
CE
A
PE-1
1
CE
B
PE-2
Provider Core
3
Receiver
PE-1
1
4:3:192.168.6.1:1:0:0.0.0.0:32:224.7.7.7:192.168.6.1:192.168.2.1
PIM (S,G) Join

Customer PIM domain
10.0.101.2
C-DR
CE
A
CE
B
3:192.168.6.1:1:0:0.0.0.0:32:224.7.7.7:192.168.6.1
PMSI RSVP Session ID, Label = 0, Leaf Info Required
AS 65512
lo0: 192.168.6.1
CE
C
PE-3
C-RP
lo0: 192.168.2.2
Hardware Requirements for

Next-Generation MVPNs
Next-Generation MVPN Junos OS Support
Requires tunnel service PIC on certain routers
Junos OS supports:
Customers first hop DR

Customers candidate RPs
All PE routers participating in customers multicast network
RSVP Selective Trees

PIM-SSM Tunnels
Tunnel services simply needs to be enabled on the

MX Series DPC/MPCs
Data MDT Tunnels
PIM features
[edit]
user@pe1# show chassis
fpc 1 {
pic 0 {
tunnel-services {
bandwidth 1g;
}
}
}
PIM Sparse Mode

PIM Dense Mode
Auto-RP
Bootstrap Protocol
Next-Generation MVPN Configuration

(1 of 4)

(2 of 4)
PE to PE MP-BGP session must be configured to allow

for MVPN signaling
[edit]
user@pe1# show protocols bgp
family inet {
unicast;
any;
}
family inet-vpn {
any;
}
family inet-mvpn {
signaling;
}
group my-int-group {
type internal;
local-address 192.168.6.1;
neighbor 192.168.2.2;
neighbor 192.168.2.1;
}
RSVP Inclusive Trees

PIMASM Tunnels
Except when using vrf-table-label
Provider Tunnel Types
Configure P2MP LSP template for provider tunnel

[edit]
user@pe1# show protocols mpls
label-switched-path mvpn-example {
template;
no-cspf;
link-protection;
p2mp;
}
Configure RSVP-TE LSP to be used as provider tunnel

Inclusive Provider Tunnel
[edit routing-instances mcast-pe-vrf]

user@pe1# show
provider-tunnel {
rsvp-te {
label-switched-path-template {
mvpn-example;
}
}
}
vrf-table-label;
Selective Provider Tunnel

user@pe1# show
provider-tunnel {
selective {
group 224.7.7.0/24 {
wildcard-source {
rsvp-te {
label-switched-pat{
default-template;
vrf-table-label;

(3 of 4)

(4 of 4)
Configure the VRF to participate in the C-PIM domain

as well as the MVPN
[edit]
user@pe1# show routing-instances mcast-pe-vrf
protocols {
pim {
rp {
local {
address 192.168.13.3;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
spt-only;
}

Options
user@pe1# set provider-tunnel ?
Possible completions:
> mdt
Data MDT tunnels for PIM MVPN
> pim-asm
PIM-SM provider tunnel
> pim-ssm
PIM-SSM provider tunnel
> rsvp-te
RSVP-TE point-to-multipoint LSP for flooding
> selective
Selective tunnels
MVPN settings

user@pe1# set protocols mvpn ?
Possible completions:
> autodiscovery-only
Use MVPN exclusively for PE router autodiscovery
> mvpn-mode
MVPN mode of operation
receiver-site
MVPN instance has sites only with multicast receivers
> route-target
Configure route-targets for MVPN routes
sender-site
MVPN instance has sites only with multicast sources
> traceoptions
Trace options for BGP-MVPN
unicast-umh-election Upstream Multicast Hop election based on unicast route
preference
Verify Multicast Packet Forwarding
pim {
rp {
local {
address 192.168.13.3;
}
}
interface all {
mode sparse;
}
}
mvpn {
mvpn-mode {
spt-only;
}
}
}
Verify PIM status

user@pe1> show pim join instance mcast-pe-vrf extensive
Instance: PIM.mcast-pe-vrf Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.7.7.7
Source: 10.0.101.2
Flags: sparse
Upstream interface: ge-1/0/9.251
Upstream neighbor: 10.0.50.2
Upstream state: Local RP, Join to Source
Keepalive timeout:
Downstream neighbors:
Interface: Pseudo-MVPN
Instance: PIM.mcast-pe-vrf Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
MVPN RIB-IN
View MVPN routes learned from remote PEs
Verify multicast traffic
Routes that populate this table have been accepted by vrfimport policy (based on vrf-target matching)
user@pe1> show multicast route extensive instance mcast-pe-vrf

Family: INET
Group: 224.7.7.7
Source: 10.0.101.2/32
Upstream interface: ge-1/0/9.251
Session description: Unknown
Statistics: 139 kBps, 263 pps, 532482 packets
Next-hop ID: 3638
Upstream protocol: MVPN
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
user@pe1> show route table bgp.mvpn.0

bgp.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:192.168.2.1:65535:192.168.2.1/240
*[BGP/170] 18:13:11, localpref 100, from 192.168.2.1
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
1:192.168.2.2:65535:192.168.2.2/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299808
7:192.168.6.1:5:65512:32:10.0.101.2:32:224.7.7.7/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
Family: INET6

user@pe1# show
instance-type vrf;
interface ge-1/0/9.251;
interface lo0.13;
provider-tunnel {
rsvp-te {
label-switched-path-template {
mvpn-example;
}
}
}
vrf-target target:65512:100;
vrf-table-label;
protocols {
bgp {
group external {
type external;
export exp-policy;
neighbor 10.0.50.2 {
peer-as 65501;
}
}
View VRF PIM Status
Provider tunnels
Full VRF example configuration
VRF Specific MVPN Routes
Verify Provider Tunnel
View MVPN routes specific to a particular VRF
View status of point to multipoint LSP
user@pe1> show route table mcast-pe-vrf.mvpn.0

mcast-pe-vrf.mvpn.0: 5 destinations, 6 routes (5 active, 1 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:192.168.2.1:65535:192.168.2.1/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
1:192.168.2.2:65535:192.168.2.2/240
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299808
1:192.168.6.1:5:192.168.6.1/240
*[MVPN/70] 00:41:29, metric2 1
Indirect
5:192.168.6.1:5:32:10.0.101.2:32:224.7.7.7/240
*[PIM/105] 18:23:21
Multicast (IPv4)
7:192.168.6.1:5:65512:32:10.0.101.2:32:224.7.7.7/240
*[PIM/105] 00:18:31
Multicast (IPv4)
[BGP/170] 00:18:31, localpref 100, from 192.168.2.1
AS path: I
> to 172.22.250.2 via ge-1/0/4.250, Push 299888
user@pe1> show rsvp session

Ingress RSVP: 2 sessions
To
From
State
192.168.2.1
192.168.6.1
Up
192.168.2.2
192.168.6.1
Up
Total 2 displayed, Up 2, Down 0
Rt Style Labelin Labelout LSPname

0 1 SE
300096 192.168.2.1:192.168.6.1:5:mvpn:mcast-pe-vrf
0 1 SE
300096 192.168.2.2:192.168.6.1:5:mvpn:mcast-pe-vrf
Verify multicast traffic with traverse point to multipoint

LSP
user@pe1> show route forwarding-table destination 224.7.7.7 extensive
Routing table: mcast-pe-vrf.inet [Index 5]
Internet:
Destination: 224.7.7.7.10.0.101.2/64
Route type: user
Route reference: 0
Route interface-index: 223
Flags: cached, check incoming interface , accounting, sent to PFE
Next-hop type: flood
Index: 3638
Reference: 2
Nexthop: 172.22.250.2
Next-hop type: Push 300096
Index: 3625
Reference: 1
Next-hop interface: ge-1/0/4.250

MulticastVPNs (Compatibility Mode)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MulticastVPNs (Compatibility Mode)

Загружено:

Авторское право:

Доступные форматы

Model for Multiservice Network

Signalling and Auto-Discovery (BGP)

Transport Infrastructure (MPLS LSPs)

2010 Juniper Networks, Inc. All rights reserved.

Legacy Model for MVPN (draft-Rosen)

Legacy Multicast Topology (draft-Rosen)

Customer PIM domain

Customer PIM domain

1.1.1.1 224.7.7.7 M-cast Data

192.168.16.1 239.1.1.1 1.1.1.1 224.7.7.7 M-cast Data

1.1.1.1 224.7.7.7 M-cast Data

PE routers must participate in both customers and

Signalling and Auto-discovery (PIM)

Transport Infrastructure (multicast GRE tunnels)

Multicast data, hellos, join/prunes, Bootstrap, Auto-RP, etc.

Multicast trees across the core signalled by PIM running in

PIM adjacencies between PEs (per-VRF) to

2010 Juniper Networks, Inc. All rights reserved.

Motivations Behind NG-MVPN

Model for Next-Generation MVPN

IETF motivations for a new MVPN scheme called

Increasing interest from customers of Layer 3 VPN services

Point to multipoint MPLS LSPs provide multicast-like

Signalling and Auto-discovery (BGP)

Transport Infrastructure (MPLS LSPs)

Traffic Engineering, bandwidth guarantees, fast-reroute

2010 Juniper Networks, Inc. All rights reserved.

2010 Juniper Networks, Inc. All rights reserved.

Replacing PIM with BGP

Next-Generation MVPN Terms

BGP for PE-PE signaling

Seven MP-BGP NLRI for

PMSI : Type of tunnel to use to transport multicast data

RSVP point to multipoint LSPs

Autodiscovery for selective

Provider instance PIM distribution trees (similar to draft-Rosen)

Multidirectional: All PEs in a MVPN can transmit multicast packets

PE routers might need only

Unidirectional: Enables only a particular PE to transmit multicast

Can be the same as Layer 3

A particular PE can transmit multicast packets to a subset of PEs

2010 Juniper Networks, Inc. All rights reserved.

Next-Generation MVPN BGP

2010 Juniper Networks, Inc. All rights reserved.

Next-Generation MVPN BGP NLRI Types

Next-generation MVPN routes use the MCAST-VPN NLRI

Type 1: Intra-AS Inclusive MVPN Membership Discovery

Next-generation MVPN draft specifies new attributes

MPLS label that receiving PE should

Next-Generation MVPN BGP NLRI Types

C-S using SPMSI

Sent by receiver PE upon receiving a Type 3 with the leaf

Learned through PIM register messages (RP), MSDP source active

Type 6: Shared Tree Join Route

2010 Juniper Networks, Inc. All rights reserved.

2010 Juniper Networks, Inc. All rights reserved.

Type 4: Selective MVPN Autodiscovery Route for Leaf

Sent by PE router that discovers an active multicast source

Type 5: Source Active Autodiscovery Route

Sent by the PE that initiates an S-PMSI

Next-Generation MVPN BGP NLRI Types

Type 3: Selective MVPN Autodiscovery Route

Used for membership discovery between PE routers in