Re: [media-types] [Anima] registration for +cose

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 02 May 2023 17:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7DCC151B38; Tue, 2 May 2023 10:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 pysMVxS8-fOi; Tue, 2 May 2023 10:33:31 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70ABAC14CF1C; Tue, 2 May 2023 10:33:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3C08F3898E; Tue, 2 May 2023 13:51:40 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1zbm5q6TcALT; Tue, 2 May 2023 13:51:38 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 18ACE3898D; Tue, 2 May 2023 13:51:38 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1683049898; bh=mR+DOfypSEVBJ/0HnQBI7vkxktFvXu5daGV7S6ToVR8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=qfrC99GKeN+mNQqg26aKFaosSgEoCGwxhyh+/0jswSvpKk2Ox4QVht9C0Y0i52bY2 xnCVUnKebe43PKc2BGezTOT0ak5YzTYxkNXK4p0/v5POUzJAJicdizXxEQTO0P/Tjo i/JEGCnVscCP5Zoc7eVdDdFt/P+nVxKjuJqKXEUfGoD3/hezkIFtP31Keh+KJjrcpv tiUr94MGncczML2MU4BrmtbxYGUKD/WNrOcI/bHrX4RElljX31BOxmZaY/a46/mutA 4PkXFeH5i9Inl2YuL4N3YgiownhURw7qzAiGLiZLMd55e9QLpjJoT9RfGFuvegRPIv BDwWO/W1fAN7Q==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A42AD6D; Tue, 2 May 2023 13:33:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>, "media-types@ietf.org" <media-types@ietf.org>, "anima@ietf.org" <anima@ietf.org>, "cose@ietf.org" <cose@ietf.org>
In-Reply-To: <DU0P190MB1978A0678A74F68B6F9DC38BFD629@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
References: <15505.1680886012@localhost> <DU0P190MB1978A0678A74F68B6F9DC38BFD629@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 02 May 2023 13:33:20 -0400
Message-ID: <22557.1683048800@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/aoat1ILh0oqhNjWRka0HoijwxjQ>
Subject: Re: [media-types] [Anima] registration for +cose
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 May 2023 17:33:36 -0000

Esko Dijk <esko.dijk@iotconsultancy.nl> wrote:
    > 1. Given the existing names of registrations in the Structured Syntax
    > Suffixes registry, the following name would be more appropriate
    > perhaps:

    >     Name: CBOR Object Signing and Encryption (COSE)

    > 2. While STD96 as reference is probably correct, it would be useful to
    > add the latest COSE RFC (9052) as well. This is also more in line with
    > the other registrations that list RFC numbers. And RFCs are better
    > known than STDs. Or maybe this was already intended.

getting used to using STD numbers is kinda important.
The point of STD numbers is that they are an indirection.
would this link be better: https://www.rfc-editor.org/info/std96

    > 3. The security considerations should point to a section of RFC 9052
    > (Section 12), also like other registrations do.

I thought it did :-)

    > 4. Encoding considerations should mention COSE - current text looks
    > like it could be a copy/paste bug:

    >     Encoding considerations: COSE is always encoded as CBOR, which is
    > binary

Yes, that's better.

as per RFC6838:

Name: application/cose
+suffix: +cose
References: https://www.rfc-editor.org/info/std96 (RFC9052)
Encoding considerations: COSE is always encoded as CBOR, which is binary
Interoperability considerations: None
Fragment identifier considerations: N/A
Security considerations: as per RFC9052, section 12
Contact: IETF COSE WG
Author/Change controller: IESG

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide