Committed to connecting the world

  •  
wtisd

ITU-T work programme

[2009-2012] : [SG15] : [Q10/15]

[Declared patent(s)]  - [Publication]

Work item: G.8113.1/Y.1372.1 (ex G.tpoam G.mplstpoam)
Subject/title: Operations, Administration and Maintenance mechanism for MPLS-TP in Packet Transport Network (PTN)
Status: Approved on 2012-11-20 
Approval process: TAP
Type of work item: Recommendation
Version: New
Equivalent number: -
Timing: -
Liaison: -
Supporting members: -
Summary: This Recommendation specifies mechanisms for user-plane OAM (Operations, Administration and Maintenance) in MPLS-TP networks to meet the MPLS-TP OAM requirements defined in [IETF RFC 5860]. It also specifies the MPLS-TP OAM packet formats, syntax and semantics of MPLS-TP OAM packet fields. The OAM mechanisms defined in this Recommendation assume common forwarding of the MPLS-TP user packets and MPLS-TP OAM packets. In transport networks, the OAM return path is always in band. The MPLS-TP OAM mechanisms as described in this Recommendation apply to co-routed bidirectional point-to-point MPLS-TP connections. Unidirectional point-to-point and point-to-multipoint MPLS-TP connections will be addressed in a future version of this Recommendation. This Recommendation is compliant with the transport profile of MPLS as defined by the IETF. In the event of a misalignment in MPLS-TP related architecture, framework, and protocols between this ITU-T Recommendation and the normatively referenced IETF RFCs, the RFCs will take precedence.
Comment: Sent to WTSA-12.
Reference(s):
  Historic references:
-
Contact(s):
Jia He, Editor
Han Li, Editor
ITU-T A.5 justification(s):
Generate A.5 drat TD
[IETF RFC 3031 (2001) (awaiting validation)]
[IETF RFC 3032 (2001) (awaiting validation)]
[IETF RFC 3443 (2003) (awaiting validation)]
[IETF RFC 4385 (2006) (awaiting validation)]
[IETF RFC 5462 (2009) (awaiting validation)]
[IETF RFC 5586 (2009) (awaiting validation)]
[IETF RFC 5654 (2009) (awaiting validation)]
[IETF RFC 5718 (2010) (awaiting validation)]
[IETF RFC 5860 (2010) (awaiting validation)]
[IETF RFC 6371 (2011) (awaiting validation)]
[Submit new A.5 justification ]
See guidelines for creating & submitting ITU-T A.5 justifications
First registration in the WP: 2009-05-01 10:11:55
Last update: 2012-12-03 14:07:35