Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM
draft-betts-itu-oam-ach-code-point-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rtg area)
Last updated 2012-03-26 (latest revision 2012-02-20)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd None
IESG IESG state Waiting for AD Go-Ahead::Point Raised - writeup needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
IESG note Huub van Helvoort (Huub.van.Helvoort@huawei.com) is the document shepherd.
Send notices to malcolm.betts@zte.com.cn, draft-betts-itu-oam-ach-code-point@tools.ietf.org, Huub.van.Helvoort@huawei.com
Network Working Group                                          M. Betts
Internet Draft                                                      ZTE
Intended status: Informational                        February 20, 2012
Expires: August 20, 2012

      Allocation of an Associated Channel Code Point for Use by ITU-T
                            Ethernet based OAM
                 draft-betts-itu-oam-ach-code-point-03.txt

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on August 20, 2012.

Copyright Notice

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

   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.

Betts                  Expires August 20, 2012                 [Page 1]
Internet-Draft     ACh code point for Ethernet OAM        February 2012

Abstract

   This document assigns an Associated Channel Type code point for
   carrying Ethernet based Operations, Administration, and Management
   messages in the MPLS Generic Associated Channel (G-ACh).

1. Introduction

   MPLS-TP 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], that are intended to meet the OAM
   functional requirements defined in [RFC5860].

   The ITU-T has documented, in draft new Recommendation [G.8113.1], the
   use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
   carried in the MPLS Generic Associated Channel (G-ACh). This approach
   requires the allocation of an ACH Type from the registry of ACH types
   maintained by IANA in order that the messages that will be described
   in [G.8113.1] can be identified by an implementation.

   To fulfill the request from ITU-T SG15 in [LS370] and to allow
   deployment of an Ethernet based OAM solution without continuing to
   resorting to the use of an experimental ACH Type, this document
   requests IANA to assign an ACH Type code point for use by the ITU-T.
   The ACH type shall be known as the Ethernet based OAM ACH 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].

2. Scope of the Ethernet based OAM ACH Type

   The code point allocated by this document is intended to be used only
   for Ethernet based OAM messages, defined in the ITU-T Recommendation
   [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
   and procedures, address the OAM functional requirements defined in
   [RFC5860]. Other message types should not be carried behind this code
   point.

   This code point may be used on any transport construct that uses the
   G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.

Betts                  Expires August 20, 2012                 [Page 2]
Internet-Draft     ACh code point for Ethernet OAM        February 2012

   All ITU-T Recommendations are subject to revisions. Therefore, the
   code point allocated by this document may be used for future versions
   of [G.8113.1].

3. Security Considerations

   As noted in [RFC5586], when new ACH Types are defined the "security
   considerations must be described in the relevant associated channel
   type." Thus, any specification of messages to be carried on the
   Ethernet OAM ACH Type must include the necessary security
   considerations. The IETF takes this opportunity to remind the ITU-T
   of the need to describe security considerations in [G.8113.1].

4. IANA Considerations

   IANA maintains a registry of Pseudowire Associated Channel Types as a
   subregistry of the Pseudowire Name Spaces registry.
Show full document text