<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Hi all,<br />
<br />
I would like to inform you that the specs council has accepted our proposal to create a new working group as a dedicated home of the OpenID for Verifiable Credentials specs family. The new working group is designated as “Digital Credentials Protocols WG” (DCP WG). Please find the charter below.<br />
<br />
I would like to share our plans for starting the working group with you and get feedback. <br />
<br />
Our first suggestion is to migrate all specs to Github as soon as we can and a timetable is being developed how to do this. In our experience, GitHub is easier to work with for specification development and this move should speed up our work as well as attract further contributors. GitHub would be used in the same way as BitBucket is used (e.g. emails would be sent to the mailing list when issues are opened), except that we suggest there is one repository per specification with dedicated issue/PR tracker. If anyone objects to the specs moving to GitHub please let us know.<br />
<br />
Moving spec management and development from the Connect WG over to the new Digital Credentials WG will be a little more complex.<br />
<br />
For the three core specs, specifically:</div>
<ul>
<li>OpenID for Verifiable Presentations</li>
<li>OpenID for Verifiable Credential Issuance</li>
<li>Self-Issued OpenID Provider v2.0</li>
</ul>
<div dir="auto">These need to remain under Connect WG, until they have been through an Implementers Draft review process to ensure IPR protection for all of the contributors during the past few years. There are outstanding topics we need to solve before moving the specs to the first/next Implementers Draft. So our plan is to migrate to OIDF Github repos, evolve the specs up until the point where we can enter Implementers Draft and subsequently move them into the DCP WG. <br />
<br />
For the following, more recent drafts:</div>
<ul>
<li>OpenID for Verifiable Presentations over BLE</li>
<li>OpenID Connect UserInfo Verifiable Credentials</li>
</ul>
<div dir="auto">We will seek the approval of the initial contributors to directly adopt them in the Digital Credentials Protocols WG and move them to OIDF Github repos. <br />
<br />
The remaining two drafts:</div>
<ul>
<li>Security and Trust in OpenID for Verifiable Credentials</li>
<li>OpenID4VC High Assurance Interoperability Profile with SD-JWT VC</li>
</ul>
<div dir="auto">These are not adopted yet by the Connect WG, so the initial contributors would propose them for adoption by the DCP WG.<br />
<br />
We will keep http://openid.ne/openid4vc as the central place to publish links to all the specifications. <br />
<br />
A roadmap for these steps is being developed (with target dates) and will be communicated once the DCP WG co-chairs are confirmed and comfortable that the plan is clear and achievable.<br />
<br />
The first Digital Credentials Protocols Working Group meeting is scheduled for the 31st August 2023 at 4pm CEST in place of the regular SIOP Special Topic Call. Co-chairs for the WG will be confirmed at this first meeting.<br />
<br />
best regards,<br />
Torsten. <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Digital Credentials Protocols WG - Charter <br />
<br />
1) Working Group name:<br />
Digital Credentials Protocols Working Group<br />
<br />
2) Purpose:<br />
In the Issuer-Holder-Verifier Model, Issuers issue Digital Credentials to the Holder’s Wallet, which the End-User can then use to present the Digital Credentials to the Verifiers. Digital Credentials are cryptographically signed statements about a Subject, typically the Wallet Holder. Verifiers can check the authenticity of the data in the Digital Credentials and optionally enforce Key Binding, Biometrics Binding and/or Claim-based Binding i.e., ask the Wallet to prove that it is the intended Holder of the Digital Credential.<br />
<br />
The goal of this WG is to develop OpenID specifications for the Issuer-Holder-Verifier-Model use-cases to enable issuance and presentations of the Digital Credentials of any format (IETF SD-JWT, ISO/IEC 18013-5, etc.) and pseudonymous authentication from the End-User to the Verifier.<br />
These specifications are aimed at enabling End-Users to gain more control, privacy, and portability over their identity information; cheaper, faster, and more secure identity verification, when transforming physical credentials into digital ones using digital credentials; and a universal approach to handle identification, authentication, and authorization in digital and physical space.<br />
<br />
The work is planned to be done in liaison with the European Commission, Decentralized Identity Foundation (DIF), the European Telecommunications Standards Institute (ETSI), and ISO/IEC SC17 WG4 and WG10, which have expressed interest in profiling specifications proposed to be worked on in this WG. There is also a liaison with the OpenWallet Foundation (OWF), to foster implementation of the standards developed by this WG. <br />
<br />
3) Scope:<br />
Creation of specifications describing:<br />
· Issuance of Digital Credentials from the Issuer to the Wallet (acting as RP). This includes the mechanisms to specify which Digital Credentials the Issuer is capable of issuing. <br />
· Presentation of Digital Credentials between the Wallet (acting as IdP) and the Verifier via online (over the Internet) and proximity (near field communication) communication channels. This includes the mechanisms to specify which Digital Credentials are being requested.<br />
· Pseudonymous authentication from the End-User to the Verifier.<br />
· Interoperability profiles of the above specifications<br />
Out of Scope:<br />
Legal or regulatory advice, Identity Proofing, Identity information verification, new Credential formats<br />
<br />
4) Proposed specifications:<br />
OpenID for Verifiable Presentations<br />
OpenID for Verifiable Credential Issuance<br />
Self-Issued OpenID Provider v2.0<br />
OpenID for Verifiable Presentations over BLE<br />
OpenID Connect UserInfo Verifiable Credentials<br />
Security and Trust in OpenID for Verifiable Credentials<br />
OpenID4VC High Assurance Interoperability Profile with SD-JWT VC<br />
<br />
5) Anticipated audience or users<br />
· Issuers of Digital Credentials<br />
· Verifiers Digital Credentials<br />
· Wallet Providers<br />
· Trust Framework operators<br />
· Regulators<br />
· Security Researchers<br />
· Developer tools & infrastructure/service provider<br />
6) Language:<br />
English<br />
<br />
7) Method of work<br />
Mailing list and telephone/internet conference calls combined with face-to-face (where needed) and<br />
information sharing/collaborative working via online tools.<br />
<br />
8) The basis for determining when the work is completed:<br />
Approved “final” specifications consistent with the purpose and scope that have been through the OpenID Foundation process including vote by the membership and running code in one or more proof-of-concept, interoperability event or commercial project.<br />
<br />
Background info:<br />
Related Work<br />
The work is planned to be done in liaison with the European Commission, Decentralized Identity Foundation (DIF), ETSI, and ISO/IEC SC17 WG4 and WG10, which have expressed interest in profiling specifications proposed to be worked on in this WG.<br />
https://openid.net/sg/openid4vc/specifications/<br />
<br />
Proposers:<br />
Kristina Yasuda, Microsoft<br />
Torsten Lodderstedt, yes.com AG<br />
Joseph Heenan, Authlete<br />
Mark Haine, Considrd.Consulting Limited<br />
Oliver Terbu, Spruce Systems Inc.<br />
Takahiko Kawasaki, Authlete<br />
Vittorio Bertocci, Okta<br />
Giuseppe De Marco, Dipartimento per la trasformazione digitale<br />
Brian Campbell, Ping Identity<br />
Michael B. Jones, independent<br />
Jacob Ideskog, Curity AB<br />
Morteza Ansari, independent<br />
David Luna, ForgeRock<br />
Timo Glastra, Animo Solutions<br />
Judith Kahrer, Curity AB<br />
<br />
<br />
<br />
Anticipated contributions:<br />
https://openid.net/sg/openid4vc/specifications/<br />
https://github.com/vcstuff/oid4vc-haip-sd-jwt-vc<br />
<br />
<br />
<br /></div>
</div>
</body>
</html>