ITU-T Y 1714-2009 MPLS management and OAM framework (Study Group 15)《多协议标签交换(MPLS)管理和操作管理维护(OAM)架构 15号研究组》.pdf

《ITU-T Y 1714-2009 MPLS management and OAM framework (Study Group 15)《多协议标签交换(MPLS)管理和操作管理维护(OAM)架构 15号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 1714-2009 MPLS management and OAM framework (Study Group 15)《多协议标签交换(MPLS)管理和操作管理维护(OAM)架构 15号研究组》.pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T Y.1714TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2009) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Internet protocol aspects Operation, administration and maintenance MPLS management and OAM

2、 framework Recommendation ITU-T Y.1714 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces

3、and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and r

4、esource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 NEXT GENERATION NETWORKS Frameworks and functional architectur

5、e models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.24

6、99 Network control architectures and protocols Y.2500Y.2599 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.1714 (01/2009) i Recommendation ITU-T Y.1714 MPLS management and OAM framework Summary Recommendati

7、on ITU-T Y.1714 covers MPLS user-plane operation, administration and maintenance, control plane aspects and TMN aspects of MPLS management. Specifically, the mechanisms covered in this Recommendation are being worked on at different standard bodies mainly ITU-T and IETF. This Recommendation focuses

8、on MPLS technology specific OAM aspects of the TMN model of Recommendation ITU-T M.3010. The Recommendations scope is limited to those components and interfaces that interface between network elements (user and control plane), and between network elements and EMS, NMS systems. Source Recommendation

9、ITU-T Y.1714 was approved on 13 January 2009 by ITU-T Study Group 15 (2009-2012) under Recommendation ITU-T A.8 procedures. ii Rec. ITU-T Y.1714 (01/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information

10、 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 view to standardizing telecommunications on a worldwide

11、 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 Recommendations is covered by the procedure laid down in WTSA R

12、esolution 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 conciseness to indicate both a telecommunication administrat

13、ion 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 Recommendation is achieved when all of these mandatory provisions

14、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. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the

15、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, whether asserted by ITU members or others outside of

16、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 are cautioned that this may not represent the latest in

17、formation and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.1714 (01/2009) iii CONTENTS P

18、age 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 4 5 Network models 5 5.1 MPLS infrastructure . 5 5.2 Interworking LSP . 5 5.3 ATM-MPLS network . 7 5.4 L3 VPN MPLS networks 7 5.5 L2 VPN MPLS networks 9 6 Related R

19、ecommendations and context 9 6.1 User plane aspects 9 6.2 Data plane recovery mechanisms . 10 6.3 Control plane aspects 11 6.4 Management plane 12 6.5 OAM relationship between client layers and MPLS server layer 12 7 MPLS TMN aspects . 12 7.1 MPLS network supervisory function 12 7.2 Management aspec

20、ts. 13 7.3 MIBs for user plane management. 13 8 Security. 13 Appendix I Detection of data plane defects 14 I.1 Detection of transmission interface failures. 14 I.2 Detection of node failures 14 I.3 Detection of path failures . 14 Appendix II Diagnostic tools 16 II.1 Virtual channel connectivity veri

21、fication . 16 II.2 Label switched router self test 16 Appendix III MPLS management capabilities 17 III.1 MPLS data plane management. 17 III.2 MPLS LDP control plane management 17 Appendix IV Fault management. 19 IV.1 Bidirectional forwarding detection. 19 Bibliography. 20 iv Rec. ITU-T Y.1714 (01/20

22、09) Introduction This Recommendation is an umbrella Recommendation to progress work on all aspects of multiprotocol label switching (MPLS) management. This Recommendation covers MPLS user-plane operation, administration and maintenance (OAM); control plane aspects, and TMN aspects of MPLS management

23、. It is recognized that the scope of this work crosses many ITU-T Study Groups and Questions as well as other standards bodies. Many aspects of MPLS management have been worked concurrently with the preparation of this Recommendation. Those specific aspects of management not ready for normative refe

24、rence at the time of issue will be addressed via normal ITU document update procedures and are identified in this Recommendation as “for further study“. Rec. ITU-T Y.1714 (01/2009) 1 Recommendation ITU-T Y.1714 MPLS management and OAM framework 1 Scope This Recommendation covers MPLS user-plane oper

25、ation, administration and maintenance, control plane aspects and TMN aspects of MPLS management. The mechanisms covered in this Recommendation are being worked on at different standard bodies mainly ITU-T and IETF. This Recommendation focuses on MPLS technology specific OAM aspects of the TMN model

26、of ITU-T M.3010. The Recommendations scope is limited to those components and interfaces that interface between network elements (user and control plane), and between network elements and EMS, NMS systems (the Q interface). Figure 1 shows the scope of this Recommendation and interaction with other I

27、TU-T Study Groups and standard bodies. Y.1714(09)_F01X interfaceNetwork element layer management:data-plane and control-plane OAM(ITU-T, IETF)Q interfaceMIBSTransmissioninterfaceFCAPS:fault,configuration,accounting,performance,security(ITU-T, IETF) Q interfaceService management layerNetwork manageme

28、nt layerBusiness management layerService management layerNetwork management layerBusiness management layerNetwork element layer(ITU-T, IETF)Element management layerNetwork element layer(ITU-T, IETF)Element management layerFigure 1 Generic TMN model 2 References The following ITU-T Recommendations an

29、d other references contain provisions which, through reference in this 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 encou

30、raged to investigate the possibility of applying the most recent edition 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 doc

31、ument, the status of a Recommendation. ITU-T G.8110 Recommendation ITU-T G.8110/Y.1370 (2005), MPLS layer network architecture. ITU-T I.610 Recommendation ITU-T I.610 (1999), B-ISDN operation and maintenance principles and functions. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a

32、telecommunications management network. ITU-T M.3016.x Recommendation ITU-T M.3016.x-series (2005), Security for the management plane. 2 Rec. ITU-T Y.1714 (01/2009) ITU-T Q.812 Recommendation ITU-T Q.812 (2004), Upper layer protocol profiles for the Q and X interfaces. ITU-T Y.1411 Recommendation ITU

33、-T Y.1411 (2003), ATM-MPLS network interworking Cell mode user plane interworking. ITU-T Y.1561 Recommendation ITU-T Y.1561 (2004), Performance and availability parameters for MPLS networks. ITU-T Y.1710 Recommendation ITU-T Y.1710 (2001), Requirements for OAM functionality for MPLS networks. ITU-T

34、Y.1711 Recommendation ITU-T Y.1711 (2002), Operation & Maintenance mechanism for MPLS networks. ITU-T Y.1712 Recommendation ITU-T Y.1712 (2004), OAM functionality for ATM-MPLS interworking. ITU-T Y.1713 Recommendation ITU-T Y.1713 (2004), Misbranching detection for MPLS networks. ITU-T Y.1720 Recomm

35、endation ITU-T Y.1720 (2003), Protection switching for MPLS networks. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for Next Generation Networks. IETF RFC 792 IETF RFC 792 (1981), Internet Control Message Protocol. IETF RFC 2206 IETF RFC 2206 (1997),

36、 RSVP Management Information Base using SMIv2. IETF RFC 3031 IETF RFC 3031 (2001), Multiprotocol Label Switching Architecture. IETF RFC 3036 IETF RFC 3036 (2001), LDP Specification. IETF RFC 3107 IETF RFC 3107 (2001), Carrying Label Information in BGP-4. IETF RFC 3209 IETF RFC 3209 (2001), RSVP-TE:

37、Extensions to RSVP for LSP Tunnels. IETF RFC 3212 IETF RFC 3212 (2002), Constraint-Based LSP Setup using LDP. IETF RFC 3478 IETF RFC 3478 (2003), Graceful Restart Mechanism for Label Distribution Protocol. IETF RFC 3479 IETF RFC 3479 (2003), Fault Tolerance for the Label Distribution Protocol (LDP).

38、 IETF RFC 3811 IETF RFC 3811 (2004), Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management. IETF RFC 3812 IETF RFC 3812 (2004), Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB). Rec. ITU-T Y.1714 (01/2009) 3 IETF R

