<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Hi all</div><div><br></div>Unfortunately I am sad to say that I do not support the adoption of this document as it currently stands. I would have liked to have a discussion on a working group call about it, but due to travel I’m unable to join today’s working group call so I thought it best to express my sentiments in writing instead. It is unfortunate that the call for adoption was started without the <a href="https://lists.openid.net/pipermail/openid-specs-ab/2024-August/010349.html">promised discussion at a Thursday working group meeting</a> happening first.<div><br></div><div>Firstly, it is important to say that I am very supportive of working on a profile of OpenID Federation for Wallets, and as a work like that would be at the intersection of the various specifications it could happen in the same place as the Federation specs or it could happen in the same place as the other digital credentials work is happening.<br id="lineBreakAtBeginningOfMessage"><div><br></div><div>This document however has not restricted itself to being a profile of OpenID Federation for Wallets, and hence it must not be adopted in the Connect WG in its current form. Adopting it would cause considerable confusion for implementors and specification authors, which would be harmful.</div><div><br></div><div>The following parts of the document are not solving a problem specific to federation and hence I believe should not be included in a “OpenID Federation Wallet Architecture”:</div><div><br></div><div>4. Wallet Instance Types (this just seems out of place in general as the terms defined don’t seem to be used in the rest of the specification)</div><div><br></div><div>6.1. Metadata for OpenID Wallet Provider (in particular the new ‘aal_values_supported’)</div><div><br></div><div>6.2 Metadata for the OpenID Credential Issuer</div><div><br></div><div>6.3. Metadata for OpenID Wallet Relying Party (in particular the new ‘request_uris’, ‘response_uris_supported’, ‘presentation_definitions_supported’ items are generic mechanisms that, if they need to be defined and solve the stated problem, should be defined in the VCI specification, and ‘jwks’ is little borderline and rather under documented as it’s not clear how in interworks with the existing non-federation mechanisms, e.g. the .well-known mechanism for credential keys defined in I think SD JWT VC)</div><div><br></div><div>6.3.1. Security Considerations About The Parameters request_uris And response_uris_supported (this section is also I believe technically incorrect, URL fragments don’t work like this and this is not the same way connect uses URI fragments in request uris, and there are good reasons why the JAR RFC dropped the URI fragments)</div><div><br></div><div>6.3.2. Security Considerations About The End-User's Data Protection Using presentation_definitions_supported</div><div><br></div><div>I would say in general that the text is not clear about what is new normative test and what is repeating what is already normative in other specifications. (I have not throughly reviewed the document so I have may more comments in the future.)</div><div><br></div><div>I would agree that one of two of these issues could be fixed after adoption, but I believe there substantive enough issues to not proceed with adoption until they are resolved and the overall form and intent of the document that is to be adopted is clearer (e.g. the document title is aligned with the content). I should be able to join the Thursday call in 2 weeks time to further discuss anything.</div><div><br></div><div>(For clarity, this email is sent with my Authlete ‘hat’ on.)</div><div><br></div><div>Thanks</div><div><br></div><div>Joseph</div><div><br></div><div><br></div><div><br><blockquote type="cite"><div>On 6 Aug 2024, at 02:15, Michael Jones via Openid-specs-ab <openid-specs-ab@lists.openid.net> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;">The OpenID Federation Wallet Architectures 1.0 specification was contributed to the working group last week at<a href="https://lists.openid.net/pipermail/openid-specs-ab/2024-July/010345.html" style="color: rgb(70, 120, 134); text-decoration: underline;">https://lists.openid.net/pipermail/openid-specs-ab/2024-July/010345.html</a>. Per the decision on today’s working group call, this note starts a two-week call for working group adoption of the specification, running until Monday, August 19, 2024. Please reply to this e-mail indicating whether you support adoption and providing feedback on the specification.<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;">This specification is a starting point – not an endpoint. If adopted, it can and will be revised by the working group.<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;">This specification largely records what the Italian wallet deployment is actually doing.<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;">For your convenience, this specification is hosted at<span class="Apple-converted-space"> </span><a href="https://github.com/peppelinux/federation-wallet/" style="color: rgb(70, 120, 134); text-decoration: underline;">https://github.com/peppelinux/federation-wallet/</a><span class="Apple-converted-space"> </span>and rendered HTML can be viewed at<span class="Apple-converted-space"> </span><a href="https://peppelinux.github.io/federation-wallet/main.html" style="color: rgb(70, 120, 134); text-decoration: underline;">https://peppelinux.github.io/federation-wallet/main.html</a>.<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"> -- Mike (writing as working group co-chair)<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Aptos, sans-serif;"><o:p> </o:p></div></div><span style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Openid-specs-ab mailing list</span><br style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Openid-specs-ab@lists.openid.net</a><br style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a></div></blockquote></div><br></div></body></html>