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

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

Return-Path: <wwwrun@rfcpa.amsl.com>
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 DDF44C15108B for <core@ietfa.amsl.com>; Wed, 24 May 2023 01:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.107
X-Spam-Level:
X-Spam-Status: No, score=-3.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.84, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 S19JjwMWNSRI for <core@ietfa.amsl.com>; Wed, 24 May 2023 01:18:39 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 BE9DBC1519B9 for <core@ietf.org>; Wed, 24 May 2023 01:18:39 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 95D887FDFD; Wed, 24 May 2023 01:18:39 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: christian@amsuess.com, cabo@tzi.org, zach.shelby@arm.com, core@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230524081839.95D887FDFD@rfcpa.amsl.com>
Date: Wed, 24 May 2023 01:18:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/-nWMiHhdXIxV1n51fWqxxjqYEhw>
Subject: [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: Wed, 24 May 2023 08:18:44 -0000

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