[jose] Re: Do you need the JWP JSON Serialization?
Brian Campbell <bcampbell@pingidentity.com> Wed, 07 August 2024 17:46 UTC
Return-Path: <bcampbell@pingidentity.com>
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 D9510C14F695 for <jose@ietfa.amsl.com>; Wed, 7 Aug 2024 10:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=pingidentity.com
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 Y2i6TpL9IHsQ for <jose@ietfa.amsl.com>; Wed, 7 Aug 2024 10:46:49 -0700 (PDT)
Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24834C14F5F5 for <jose@ietf.org>; Wed, 7 Aug 2024 10:46:44 -0700 (PDT)
Received: by mail-ua1-x92d.google.com with SMTP id a1e0cc1a2514c-820f7c6eaa5so42487241.3 for <jose@ietf.org>; Wed, 07 Aug 2024 10:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1723052803; x=1723657603; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wxX+J7yIahwRvVfDHHsK4pO8zntbniDFUsa1SLZ79TM=; b=ACjGW5aMsSmGZJ67E9WQojHRcDPJKp//uHg1xtDF2bucJSCRsz/4WI1TKpwJfzsfLo hx0dCLMhQofnMIqKhbP0c1RNRn2NPWP62bhwTWE3ib+KV78zCADumjdjCFNPeqK2Kj09 lLewyJYK0syS8LEqBrJ2buuokth50Zy3i5ZprYd2TY3x5TKDyswI0FiIbsy3w4svtn0e BLXT+iIGv7Q2UF75nEqU5lJz9+CVXOfPDDyYApHxLApPbvETgdjxHiBTo7QnqEvjkAJ8 x1I7fmhp6wa3WO5Xh87H6pWBFzvJmiX+Z8y8BNPgMeLhX823c157IKFE98sfUJmAY4/q qFog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723052803; x=1723657603; 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=wxX+J7yIahwRvVfDHHsK4pO8zntbniDFUsa1SLZ79TM=; b=O/gfWXmpf/xZDoEK8vbdbJXVIEy9r7IcdIbTTjsrtoHg7gcxiIU4A4xWY4JGYXPW1z D8sbTkTeDgUT9dpYg5cuoT3UxYLWZzvS6r+0clqORT3uWcpkTIysQM5jf7kMjjbDuYZM I3vX+FXF45/1McjxPBN/7DHYa1uvLsMpd1RwrSN/9DEkh6HjK1raVTQLouZBRS++jrE9 fs/pLpUHNZvhWtwqYNicAtqX2sYyke0yNFBgfaeT0lw7aYtOg1TpBrzcIIYHfr+d3nBx KewCVLpYVvQBaoyTDsP8Jl9o4n+1QgKVREYMNp1Yy5C6yIrzA0xa8FgR2Rc8Mhpq0PnE ZqCw==
X-Gm-Message-State: AOJu0Yz5JTirs5WwtDhPYnHkx4+n2w1faLyMPJfngaq1HhX+g3va48oW T5H3hJuuktCIBmCl/sHK5gXMiwx6hr+FCAkFFmGXgF8mbVHFEKaA9ZYCPU9ijMHHx8nTS90X0cl gqLOpylU3be7pQTKpYNSi7/TEaIZWFxGoUVYLEjBRqcP+uaErQNsAXN4yjwz+79qgh6Od/kzuR8 VxglfiI8Mp
X-Google-Smtp-Source: AGHT+IFrfn+8CcdLi2sh2o1xXzJaee1I5uIso8WGeP2Uh5thA3XYz/PbmZZVT1PuAsc+Kl0WK0J8p09oUOy+CZkqsGY=
X-Received: by 2002:a05:6102:d92:b0:48f:cff1:80b9 with SMTP id ada2fe7eead31-4945beb0311mr20849685137.23.1723052802719; Wed, 07 Aug 2024 10:46:42 -0700 (PDT)
MIME-Version: 1.0
References: <SJ0PR02MB74391ECC2D8130E1F0994C1AB7BF2@SJ0PR02MB7439.namprd02.prod.outlook.com>
In-Reply-To: <SJ0PR02MB74391ECC2D8130E1F0994C1AB7BF2@SJ0PR02MB7439.namprd02.prod.outlook.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 07 Aug 2024 11:46:15 -0600
Message-ID: <CA+k3eCQNWURoC=PcgNsmqGNhbd0Vpu9ukSwx+ZzJ7zLLS1hckg@mail.gmail.com>
To: Michael Jones <michael_b_jones@hotmail.com>
Content-Type: multipart/alternative; boundary="0000000000003c628e061f1b7e19"
Message-ID-Hash: VUZOR3N3SA2CQSXAEP5A66IAU32NPVB3
X-Message-ID-Hash: VUZOR3N3SA2CQSXAEP5A66IAU32NPVB3
X-MailFrom: bcampbell@pingidentity.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "jose@ietf.org" <jose@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [jose] Re: Do you need the JWP JSON Serialization?
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/tD36rK3UdR9q5zSanqqZwralroI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Owner: <mailto:jose-owner@ietf.org>
List-Post: <mailto:jose@ietf.org>
List-Subscribe: <mailto:jose-join@ietf.org>
List-Unsubscribe: <mailto:jose-leave@ietf.org>
Trying to take a bit of learning from history - the many JSON serializations for JWS and JWE have, to the best of my knowledge, been very scantily used or implemented in comparison to the popular compact serializations. As such, I don't believe the JWP JSON Serialization is needed. On Tue, Aug 6, 2024 at 5:42 PM Michael Jones <michael_b_jones@hotmail.com> wrote: > I’m writing to ask whether any of you have a use case that requires the > JSON Web Proof JSON Serialization? Unless concrete reasons are provided to > keep it, we propose to make the Compact Serialization the only JSON > Serialization for JWPs. This is being tracked at > https://github.com/ietf-wg-jose/json-web-proof/issues/100. > > > > Responses saying “I don’t need the JSON Serialization” are also welcomed. > > > > (A CBOR serialization is planned of course – something we hope to create > before IETF 121 in Dublin, building on the work to use binary fields values > in computations that we did prior to Vancouver.) > > > > Thanks, > > -- Mike & > DW > > > _______________________________________________ > jose mailing list -- jose@ietf.org > To unsubscribe send an email to jose-leave@ietf.org > -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
- [jose] Do you need the JWP JSON Serialization? Michael Jones
- [jose] Re: Do you need the JWP JSON Serialization? Bret Jordan
- [jose] Re: Do you need the JWP JSON Serialization? Michael Jones
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Carsten Bormann
- [jose] Re: Do you need the JWP JSON Serialization? David Waite
- [jose] Re: Do you need the JWP JSON Serialization? Carsten Bormann
- [jose] Re: Do you need the JWP JSON Serialization? Brian Campbell
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Brian Campbell
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Neil Madden
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Neil Madden
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Neil Madden
- [jose] Re: Do you need the JWP JSON Serialization? Orie Steele
- [jose] Re: Do you need the JWP JSON Serialization? Brian Campbell
- [jose] Re: Do you need the JWP JSON Serialization? David Waite