IETF Logo Mail Archive

Re: [jose] [Anima] do we need +jose?

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 11 May 2023 12:40 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70838C17B35B; Thu, 11 May 2023 05:40:58 -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 ZDOceSolnb6O; Thu, 11 May 2023 05:40:54 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A65F9C151B2E; Thu, 11 May 2023 05:40:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 76C553898C; Thu, 11 May 2023 08:59:35 -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 eLZ1-2PL8Ia5; Thu, 11 May 2023 08:59:34 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B34FD3898B; Thu, 11 May 2023 08:59:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1683809974; bh=YbHoklbQ6O0v4myknkzoABVMNw6EFufYe6TIAGR1CBU=; h=From:To:Subject:In-Reply-To:References:Date:From; b=Y8tlydCefiJ2uoOCrYwzdO+82dLwmF6+knJGGuwVddoatj5iB2cdxW2HeGgBK191/ sxOp0hCZ9MaKrMC9n7vqZvlxuSRDjLDk47m/mUJ3S6e8oMUFN3ajBX/Tf2AeQS2YZX zjHmUY3IJbUCm+kIKh9xBP1bmqTuzNRIGOHeYD8PzR6xaWDEw+cigHstTO52xy8PmW 2OK5imzBiX2KYul5yDZxY/gtciLhk5T3E6pkOwbqYTjVz9oAoFhn+Pa4AhOudHbHW/ cOT6hnuRMG2G4d8KwMFx/I+KE6QffewnspbqdEnAdJKuXKKlZbClZkHywnp1eJ2RNQ 2CV/Z/aodfiuw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9AF2E17A; Thu, 11 May 2023 08:40:44 -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>, "jose@ietf.org" <jose@ietf.org>
In-Reply-To: <DU0P190MB197848EED33915762E134418FD749@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
References: <16284.1680886223@localhost> <E5148BFA-C50F-4EE1-B7ED-1D8A9EA15C43@intel.com> <DS7PR21MB3406D6E2E9315926EE7E80028E969@DS7PR21MB3406.namprd21.prod.outlook.com> <32345.1680916659@localhost> <BY5PR01MB59558857C66E30DCADEDE64AA39E9@BY5PR01MB5955.prod.exchangelabs.com> <16283.1682887399@localhost> <14942.1683658240@localhost> <DU0P190MB19787C6FA946DB90D96B3BE9FD779@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <DU0P190MB197848EED33915762E134418FD749@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: Thu, 11 May 2023 08:40:44 -0400
Message-ID: <14397.1683808844@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/aZMcyNeZPqAK8KlGhIsV3pbuIW8>
Subject: Re: [jose] [Anima] do we need +jose?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2023 12:40:58 -0000

Esko Dijk <esko.dijk@iotconsultancy.nl> wrote:
    > It could also be named +josejson or +jose-json then ? Not as nice as
    > +jws but at least more relatable to the original media type name.

It seems like less of a good idea, but I'm not opposed to it.

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

v2.23.0 | Report a Bug | By Email