RFC Errata
Found 1 record.
Status: Verified (1)
RFC 8072, "YANG Patch Media Type", February 2017
Source of RFC: netconf (ops)
Errata ID: 5131
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Robert Wilton
Date Reported: 2017-09-28
Verifier Name: Benoit Claise
Date Verified: 2017-10-12
Section 2.2 says:
Regarding section 2.2 of RFC 8072, the third paragraph states: ... If the edit does not identify any existing resource instance and the operation for the edit is not "create", then the request MUST NOT be processed and a "404 Not Found" error response MUST be sent by the server.
It should say:
... If the edit does not identify any existing resource instance and the operation for the edit is "delete" or "move" then the request MUST NOT be processed and a "404 Not Found" error response MUST be sent by the server.
Notes:
As per the second paragraph of section 2.2 of RFC 8072, the operations are expected to mirror the semantics of the "operation" attribute described in Section 7.2 of [RFC6241].
The spec also doesn't specify what happens if it is a "create" operation and the resource already exists. It should probably also state that "400 Bad Request" is returned.