Re: [Cbor] [Technical Errata Reported] RFC8610 (6575)
Barry Leiba <barryleiba@computer.org> Wed, 01 June 2022 14:15 UTC
Return-Path: <barryleiba@gmail.com>
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 25BFBC14F747 for <cbor@ietfa.amsl.com>; Wed, 1 Jun 2022 07:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level:
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 TfJdX9cW_srN for <cbor@ietfa.amsl.com>; Wed, 1 Jun 2022 07:15:22 -0700 (PDT)
Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 857F3C14F742 for <cbor@ietf.org>; Wed, 1 Jun 2022 07:15:22 -0700 (PDT)
Received: by mail-ed1-f45.google.com with SMTP id b8so2369476edf.11 for <cbor@ietf.org>; Wed, 01 Jun 2022 07:15:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=76U1NUG171iXLv4wSiDKiSKAecYjWo/U7N29E2HjPxY=; b=K1XyDxSklevC3/ERvf1yTywW1fqJC3maVw1NQ5ECtdaG+G4zbPhfUcQtuBjoX6QxKS qH92z7/TmJmEZGHGU5Yt8OSoXKiVZBmtwt5zWmjfUwy5HReiCtsrtQfoXAWv/b6lx9Ia PI+z+oJoZypRuCKQrK+cNV7z8mYMBtjDfNpQPqxWnAnzFqtvh0yFCTWxVwUne2lVGfPM 9rQ7ByYllyisgH1fQgX24j+mLdOWpMtrUDmDluHvdVXnb9pvY7qRa7CnBS0AssF6W5wc YvGR+XCcZDAFP2wYYSG/AK6fF9CfYTnxv6VbLNC0i/9EiM3Q+NLn7i2M+qJPocSSshVm /L0Q==
X-Gm-Message-State: AOAM533X/kE8DPndvawYiVop9gGAw7BtEcEsLJGFt2tn6PIw2FUx1W1g +LUkDw78gvmyA8EMrgkMOsC1L1lXHyN6NDnmM8E=
X-Google-Smtp-Source: ABdhPJyN+8vZRJcm/FY6d9Bu3eSwtQNY20d4+NJHsoPDmLcRngMNXje3JISYgVTl+iRJZzhS58xJEUJ21gugBfT6FAE=
X-Received: by 2002:a05:6402:50d1:b0:42b:c3e:d71e with SMTP id h17-20020a05640250d100b0042b0c3ed71emr151759edb.144.1654092920701; Wed, 01 Jun 2022 07:15:20 -0700 (PDT)
MIME-Version: 1.0
References: <20210506235220.437A7F40791@rfc-editor.org> <21654B6B-65E0-4772-8B6D-149FC2CB5021@tzi.org>
In-Reply-To: <21654B6B-65E0-4772-8B6D-149FC2CB5021@tzi.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 01 Jun 2022 10:15:08 -0400
Message-ID: <CALaySJL6ikPk4gY5itMQcE4+ePseHxbx4iUx1XYNWbQGmu-TvA@mail.gmail.com>
To: Francesca Palombini <francesca.palombini@ericsson.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Carsten Bormann <cabo@tzi.org>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, Laurence Lundblade <lgl@island-resort.com>, cbor@ietf.org, Christian Amsüss <christian@amsuess.com>, christoph.vigano@uni-bremen.de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Xvsp8TsFSPv3HNGPFFoxMC2V3iE>
Subject: Re: [Cbor] [Technical Errata Reported] RFC8610 (6575)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.34
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: Wed, 01 Jun 2022 14:15:26 -0000
Francesca, will you please close this report as "held for document update", as suggested below? Thanks, Barry On Fri, May 7, 2021 at 9:28 AM Carsten Bormann <cabo@tzi.org> wrote: > > Well, representation types for tags are explained in 3.6, so 2.2.3 should have a forward reference to 3.6 instead of trying to restate 3.6 (which it only manages by half). > (Note that the text doesn’t say what #6.24 without parentheses means — the ABNF suggests that the number after the dot should be ai not argument. > In hindsight, maybe using a different character than “.” for tag/argument would have been more suggestive.) > > I’d say, this is "hold for document update” so we get a chance to cover the corner case, but it is worth saying now that 3.6 is the detailed description of the exception for #6.nn(tt). > > Grüße, Carsten > > > > On 7. May 2021, at 01:52, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > > > 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/eid6575 > > > > -------------------------------------- > > Type: Technical > > Reported by: Laurence Lundblade <lgl@island-resort.com> > > > > Section: 2.2.3 > > > > Original Text > > ------------- > > Where a major type of 6 (Tag) is used, the type > > of the tagged item can be specified by appending it in parentheses. > > > > Corrected Text > > -------------- > > Where a major type of 6 (Tag) is used, the type of the tagged item can be specified by appending it in parentheses. Additionally, > > for major type 6 the value of the argument, not the additional info is what follows the dot. > > > > Notes > > ----- > > The text at the top of page 50 is correct. The examples in 2.2.3 are also correct. > > > > 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 > > _______________________________________________ > CBOR mailing list > CBOR@ietf.org > https://www.ietf.org/mailman/listinfo/cbor
- [Cbor] [Technical Errata Reported] RFC8610 (6575) RFC Errata System
- Re: [Cbor] [Technical Errata Reported] RFC8610 (6… Barry Leiba