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

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

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: <20230217133442.C51904C923@rfcpa.amsl.com>
Date: Fri, 17 Feb 2023 05:34:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/Q5F6KqNxXoPg8Q3ok41dEl7av98>
Subject: [i2rs] [Editorial Errata Reported] RFC8431 (7361)
Precedence: list

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/eid7361

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

Section: 3

Original Text
-------------
     rpc route-update {
       description
         "To update a route or a list of routes of a RIB.
          The inputs:
            1. The match conditions, which could be:
              a. route prefix,
              b. route attributes, or
              c. nexthop.
            2. The update parameters to be used:
              a. new nexthop,
              b. new route attributes, or
              c. nexthop.


Corrected Text
--------------
     rpc route-update {
       description
         "To update a route or a list of routes of a RIB.
          The inputs:
            1. The match conditions, which could be:
              a. route prefix,
              b. route attributes, or
              c. nexthop.
            2. The update parameters to be used:
              a. new nexthop, or
              b. new route attributes

Notes
-----
Excess item 2.c (page 61)

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

[i2rs] [Editorial Errata Reported] RFC8431 (7361) RFC Errata System