draft-ietf-mpls-seamless-mcast-08.txt   draft-ietf-mpls-seamless-mcast-09.txt 
Network Working Group Y. Rekhter Network Working Group Y. Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: May 2014 Expiration Date: June 2014
R. Aggarwal R. Aggarwal
T. Morin T. Morin
France Telecom France Telecom
I. Grosclaude I. Grosclaude
France Telecom France Telecom
N. Leymann N. Leymann
Deutsche Telekom AG Deutsche Telekom AG
S. Saad S. Saad
AT&T AT&T
November 11 2013 December 9 2013
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-08.txt draft-ietf-mpls-seamless-mcast-09.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 6, line 24 skipping to change at page 6, line 24
ingress area segment, backbone area segment, and egress area segment. ingress area segment, backbone area segment, and egress area segment.
Within each area a segment is carried over an intra-area P2MP LSP or Within each area a segment is carried over an intra-area P2MP LSP or
instantiated using ingress replication. instantiated using ingress replication.
When intra-area P2MP LSPs are used to instantiate the intra-area When intra-area P2MP LSPs are used to instantiate the intra-area
segments there could be either 1:1 or n:1 mapping between intra-area segments there could be either 1:1 or n:1 mapping between intra-area
segments of the inter-area P2MP service LSP and a given intra-area segments of the inter-area P2MP service LSP and a given intra-area
P2MP LSP. The latter is realized using P2MP LSP hierarchy with P2MP LSP. The latter is realized using P2MP LSP hierarchy with
upstream-assigned labels [RFC5331]. For simplicity of presentation we upstream-assigned labels [RFC5331]. For simplicity of presentation we
assume that P2MP LSP hierarchy is used even with 1:1 mapping, in assume that P2MP LSP hierarchy is used even with 1:1 mapping, in
which case the upstream-assigned label SHOULD be an Implicit NULL. which case an Implicit NULL is used as the upstream-assigned label.
When intra-area segments of the inter-area P2MP service LSP are When intra-area segments of the inter-area P2MP service LSP are
instantiated using ingress replication, then multiple such segments instantiated using ingress replication, then multiple such segments
may be carried in the same P2P RSVP-TE or MP2P LDP LSP. This can be may be carried in the same P2P RSVP-TE or MP2P LDP LSP. This can be
achieved using downstream-assigned labels alone. achieved using downstream-assigned labels alone.
The ingress area segment of a P2MP service LSP is rooted at a PE (or The ingress area segment of a P2MP service LSP is rooted at a PE (or
at an ASBR in the case where the P2MP service LSP spans multiple at an ASBR in the case where the P2MP service LSP spans multiple
ASes). The leaves of this segment are other PEs/ASBRs and ABRs in the ASes). The leaves of this segment are other PEs/ASBRs and ABRs in the
same area as the root PE. same area as the root PE.
skipping to change at page 20, line 39 skipping to change at page 20, line 39
Extended Community carried by the route contains the IP address of Extended Community carried by the route contains the IP address of
this ABR, then the following procedures will be executed. this ABR, then the following procedures will be executed.
If the value of the third octet of the MCAST-VPN NLRI of the received If the value of the third octet of the MCAST-VPN NLRI of the received
Leaf A-D route is either 0x01, or 0x02, or 0x03, this indicates that Leaf A-D route is either 0x01, or 0x02, or 0x03, this indicates that
the Leaf A-D route was originated in response to an S-PMSI or I-PMSI the Leaf A-D route was originated in response to an S-PMSI or I-PMSI
A-D route (see section "Leaf A-D Route for Global Table Multicast"). A-D route (see section "Leaf A-D Route for Global Table Multicast").
In this case the egress ABR MUST find a S-PMSI or I-PMSI route whose In this case the egress ABR MUST find a S-PMSI or I-PMSI route whose
NLRI has the same value as the Route Key field of the received Leaf NLRI has the same value as the Route Key field of the received Leaf
A-D route. If such a matching route is found then the Leaf A-D route A-D route. If such a matching route is found then the Leaf A-D route
MUST be accepted, else it MUST be discarded. If the Leaf A-D route MUST be accepted. If the Leaf A-D route is accepted and if it is the
is accepted and if it is the first Leaf A-D route update for the first Leaf A-D route update for the Route Key field in the route, or
Route Key field in the route, or the withdrawl of the last Leaf A-D the withdrawl of the last Leaf A-D route for the Route Key field then
route for the Route Key field then the following procedures will be the following procedures will be executed.
executed.
If the RD of the received Leaf A-D route is set to all 0s or all 1s If the RD of the received Leaf A-D route is set to all 0s or all 1s
then the received Leaf A-D route is for the global table multicast then the received Leaf A-D route is for the global table multicast
service. service.
If the received Leaf A-D route is the first Leaf A-D route update for If the received Leaf A-D route is the first Leaf A-D route update for
the Route Key field carried in the route, then the egress ABR the Route Key field carried in the route, then the egress ABR
originates a Leaf A-D route, whose MCAST-VPN NLRI is constructed as originates a Leaf A-D route, whose MCAST-VPN NLRI is constructed as
follows. follows.
skipping to change at page 22, line 37 skipping to change at page 22, line 36
7.2.1. Received Leaf A-D route is for MVPN or VPLS 7.2.1. Received Leaf A-D route is for MVPN or VPLS
If the value of the third octet of the MCAST-VPN NLRI of the received If the value of the third octet of the MCAST-VPN NLRI of the received
Leaf A-D route is either 0x01, or 0x02, or 0x03, this indicates that Leaf A-D route is either 0x01, or 0x02, or 0x03, this indicates that
the Leaf A-D route was originated in response to an MVPN or VPLS S- the Leaf A-D route was originated in response to an MVPN or VPLS S-
PMSI or I-PMSI A-D route (see section "Leaf A-D Route for Global PMSI or I-PMSI A-D route (see section "Leaf A-D Route for Global
Table Multicast"). In this case the ABR MUST re-advertise in the Table Multicast"). In this case the ABR MUST re-advertise in the
egress area the MVPN/VPLS A-D route that matches the Leaf A-D route egress area the MVPN/VPLS A-D route that matches the Leaf A-D route
to signal the binding of the intra-area P2MP LSP to the inter-area to signal the binding of the intra-area P2MP LSP to the inter-area
P2MP service LSP. This must be done ONLY if (a) such a binding hasn't P2MP service LSP. This must be done if and only if (a) such a binding
already been advertised, or (b) the binding has changed. The re- hasn't already been advertised, or (b) the binding has changed. The
advertised route MUST carry the Inter-area P2MP Segmented Next-Hop re-advertised route MUST carry the Inter-area P2MP Segmented Next-Hop
Extended Community. Extended Community.
The PMSI Tunnel attribute of the re-advertised route specifies either The PMSI Tunnel attribute of the re-advertised route specifies either
an intra-area P2MP RSVP-TE LSP or an intra-area P2MP LDP LSP rooted an intra-area P2MP RSVP-TE LSP or an intra-area P2MP LDP LSP rooted
at the ABR and MUST also carry an upstream assigned MPLS label. The at the ABR and MUST also carry an upstream assigned MPLS label. The
upstream-assigned MPLS label MUST be set to implicit NULL if the upstream-assigned MPLS label MUST be set to implicit NULL if the
mapping between the inter-area P2MP service LSP and the intra-area mapping between the inter-area P2MP service LSP and the intra-area
P2MP LSP is one-to-one. If the mapping is many-to-one the intra-area P2MP LSP is one-to-one. If the mapping is many-to-one the intra-area
segment of the inter-area P2MP service LSP (referred to as the segment of the inter-area P2MP service LSP (referred to as the
"inner" P2MP LSP) is constructed by nesting the inter-area P2MP "inner" P2MP LSP) is constructed by nesting the inter-area P2MP
service LSP in an intra-area P2MP LSP (referred to as the "outer" service LSP in an intra-area P2MP LSP (referred to as the "outer"
intra-area P2MP LSP), by using P2MP LSP hierarchy based on upstream- intra-area P2MP LSP), by using P2MP LSP hierarchy based on upstream-
assigned MPLS labels [RFC 5332]. assigned MPLS labels [RFC 5332].
If segments of multiple MVPN or VPLS S-PMSI service LSPs are carried If segments of multiple MVPN or VPLS S-PMSI service LSPs are carried
over a given intra-area P2MP LSP, each of these segments MUST carry a over a given intra-area P2MP LSP, each of these segments MUST carry a
distinct upstream-assigned label, even if all these service LSPs are distinct upstream-assigned label, even if all these service LSPs are
for (C-S/*, C-G/*)s from the same MVPN/VPLS. Therefore, an ABR for (C-S/*, C-G/*)s from the same MVPN/VPLS. Therefore, an ABR
maintains an LFIB state for each of the (C-S/*, C-G/*)s carried over maintains an LFIB state for each such S-PMSI traversing the ABR (that
S-PMSIs traversing this ABR (that applies to both the ingress and the applies to both the ingress and the egress ABRs).
egress ABRs).
7.2.2. Received Leaf A-D route is for global table multicast 7.2.2. Received Leaf A-D route is for global table multicast
When the RD of the received Leaf A-D route is set to all 0s or all When the RD of the received Leaf A-D route is set to all 0s or all
1s, then this is the case of inter-area P2MP service LSP being 1s, then this is the case of inter-area P2MP service LSP being
associated with the global table multicast service. The procedures associated with the global table multicast service. The procedures
for this are described below. for this are described below.
7.2.2.1. Global Table Multicast and S-PMSI A-D Routes 7.2.2.1. Global Table Multicast and S-PMSI A-D Routes
 End of changes. 7 change blocks. 
16 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/