ITU-T Y 1371-2015 Interfaces for the MPLS transport profile layer network (Study Group 15)《传送级多协议标签交换的剖面层网络接口》.pdf

1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T G.8112/Y.1371 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2015) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Packet over Transport aspects MPLS over Transport aspects SERIES Y: GLOBAL INFOR

2、MATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Transport Interfaces for the MPLS transport profile layer network Recommendation ITU-T G.8112/Y.1371 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INT

3、ERNATIONAL 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 TELEPHON

4、E 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 SEC

5、TIONS 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 asp

6、ects G.8000G.8099 MPLS over Transport aspects G.8100G.8199 Synchronization, quality 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.8112/Y.1371 (08/2015) i Recommen

7、dation ITU-T G.8112/Y.1371 Interfaces for the MPLS transport profile layer network Summary Recommendation ITU-T G.8112/Y.1371 specifies the interfaces for the multi-protocol label switching transport profile (MPLS-TP) layer network. The interfaces for the MPLS-TP layer network use various server lay

8、er networks, like the plesiochronous digital hierarchy (PDH), synchronous digital hierarchy (SDH), optical transport hierarchy (OTH) and the Ethernet MAC layer network (ETH). History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T G.8112/Y.1371 2006-10-07 15 11.1002/1000/8783 1.1 IT

9、U-T G.8112/Y.1371 (2006) Cor. 1 2007-01-09 15 11.1002/1000/9006 2.0 ITU-T G.8112/Y.1371 2012-10-29 15 11.1002/1000/11772 2.1 ITU-T G.8112/Y.1371 (2012) Amd. 1 2014-04-04 15 11.1002/1000/12187 2.2 ITU-T G.8112/Y.1371 (2012) Cor. 1 2015-01-13 15 11.1002/1000/12385 3.0 ITU-T G.8112/Y.1371 2015-08-13 15

10、 11.1002/1000/12547 _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T G.8112/Y.1371 (08/2015) FOREWORD The International Tele

11、communication Union (ITU) is the United Nations specialized agency 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 t

12、ariff questions and issuing Recommendations on them with a view 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 Reco

13、mmendations on these topics. The approval of ITU-T Recommendations 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 Recomm

14、endation, the expression “Administration“ is used for conciseness 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., interopera

15、bility or applicability) and compliance with the Recommendation 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 co

16、mpliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU 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, validi

17、ty or applicability of claimed Intellectual Property Rights, 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 requir

18、ed to implement this Recommendation. However, implementers are 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 2015 All rights reserved. No part of this publication may be reproduced

19、, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T G.8112/Y.1371 (08/2015) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 3 3.1 Terms defined elsewhere 3 3.2 Terms defined in this Recommendation . 3 4 Abbreviations and acronyms 3 5 Conventions 5

20、 6 MPLS transport profile layer network interface structure 6 6.1 NNI basic signal structure 7 6.2 Information structure for the MPLS-TP network node interfaces 10 6.3 MPLS-TP labels . 17 6.4 MPLS-TP shim header . 17 7 Multiplexing/mapping principles 18 7.1 Mapping 18 7.2 MPLS-TP multiplex . 18 7.3

21、MPLS-TP tandem connection monitoring 18 8 Physical specification of the MPLS-TP interfaces . 18 Appendix I Example of layer networks in ETH UNI and MPLS-TP NNI . 19 Appendix II Bandwidth requirements for MPLS-TP transport 20 Rec. ITU-T G.8112/Y.1371 (08/2015) 1 Recommendation ITU-T G.8112/Y.1371 Int

22、erfaces for the MPLS transport profile layer network 1 Scope This Recommendation specifies the interfaces for the multi-protocol label switching transport profile (MPLS-TP) layer network, in particular the: encapsulation of MPLS-TP client signals into the MPLS-TP characteristic information that will

23、 be present on MPLS-TP network-to-network interface (NNI) links in the transport network; encapsulation of MPLS-TP characteristic information into the MPLS-TP link frames that will be present on MPLS-TP NNI links in the transport network; MPLS-TP layer network within the transport network and associ

