From nobody Wed May 31 10:00:51 2023
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 3013DC151700
 for <cbor@ietfa.amsl.com>; Wed, 31 May 2023 10:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham 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 avTIbkur6Rcn for <cbor@ietfa.amsl.com>;
 Wed, 31 May 2023 10:00:47 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de
 [IPv6:2001:638:708:32::21])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 8EBB5C1516E3
 for <cbor@ietf.org>; Wed, 31 May 2023 10:00:46 -0700 (PDT)
Received: from [192.168.217.124] (p548dc0f6.dip0.t-ipconnect.de
 [84.141.192.246])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QWbB408YSzDCbn;
 Wed, 31 May 2023 19:00:43 +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: <CAAse2dEFB_FVP6_KkNANSYPW+yX4-M9pN3YkUq5=FTgLZnyWGw@mail.gmail.com>
Date: Wed, 31 May 2023 19:00:43 +0200
Cc: cbor@ietf.org, Wolf McNally <wolf@wolfmcnally.com>,
 Shannon.Appelcline@gmail.com
X-Mao-Original-Outgoing-Id: 707245243.527227-e736b882dde3489db4377434ab0511c4
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFD1AFCB-45F7-4893-B4B8-F2F093FEE6E5@tzi.org>
References: <CAAse2dEFB_FVP6_KkNANSYPW+yX4-M9pN3YkUq5=FTgLZnyWGw@mail.gmail.com>
To: Christopher Allen <ChristopherA@lifewithalacrity.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/mrTvYsEm0mnSyBALVG6kSKFi0wU>
Subject: Re: [Cbor] Updated Drafts for dCBOR I-D and Gordian Envelope
 Structured Data Format I-D & IANA Tag Registration
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
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, 31 May 2023 17:00:51 -0000

On 2023-05-08, at 19:40, Christopher Allen =
<ChristopherA@lifewithalacrity.com> wrote:
>=20
> Gordian Envelope Internet-Drafts, which have been recently submitted =
to the Internet Engineering Task Force (IETF).

I did a quick skim after today=E2=80=99s meeting.

First a few comprehension questions:

(1) Why do things that already identify themselves as Gordian Elements =
(tag 201 to 206) need to be tagged again with 200?  Is there any =
function of this I=E2=80=99m missing?

(2) What is 221? 224?

(3) I don=E2=80=99t understand the way =E2=80=9Cknown values=E2=80=9D =
(Section 6) mix with the things they are predicates over.

Editorial comments:

(a) Some forward slashes probably want to be backslashes.
(You don=E2=80=99t need backslashes inside hex values in CBOR diagnostic =
notation.)
Did you check those examples?

(b) I don=E2=80=99t know that you need =E2=80=9CCBOR hex=E2=80=9D for =
all the examples, but if you do, can I recommend "CBOR pretty=E2=80=9D =
format?  (Generate with diag2pretty.rb, which is part of the cbor-diag =
gem.)

Technical comments:

(4) I don=E2=80=99t find the crypto agility that was promised.
You probably want to use algorithm identifiers from the COSE algorithms =
registry (RFC 9053).

Gr=C3=BC=C3=9Fe, Carsten

