draft-ietf-mpls-tp-rosetta-stone-02.txt   draft-ietf-mpls-tp-rosetta-stone-03.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: November 2010 L. Andersson (Ed) Expires: May 2011 L. Andersson (Ed)
Ericsson Ericsson
N. Sprecher (Ed) N. Sprecher (Ed)
Nokia Siemens Networks Nokia Siemens Networks
May 18, 2010 November 28, 2010
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-02 draft-ietf-mpls-tp-rosetta-stone-03
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 3, line 30 skipping to change at page 3, line 30
3.31. MPLS-TP network: 11 3.31. MPLS-TP network: 11
3.32. Equipment Management Function (EMF): 11 3.32. Equipment Management Function (EMF): 11
3.33. Data Communication Network (DCN): 11 3.33. Data Communication Network (DCN): 11
3.34. Communication Channel (CC): 11 3.34. Communication Channel (CC): 11
3.35. Embedded Communication Channel (ECC): 12 3.35. Embedded Communication Channel (ECC): 12
3.36. Management Communication Channel (MCC): 12 3.36. Management Communication Channel (MCC): 12
3.37. Management Communication Network (MCN): 12 3.37. Management Communication Network (MCN): 12
3.38. Signaling Communication Channel (SCC): 12 3.38. Signaling Communication Channel (SCC): 12
3.39. Signaling Communication Network (SCN): 12 3.39. Signaling Communication Network (SCN): 12
3.40. Operations System (OS): 12 3.40. Operations System (OS): 12
3.41. Maintenance Entity 13 3.41. Maintenance Entity 12
3.42. Maintenance End Points (MEPs) 13 3.42. Maintenance End Points (MEPs) 13
3.43. Maintenance Intermediate Points (MIPs) 14 3.43. Maintenance Intermediate Points (MIPs) 14
3.44. Server MEPs 14 3.44. Server MEPs 14
4. Guidance on the Application of this Thesaurus 18 4. Guidance on the Application of this Thesaurus 18
5. Management Considerations 18 5. Management Considerations 18
6. Security Considerations 19 6. Security Considerations 18
7. IANA Considerations 19 7. IANA Considerations 19
8. Acknowledgments 19 8. Acknowledgments 19
9. References 19 9. References 19
9.1. Normative References 19 9.1. Normative References 19
9.2. Informative References 20 9.2. Informative References 20
Authors' Addresses 20 Authors' Addresses 20
Contributing Authors' Addresses 21 Contributing Authors' Addresses 21
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
forms the basis of many Recommendations within the ITU-T. forms the basis of many Recommendations within the ITU-T.
Because of the difference in historic background of MPLS, and Because of the difference in historic background of MPLS, and
inherently MPLS-TP (the Internet) and the Transport Network (ITU inherently MPLS-TP (the Internet) and the Transport Network (ITU
skipping to change at page 7, line 7 skipping to change at page 7, line 7
3.6. Co-routed bidirectional path: 3.6. Co-routed bidirectional path:
A path where the forward and backward directions follow the same A path where the forward and backward directions follow the same
route (links and nodes) across the network. Both directions are route (links and nodes) across the network. Both directions are
setup, monitored and protected as a single entity. A transport setup, monitored and protected as a single entity. A transport
network path is typically co-routed. network path is typically co-routed.
3.7. Domain: 3.7. Domain:
A domain represents a collection of entities (for example network A domain represents a collection of entities (for example network
elements) that are grouped for a particular purpose, examples of elements) that are grouped for a particular purpose, examples of
which are administrative and/or managerial responsibilities, trust which are administrative and/or managerial responsibilities, trust
relationships, addressing schemes, infrastructure capabilities, relationships, addressing schemes, infrastructure capabilities,
aggregation, survivability techniques, distributions of control aggregation, survivability techniques, distributions of control
functionality, etc. Examples of such domains include IGP areas and functionality, etc. Examples of such domains include IGP areas and
Autonomous Systems. Autonomous Systems.
3.8. Layer network: 3.8. Layer network:
Layer network is defined in [ITU-T_G.805]. A layer network provides Layer network is defined in [ITU-T_G.805]. A layer network provides
skipping to change at page 9, line 36 skipping to change at page 9, line 36
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] [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,
skipping to change at page 10, line 34 skipping to change at page 10, line 34
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 path that supports traffic flow in only one direction.
[editor: from: draft-ietf-mpls-tp-oam-requirements [1]] [editor: from: [RFC5860] ]
3.26. Failure: 3.26. Failure:
[editor: this is not in [1] BUT added for completeness] [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 The inability of a function to perform a required action. This does
not include an inability due to preventive maintenance, lack of not include an inability due to preventive maintenance, lack of
skipping to change at page 11, line 23 skipping to change at page 11, line 23
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: draft-ietf-mpls-tp-framework [2]] [editor: from: [RFC5921] and [RFC5951] ]
[editor: from: draft-gray-mpls-tp-nm-req [3]]
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 5 skipping to change at page 11, line 51
management communications related to the management plane, for management communications related to the management plane, for
distributed signaling communications related to the control plane, distributed signaling communications related to the control plane,
and other operations communications (e.g., order-wire/voice and other operations communications (e.g., order-wire/voice
communications, software downloads, etc.). communications, software downloads, etc.).
3.35. Communication Channel (CC): 3.35. Communication Channel (CC):
A logical channel between network elements (NEs) that can be used - A logical channel between network elements (NEs) that can be used -
e.g. - for management plane application or control plane e.g. - for management plane application or control plane
applications. The physical channel supporting the CC is technology applications. The physical channel supporting the CC is technology
specific. See [3] APPENDIX A specific. See [RFC5951] APPENDIX A
3.36. Embedded Communication Channel (ECC): 3.36. Embedded Communication Channel (ECC):
A logical operations channel between network elements (NEs) that can A logical operations channel between network elements (NEs) that can
be utilized by multiple applications (e.g., management plane be utilized by multiple applications (e.g., management plane
applications, control plane applications, etc.). The physical applications, control plane applications, etc.). The physical
channel supporting the ECC is technology specific. An example of channel supporting the ECC is technology specific. An example of
physical channels supporting the ECC is a DCC channel within SDH. physical channels supporting the ECC is a DCC channel within SDH.
3.37. Management Communication Channel (MCC): 3.37. Management Communication Channel (MCC):
skipping to change at page 12, line 42 skipping to change at page 12, line 40
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: draft-busi-mpls-tp-oam-framework-00 [4]] [editor: from: draft-busi-mpls-tp-oam-framework-00 [1] ]
[editor: MPLS Section: already defined in 3.30]
[editor: OAM flow: to be added in future revision of this document.] [editor: OAM flow: to be added in future revision of this document.]
[editor: Tandem Connection: already defined in 3.19]
3.42. Maintenance Entity 3.42. Maintenance Entity
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) Maintenance End Points (MEPs), that should be configured and
managed in order to bound the OAM responsibilities of an OAM flow managed in order to bound the OAM responsibilities of an OAM flow
[editor: definition?] across a network or sub-network, i.e. a [editor: definition?] across a network or sub-network, i.e. a
transport path or segment, in the specific layer network that is transport path or segment, in the specific layer network that is
being monitored and managed. being monitored and managed.
A Maintenance Entity may be defined to monitor and manage A Maintenance Entity may be defined to monitor and manage
skipping to change at page 16, line 4 skipping to change at page 15, line 45
3.25 trail termination point 3.25 trail termination point
3.26 transport 3.26 transport
3.27 transport entity 3.27 transport entity
3.28 transport processing function 3.28 transport processing function
3.29 unidirectional connection 3.29 unidirectional connection
3.30 unidirectional trail 3.30 unidirectional trail
3.31 Z layer 3.31 Z layer
Transport MPLS (MPLS-TP) Recommendations uses the following terms
Transport MPLS (T-MPLS) Recommendations uses the following terms
defined in ITU-T Rec. G.809: defined in ITU-T Rec. G.809:
3.33 access point 3.33 access point
3.34 adaptation 3.34 adaptation
3.35 adapted information 3.35 adapted information
3.36 characteristic information 3.36 characteristic information
skipping to change at page 16, line 33 skipping to change at page 16, line 29
3.52 port 3.52 port
3.53 reference point 3.53 reference point
3.56 traffic unit 3.56 traffic unit
3.57 transport 3.57 transport
3.58 transport entity 3.58 transport entity
Transport MPLS (T-MPLS) Recommendations uses the following term Transport MPLS (MPLS-TP) Recommendations uses the following term
defined in ITU-T Rec. G.8010/Y.1306: defined in ITU-T Rec. G.8010/Y.1306:
3.59 point-to-point Ethernet connection 3.59 point-to-point Ethernet connection
Transport MPLS (T-MPLS) Recommendations uses the following terms Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in [ITU-T_Y.1711]: defined in [ITU-T_Y.1711]:
3.60 backward direction 3.60 backward direction
3.62 client/server (relationship between layer networks) 3.62 client/server (relationship between layer networks)
3.63 failure 3.63 failure
3.64 forward direction 3.64 forward direction
3.65 user-plane 3.65 user-plane
Transport MPLS (T-MPLS) Recommendations uses the following terms
Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in [ITU-T_Y.1720]: defined in [ITU-T_Y.1720]:
3.66 1+1 protection 3.66 1+1 protection
3.67 1:1 protection 3.67 1:1 protection
3.68 bidirectional protection switching 3.68 bidirectional protection switching
3.69 bridge 3.69 bridge
3.71 extra traffic 3.71 extra traffic
3.72 failure 3.72 failure
skipping to change at page 18, line 4 skipping to change at page 17, line 45
3.84 rerouting 3.84 rerouting
3.85 revertive protection switching 3.85 revertive protection switching
3.86 selector 3.86 selector
3.87 shared mesh protection 3.87 shared mesh protection
3.88 Shared Risk Group (SRG) 3.88 Shared Risk Group (SRG)
3.89 sink of the protection domain 3.89 sink of the protection domain
3.90 source of the protection domain 3.90 source of the protection domain
3.91 unidirectional protection switching 3.91 unidirectional protection switching
3.92 wait to restore 3.92 wait to restore
3.93 wait to restore timer 3.93 wait to restore timer
3.94 working LSP 3.94 working LSP
Transport MPLS (T-MPLS) Recommendations uses the following terms Transport MPLS (MPLS-TP) Recommendations uses the following terms
defined in [ITU-T_Y.1731]: defined in [ITU-T_Y.1731]:
3.95 in-service OAM 3.95 in-service OAM
===== end of [ITU-T_G.8101] ===== ===== end of [ITU-T_G.8101] =====
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
skipping to change at page 19, line 23 skipping to change at page 19, line 15
7. IANA Considerations 7. IANA Considerations
To be incorporated in a future revision of this document To be incorporated in a future revision of this document
<<TBA>> <<TBA>>
8. Acknowledgments 8. Acknowledgments
The authors would like to thank all members of the teams (the Joint The authors would like to thank all members of the teams (the Joint
Working Team, the MPLS Interoperability Design Team in IETF and the Working Team, the MPLS Interoperability Design Team in IETF and the
T-MPLS Ad Hoc Group in ITU-T) involved in the definition and MPLS-TP Ad Hoc Group in ITU-T) involved in the definition and
specification of MPLS Transport Profile. specification of MPLS Transport Profile.
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Vigoureux, M., Betts, M., Ward, D., "Requirements for OAM in [1] Busi, I., Niven-Jenkins, B., et al., "MPLS-TP OAM Framework
MPLS Transport Networks", draft-ietf-mpls-tp-oam-requirements- and Overview", draft-ietf-mpls-tp-oam-framework-01, july 2009
03, august 2009
[2] Bocci, M., Bryant, S., Levrau, L., "A Framework for MPLS in [RFC5654] B. Niven-Jenkins, et al., "Requirements of an MPLS
Transport Networks'', draft-ietf-mpls-tp-framework-06, october Transport Profile", September 2009
2009
[3] Gray, E., Mansfield, S., et al., ''MPLS TP Network Management [RFC5921] Bocci, M., Bryant, S., Levrau, L., "A Framework for MPLS
Requirements'', draft-ietf-mpls-tp-nm-req-06, october 2009 in Transport Networks", July 2010
[4] Busi, I., Niven-Jenkins, B., et al., ''MPLS-TP OAM Framework [RFC5860] Vigoureux, M., Betts, M., Ward, D., "Requirements for OAM
and Overview'', draft-ietf-mpls-tp-oam-framework-01, july 2009 in MPLS Transport Networks", May 2010
[RFC5654] B. Niven-Jenkins, et al., ''Requirements of an MPLS [RFC5951] Gray, E., Mansfield, S., et al., "MPLS TP Network
Transport Profile'', September 2009 Management Requirements", September 2010
[RFC3031] E. Rosen, etal., ''Requirements of an MPLS Transport [RFC3031] E. Rosen, etal., "Requirements of an MPLS Transport
Profile'', january 2001 Profile", january 2001
[RFC4397] I. Bryskin, A. Farrel, ''A Lexicography for the [RFC4397] I. Bryskin, A. Farrel, "A Lexicography for the
Interpretation of Generalized Multiprotocol Label Interpretation of Generalized Multiprotocol Label
Switching (GMPLS) Terminology within the Context of the Switching (GMPLS) Terminology within the Context of the
ITU-T's Automatically Switched Optical Network (ASON) ITU-T's Automatically Switched Optical Network (ASON)
Architecture'', february 2006 Architecture", february 2006
9.2. Informative References 9.2. Informative References
For information on the availability of the following documents, For information on the availability of the following documents,
please see http://www.itu.int please see http://www.itu.int
[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 & [ITU-T_Y.1711] ITU-T Recommendation Y.1711 (10/2005) Operation &
Maintenance mechanism for MPLS networks. Maintenance mechanism for MPLS networks.
[ITU-T_Y.1720] ITU-T Recommendation Y.1720 (02/2008), Protection [ITU-T_Y.1720] ITU-T Recommendation Y.1720 (02/2008), Protection
switching for MPLS networks. switching for MPLS networks.
[ITU-T_Y.1731] ITU-T Recommendation Y.1731 (02/2008), OAM functions [ITU-T_Y.1731] ITU-T Recommendation Y.1731 (02/2008), OAM functions
and mechanisms for Ethernet based networks. and mechanisms for Ethernet based networks.
 End of changes. 33 change blocks. 
45 lines changed or deleted 37 lines changed or added

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