[Openid-specs-ab] SIOP Special Topic Call Notes 8-Dec-22

Mike Jones Michael.Jones at microsoft.com
Thu Dec 8 16:12:48 UTC 2022


SIOP Special Topic Call Notes 8-Dec-22

Mike Jones
Jan Vereecken
David Chadwick
Petteri Stenius
Joseph Heenan
Brian Campbell
Bjorn Hjelm
George Fletcher
Jeremie Miller
Dmitri Zagidulin

Jan Vereecken from Meeco introduced himself

Implementer's Drafts
              We discussed the need to publish new Implementer's Drafts of the specs soon
              This feedback comes both from the ISO interop in Melbourne this week and from others using the specs
              We need to make a focused effort to achieve this soon

Pull Requests
              https://bitbucket.org/openid/connect/pull-requests/
              PR #354: Restructure of OpenID4VP and SIOPv2 (pre ID-2)
                           Discussed during the call
                           Mike asked for reviews during the call
                           This is a prerequisite for the Implementer's Drafts
              PR #368: fix optional client id in pop
                           We discussed consistently using OPTIONAL or CONDITIONAL
                           Joseph found some of the wording odd, and is making a comment
                           David Chadwick said that many clients won't be registered with wallets
                           David is good with the client_id being optional
              PR #370: fix: Inconsistency in jwk, kid and x5c language (issue #1722)
                           Seems ready to merge after considering Oliver's comment
              PR #371: fix: clarify that the examples use parameters from the format profile (issue #1718)
                           Reviewed on the call resulting in several approvals
                           Merged
              PR #373: Added grants structure to credential offer
                           Please apply Kristina's comments, then merge
              PR #374: New VP error codes
                           David explained the choice of the name invalid_policy_reference to us
                           Mike said that perhaps invalid_policy_reference could become presentation_definition_not_found
                           Jeremie also will add a comment about the naming
              PR #251: adding an example of presenting an LDP_VC signed using bbs
                           Torsten made comments that don't appear to have been addressed
                           Karthik, can you update us on the status of it?

Issues
              https://bitbucket.org/openid/connect/issues?status=new&status=open&component=SIOP&component=Verifiable%20Presentation&component=Credential%20Issuance
              #1749: Change SIOP v2 request to OAuth2/JAR parameter set?
                           David said that this appears to be ready for a PR
              #1750: PKCE and pre-auth code flow in VCI
                           A PR should be created to do this
              #1737: OID4VP session identification for same device flow
                           This was an implementation issue that David's group had
                           We suggest creating a PR to describe using state to achieve this
              #1719: Pre-auth flow: Credential binding of IIR and Access token for AS and RP
                           We asked that clarifying text be proposed in the issue
                           David will also add a comment making suggestions
              #1551: Administrative Trust in the RP
                           David said that they've implemented this in the NGI Atlantic project with Spruce
                           Mike asked David if he was proposing syntax to say what trust methods the party supported
                                         He said that that was correct
                           David said that the information could be in the message or the metadata
                           PR #255 was created but was closed for lack of consensus
                           People are asked to weigh in on the issue whether they want to see this functionality added
                                         and if so, whether they agree with the mechanism proposed whether they'd like to see specific changes to it

Next Call
              The next call is the regular Connect call at 3pm Pacific Time on Monday, December 12

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20221208/1488d1e7/attachment-0001.html>


More information about the Openid-specs-ab mailing list