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

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 11 April 2021 16:11 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 A5E483A12B3 for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6Tm0hUynbYGA for <cbor@ietfa.amsl.com>; Sun, 11 Apr 2021 09:10:57 -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 272DD3A12AF for <cbor@ietf.org>; Sun, 11 Apr 2021 09:10:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9648FF40799; Sun, 11 Apr 2021 09:10:45 -0700 (PDT)
To: henk.birkholz@sit.fraunhofer.de, christoph.vigano@uni-bremen.de, cabo@tzi.org, superuser@gmail.com, francesca.palombini@ericsson.com, barryleiba@computer.org, christian@amsuess.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: smbarte2@illinois.edu, cbor@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210411161045.9648FF40799@rfc-editor.org>
Date: Sun, 11 Apr 2021 09:10:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/WI3Lpora3FTZrAzOpKDMW55txwA>
X-Mailman-Approved-At: Wed, 14 Apr 2021 02:21:06 -0700
Subject: [Cbor] [Technical Errata Reported] RFC8610 (6527)
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: Sun, 11 Apr 2021 16:11:02 -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/eid6527

--------------------------------------
Type: Technical
Reported by: Sean Bartell <smbarte2@illinois.edu>

Section: B

Original Text
-------------
     SESC = "\" (%x20-7E / %x80-10FFFD)

Corrected Text
--------------
     SESC = "\" (%x22 / %x27 / %x2F / %x5C / %x62 / %x66 / %x6E / %x72 / %x74 / %x75 4HEXDIG )

Notes
-----
The ABNF rule for string escape codes should specify which escape codes are allowed, and also specify that "\u" must be followed by four hex digits. My suggested correction is based on JSON, but with the addition of "\'" (single quote) for use in text-based byte strings (section G.2). (Presumably, characters outside the BMP must be escaped using a surrogate pair, as in JSON.)

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