draft-ietf-mpls-seamless-mcast-07.txt   draft-ietf-mpls-seamless-mcast-08.txt 
Network Working Group Y. Rekhter Network Working Group Y. Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: October 2013 Expiration Date: May 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
May 14 2013 November 11 2013
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-07.txt draft-ietf-mpls-seamless-mcast-08.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 3, line 20 skipping to change at page 3, line 20
4 Inter-area P2MP Segmented Next-Hop Extended Community . 7 4 Inter-area P2MP Segmented Next-Hop Extended Community . 7
5 Discovering P2MP FEC of Inter-Area P2MP Service LSP ... 7 5 Discovering P2MP FEC of Inter-Area P2MP Service LSP ... 7
5.1 BGP MVPN .............................................. 8 5.1 BGP MVPN .............................................. 8
5.2 BGP VPLS or LDP VPLS with BGP auto-discovery .......... 9 5.2 BGP VPLS or LDP VPLS with BGP auto-discovery .......... 9
5.3 Global Table Multicast over MPLS ...................... 11 5.3 Global Table Multicast over MPLS ...................... 11
6 Egress PE/ASBR Procedures ............................. 11 6 Egress PE/ASBR Procedures ............................. 11
6.1 Determining the Upstream ABR/PE/ASBR (Upstream Node) .. 12 6.1 Determining the Upstream ABR/PE/ASBR (Upstream Node) .. 12
6.1.1 Upstream Node for MVPN or VPLS ........................ 12 6.1.1 Upstream Node for MVPN or VPLS ........................ 12
6.1.2 Upstream Node for Global Table Multicast .............. 12 6.1.2 Upstream Node for Global Table Multicast .............. 12
6.2 Originating a Leaf A-D Route .......................... 13 6.2 Originating a Leaf A-D Route .......................... 13
6.2.1 Leaf A-D Route for MVPN and VPLS ...................... 13 6.2.1 Leaf A-D Route for MVPN and VPLS ...................... 14
6.2.2 Leaf A-D Route for Global Table Multicast ............. 14 6.2.2 Leaf A-D Route for Global Table Multicast ............. 14
6.2.3 Constructing the Rest of the Leaf A-D Route ........... 16 6.2.3 Constructing the Rest of the Leaf A-D Route ........... 16
6.3 PIM-SM in ASM mode for Global Table Multicast ......... 16 6.3 PIM-SM in ASM mode for Global Table Multicast ......... 16
6.3.1 Option 1 .............................................. 16 6.3.1 Option 1 .............................................. 17
6.3.1.1 Originating Source Active A-D Routes .................. 17 6.3.1.1 Originating Source Active A-D Routes .................. 17
6.3.1.2 Receiving BGP Source Active A-D Route by PE ........... 17 6.3.1.2 Receiving BGP Source Active A-D Route by PE ........... 17
6.3.1.3 Handling (S, G, RPTbit) state ......................... 18 6.3.1.3 Handling (S, G, RPTbit) state ......................... 18
6.3.2 Option 2 .............................................. 18 6.3.2 Option 2 .............................................. 18
6.3.2.1 Originating Source Active A-D Routes .................. 18 6.3.2.1 Originating Source Active A-D Routes .................. 18
6.3.2.2 Receiving BGP Source Active A-D Route ................. 19 6.3.2.2 Receiving BGP Source Active A-D Route ................. 19
6.3.2.3 Pruning Sources off the Shared Tree ................... 19 6.3.2.3 Pruning Sources off the Shared Tree ................... 19
6.3.2.4 More on handling (S, G, RPTbit) state ................. 20 6.3.2.4 More on handling (S, G, RPTbit) state ................. 20
7 Egress ABR Procedures ................................. 20 7 Egress ABR Procedures ................................. 20
7.1 Handling Leaf A-D route on Egress ABR ................. 20 7.1 Handling Leaf A-D route on Egress ABR ................. 20
7.2 P2MP LSP as the Intra-Area LSP in the Egress Area ..... 22 7.2 P2MP LSP as the Intra-Area LSP in the Egress Area ..... 22
7.2.1 Received Leaf A-D route is for MVPN or VPLS ........... 22 7.2.1 Received Leaf A-D route is for MVPN or VPLS ........... 22
7.2.2 Received Leaf A-D route is for global table multicast . 23 7.2.2 Received Leaf A-D route is for global table multicast . 23
7.2.2.1 Global Table Multicast and S-PMSI A-D Routes .......... 23 7.2.2.1 Global Table Multicast and S-PMSI A-D Routes .......... 23
7.2.2.2 Global Table Multicast and Wildcard S-PMSI A-D Routes . 24 7.2.2.2 Global Table Multicast and Wildcard S-PMSI A-D Routes . 24
7.2.3 Global Table Multicast and the Expected Upstream Node . 24 7.2.3 Global Table Multicast and the Expected Upstream Node . 25
7.2.4 P2MP LDP LSP as the Intra-Area P2MP LSP ............... 25 7.2.4 P2MP LDP LSP as the Intra-Area P2MP LSP ............... 25
7.2.5 P2MP RSVP-TE LSP as the Intra-Area P2MP LSP ........... 25 7.2.5 P2MP RSVP-TE LSP as the Intra-Area P2MP LSP ........... 25
7.3 Ingress Replication in the Egress Area ................ 25 7.3 Ingress Replication in the Egress Area ................ 26
8 Ingress ABR Procedures ................................ 26 8 Ingress ABR Procedures ................................ 26
8.1 P2MP LSP as the Intra-Area LSP in the Backbone Area ... 26 8.1 P2MP LSP as the Intra-Area LSP in the Backbone Area ... 26
8.2 Ingress Replication in the Backbone Area .............. 26 8.2 Ingress Replication in the Backbone Area .............. 27
9 Ingress PE/ASBR Procedures ............................ 27 9 Ingress PE/ASBR Procedures ............................ 27
9.1 P2MP LSP as the Intra-Area LSP in the Ingress Area .... 28 9.1 P2MP LSP as the Intra-Area LSP in the Ingress Area .... 28
9.2 Ingress Replication in the Ingress Area ............... 28 9.2 Ingress Replication in the Ingress Area ............... 29
10 Common Tunnel Type in the Ingress and Egress Areas .... 29 10 Common Tunnel Type in the Ingress and Egress Areas .... 29
11 Placement of Ingress and Egress PEs ................... 30 11 Placement of Ingress and Egress PEs ................... 30
12 MVPN with Virtual Hub-and-Spoke ....................... 30 12 MVPN with Virtual Hub-and-Spoke ....................... 30
13 Data Plane ............................................ 31 13 Data Plane ............................................ 31
13.1 Data Plane Procedures on ABRs ......................... 31 13.1 Data Plane Procedures on ABRs ......................... 31
13.2 Data Plane Procedures on Egress PEs ................... 31 13.2 Data Plane Procedures on Egress PEs ................... 31
13.3 Data Plane Procedures on Ingress PEs .................. 32 13.3 Data Plane Procedures on Ingress PEs .................. 32
13.4 Data Plane Procedures on Transit Routers .............. 33 13.4 Data Plane Procedures on Transit Routers .............. 33
14 Support for Inter-Area Transport LSPs ................. 33 14 Support for Inter-Area Transport LSPs ................. 33
14.1 Transport Tunnel Tunnel Type .......................... 33 14.1 Transport Tunnel Tunnel Type .......................... 33
skipping to change at page 8, line 11 skipping to change at page 8, line 11
either by configuration, or based on the application-specific either by configuration, or based on the application-specific
procedures (e.g., MVPN-specific procedures, VPLS-specific procedures (e.g., MVPN-specific procedures, VPLS-specific
procedures). procedures).
5.1. BGP MVPN 5.1. BGP MVPN
Egress PEs and/or ASBRs discover the P2MP FEC of the service LSPs Egress PEs and/or ASBRs discover the P2MP FEC of the service LSPs
used by BGP MVPN using the I-PMSI or S-PMSI A-D routes that are used by BGP MVPN using the I-PMSI or S-PMSI A-D routes that are
originated by the ingress PEs or ASBRs following the procedures of originated by the ingress PEs or ASBRs following the procedures of
[RFC6514], along with modifications as described in this document. [RFC6514], along with modifications as described in this document.
The NLRI of such routes encodes the P2MP FEC. The procedures in this The NLRI of such routes encodes the P2MP FEC.
document require that at least one ABR in a given IGP area act as
Route Reflector for MVPN A-D routes. The procedures in this document require that at least one ABR in a
given IGP area acts as a Route Reflector for MVPN A-D routes. Such a
Router Reflector is responsible for re-advertising MVPN A-D routes
across area's boundaries. When re-advertising these routes across
area's boundaries, this Route Reflector MUST follow the procedures in
this document. Note that such a Route Reflector may also re-advertise
MVPN A-D routes within the same area, in which case it follows the
plain BGP Route Reflector procedures [RFC4456].
The "Leaf Information Required" flag MUST be set in the P-Tunnel The "Leaf Information Required" flag MUST be set in the P-Tunnel
attribute carried in such routes, when originated by the ingress PEs attribute carried in such routes, when originated by the ingress PEs
or ASBRs, except for the case where (a) as a matter of policy or ASBRs, except for the case where (a) as a matter of policy
(provisioned on the ingress PEs or ASBRs) there is no aggregation of (provisioned on the ingress PEs or ASBRs) there is no aggregation of
ingress area segments of the service LSPs, and (b) mLDP is used as ingress area segments of the service LSPs, and (b) mLDP is used as
the protocol to establish intra-area transport LSPs in the ingress the protocol to establish intra-area transport LSPs in the ingress
area. Before any Leaf A-D route is advertised by a PE or ABR in the area. Before any Leaf A-D route is advertised by a PE or ABR in the
same area, as described in the following sections, an I-PMSI/S-PMSI same area, as described in the following sections, an I-PMSI/S-PMSI
A-D route is advertised either with an explicit Tunnel Type and A-D route is advertised either with an explicit Tunnel Type and
skipping to change at page 10, line 43 skipping to change at page 10, line 50
to its own IP address. Presence of this community in the I-PMSI/S- to its own IP address. Presence of this community in the I-PMSI/S-
PMSI A-D routes indicates to ABRs and PEs/ASBRs that they have to PMSI A-D routes indicates to ABRs and PEs/ASBRs that they have to
follow the procedures in this document when these procedures differ follow the procedures in this document when these procedures differ
from those in [VPLS-P2MP]. from those in [VPLS-P2MP].
Note that the procedures in the above paragraph apply when intra-area Note that the procedures in the above paragraph apply when intra-area
segments are realized by either intra-area P2MP LSPs or by ingress segments are realized by either intra-area P2MP LSPs or by ingress
replication. replication.
The procedures in this document require that at least one ABR in a The procedures in this document require that at least one ABR in a
given area act as Route Reflector for VPLS A-D routes. These ABRs/RRs given area acts as a Route Reflector for VPLS A-D routes. Such a
MUST NOT modify BGP Next Hop when re-advertising these A-D routes. Router Reflector is responsible for re-advertising VPLS A-D routes
across area's boundaries. When re-advertising these routes across
area's boundaries, this Route Reflector MUST follow the procedures in
this document. Note that such a Route Reflector may also re-advertise
VPLS A-D routes within the same area, in which case it follows plain
BGP Route Reflector procedures [RFC4456].
When re-advertising VPLS A-D routes a Route Reflector MUST NOT modify
BGP Next Hop of these routes.
5.3. Global Table Multicast over MPLS 5.3. Global Table Multicast over MPLS
This section describes how the egress PEs discover the P2MP FEC when This section describes how the egress PEs discover the P2MP FEC when
the application is global table multicast over an MPLS-capable the application is global table multicast over an MPLS-capable
infrastructure. In the rest of the document we will refer to this infrastructure. In the rest of the document we will refer to this
application as "global table multicast". application as "global table multicast".
When PIM-SM is used for non-bidirectional ASM ("Any Source When PIM-SM is used for non-bidirectional ASM ("Any Source
Multicast") group addresses, this document refers to this as "PIM-SM Multicast") group addresses, this document refers to this as "PIM-SM
skipping to change at page 38, line 44 skipping to change at page 38, line 44
[RFC1997] "BGP Communities Attribute", Ravi Chandra, et al., RFC1997, [RFC1997] "BGP Communities Attribute", Ravi Chandra, et al., RFC1997,
August 1996 August 1996
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
Levels.", Bradner, March 1997 Levels.", Bradner, March 1997
[RFC4360] S. Sangle et. al., "BGP Extended Communities Attribute", [RFC4360] S. Sangle et. al., "BGP Extended Communities Attribute",
RFC4360, February 2006 RFC4360, February 2006
[RFC4456] T. Bates et. al., "BGP Route Reflection: An Alternative to
Full Mesh Internal BGP (IBGP)", RFC4456, April 2006
[RFC4684] P. Marques et. al., "Constrained Route Distribution for [RFC4684] P. Marques et. al., "Constrained Route Distribution for
Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
Internet Protocol (IP) Virtual Private Networks (VPNs)", RFC 4684, Internet Protocol (IP) Virtual Private Networks (VPNs)", RFC 4684,
November 2006 November 2006
[RFC4760] Bates, T., Rekhter, Y., Chandra, R., and D. Katz, [RFC4760] Bates, T., Rekhter, Y., Chandra, R., and D. Katz,
"Multiprotocol Extensions for BGP-4", RFC 4760, January 2007. "Multiprotocol Extensions for BGP-4", RFC 4760, January 2007.
[RFC4761] Kompella, K., Rekhter, Y., "Virtual Private LAN Service [RFC4761] Kompella, K., Rekhter, Y., "Virtual Private LAN Service
(VPLS) Using BGP for Auto-Discovery and Signaling", RFC 4761, January (VPLS) Using BGP for Auto-Discovery and Signaling", RFC 4761, January
 End of changes. 12 change blocks. 
14 lines changed or deleted 32 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/