24、ated MPLS-TP multiplexing; MPLS-TP nested connection monitoring per layer network level within the transport network; MPLS-TP operation, administration and maintenance (OAM) associated with nested connection monitoring in the transport network; encapsulation of MPLS-TP control plane information. The

25、 MPLS-TP network uses various server layer networks like optical transport hierarchy (OTH), synchronous digital hierarchy (SDH), plesiochronous digital hierarchy (PDH) and Ethernet MAC layer network (ETH). The detailed requirements are specified in a number of ITU-T Recommendations, ANSI Standards,

26、IEEE Standards and IETF RFCs, which are cited. This Recommendation specifies point-to-point label-switched paths (LSPs); point-to-multipoint LSPs are for further study. This Recommendation does not cover inter-operator control plane aspects of the MPLS-TP NNI. This Recommendation provides a represen

27、tation of the MPLS-TP technology using the methodologies that have been used for other transport technologies e.g., SDH, optical transport network (OTN) and Ethernet.1 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, cons

28、titute 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 edition of the R

29、ecommendations 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.704 Recommendation ITU-T G.704 (19

30、98), Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels. ITU-T G.705 Recommendation ITU-T G.705 (2000), Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks. _ 1 This Recommendation is intended to be aligned with the IET

31、F MPLS RFCs normatively referenced by this Recommendation. 2 Rec. ITU-T G.8112/Y.1371 (08/2015) ITU-T G.707 Recommendation ITU-T G.707/Y.1322 (2007), Network node interface for the synchronous digital hierarchy (SDH). ITU-T G.709 Recommendation ITU-T G.709/Y.1331 (2012), Interfaces for the optical t

32、ransport network. ITU-T G.832 Recommendation ITU-T G.832 (1998), Transport of SDH elements on PDH networks Frame and multiplexing structures. ITU-T G.951 Recommendation ITU-T G.951 (1988), Digital line systems based on the 1544 kbit/s hierarchy on symmetric pair cables. ITU-T G.7041 Recommendation I

33、TU-T G.7041/Y.1303 (2011), Generic framing procedure. ITU-T G.7043 Recommendation ITU-T G.7043/Y.1343 (2004), Virtual concatenation of plesiochronous digital hierarchy (PDH) signals. ITU-T G.7712 Recommendation ITU-T G.7712/Y.1703 (2010), Architecture and specification of data communication network.

34、 ITU-T G.8001 Recommendation G.8001/Y.1354 (2013), Terms and definitions for Ethernet frames over transport. ITU-T G.8012 Recommendation G.8012/Y.1308 (2004), Ethernet UNI and Ethernet NNI. ITU-T G.8040 Recommendation ITU-T G.8040/Y.1340 (2005), GFP frame mapping into Plesiochronous Digital Hierarch

35、y (PDH). ITU-T G.8101 Recommendation G.8101/Y.1355 (2015), Terms and definitions for MPLS transport profile. ITU-T G.8110.1 Recommendation ITU-T G.8110.1/Y.1370.1 (2011), Architecture of the Multi-Protocol Label Switching transport profile layer network. ITU-T G.8151 Recommendation ITU-T G.8151/Y.13

36、74 (2015), Management aspects of the MPLS-TP network element. ITU-T Y.1415 Recommendation ITU-T Y.1415 (2005), Ethernet-MPLS network interworking User plane interworking. ITU-Y Y.1711 Recommendation ITU-T Y.1711 (2004), Operation client layer network interface as specified in IETF RFC 5921 and IETF

37、RFC 6215. The MPLS-TP layer interface can be deployed as a network-to-network interface (NNI) and within the transport network. As described in IETF RFC 5921, the MPLS-TP layer network consists of the Transport Service layer and the Transport Path layer. The MPLS-TP NNI provides the interface betwee

38、n two MPLS-TP PEs and could be used for the support of client layer connection services, i.e., the Transport Service layer and the connection within transport, i.e., Transport Path layer. The user-to-network interface (UNI) provides the interface for client services that are carried by MPLS-TP layer

