Re: [Rats] [Cbor] I-D: draft-rundgren-cote-00

Anders Rundgren <> Thu, 21 July 2022 05:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B4CF4C15949B; Wed, 20 Jul 2022 22:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id k5oupq_pIBER; Wed, 20 Jul 2022 22:09:33 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 05D6AC157B3A; Wed, 20 Jul 2022 22:09:32 -0700 (PDT)
Received: by with SMTP id w8-20020a05600c014800b003a32e89bc4eso188595wmm.5; Wed, 20 Jul 2022 22:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=7TV4ozDkdPExWPD94swIUbrSV0B16omxllh5pwtq25I=; b=oyrvy5C5cvn4k5jMArKq6nNSLPpcKnVkD0MGYBGWMasGVjcYyEfZjoJr9vjvL8cN/Y s6LwO2pQnayNrW5DTjONc2SXIZdcw9AT4f8hmO1s5lXhHPnak6J4ToNoXnezumoxPBLU YZaHHi6rVVuTkPK/098v4yBjSCOhkIn/QNUF+hp7R+hnHiCJ3K6zv96yYyyFPiBHBEsL oXjBvF4PluqM7ZXEQJ7EE82rSlYu6FkzCI6KUAuhwFgAwwiJ2yYYFWHT6+4yPOj4sNTA IC8OJ5o4adDfJy++Kj9YBMpiUdqmrJ0A+Owa1szSIQK5vVEAoBFlRIOywyk6zmCCDYYT vp3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=7TV4ozDkdPExWPD94swIUbrSV0B16omxllh5pwtq25I=; b=1Ek5MAt76rtUYtIHTgVmssSfnN6dDCY3mcOu0FKVIlkSrLruPER09PWA5Ql59nvp66 yPYFnbXrVUmjDMgkydkW4zx1UYsw9QkMMV0VdgbOx5UVUmQhw9KA800bH5MUOU4vKnpZ mOevNY4EMrJjzkVZ2KosS/2hYWKj8HYY/BQQkmo2EdjzEvIpkZqa48sMBYU6rrb4j0Mv dJazn5pjIOw/9/ZSdECskpwQoZRQiABvsUfbRgI1IWQOJuXXl7wVeoGcY1dFTewv8Lra 4lfF6kqk1VigdyIs6VOkRUgfLAqTHFSGZIRubu6Tb9X1mpJGCyQ7VKvI3XDcQcvuVH98 kOOQ==
X-Gm-Message-State: AJIora8aLU79IdNitzyzzrqwPXZDxKb3D+fFa2yucDv8tLgNw0HRBPyf PpSL2nMEJuLR9e4/w0sm2oFg/Li4AXw=
X-Google-Smtp-Source: AGRyM1vgHOpmm8/r5/2IbUj5rWd3OCqCyX0/BBlN9aBBAFBG7/7Kh8uWOuu2GedliIa32wI0GoCRdg==
X-Received: by 2002:a1c:ed0e:0:b0:3a2:d7d0:c607 with SMTP id l14-20020a1ced0e000000b003a2d7d0c607mr6285208wmh.147.1658380170863; Wed, 20 Jul 2022 22:09:30 -0700 (PDT)
Received: from ?IPV6:2a01:e34:ec4e:5670:5cd3:7291:3d36:5830? ([2a01:e34:ec4e:5670:5cd3:7291:3d36:5830]) by with ESMTPSA id k6-20020a5d5186000000b0021e571a99d5sm186160wrv.17.2022. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jul 2022 22:09:30 -0700 (PDT)
Message-ID: <>
Date: Thu, 21 Jul 2022 07:09:28 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Michael Richardson <>, "" <>,
References: <> <> <> <> <> <> <1663483.1658345550@dooku>
From: Anders Rundgren <>
In-Reply-To: <1663483.1658345550@dooku>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Rats] [Cbor] I-D: draft-rundgren-cote-00
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Remote ATtestation procedureS <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jul 2022 05:09:34 -0000

On 2022-07-20 21:32, Michael Richardson wrote:
>> The primary purpose is to enable developers defining community- or
>> application-specific type identifiers without having to go through an IANA
>> registration process. Although the scheme imposes no restrictions on type
>> identifiers (beyond being valid CBOR data items), using URLs should due to
>> their ubiquity be a candidate for CBOR based standards.
> I'm not sure I understand why RATS is on the CC.

Well, the RATS WG is just about to adopt an entirely different CBOR object typing scheme :)

> A URL is rather bulky for some uses, but if the CBOR is encoding thousands of
> items in a compact form, then the amortization of the tag makes sense.

COTE represents an alternative, not a "competitor".  For the type of work I do with CBOR (taking it to the financial industry), the overhead is insignificant compared to the associated payloads.  That the predecessors that mostly are based on XML come with URL- or URI-based identifiers is another motive.

The core idea behind URL-based identifiers is making identifiers point to their actual definition.  Some recent standards like even require URL-based payment method identifiers to be pointing to machine-readable data which is used by browsers for invoking associated (but locally installed) applications!

COTE outlaws such uses but supports "browsable" identifiers.

> draft-ietf-cbor-file-magic provides a similiar mechanism with the
> recommendation that one go for a 4-byte tag from the FCFS space.
> yes, that involves a trip through IANA... an email and a delay of perhaps a
> week.

> I agree with Carsten that the document is a bit underspecified.

You are welcome with additional input.  I hope to do a real 00-submission next week that will include an appendix dealing with "URL Identifier Management".

As Carsten also pointed out, the CBOR WG has a bit of homework to do in order to create a robust repository of tags and associated (URL-based) definitions.