attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Greetings,<div class=""><br class=""></div><div class="">The current process for submitting IPP Everywhere Self-Certification results to the PWG are detailed at the bottom of this page:</div><div class=""><br class=""></div><div class=""><font color="#0068da" class=""><span style="caret-color: rgb(0, 104, 218);" class=""><u class=""><a href="https://www.pwg.org/ippeveselfcert/#submitting" class="">https://www.pwg.org/ippeveselfcert/#submitting</a></u></span></font></div><div class=""><br class=""></div><div class="">(This named anchor currently doesn't work so scroll to the bottom of the page...)</div><div class=""><br class=""></div><div class="">The two submission methods listed there are:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">a) Post your JSON file to the <a href="mailto:ippeveselfcert@pwg.org" class="">ippeveselfcert@pwg.org</a> reflector</div><div class="">b) Create a new issue on the istopwg/ippeveselfcert GitHub project (<a href="https://github.com/istopwg/ippeveselfcert/issues/new" class="">https://github.com/istopwg/ippeveselfcert/issues/new</a>) and attach it to that issue</div></blockquote><div class=""><br class=""></div><div class="">In contrast to the old process that used reasonably confidential submissions within the PWG website itself, this new process is completely out in the open. Printer vendors might want to reveal these only after they have been released to the public. Also, those that are submitting the test results might not want their identities to be made public.</div><div class=""><br class=""></div><div class="">Speaking to the first issue, there is a question of trust: the PWG officer might be an employee of a different printer vendor. So doing early submissions really isn't an option unless it the submissions were held "in escrow" by some neutral third party. That starts to get over-engineered pretty quickly.</div><div class=""><br class=""></div><div class="">The only resolution to these issues I can imagine would be:</div><div class=""><br class=""></div><div class="">1. Change the submission process to submit to a different email address (e.g. <a href="mailto:ippeveselfcert@pwg.org" class="">ippeveselfcertsubmission@pwg.org</a>) and make that a private reflector or a role-based email address</div><div class=""><br class=""></div><div class="">2. State cleary on the page that the certification test reports will be processed ASAP, and cannot be held in escrow, so it is up to the submitter to submit them only once they have been released to the public to avoid pre-announcing products and annoying your company's marketing department.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""><div class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/</div><br class=""></div></body></html>