draft-ietf-mpls-tp-framework-02.txt   draft-ietf-mpls-tp-framework-03.txt 
MPLS Working Group M. Bocci, Ed. MPLS Working Group M. Bocci, Ed.
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track S. Bryant, Ed. Intended status: Standards Track S. Bryant, Ed.
Expires: January 11, 2010 Cisco Systems Expires: March 1, 2010 Cisco Systems
L. Levrau L. Levrau
Alcatel-Lucent Alcatel-Lucent
July 10, 2009 August 28, 2009
A Framework for MPLS in Transport Networks A Framework for MPLS in Transport Networks
draft-ietf-mpls-tp-framework-02 draft-ietf-mpls-tp-framework-03
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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 11, 2010. This Internet-Draft will expire on March 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 26 skipping to change at page 3, line 7
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119]. document are to be interpreted as described in RFC2119 [RFC2119].
Although this document is not a protocol specification, these key Although this document is not a protocol specification, these key
words are to be interpreted as instructions to the protocol designers words are to be interpreted as instructions to the protocol designers
producing solutions that satisfy the architectural concepts set out producing solutions that satisfy the architectural concepts set out
in this document. in this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Motivation and Background . . . . . . . . . . . . . . . . 3 1.1. Motivation and Background . . . . . . . . . . . . . . . . 4
1.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Applicability . . . . . . . . . . . . . . . . . . . . . . 5
1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7
2. Introduction to Requirements . . . . . . . . . . . . . . . . . 6 1.4.1. MPLS Transport Profile. . . . . . . . . . . . . . . . 7
3. Transport Profile Overview . . . . . . . . . . . . . . . . . . 7 1.4.2. MPLS-TP Label Switched Path . . . . . . . . . . . . . 7
3.1. Packet Transport Services . . . . . . . . . . . . . . . . 7 1.4.3. MPLS-TP PE . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Architecture . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.4. MPLS-TP Provider Router . . . . . . . . . . . . . . . 8
3.3. MPLS-TP Forwarding Domain . . . . . . . . . . . . . . . . 10 1.4.5. Additional Definitions and Terminology . . . . . . . . 8
3.4. MPLS-TP LSP Clients . . . . . . . . . . . . . . . . . . . 12 2. Introduction to Requirements . . . . . . . . . . . . . . . . . 8
3.4.1. Network Layer Transport Service . . . . . . . . . . . 12 3. Transport Profile Overview . . . . . . . . . . . . . . . . . . 9
3.5. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 16 3.1. Packet Transport Services . . . . . . . . . . . . . . . . 9
3.6. Operations, Administration and Maintenance (OAM) . . . . . 17 3.2. Architecture . . . . . . . . . . . . . . . . . . . . . . . 10
3.7. Generic Associated Channel (G-ACh) . . . . . . . . . . . . 21 3.3. MPLS-TP Forwarding Domain . . . . . . . . . . . . . . . . 12
3.8. Control Plane . . . . . . . . . . . . . . . . . . . . . . 24 3.4. MPLS-TP LSP Clients . . . . . . . . . . . . . . . . . . . 14
3.8.1. PW Control Plane . . . . . . . . . . . . . . . . . . . 26 3.4.1. Network Layer Transport Service . . . . . . . . . . . 14
3.8.2. LSP Control Plane . . . . . . . . . . . . . . . . . . 26 3.5. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 18
3.9. Static Operation of LSPs and PWs . . . . . . . . . . . . . 27 3.6. Operations, Administration and Maintenance (OAM) . . . . . 19
3.10. Survivability . . . . . . . . . . . . . . . . . . . . . . 27 3.7. Generic Associated Channel (G-ACh) . . . . . . . . . . . . 23
3.11. Network Management . . . . . . . . . . . . . . . . . . . . 28 3.8. Control Plane . . . . . . . . . . . . . . . . . . . . . . 26
4. Security Considerations . . . . . . . . . . . . . . . . . . . 29 3.8.1. PW Control Plane . . . . . . . . . . . . . . . . . . . 28
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 3.8.2. LSP Control Plane . . . . . . . . . . . . . . . . . . 28
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30 3.9. Static Operation of LSPs and PWs . . . . . . . . . . . . . 29
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.10. Survivability . . . . . . . . . . . . . . . . . . . . . . 29
7.1. Normative References . . . . . . . . . . . . . . . . . . . 30 3.11. Network Management . . . . . . . . . . . . . . . . . . . . 30
7.2. Informative References . . . . . . . . . . . . . . . . . . 33 4. Security Considerations . . . . . . . . . . . . . . . . . . . 31
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1. Normative References . . . . . . . . . . . . . . . . . . . 32
7.2. Informative References . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
1.1. Motivation and Background 1.1. Motivation and Background
This document describes a framework for a Multiprotocol Label This document describes a framework for a Multiprotocol Label
Switching Transport Profile (MPLS-TP). It presents the architectural Switching Transport Profile (MPLS-TP). It presents the architectural
framework for MPLS-TP, defining those elements of MPLS applicable to framework for MPLS-TP, defining those elements of MPLS applicable to
supporting the requirements in [I-D.ietf-mpls-tp-requirements] and supporting the requirements in [I-D.ietf-mpls-tp-requirements] and
what new protocol elements are required. what new protocol elements are required.
skipping to change at page 6, line 8 skipping to change at page 7, line 8
[I-D.ietf-mpls-tp-requirements] and what new protocol elements are [I-D.ietf-mpls-tp-requirements] and what new protocol elements are
required. required.
This document describes the architecture for MPLS-TP when the LSP This document describes the architecture for MPLS-TP when the LSP
client is a pseudowire, and when the LSP is providing a network layer client is a pseudowire, and when the LSP is providing a network layer
transport service. transport service.
1.4. Terminology 1.4. Terminology
Term Definition Term Definition
------- ------------------------------------------------------------- ---------------- ------------------------------------------
LSP Label Switched Path LSP Label Switched Path
MPLS-TP MPLS Transport profile MPLS-TP MPLS Transport profile
SDH Synchronous Digital Hierarchy SDH Synchronous Digital Hierarchy
ATM Asynchronous Transfer Mode ATM Asynchronous Transfer Mode
OTN Optical Transport Network OTN Optical Transport Network
cl-ps Connectionless - Packet Switched cl-ps Connectionless - Packet Switched
co-cs Connection Oriented - Circuit Switched co-cs Connection Oriented - Circuit Switched
co-ps Connection Oriented - Packet Switched co-ps Connection Oriented - Packet Switched
OAM Operations, Administration and Maintenance OAM Operations, Administration and Maintenance
G-ACh Generic Associated Channel G-ACh Generic Associated Channel
GAL Generic Alert Label GAL Generic Alert Label
MEP Maintenance End Point MEP Maintenance End Point
MIP Maintenance Intermediate Point MIP Maintenance Intermediate Point
APS Automatic Protection Switching APS Automatic Protection Switching
SCC Signaling Communication Channel SCC Signaling Communication Channel
MCC Management Communication Channel MCC Management Communication Channel
EMF Equipment Management Function EMF Equipment Management Function
FM Fault Management FM Fault Management
CM Configuration Management CM Configuration Management
PM Performance Management PM Performance Management
MPLS-TP MPLS Transport Profile. The set of MPLS functions that meet LSR Label Switch Router.
the requirements in [I-D.ietf-mpls-tp-requirements]. MPLS-TP PE MPLS-TP Provider Edge
MPLS-TP P Router An MPLS-TP Provider (P) router
Detailed definitions and additional terminology may be found in 1.4.1. MPLS Transport Profile.
The MPLS Transport Profile (MPLS-TP) is the set of MPLS functions
that meet the requirements in [I-D.ietf-mpls-tp-requirements].
1.4.2. MPLS-TP Label Switched Path
An MPLS-TP Label Switched Path (MPLS-TP LSP) is an LSP that conforms
to a subset of the capabilities of an MPLS LSP. Specifically, it is
an MPLS LSP that is used in an MPLS transport network as defined by
this document to meet the requirements set out in
[I-D.ietf-mpls-tp-requirements]. The characteristics of an MPLS-TP
LSP are primarily that it:
1. Uses a subset of the MPLS OAM tools defined as described in
[I-D.ietf-mpls-tp-oam-framework].
2. Supports only 1+1, 1:1, and 1:N protection functions.
3. Is traffic engineered.
4. Is established and maintained using GMPLS protocols when a
control plane is used.
1.4.3. MPLS-TP PE
An MPLS-TP Provider Edge (MPLS-TP PE) is an MPLS-TP LSR that adapts
client traffic and encapsulate it to be carried over an MPLS-TP LSP.
Encapsulation may be as simple as pushing a label, or it may require
the use of a pseudowire. An MPLS-TP PE exists at the interface
between a pair of layer networks.
1.4.4. MPLS-TP Provider Router
An MPLS-TP Provider router (MPLS-TP P Router) is an MPLS-TP LSR that
does not provide MPLS-TP PE functionality. An MPLS-TP P router
switches LSPs which carry client traffic, but do not adapt the client
traffic and encapsulate it to be carried over an MPLS-TP LSP.
Note that the use of the term "router" in this context is historic
and neither requires nor precludes the ability to perform IP
forwarding.
1.4.5. Additional Definitions and Terminology
Detailed definitions and additional terminology may be found in .
[I-D.ietf-mpls-tp-requirements]. [I-D.ietf-mpls-tp-requirements].
2. Introduction to Requirements 2. Introduction to Requirements
The requirements for MPLS-TP are specified in The requirements for MPLS-TP are specified in
[I-D.ietf-mpls-tp-requirements], [I-D.ietf-mpls-tp-oam-requirements], [I-D.ietf-mpls-tp-requirements], [I-D.ietf-mpls-tp-oam-requirements],
and [I-D.ietf-mpls-tp-nm-req]. This section provides a brief and [I-D.ietf-mpls-tp-nm-req]. This section provides a brief
reminder to guide the reader. It is not intended as a substitute for reminder to guide the reader. It is not intended as a substitute for
these documents. these documents.
skipping to change at page 33, line 28 skipping to change at page 35, line 28
[I-D.ietf-mpls-tp-nm-req] Mansfield, S. and K. Lam, "MPLS [I-D.ietf-mpls-tp-nm-req] Mansfield, S. and K. Lam, "MPLS
TP Network Management TP Network Management
Requirements", Requirements",
draft-ietf-mpls-tp-nm-req-02 draft-ietf-mpls-tp-nm-req-02
(work in progress), June 2009. (work in progress), June 2009.
[I-D.ietf-mpls-tp-oam-framework] Busi, I. and B. Niven-Jenkins, [I-D.ietf-mpls-tp-oam-framework] Busi, I. and B. Niven-Jenkins,
"MPLS-TP OAM Framework and "MPLS-TP OAM Framework and
Overview", draft-ietf-mpls-tp- Overview", draft-ietf-mpls-tp-
oam-framework-00 (work in oam-framework-01 (work in
progress), March 2009. progress), July 2009.
[I-D.ietf-mpls-tp-oam-requirements] Vigoureux, M., Ward, D., and M. [I-D.ietf-mpls-tp-oam-requirements] Vigoureux, M., Ward, D., and M.
Betts, "Requirements for OAM in Betts, "Requirements for OAM in
MPLS Transport Networks", draft- MPLS Transport Networks", draft-
ietf-mpls-tp-oam-requirements-02 ietf-mpls-tp-oam-requirements-02
(work in progress), June 2009. (work in progress), June 2009.
[I-D.ietf-mpls-tp-requirements] Niven-Jenkins, B., Brungard, D., [I-D.ietf-mpls-tp-requirements] Niven-Jenkins, B., Brungard, D.,
Betts, M., Sprecher, N., and S. Betts, M., Sprecher, N., and S.
Ueno, "MPLS-TP Requirements", dr Ueno, "MPLS-TP Requirements", dr
aft-ietf-mpls-tp-requirements-09 aft-ietf-mpls-tp-requirements-10
(work in progress), June 2009. (work in progress), August 2009.
[I-D.ietf-mpls-tp-survive-fwk] Sprecher, N., Farrel, A., and H. [I-D.ietf-mpls-tp-survive-fwk] Sprecher, N., Farrel, A., and H.
Shah, "Multiprotocol Label Shah, "Multiprotocol Label
Switching Transport Profile Switching Transport Profile
Survivability Framework", draft- Survivability Framework", draft-
ietf-mpls-tp-survive-fwk-00 ietf-mpls-tp-survive-fwk-00
(work in progress), April 2009. (work in progress), April 2009.
[I-D.ietf-pwe3-dynamic-ms-pw] Martini, L., Bocci, M., Bitar, [I-D.ietf-pwe3-dynamic-ms-pw] Martini, L., Bocci, M., Bitar,
N., Shah, H., Aissaoui, M., and N., Shah, H., Aissaoui, M., and
F. Balus, "Dynamic Placement of F. Balus, "Dynamic Placement of
Multi Segment Pseudo Wires", Multi Segment Pseudo Wires",
draft-ietf-pwe3-dynamic-ms-pw-09 draft-ietf-pwe3-dynamic-ms-pw-09
(work in progress), March 2009. (work in progress), March 2009.
[I-D.ietf-pwe3-ms-pw-arch] Bocci, M. and S. Bryant, "An [I-D.ietf-pwe3-ms-pw-arch] Bocci, M. and S. Bryant, "An
Architecture for Multi-Segment Architecture for Multi-Segment
Pseudowire Emulation Edge-to- Pseudowire Emulation Edge-to-
Edge", Edge",
draft-ietf-pwe3-ms-pw-arch-06 draft-ietf-pwe3-ms-pw-arch-07
(work in progress), (work in progress), July 2009.
February 2009.
[I-D.ietf-pwe3-redundancy] Muley, P. and M. Bocci, [I-D.ietf-pwe3-redundancy] Muley, P. and M. Bocci,
"Pseudowire (PW) Redundancy", "Pseudowire (PW) Redundancy",
draft-ietf-pwe3-redundancy-01 draft-ietf-pwe3-redundancy-01
(work in progress), (work in progress),
September 2008. September 2008.
[I-D.ietf-pwe3-segmented-pw] Martini, L., Nadeau, T., Metz, [I-D.ietf-pwe3-segmented-pw] Martini, L., Nadeau, T., Metz,
C., Duckett, M., Bocci, M., C., Duckett, M., Bocci, M.,
Balus, F., and M. Aissaoui, Balus, F., and M. Aissaoui,
"Segmented Pseudowire", "Segmented Pseudowire",
draft-ietf-pwe3-segmented-pw-12 draft-ietf-pwe3-segmented-pw-13
(work in progress), June 2009. (work in progress), August 2009.
[RFC4377] Nadeau, T., Morrow, M., Swallow, [RFC4377] Nadeau, T., Morrow, M., Swallow,
G., Allan, D., and S. G., Allan, D., and S.
Matsushima, "Operations and Matsushima, "Operations and
Management (OAM) Requirements Management (OAM) Requirements
for Multi-Protocol Label for Multi-Protocol Label
Switched (MPLS) Networks", Switched (MPLS) Networks",
RFC 4377, February 2006. RFC 4377, February 2006.
[RFC4379] Kompella, K. and G. Swallow, [RFC4379] Kompella, K. and G. Swallow,
 End of changes. 12 change blocks. 
44 lines changed or deleted 94 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/