[Lime] [Editorial Errata Reported] RFC8531 (5719)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 05 May 2019 19:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E108412013F for <lime@ietfa.amsl.com>; Sun, 5 May 2019 12:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1yISWCXlYUAU for <lime@ietfa.amsl.com>; Sun, 5 May 2019 12:14:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3318120137 for <lime@ietf.org>; Sun, 5 May 2019 12:14:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E9155B821F0; Sun, 5 May 2019 12:14:31 -0700 (PDT)
To: dekumar@cisco.com, bill.wu@huawei.com, wangzitao@huawei.com, ibagdona@gmail.com, warren@kumari.net, cpignata@cisco.com, rbonica@juniper.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, lime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190505191431.E9155B821F0@rfc-editor.org>
Date: Sun, 05 May 2019 12:14:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/Vfw9Hzz9rbdfSUY5bUTthJH75ew>
X-Mailman-Approved-At: Sun, 05 May 2019 15:33:58 -0700
Subject: [Lime] [Editorial Errata Reported] RFC8531 (5719)
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." <lime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime>, <mailto:lime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lime/>
List-Post: <mailto:lime@ietf.org>
List-Help: <mailto:lime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime>, <mailto:lime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2019 19:14:34 -0000

The following errata report has been submitted for RFC8531,
"Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5719

--------------------------------------
Type: Editorial
Reported by: Nikolai Malykh <nmalykh@ieee.org>

Section: 4.4

Original Text
-------------
   There are several RPC commands defined for the purpose of OAM.  In
   this section, we present a snippet of the Continuity Check command
   for illustration purposes.  Please refer to Section 4.5 for the
   complete data hierarchy and Section 5 for the YANG module.


Corrected Text
--------------
   There are several RPC commands defined for the purpose of OAM.  In
   this section, we present a snippet of the Continuity Check command
   for illustration purposes.  Please refer to Section 4.7 for the
   complete data hierarchy and Section 5 for the YANG module.


Notes
-----
Incorrect Section No.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8531 (draft-ietf-lime-yang-connection-oriented-oam-model-07)
--------------------------------------
Title               : Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols
Publication Date    : April 2019
Author(s)           : D. Kumar, Q. Wu, Z. Wang
Category            : PROPOSED STANDARD
Source              : Layer Independent OAM Management in the Multi-Layer Environment
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG