Re: [core] [Editorial Errata Reported] RFC7959 (7523)

Carsten Bormann <cabo@tzi.org> Mon, 05 June 2023 09:01 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20230524081839.95D887FDFD@rfcpa.amsl.com>
Date: Mon, 05 Jun 2023 11:01:02 +0200
Cc: Christian Amsüss <christian@amsuess.com>, Zach Shelby <zach.shelby@arm.com>, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3965FA75-8C96-4C52-958F-92C6BB8CB1CA@tzi.org>
References: <20230524081839.95D887FDFD@rfcpa.amsl.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/w_OT6Kr-4RWoKR1OSYiICPRcGe8>
Subject: Re: [core] [Editorial Errata Reported] RFC7959 (7523)
Precedence: list

This is a valid erratum; the errata report needs to be verified.

(It is properly editorial as this is about a mistake in a legend for the examples; the normative part of the specification is not concerned.)

Grüße, Carsten



> On 2023-05-24, at 10:18, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC7959,
> "Block-Wise Transfers in the Constrained Application Protocol (CoAP)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7523
> 
> --------------------------------------
> Type: Editorial
> Reported by: Christian Amsüss <christian@amsuess.com>
> 
> Section: 3
> 
> Original Text
> -------------
>   then the block number (NUM), more bit (M), and block size exponent
>   (2**(SZX+4)) separated by slashes.  For example, a Block2 Option
> 
> Corrected Text
> --------------
>   then the block number (NUM), more bit (M), and block size
>   (2**(SZX+4)) separated by slashes.  For example, a Block2 Option
> 
> Notes
> -----
> The examples are given in the style of "2:1/1/128", wher 128 is the size (2**(SZX+4)), not the size exponent -- it contains the size exponent in the expression, but the full expression is the size.
> 
> (Reporting this as an erratum because the use of "SZX" for "size" instead of "size exponent" has some potential for spreading and creating confusion; for example in Wireshark at https://gitlab.com/wireshark/wireshark/-/merge_requests/10763)
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC7959 (draft-ietf-core-block-21)
> --------------------------------------
> Title               : Block-Wise Transfers in the Constrained Application Protocol (CoAP)
> Publication Date    : August 2016
> Author(s)           : C. Bormann, Z. Shelby, Ed.
> Category            : PROPOSED STANDARD
> Source              : Constrained RESTful Environments
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG

[core] [Editorial Errata Reported] RFC7959 (7523) RFC Errata System
Re: [core] [Editorial Errata Reported] RFC7959 (7… Carsten Bormann