attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks Ira! I will update that issue with your citations (and attribute them to you) and close it.<div class=""><br class=""></div><div class="">(I would LOVE to make a system that registers conformance requirements from specifications, and when one spec includes another, its normative statements would be sort of #included in, so that for a given spec we could see all the normative conformance requirements that pertain to a particular specification, without all the legwork and cross-checking.)<br class=""><div class=""><br class=""><div class=""><div class="">
Smith<br class=""><br class=""><br class="">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 2016-09-15, at 7:09 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class="">Hi Smith,<br class=""><br class=""></div>I disagree. <br class=""><br class=""></div><div class="">PWG 5100.14 doesn't say you MUST support Upgrade, BUT it does say <br class="">the rest about advertise and support ipps URIs. <br class=""></div></div><br class="">And PWG 5100.14 also says you MUST do IPP/2.0 (PWG 5100.12), which <br class="">says on page 33:<br class=""><br class="">7.4 IPP over TLS Conformance Requirements<br class="">To claim conformance to this specification, an IPP Printer or IPP Client<br class="">that supports TLS MUST:<br class=""><br class="">1. Support the HTTP Upgrade protocol as defined in [RFC2817]; and<br class="">2. Support the required minimum cipher suite for interoperability defined <br class="">in the claimed TLS specification.<br class=""><br class=""></div><div class="">Cheers,<br class=""></div><div class="">- Ira<br class=""></div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br class="">Chair - Linux Foundation Open Printing WG<br class="">Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP & Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br class="">May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br class=""><br class=""><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div class=""></div><div class=""></div><div class=""></div><div class=""></div></div></div></div></div></div>
<br class=""><div class="gmail_quote">On Thu, Sep 15, 2016 at 4:29 PM, <span dir="ltr" class=""><<a href="mailto:smith.kennedy@hp.com" target="_blank" class="">smith.kennedy@hp.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[Issue Unconfirmed]<br class="">
<br class="">
In PWG 5100.20, page 16, it says this:<br class="">
<br class="">
Printers that report support for TLS MUST also support HTTP Upgrade to TLS,<br class="">
correctly advertise themselves using the "_ipps._tcp,_print" sub-type, and<br class="">
support using an "ipps" URI.<br class="">
<br class="">
This is not a conformance requirement from 5100.14, however. So B-5.1<br class="">
really ought to be removed or at least be made into a SHOULD rather than a<br class="">
MUST.<br class="">
<br class="">
Link: <a href="http://www.pwg.org/issues/49" rel="noreferrer" target="_blank" class="">http://www.pwg.org/issues/49</a><br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
ipp mailing list<br class="">
<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank" class="">https://www.pwg.org/mailman/<wbr class="">listinfo/ipp</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>