[dtn] [Errata Held for Document Update] RFC9171 (7881)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 07 April 2024 23:12 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38988C14F5F6; Sun, 7 Apr 2024 16:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=no 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 CFsggQENDjm5; Sun, 7 Apr 2024 16:12:46 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 A7BDBC14F5E3; Sun, 7 Apr 2024 16:12:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 57823CE3DB; Sun, 7 Apr 2024 16:12:46 -0700 (PDT)
To: jh571912@ohio.edu, sburleig.sb@gmail.com, kfall+rcs@kfall.com, edward.birrane@jhuapl.edu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ek.ietf@gmail.com, iesg@ietf.org, dtn@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240407231246.57823CE3DB@rfcpa.amsl.com>
Date: Sun, 07 Apr 2024 16:12:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/qlyvr34VaMfLVzTzh9VFfhqoE2I>
Subject: [dtn] [Errata Held for Document Update] RFC9171 (7881)
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2024 23:12:51 -0000

The following errata report has been held for document update 
for RFC9171, "Bundle Protocol Version 7". 

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

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

Reported by: John Huff <jh571912@ohio.edu>
Date Reported: 2024-04-03
Held by: Erik Kline (IESG)

Section: 6.1.1

Original Text
-------------
   The first element of each bundle status item SHALL be a status
   indicator, a Boolean value indicating whether or not the
   corresponding bundle status is asserted, encoded as a CBOR Boolean
   value.

Corrected Text
--------------
   The first element of each bundle status item SHALL be a status
   indicator, a Boolean value indicating whether or not the
   corresponding bundle status is asserted, encoded as a CBOR simple
   value.  A value of 'true' SHALL be encoded as a CBOR simple value
   with additional information 21.  A value of 'false' SHALL be encoded
   as a CBOR simple value with additional information 20.

Notes
-----
The CBOR spec does not define a 'Boolean' type (RFC8949). It's become common practice to encode boolean values as simple values (major type 7), with additional information 21 indicating 'true' and additional information 20 indicating 'false' (RFC9254, RFC8152). However, this should be explicitly stated for clarity.

--- comments ---

The original text refers to "Boolean values" and not to any "Boolean type"; it is technically correct as is.

As noted, CBOR doesn't have a specific "type" per se for a Boolean, but RFC 8948 S3.3 clearly specifies an encoding for `true` and `false`.

That said, there might be room here for additional clarity for implementers if there is ever to be a 9171bis.

--------------------------------------
RFC9171 (draft-ietf-dtn-bpbis-31)
--------------------------------------
Title               : Bundle Protocol Version 7
Publication Date    : January 2022
Author(s)           : S. Burleigh, K. Fall, E. Birrane, III
Category            : PROPOSED STANDARD
Source              : Delay/Disruption Tolerant Networking
Stream              : IETF
Verifying Party     : IESG