MIME-Version: 1.0
From: Dick Hardt <dick.hardt@gmail.com>
Date: Sat, 21 Sep 2024 06:42:01 +0200
Message-ID: 
 <CAD9ie-s_gFmkCC8uKXQXC0W1u_zcaktvvNV6wEC4RtJQMarnng@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fccf45062299c85c"
Message-ID-Hash: 7WA3YBCFAXNKR7U4XNGNFF7HK3IBZYWZ
CC: kristina@sfc.keio.ac.jp
Precedence: list
Reply-To: Dick.Hardt@gmail.com
Subject: =?utf-8?q?=5BOAUTH-WG=5D_SD-JWT_and_Unlinkability?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/oauth/SL3ZDUQlc5_f4wu1p3fFL0b8th4>

--000000000000fccf45062299c85c
Content-Type: text/plain; charset="UTF-8"

Is it really going to be practical to batch issue claims, and have the
holder randomly choose between them on presentation?

As an implementer, what is the right number of claims to be in a batch?

This section of the draft reads as a hack to add a new capability
(unlinkability) to a mechanism that did not have that as a design objective.

This is going to be like the "alg":"null" for SD-JWT. :-)

--000000000000fccf45062299c85c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Is it really going to be practical to batch issue claims, =
and have the holder randomly choose between them on presentation?<div><br><=
/div><div>As an implementer, what is the right number of claims to be in a =
batch?</div><div><br></div><div>This section of the draft reads as a hack t=
o add a new capability (unlinkability) to a mechanism that did=C2=A0not hav=
e that as a design objective.</div><div><br></div><div>This is going to be =
like the &quot;alg&quot;:&quot;null&quot; for SD-JWT. :-)</div><div><br></d=
iv><div><br></div></div>

--000000000000fccf45062299c85c--