Re: [Anima] [media-types] do we need +jose?
Orie Steele <orie@transmute.industries> Thu, 11 May 2023 12:08 UTC
Return-Path: <orie@transmute.industries>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE570C152573 for <anima@ietfa.amsl.com>; Thu, 11 May 2023 05:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=transmute.industries
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 M5evo5_jL0zb for <anima@ietfa.amsl.com>; Thu, 11 May 2023 05:07:58 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 ietfa.amsl.com (Postfix) with ESMTPS id C4131C152565 for <anima@ietf.org>; Thu, 11 May 2023 05:07:58 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-956ff2399c9so1633769566b.3 for <anima@ietf.org>; Thu, 11 May 2023 05:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1683806877; x=1686398877; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZkA6FTkEL1hp0JFDH5fSPABj5ZoDvVKK9FLDab5tLr8=; b=lXHv6tiPncbRMznbIUrGFrWAkwt+fLXZI6Z6ljW5GykADlWxP+WSQQFNrznrQbLr0X pll++4mYO6pa0ZMQlmSvQhiztoS0BYi6d3jpS0UOfW1WXCxoyODCdVIMROl79AiBQqFK /f/sSsOJSxea+CuBJXAc6wsVJprDVEVp8Z+SHdEQWrnZKxy6ABhFa2bKUF7Avnn+qiSg 509dPuQeV3KGkv4OW+ai/C0VppD9789fbP65S9y55YDh6vgbwhwfL4VWx7v2BnxUhINZ xb78WzGg9ox06Z81tMbqe+el0DFiKQ1QZOEuSKx65Zwt019kYp6y+muI5CTytr561qfw I4JA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683806877; x=1686398877; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZkA6FTkEL1hp0JFDH5fSPABj5ZoDvVKK9FLDab5tLr8=; b=VMQVA8tqJ0sMJuTO2cpBatQZCU9raFq0Mg+mwlTnPYvLceZrCDYi+tcesOXC5w8bHe NmFIaJ9BChc5ITQg5pEhGKEjUDmt+zClTuT4DOKof3dFxGUhEDc60Z1I61O6TF7egdKz VZRFlYU4EbOOoBS/fwBYVv9sIOYUtAmc1AIEW9wapDRnUM+PW9yZI8ZeYuDXb8y7+Dfk 10PI5QBAR9QSUT+Ij/ZEzJGqLel8oCkQXu7WsQkEyYaQrrnI7jSEtaOPJ/BImmH7wRLJ UVTPfo3fXFZj8BNhKcAXAFa3DO+NaXQqkCTlXCTGIfllcDYNhqCXoPAiwksgiVhXjBPj dFWA==
X-Gm-Message-State: AC+VfDyEyEiXsKF2lqnwgGvQteK7nRBm9yAvb0PHyw586+FtvD7wMw0D qeGEdWPtqvh/G4/k8QmG9SdEChBoC+RyqCihH9OLog==
X-Google-Smtp-Source: ACHHUZ5TxUQGeC9oU/1wTNswqYzQUv78793P40wvZG+fAn0WjEcpnyLLrOSqLlTnMEqAejTmzBbX8LjrxiWWFCq+YlQ=
X-Received: by 2002:a17:906:5d08:b0:965:9d20:a41b with SMTP id g8-20020a1709065d0800b009659d20a41bmr19216295ejt.16.1683806876735; Thu, 11 May 2023 05:07:56 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <DU0P190MB197848EED33915762E134418FD749@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
From: Orie Steele <orie@transmute.industries>
Date: Thu, 11 May 2023 07:07:44 -0500
Message-ID: <CAN8C-_K5wNO_z+x=uMDAnGKhpG4+2F=h+RBuNfwZav_GL0iwLQ@mail.gmail.com>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, media-types@ietf.org, anima@ietf.org, JOSE WG <jose@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c22f8b05fb69d6f1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IkiJ5xgi7_VCAfcF9lbaoqa6-hc>
Subject: Re: [Anima] [media-types] do we need +jose?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2023 12:08:03 -0000
This draft might change those requirements, it could use more reviews: https://datatracker.ietf.org/doc/draft-ietf-mediaman-suffixes/ I personally think we should not assume every structured suffix will also be a registered sub type. I think we should: 1. Move the normative statements to a document and out of the registry. 2. Update the registry policy to have specification required. 3. Detail the processing guidelines from right to left, in a way that does not create exceptions. 4. If 4 is impossible, document the exception and take steps to avoid them in the future. On Thu, May 11, 2023, 5:07 AM Esko Dijk <esko.dijk@iotconsultancy.nl> wrote: > Update to my previous email: as I learnt now the registration of a +suffix > in the SSS registry doesn't require that the registered name is an existing > media type name. (Example: +der) > So +jws could be registered with the registration fields pointing to RFC > 7515 "application/jose+json" as the reference. > > 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. > > Esko > > -----Original Message----- > From: Esko Dijk > Sent: Wednesday, May 10, 2023 16:38 > To: Michael Richardson <mcr+ietf@sandelman.ca>; media-types@ietf.org; > anima@ietf.org; jose@ietf.org > Subject: RE: [Anima] do we need +jose? > > > should really be doing: > > application/voucher+jws > > Because "application/jws" does not seem to be an existing media type, it > would be strange to use "+jws". > Looking at draft-ietf-anima-jws-voucher-06: what it really uses is the > "JWS JSON Serialization" which has the "application/jose+json" media type. > This is not the "application/jose" type, so it would be strange to use > "+jose" as your subject suggests. > Now given that we shouldn't use multiple structured syntax suffixes in > concatenation at this moment, the only option for the suffix media type at > this moment looks to be "+json". > > (Or alternatively we would need a new spec that defines the > "application/jws" media type - not advisable it seems, adds to confusion.) > > So we can have names like e.g.: > > application/voucher-jose+json > application/voucher-jws+json > > In the cases above the "+json" at the end isn't wrong, because it actually > is JSON. (For the earlier case of "application/voucher-cms+json" it was > wrong as you say, because the CMS envelope isn't actually JSON.) > > Esko > > > IoTconsultancy.nl | Email/Teams: esko.dijk@iotconsultancy.nl > > > -----Original Message----- > From: Anima <anima-bounces@ietf.org> On Behalf Of Michael Richardson > Sent: Tuesday, May 9, 2023 20:51 > To: media-types@ietf.org; anima@ietf.org; jose@ietf.org > Subject: [Anima] do we need +jose? > > > Hi, https://datatracker.ietf.org/doc/draft-ietf-anima-jws-voucher/ > is in WGLC, and > https://datatracker.ietf.org/doc/draft-ietf-anima-brski-prm/ depends upon > it. > > In anima-jws-voucher, we defined: > > https://www.ietf.org/archive/id/draft-ietf-anima-jws-voucher-06.html#name-application-voucher-jwsjson > > Type name: application > Subtype name: voucher-jws+json > > which is in alignment with > https://www.rfc-editor.org/rfc/rfc8366.html#section-8.3 > where we defined: > Type name: application > Subtype name: voucher-cms+json > > probably this was a mistake! (JSON in a CMS envelope) > > I think, based upon discussion about +cose and our other documents, that we > should really be doing: > application/voucher+jws > > While jwt is given as a structured suffix in the IANA registry, jws is not. > I'm not entirely sure if this matters... we are dealing with JWS, not > tokens... > > Please advise. While we have lots of running code (since 2018) for > voucher-jws, it's a > change we could probably make via Postel Principal. > > -- > Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types >
- [Anima] do we need +jose? Michael Richardson
- Re: [Anima] do we need +jose? Esko Dijk
- Re: [Anima] do we need +jose? Esko Dijk
- Re: [Anima] [media-types] do we need +jose? Orie Steele
- Re: [Anima] do we need +jose? Michael Richardson
- Re: [Anima] do we need +jose? Kovatsch, Matthias