[i2rs] [Editorial Errata Reported] RFC8431 (7359)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 17 February 2023 12:18 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE9AC14CE2E for <i2rs@ietfa.amsl.com>; Fri, 17 Feb 2023 04:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhQKMgrHUI1a for <i2rs@ietfa.amsl.com>; Fri, 17 Feb 2023 04:18:25 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CBFAC151524 for <i2rs@ietf.org>; Fri, 17 Feb 2023 04:18:23 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5DF5D4C923; Fri, 17 Feb 2023 04:18:23 -0800 (PST)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, wang_little_star@sina.com, mach.chen@huawei.com, dass.amit@gmail.com, hari@netflix.com, sriganeshkini@gmail.com, nitin_bahadur@yahoo.com, i2rs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230217121823.5DF5D4C923@rfcpa.amsl.com>
Date: Fri, 17 Feb 2023 04:18:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/NLaafIld0QM_S92pxdn-fImlDqQ>
Subject: [i2rs] [Editorial Errata Reported] RFC8431 (7359)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2023 12:18:29 -0000

The following errata report has been submitted for RFC8431,
"A YANG Data Model for the Routing Information Base (RIB)".

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

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

Section: 3

Original Text
-------------
     grouping vxlan-header {
       description
         "The VXLAN encapsulation header information.";
       choice vxlan-type {
         description
           "NVGRE can use either an IPv4
            or an IPv6 header for encapsulation.";
         case ipv4 {
           uses ipv4-header;
         }
         case ipv6 {
           uses ipv6-header;
         }
       }
       leaf vxlan-identifier {
         type uint32;
         mandatory true;
         description
           "The VXLAN identifier of the VXLAN header.";
       }
     }


Corrected Text
--------------
     grouping vxlan-header {
       description
         "The VXLAN encapsulation header information.";
       choice vxlan-type {
         description
           "VXLAN can use either an IPv4
            or an IPv6 header for encapsulation.";
         case ipv4 {
           uses ipv4-header;
         }
         case ipv6 {
           uses ipv6-header;
         }
       }
       leaf vxlan-identifier {
         type uint32;
         mandatory true;
         description
           "The VXLAN identifier of the VXLAN header.";
       }
     }


Notes
-----
In the description, instead of VXLAN, NVGRE is indicated (page 49)

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. 

--------------------------------------
RFC8431 (draft-ietf-i2rs-rib-data-model-15)
--------------------------------------
Title               : A YANG Data Model for the Routing Information Base (RIB)
Publication Date    : September 2018
Author(s)           : L. Wang, M. Chen, A. Dass, H. Ananthakrishnan, S. Kini, N. Bahadur
Category            : PROPOSED STANDARD
Source              : Interface to the Routing System
Area                : Routing
Stream              : IETF
Verifying Party     : IESG