Re: [Cbor] [COSE] CBOR magic number, file format and tags

Michael Richardson <mcr@sandelman.ca> Fri, 22 January 2021 16:17 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 02C6D3A12B9; Fri, 22 Jan 2021 08:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 co-iPpqQx6Wq; Fri, 22 Jan 2021 08:17:03 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DA4F3A12B7; Fri, 22 Jan 2021 08:17:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 9D98638A05; Fri, 22 Jan 2021 11:19:07 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HbIQLgdRjpz1; Fri, 22 Jan 2021 11:19:07 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 358C538A01; Fri, 22 Jan 2021 11:19:07 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 72758136; Fri, 22 Jan 2021 11:17:00 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: worley@ariadne.com
cc: cbor@ietf.org, doug@ewellic.org, cose@ietf.org
In-Reply-To: <87lfcld7di.fsf@hobgoblin.ariadne.com>
References: <87lfcld7di.fsf@hobgoblin.ariadne.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23722.1611332220.1@localhost>
Date: Fri, 22 Jan 2021 11:17:00 -0500
Message-ID: <23723.1611332220@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/FtHUxeF074S1toccMhWkGRkW1cE>
Subject: Re: [Cbor] [COSE] CBOR magic number, file format and tags
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: Fri, 22 Jan 2021 16:17:08 -0000

Dale R. Worley <worley@ariadne.com> wrote:
    > Michael Richardson <mcr+ietf@sandelman.ca> writes:
    >> That tells us that it might be CBOR.
    >>
    >> It does not distinguish a CBOR encoded certificate from a CBOR encoded
    >> RFC8366 artifact, for instance.

    > Uh, yes?  They're both CBOR, right?  It's still the magic number for
    > CBOR.

    > Do you mean to say, you want a place in CBOR to place a magic number
    > that describes the particular kind of CBOR structure this is?

Yes.

    > If so,
    > you should make that clear right at the start of the I-D.  Indeed, in
    > the Abstract, though it needs other work, too.  Checking again, it
    > looks like you don't really lay that out until section 6, whereas I
    > only read it through section 5.  My mistake, but lots of other people
    > will make it as well.

Better wording suggestions welcome.