Re: [Cbor] AD review of draft-ietf-cbor-file-magic-10
Carsten Bormann <cabo@tzi.org> Sun, 03 April 2022 20:01 UTC
Return-Path: <cabo@tzi.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 104893A1D3E; Sun, 3 Apr 2022 13:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 Rd-x7LIRIBDi; Sun, 3 Apr 2022 13:01:46 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC50A3A10B4; Sun, 3 Apr 2022 13:01:43 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KWlD34Q9tzDCc2; Sun, 3 Apr 2022 22:01:39 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17787.1649014907@localhost>
Date: Sun, 03 Apr 2022 22:01:39 +0200
Cc: Francesca Palombini <francesca.palombini@ericsson.com>, "draft-ietf-cbor-file-magic@ietf.org" <draft-ietf-cbor-file-magic@ietf.org>, "cbor@ietf.org" <cbor@ietf.org>
X-Mao-Original-Outgoing-Id: 670708899.1289181-e11ae0ffa5ab737036a691b09106d324
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE1E42F7-3669-4547-B4BF-57AB738A5ABE@tzi.org>
References: <HE1PR07MB4217656476550D97A1ACEA6A98E09@HE1PR07MB4217.eurprd07.prod.outlook.com> <47C46EEB-3736-403A-AA39-6989A3BD755A@tzi.org> <17787.1649014907@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/XlVZJfPYwQ00BPvymXG8JqwtYjo>
Subject: Re: [Cbor] AD review of draft-ietf-cbor-file-magic-10
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, 03 Apr 2022 20:02:03 -0000
On 2022-04-03, at 21:41, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > > Carsten Bormann <cabo@tzi.org> wrote: >> I have created a pull request with changes for the items that I think we could resolve: >> https://github.com/cbor-wg/cbor-magic-number/pull/20 >> A few responses below, with a few questions embedded. >> I haven’t done 14 to 19 yet. > > I perhaps finished all the points on top of Carsten's branch. Thank you! I see two comments from Francesca we haven’t replied to and two more we haven’t addressed yet: > 16. ----- > > Section 5.1 and 5.2 > > […] > > Additional comment: I think it is better to described the Data Item as "byte string" as for the current registration, rather than update to "tagged byte string" - that is not a CBOR Data Item per se. Well, 55800 and 55801 are meant to have a tagged byte string as their content: The tag is the 32-bit tag that actually defines the format. So it’s 55800(1330664270(h'424F52’)) (diagnostic notation in Appendix B) or #6.55801(#6.1668546992('BOR’)) (Appendix C.1, this time in CDDL form). > > 17. ----- > > […] > > Also it is a bit confusing to use "NNNNNNNN" and not just "N" (as I read it as a decimal, and 8xN doesn't really give me any more information about the number). I think NNNNNNNN is a reasonable representation of a larger number, but I’m also not opposed to changing this to N (twice). Also, we might want to work a bit on: > 18. ----- > > Appendix A > > FP: I have some vague memory of this being discussed during interims - so please remind me if I have forgotten, but why is this an appendix rather than in the document itself? We might provide a little more text about moving this into an appendix. > 19. ----- > > Appendix C > > FP: I think a bit more text around the motivation and need for such a tag would be useful. Yes, that also could use a bit more work. Despite 18 and 19 not yet being addressed, I would prefer to submit a -11 with what we have now so people actually review that and not -10. Grüße, Carsten
- [Cbor] AD review of draft-ietf-cbor-file-magic-10 Francesca Palombini
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Michael Richardson
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Carsten Bormann
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Michael Richardson
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Carsten Bormann
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Michael Richardson
- Re: [Cbor] AD review of draft-ietf-cbor-file-magi… Francesca Palombini