draft-ietf-mpls-seamless-mcast-12.txt   draft-ietf-mpls-seamless-mcast-13.txt 
skipping to change at page 1, line 21 skipping to change at page 1, line 21
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
June 6 2014 June 10 2014
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-12.txt draft-ietf-mpls-seamless-mcast-13.txt
Abstract Abstract
This document describes procedures for building inter-area point-to- This document describes procedures for building inter-area point-to-
multipoint (P2MP) segmented service LSPs by partitioning such LSPs multipoint (P2MP) segmented service LSPs by partitioning such LSPs
into intra-area segments and using BGP as the inter-area routing and into intra-area segments and using BGP as the inter-area routing and
label distribution protocol. Within each IGP area the intra-area label distribution protocol. Within each IGP area the intra-area
segments are either carried over intra-area P2MP LSPs, using P2MP LSP segments are either carried over intra-area P2MP LSPs, using P2MP LSP
hierarchy, or instantiated using ingress replication. The intra-area hierarchy, or instantiated using ingress replication. The intra-area
P2MP LSPs may be signaled using P2MP RSVP-TE or P2MP mLDP. If ingress P2MP LSPs may be signaled using P2MP RSVP-TE or P2MP mLDP. If ingress
skipping to change at page 4, line 30 skipping to change at page 4, line 30
14 Support for Inter-Area Transport LSPs ................. 33 14 Support for Inter-Area Transport LSPs ................. 33
14.1 Transport Tunnel Tunnel Type .......................... 34 14.1 Transport Tunnel Tunnel Type .......................... 34
14.2 Discovering Leaves of the Inter-Area P2MP Service LSP . 34 14.2 Discovering Leaves of the Inter-Area P2MP Service LSP . 34
14.3 Discovering P2MP FEC of P2MP Transport LSP ............ 34 14.3 Discovering P2MP FEC of P2MP Transport LSP ............ 34
14.4 Egress PE Procedures for P2MP Transport LSP ........... 35 14.4 Egress PE Procedures for P2MP Transport LSP ........... 35
14.5 ABRs and Ingress PE procedures for P2MP Transport LSP . 36 14.5 ABRs and Ingress PE procedures for P2MP Transport LSP . 36
14.6 Discussion ............................................ 37 14.6 Discussion ............................................ 37
15 IANA Considerations ................................... 39 15 IANA Considerations ................................... 39
16 Security Considerations ............................... 39 16 Security Considerations ............................... 39
17 Acknowledgements ...................................... 39 17 Acknowledgements ...................................... 39
18 References ............................................ 40 18 References ............................................ 39
18.1 Normative References .................................. 40 18.1 Normative References .................................. 39
18.2 Informative References ................................ 41 18.2 Informative References ................................ 41
19 Author's Address ...................................... 41 19 Author's Address ...................................... 41
1. Introduction 1. Introduction
This document describes procedures for building inter-area point-to- This document describes procedures for building inter-area point-to-
multipoint (P2MP) segmented service LSPs by partitioning such LSPs multipoint (P2MP) segmented service LSPs by partitioning such LSPs
into intra-area segments and using BGP as the inter-area routing and into intra-area segments and using BGP as the inter-area routing and
label distribution protocol. Within each IGP area the intra-area label distribution protocol. Within each IGP area the intra-area
segments are either carried over intra-area P2MP LSPs, potentially segments are either carried over intra-area P2MP LSPs, potentially
skipping to change at page 39, line 11 skipping to change at page 39, line 11
to PE5, which has no receivers for this stream. Likewise, (C-S2, C- to PE5, which has no receivers for this stream. Likewise, (C-S2, C-
G2) will be delivered not just to PE3, PE4, and PE5, but also to PE2, G2) will be delivered not just to PE3, PE4, and PE5, but also to PE2,
which has no receivers for this stream. which has no receivers for this stream.
15. IANA Considerations 15. IANA Considerations
This document defines a new BGP Extended Community called "Inter-area This document defines a new BGP Extended Community called "Inter-area
P2MP Segmented Next-Hop" (see section "Inter-area P2MP Segmented P2MP Segmented Next-Hop" (see section "Inter-area P2MP Segmented
Next-Hop Extended Community"). This community is IP Address Specific, Next-Hop Extended Community"). This community is IP Address Specific,
of an extended type, and is transitive. A codepoint for this of an extended type, and is transitive. A codepoint for this
community should be assigned both from the IPv4 Address Specific community has been assigned both from the IPv4 Address Specific
Extended Community registry, and from the IPv6 Address Specific Extended Community registry, and from the IPv6 Address Specific
Extended Community registry. The same code point should be assigned Extended Community registry. IANA is requested to change in these
from both registries. registries the reference to the RFC number as soon as this document
is published as an RFC.
IANA is requested to assign one code point from the range for
transitive communities in the IPv4 Address Specific Extended
Community register within the Border Gateway Protocol (BGP) Extended
Communities namespace.
IANA is requested to assign one code point from the range for
transitive communities in the IPv6 Address Specific Extended
Community register within the Border Gateway Protocol (BGP) Extended
Communities namespace.
Further, the lowest value that is available in both registries should
be allocated.
This document also assigns a new Tunnel Type in the PMSI Tunnel This document also assigns a new Tunnel Type in the PMSI Tunnel
Attribute, called the "Transport Tunnel" (see section "Transport Attribute, called the "Transport Tunnel" (see section "Transport
Tunnel Type"). This Tunnel Type is assigned a value of 8. Tunnel Type"). This Tunnel Type is assigned a value of 8.
16. Security Considerations 16. Security Considerations
Procedures described in this document are subject to similar security Procedures described in this document are subject to similar security
threats as any MPLS deployment. It is recommended that baseline threats as any MPLS deployment. It is recommended that baseline
security measures are considered as described in Security Framework security measures are considered as described in Security Framework
 End of changes. 5 change blocks. 
20 lines changed or deleted 8 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/