draft-ietf-mpls-tp-p2mp-framework-00.txt   draft-ietf-mpls-tp-p2mp-framework-01.txt 
MPLS Working Group D. Frost, Ed. MPLS Working Group D. Frost, Ed.
Internet-Draft S. Bryant, Ed. Internet-Draft S. Bryant, Ed.
Intended status: Informational Cisco Systems Intended status: Informational Cisco Systems
Expires: July 25, 2013 M. Bocci, Ed. Expires: October 10, 2013 M. Bocci, Ed.
Alcatel-Lucent Alcatel-Lucent
L. Berger, Ed. L. Berger, Ed.
LabN Consulting LabN Consulting
January 21, 2013 April 08, 2013
A Framework for Point-to-Multipoint MPLS in Transport Networks A Framework for Point-to-Multipoint MPLS in Transport Networks
draft-ietf-mpls-tp-p2mp-framework-00 draft-ietf-mpls-tp-p2mp-framework-01
Abstract Abstract
The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP) The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP)
is the common set of MPLS protocol functions defined to enable the is the common set of MPLS protocol functions defined to enable the
construction and operation of packet transport networks. The MPLS-TP construction and operation of packet transport networks. The MPLS-TP
supports both point-to-point and point-to-multipoint transport paths. supports both point-to-point and point-to-multipoint transport paths.
This document defines the elements and functions of the MPLS-TP This document defines the elements and functions of the MPLS-TP
architecture applicable specifically to supporting point-to- architecture applicable specifically to supporting point-to-
multipoint transport paths. multipoint transport paths.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functions of a packet transport network.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 25, 2013. This Internet-Draft will expire on October 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.1. Additional Definitions and Terminology . . . . . . . . 4 1.2.1. Additional Definitions and Terminology . . . . . . . 3
1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. MPLS Transport Profile Point-to-Multipoint Requirements . . . 4 2. MPLS Transport Profile Point-to-Multipoint Requirements . . . 4
3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. MPLS-TP Encapsulation and Forwarding . . . . . . . . . . . 6 3.1. MPLS-TP Encapsulation and Forwarding . . . . . . . . . . 5
4. Operations, Administration and Maintenance (OAM) . . . . . . . 6 4. Operations, Administration and Maintenance (OAM) . . . . . . 5
5. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Point-to-Multipoint LSP Control Plane . . . . . . . . . . 7 5.1. Point-to-Multipoint LSP Control Plane . . . . . . . . . . 6
5.2. Point-to-Multipoint PW Control Plane . . . . . . . . . . . 7 5.2. Point-to-Multipoint PW Control Plane . . . . . . . . . . 7
6. Survivability . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Survivability . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Network Management . . . . . . . . . . . . . . . . . . . . . . 8 7. Network Management . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP) The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP)
is the common set of MPLS protocol functions defined to meet the is the common set of MPLS protocol functions defined to meet the
requirements specified in [RFC5654]. The MPLS-TP Framework [RFC5921] requirements specified in [RFC5654]. The MPLS-TP Framework [RFC5921]
provides an overall introduction to the MPLS-TP and defines the provides an overall introduction to the MPLS-TP and defines the
general architecture of the Transport Profile, as well as those general architecture of the Transport Profile, as well as those
aspects specific to point-to-point transport paths. The purpose of aspects specific to point-to-point transport paths. The purpose of
this document is to define the elements and functions of the MPLS-TP this document is to define the elements and functions of the MPLS-TP
architecture applicable specifically to supporting point-to- architecture applicable specifically to supporting point-to-
multipoint transport paths. multipoint transport paths.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication (IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network. capabilities and functions of a packet transport network.
1.1. Scope 1.1. Scope
This document defines the elements and functions of the MPLS-TP This document defines the elements and functions of the MPLS-TP
architecture related to supporting point-to-multipoint transport architecture related to supporting point-to-multipoint transport
paths. The reader is referred to [RFC5921] for those aspects of the paths. The reader is referred to [RFC5921] for those aspects of the
MPLS-TP architecture that are generic, or concerned specifically with MPLS-TP architecture that are generic, or concerned specifically with
point-to-point transport paths. point-to-point transport paths.
1.2. Terminology 1.2. Terminology
skipping to change at page 4, line 37 skipping to change at page 4, line 4
MPLS-TE MPLS Traffic Engineering MPLS-TE MPLS Traffic Engineering
P2MP Point-to-multipoint P2MP Point-to-multipoint
PW Pseudowire PW Pseudowire
1.2.1. Additional Definitions and Terminology 1.2.1. Additional Definitions and Terminology
Detailed definitions and additional terminology may be found in Detailed definitions and additional terminology may be found in
[RFC5921] and [RFC5654]. [RFC5921] and [RFC5654].
1.3. Applicability 1.3. Applicability
The point-to-multipoint connectivity provided by an MPLS-TP network The point-to-multipoint connectivity provided by an MPLS-TP network
is based on the point-to-multipoint connectivity provided by MPLS is based on the point-to-multipoint connectivity provided by MPLS
networks. MPLS TE-LSP support is discussed in [RFC4875] and networks. P2MP MPLS TE-LSP support is discussed in [RFC4875] and
[RFC5332], and PW support is being developed based on [RFC5332], and P2MP PW support is being developed based on
[I-D.ietf-pwe3-p2mp-pw-requirements] and [I-D.ietf-pwe3-p2mp-pw-requirements] and
[I-D.ietf-l2vpn-vpms-frmwk-requirements]. MPLS-TP point-to- [I-D.ietf-l2vpn-vpms-frmwk-requirements]. MPLS-TP point-to-
multipoint connectivity is analogous to that provided by traditional multipoint connectivity is analogous to that provided by traditional
transport technologies such as Optical Transport Network (OTN) point- transport technologies such as Optical Transport Network (OTN) point-
to-multipoint [ref?] and optical drop-and-continue [ref?], and thus to-multipoint [G.798] and drop-and-continue [G.780], and thus
supports the same class of traditional applications. supports the same class of traditional applications, e.g., video
distribution.
2. MPLS Transport Profile Point-to-Multipoint Requirements 2. MPLS Transport Profile Point-to-Multipoint Requirements
The requirements for MPLS-TP are specified in [RFC5654], [RFC5860], The requirements for MPLS-TP are specified in [RFC5654], [RFC5860],
and [RFC5951]. This section provides a brief summary of point-to- and [RFC5951]. This section provides a brief summary of point-to-
multipoint transport requirements as set out in those documents; the multipoint transport requirements as set out in those documents; the
reader is referred to the documents themselves for the definitive and reader is referred to the documents themselves for the definitive and
complete list of requirements. complete list of requirements.
o MPLS-TP must support unidirectional point-to-multipoint (P2MP) o MPLS-TP must support unidirectional point-to-multipoint (P2MP)
skipping to change at page 7, line 8 skipping to change at page 6, line 21
needed to the MPLS-TP profile of [RFC6374] [RFC6375]. needed to the MPLS-TP profile of [RFC6374] [RFC6375].
[Editor's note: Additional information / text has been published in [Editor's note: Additional information / text has been published in
[I-D.hmk-mpls-tp-p2mp-oam-framework]. The Editors will coordinate [I-D.hmk-mpls-tp-p2mp-oam-framework]. The Editors will coordinate
with the draft authors to identify which text should be folded into with the draft authors to identify which text should be folded into
this document and which should remain in a standalone document.] this document and which should remain in a standalone document.]
5. Control Plane 5. Control Plane
The framework for the MPLS-TP control plane is provided in [RFC6373]. The framework for the MPLS-TP control plane is provided in [RFC6373].
This document reviews MPLS-TP control plane requirments as well as This document reviews MPLS-TP control plane requirements as well as
provides details on how the MPLS-TP control plane satisfies these provides details on how the MPLS-TP control plane satisfies these
requirements. Most of the requirements identified in [RFC6373] apply requirements. Most of the requirements identified in [RFC6373] apply
equally to P2P and P2MP transport paths. The key P2MP specific equally to P2P and P2MP transport paths. The key P2MP specific
control plane requirements are identified in requirement 6 (P2MP control plane requirements are identified in requirement 6 (P2MP
transport paths), 34 (use P2P sub-layers), 49 (common recovery transport paths), 34 (use P2P sub-layers), 49 (common recovery
solutions for P2P and P2MP), 59 (1+1 protection), 62 (1:n solutions for P2P and P2MP), 59 (1+1 protection), 62 (1:n
protection), and 65 (1:n shared mesh recovery). protection), and 65 (1:n shared mesh recovery).
[RFC6373] defines the control plane approach used to support MPLS-TP [RFC6373] defines the control plane approach used to support MPLS-TP
transport paths. It identifies Generalized MPLS (GMPLS) as the transport paths. It identifies Generalized MPLS (GMPLS) as the
skipping to change at page 8, line 17 skipping to change at page 7, line 29
not address recovery of P2MP PWs. Such recovery can be provided via not address recovery of P2MP PWs. Such recovery can be provided via
P2MP LSP recovery as generally discussed in [RFC6372]. P2MP LSP recovery as generally discussed in [RFC6372].
Alternatively, PW recovery [RFC6718] can be extended to explicitly Alternatively, PW recovery [RFC6718] can be extended to explicitly
support recovery of P2MP PWs. support recovery of P2MP PWs.
6. Survivability 6. Survivability
The overall survivability architecture for MPLS-TP is defined in The overall survivability architecture for MPLS-TP is defined in
[RFC6372], and section 4.7.3 in particular describes the application [RFC6372], and section 4.7.3 in particular describes the application
of linear protection to unidirectional P2MP entities using 1+1 and of linear protection to unidirectional P2MP entities using 1+1 and
1:1 protection architecture. The approach is for the root of the 1:1 protection architecture. For 1+1, the approach is for the root
P2MP tree to bridge the user traffic to both the working and of the P2MP tree to bridge the user traffic to both the working and
protection entities. Each sink/leaf MPLS-TP node selects the traffic protection entities. Each sink/leaf MPLS-TP node selects the traffic
from one entity according to some predetermined criteria. Fault from one entity according to some predetermined criteria. For 1:1,
notification happens from the node idenifying the fault to the root the source/root MPLS-TP node needs to identify the existence of a
fault condition on any of the branches of the network. Fault
notification happens from the node identifying the fault to the root
node and from the leaves to the root via an out of band path. In node and from the leaves to the root via an out of band path. In
either case the root then selects the protection transport path for either case the root then selects the protection transport path for
traffic transfer. More sophisticated survivability approaches such traffic transfer. More sophisticated survivability approaches such
as partial tree protection and 1:n protection are for further study. as partial tree protection and 1:n protection are for further study.
The IETF has no experience with P2MP PW survivability as yet, and The IETF has no experience with P2MP PW survivability as yet, and
therefore it is proposed that the P2MP PW survivability will therefore it is proposed that the P2MP PW survivability will
initially rely on the LSP survivability. Further work is needed on initially rely on the LSP survivability. Further work is needed on
this subject, partiularly if a requiremnet emerges to provide this subject, particularly if a requirement emerges to provide
survivability for P2MP PWs in an MPLS-TP context. survivability for P2MP PWs in an MPLS-TP context.
7. Network Management 7. Network Management
The network management architecture and requirements for MPLS-TP are The network management architecture and requirements for MPLS-TP are
specified in [RFC5951]. They derive from the generic specifications specified in [RFC5951]. They derive from the generic specifications
described in ITU-T G.7710/Y.1701 [G.7710] for transport technologies. described in ITU-T G.7710/Y.1701 [G.7710] for transport technologies.
They also incorporate the OAM requirements for MPLS Networks They also incorporate the OAM requirements for MPLS Networks
[RFC4377] and MPLS-TP Networks [RFC5860] and expand on those [RFC4377] and MPLS-TP Networks [RFC5860] and expand on those
requirements to cover the modifications necessary for fault, requirements to cover the modifications necessary for fault,
configuration, performance, and security in a transport network. configuration, performance, and security in a transport network.
[Editor's note: Decide what if anything needs to be said about P2MP- [Editor's note: Decide what if anything needs to be said about P2MP-
specific network management considerations.] specific network management considerations.]
Section 3.14 of " Framework for MPLS in Transport Networks" [RFC5921] Section 3.14 of " Framework for MPLS in Transport Networks" [RFC5921]
describe the aspects of network management in the P2P MPLS-TP case. describe the aspects of network management in the P2P MPLS-TP case.
This apply to the P2MP case. This apply to the P2MP case.
skipping to change at page 9, line 23 skipping to change at page 8, line 34
IANA considerations resulting from specific elements of MPLS-TP IANA considerations resulting from specific elements of MPLS-TP
functionality are detailed in the documents specifying that functionality are detailed in the documents specifying that
functionality. This document introduces no additional IANA functionality. This document introduces no additional IANA
considerations in itself. considerations in itself.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC4872] Lang, J., Rekhter, Y., and [RFC4872] Lang, J.P., Rekhter, Y., and D. Papadimitriou, "RSVP-TE
D. Papadimitriou, "RSVP-TE Extensions in Support of End-to-End Generalized Multi-
Extensions in Support of Protocol Label Switching (GMPLS) Recovery", RFC 4872, May
End-to-End Generalized 2007.
Multi-Protocol Label
Switching (GMPLS)
Recovery", RFC 4872,
May 2007.
[RFC4873] Berger, L., Bryskin, I., [RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,
Papadimitriou, D., and A. "GMPLS Segment Recovery", RFC 4873, May 2007.
Farrel, "GMPLS Segment
Recovery", RFC 4873,
May 2007.
[RFC4875] Aggarwal, R., [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa,
Papadimitriou, D., and S. "Extensions to Resource Reservation Protocol - Traffic
Yasukawa, "Extensions to Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Resource Reservation Switched Paths (LSPs)", RFC 4875, May 2007.
Protocol - Traffic
Engineering (RSVP-TE) for
Point-to-Multipoint TE
Label Switched Paths
(LSPs)", RFC 4875,
May 2007.
[RFC5036] Andersson, L., Minei, I., [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP
and B. Thomas, "LDP Specification", RFC 5036, October 2007.
Specification", RFC 5036,
October 2007.
[RFC5331] Aggarwal, R., Rekhter, Y., [RFC5331] Aggarwal, R., Rekhter, Y., and E. Rosen, "MPLS Upstream
and E. Rosen, "MPLS Label Assignment and Context-Specific Label Space", RFC
Upstream Label Assignment 5331, August 2008.
and Context-Specific Label
Space", RFC 5331,
August 2008.
[RFC5332] Eckert, T., Rosen, E., [RFC5332] Eckert, T., Rosen, E., Aggarwal, R., and Y. Rekhter, "MPLS
Aggarwal, R., and Y. Multicast Encapsulations", RFC 5332, August 2008.
Rekhter, "MPLS Multicast
Encapsulations", RFC 5332,
August 2008.
[RFC5654] Niven-Jenkins, B., [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
Brungard, D., Betts, M., and S. Ueno, "Requirements of an MPLS Transport Profile",
Sprecher, N., and S. Ueno, RFC 5654, September 2009.
"Requirements of an MPLS
Transport Profile",
RFC 5654, September 2009.
[RFC5921] Bocci, M., Bryant, S., [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Frost, D., Levrau, L., and Berger, "A Framework for MPLS in Transport Networks", RFC
L. Berger, "A Framework for 5921, July 2010.
MPLS in Transport
Networks", RFC 5921,
July 2010.
[RFC6374] Frost, D. and S. Bryant, [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay
"Packet Loss and Delay Measurement for MPLS Networks", RFC 6374, September 2011.
Measurement for MPLS
Networks", RFC 6374,
September 2011.
[RFC6375] Frost, D. and S. Bryant, "A [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay
Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks",
Measurement Profile for RFC 6375, September 2011.
MPLS-Based Transport
Networks", RFC 6375,
September 2011.
10.2. Informative References 10.2. Informative References
[G.7710] "ITU-T Recommendation [G.7710] ITU-T Recommendation G.7710/Y.1701 (07/2007), "Common
G.7710/Y.1701 (07/07), equipment management function requirements", 2007.
"Common equipment
management function
requirements"", 2005.
[I-D.hmk-mpls-tp-p2mp-oam-framework] Koike, Y., Hamano, T., and [G.780] ITU-T Recommendation G.780//Y.1351 (07/2010), "Terms and
M. Namiki, "A framework for definitions for synchronous digital hierarchy (SDH)
Point-to-Multipoint MPLS-TP networks", 2010.
OAM", draft-hmk-mpls-tp-
p2mp-oam-framework-01 (work
in progress),
November 2012.
[I-D.ietf-l2vpn-vpms-frmwk-requirements] Kamite, Y., JOUNAY, F., [G.798] ITU-T Recommendation G.798 (10/2010), "Characteristics of
Niven-Jenkins, B., optical transport network hierarchy equipment functional
Brungard, D., and L. Jin, blocks", 2010.
"Framework and Requirements
for Virtual Private
Multicast Service (VPMS)",
draft-ietf-l2vpn-vpms-
frmwk-requirements-05 (work
in progress), October 2012.
[I-D.ietf-pwe3-p2mp-pw] Sivabalan, S., Boutros, S., [I-D.hmk-mpls-tp-p2mp-oam-framework]
and L. Martini, "Signaling Koike, Y., Hamano, T., and M. Namiki, "Framework for
Root-Initiated Point-to- Point-to-Multipoint MPLS-TP OAM", draft-hmk-mpls-tp-p2mp-
Multipoint Pseudowire using oam-framework-02 (work in progress), February 2013.
LDP",
draft-ietf-pwe3-p2mp-pw-04
(work in progress),
March 2012.
[I-D.ietf-pwe3-p2mp-pw-requirements] Bocci, M., Heron, G., and [I-D.ietf-l2vpn-vpms-frmwk-requirements]
Y. Kamite, "Requirements Kamite, Y., JOUNAY, F., Niven-Jenkins, B., Brungard, D.,
and Framework for Point-to- and L. Jin, "Framework and Requirements for Virtual
Multipoint Pseudowires over Private Multicast Service (VPMS)", draft-ietf-l2vpn-vpms-
MPLS PSNs", draft-ietf- frmwk-requirements-05 (work in progress), October 2012.
pwe3-p2mp-pw-requirements-
05 (work in progress),
September 2011.
[I-D.raggarwa-pwe3-p2mp-pw-encaps] Aggarwal, R. and F. JOUNAY, [I-D.ietf-pwe3-p2mp-pw-requirements]
"Point-to-Multipoint Bocci, M., Heron, G., and Y. Kamite, "Requirements and
Pseudo-Wire Encapsulation", Framework for Point-to-Multipoint Pseudowires over MPLS
draft-raggarwa-pwe3-p2mp- PSNs", draft-ietf-pwe3-p2mp-pw-requirements-05 (work in
pw-encaps-01 (work in progress), September 2011.
progress), March 2010.
[RFC4377] Nadeau, T., Morrow, M., [I-D.ietf-pwe3-p2mp-pw]
Swallow, G., Allan, D., and Sivabalan, S., Boutros, S., and L. Martini, "Signaling
S. Matsushima, "Operations Root-Initiated Point-to-Multipoint Pseudowire using LDP",
and Management (OAM) draft-ietf-pwe3-p2mp-pw-04 (work in progress), March 2012.
Requirements for Multi-
Protocol Label Switched
(MPLS) Networks", RFC 4377,
February 2006.
[RFC5860] Vigoureux, M., Ward, D., [I-D.raggarwa-pwe3-p2mp-pw-encaps]
and M. Betts, "Requirements Aggarwal, R. and F. JOUNAY, "Point-to-Multipoint Pseudo-
for Operations, Wire Encapsulation", draft-raggarwa-pwe3-p2mp-pw-encaps-01
Administration, and (work in progress), March 2010.
Maintenance (OAM) in MPLS
Transport Networks",
RFC 5860, May 2010.
[RFC5951] Lam, K., Mansfield, S., and [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S.
E. Gray, "Network Matsushima, "Operations and Management (OAM) Requirements
Management Requirements for for Multi-Protocol Label Switched (MPLS) Networks", RFC
MPLS-based Transport 4377, February 2006.
Networks", RFC 5951,
September 2010.
[RFC6371] Busi, I. and D. Allan, [RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for
"Operations, Operations, Administration, and Maintenance (OAM) in MPLS
Administration, and Transport Networks", RFC 5860, May 2010.
Maintenance Framework for
MPLS-Based Transport
Networks", RFC 6371,
September 2011.
[RFC6372] Sprecher, N. and A. Farrel, [RFC5951] Lam, K., Mansfield, S., and E. Gray, "Network Management
"MPLS Transport Profile Requirements for MPLS-based Transport Networks", RFC 5951,
(MPLS-TP) Survivability September 2010.
Framework", RFC 6372,
September 2011.
[RFC6373] Andersson, L., Berger, L., [RFC6371] Busi, I. and D. Allan, "Operations, Administration, and
Fang, L., Bitar, N., and E. Maintenance Framework for MPLS-Based Transport Networks",
Gray, "MPLS Transport RFC 6371, September 2011.
Profile (MPLS-TP) Control
Plane Framework", RFC 6373,
September 2011.
[RFC6718] Muley, P., Aissaoui, M., [RFC6372] Sprecher, N. and A. Farrel, "MPLS Transport Profile (MPLS-
and M. Bocci, "Pseudowire TP) Survivability Framework", RFC 6372, September 2011.
Redundancy", RFC 6718,
August 2012. [RFC6373] Andersson, L., Berger, L., Fang, L., Bitar, N., and E.
Gray, "MPLS Transport Profile (MPLS-TP) Control Plane
Framework", RFC 6373, September 2011.
[RFC6718] Muley, P., Aissaoui, M., and M. Bocci, "Pseudowire
Redundancy", RFC 6718, August 2012.
Authors' Addresses Authors' Addresses
Dan Frost (editor) Dan Frost (editor)
Cisco Systems Cisco Systems
EMail: danfrost@cisco.com EMail: danfrost@cisco.com
Stewart Bryant (editor) Stewart Bryant (editor)
Cisco Systems Cisco Systems
Phone:
Fax:
EMail: stbryant@cisco.com EMail: stbryant@cisco.com
URI:
Matthew Bocci (editor) Matthew Bocci (editor)
Alcatel-Lucent Alcatel-Lucent
Voyager Place, Shoppenhangers Road Voyager Place, Shoppenhangers Road
Maidenhead, Berks SL6 2PJ Maidenhead, Berks SL6 2PJ
United Kingdom United Kingdom
EMail: matthew.bocci@alcatel-lucent.com EMail: matthew.bocci@alcatel-lucent.com
Lou Berger (editor) Lou Berger (editor)
 End of changes. 41 change blocks. 
187 lines changed or deleted 120 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/