<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Aptos",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi All, <o:p></o:p></p>
<p class="MsoNormal">(sending this email as a co-chair)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As discussed in the WG meeting today (Nov 16th), This is an official call for adoption of “OpenID4VC High Assurance Interoperability Profile with SD-JWT VC” document:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://vcstuff.github.io/oid4vc-haip-sd-jwt-vc/draft-oid4vc-haip-sd-jwt-vc.html">https://vcstuff.github.io/oid4vc-haip-sd-jwt-vc/draft-oid4vc-haip-sd-jwt-vc.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please reply on the mailing list and let us know if you are in favor or against adopting this draft as WG document, by
<b>Nov 30th.<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Kristina<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Note: the OIDF process has different stages for specifications. It starts with an individual draft that is contributed to the WG (0). The WG then adopts the document (1) and decides how to evolve the specification, typically through issues
and PRs. If the WG believes the draft has a certain maturity, it will send the draft into implementers draft review and voting (2). That brings the draft to the attention of the whole OIDF membership and ensures IPR protection. Once the WG thinks the draft
is ready for final publication, the draft will be sent through a membership voting again (3).<o:p></o:p></p>
<p class="MsoNormal">This post is about (1) and Torsten’s email below is (0). The draft will be discussed and evolved further once it is adopted by the WG.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> torsten@lodderstedt.net <torsten@lodderstedt.net>
<br>
<b>Sent:</b> Thursday, November 16, 2023 8:16 AM<br>
<b>To:</b> openid-specs-digital-credentials-protocols@lists.openid.net<br>
<b>Cc:</b> Kristina Yasuda <Kristina.Yasuda@microsoft.com><br>
<b>Subject:</b> OpenID4VC High Assurance Interoperability Profile with SD-JWT VC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div name="messageBodySection">
<div>
<p class="MsoNormal">Hi all,<br>
<br>
Kristina and I would like to contribute the "OpenID4VC High Assurance Interoperability Profile with SD-JWT VC (HAIP)" to the DCP WG. <br>
<br>
HAIP is a profile of OpenID 4 VC with SD-JWT VC aimed at deployments with regulatory and higher security requirements, like eIDAS 2 or the Trusted Web project. It is already being adopted by implementers, like the Wallet Framework for .NET. <br>
<br>
best regards,<br>
Torsten. <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>