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="">Smith,<div class=""><br class=""></div><div class="">I agree with Ira - TLS version numbers, errors, etc. belong at the TLS level and not in IPP.</div><div class=""><br class=""></div><div class="">I've included a few specific comments inline below...</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 27, 2018, at 4:25 PM, Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">...</div></div></div></blockquote><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">None of these seem to cover a lower-level protocol negotiation level failure. Do we need to add a new one for TLS version negotiation failure?</div></div></div></blockquote><div><br class=""></div>I don't think so. If the Client and Printer cannot negotiate a common supported version of TLS, the connection will fail and the Printer won't have the opportunity to tell the Client why in an IPP response since the request will not have been received.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""> The Client can learn the Printer's maximum TLS version via the "TLS" DNS-SD TXT record key (5100.14 section 4.2.3.4). The "uri-security-supported" attribute simply uses 'tls' but lists no version (which troubles me because DNS-SD shouldn't be more descriptive than IPP).</div></div></div></blockquote><div><br class=""></div></div>While the TLS key does provide slightly more information, I don't think this is critical since a) most/all? clients look for _ipps advertisements these days to determine TLS support and b) Clients do not trust such information for downgrading to a lower version of TLS thanks to the SSL3 and TLS/1.0 downgrade attacks.</div><div class=""><br class=""></div><div class="">At best the information might allow a Client to hide printers that (for example) only support TLS/1.0, or treat such printers as insecure after a suitably ominous warning to the user...</div><div class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Menlo; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div>
</div>
<br class=""></div></body></html>