draft-ietf-mpls-tp-p2mp-framework-05.txt   draft-ietf-mpls-tp-p2mp-framework-06.txt 
MPLS Working Group D. Frost MPLS Working Group D. Frost
Internet-Draft S. Bryant Internet-Draft Blue Sun
Intended status: Informational Cisco Systems Intended status: Informational S. Bryant
Expires: May 22, 2014 M. Bocci Expires: July 21, 2014 Cisco Systems
M. Bocci
Alcatel-Lucent Alcatel-Lucent
L. Berger L. Berger
LabN Consulting LabN Consulting
November 18, 2013 January 17, 2014
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-05 draft-ietf-mpls-tp-p2mp-framework-06
Abstract Abstract
The Multiprotocol Label Switching Transport Profile is the common set The Multiprotocol Label Switching Transport Profile is the common set
of MPLS protocol functions defined to enable the construction and of MPLS protocol functions defined to enable the construction and
operation of packet transport networks. The MPLS-TP supports both operation of packet transport networks. The MPLS-TP supports both
point-to-point and point-to-multipoint transport paths. This point-to-point and point-to-multipoint transport paths. This
document defines the elements and functions of the MPLS-TP 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.
skipping to change at page 1, line 40 skipping to change at page 1, line 41
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 May 22, 2014. This Internet-Draft will expire on July 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.1. Additional Definitions and Terminology . . . . . . . 3 1.2.1. Additional Definitions and Terminology . . . . . . . 3
1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
2. MPLS Transport Profile Point-to-Multipoint Requirements . . . 3 2. MPLS-TP P2MP Requirements . . . . . . . . . . . . . . . . . . 4
3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. MPLS-TP Encapsulation and Forwarding . . . . . . . . . . 6 3.1. MPLS-TP Encapsulation and Forwarding . . . . . . . . . . 6
4. Operations, Administration and Maintenance . . . . . . . . . 6 4. Operations, Administration and Maintenance . . . . . . . . . 6
5. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Point-to-Multipoint LSP Control Plane . . . . . . . . . . 7 5.1. P2MP LSP Control Plane . . . . . . . . . . . . . . . . . 7
5.2. Point-to-Multipoint PW Control Plane . . . . . . . . . . 8 5.2. P2MP PW Control Plane . . . . . . . . . . . . . . . . . . 8
6. Survivability . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Survivability . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Network Management . . . . . . . . . . . . . . . . . . . . . 8 7. Network Management . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . 9 10.1. Normative References . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . 10 10.2. Informative References . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The Multiprotocol Label Switching Transport Profile is the common set The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the
of MPLS protocol functions defined to meet the requirements specified common set of MPLS protocol functions defined to meet the
in [RFC5654]. The MPLS-TP Framework [RFC5921] provides an overall requirements specified in [RFC5654]. The MPLS-TP Framework [RFC5921]
introduction to the MPLS-TP and defines the general architecture of provides an overall introduction to the MPLS-TP and defines the
the Transport Profile, as well as those aspects specific to point-to- general architecture of the Transport Profile, as well as those
point transport paths. The purpose of this document is to define the aspects specific to point-to-point transport paths. The purpose of
elements and functions of the MPLS-TP architecture applicable this document is to define the elements and functions of the MPLS-TP
specifically to supporting point-to-multipoint transport paths. architecture applicable specifically to supporting point-to-
multipoint transport paths.
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
Term Definition Term Definition
------- --------------------------------------------------- ------- ---------------------------------------------------
CE Customer Edge CE Customer Edge
GMPLS Generalized MPLS
LDP Label Distribution Protocol
LSP Label Switched Path LSP Label Switched Path
LSR Label Switching Router LSR Label Switching Router
MEG Maintenance Entity Group MEG Maintenance Entity Group
MEP Maintenance Entity Group End Point MEP Maintenance Entity Group End Point
MIP Maintenance Entity Group Intermediate Point MIP Maintenance Entity Group Intermediate Point
MPLS Multiprotocol Label Switching
MPLS-TE MPLS Traffic Engineering MPLS-TE MPLS Traffic Engineering
MPLS-TP MPLS Transport Profile MPLS-TP MPLS Transport Profile
OAM Operations, Administration and Maintenance OAM Operations, Administration, and Maintenance
OTN Optical Transport Network OTN Optical Transport Network
P2MP Point-to-multipoint P2MP Point-to-multipoint
PW Pseudowire PW Pseudowire
RSVP-TE Resource Reservation Protocol - Traffic Engineering RSVP-TE Resource Reservation Protocol - Traffic Engineering
SDH Synchronous Digital Hierarchy SDH Synchronous Digital Hierarchy
tLDP Targeted LDP tLDP Targeted LDP
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. P2MP MPLS TE-LSP support is discussed in [RFC4875] and networks. Traffic Engineered P2MP LSP support is discussed in
[RFC5332], and P2MP PW support is being developed based on [RFC4875] and [RFC5332], and P2MP PW support is being developed based
[I-D.ietf-pwe3-p2mp-pw-requirements] and on [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 point-to- transport technologies such as Optical Transport Network point-to-
multipoint [G.798] and drop-and-continue [G.780], and thus supports multipoint [G.798] and drop-and-continue [G.780], and thus supports
the same class of traditional applications, e.g., video distribution. the same class of traditional applications, e.g., video distribution.
There is no definition for MPLS TE-LSP support of multipoint-to- The scope of this document is limited to point-to-multipoint
multipoint connectivity and none is anticipated. functions and it does not discuss multipoint-to-multipoint support.
2. MPLS Transport Profile Point-to-Multipoint Requirements 2. MPLS-TP P2MP 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. This summary does not include the complete list of requirements. This summary does not include the
[RFC2119] conformance language used in original documents as this [RFC2119] conformance language used in original documents as this
document is not authoritative. document is not authoritative.
From [RFC5654]: From [RFC5654]:
skipping to change at page 5, line 36 skipping to change at page 5, line 40
o For unidirectional (P2P and point-to-multipoint (P2MP)) o For unidirectional (P2P and point-to-multipoint (P2MP))
connection, proactive measurement of packet loss and loss ratio is connection, proactive measurement of packet loss and loss ratio is
required. required.
o For a unidirectional (P2P and P2MP) connection, on-demand o For a unidirectional (P2P and P2MP) connection, on-demand
measurement of delay measurement is required. measurement of delay measurement is required.
3. Architecture 3. Architecture
The overall architecture of the MPLS Transport Profile is defined in The overall architecture of the MPLS-TP is defined in [RFC5921]. The
[RFC5921]. The architecture for point-to-multipoint MPLS-TP architecture for point-to-multipoint MPLS-TP comprises the following
comprises the following additional elements and functions: additional elements and functions:
o Unidirectional point-to-multipoint LSPs o Unidirectional point-to-multipoint LSPs
o Unidirectional point-to-multipoint PWs o Unidirectional point-to-multipoint PWs
o Optional point-to-multipoint LSP and PW control planes o Optional point-to-multipoint LSP and PW control planes
o Survivability, network management, and Operations, Administration o Survivability, network management, and Operations, Administration
and Maintenance functions for point-to-multipoint PWs and LSPs and Maintenance functions for point-to-multipoint PWs and LSPs
skipping to change at page 7, line 38 skipping to change at page 7, line 41
The PW and LSP control planes, collectively, must satisfy the MPLS-TP The PW and LSP control planes, collectively, must satisfy the MPLS-TP
control-plane requirements. As with P2P services, when P2MP client control-plane requirements. As with P2P services, when P2MP client
services are provided directly via LSPs, all requirements must be services are provided directly via LSPs, all requirements must be
satisfied by the LSP control plane. When client services are satisfied by the LSP control plane. When client services are
provided via PWs, the PW and LSP control planes can operate in provided via PWs, the PW and LSP control planes can operate in
combination, and some functions may be satisfied via the PW control combination, and some functions may be satisfied via the PW control
plane while others are provided to PWs by the LSP control plane. plane while others are provided to PWs by the LSP control plane.
This is particularly noteworthy for P2MP recovery. This is particularly noteworthy for P2MP recovery.
5.1. Point-to-Multipoint LSP Control Plane 5.1. P2MP LSP Control Plane
The MPLS-TP control plane for point-to-multipoint LSPs uses GMPLS and The MPLS-TP control plane for P2MP LSPs uses GMPLS and is based on
is based on RSVP-TE for point-to-multipoint LSPs as defined in RSVP-TE for P2MP LSPs as defined in [RFC4875]. A detailed listing of
[RFC4875]. A detailed listing of how GMPLS satisfies MPLS-TP control how GMPLS satisfies MPLS-TP control plane requirements is provided in
plane requirements is provided in [RFC6373]. [RFC6373].
Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS [RFC6373]notes that recovery techniques for Traffic Engineered P2MP
recovery, [RFC4872] and [RFC4873], do not explicitly cover their LSPs are not formally defined, and such that a definition is needed.
interactions. MPLS-TP requires a formal definition of recovery A formal definition will be based on existing RFCs and may not
techniques for P2MP LSPs. Such a formal definition will be based on require any new protocol mechanisms but, nonetheless, should be
existing RFCs and may not require any new protocol mechanisms but, documented. GMPLS recovery is defined in [RFC4872] and [RFC4873].
nonetheless, should be documented. Protection of P2MP LSPs is also Protection of P2MP LSPs is also discussed in [RFC6372] Section 4.7.3.
discussed in [RFC6372] Section 4.7.3.
5.2. Point-to-Multipoint PW Control Plane 5.2. P2MP PW Control Plane
The MPLS-TP control plane for point-to-multipoint PWs should be based The MPLS-TP control plane for P2MP PWs should be based on the LDP
on the LDP control protocol used for point-to-point PWs [RFC4447], control protocol used for point-to-point PWs [RFC4447], with updates
with updates as required for P2MP applications. A detailed as required for P2MP applications. A detailed specification of the
specification of the control plane for P2MP PWs is for further study. control plane for P2MP PWs is for further study.
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. For 1+1, the approach is for the root 1:1 protection architecture. For 1+1, the approach is for the root
of the 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. For 1:1, from one entity according to some predetermined criteria. For 1:1,
skipping to change at page 9, line 15 skipping to change at page 9, line 18
identifies areas where additional MIB modules are required. While identifies areas where additional MIB modules are required. While
the document does not consider P2MP transport paths, it does provide the document does not consider P2MP transport paths, it does provide
a foundation for an analysis of areas where MIB module modification a foundation for an analysis of areas where MIB module modification
and addition may be needed to fully support P2MP transport paths. and addition may be needed to fully support P2MP transport paths.
There has also been work in the MPLS working group on a P2MP specific There has also been work in the MPLS working group on a P2MP specific
MIB, [I-D.ietf-mpls-p2mp-te-mib]. MIB, [I-D.ietf-mpls-p2mp-te-mib].
8. Security Considerations 8. Security Considerations
General security considerations for MPLS-TP are covered in [RFC5921]. General security considerations for MPLS-TP are covered in [RFC5921].
Additional security considerations for point-to-multipoint LSPs are Additional security considerations for P2MP LSPs are provided in
provided in [RFC4875]. This document introduces no new security [RFC4875]. This document introduces no new security considerations
considerations beyond those covered in those documents. beyond those covered in those documents.
9. IANA Considerations 9. IANA Considerations
There are no requests for IANA actions in this document. There are no requests for IANA actions in this document.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE [RFC4872] Lang, J., Rekhter, Y., and D. Papadimitriou, "RSVP-TE
skipping to change at page 11, line 40 skipping to change at page 11, line 40
Gray, "MPLS Transport Profile (MPLS-TP) Control Plane Gray, "MPLS Transport Profile (MPLS-TP) Control Plane
Framework", RFC 6373, September 2011. Framework", RFC 6373, September 2011.
[RFC6639] King, D. and M. Venkatesan, "Multiprotocol Label Switching [RFC6639] King, D. and M. Venkatesan, "Multiprotocol Label Switching
Transport Profile (MPLS-TP) MIB-Based Management Transport Profile (MPLS-TP) MIB-Based Management
Overview", RFC 6639, June 2012. Overview", RFC 6639, June 2012.
Authors' Addresses Authors' Addresses
Dan Frost Dan Frost
Cisco Systems Blue Sun
EMail: danfrost@cisco.com EMail: frost@mm.st
Stewart Bryant Stewart Bryant
Cisco Systems Cisco Systems
EMail: stbryant@cisco.com EMail: stbryant@cisco.com
Matthew Bocci Matthew Bocci
Alcatel-Lucent Alcatel-Lucent
Voyager Place, Shoppenhangers Road Voyager Place, Shoppenhangers Road
Maidenhead, Berks SL6 2PJ Maidenhead, Berks SL6 2PJ
United Kingdom United Kingdom
 End of changes. 23 change blocks. 
54 lines changed or deleted 52 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/