1、 International Telecommunication Union ITU-T G.8110.1/Y.1370.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2011) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Packet over Transport aspects MPLS over Transport aspects SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERN
2、ET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Transport Architecture of the Multi-Protocol Label Switching transport profile layer network Recommendation ITU-T G.8110.1/Y.1370.1 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS I
3、NTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPH
4、ONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 DIGITAL S
5、ECTIONS AND DIGITAL LINE SYSTEM G.900G.999 MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE GENERIC AND USER-RELATED ASPECTS G.1000G.1999 TRANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DATA OVER TRANSPORT GENERIC ASPECTS G.7000G.7999 PACKET OVER TRANSPORT ASPECTS G.8000G.8999 Ethernet over Transport a
6、spects G.8000G.8099 MPLS over Transport aspects G.8100G.8199Quality and availability targets G.8200G.8299 Service Management G.8600G.8699 ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) i Recommendation ITU-T
7、 G.8110.1/Y.1370.1 Architecture of the Multi-Protocol Label Switching transport profile layer network Summary Recommendation ITU-T G.8110.1/Y.1370.1 provides functional components, based on Recommendation ITU-T G.805, that allow the Multi-Protocol Label Switching Transport Profile (MPLS-TP) to be mo
8、delled in a way that is consistent with the description of other transport technologies defined by the ITU-T, (e.g., the synchronous digital hierarchy (SDH) and the optical transport network (OTN), to simplify integration with other transport technologies. This Recommendation provides a representati
9、on of the MPLS-TP technology using the methodologies that have been used for other transport technologies (e.g., SDH, OTN and Ethernet). NOTE This ITU-T Recommendation is intended to be aligned with the IETF MPLS RFCs normatively referenced by this Recommendation. In this Recommendation the architec
10、ture of MPLS-TP forwarding, operation, administration and maintenance (OAM), and network survivability is modelled from a network-level viewpoint. The description of the control plane and management plane aspects of MPLS-TP is outside the scope of this Recommendation. The functional components descr
11、ibed in this Recommendation also support the architecture for point-to-multipoint (p2mp) MPLS-TP label switched paths (LSPs), in compliance with IETF RFC 5331 and IETF RFC 5332. This edition of ITU-T G.8110.1/Y.1370.1 includes the changes introduced by Erratum 1 (09/2012). History Edition Recommenda
12、tion Approval Study Group 1.0 ITU-T G.8110.1/Y.1370.1 2006-11-10 15 1.1 ITU-T G.8110.1/Y.1370.1 (2006) Amd. 1 2007-07-29 15 2.0 ITU-T G.8110.1/Y.1370.1 2011-12-16 15 ii Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized a
13、gency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a vi
14、ew to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommenda
15、tions is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for concise
16、ness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendati
17、on is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. IN
18、TELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights,
19、 whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers a
20、re cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permiss
21、ion of ITU. Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) iii Table of Contents Page 1 Scope 1 2 References. 2 3 Definitions 4 4 Abbreviations and acronyms 5 5 Conventions 8 6 Functional architecture of MPLS Transport Profile (MPLS-TP) networks . 8 6.1 MPLS-TP network layered structure 9 6.2 MPLS-TP layer
22、network . 11 6.3 MPLS-TP layer network partitioning . 16 6.4 MPLS-TP network topology 16 6.5 MPLS-TP label behaviour 20 7 Server/client associations 20 7.1 MT/client adaptation 20 7.2 MT/MT adaptation . 21 7.3 Server/MT adaptation . 22 8 MPLS-TP OAM architecture 24 8.1 General . 24 8.2 MPLS-TP conne
23、ction and trail supervision . 26 8.3 MPLS-TP maintenance entity group monitoring . 28 8.4 MPLS-TP MIP 29 8.5 Bandwidth considerations with MPLS-TP OAM . 30 9 MPLS-TP survivability techniques. 30 10 MPLS-TP Diff-Serv architecture 30 10.1 Short-pipe model 31 10.2 Uniform model . 31 11 MPLS-TP TTL beha
24、viour 32 12 Security aspects 32 Annex A Default configuration options for MPLS-TP in a transport network application 33 Appendix I An example of MPLS-TP layer structure 35 Bibliography. 41 Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) 1 Recommendation ITU-T G.8110.1/Y.1370.1 Architecture of the Multi-Proto
25、col Label Switching transport profile layer network11 Scope This Recommendation provides the functional components, based on ITU-T G.805, that are necessary to describe the deployment of Multi-Protocol Label Switching Transport Profile (MPLS-TP) in a transport network. This model allows MPLS-TP to b
26、e modelled in a way that is consistent with the description of other transport technologies defined by ITU-T, (e.g., the synchronous digital hierarchy (SDH), the optical transport network (OTN), etc.). _ 1Cisco Systems has expressed concerns that the following text has been removed from the consente
27、d text: “This Recommendation complies with the transport profile of MPLS Architecture as defined by the IETF. In the event of a difference between this ITU-T Recommendation and any of the normatively referenced IETF RFCs, the RFCs will take precedence.“ as without this statement, interoperability is
28、sues may arise. 1France Telecom Orange has expressed its concerns that the following text has been removed from the consented text: “This Recommendation complies with the transport profile of MPLS Architecture as defined by the IETF. In the event of a difference between this ITU-T Recommendation and
29、 any of the normatively referenced IETF RFCs, the RFCs will take precedence.“ as without this statement, interoperability issues may arise. 1Juniper Networks has stated its concerns about the changes to the consented text of this Recommendation that it believes have introduced potential issues in im
30、plementation, deployment, and interoperability. Juniper Networks believes that it is important to provide a clarification that in the event of any misalignment, the definition of MPLS provided in the referenced RFCs takes precedence over any description or modeling of MPLS-TP provided in this Recomm
31、endation. 1Nokia Siemens Networks has expressed concerns that the following text has been removed from the consented text: “This Recommendation complies with the transport profile of MPLS Architecture as defined by the IETF. In the event of a difference between this ITU-T Recommendation and any of t
32、he normatively referenced IETF RFCs, the RFCs will take precedence.“ as without this statement, interoperability issues may arise. 1Telefon AB - LM Ericsson has expressed concerns that the following text has been removed from the consented text: “This Recommendation complies with the transport profi
33、le of MPLS Architecture as defined by the IETF. In the event of a difference between this ITU-T Recommendation and any of the normatively referenced IETF RFCs, the RFCs will take precedence.“ as without this statement, interoperability issues may arise. 1Verizon Communications has expressed concerns
34、 that the following text has been removed from the consented ITU-T G.8110.1 text: “This Recommendation complies with the transport profile of MPLS Architecture as defined by the IETF. In the event of a difference between this ITU-T Recommendation and any of the normatively referenced IETF RFCs, the
35、RFCs will take precedence.“ Without this statement, interoperability issues may arise. 2 Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) This Recommendation provides a representation of the MPLS-TP technology using the methodologies that have been used for other transport technologies, (e.g., SDH, OTN and Et
36、hernet).2MPLS-TP is a connection-oriented packet-switched transport layer network technology that uses pseudowires (PWs) and MPLS-TP label switched paths (LSPs). The MPLS-TP is a profile of the MPLS that supports deployment in transport networks and allows operations in a manner consistent with othe
37、r transport technologies. Its operation is independent of the mechanisms used for configuration and management. In some applications, the data plane only supports forwarding based on the MPLS label; it does not support IP forwarding. The architecture of the MPLS-TP forwarding, operation, administrat
38、ion and maintenance (OAM), and network survivability, is modelled from a network-level viewpoint. The description of the control plane and management plane aspects of the MPLS-TP is outside the scope of this Recommendation. The functional components described in this Recommendation also support the
39、architecture for point-to-multipoint (p2mp) MPLS-TP LSPs in compliance with IETF RFC 5331 and IETF RFC 5332. As the MPLS-TP is a profile of the MPLS, this Recommendation uses the applicable functional components provided in the MPLS layer network architecture of ITU-T G.8110 and extends them with ad
40、ditional capabilities (e.g., OAM and protection) that are not modelled in ITU-T G.8110. This version of this Recommendation only provides those functional components (based on ITU-T G.805) and architectural models required to model an Ethernet service carried by a single-segment pseudowire (SS-PW) o
41、ver co-routed bidirectional LSPs, which may be hierarchical, and do not use penultimate hop popping (PHP). Other clients for LSPs (e.g., Internet Protocol (IP), and PWs and modes of operation (e.g., multi-segment pseudowire (MS-PW) or associated bidirectional LSPs), as described in IETF RFC 5921, ar
42、e supported as defined in IETF RFC 5921 and IETF RFC 6215 but are not modelled in this version of the Recommendation. They will be added in future versions of this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in thi
43、s text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edit
44、ion of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T G.805 Recommendation ITU
45、-T G.805 (2000), Generic functional architecture of transport networks. ITU-T G.806 Recommendation ITU-T G.806 (2009), Characteristics of transport equipment Description methodology and generic functionality. ITU-T G.808.1 Recommendation ITU-T G.808.1 (2010), Generic protection switching Linear trai
46、l and subnetwork protection. _ 2This ITU-T Recommendation is intended to be aligned with the IETF MPLS RFCs normatively referenced by this Recommendation. Rec. ITU-T G.8110.1/Y.1370.1 (12/2011) 3 ITU-T G.7712 Recommendation ITU-T G.7712/Y.1703 (2010), Architecture and specification of data communica
47、tion network. ITU-T G.8010 Recommendation ITU-T G.8010/Y.1306 (2004), Architecture of Ethernet layer networks. ITU-T G.8013 Recommendation ITU-T G.8013/Y.1731 (2011), OAM functions and mechanisms for Ethernet based networks, plus Corrigendum 1 (2011). ITU-T G.8080 Recommendation ITU-T G.8080/Y.1304
48、(2006), Architecture for the automatically switched optical network. ITU-T G.8101 Recommendation ITU-T G.8101/Y.1355 (2010), Terms and definitions for MPLS transport profile. ITU-T G.8110 Recommendation ITU-T G.8110/Y.1370 (2005), MPLS layer network architecture. ITU-T M.1400 Recommendation ITU-T M.
49、1400 (2006), Designations for interconnections among operators networks. ITU-T Y.1415 Recommendation ITU-T Y.1415 (2005), Ethernet-MPLS network interworking User plane interworking. IETF RFC 3031 IETF RFC 3031 (2001), Multiprotocol Label Switching Architecture. IETF RFC 3032 IETF RFC 3032 (2001), MPLS Label Stack Encoding. IETF RFC 3270 IETF RFC 3270 (2002), Multi-Protocol Label Switching (MPLS) Support of Differentiated Services. IETF RFC 3443 IETF R
