RFC 6671

RFC 6671 💖

Allocation of a Generic Associated Channel Type for ITU-T MPLS Transport Profile Operation, Maintenance, and Administration (MPLS-TP OAM)

Written by M. Betts from ZTE 🎀 Category: Informational, dated November 2012, ISSN 2070-1721. The header doesn't list anything it obsoletes or updates. It's an IETF document. ✨

Abstract

okay so this doc gives a Generic Associated Channel (G-ACh) Type to ITU-T MPLS Transport Profile OAM messages, so they can ride in the MPLS Generic Associated Channel 🦋

Status of This Memo

This one is not an Internet Standards Track spec. It's published just for info 🧚

It's a product of the Internet Engineering Task Force (IETF) and represents the consensus of the IETF community. It got public review and was approved by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 if you want the details 💅

For current status, errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc6671.

IESG Note

the IESG is being very clear here 👑 The IETF has built a set of OAM tools for MPLS-TP that were published as Standards Track RFCs, and you can find the list in RFC 6669. Approving this doc and assigning an ACh Type does not mean the IETF endorses the alternate MPLS-TP OAM described in G.8113.1. The IESG recommends that the RFCs noted above should be implemented instead 🫶

Copyright Notice

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved 🌈

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they were on the publication date. Please actually read those, because they lay out your rights and restrictions for this document. Code Components pulled out of this document must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in that license 📜

1. Introduction ✨

The Transport Profile of MPLS (MPLS-TP), defined in [RFC5654], is a profile of MPLS tech for packet transport networks. The MPLS-TP profile includes a set of Operations, Administration, and Management (OAM) tools that the IETF defined in [RFC6669]. Those tools exist to meet the OAM functional requirements in [RFC5860] 🧠

ITU-T Recommendation [G.8113.1] documents MPLS-TP OAM, and it builds on Ethernet OAM as documented in [Y.1731]. The messages in [G.8113.1] are meant to be carried in a new Generic Associated Channel (G-ACh) Type in the MPLS Generic Associated Channel. To carry them interoperably, you use a G-ACh Type from the IANA-maintained registry "Pseudowire Associated Channel Types" 🎀

ITU-T SG15 asked for this in [LS370]. So that the [G.8113.1] OAM solution can be deployed without using an experimental G-ACh Type, IANA assigned G-ACh Type <0x8902> for ITU-T's use with [G.8113.1]. It's called the "G.8113.1 OAM G-ACh Type" 🦋

Some IETF folks don't think building or deploying a second protocol solution in the same architectural problem space is necessary or advisable, per [RFC6670] 🙈

2. Conventions Used in This Document 💅

2.1. Requirements Notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] 🔥

3. Scope of the G.8113.1 OAM G-ACh Type 🌸

this part is the big rule, bestie 👑 The G-ACh Type assigned by this document MUST only be used for OAM messages, as defined in the ITU-T Recommendation [G.8113.1], carried in the G-ACh. The OAM messages and procedures carried behind this G-ACh Type are restricted to only the ones that address the OAM functional requirements defined in [RFC5860]. Other message types MUST NOT be carried behind this G-ACh Type 😭

ITU-T Recommendations can be updated by errata, corrigenda, amendments, or complete revisions. In any update of [G.8113.1], the G-ACh Type assigned by this document MUST NOT be used for any functions that aren't identified as OAM functional requirements in [RFC5860]. An update of [G.8113.1] may use this G-ACh Type to support the OAM functions identified in [RFC5860]. When an amendment or complete revision of G.8113.1 gets approved, the reference to [G.8113.1] in this document should be updated to show the approval date of the new version 💀

The G-ACh Type assigned by this document may be used on any transport construct that uses the G-ACh, for example MPLS-TP Sections, MPLS-TP LSPs, or PWs as described in [G.8113.1] 🧚

4. Security Considerations 🔥

As [RFC5586] notes, when new G-ACh Types get defined, the "security considerations MUST be described in the relevant associated channel type specification". The IETF is taking this moment to remind the ITU-T that it needs to describe security considerations in [G.8113.1]. This is serious, babe. Don't skip it 😭💀

5. IANA Considerations 🎀

IANA maintains the "Pseudowire Associated Channel Types" sub-registry of the "Pseudowire Name Spaces (PWE3)" registry 🍓

IANA has allocated a new G-ACh Type like this:

   Value        Description              TLV Follows  Reference
   -----------  -----------------------  -----------  ---------
   0x8902       G.8113.1 OAM             No           [RFC6671]

6. References 📚

6.1. Normative References

• [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
• [RFC5586] Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed., "MPLS Generic Associated Channel", RFC 5586, June 2009.
• [RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009.
• [RFC5860] Vigoureux, M., Ed., Ward, D., Ed., and M. Betts, Ed., "Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks", RFC 5860, May 2010.
• [G.8113.1] ITU-T Recommendation G.8113.1/Y.1372.1, "Operations, Administration and Maintenance mechanism for MPLS-TP in Packet Transport Network (PTN)", 11/2012, http://www.itu.int/rec/T-REC-G.8113.1/en.
• [Y.1731] ITU-T Recommendation G.8013/Y.1731, "OAM functions and mechanisms for Ethernet based networks" 07/2011 as updated by Corrigendum 1, 10/2011, and Amendment 1, 05/2012, http://www.itu.int/rec/T-REC-G.8013/en.

6.2. Informative References

• [LS370] "Liaison Statement: LS370 - Current status of Recommendation ITU-T G.8113.1/Y.1372.1, Operations, Administration and Maintenance mechanism for MPLS-TP in Packet Transport Network (PTN)", January 2012, https://datatracker.ietf.org/liaison/1125/.
• [RFC6669] Sprecher, N. and L. Fang, "An Overview of the Operations, Administration, and Maintenance (OAM) Tool Set for MPLS-Based Transport Networks", RFC 6669, July 2012.
• [RFC6670] Sprecher, N. and KY. Hong, "The Reasons for Selecting a Single Solution for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM)", RFC 6670, July 2012.

Author's Address 💖

Malcolm Betts ZTE EMail: malcolm.betts@zte.com.cn