[mpls] Liaison Statement: Re: LS205 - Considerations on the approach, to providing OAM for MPLS-TP (#37.02)

IETF Chair <chair@ietf.org> Tue, 27 July 2010 09:31 UTC

Message-ID: <4C4EA77A.5000602@ietf.org>
Date: Tue, 27 Jul 2010 05:31:38 -0400
From: IETF Chair <chair@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: tsbsg15@itu.int, greg.jones@itu.int, hiroshi.ota@itu.int
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, steve.trowbridge@alcatel-lucent.com, malcolm.betts@zte.com.cn, iab-chair@iab.org, yoichi.maeda@ntt-at.co.jp, paf@cisco.co, rcallon@juniper.net, iab@iab.org, adrian.farrel@huawei.com, IETF Liaison Statements <statements@ietf.org>, iesg@ietf.org
Subject: [mpls] Liaison Statement: Re: LS205 - Considerations on the approach, to providing OAM for MPLS-TP (#37.02)
Precedence: list

Purpose: In response

Thank you for your liaison COM15-LS205-E, Considerations on the approach
to providing OAM for MPLS-TP.

We agree that it is desirable to extend the OAM capabilities of the MPLS
protocol suite to support the needs of the transport network operators
in a timely manner. We hope that these requirements are correctly
captured in RFC 5654 and RFC 5860 both of which completed the IETF
consensus process and received substantial and constructive review by
Study Group 15 of the ITU-T.

As you appreciate, both the IETF and the ITU-T are contribution driven
organizations. The IETF would therefore encourage the service providers
who are requesting more rapid development of standards to participate
more fully in the IETF standardization process.

Your liaison references some interoperability tests. It is hard for us
to evaluate the scope and validity of these tests for a number of reasons:

   - The specification of the protocols actually tested and the
     detailed results are confidential to the participants and not
     generally available.

   - We cannot assess which features documented in the referenced
     draft (draft-bhh-mpls-tp-oam-y1731) were tested and which
     were not tested.

   - The current revision of draft-bhh-mpls-tp-oam-y1731 does not
     provide full details of the protocol mechanisms of all of the
     features it describes.

   - The test description refers to the unpublished G.8114 (2008),
     which we understand does not have ITU-T consensus.

With regard to the specific technical proposal outlined in the liaison,
the IETF process is available to investigate the approaches to the
design of an enhanced MPLS OAM to satisfy the needs of network
operators, including of course the transport network operators. Such
ideas must comply with previously agreed requirements unless new
requirements are brought forward and agreed by consensus in both the
IETF and the ITU-T. All new approaches are subject to technical
discussion within the IETF and will be reviewed by IETF consensus.
Proponents of alternative solutions are encouraged to discuss them on
the appropriate IETF mailing lists and to attempt to persuade the
community of the technical merit of their proposals.

The IETF looks forward to working cooperatively with the ITU-T to
develop MPLS-TP OAM solution components in a timely manner that meets
the needs of network operators wishing to deploy MPLS technology.

On behalf of the IESG,
 Russ Housley

[mpls] Liaison Statement: Re: LS205 - Considerati… IETF Chair