draft-ietf-mpls-tp-rosetta-stone-05.txt   draft-ietf-mpls-tp-rosetta-stone-06.txt 
MPLS Working Group H. van Helvoort (Ed) MPLS Working Group H. van Helvoort (Ed)
Internet Draft Huawei Technologies Internet Draft Huawei Technologies
Intended status: Informational Intended status: Informational
Expires: July 2012July L. Andersson (Ed) Expires: January 2013 L. Andersson (Ed)
Ericsson Ericsson
N. Sprecher (Ed) N. Sprecher (Ed)
Nokia Siemens Networks Nokia Siemens Networks
January 17, 2012 July 16, 2012
A Thesaurus for the Terminology used in Multiprotocol Label A Thesaurus for the Terminology used in Multiprotocol Label
Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
Transport Network Recommendations. Transport Network Recommendations.
draft-ietf-mpls-tp-rosetta-stone-05 draft-ietf-mpls-tp-rosetta-stone-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the 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 39 skipping to change at page 1, line 39
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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 July 2012. This Internet-Draft will expire in January 2013.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
recommendations. recommendations.
It is important to note that MPLS-TP is applicable in a wider set of It is important to note that MPLS-TP is applicable in a wider set of
contexts than just Transport Networks. The definitions presented in contexts than just Transport Networks. The definitions presented in
this document do not provide exclusive nor complete interpretations this document do not provide exclusive nor complete interpretations
of MPLS-TP concepts. This document simply allows the MPLS-TP terms of MPLS-TP concepts. This document simply allows the MPLS-TP terms
to be applied within the Transport Network context. to be applied within the Transport Network context.
Table of Contents Table of Contents
1. Introduction 3 1. Introduction 4
1.1. Contributing Authors 4 1.1. Contributing Authors 4
1.2. Abbreviations 4 1.2. Abbreviations 4
SCC Signaling Communication Channel 5 SCC Signaling Communication Channel 5
2. Terminology 5 2. Terminology 5
2.1. MPLS-TP Terminology Sources 5 2.1. MPLS-TP Terminology Sources 5
2.2. ITU-T Transport Network Terminology Sources 5 2.2. ITU-T Transport Network Terminology Sources 5
2.3. Common Terminology Sources 5 2.3. Common Terminology Sources 6
3. Thesaurus 5 3. Thesaurus 6
3.1. Associated bidirectional path: 6 3.1. Associated bidirectional path: 6
3.2. Bidirectional path: 6 3.2. Bidirectional path: 6
3.3. Client layer network: 6 3.3. Client layer network: 6
3.4. Concatenated Segment: 6 3.4. Concatenated Segment: 6
3.5. Control Plane: 6 3.5. Control Plane: 6
3.6. Co-routed bidirectional path: 6 3.6. Co-routed bidirectional path: 7
3.7. Domain: 6 3.7. Domain: 7
3.8. Layer network: 7 3.8. Layer network: 7
3.9. Link: 7 3.9. Link: 7
3.10. MPLS-TP Logical Ring: 7 3.10. MPLS-TP Logical Ring: 8
3.11. MPLS-TP Physical Ring: 7 3.11. MPLS-TP Physical Ring: 8
3.12. MPLS-TP Ring Topology: 8 3.12. MPLS-TP Ring Topology: 8
3.13. Path: 8 3.13. Path: 8
3.14. Section Layer Network: 8 3.14. Section Layer Network: 8
3.15. Segment: 8 3.15. Segment: 9
3.16. Server layer: 8 3.16. Server layer: 9
3.17. Span: 9 3.17. Span: 9
3.18. Sublayer: 9 3.18. Sublayer: 9
3.19. Tandem Connection: 9 3.19. Tandem Connection: 9
3.20. Transport Network: 9 3.20. Transport Network: 9
3.21. Transport path: 9 3.21. Transport path: 10
3.22. Transport path layer: 10 3.22. Transport path layer: 10
3.23. Transport service layer: 10 3.23. Transport service layer: 10
3.24. Transmission media layer: 10 3.24. Transmission media layer: 10
3.25. Unidirectional path: 10 3.25. Unidirectional path: 10
3.26. Failure: 10 3.26. Failure: 10
3.27. Fault: 10 3.27. Fault: 10
3.28. Defect: 10 3.28. Defect: 11
3.29. MPLS Transport Profile (MPLS-TP): 11 3.29. MPLS Transport Profile (MPLS-TP): 11
3.30. MPLS Section: 11 3.30. MPLS Section: 11
3.31. MPLS-TP NE: 11 3.31. MPLS-TP NE: 11
3.32. MPLS-TP network: 11 3.32. MPLS-TP network: 11
3.33. Equipment Management Function (EMF): 11 3.33. Equipment Management Function (EMF): 11
3.34. Data Communication Network (DCN): 11 3.34. Data Communication Network (DCN): 11
3.35. Communication Channel (CC): 11 3.35. Communication Channel (CC): 11
3.36. Embedded Communication Channel (ECC): 11 3.36. Embedded Communication Channel (ECC): 12
3.37. Management Communication Channel (MCC): 12 3.37. Management Communication Channel (MCC): 12
3.38. Management Communication Network (MCN): 12 3.38. Management Communication Network (MCN): 12
3.39. Signaling Communication Channel (SCC): 12 3.39. Signaling Communication Channel (SCC): 12
3.40. Signaling Communication Network (SCN): 12 3.40. Signaling Communication Network (SCN): 12
3.41. Operations System (OS): 12 3.41. Operations System (OS): 12
3.42. Maintenance Entity 12 3.42. OAM flow: 12
3.43. Maintenance End Points (MEPs) 13 3.43. Maintenance Entity Group (MEG): 13
3.44. Maintenance Intermediate Points (MIPs) 13 3.44. Maintenance Entity (ME): 13
3.45. Server MEPs 14 3.45. Maintenance Entity Group End Point (MEP): 13
4. Guidance on the Application of this Thesaurus 18 3.46. Maintenance Entity Group Intermediate Point (MIP): 14
5. Management Considerations 18 3.47. Server MEPs: 14
6. Security Considerations 18 3.48. Link recovery: 15
7. IANA Considerations 18 3.49. Segment recovery: 15
8. Acknowledgments 19 3.50. End-to-end recovery: 15
9. References 19 3.51. Transport Entity: 15
9.1. Normative References 19 3.52. Working Entity: 15
9.2. Informative References 19 3.53. Protection Entity: 15
3.54. Recovery entity: 15
4. Guidance on the Application of this Thesaurus 16
5. Management Considerations 16
6. Security Considerations 16
7. IANA Considerations 16
8. Acknowledgments 17
9. References 17
9.1. Normative References 17
9.2. Informative References 17
1. Introduction 1. Introduction
Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
developed by the IETF to facilitate the Operation, Administration developed by the IETF to facilitate the Operation, Administration
and Management of Label Switched Paths (LSPs) in a Transport Network and Management of Label Switched Paths (LSPs) in a Transport Network
environment as defined by the ITU-T. environment as defined by the ITU-T.
The ITU-T has specified a Transport Network architecture for the The ITU-T has specified a Transport Network architecture for the
transfer of signals from different technologies. This architecture transfer of signals from different technologies. This architecture
skipping to change at page 5, line 33 skipping to change at page 5, line 43
MPLS-TP terminology is principally defined in [RFC3031]. Other MPLS-TP terminology is principally defined in [RFC3031]. Other
documents provide further key definitions including [RFC4397], and documents provide further key definitions including [RFC4397], and
[RFC....]. [RFC....].
2.2. ITU-T Transport Network Terminology Sources 2.2. ITU-T Transport Network Terminology Sources
The ITU-T Transport Network is specified in a number of The ITU-T Transport Network is specified in a number of
recommendations: generic functional architectures and requirements recommendations: generic functional architectures and requirements
are specified in [ITU-T_G.805], [ITU-T_G.806], and [ITU-T_G.872]. are specified in [ITU-T_G.805], [ITU-T_G.806], and [ITU-T_G.872].
[ITU-T_G.8101] contains an overview of the Terms and Definitions for ITU-T Recommendation [ITU-T_G.8101] contains an overview of the
transport MPLS. Terms and Definitions for transport MPLS.
2.3. Common Terminology Sources 2.3. Common Terminology Sources
The work in this document builds on the shared view of MPLS The work in this document builds on the shared view of MPLS
requirements. requirements.
3. Thesaurus 3. Thesaurus
[editor: from [RFC5654] mpls-tp-requirements == complete]
3.1. Associated bidirectional path: 3.1. Associated bidirectional path:
A path that supports traffic flow in both directions but that is A path that supports traffic flow in both directions but that is
constructed from a pair of unidirectional paths (one for each constructed from a pair of unidirectional paths (one for each
direction) that are associated with one another at the path's direction) that are associated with one another at the path's
ingress/egress points. The forward and backward directions are ingress/egress points. The forward and backward directions are
setup, monitored, and protected independently. As a consequence, setup, monitored, and protected independently. As a consequence,
they may or may not follow the same route (links and nodes) across they may or may not follow the same route (links and nodes) across
the network. the network.
skipping to change at page 9, line 36 skipping to change at page 9, line 44
3.19. Tandem Connection: 3.19. Tandem Connection:
A tandem connection is an arbitrary part of a transport path that A tandem connection is an arbitrary part of a transport path that
can be monitored (via OAM) independently from the end-to-end can be monitored (via OAM) independently from the end-to-end
monitoring (OAM). It may be a monitored segment, a monitored monitoring (OAM). It may be a monitored segment, a monitored
concatenated segment or any other monitored ordered sequence of concatenated segment or any other monitored ordered sequence of
contiguous hops and/or segments (and their interconnecting nodes) of contiguous hops and/or segments (and their interconnecting nodes) of
a transport path. a transport path.
[editor: this is not in [RFC5654] but added for completeness]
3.20. Transport Network: 3.20. Transport Network:
A Transport Network provides transmission of traffic between A Transport Network provides transmission of traffic between
attached client devices by establishing and maintaining point-to- attached client devices by establishing and maintaining point-to-
point or point-to-multipoint connections between such devices. A point or point-to-multipoint connections between such devices. A
Transport Network is independent of any higher-layer network that Transport Network is independent of any higher-layer network that
may exist between clients, except to the extent required to supply may exist between clients, except to the extent required to supply
this transmission service. In addition to client traffic, a this transmission service. In addition to client traffic, a
Transport Network may carry traffic to facilitate its own operation, Transport Network may carry traffic to facilitate its own operation,
such as that required to support connection control, network such as that required to support connection control, network
skipping to change at page 10, line 32 skipping to change at page 10, line 36
3.24. Transmission media layer: 3.24. Transmission media layer:
A layer network, consisting of a section layer network and a A layer network, consisting of a section layer network and a
physical layer network as defined in [ITU-T_G.805], that provides physical layer network as defined in [ITU-T_G.805], that provides
sections (two-port point-to-point connections) to carry the sections (two-port point-to-point connections) to carry the
aggregate of network-transport path or network-service layers on aggregate of network-transport path or network-service layers on
various physical media. various physical media.
3.25. Unidirectional path: 3.25. Unidirectional path:
A path that supports traffic flow in only one direction. A Unidirectional Path is a path that supports traffic flow in only
one direction.
[editor: from: [RFC5860] == complete]
3.26. Failure: 3.26. Failure:
[editor: this is not in [RFC5860] but added for completeness]
The fault cause persisted long enough to consider the ability of an The fault cause persisted long enough to consider the ability of an
item to perform a required function to be terminated. The item may item to perform a required function to be terminated. The item may
be considered as failed; a fault has now been detected. See also be considered as failed; a fault has now been detected. See also
[ITU-T_G.806]. [ITU-T_G.806].
3.27. Fault: 3.27. Fault:
The inability of a function to perform a required action. This does A Fault is the inability of a function to perform a required action.
not include an inability due to preventive maintenance, lack of This does not include an inability due to preventive maintenance,
external resources, or planned actions. See also [ITU-T_G.806]. lack of external resources, or planned actions. See also [ITU-
T_G.806].
3.28. Defect: 3.28. Defect:
The situation for which density of anomalies has reached a level The situation for which the density of anomalies has reached a level
where the ability to perform a required function has been where the ability to perform a required function has been
interrupted. Defects are used as input for PM, the control of interrupted. Defects are used as input for PM, the control of
consequent actions, and the determination of fault cause. See also consequent actions, and the determination of fault cause. See also
[ITU-T_G.806]. [ITU-T_G.806].
3.29. MPLS Transport Profile (MPLS-TP): 3.29. MPLS Transport Profile (MPLS-TP):
The set of MPLS functions used to support packet transport services The set of MPLS functions used to support packet transport services
and network operations. and network operations.
3.30. MPLS Section: 3.30. MPLS Section:
A network segment between two LSRs that are immediately adjacent at A network segment between two LSRs that are immediately adjacent at
the MPLS layer. the MPLS layer.
[editor: from: [RFC5921] and [RFC5951] == complete]
3.31. MPLS-TP NE: 3.31. MPLS-TP NE:
A network element (NE) that supports MPLS-TP functions. A network element (NE) that supports MPLS-TP functions.
3.32. MPLS-TP network: 3.32. MPLS-TP network:
A network in which MPLS-TP NEs are deployed A network in which MPLS-TP NEs are deployed
3.33. Equipment Management Function (EMF): 3.33. Equipment Management Function (EMF):
skipping to change at page 12, line 40 skipping to change at page 12, line 42
A DCN supporting control plane communication is referred to as a A DCN supporting control plane communication is referred to as a
Signaling Communication Network (SCN). Signaling Communication Network (SCN).
3.41. Operations System (OS): 3.41. Operations System (OS):
A system that performs the functions that support processing of A system that performs the functions that support processing of
information related to operations, administration, maintenance, and information related to operations, administration, maintenance, and
provisioning (OAM&P) for the networks, including surveillance and provisioning (OAM&P) for the networks, including surveillance and
testing functions to support customer access maintenance. testing functions to support customer access maintenance.
[editor: from: OAM Framework RFC [RFC6371] == complete]
3.42. OAM flow: 3.42. OAM flow:
The set of all OAM packets originating with a specific source MEP An OAM flow is the set of all OAM packets originating with a
that instrument one direction of a MEG (or possibly both in the specific source MEP that instrument one direction of a MEG (or
special case of data plane loopback). possibly both in the special case of data plane loopback).
3.43. Maintenance Entity 3.43. Maintenance Entity Group (MEG):
A Maintenance Entity Group is defined, for the purpose of connection
monitoring, between a set of connection points within a connection.
This set of connection points may be located at the boundary of one
administrative domain or a protection domain, or the boundaries of
two adjacent administrative domains. The MEG may consist of one or
more Maintenance Entities (ME).
In an MPLS-TP layer network an MEG consists of only one ME.
3.44. Maintenance Entity (ME):
A Maintenance Entity can be viewed as the association of two (or A Maintenance Entity can be viewed as the association of two (or
more) Maintenance End Points (MEPs), that should be configured and more) MEG End Points (MEPs), that should be configured and managed
managed in order to bound the OAM responsibilities of an OAM flow in order to bound the OAM responsibilities of an OAM flow across a
across a network or sub-network, i.e. a transport path or segment, network or sub-network, i.e. a transport path or segment, in the
in the specific layer network that is being monitored and managed. specific layer network that is being monitored and managed.
A Maintenance Entity may be defined to monitor and manage A Maintenance Entity may be defined to monitor and manage
bidirectional or unidirectional point-to-point connectivity or bidirectional or unidirectional point-to-point connectivity or
point-to-multipoint connectivity in an MPLS-TP layer network. point-to-multipoint connectivity in an MPLS-TP layer network.
[editor: should the following be included?]
Therefore, in the context of MPLS-TP LSP or PW Maintenance Entity Therefore, in the context of MPLS-TP LSP or PW Maintenance Entity
(defined below) LERs and T-PEs can be MEPs while LSRs and S-PEs can (defined below) LERs and T-PEs can be MEPs while LSRs and S-PEs can
be MIPs. In the case of Tandem Connection Maintenance Entity be MIPs. In the case of Tandem Connection Maintenance Entity
(defined below), LSRs and S-PEs can be either MEPs or MIPs. (defined below), LSRs and S-PEs can be either MEPs or MIPs.
The following properties apply to all MPLS-TP MEs: The following properties apply to all MPLS-TP MEs:
o OAM entities can be nested but not overlapped. o OAM entities can be nested but not overlapped.
o Each OAM flow is associated to a unique Maintenance Entity. o Each OAM flow is associated to a unique Maintenance Entity.
o OAM packets are subject to the same forwarding treatment as the o OAM packets are subject to the same forwarding treatment as the
data traffic, but they are distinct from the data traffic. data traffic, but they are distinct from the data traffic.
3.44. Maintenance End Points (MEPs) 3.45. Maintenance Entity Group End Point (MEP):
Maintenance End Points (MEPs) are the end points of a pre-configured Maintenance Entity Group End Points (MEPs) are the end points of a
(through the management or control planes) ME. MEPs are responsible pre-configured (through the management or control planes) ME. MEPs
for activating and controlling all of the OAM functionality for the are responsible for activating and controlling all of the OAM
ME. A MEP may initiate an OAM packet to be transferred to its functionality for the ME. A MEP may initiate an OAM packet to be
corresponding MEP, or to an intermediate MIP that is part of the ME. transferred to its corresponding MEP, or to an intermediate MIP that
is part of the ME.
A MEP terminates all the OAM packets that it receives corresponding A MEP terminates all the OAM packets that it receives corresponding
to its ME and does not forward them further along the path. to its ME and does not forward them further along the path.
All OAM packets coming to a MEP source are tunnelled via label All OAM packets coming to a MEP source are tunnelled via label
stacking and are not processed within the ME as they belong either stacking and are not processed within the ME as they belong either
to the client network layers or to an higher TCM level. to the client network layers or to an higher TCM level.
A MEP in a tandem connection is not coincident with the termination A MEP in a tandem connection is not coincident with the termination
of the MPLS-TP transport path (LSP or PW), though it can monitor its of the MPLS-TP transport path (LSP or PW), though it can monitor its
connectivity (e.g. count packets). A MEP of an MPLS-TP network connectivity (e.g. count packets). A MEP of an MPLS-TP network
transport path is coincident with transport path termination and transport path is coincident with transport path termination and
monitors its connectivity (e.g. count packets). monitors its connectivity (e.g. count packets).
MPLS-TP MEP notifies a fault indication to the MPLS-TP client layer MPLS-TP MEP notifies a fault indication to the MPLS-TP client layer
network. network.
3.45. Maintenance Intermediate Points (MIPs) 3.46. Maintenance Entity Group Intermediate Point (MIP):
A Maintenance Intermediate Point (MIP) is a point between the two A Maintenance Entity Group Intermediate Point (MIP) is a point
MEPs in an ME and is capable of responding to some OAM packets and between the two MEPs in an ME and is capable of responding to some
forwarding all OAM packets while ensuring fate sharing with data OAM packets and forwarding all OAM packets while ensuring fate
plane packets. A MIP responds only to OAM packets that are sent on sharing with data plane packets. A MIP responds only to OAM packets
the ME it belongs to and that are addressed to the MIP, it does not that are sent on the ME it belongs to and that are addressed to the
initiate OAM messages. MIP, it does not initiate OAM messages.
3.46. Server MEPs 3.47. Server MEPs:
A server MEP is a MEP of an ME that is defined in a layer network A server MEP is a MEP of an ME that is defined in a layer network
below the MPLS-TP layer network being referenced. A server MEP below the MPLS-TP layer network being referenced. A server MEP
coincides with either a MIP or a MEP in the client (MPLS-TP) layer coincides with either a MIP or a MEP in the client (MPLS-TP) layer
network. network.
For example, a server MEP can be either: For example, a server MEP can be either:
. A termination point of a physical link (e.g. 802.3), an SDH VC or . A termination point of a physical link (e.g. 802.3), an SDH VC or
OTH ODU for the MPLS-TP Section layer network, defined in [5] OTH ODU for the MPLS-TP Section layer network, defined in [5]
skipping to change at page 14, line 39 skipping to change at page 15, line 9
. An MPLS-TP LSP MEP for MPLS-TP PWs, defined in [5] section 3.4.; . An MPLS-TP LSP MEP for MPLS-TP PWs, defined in [5] section 3.4.;
. An MPLS-TP TCM MEP for higher-level TCMs, defined in [5] sections . An MPLS-TP TCM MEP for higher-level TCMs, defined in [5] sections
3.3. and 3.5. 3.3. and 3.5.
The server MEP can run appropriate OAM functions for fault The server MEP can run appropriate OAM functions for fault
detection, and notifies a fault indication to the MPLS-TP layer detection, and notifies a fault indication to the MPLS-TP layer
network. network.
[editor: check definitions in [RFC6372] ] 3.48. Link recovery:
o MPLS-TP link recovery refers to the recovery of an individual MPLS-TP link recovery refers to the recovery of an individual link
link (and hence all or a subset of the LSPs routed over the link) (and hence all or a subset of the LSPs routed over the link) between
between two MPLS-TP nodes. For example, link recovery may be two MPLS-TP nodes. For example, link recovery may be provided by
provided by server layer recovery. server layer recovery.
o Segment recovery refers to the recovery of an LSP segment (i.e., 3.49. Segment recovery:
Segment recovery refers to the recovery of an LSP segment (i.e.,
segment and concatenated segment in the language of [RFC5654]) segment and concatenated segment in the language of [RFC5654])
between two nodes and is used to recover from the failure of one or between two nodes and is used to recover from the failure of one or
more links or nodes. more links or nodes.
o End-to-end recovery refers to the recovery of an entire LSP, from 3.50. End-to-end recovery:
its ingress to its egress node.
o A "Transport Entity" is a node, link, transport path segment,
concatenated transport path segment, or entire transport path.
o A "Working Entity" is a transport entity that carries traffic
during normal network operation.
o A "Protection Entity" is a transport entity that is pre-allocated
and used to protect and transport traffic when the working entity
fails.
o A "Recovery Entity" is a transport entity that is used to recover
and transport traffic when the working entity fails.
[editor: the following are definitions from G.8101 which should be
defined only if they will cause misunderstanding. It is not usefull
to define them if the definition is the same in IETF and ITU-T, TBD]
===== [ITU-T_G.8101] =====
3.1 access point
3.2 adapted information
3.3 characteristic information
3.4 client/server relationship
3.5 connection
3.6 connection point
3.9 forward direction
3.12 link connection
3.13 matrix
3.14 network
3.15 network connection
3.16 network operator
3.17 port
3.18 reference point
3.19 service provider
3.20 subnetwork
3.21 subnetwork connection
3.22 termination connection point
3.23 trail
3.24 trail termination
3.25 trail termination point
3.26 transport
3.27 transport entity
3.28 transport processing function
3.29 unidirectional connection
3.30 unidirectional trail
3.31 Z layer
Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in ITU-T Rec. G.809:
3.34 adaptation
3.37 client/server relationship (relationship between layer
networks)
3.56 traffic unit
Transport MPLS (MPLS-TP) Recommendations uses the following term
defined in ITU-T Rec. G.8010/Y.1306:
3.59 point-to-point Ethernet connection
Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in [ITU-T_Y.1711]:
3.60 backward direction
3.65 user-plane
Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in [ITU-T_Y.1720]:
3.66 1+1 protection
3.67 1:1 protection
3.68 bidirectional protection switching
3.69 bridge
3.71 extra traffic
3.72 failure
3.73 forced switch for working LSP
3.74 hold-off time
3.75 manual switch
3.76 MPLS protection domain
3.77 non-revertive protection switching
3.78 no request
3.79 packet 1+1 protection
3.80 path switch LSR
3.81 path merge LSR
3.82 protection LSP
3.83 protection switching
3.84 rerouting
3.85 revertive protection switching
3.86 selector
3.87 shared mesh protection
3.88 Shared Risk Group (SRG)
3.89 sink of the protection domain End-to-end recovery refers to the recovery of an entire LSP, from
its ingress to its egress node.
3.90 source of the protection domain 3.51. Transport Entity:
3.91 unidirectional protection switching A "Transport Entity" is a node, link, transport path segment,
concatenated transport path segment, or entire transport path.
3.92 wait to restore 3.52. Working Entity:
3.93 wait to restore timer A "Working Entity" is a transport entity that carries traffic during
normal network operation.
3.94 working LSP 3.53. Protection Entity:
Transport MPLS (MPLS-TP) Recommendations uses the following terms A "Protection Entity" is a transport entity that is pre-allocated
defined in [ITU-T_Y.1731]: and used to protect and transport traffic when the working entity
fails.
3.95 in-service OAM 3.54. Recovery entity:
===== end of [ITU-T_G.8101] ===== A "Recovery Entity" is a transport entity that is used to recover
and transport traffic when the working entity fails.
4. Guidance on the Application of this Thesaurus 4. Guidance on the Application of this Thesaurus
As discussed in the introduction to this document, this thesaurus is As discussed in the introduction to this document, this thesaurus is
intended to bring the concepts and terms associated with MPLS-TP intended to bring the concepts and terms associated with MPLS-TP
into the context of the ITU-T's Transport Network architecture. into the context of the ITU-T's Transport Network architecture.
Thus, it should help those familiar with MPLS to see how they may Thus, it should help those familiar with MPLS to see how they may
use the features and functions of the Transport Network in order to use the features and functions of the Transport Network in order to
meet the requirements of MPLS-TP. meet the requirements of MPLS-TP.
skipping to change at page 20, line 26 skipping to change at page 18, line 15
[ITU-T_G.8101] ITU-T Recommendation G.8101/Y.1355 (12/2006), Terms [ITU-T_G.8101] ITU-T Recommendation G.8101/Y.1355 (12/2006), Terms
and definitions for transport MPLS. and definitions for transport MPLS.
[ITU-T_G.805] ITU-T Recommendation G.805 (03/2000), Generic [ITU-T_G.805] ITU-T Recommendation G.805 (03/2000), Generic
functional architecture of transport networks. functional architecture of transport networks.
[ITU-T_G.806] ITU-T Recommendation G.806 (03/2006), Characteristics [ITU-T_G.806] ITU-T Recommendation G.806 (03/2006), Characteristics
of transport equipment - Description methodology and of transport equipment - Description methodology and
generic functionality. generic functionality.
[ITU-T_Y.1711] ITU-T Recommendation Y.1711 (10/2005) Operation &
Maintenance mechanism for MPLS networks.
[ITU-T_Y.1720] ITU-T Recommendation Y.1720 (02/2008), Protection
switching for MPLS networks.
[ITU-T_Y.1731] ITU-T Recommendation Y.1731 (02/2008), OAM functions
and mechanisms for Ethernet based networks.
[ITU-T_G.872] ITU-T Recommendation G.872 (11/2001), Architecture of [ITU-T_G.872] ITU-T Recommendation G.872 (11/2001), Architecture of
optical transport networks. optical transport networks.
[ITU-T G.7710] ITU-T Recommendation G.7710 (07/2007), Common [ITU-T G.7710] ITU-T Recommendation G.7710 (07/2007), Common
equipment management function requirements equipment management function requirements
[ITU-T Y.2611] ITU-T Recommendation Y.2611 (12/2006), High-level [ITU-T Y.2611] ITU-T Recommendation Y.2611 (12/2006), High-level
architecture of future packet-based networks architecture of future packet-based networks
Authors' Addresses Authors' Addresses
 End of changes. 45 change blocks. 
237 lines changed or deleted 104 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/