attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Ira,<div><br><div><div>On Feb 28, 2014, at 11:19 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><font color="#000000">...</font></div>(4) In a standards-track RFC for "ipps:" we aren't allowed to put an annex<br>
</div>with code fragments - but such guidance could be published by the PWG.<br></div></div></div></div></blockquote></div><div><br></div>I think we could get away with a short mention of CUPS with an informative reference to the CUPS web site (<a href="https://www.cups.org/">https://www.cups.org/</a>); include it in the security considerations - since IPP and IPPS use the same port, the IPP Server/Printer needs to determine whether the initial request data is a TLS ClientHello or a HTTP request, strategies for doing so, and a pointer to an existing implementation (CUPS).</div><div><br></div><div>(FWIW, all CUPS does is check whether the initial bytes look like a DELETE, GET, HEAD, OPTIONS, POST, PUT, or TRACE request. If not, we let the TLS library validate the ClientHello)</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>