Subject: [netmod] [Errata Rejected] RFC8349 (6251)

From: RFC Errata System <[email-masked]>
Date: Fri, 14 Aug 2020 10:41:56 -0700 (PDT)

The following errata report has been rejected for RFC8349,
"A YANG Data Model for Routing Management (NMDA Version)".

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

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Tarek Saad <[email-masked]>
Date Reported: 2020-08-07
Rejected by: Rob Wilton (IESG)

Section: 7

Original Text
-------------
The RPC "active-route" is used to retrieve the active route in a RIB.
RFC8349 defined two AFIs (v4/v6).

draft-ietf-mpls-base-yang is defining a new RIB AFI for MPLS as per section 3 in RFC8349.

The RPC has a "MUST" statement that all RIBs must augment input
parameters with a leaf named 'destination-address'.

For MPLS RIB, it makes sense to augment with leaf named 'local-label' since MPLS routes are identified by MPLS label.

We ask to make the following change:

OLD:
           action active-route {
             description
               "Return the active RIB route that is used for the
                destination address.

                Address-family-specific modules MUST augment input
                parameters with a leaf named 'destination-address'.";

Corrected Text
--------------
NEW:
           action active-route {
             description
               "Return the active RIB route that is used for the
                destination address.

                Address-family-specific modules MUST augment input
                parameters with a suitable leaf that identifies the route.";

Notes
-----

 --VERIFIER NOTES-- 
After discussion between the submitter and authors of the RFC it was agreed that the errata should be rejected.

--------------------------------------
RFC8349 (draft-ietf-netmod-rfc8022bis-11)
--------------------------------------
Title               : A YANG Data Model for Routing Management (NMDA Version)
Publication Date    : March 2018
Author(s)           : L. Lhotka, A. Lindem, Y. Qu
Category            : PROPOSED STANDARD
Source              : Network Modeling
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG