wdiff rfc6671.original rfc6671.txt

Network Working Group
Internet Engineering Task Force (IETF) M. Betts
Internet Draft
Request for Comments: 6671 ZTE
Intended status:
Category: Informational April 10, 2012
Expires: October 10, July 2012
ISSN: 2070-1721

Allocation of a Generic Associated Channel Type for ITU-T
MPLS Transport Profile Operation, Maintenance, and Administration
(MPLS-TP OAM)
draft-betts-itu-oam-ach-code-point-04.txt

Abstract

This document assigns a Generic Associated Channel (G-ACh) Type for
carrying ITU-T MPLS Transport Profile Operations, Administration, and
Management (MPLS-TP OAM) messages in the MPLS Generic Associated
Channel.

Status of this This Memo

This Internet-Draft document is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents as Internet-
Drafts.

Internet-Drafts
approved by the IESG are draft documents valid for a maximum candidate for any level of Internet
Standard; see Section 2 of six
months RFC 5741.

Information about the current status of this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
http://www.rfc-editor.org/info/rfc6671.

IESG Note

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 current Internet-Drafts
the relevant RFCs can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt found in RFC 6669. The list approval of Internet-Draft Shadow Directories can 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 accessed at
http://www.ietf.org/shadow.html

This Internet-Draft will expire on October 10, 2012. implemented.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.

Abstract

This Code Components extracted from this document assigns a Generic Associated Channel (G-ACh) Type for
carrying ITU-T MPLS Transport Profile Operations, Administration, must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and
Management (MPLS-TP OAM) messages are provided without warranty as
described in the MPLS Generic Associated
Channel. Simplified BSD License.

1. Introduction

The Transport Profile of MPLS (MPLS-TP) defined in [RFC5654] is a
profile of MPLS technology for use in packet transport networks. The
MPLS-TP profile includes a set of Operations, Administration, and
Management (OAM) tools defined by the IETF
[I-D.ietf-mpls-tp-oam-analysis], [RFC6669] that are used to
meet the OAM functional requirements defined in [RFC5860].

ITU-T Recommendation [G.8113.1] documents MPLS-TP OAM. This
Recommendation builds upon Ethernet OAM as documented in [Y.1731].
The messages in [G.8113.1] are defined to be carried in a new Generic
Associated Channel (G-ACh) Type in the MPLS Generic Associated
Channel. In order to carry these messages in an interoperable
fashion, a Generic Associated Channel Type from the IANA maintained
registry "Pseudowire Associated Channel Types'' Types" is to be used.

To fulfill the request from ITU-T SG15 in [LS370] and to allow
deployment of the [G.8113.1] OAM solution without using an
experimental G-ACh Type, this document requests IANA to assign has assigned a G-
ACh G-ACh Type <TBD-value>
for use by the ITU-T for [G.8113.1]. This G-ACh type shall
be Type is known as the G.8113.1
"G.8113.1 OAM G-ACh Type. Type".

A number of experts in the IETF do not consider that the development
or deployment of a second protocol solution within the same
architectural problem space is necessary or advisable
[I-D.sprecher-mpls-tp-oam-considerations]. [RFC6670].

2. Conventions used Used in this document This Document

2.1. Requirements notation 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

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, Type are restricted to only those that address the OAM
functional requirements defined in [RFC5860]. Other message types
MUST NOT be carried behind this G-ACh type. Type.

All ITU-T Recommendations are subject to updates by errata,
corrigenda, amendments amendments, or complete revisions. In any update of
[G.8113.1]
[G.8113.1], the G-ACh Type assigned by this document MUST NOT be used
for any functions not identified as OAM functional requirements in
[RFC5860]. An update of [G.8113.1] may use the G-ACh Type assigned
by this document to support the OAM functions identified in
[RFC5860]. When an amendment or complete revision of G.8113.1 is
approved
approved, the reference to [G.8113.1], provided 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, e.g., MPLS-TP Sections, MPLS-TP LSPs LSPs,
or PWs as described in [G.8113.1].

4. Security Considerations

As noted in [RFC5586], when new G-ACh Types are defined, the
"security considerations MUST be described in the relevant associated
channel type specification." specification". The IETF takes this opportunity to
remind the ITU-T of the need to describe security considerations in
[G.8113.1].

5. IANA Considerations

IANA maintains a registry of Pseudowire the "Pseudowire Associated Channel Types as
a subregistry Types" sub-registry
of the Pseudowire "Pseudowire Name Spaces (PWE3)" registry.

IANA is requested to allocate has allocated a new G-ACh Type as follows:

Value Description TLV Follows Reference
----------- ----------------------- ----------- ---------
TBD G.8113.1 OAM No [This.I-D]

A value of 0x8902 is suggested. [RFC6671]

6. References

6.1. Normative References

[RFC2119] Key Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels, Levels", BCP 14, RFC 2119, March 1997 1997.

[RFC5586] MPLS Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
"MPLS Generic Associated Channel, Channel", RFC 5586, June 2009 2009.

[RFC5654] Requirements Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed.,
Sprecher, N., and S. Ueno, "Requirements of an MPLS
Transport Profile, Profile", RFC 5654, September 2009 2009.

[RFC5860] Requirements Vigoureux, M., Ed., Ward, D., Ed., and M. Betts, Ed.,
"Requirements for Operations, Administration, and
Maintenance (OAM) in MPLS Transport Networks, RFC5860, Networks", RFC 5860,
May
2010 2010.

[G.8113.1] ITU-T Recommendation ''Operations, Recommendation, "Operations, Administration and
Maintenance mechanism for MPLS-TP in Packet Transport
Network (PTN)'' 10/12,
http://www.itu.int/rec/T-REC-G.8113.1/en
(Note to RFC editor: This link will become valid after
G.8113.1 is approved) (PTN)", <date>,
http://www.itu.int/rec/T-REC-G.8113.1/en.

[Y.1731] ITU-T Recommendation ''OAM Recommendation, "OAM functions and mechanisms for
Ethernet based networks'' networks" 7/2007 as updated by Corrigendum
1, 10/2011, http://www.itu.int/rec/T-REC-Y.1731/en http://www.itu.int/rec/T-REC-Y.1731/en.

6.2. Informative References

[LS370] Liaison statement from "Liaison Statement: LS370 - Current status of
Recommendation ITU-T SG 15,
https://datatracker.ietf.org/liaison/1125/

[I-D.ietf-mpls-tp-oam-analysis] 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., N. and L. Fang, L., "An Overview of the OAM Operations,
Administration, and Maintenance (OAM) Tool Set for MPLS based MPLS-
Based Transport Networks", draft-ietf-mpls-
tp-oam-analysis, work in progress.

[I-D.sprecher-mpls-tp-oam-considerations] RFC 6669, July 2012.

[RFC6670] Sprecher, N. and KY. Hong, KY., "The Reasons for Selecting a
Single Solution for MPLS-TP OAM", draft-sprecher-mpls-tp-
oam-considerations, work in progress.

7. Acknowledgments

This document was prepared using 2-Word-v2.0.template.dot. MPLS Transport Profile (MPLS-TP)
Operations, Administration, and Maintenance (OAM)", RFC
6670, July 2012.

Author's Address

Malcolm Betts
ZTE

Email:

EMail: malcolm.betts@zte.com.cn