Liaison statement
Response to your Liaison Statement - LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) "Requirements and Reference Model for optimized traceroute of joint Internet Protocol/Multi-Protocol Label Switching"

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2024-03-15
From Group mpls
From Contact Adrian Farrel
To Group ITU-T-SG-11
To Contacts Tatiana Kurakova <tatiana.kurakova@itu.int>
Study Group 11 <tsbsg11@itu.int>
Denis Andreev <denis.andreev@itu.int>
Cc Multiprotocol Label Switching Discussion List <mpls@ietf.org>
Multiprotocol Label Switching Working Group Chairs <mpls-chairs@ietf.org>
Routing Area Directors <rtg-ads@ietf.org>
Operations and Management Area Working Group Discussion List <opsawg@ietf.org>
Operations and Management Area Working Group Chairs <opsawg-chairs@ietf.org>
Operations and Management Area Directors <ops-ads@ietf.org>
Scott Mansfield <Scott.Mansfield@ericsson.com>
itu-t-liaison@iab.org <itu-t-liaison@iab.org>
Response Contact mpls@ietf.org
opsawg@ietf.org
Technical Contact Adrian Farrel <adrian@olddog.co.uk>
Purpose For information
Attachments (None)
Liaisons referred by this one LS on the consent of draft Recommendation ITU-T Q.3962 (ex. Q.joint_tr) “Requirements and Reference Model for optimized traceroute of joint Internet Protocol/Multi-Protocol Label Switching”
Body 
Thank you for your Liaison Statement - LS on the consent of draft
Recommendation ITU-T Q.3962 (ex. Q.joint_tr) "Requirements and Reference Model
for optimized traceroute of joint Internet Protocol/Multi-Protocol Label
Switching" dated 2023-10-24. This has been passed on to the MPLS working group
by the OPSAWG for consideration.

The MPLS working group would like to thank you for sharing your requirements as
expressed in Q.3962.

Our current understanding of your requirements suggests that all or most of
your requirements can be addressed using existing IP/MPLS OAM tools, and that
no further protocol work is necessary.

We would welcome all experts to bring these requirements to the IETF's MPLS
working group with a view to working collaboratively on an Informational RFC
that describes how to deliver the function you want to see. Obviously, should
any gaps be discovered during this process, the working group would also be
pleased to engage in additional protocol work to resolve any issues using the
procedures described in RFC 4775 and RFC 4929.

Kind regards,
Adrian Farrel, MPLS Working Group Co-Chair (On behalf of the MPLS Working Group
and Co-Chairs) Joe Clarke, OPSAWG Co-Chair (On behalf of the OPSAWG and
Co-Chairs)