IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 20 April 2022 18:14 UTC

Return-Path: <mcr@sandelman.ca>
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 BBDF33A094F; Wed, 20 Apr 2022 11:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.316
X-Spam-Level:
X-Spam-Status: No, score=-0.316 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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=no 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 aHdcmjND7_Hg; Wed, 20 Apr 2022 11:14:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD993A0937; Wed, 20 Apr 2022 11:14:19 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [142.169.78.146]) by relay.sandelman.ca (Postfix) with ESMTPS id 33B2D1F4A4; Wed, 20 Apr 2022 18:14:17 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 282BB1A03B8; Wed, 20 Apr 2022 08:48:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Roman Danyliw <rdd@cert.org>
cc: The IESG <iesg@ietf.org>, christian@amsuess.com, cbor@ietf.org, cbor-chairs@ietf.org, draft-ietf-cbor-file-magic@ietf.org
In-reply-to: <165042018713.9385.10789424906577326164@ietfa.amsl.com>
References: <165042018713.9385.10789424906577326164@ietfa.amsl.com>
Comments: In-reply-to Roman Danyliw via Datatracker <noreply@ietf.org> message dated "Tue, 19 Apr 2022 19:03:07 -0700."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 20 Apr 2022 08:48:43 -0400
Message-ID: <791842.1650458923@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/sl_JIYZGJzd31qrrkKLcVKAg-58>
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 18:14:27 -0000

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 =-

v2.23.0 | Report a Bug | By Email