Re: [Netconf] [Technical Errata Reported] RFC8040 (5565)

[Martin Bjorklund <[e-mail]>]

Hi,

I don't think this errata should be accepted.  404 means that the
requested resource doesn't exist, but "data-missing" can be returned
e.g. if you try to patch an existing resource of type leafref to point
to a non-existing leaf.


/martin


RFC Errata System <[e-mail]> wrote:
> The following errata report has been submitted for RFC8040,
> "RESTCONF Protocol".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5565
> 
> --------------------------------------
> Type: Technical
> Reported by: Qin Wu <[e-mail]>
> 
> Section: 7
> 
> Original Text
> -------------
>               +-------------------------+------------------+
>               | error-tag               | status code      |
>               +-------------------------+------------------+
>               | in-use                  | 409              |
>               | lock-denied             | 409              |
>               | resource-denied         | 409              |
>               | data-exists             | 409              |
>               | data-missing            | 409              |
> 
> 
> Corrected Text
> --------------
>               +-------------------------+------------------+
>               | error-tag               | status code      |
>               +-------------------------+------------------+
>               | in-use                  | 409              |
>               | lock-denied             | 409              |
>               | resource-denied         | 409              |
>               | data-exists             | 409              |
>               | data-missing            | 404              |
> 
> 
> Notes
> -----
> The <error-tag> data missing should be mapped to status code '404' instead of '409' to get consistent with the defintion of data-missing in RFC6241.
> 
> 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. 
> 
> --------------------------------------
> RFC8040 (draft-ietf-netconf-restconf-18)
> --------------------------------------
> Title               : RESTCONF Protocol
> Publication Date    : January 2017
> Author(s)           : A. Bierman, M. Bjorklund, K. Watsen
> Category            : PROPOSED STANDARD
> Source              : Network Configuration
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>