[core] [Errata Held for Document Update] RFC7252 (4895)

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

To: esko.dijk@philips.com, 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
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230118085642.3B11E961FB@rfcpa.amsl.com>
Date: Wed, 18 Jan 2023 00:56:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/siPCwad_vLLbil5fqTxMRgL69DU>
Subject: [core] [Errata Held for Document Update] RFC7252 (4895)
Precedence: list

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

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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Esko Dijk <esko.dijk@philips.com>
Date Reported: 2016-12-23
Held by: Francesca Palombini (IESG)

Section: 6.4

Original Text
-------------
Note that these rules completely resolve any percent-encoding.

Corrected Text
--------------
Note that these rules completely resolve any percent-encoding. Also
note that a trailing slash character in the <path> component represents
a separate, zero-character path segment (see [RFC3986] Section 3.3
ABNF) and therefore it is encoded using a Uri-Path Option of zero
length.

Notes
-----
The current specification for decomposing a URI into CoAP Options (Section 6.4) is correct; however the text may still be unclear to implementers who may think that the phrase "not including the delimiting slash characters" means simply omitting a trailing slash character in the URI path. This is incorrect. See the discussion outcome in email thread https://www.ietf.org/mail-archive/web/core/current/msg08223.html . Therefore, a minor clarification is proposed in the notes after the parsing steps.

--------------------------------------
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 Held for Document Update] RFC7252 … RFC Errata System