39、FC 3813 IETF RFC 3813 (2004), Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB). IETF RFC 3814 IETF RFC 3814 (2004), Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Inform

40、ation Base (MIB). IETF RFC 3815 IETF RFC 3815 (2004), Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP). IETF RFC 3985 IETF RFC 3985 (2005), Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture. IETF RFC 4090 IETF RFC 4090 (2005), Fast R

41、eroute Extensions to RSVP-TE for LSP Tunnels. IETF RFC 4221 IETF RFC 4221 (2005), Multiprotocol Label Switching (MPLS) Management Overview. IETF RFC 4364 IETF RFC 4364 (2006), BGP/MPLS IP Virtual Private Networks (VPNs). IETF RFC 4377 IETF RFC 4377 (2006), Operations and Management Requirements for

42、Multi-Protocol Label Switched (MPLS) Networks. IETF RFC 4378 IETF RFC 4378 (2006), A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM). IETF RFC 4379 IETF RFC 4379 (2006), Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures. 3 Definitions 3.1 Terms de

43、fined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 control plane: ITU-T Y.2011. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 link protection: In this type of protection, during the failure, all the label switched pa

44、ths (LSPs) using the protected link as an output interface are rerouted over the single backup LSP. A backup LSP that bypasses a single link of the protected LSP is called next hop (NHOP) bypass LSP. 3.2.2 network supervisory function: A function, which coordinates a set of mechanisms to monitor the

45、 defect state of the LSP. 3.2.3 node protection: Node protection is similar to link protection except that the destination of the backup LSP is a node further downstream the point of failure. Typically node protection is using the next node downstream the point of failure, in this case the backup LS

46、P is known as the “next next hop (NNHOP) bypass LSP“. 4 Rec. ITU-T Y.1714 (01/2009) When a node failure occurs, the LSPs are rerouted completely around the failed node. 3.2.4 path protection: Path protection provides end-to-end protection from source to tail for a given LSP. More details can be foun

47、d in ITU-T Y.1720. 3.2.5 user plane: This refers to the set of traffic forwarding components through which traffic flows. NOTE “User plane“ is also referred to as “transport plane“ in other ITU-T Recommendations. 4 Abbreviations This Recommendation uses the following abbreviations: ATM Asynchronous

48、Transfer Mode BFD Bidirectional Forwarding Detection BGP Border Gateway Protocol CE Customer Edge CsC Carriers Carrier eBGP External BGP FEC Forwarding Equivalent Class FR Frame Relay FTN FEC-to-NHLFE IGP Interior Gateway Protocol ILM Incoming Label Map IP Internet Protocol IWF Interworking Function

49、 LDP Label Distribution Protocol LSP Label Switched Path LSR Label Switched Router MIB Management Information Base MPLS Multiprotocol Label Switching MTU Maximum Transmission Unit NHLFE Next Hop Label Forwarding Entry NHP Next Hop NNHP Next Next Hop OAM Operation, Administration and Maintenance PE Provider Edge POS Packet Over Sonet RRO Record Route Object RSVP Resource Reservation Protocol TDM Time Division Multiplexing TE Traffic Engineering Rec. ITU-T Y.1714 (01/20