LS332 - Consent of Recommendation ITU-T G.8113.2/Y.1372.2 -> IESG
|From Contact||Greg Jones|
|Deadline||2011-10-28 Action Taken|
LS332 - Consent of Recommendation ITU-T G.8113.2/Y.1372.2 - pdf body
LS332 - Consent of Recommendation ITU-T G.8113.2/Y.1372.2 - pdf attach
|Liaisons referring to this one||
Completion of RFCs needed for G.8113.2
The experts of Q10/15 would like to inform you that they have agreed to consent Recommendation ITU-T G.8113.2/Y.1372.2, “Operations, Administration and Maintenance mechanism for MPLS-TP networks using the tools defined for MPLS.” This Recommendation provides MPLS-TP OAM mechanisms. It 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 using co-routed bidirectional point-to-point connections, the OAM return path is always in band. Note that the following IDs need to be approved and in the RFC Editor’s queue by 28 October 2011 in order to initiate the Last Call in the approval process so that it will complete before the December SG15 plenary: 1. draft-ietf-mpls-tp-oam-framework, Operations, Administration and Maintenance Framework for MPLS-based Transport Networks. 2. draft-ietf-mpls-tp-cc-cv-rdi, Proactive Connectivity Verification, Continuity Check and Remote Defect Indication for MPLS-TP. 3. draft-ietf-mpls-tp-fault, MPLS Fault Management OAM. 4. draft-ietf-mpls-tp-on-demand-cv, MPLS On-demand Connectivity Verification and Route Tracing. The following ID is not required for LC initiation because it is in the Bibliography section: 5. draft-ietf-mpls-tp-li-lb, MPLS-TP Lock Instruct and Loopback Functions. Attach: TD478/PLEN, "Draft Recommendation ITU-T G.8113.2/Y.1372.2".