<div dir="ltr">I support the adoption of this document. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 22, 2023 at 11:33 AM David Chadwick via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net">openid-specs-digital-credentials-protocols@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<p>I support adoption<br>
</p>
<div>On 22/09/2023 09:46, torsten--- via
Openid-specs-digital-credentials-protocols wrote:<br>
</div>
<blockquote type="cite">
<div name="messageBodySection">
<div dir="auto">Hi all, <br>
<br>
@Daniel: thanks a lot for your offer to contribute the
document. <br>
<br>
<strong>As discussed in the WG meeting yesterday, please
indicate whether you support the adoption of this document
as WG draft. </strong><br>
<br>
Note: the OIDF process has different stages for
specifications. It starts with an individual draft that is
contributed to the WG (1). The WG then takes over control 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 publication, the draft
will be sent through a membership voting again (3).<br>
<br>
This post is about (1). So we will be evolving this draft as a
WG. So even if you think the current draft needs to be
enhanced, no worries, we will open discuss this in the WG. <br>
<br>
best regards,<br>
Torsten. <br>
</div>
</div>
<div name="messageSignatureSection"><br>
<div>Torsten.</div>
</div>
<div name="messageReplySection">Am 11. Sept. 2023, 17:14 +0200
schrieb Daniel Fett via
Openid-specs-digital-credentials-protocols
<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank"><openid-specs-digital-credentials-protocols@lists.openid.net></a>:<br>
<blockquote type="cite" style="border-left-color:grey;border-left-width:thin;border-left-style:solid;margin:5px;padding-left:10px">
<p>Hi all,</p>
<p>I'd like to contribute the "Security and Trust" document to
the DCP WG: <a href="https://github.com/vcstuff/oid4vc-security-and-trust" target="_blank">https://github.com/vcstuff/oid4vc-security-and-trust</a></p>
<p>It has been discussed earlier, but had no official status
so far.<br>
</p>
<p>-Daniel<br>
</p>
--<br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
</blockquote>
</div>
-- <br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div></div><div><b>Amir Sharif</b><br></div><div><div><b>Researcher</b><br></div><div><b>Security and Trust Research Unit</b></div><div><b>Cybersecurity Center</b></div><div><b>Fondazione Bruno Kessler, Trento, Italy</b></div><div><div style="font-size:12.8px"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="color:rgb(136,136,136);font-size:12.8px">personal page:</span><a href="https://st.fbk.eu/people/amir-sharif" style="color:rgb(17,85,204)" target="_blank">https://st.fbk.eu/people/amir-sharif</a><b style="color:rgb(32,33,36)"> </b></div><div style="color:rgb(136,136,136)">FBK web: <a href="https://www.fbk.eu" target="_blank">www.fbk.eu</a></div><div style="color:rgb(136,136,136)">Cybersecurity center web: <a href="https://cs.fbk.eu" style="color:rgb(17,85,204)" target="_blank">www.cs.fbk.eu</a></div></div></div></div></div></div></div></div></div><div style="color:rgb(34,34,34)"><span style="color:rgb(136,136,136);font-size:12.8px">Security &Trust web:</span> <a href="https://st.fbk.eu" style="color:rgb(17,85,204);font-size:12.8px" target="_blank">st.fbk.eu</a></div></div><div dir="ltr"><b><br></b></div><div dir="ltr" style="text-align:center"> <b><br></b></div></div></div></div></div>
<br>
<div style="font-family:Arial,Helvetica,sans-serif"><span style="font-size:x-small">--</span></div><div><div><font size="1"><font face="Arial, Helvetica, sans-serif">Le informazioni contenute nella presente comunicazione sono di natura </font><span style="font-family:Arial,Helvetica,sans-serif">privata e come tali sono da considerarsi riservate ed indirizzate </span><span style="font-family:Arial,Helvetica,sans-serif">esclusivamente ai destinatari indicati e per le finalità strettamente </span><span style="font-family:Arial,Helvetica,sans-serif">legate al relativo contenuto. Se avete ricevuto questo messaggio per </span><span style="font-family:Arial,Helvetica,sans-serif">errore, vi preghiamo di eliminarlo e di inviare una comunicazione </span><span style="font-family:Arial,Helvetica,sans-serif">all’indirizzo e-mail del mittente.</span></font></div></div><div style="font-family:Arial,Helvetica,sans-serif"><font face="Arial, Helvetica, sans-serif" size="1">--</font></div><div style="font-family:Arial,Helvetica,sans-serif"><font size="1">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material.</font></div>