[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 RFC 7319

Network Working Group                                Donald Eastlake 3rd
Internet-Draft                                                    Huawei
Intended Status: Best Current Practice
Expires: November 21, 2014                                  May 22, 2014


IANA Considerations for CFM (Connectivity Fault Management) Code Points
            <draft-eastlake-iana-cfm-considerations-02.txt>


Status of This Document

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

   This document is intended to become a Best Current Practice.
   Distribution of this document is unlimited. Comments should be sent
   to the author.

   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/1id-abstracts.html. The list of Internet-Draft
   Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


Abstract

   IEEE 802.1 has specified Connectivity Fault Management (CFM) OAM
   facilities. CFM messages are structured with an OpCode field and have
   provision for the inclusion of TLV (type, length, value) 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.












D. Eastlake                                                     [Page 1]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


Table of Contents

      1. Introduction............................................3
      1.1 Terminology............................................3

      2. IANA Considerations.....................................4
      3. Security Considerations.................................4

      Normative References.......................................5
      Informative References.....................................5
      Author's Address...........................................5

      Appendix A: IEEE 802.1 WG Liaison..........................6







































D. Eastlake                                                     [Page 2]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


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 (type, length, value) 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 the values from 32
   through 63 to ITU-T [Y.1731].



1.1 Terminology

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































D. Eastlake                                                     [Page 3]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


2. IANA Considerations

   IANA is requested to create a "CFM OAM IETF Parameters" Registry with
   two registries as follows:


         Registry Name: CFM OAM IETF OpCodes

         Registration Procedures: Standards Action

         Reference: [802.1Q] [this document]

         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    Reference
         =====    ==========    =========
         64-95    Unassigned    [this document]


         Registry Name: CFM OAM IETF TLV Types

         Registration Procedures: Standards Action

         Reference: [802.1Q] [this document]

         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    Reference
         =====    ==========    =========
         64-95    Unassigned    [this document]



3. Security Considerations

   This document is concerned with assignment of values from the blocks
   of IEEE 802.1 CFM OpCodes and TLV Types that the IEEE 802.1 Working
   Group has allocated to the IETF. It is not directly concerned with
   security.









D. Eastlake                                                     [Page 4]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


Normative References

   [802.1Q] - "IEEE Standard for Local and metropolitan area networks /
         Media Access Control (MAC) Bridges and Virtual Bridge Local
         Area Networks", IEEE Std 802.1Q-2011, 31 August 2011.

   [RFC5226] - Narten, T. and H. Alvestrand, "Guidelines for Writing an
         IANA Considerations Section in RFCs", BCP 26, RFC 5226, May
         2008.



Informative References

   [RFC6291] - Andersson, L., van Helvoort, H., Bonica, R., Romascanu,
         D., and S. Mansfield, "Guidelines for the Use of the "OAM"
         Acronym in the IETF", BCP 161, RFC 6291, June 2011.

   [Y.1731] - ITU-T Recommendation G.8013/Y.1731, "OAM Functions and
         Mechanisms for Ethernet-based Networks", July 2011.



Author's Address

   Donald Eastlake 3rd
   Huawei
   155 Beaver Street
   Milford, MA 01757 USA

   tel:   +1-508-333-2270
   email: d3e3e3@gmail.com




















D. Eastlake                                                     [Page 5]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


Appendix A: IEEE 802.1 WG Liaison

   To:         Jari Arkko, IETF chair
   cc:         Stephen J. Trowbridge, ITU-T SG15 chair,
               Donald Eastlake, Erik Nordmark, IETF TRILL WG,
               Eric Gray, IETF/IEEE liaison

   From:       Tony Jeffree, IEEE 802.1 WG Chair

   Date:       Thursday, 06 March 2014

   Reference:  24 September 2013 Liaison from TRILL WG

   After considering the referenced liaison from the TRILL WG,
   IEEE 802.1 has voted to approve the allocation of code points
   from the Connectivity Fault Management protocol of IEEE Std
   802.1Q(TM)-2011 for use by IETF.  The expectation of IEEE
   802.1 is that these code points will be allocated through
   IANA only on the basis of IETF standards actions.
   Specifically, the allocation includes:


     + 32 CFM OpCode Field values. Reference IEEE Std 802.1Q-2011

       Clause 21.4.3, Table 21-4. The OpCode Field values 64-95
                                                               10
       are allocated to the IETF.


     + 32 TLV Type Field values. Reference IEEE Std 802.1Q-2011

       Clause 21.5.1.1, Table 21-6. The Type Field values 64-95
                                                               10
       are allocated to the IETF.


   IEEE Std 802.1Q will be revised at some future date to document this
   allocation. In the meantime, the allocation will be recorded through
   the IEEE 802.1 maintenance process.

   Regards,

   Tony Jeffree
   IEEE 802.1 Working Group Chair








D. Eastlake                                                     [Page 6]


INTERNET-DRAFT                   IANA Considerations for CFM Code Points


Copyright and IPR Provisions

   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.






































D. Eastlake                                                     [Page 7]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/