[OAUTH-WG] Re: SD-JWT linkability

Brian Campbell <bcampbell@pingidentity.com> Sun, 22 December 2024 19:34 UTC

Return-Path: <bcampbell@pingidentity.com>
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 057A1C14F71B for <oauth@ietfa.amsl.com>; Sun, 22 Dec 2024 11:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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 BCNgG2cvKitz for <oauth@ietfa.amsl.com>; Sun, 22 Dec 2024 11:34:33 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (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 42EA2C14F5FE for <oauth@ietf.org>; Sun, 22 Dec 2024 11:34:33 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id ada2fe7eead31-4aff04f17c7so2634447137.0 for <oauth@ietf.org>; Sun, 22 Dec 2024 11:34:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1734896072; x=1735500872; 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=EiLVXr0MT+jYhfBIs1QF04gTENncUeRS0FZwbbv4DqY=; b=VLV8Z80olwjfKeOGtWUNXPI3s3/alz73dX8yKkh+7B62YBgwqqxlNM2ln4z9TlZV/o hv4kE8ReIPOsFbeGUOweZg5yezqlh1AenftZjSbREjwg/LQFdcEouITyy+4tIVCabkL/ OBgDTL2l+lBtq17EimkXsfOaiEZN0sYW1TaU63HGYxRoJy9ou6boN4wH4/6i3PM2PTp/ H2TcaQnmFXAo6WcKVHIjL/ncLiDa8dhFw9XRQ4lhhmdLG7SmH4zsCBIjPMGyIj8Daoa1 fSoRU6+y2ze3rHp9xA7Vq9QqMd8ccyteKUYEO7ebs4yBVO0bBG20LLBq4f21uo4N4YgA vAmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734896072; x=1735500872; 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=EiLVXr0MT+jYhfBIs1QF04gTENncUeRS0FZwbbv4DqY=; b=g0ym1ZBa/6D/vmV76ZjKwbiK95OmpZmUo4Tak8Uu/ZPoDC8fAs4OdZNb7PlCV2+P5o VPcvK1iByncN2H20oppagU3zeTaB01FGx+23Eapl/5Wyx6fr3GqAFCWsdtkbgES5dY4P qNfgw/VEsg93QirJyfblxl0C2fFDSwelSPDQR2l9+GtkCDe7odDa005CwH3UR59eXplC h+BJRrexvCPUj5fXeGS/NM5yNcs5Ihn368g4N1rLueGau6U2z9hljvGFFTBsOgI1wrDc WL9Px+vhuqUgydZIBKxIDLgZtXq3E57Y5/3W6ZX9yxnmo25d4W95vw/lVCiwg8+e1B7f y9eQ==
X-Gm-Message-State: AOJu0Ywyo+xldzx8PiN5r6UF684NQUm9JpWx0vUg3dEPn+uqmreTaTNf T0P5vsR7cwXkPqJilmUzTUJ/m5+0WQFRso8cBw/HTgK9kaipSBSnsNNWpLmTZEXf2yAW82Pa2Qb dyV4dcqYnC660as6xaDAIdN1kCO0fS1GKgcRkEjwjR+5gljjtQgg+8eyPgdkaIymBTbXJserNOP Zg6XTABnwOEhZ+QEg+FUMJ
X-Gm-Gg: ASbGnctaPw0paVDjniSinF7d/W4msIDhLVHT/M0oixV4L7t6s1VKAihECVfaaXRlXf0 Dl3/wkLAZwjiftMBXVg6V0kWZtmDLgDXc+YAfbm9EAtzvHdbiEkCkO8Mo0T3N8FFvNfi4dfY=
X-Google-Smtp-Source: AGHT+IG+yMY8XPJ7N+kArqgNsr4G2aS7T9QRNOZPK5/769lGvvzwJ29FApXlfeFEQby8J6G7vvXyV+27+Ty506Nu8xM=
X-Received: by 2002:a05:6102:4a91:b0:4af:f809:5162 with SMTP id ada2fe7eead31-4b2cd6a088emr7967489137.3.1734896072284; Sun, 22 Dec 2024 11:34:32 -0800 (PST)
MIME-Version: 1.0
References: <CACsn0ckGp4AocD1fQbMCs45P_Z5vjveggzDJw=-Vk5kxinM28Q@mail.gmail.com> <D8C86F2E-E288-4799-98BD-108F553C8CFE@authlete.com> <CACsn0cnKLr0Z-uJRM0TySCXCBbcO8wkDhRFLbsh8K8LBJepTbA@mail.gmail.com> <50282CFE-6DE4-48B7-9080-E2D4E81F9569@authlete.com> <CACsn0ckGOpLR617mFTjVH94kiV3Xi4U6PZT-w=YW9g1_+tZ9Jg@mail.gmail.com> <7D0A7B17-9C40-4439-900D-81A744F7AD4F@authlete.com> <CACsn0cnfXtKztn1gkg_hpjPTetVr6j_+0EtERPccLtGwSkDG7w@mail.gmail.com> <F524EFC2-CB12-42B7-A8AA-BF3141338304@authlete.com>
In-Reply-To: <F524EFC2-CB12-42B7-A8AA-BF3141338304@authlete.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Sun, 22 Dec 2024 12:34:22 -0700
Message-ID: <CA+k3eCQg8R+jkb=n9s2kjVQWQ1WQ4WLeQmc2kKHd8nNnB622Gw@mail.gmail.com>
To: Joseph Heenan <joseph@authlete.com>
Content-Type: multipart/alternative; boundary="0000000000001c7c960629e0f88c"
Message-ID-Hash: AK2PAHB4O4CADP7IYTUXEMWEKOX3LSUR
X-Message-ID-Hash: AK2PAHB4O4CADP7IYTUXEMWEKOX3LSUR
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
CC: IETF oauth WG <oauth@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [OAUTH-WG] Re: SD-JWT linkability
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/bgVjf4xEdHT0fYyxzj-mEqjO1xU>
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>

On Sat, Dec 21, 2024 at 1:37 PM Joseph Heenan <joseph@authlete.com> wrote:

>
>  < ...  snip ... >
>
> The current text is clear that there are situations where issuer-verifier
> linkability can’t be fully prevented.
>
> Process wide, I believe if you think the text currently in the
> specification is inadequate, you need to make a concrete suggestion that
> doesn’t introduce new problems and hence can gain consensus with working
> group members.
>
>
I believe this kinda gets at the heart of things here. It does for me
anyway. There are indeed some legitimate and not obvious or intuitive
privacy considerations inherent in salted-hash based selective disclosure
mechanisms like SD-JWT (also SD-CWT, ISO mdoc/mDL, and probably others I'm
unaware of) that deserve serious treatment in a prospective RFC. The
authors on this draft have endeavored to provide thoughtful treatment of
the topic(s) and believe that the current text, while obviously not
perfect, is reasonably clear and provides sufficient discourse on the
subject(s). Watson feels otherwise, which is a completely reasonable
viewpoint. However, at this stage of things especially, I believe it is
incumbent on him to provide a concrete suggestion that doesn't introduce
new/unwanted problems and can be viewed as at least acceptable as rough
consensus of the working group. This thread and several others of a very
similar vein over the last few months suggests that, from my perspective as
both draft author and WG participant anyway, the various proposals don't
meet that bar.

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