[Openid-specs-ab] Spec Call Notes 15-May-23

Thu May 18 06:39:56 UTC 2023

Am 18. Mai 2023, 04:53 +0200 schrieb Michael Jones <michael_b_jones at hotmail.com>:
> Thanks for the reminder, Torsten.  Indeed the BLE spec has been adopted.
>
> Shall I publish the current version as -00 to openid.net/specs/
Yes, please.
>  or is there a previous set of sources/html output that should be -00?  Once we’ve published -00, we can reference it from https://openid.net/wg/connect/status/.
>
>                                                        Thanks,
>                                                        -- Mike
>
> P.S.  Is it time for a call for adoption for the security analysis document?
There are outstanding comments, we will call for adoption once they have been solved.
>
> From: torsten at lodderstedt.net <torsten at lodderstedt.net>
> Sent: Wednesday, May 17, 2023 1:08 PM
> To: Artifact Binding/Connect Working Group <openid-specs-ab at lists.openid.net>; Michael Jones <michael_b_jones at hotmail.com>
> Cc: Kristina Yasuda <Kristina.Yasuda at microsoft.com>
> Subject: Re: [Openid-specs-ab] Spec Call Notes 15-May-23
>
> The call for adoption went out on 11/23/22 - look for "OpenID for Verifiable Presentations over BLE (Request for WG Adoption)“.
> Am 17. Mai 2023, 20:07 +0200 schrieb Michael Jones via Openid-specs-ab <openid-specs-ab at lists.openid.net>:
>
> > To avoid any ambiguity, a call-for-adoption e-mail should be sent to the working group, giving people two weeks to comment.  After it’s adopted, the spec can then be added to the list of working group specifications at https://openid.net/wg/connect/status/.  If the editors believe it’s ready for adoption, please let us know and any of the chairs can send that e-mail.
> >
> > We should also consider adopting the security analysis document, if the authors of it think that it’s time to do so.
> >
> >                                                        -- Mike
> >
> > From: Kristina Yasuda <Kristina.Yasuda at microsoft.com>
> > Sent: Wednesday, May 17, 2023 10:10 AM
> > To: Artifact Binding/Connect Working Group <openid-specs-ab at lists.openid.net>
> > Cc: Michael Jones <michael_b_jones at hotmail.com>
> > Subject: RE: Spec Call Notes 15-May-23
> >
> > Hi All, The understanding of the editors of the BLE spec is that it was adopted. I could not find connect call minutes documenting that during my quick search, but we have been discussing the draft as an already adopted document, and no one has objected, for example in the attached email. What is the idea behind “OpenID DID Method”? Best,Krisitna From: Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> On Behalf Of Michael Jones via Openid-specs-ab
> > Sent: Monday, May 15, 2023 5:15 PM
> > To: openid-specs-ab at lists.openid.netCc: Michael Jones <michael_b_jones at hotmail.com>
> > Subject: [Openid-specs-ab] Spec Call Notes 15-May-23
> >
> > Spec Call Notes 15-May-23
> >
> > Mike Jones
> > Nat Sakimura
> > David Waite
> > Andres Olave - CTO of Velocity Network Foundation
> > Edmund Jay
> > Takahiko Kawasaki
> >
> > Events and Initiatives
> >               EIC
> >                            OpenID4VC was a hot topic
> >                            On Friday, we held a liaison meeting with EC wallet participants
> >                            Joseph Heenan reported that he's starting OpenID4VP certification tests
> >                                          Nat observed that we still need to define exactly what tests will be included
> >                                          The tests will be based on a profile
> >                            There were discussions on the use of Federation for trust establishment in the context of EIDAS2
> >
> >               Identiverse
> >                            Will be in two weeks
> >                            The board will meet
> >                                          Mike plans to propose process updates enabling the use of GitHub, etc.
> >
> > OpenID for Verifiable Presentations over BLE
> >               A call for review went out on April 25th
> >                             https://openid.bitbucket.io/connect/openid-4-verifiable-presentations-over-ble-1_0.html              We don't believe that a call for adoption has occurred yet
> >
> > OpenID DID Method
> >               Giuseppe De Marco asked Nat and Mike about registering an OpenID DID method
> >               Nat suggested that this be in a working specification so we have clear control over it
> >
> > PRs
> >               https://bitbucket.org/openid/connect/pull-requests/              PR #510: [Federation] introductionary text, metadata section, editorials
> >                            This is actively being worked on by the editors
> >               PR #518: feat: [Federation] trust_chain JWS header parameter
> >                            This is actively being worked on by the editors
> >                            Reviews are requested
> >               PR #513: add version to userinfo profile
> >                            Nat said that this should be -00 and the previous version should be revoked
> >                            Mike will update his PR comments accordingly
> >               PR #468: First draft of OpenID 4 VC Security Analysis
> >                            Nat said that it's probably time for working group adoption discussions
> >
> > Open Issues
> >               https://bitbucket.org/openid/connect/issues?status=new&status=open              #1921: trust_chain as JWT header claim
> >                            This parallels having the "x5c" header parameter
> >                            Review requested
> >
> > Next Call
> >               The next call will be Thursday, May 18 at 7am Pacific Time
> > _______________________________________________
> > Openid-specs-ab mailing list
> > Openid-specs-ab at lists.openid.nethttps://lists.openid.net/mailman/listinfo/openid-specs-ab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20230518/fbea6b49/attachment.html>