<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I also support adoption of the document<br><div><div><br></div><div>---<br><div>
<meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Judith Kahrer<br>Product Marketing Engineer<br>Curity AB<br>Sankt Göransgatan 66, Stockholm, Sweden<br><br>E: judith.kahrer@curity.io<br>W: curity.io<br><br><br></div></div>
</div>
<div><br><blockquote type="cite"><div>On 22 Sep 2023, at 10:46, torsten--- via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net> wrote:</div><br class="Apple-interchange-newline"><div>
<title></title>
<div>
<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 class="matchFont">Torsten.</div>
</div>
<div name="messageReplySection">Am 11. Sept. 2023, 17:14 +0200 schrieb Daniel Fett via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net>:<br>
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;"><p>Hi all,</p><p>I'd like to contribute the "Security and Trust" document to the DCP WG: <a moz-do-not-send="true" href="https://github.com/vcstuff/oid4vc-security-and-trust" class="moz-txt-link-freetext">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>
Openid-specs-digital-credentials-protocols@lists.openid.net<br>
https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols<br></blockquote>
</div>
</div>
-- <br>Openid-specs-digital-credentials-protocols mailing list<br>Openid-specs-digital-credentials-protocols@lists.openid.net<br>https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols<br></div></blockquote></div><br></div></div></body></html>