<div dir="ltr"><div dir="ltr">I do not believe the Working Group should adopt the OpenID Connect Key Binding draft.</div><div dir="ltr"><br></div><div dir="ltr">I
find that this document is conceptually duplicative of much of the
existing Working Group's efforts on the OpenID Connect UserInfo
Verifiable Credentials (VC) document. Richard, one of the authors of the
UserInfo VC draft, recently proposed reviving that draft and rebasing
it on the latest OpenID4VCI and the simpler SD-JWT VC token construct. I
previously expressed <a href="https://lists.openid.net/pipermail/openid-specs-ab/2025-September/010981.html">my support for that proposal on the mailing list</a>,
and I reiterate that support now.</div><div><br></div><div><div>Even if some
authors and contributors to the UserInfo VC work have shifted their focus, I
believe the Working Group should not discard or disregard that existing
work by adopting a duplicative specification. At a minimum, there should
be a clear attempt at collaboration or reconciliation between these
efforts before proceeding with adoption.</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Sep 23, 2025 at 10:38 AM george--- via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>As per my many comments and emails on this topic…<div><br></div><div>I am in favor of providing a mechanisms for Relying Parties to be able to share attributes regarding the authentication of the logged in user with downstream systems (e.g. resource servers). I am not in favor of using an id_token to communicate this information.</div><div><br></div><div>Not sure if this is helpful to the chairs or not :) </div><div><br id="m_-1287078269931922596lineBreakAtBeginningOfMessage"><div>
<div>George Fletcher</div><div>Identity Standards Architect</div><div>Practical Identity LLC</div><div><br></div><br>
</div>
<div><br><blockquote type="cite"><div>On Sep 15, 2025, at 6:57 PM, Michael Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:</div><br><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt">This starts a two-week call for feedback on whether to adopt the OpenID Connect OpenID Connect Key Binding specification contributed to the working group by Dick Hardt and Ethan Heilman as an OpenID Connect Working Group specification. Please reply-all by Monday, September 29, 2025 saying whether you are favor of adoption or not, also saying why.<u></u><u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt"><u></u> <u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt">The specification was contributed at<span> </span><a href="https://lists.openid.net/pipermail/openid-specs-ab/2025-August/010890.html" style="color:rgb(70,120,134);text-decoration:underline" target="_blank">https://lists.openid.net/pipermail/openid-specs-ab/2025-August/010890.html</a>. It has been extensively discussed by the working group both on calls and on the mailing list. From my observations of the discussion as a working group chair, I believe that there is consensus that it would be useful to have a standard solving the problem addressed by this specification.<u></u><u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt"><u></u> <u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt"> Writing as a working group chair,<u></u><u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt"> -- Mike<u></u><u></u></span></div><div style="margin:0in;font-size:12pt;font-family:Aptos,sans-serif"><span style="font-size:11pt"><u></u> <u></u></span></div></div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Openid-specs-ab mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><a href="mailto:Openid-specs-ab@lists.openid.net" style="color:rgb(70,120,134);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">Openid-specs-ab@lists.openid.net</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" style="color:rgb(70,120,134);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a></div></blockquote></div><br></div></div>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div></div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">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.</font></span></i>