P2MP TE MPLS technology
and its applicability

MPLS JAPANNTT 安川正祥

What is a P2MP TE LSP ?
z Point to Multipoint Label Switched Path (LSP)–Efficient traffic replication in the network– Application agnostic
z Set up with TE constraints–May involve resource reservations throughout thenetwork– Determine path of these P2MP TE LSPsz RSVP-TE Signaling–Enhancements to P2P (GMPLS) RSVP-TE

Solution Terminology
Ingress LSR: PE1
Egress LSR : PE2, PE3,PE4, PE5
P1, P2: Branch nodes

PE1P2MP LSP Tunnel

P1P2PE3P3PE5PE4P2P sub-LSPPE2

Solution Mechanism: P2MP Tunnelz Determines set of destinations terminating theunidirectional traffic flow and for which resource
reservation is required
z May comprise multiple P2MP LSP Tunnels(at least one)z Identified by the P2MP SESSION Object which
includes–––P2MP ID: identifies the destination of the P2MP tunnel
Tunnel ID: 16 bit identifier
Extended Tunnel ID: local IPv4/IPv6 Address or left unspecified

Solution Mechanism: P2MP LSP Tunnelz A specific instance of a P2MP Tunnel

determined by the source of the traffic flowz May comprise multiple P2P sub-LSPs
z Identified by the P2MP Tunnel SESSION andP2MP SENDER_TEMPLATE object combinationz P2MP SENDER_TEMPLATE––Identifies the sender (ingress)
Includesz Source IPv4/IPv6 addressz LSP ID

Solution Mechanism: P2P Sub-LSP
LSP from the ingress LSR to a particular egress LSR
z A P2MP LSP Tunnel comprises multiple P2P sub-LSPsz A P2P sub-LSP is represented byz––zP2P sub-LSP object
Sub-explicit route object

P2P sub-LSP Object–Identifies a P2P Sub-LSP–Egress LSR Destination address– P2P sub-LSP identifier (sub-LSP ID)
z

Sub-Explicit route––Represents the explicit route from ingress LSR to the egress LSR
May be compressedMultiple Path Messages: Example
PE1
P2MP Tunnel: ID_1 {PE2,PE3,PE4}
L3
L4->{L5}
P1

PE4

PE3

L3->{L1, L2}
L1P2

L2
P2MP LSP Tunnel: {PE1; ID_1}
P2P sub-LSP list: [PE2, PE3, PE4]P3
PE2PE5

Single Path Message: Example
P2P sub-LSP PE4 ERO: {P1,PE4}
P2P sub-LSP PE2 ERO: {P1,PE2}

PE1L4L3P2P1PE4L1P2P sub-LSP PE3 ERO: {P2,P3,PE3}
P2P sub-LSP PE5 ERO: {P3,PE5}
Compression = Avoids duplicationof common ERO segments

PE3L3->{L1, L2}
L5

L2PE2L7
P3
L5->{L6,L7}

L6PE5

Standards Statusz Work done as part of the IETF MPLS WG charterz Requirement document under last call–

URL: <http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mprequirement-04.txt>–

revisited version under mailing list discussionz Solution document (individual status)––URL: <http://www.ietf.org/internet-drafts/ draft-raggarwa-mpls-rsvp-tep2mp-00.txt>

virtual team of ~ 30 people working on the document– new version was submitted for the next IETF meeting(Washington DC, Nov’04)

IP Multicast VPNs
P2MP TE MPLS is applicable to IP Multicast VPNs.
z Because of its TE and QoS capabilities, this combination
provides easy and flexible IP multicast VPN service
operation for the service provider.
z MVPNs architectures proposals- draft-rosen-vpn-mcast-07.txt- draft-raggarwa-l3vpn-mvpn-vpls-mcast-00.txt- draft-yasukawa-l3vpn-p2mp-mcast-00.txt
zIdea 1: Solution to construct a single provider
wide customer’s IP multicast networkzz

Construct a single provider wide customer’s IP multicast networkby interconnecting customer’s private IP multicast networks.
PIM neighbor relationships are preserved between provider’s PEs.
(PIM control messages are transmitted transparently over P-MPLS
network.)
PIM neighbor
relationship

Source

PIM neighbor
relationship

CEC-IPmcast
network

PIM neighbor
relationship

PERPCEPE

C-IPmcast
networkPE

PIM neighbor
relationship

P

P-MPLS
networkCE
A single provider wide
Customer’s IP multicast network

Receiver
C-IPmcast
networkIdea 2: Solution to construct multiple
independent customer’s IP multicast networkszz

Construct multiple independent customer’s IP multicast networkby making PEs to perform proxy-source/RP of original IP multicast
networks.
PIM neighbor relationships are not preserved between provider’sPEs. (PIM control messages are terminated at each PE.)
PIM neighbor
relationship

PIM neighbor
relationship

SourceCE

ProxySource/RP

C-IPmcast
network

ProxySource/RPPP-MPLSnetwork

ProxySource/RPRP

CE

C-IPmcast
network
PIM neighbor
relationship

CEReceiver
C-IPmcast
networkBGP/MPLS IP Multicast VPNszzzzz

Make each PE to act as Proxy-Source/RP for each customers IPmulticast domain.
Setup a default/data P2MP tree from a PE which accommodates IP
multicast source to PEs which accommodate customers RP &Receivers.
Default P2MP Tress is established when a multicast VPN info isconfigured on each PE.
Data P2MP Tree is established based on traffic flow on demandbasis.
IP multicast register info is transferred by MP-BGP between PEs.
MP-BGPC-(PIM-SM NW)
Join(S,G), Register stopSource
CE
Join(*,G)

Proxy-Source

CE

Receiver

ReceiverRegister
Receiver

ProxySource/RP

ProxySource/RP

Join(*,G)/Join(S,G)

ReceiverDefault P2MP TreeP

ReceiverJoin(*,G)CE
Proxy-RP

RegisterJoin(S,G), Register stop RP

Data P2MP Tree

P-MPLS
networkJoin(*,G)/Join(S,G)
CE

Receiver

ReceiverThank you !