[Cbor] [Technical Errata Reported] RFC8610 (6278)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 04 September 2020 00:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49BD3A13EE for <cbor@ietfa.amsl.com>; Thu, 3 Sep 2020 17:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFfVboYFskqa for <cbor@ietfa.amsl.com>; Thu, 3 Sep 2020 17:17:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77B2F3A07F2 for <cbor@ietf.org>; Thu, 3 Sep 2020 17:17:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6E249F40781; Thu, 3 Sep 2020 17:17:02 -0700 (PDT)
To: henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org, superuser@gmail.com, barryleiba@computer.org, francesca.palombini@ericsson.com, ietf@augustcellars.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: eds@reric.net, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200904001702.6E249F40781@rfc-editor.org>
Date: Thu, 3 Sep 2020 17:17:02 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Q8Rry56az-_5bd4j-u5g0-jlKZg>
X-Mailman-Approved-At: Thu, 03 Sep 2020 17:34:11 -0700
Subject: [Cbor] [Technical Errata Reported] RFC8610 (6278)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Sep 2020 00:17:20 -0000

The following errata report has been submitted for RFC8610,
"Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures".

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

--------------------------------------
Type: Technical
Reported by: Eric Seppanen <eds@reric.net>

Section: Appendix B

Original Text
-------------
BCHAR = %x20-26 / %x28-5B / %x5D-10FFFD / SESC / CRLF


Corrected Text
--------------
BCHAR = %x20-26 / %x28-5B / %x5D-7E / %x80-10FFFD / SESC / CRLF


Notes
-----
Between draft 6 and 7 of the RFC, the ASCII DELETE character 0x7F was excluded from the character set allowed in text literals.  I believe it should also be excluded from the character set of bytestring literals.

A 0x7F byte could not be decoded if included in a hex or base64 bytestring, leaving only UTF-8 bytestrings.  Since there is no discussion in the text of any reason to allow this character in a UTF-8 bytestring when it was not allowed in a UTF-8 text string, I suspect this was an oversight.

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. 

--------------------------------------
RFC8610 (draft-ietf-cbor-cddl-08)
--------------------------------------
Title               : Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
Publication Date    : June 2019
Author(s)           : H. Birkholz, C. Vigano, C. Bormann
Category            : PROPOSED STANDARD
Source              : Concise Binary Object Representation Maintenance and Extensions
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG