Re: [OAUTH-WG] Request for Feedback on "SD-JWT VC" Draft Specification

Leif Johansson <leifj@mnt.se> Sat, 27 May 2023 10:52 UTC

Return-Path: <leifj@mnt.se>
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 C9FF3C151080 for <oauth@ietfa.amsl.com>; Sat, 27 May 2023 03:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.001
X-Spam-Level:
X-Spam-Status: No, score=-1.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20221208.gappssmtp.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 0XWeJKD--hVJ for <oauth@ietfa.amsl.com>; Sat, 27 May 2023 03:52:08 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 1D5AFC151065 for <oauth@ietf.org>; Sat, 27 May 2023 03:52:07 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-4f4b0a0b557so1733464e87.1 for <oauth@ietf.org>; Sat, 27 May 2023 03:52:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20221208.gappssmtp.com; s=20221208; t=1685184724; x=1687776724; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=brKymFnly15/j/U/jY1gwmEjPDftd7Fm1T5nQMlwCDc=; b=0JRGblsMH5nI6/Ho8qQJsNjtCXAyxZUbqJBJQQKzF8CTOiUfap2NZM7+5mFZLRUNfl ia5bIqCfjMsQoYhChqJ+nB1UcImCMkYkDB11VY8FVTz26bruvOuLy8O9D9JGBy+b+Pzk RlR6HMryY7XZ59Z1w3W/yETTjzWBuJDpoAucopoAmILURb3MUvdLB+Ods4Jr/L16RiI3 Ptrusf7BatLsgOfKi85kNr0q7LmuXcKBYbYtwLhahaeJ9UxyXuRODqQd7zxcNPNVNUIQ KN176L+aUJ0eQNbJH41VHmACb8kL8Fnyyd85iYybOzkjpMGpg6S0LdJ5fzB3Wv/ZjDL0 ghpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685184724; x=1687776724; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=brKymFnly15/j/U/jY1gwmEjPDftd7Fm1T5nQMlwCDc=; b=lz/JMqAeGstGs+EwkmI7AJfEAdMivM/ffIhWvb0Z1HL65PYVYYQ5gz2MvMRy982BNw 0Chq31sHCtTKxomB3AB5SAwc3jja1BG3MmSt5QC981SMwPGBs8Nog5dCEwOXqh17LLEp zjq5Fq2JToaJm6CcMq1fjYS4I137KPK19Oi+gopA2+nlOl/rgn+9QJBM+65xqsuYaIIz GqNJ3xp9ALtbQO2NF4HC6Z5/g1G98hcZ6cMcJISE9aO0yhOvPvCAiRk8+CyXDbTYYDOE 9dlMnQKoUv14M5kpVO8mhOcTV+KDvMhQWiHah4r6Jbi6oOzSHMEP4beQT97SomtUh56u BROA==
X-Gm-Message-State: AC+VfDy6Ot0Cbcyp/4t0r4dE6wz3eK29S1Aof3Q59/FA+feI634OmiXq fmYvf6Jbo4Ewf2HcdOfOhMrIiJmlgkoaE3AZqkz/T6YJ
X-Google-Smtp-Source: ACHHUZ69LPx+gsiE3OWaViuelK8OsyA0TztyNQNNyNtwUgDCnk751MMaRceJmmgmjZ7zc0+LvocXRg==
X-Received: by 2002:a19:f80c:0:b0:4f3:880b:285a with SMTP id a12-20020a19f80c000000b004f3880b285amr1449277lff.29.1685184723668; Sat, 27 May 2023 03:52:03 -0700 (PDT)
Received: from smtpclient.apple (h-82-196-111-181.NA.cust.bahnhof.se. [82.196.111.181]) by smtp.gmail.com with ESMTPSA id h8-20020a05651211c800b004f13cd61ebbsm1076799lfr.175.2023.05.27.03.52.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 27 May 2023 03:52:03 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-053D86EC-92BD-4661-90BC-8FD2A7354E22"
Content-Transfer-Encoding: 7bit
From: Leif Johansson <leifj@mnt.se>
Mime-Version: 1.0 (1.0)
Date: Sat, 27 May 2023 12:51:52 +0200
Message-Id: <3C7DCACC-7CD5-42B4-A169-9AA9564854A3@mnt.se>
References: <CAP_qYy=5nh+tzk_g067bewFO1QYEj_q=8gBNff_uZ_tA+_pU1g@mail.gmail.com>
Cc: Oliver Terbu <oliver.terbu@spruceid.com>, oauth <oauth@ietf.org>
In-Reply-To: <CAP_qYy=5nh+tzk_g067bewFO1QYEj_q=8gBNff_uZ_tA+_pU1g@mail.gmail.com>
To: Giuseppe De Marco <demarcog83@gmail.com>
X-Mailer: iPhone Mail (20B101)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ApYMTwZVly9pYFFzPgD556WyqlI>
Subject: Re: [OAUTH-WG] Request for Feedback on "SD-JWT VC" Draft Specification
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: Sat, 27 May 2023 10:52:09 -0000

