IETF Logo Mail Archive

Re: [Cbor] Roman Danyliw's Discuss on draft-ietf-cbor-file-magic-11: (with DISCUSS and COMMENT)

Carsten Bormann <cabo@tzi.org> Wed, 20 April 2022 20:46 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 53A823A10F3; Wed, 20 Apr 2022 13:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 Ru60untvX-rV; Wed, 20 Apr 2022 13:46:34 -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 9F58D3A0896; Wed, 20 Apr 2022 13:46:33 -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 4KkCPx5c0kzDCcC; Wed, 20 Apr 2022 22:46:29 +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: <CALaySJL90x-_w=YOZ8VS8Df=g138vWAhX80nqsG=hpyiH=+Z-Q@mail.gmail.com>
Date: Wed, 20 Apr 2022 22:46:29 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Roman Danyliw <rdd@cert.org>, draft-ietf-cbor-file-magic@ietf.org, cbor@ietf.org, The IESG <iesg@ietf.org>, Christian Amsüss <christian@amsuess.com>, CBOR Working Group <cbor-chairs@ietf.org>
X-Mao-Original-Outgoing-Id: 672180389.4683681-1b51bc628c44a15ecef5bce5f4be8a9d
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C8BF4AB-9B53-490F-83EF-F0AB1928C6CF@tzi.org>
References: <165042018713.9385.10789424906577326164@ietfa.amsl.com> <791842.1650458923@dooku> <CALaySJL90x-_w=YOZ8VS8Df=g138vWAhX80nqsG=hpyiH=+Z-Q@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/nEuBS4-IQYFgWN8xTetHyQW1c-Q>
Subject: Re: [Cbor] Roman Danyliw's Discuss on draft-ietf-cbor-file-magic-11: (with DISCUSS and COMMENT)
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: Wed, 20 Apr 2022 20:46:39 -0000


> On 2022-04-20, at 20:49, Barry Leiba <barryleiba@computer.org> wrote:
> 
> I think we should consistently use "designer of [the / a] CBOR Protocol".

Yes.

https://github.com/cbor-wg/cbor-magic-number/pull/21/commits/e4ccccd

Grüße, Carsten


> 
> Barry
> 
> On Wed, Apr 20, 2022 at 2:14 PM Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
>> 
>> 
>> Roman Danyliw via Datatracker <noreply@ietf.org> wrote:
>>> (a) "In both enveloping methods, CBOR Protocol designers need to obtain
>>> a CBOR tag for each kind of object that they might store on disk.
>>> ... The IANA policy for 4-byte CBOR Tags is First Come First Served,
>>> ..."
>> 
>>> (b) "This tag needs to be allocated by the author of the CBOR
>>> Protocol."
>> 
>>> Both of these statements are made in this section and they appear to
>>> conflict.  (a) appears to be saying that CBOR tags will be allocated
>> 
>> I guess it's unclear that "author of the CBOR protocol" is the same as the
>> "protocol designer".   Which term would you prefer we used?
>> 
>> I guess we could write, "designer of the CBOR protocol"?
>> if draft-ietf-cose-cbor-encoded-cert-03, wanted a tag, then that would be
>> John, Goran, S.Raza,... or more collectively, the COSE WG.
>> 
>>> Thank to Chris Wood for the SECDIR review.  Please review the editorial
>>> suggestions posed there.
>> 
>> Roger, wilco.
>> 
>> 
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>> -= IPv6 IoT consulting =-
>> 
>> 
>> 
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.23.0 | Report a Bug | By Email