IANA Considerations for Connectivity Fault Management (CFM) Code Points
RFC 7319

 
Document
Type RFC - Best Current Practice (July 2014; No errata)
Also known as BCP 191
Last updated 2014-07-18
Stream IETF
Formats plain text pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd Sam Aldrin
Shepherd write-up Show (last changed 2014-04-18)
IESG
IESG state RFC 7319 (Best Current Practice)
Telechat date
Responsible AD Ted Lemon
Send notices to d3e3e3@gmail.com, draft-eastlake-iana-cfm-considerations@ietf.org
IANA
IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack

Email authors IPR References Referenced by Nits Search lists

Internet Engineering Task Force (IETF)                   D. Eastlake 3rd
Request for Comments: 7319                                        Huawei
BCP: 191                                                       July 2014
Category: Best Current Practice
ISSN: 2070-1721

IANA Considerations for Connectivity Fault Management (CFM) Code Points

Abstract

   IEEE 802.1 has specified Connectivity Fault Management (CFM)
   Operations, Administration, and Maintenance (OAM) facilities.  CFM
   messages are structured with an OpCode field and have provision for
   the inclusion of TLV-structured information.  IEEE 802.1 has
   allocated blocks of CFM OpCodes and TLV Types to the IETF.  This
   document specifies the IANA considerations for the assignment of
   values from these blocks.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force
   (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).  Further information on
   BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7319.

Copyright Notice

   Copyright (c) 2014 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Eastlake                  Best Current Practice                 [Page 1]
RFC 7319         IANA Considerations for CFM Code Points       July 2014

Table of Contents

   1. Introduction ....................................................2
      1.1. Terminology ................................................2
   2. IANA Considerations .............................................2
   3. Security Considerations .........................................3
   4. References ......................................................3
      4.1. Normative References .......................................3
      4.2. Informative References .....................................3
   Appendix A.  IEEE 802.1 WG Liaison .................................6

1.  Introduction

   The IEEE 802.1 Working Group has specified Connectivity Fault
   Management (CFM) [802.1Q] OAM [RFC6291] facilities.  CFM messages are
   structured with an OpCode field and have provision for the inclusion
   of TLV-structured information.

   IEEE 802.1 has allocated the block of 32 CFM OpCodes from 64 through
   95 and the block of 32 CFM TLV Types from 64 through 95 to the IETF
   (see Appendix A).  This document specifies the IANA considerations
   for the assignment of values from these two blocks.

   IEEE 802.1 previously allocated similar blocks of values from 32
   through 63 to ITU-T [Y.1731].

1.1.  Terminology

   Capitalized IANA terms such as "Standards Action" are to be
   interpreted as described in [RFC5226].

2.  IANA Considerations

   IANA has created the "Connectivity Fault Management (CFM) OAM IETF
   Parameters" registry with the following two subregistries:

      Registry Name: CFM OAM IETF OpCodes

      Registration Procedures: Standards Action

      Reference: [802.1Q] [RFC7319]

      Note: This parameter originates with the IEEE 802.1 Working Group
      that has allocated the block of values from 64 to 95 to the IETF.

      Value    Assignment
      =====    ==========
      64-95    Unassigned

Eastlake                  Best Current Practice                 [Page 2]
RFC 7319         IANA Considerations for CFM Code Points       July 2014

      Registry Name: CFM OAM IETF TLV Types

      Registration Procedures: Standards Action

      Reference: [802.1Q] [RFC7319]

      Note: This parameter originates with the IEEE 802.1 Working Group
      that has allocated the block of values from 64 to 95 to the IETF.

      Value    Assignment
      =====    ==========
      64-95    Unassigned

3.  Security Considerations

   This document is concerned with assignment of values from the blocks
Show full document text