Likewise!

Skickat från min iPhone

27 maj 2023 kl. 01:12 skrev Giuseppe De Marco <demarcog83@gmail.com>:


Hi,

I support sd-jwt-vc with the will to contribute to its evolution and use it in the wallet solutions under development

Il ven 26 mag 2023, 16:57 Oliver Terbu <oliver.terbu@spruceid.com> ha scritto:
Dear all,

I hope this email finds you well. I am writing to introduce "SD-JWT-based Verifiable Credentials with JSON payloads” (SD-JWT VC):

https://datatracker.ietf.org/doc/draft-terbu-sd-jwt-vc/" target="_blank" rel="noreferrer nofollow">https://datatracker.ietf.org/doc/draft-terbu-sd-jwt-vc/

This proposal builds upon the existing SD-JWT specification by the OAuth WG and aims to address certain gaps and provide specific guidance for utilizing SD-JWT in the context of Verifiable Credentials. For example, while SD-JWT defines how to implement selective disclosure in JWTs (an important building block in many Verifiable Credential use cases), it is not opinionated about the specific JWT Claim Sets in the payload to represent Verifiable Credentials and used with HB-JWT.

As you may be aware, the SD-JWT specification has already been adopted by the OAuth WG and has gained significant traction within the industry. However, the SD-JWT specification does not provide explicit guidance on using SD-JWT for Verifiable Credentials.

The eIDAS 2.0 Architecture Reference Framework (ARF) has expressed a keen interest in utilizing SD-JWT for Verifiable Credentials, and SD-JWT VC became one of the two core credential formats of the European Digital Wallet (EUDIW):

https://github.com/eu-digital-identity-wallet/architecture-and-reference-framework" target="_blank" rel="noreferrer nofollow">https://github.com/eu-digital-identity-wallet/architecture-and-reference-framework

Verifiable Credentials play a crucial role in enhancing digital trust and enabling secure identity interactions in various domains. To ensure the seamless integration of SD-JWT into the eIDAS ARF and similar initiatives, it is essential to address the existing gaps in the SD-JWT specification specifically relevant to Verifiable Credentials.

As a general-purpose format, SD-JWT itself is not the right place to define these kinds of guidelines. The SD-JWT VC draft proposes to fill these gaps by defining additional requirements, clarifying ambiguities, and providing concrete guidelines for utilizing SD-JWT in the context of Verifiable Credentials. Since SD-JWT VC and SD-JWT are closely related, we propose to develop this specification in the OAuth working group.

Your support and endorsement of this proposal would significantly contribute to the advancement of Verifiable Credentials.

If you have any questions or require additional information regarding the "SD-JWT VC" specification or its potential impact, please do not hesitate to reach out.
I’m looking forward to your feedback!

Oliver Terbu

-- 
Director of Identity Standards, Spruce Systems, Inc.
oliver.terbu@spruceid.com
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth" rel="noreferrer noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth