draft-ietf-mpls-seamless-mcast-14.txt   draft-ietf-mpls-seamless-mcast-15.txt 
Network Working Group Y. Rekhter Network Working Group Y. Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Intended status: Standards Track Intended status: Standards Track
Expiration Date: December 2014 Expiration Date: July 2015
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
June 30 2014 E. Rosen
Juniper Networks
January 9, 2015
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-14.txt draft-ietf-mpls-seamless-mcast-15.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 39, line 33 skipping to change at page 39, line 33
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
for MPLS and GMPLS networks [RFC5920], in the mLDP specification for MPLS and GMPLS networks [RFC5920], in the mLDP specification
[RFC6388] and in P2MP RSVP-TE specification [RFC3209]. [RFC6388] and in P2MP RSVP-TE specification [RFC3209].
17. Acknowledgements 17. Acknowledgements
We would like to thank Eric Rosen for his comments. We also would We would like to thank Loa Andersson and Qin Wu for their review and
like to thank Loa Andersson and Qin Wu for their review and comments. comments.
18. References 18. References
18.1. Normative References 18.1. Normative References
[RFC1997] "BGP Communities Attribute", Ravi Chandra, et al., RFC [RFC1997] "BGP Communities Attribute", Ravi Chandra, et al., RFC
1997, August 1996 1997, August 1996
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
Levels.", Bradner, RFC 2119, March 1997 Levels.", Bradner, RFC 2119, March 1997
skipping to change at line 1859 skipping to change at page 42, line 16
Nicolai Leymann Nicolai Leymann
Deutsche Telekom AG Deutsche Telekom AG
Winterfeldtstrasse 21 Winterfeldtstrasse 21
Berlin 10781 Berlin 10781
DE DE
Email: n.leymann@telekom.de Email: n.leymann@telekom.de
Samir Saad Samir Saad
AT&T AT&T
Email: samirsaad1@outlook.com Email: samirsaad1@outlook.com
Eric Rosen
Juniper Networks
Email: erosen@juniper.net
 End of changes. 5 change blocks. 
5 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/