Re: [Cbor] [COSE] CBOR magic number, file format and tags Fri, 22 January 2021 02:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D0EC93A104B for <>; Thu, 21 Jan 2021 18:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.985
X-Spam-Status: No, score=-0.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uOhetK5Xd48i for <>; Thu, 21 Jan 2021 18:37:37 -0800 (PST)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B973E3A1044 for <>; Thu, 21 Jan 2021 18:37:37 -0800 (PST)
Received: from ([]) by with ESMTP id 2kYUloL1F92Bp2mKOl5YWf; Fri, 22 Jan 2021 02:37:36 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20180828_2048; t=1611283056; bh=11rOCr30YvwlJSzQ6FhMSPiiny+Qh4Mw6NTYmpToK64=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=qnhimPsb8K/pOOdXxUFXrrExXfAm3NC6QJF0iC+l59lZP5Wb2FIBwewvlB4aui2mL DqljetEMw9Z2V+JAfRCsbAcHiSxS7eg1XpK5T+lDbXo6wys89B2qN2Qusk4w02qujl 5zUTgBZ+oBRjQQpRAWbuzYPOpgbYBrHMgIsTcsG36TTPKjFXMKBy6LM7FJ8w8OAKRw GfM2pTIqzlvM7WX4QADrlDLOiZeYk4aV019qSR7jySdiZtrHayxwRG2tPehy/+5wfo cxRBHjLFgiLjfn10Syeq0p8B7ojoTNIsflVIZ8/u4ryHbm7+5ouTuh94k3qzE6GZhI YDnyj4DdGUGMg==
Received: from ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by with ESMTPA id 2mKJlgaLVo85j2mKMlxLSn; Fri, 22 Jan 2021 02:37:36 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id 10M2bTdP002626; Thu, 21 Jan 2021 21:37:30 -0500
Received: (from worley@localhost) by (8.14.7/8.14.7/Submit) id 10M2bTc4002623; Thu, 21 Jan 2021 21:37:29 -0500
X-Authentication-Warning: worley set sender to using -f
To: Michael Richardson <>
In-Reply-To: <4521.1611231879@localhost> (
Date: Thu, 21 Jan 2021 21:37:29 -0500
Message-ID: <>
Archived-At: <>
Subject: Re: [Cbor] [COSE] CBOR magic number, file format and tags
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 22 Jan 2021 02:37:40 -0000

Michael Richardson <> 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

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?  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.