RFC 7252, "The Constrained Application Protocol (CoAP)", June 2014

Note: This RFC has been updated by RFC 7959, RFC 8613, RFC 8974, RFC 9175

Errata ID: 4946
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Klaus Hartke
Date Reported: 2017-02-22
Rejected by: Francesca Palombini
Date Rejected: 2023-01-18

Section 6.1 says:

coap-URI = "coap:" "//" host [ ":" port ] path-abempty [ "?" query ]

It should say:

coap-URI = "coap:" "//" host [ ":" port ] path-abempty [ "?" query ]
               [ "#" fragment ]

Notes:

The optional fragment component allows for indirect identification of a secondary resource, as defined in Section 3.5 of RFC 3986. The fragment identifier is separated from the rest of the URI prior to a dereference; fragment identifiers are processed client-side and are not included in CoAP requests. The original text shows the syntax of coap:// URIs _after_ separating the fragment identifier, which leaves ambiguity as to whether fragment identifiers are supported or not. The corrected text shows the syntax of CoAP URIs _before_ separating the fragment identifier, which makes clear that fragment identifiers are supported.
--VERIFIER NOTES--
This errata is rejected to remain aligned with HTTP, see RFC 9110, Section 4.2.1

Report New Errata