39、s. UNIs are used for such a service. The location of the UNI and NNI is illustrated in Figure 6-1. UNI functions are located at the customer edge (CE) and provider edge (PE). The UNI client side (UNI-C) is located and terminated at the CE and the UNI network side (UNI-N) is located and terminated at

40、 the PE. The functions for UNI-C and UNI-N are described in IETF RFC 5921 and IETF RFC 6215. G . 8 1 1 - Y . 1 3 7 1 ( 1 2 ) _ F 6 - 12M PL S- T P PENNINNINNIU N I - N U N I - NCEU N I - C U N I - CCEUNI UNIM PL S- T P PEFigure 6-1 Locations of UNI and MPLS-TP NNI The MPLS-TP-NNI may be deployed as

41、an intra-domain interface (IaDI) within a single administrative domain and as an inter-domain interface (IrDI) between two administrative domains as illustrated in Figure 6-2. G . 8 1 1 - Y . 1 3 7 1 ( 1 2 ) _ F 6 - 22M PL S- T P PE M PL S- T P PE M PL S- T P PENNI NNI NNI NNI NNI NNIU N I - N U N I

42、 - NCEU N I - C U N I - CCEUNI UNII a D I N N II a D I N N I I r D I N N IM PL S- T P PEFigure 6-2 Locations of client-UNI and MPLS-TP NNI UNI and MPLS-TP NNI can encompass multiple layer networks. Appendix I describes an example of the Ethernet as the client service. The MPLS-TP NNI can be used to

43、carry informational elements of three planes (Figure 6-3): data (or user) plane, optionally including a data communication network (DCN) supporting management plane and control plane communications; control plane (e.g., signalling and routing); management plane. Rec. ITU-T G.8112/Y.1371 (08/2015) 7

44、G . 8 1 1 - Y . 1 3 7 1 ( 1 2 ) F 6 - 32T N E T N EM a na ge m e ntpl a neM a na ge m e ntpl a neC ont r olpl a neC ont r olpl a neD C NU s e r / da t apl a neU s e r / da t apl a neD C ND C N D C NNNIFigure 6-3 Three planes of MPLS-TP NNI Each NNI is divided into three plane-specific NNIs: NNID for

45、 the data plane informational elements, including operation, administration and maintenance (OAM), which is terminated in the layers termination, adaptation and connection/flow forwarding functions; NNIC for the control plane informational elements; NNIM for the management plane informational elemen

46、ts. This Recommendation specifies NNID and NNIC as defined in IETF RFC 6215. In IETF RFC 6215, NNID and NNIC are represented as NNI (network-to-network interface) function. An NNI function is defined at the interface of an MPLS-TE PE node as described in Figure 2 of IETF RFC 6215. NNIC and NNIM real

47、ized via the DCN interface are described in ITU-T G.7712 and ITU-T G.8151, respectively. 6.1 NNI basic signal structure The basic structure is shown in Figure 6-4. The relationship between clients and MPLS-TP is described in IETF RFC 5921 and the example of the clients for pseudowire (PW) is describ

48、ed in IETF RFC 5960. Note that this Recommendation only describes Ethernet as a client; other clients for LSP or PW are for further study. 8 Rec. ITU-T G.8112/Y.1371 (08/2015) G . 8 1 1 - Y . 1 3 7 1 ( 1 2 ) _ F 6 - 42C l i e nt s ( I P v4, I P v6) C l i e nt s ( E T H , P D H , S D H , A T M , F R

49、, H D L C , P P P )C om m on i nt e r w or ki ng i ndi c a t or s( P a yl oa d c onv e r ge nc e ) ( T i m i ng) ( S e que nc i ng)M P L S - T PM P L S - T P P ( L S P , P W )M P L S - T P T ( S ub- pa t h m a i nt e na nc e )G F P P P P i n H D L CP P P i n H D L C G F PG F PP D HP qe , P qsP D HP qe , P qsP qe - X v ,P qs - X vS D HV C - nV C - n- X vV C - 4- X cS D HV C - nV C - n- X vV C - 4- X cO T HODUkO