Title: Response to Updated draft Recommendation G.8151 [Ref 045.03] Submission Date: 11th February 2011 From: IETF Liaison to ITU-T on MPLS stbryant@cisco.com To: tsbsg15@itu.int greg.jones@itu.int hiroshi.ota@itu.int CC: swallow@cisco.com loa@pi.nu paf@cisco.com stbryant@cisco.com adrian.farrel@huawei.com mpls@ietf.org yoichi.maeda@ttc.or.jp steve.trowbridge@alcatel-lucent.com ghani.abbas@ericsson.com hhelvoort@huawei.com malcolm.betts@zte.com.cn kam.lam@alcatel-lucent.com statements@ietf.org Response Contact: stbryant@cisco.com Technical Contact: stbryant@cisco.com Purpose: For Action Thank you for your liaison statement "LS237 - Updated draft Recommendation G.8151 [Ref 045.01]" The IETF Routing Area Directorate have performed an initial review of the liaised text of draft Recommendation G.8151. We are concerned that this draft recommendation has been aligned with draft-bhh-mpls-tp-oam-y1731-06, since this is not an MPLS OAM protocol deigned within the IETF Standards Process. In particular we note that document only specifies the ICC-based MEG_ID and is therefore missing the IP based identifiers specified in draft-ietf-mpls-tp-identifiers-03. The MEP_ID is also not aligned with the MEP_ID defined in the above IETF draft. We are also concerned that this document defines an MPLS-TP MEL since a MEL is not a construct supported in MPLS-TP. We look forward to receiving a revised version of the draft Recommendation that is aligned with the jointly agreed MPLS-TP design. Please can we take this opportunity state that the IETF is committed to developing the MPLS-TP solution as described in the Joint Working Team Recommendations and meeting the jointly agreed MPLS-TP requirements documented in RFC5654.