Re: [OAUTH-WG] Call for adoption - SD-JWT

Daniel Fett <fett@danielfett.de> Fri, 05 August 2022 08:26 UTC

Return-Path: <fett@danielfett.de>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E36CC15C50A for <oauth@ietfa.amsl.com>; Fri, 5 Aug 2022 01:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_HI=-5, 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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=danielfett.de
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 6cW_c8s6GP6u for <oauth@ietfa.amsl.com>; Fri, 5 Aug 2022 01:26:33 -0700 (PDT)
Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) (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 A2171C15C505 for <oauth@ietf.org>; Fri, 5 Aug 2022 01:26:33 -0700 (PDT)
Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4Lzdwf0Cdfz9sTP for <oauth@ietf.org>; Fri, 5 Aug 2022 10:26:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=MBO0001; t=1659687986; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=J7fn+TGV6p46AEJ+/Jv9xI5VTFF3a+Bly66XDmeH1iE=; b=AGOlzhxINmgmGDdTZsTDvb0d/lll9gX+AoM93lITo3TePgEgkztPs5cPa6VcvbH99Xs5ra r02X1oA4KRea0HtZOAa81dVwC5ZIANg69U+BSTFzupN7Fy9qmw/WhwUVCIOixXlMGBgbYQ dW46uaQN9/mcF2UWhTZ3Yto4sk6Lxgf/zIwvJ7IofnSxet/EOtp9YNYMsQntZV9SB7m52U ObfSl1rGhNPic9ZzwyHxuroN5csKJvYw8vDiKi0I2kC2ccV9h2p03qdGqCojJRnplOeMn+ ojEIwqshebaGoA7pw28diP9NRbhwOORufzWQFCk9wijuJOPMwrt2LuD6cMHGUw==
Content-Type: multipart/alternative; boundary="------------HlrXwuMH3byWq4RZNzohtGMQ"
Message-ID: <937ef7f5-163c-aaab-3f62-bdffb17bf150@danielfett.de>
Date: Fri, 05 Aug 2022 10:26:25 +0200
MIME-Version: 1.0
Content-Language: de-DE
To: oauth@ietf.org
References: <7f46f3f1-d384-37ef-9e76-8cb80995fb4c@verifiablecredentials.info> <1D2C56C5-8155-40A3-BC00-2EF7D12C9122@lodderstedt.net> <9c1c8d86-ed98-a4e3-e864-a00c82a24134@verifiablecredentials.info> <CAODMz5EKYo19JK8Zs0=UhCNdHZM9SddOpCNjqOAA=LpeMXPJ_Q@mail.gmail.com> <5c0091b0-a8ed-3690-fc86-3fa662af0d15@danielfett.de> <CAJot-L3ZQQa0Rragt+ds8bkhHtjXM1hMVgvcShGYxdxYFYAhhg@mail.gmail.com>
From: Daniel Fett <fett@danielfett.de>
In-Reply-To: <CAJot-L3ZQQa0Rragt+ds8bkhHtjXM1hMVgvcShGYxdxYFYAhhg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/eVLM_Wam1nY0Q8z1R8iZRttB_9M>
Subject: Re: [OAUTH-WG] Call for adoption - SD-JWT
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2022 08:26:39 -0000

Am 05.08.22 um 10:22 schrieb Warren Parad:
> > and nobody involved in the JWP effort thinks that SD-JWT should be in that WG 
> once created
>
> Why?

For the reasons listed, I guess?

Also, mind the "As far as I am aware" part, but I don't remember any 
discussions in that direction at IETF114.

-Daniel