[OAUTH-WG] SD-JWT VC Issuer Signature Profiles/Mechanisms/Somethings

Brian Campbell <bcampbell@pingidentity.com> Fri, 25 April 2025 22:28 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@mail2.ietf.org
Delivered-To: oauth@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2BB872162D97 for <oauth@mail2.ietf.org>; Fri, 25 Apr 2025 15:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbNiScEdJekD for <oauth@mail2.ietf.org>; Fri, 25 Apr 2025 15:28:50 -0700 (PDT)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (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 mail2.ietf.org (Postfix) with ESMTPS id 785332162D81 for <oauth@ietf.org>; Fri, 25 Apr 2025 15:28:50 -0700 (PDT)
Received: by mail-ua1-x932.google.com with SMTP id a1e0cc1a2514c-86d5a786c7cso1131742241.2 for <oauth@ietf.org>; Fri, 25 Apr 2025 15:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1745620130; x=1746224930; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=S1nCcb88bM8xY6/etIDDoloITAfWKwEsNFi5Y0cN1ao=; b=JaC1lrl42mmps21zcjKaJn9ohUcKloQ9KN5TtZlWFtz7xL4qVsF27mwlOgq5c3Y//i USDCrxE24LmwKDUgRgg2mCnw0rCWI6noBFD/NJRh+NQqELR4irk9Ay4GE0l0dQfsohFi 5c+ibZOiX+KQxv33+M2gwoKvLvUuyuS8nnyYE5WJHI18UtQEv+sx1dPi0GAoWqxrJ+js AEZYph4Cz/+xmDyjcE3saQRzT7BRLwnF7/O0RgzD66grB9GZm/elr/e20a2NFRooRIQ8 mZNFC2+b/YlWCqjLlHTgYpq4g0mvxh8xIv6rPdh2wSNhrQ09MaCPqjb0w/887bK07oLP wCkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745620130; x=1746224930; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=S1nCcb88bM8xY6/etIDDoloITAfWKwEsNFi5Y0cN1ao=; b=T3mwuo7HxWAw3BnjRXd+7IImE5BO0UApYBZsNJZlI7jrNY9xOTBnxZtEg4igg4Qq1u 0UEoXLI9mZWxHpvid19NKDMM3bOxIjudA4Te2RFBhLvSni4MWCnpQERAk50hR/anhPtO YqdPYpdCdeB6SqxS7Yibfyz/ALgDXhsdain0WZ2zewnNBfCubIDo79ell/q3SJIhXpoi 4SmltcBCrUxck6MsivR2HQxCiE0JzQryBIjt5UfelnXQ74dDI7+iAO0fKPbhTgnmB/9a I6yfkI3cAH6nISGRSw9/NbD8QVZ6IaRtzMsDCQLPJFTluFsr9AMABcfcXR9t77WwYvzS i5cg==
X-Gm-Message-State: AOJu0YxnH/EOU4m/El45SN8U63tHSbWlJ5n+dBsHwcYULzsXjCksuWeQ 75SMQweez630t92yVxmtt4PZy0PHdpdkI2NCQCkeArYfK6PvJmFTeOQO9A8hfM/ClM9yWhUhYeT 153JWDFe5FaNe70PfQ5i9vTrw2qqYbr2tPRGqY1O20LNNoo+g9VSeecYFrYqVJAcmvULulY6DdS O39MRaG2dY9OjcrIyx/sjHn1g=
X-Gm-Gg: ASbGncuVdqM6Du61yWwxjZigwtin3YIjW0/N522rpLu9vpUC3ZiN32BicsW8p0/D2hi VLFpgPNovfwi/NZJK0UTUXIsHuo/ReiIx00EMiJnVggf+XtAX1IC5vdvKYwLm+P3DekMgxHXs7a NbgJN+shEgoyv9aE09SDiwwR8=
X-Google-Smtp-Source: AGHT+IGgrdbnk81/RfssTQ+Z752xbhcNZbue3sI1DplbGEVN+fVy/EpwF2AziSccjt/MH15PqVmCHGaXtcgiLFVG6RA=
X-Received: by 2002:a05:6102:b02:b0:4c3:3eb:e84d with SMTP id ada2fe7eead31-4d64255fbf1mr1265500137.21.1745620129606; Fri, 25 Apr 2025 15:28:49 -0700 (PDT)
MIME-Version: 1.0
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Fri, 25 Apr 2025 16:28:23 -0600
X-Gm-Features: ATxdqUFp_IDYdOcwVzMsWeVo3ZzHm8PWycpJoAqSs468toxRivjwPhDo-Wf5ZXE
Message-ID: <CA+k3eCTnWQQjbO+WeYNG=gx268wnV2DSu8zSrSvbn8n38zeqkg@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bd0fef0633a1db44"
Message-ID-Hash: S53HJKI6IQN3MGUDWBIK7M7PISEFOXW2
X-Message-ID-Hash: S53HJKI6IQN3MGUDWBIK7M7PISEFOXW2
X-MailFrom: bcampbell@pingidentity.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] SD-JWT VC Issuer Signature Profiles/Mechanisms/Somethings
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/-epI9a29WcxjYg8RDdyKHdV7XQ0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

While not new, the subject of how an issuer signs an SD-JWT VC and how a
verifier properly finds the public key and checks the signature has come
more into focus recently. Slides 7 and 8 of the SD-JWT VC presentation at
the Friday WG session
<https://datatracker.ietf.org/meeting/122/materials/slides-122-oauth-sessb-sd-jwt-vc-00>
of the last IETF were about PRs/issues/ideas in the area. During the
session I'd indicated intent to work towards generally what was presented
there. However, after the session some of the pesky details of life came up
and I'd not gotten to acting on that intent. In the meantime, Oliver
proposed some thoughts on the same topic in this google doc
<https://docs.google.com/document/d/1rROkQ8V0azVpXrab7M2CmVkh5EKZxrm4rwYSlNbI2MY/edit?usp=sharing>
that could pretty much obviate what I was otherwise planning on doing.
While I did add a metric junkload of comments to that document, I do think
it's conceptually the right direction and am now planning on working from
the content and discussion therein as the basis for upcoming changes.

-- 
_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._