Liaison statement
Approval of MPLS-TP document related to G.8113.1 code point and two other MPLS-TP documents

Additional information about IETF liaison relationships is available on the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2012-05-15
From Group RTG
From Contact Adrian Farrel
To Group ITU-T-SG-15
To Contacts tsbsg15@itu.int
Cc John Drake <jdrake@juniper.net>
Scott Mansfield <Scott.Mansfield@Ericsson.com>
Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian@olddog.co.uk>
The IETF Chair <chair@ietf.org>
Malcolm Johnson <Malcolm.Johnson@itu.int>
Yoichi Maeda <yoichi.maeda@ttc.or.jp>
Steve Trowbridge <steve.trowbridge@alcatel-lucent.com>
Greg Jones <Greg.Jones@itu.int>
The IESG <iesg@ietf.org>
Eliot Lear <elear@cisco.com>
Response Contact Adrian Farrel <adrian@olddog.co.uk>
Scott Mansfield <scott.mansfield@ericsson.com>
Technical Contact Scott Mansfield <scott.mansfield@ericsson.com>
Purpose For action
Deadline 2033-02-28 Action Needed
Attachments (None)
Liaisons referring to this one Response to Liaison concerning approval of MPLS-TP Documents
Body 
The IESG has just approved three Internet-Drafts for publication as
Informational RFCs. They are:

draft-ietf-mpls-tp-oam-analysis
(http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis)
draft-sprecher-mpls-tp-oam-considerations
(http://datatracker.ietf.org/doc/draft-sprecher-mpls-tp-oam-considerations/)
draft-betts-itu-oam-ach-code-point
(http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point)

With this approval, these documents will be placed in the RFC Editor queue next
week.

The document draft-betts-itu-oam-ach-code-point formally requests IANA to
allocate a Pseudowire Associated Channel Type for G.8113.1. Since G.8113.1 is a
normative reference in this document, RFC publication and code point
registration cannot happen until G.8113.1 is approved by the ITU-T for
publication. When the ITU-T approves G.8113.1 for publication, please send a
Liaison Statement to the IETF Routing Area so that the IANA can register and
publish the Pseudowire Associated Channel Type, and the final processing of the
RFC can be triggered.

Please note that the IESG will insert the following note at the top of the RFC
when it is published. This note can be seen in the IETF datatracker along with
the IESG's individual comments at
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/writeup and
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/ballot.

The IESG notes that the IETF has developed a set of OAM
tools for MPLS-TP that have been published as Standards
Track RFCs. A list of the relevant RFCs can be found in
RFC xxxx. The approval of this document and the
assignment of an ACh Type does not constitute
endorsement by the IETF of the alternate MPLS-TP OAM
documented in G.8113.1. The IESG recommends instead
that the RFCs noted above should be implemented.

[RFC Editor - please replace xxxx with the RFC number
assigned to draft-ietf-mpls-tp-oam-analysis.]

Adrian Farrel
IETF Routing Area Director