[core] [Errata Rejected] RFC7252 (4946)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 18 January 2023 09:01 UTC

To: hartke@tzi.org, zach.shelby@arm.com, hartke@tzi.org, cabo@tzi.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, core@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230118090121.10B5B961FB@rfcpa.amsl.com>
Date: Wed, 18 Jan 2023 01:01:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/N9t0elpJEjp-0L3UMdFw_UkB6K8>
Subject: [core] [Errata Rejected] RFC7252 (4946)
Precedence: list

The following errata report has been rejected for RFC7252,
"The Constrained Application Protocol (CoAP)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid4946

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Klaus Hartke <hartke@tzi.org>
Date Reported: 2017-02-22
Rejected by: Francesca Palombini (IESG)

Section: 6.1

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

Corrected Text
--------------
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

--------------------------------------
RFC7252 (draft-ietf-core-coap-18)
--------------------------------------
Title               : The Constrained Application Protocol (CoAP)
Publication Date    : June 2014
Author(s)           : Z. Shelby, K. Hartke, C. Bormann
Category            : PROPOSED STANDARD
Source              : Constrained RESTful Environments APP
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

[core] [Errata Rejected] RFC7252 (4946) RFC Errata System