Re: [netconf] [Technical Errata Reported] RFC8040 (5761)

[Andy Bierman <[e-mail]>]

Hi,

The cited text is in 4.4.1 (there is no 4.1.1).

I do not see any evidence that the WG intended to write the word
"data-exists" but
wrote "resource-denied" instead. Therefore this cannot be changed with an
errata.


Andy


On Sun, Jun 23, 2019 at 6:08 PM 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:
> https://www.rfc-editor.org/errata/eid5761
>
> --------------------------------------
> Type: Technical
> Reported by: Qin WU <[e-mail]>
>
> Section: 4.1.1
>
> Original Text
> -------------
> If the data resource already exists, then the POST request MUST fail
> and a "409 Conflict" status-line MUST be returned.  The error-tag
> value "resource-denied" is used in this case
>
> Corrected Text
> --------------
> If the data resource already exists, then the POST request MUST fail
> and a "409 Conflict" status-line MUST be returned.  The error-tag
> value "data-exists" is used in this case
>
> Notes
> -----
> The error-tag value should be corrected as "data-exists" in this case
> based on the context. According to error-tag definition in RFC6241:
>
>    error-tag:      resource-denied
>    error-type:     transport, rpc, protocol, application
>    error-severity: error
>    error-info:     none
>    Description:    Request could not be completed because of
>                    insufficient resources.
>
> It is apparent error-tag value "data-exists" should be corresponding
> to the data resource already exists condition.
>
> 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
>