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

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

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD5FC151988 for <core@ietfa.amsl.com>; Mon, 5 Jun 2023 02:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haCISgfJViAV for <core@ietfa.amsl.com>; Mon, 5 Jun 2023 02:01:07 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB9B2C151985 for <core@ietf.org>; Mon, 5 Jun 2023 02:01:05 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QZSJG4B3BzDCg2; Mon, 5 Jun 2023 11:01:02 +0200 (CEST)
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>
X-Mao-Original-Outgoing-Id: 707648462.097764-d5c52ddb4aed1bfc77cb672e156b22f3
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>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/w_OT6Kr-4RWoKR1OSYiICPRcGe8>
Subject: Re: [core] [Editorial Errata Reported] RFC7959 (7523)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 09:01:11 -0000

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