BCP 191, RFC 7319 on IANA Considerations for Connectivity Fault Management (CFM) Code Points

rfc-editor@rfc-editor.org Fri, 18 July 2014 20:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5F11B27A0 for <ietf-announce@ietfa.amsl.com>; Fri, 18 Jul 2014 13:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_gOVxEy1reR for <ietf-announce@ietfa.amsl.com>; Fri, 18 Jul 2014 13:40:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5BADF1B29FF for <ietf-announce@ietf.org>; Fri, 18 Jul 2014 13:40:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1E22A18001B; Fri, 18 Jul 2014 13:39:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 191, RFC 7319 on IANA Considerations for Connectivity Fault Management (CFM) Code Points
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140718203929.1E22A18001B@rfc-editor.org>
Date: Fri, 18 Jul 2014 13:39:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/wznMe9y-IIeJY4jl03CxIA5D4_0
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 20:40:33 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 191        
        RFC 7319

        Title:      IANA Considerations for Connectivity Fault 
                    Management (CFM) Code Points 
        Author:     D. Eastlake 3rd
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2014
        Mailbox:    d3e3e3@gmail.com
        Pages:      5
        Characters: 7759
        See Also:   BCP 191

        I-D Tag:    draft-eastlake-iana-cfm-considerations-02.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7319.txt

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.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC