RFC Errata
RFC 8040, "RESTCONF Protocol", January 2017
Note: This RFC has been updated by RFC 8527
Source of RFC: netconf (ops)
Errata ID: 6362
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Muly Ilan
Date Reported: 2020-12-22
Rejected by: Rob Wilton
Date Rejected: 2024-01-15
Section 4.3. says:
The client might request the response header fields for an XML representation of a specific "album" resource: GET /restconf/data/example-jukebox:jukebox/\ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com Accept: application/yang-data+xml The server might respond as follows: HTTP/1.1 200 OK Date: Thu, 26 Jan 2017 20:56:30 GMT Server: example-server Content-Type: application/yang-data+xml Cache-Control: no-cache ETag: "a74eefc993a2b" Last-Modified: Thu, 26 Jan 2017 14:02:14 GMT
It should say:
The client might request the response header fields for an XML representation of a specific "album" resource: GET /restconf/data/example-jukebox:jukebox/\ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com Accept: application/yang-data+xml The server might respond as follows: HTTP/1.1 200 OK Date: Thu, 26 Jan 2017 20:56:30 GMT Server: example-server Content-Type: application/yang-data+xml Cache-Control: no-cache
Notes:
Removed the "ETag" and "Last-Modified" header fields.
According to Appendix B.3.1. :
To retrieve only the configuration child resources, the "content"
parameter is set to "config". Note that the "ETag" and
"Last-Modified" headers are only returned if the "content" parameter
value is "config".
--VERIFIER NOTES--
This has been discussed at: https://mailarchive.ietf.org/arch/msg/netconf/SIpDoR7W8_na_USDHdMApjW6Wu8/
The example is not incorrect because an ETag and Last-Modified header are allowed to be returned if no content parameter has been specified, but only apply to the configuration data.
Note, the referenced text in Appendix B.3.1 (Note that the "ETag" and
"Last-Modified" headers are only returned if the "content" parameter
value is "config") looks to be incorrect and should be removed or clarified in a future revision of the protocol.