attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ira/Smith,<div class=""><br class=""></div><div class="">As an implementor's guide, I do not believe the guide should introduce any MUSTs specific to this document since we are documenting best practices based on existing specifications. I am OK with reiterating MUSTs that come from a base spec, but I suspect that might limit the useful life of the document when those base specifications are updated/replaced. I have no problem with SHOULDs since that matches the spirit of best practices.<div class=""><br class=""></div><div class="">(let's not forget that RFC 3196 is Informational...)</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 8, 2014, at 1:16 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi Smith,<br class=""><br class="">I strongly agree with your position - the IPP Implementor's Guide v2 is going<br class="">to be a standards-track (Normative) PWG spec. And statements about<br class="">MUST (requirement) or SHOULD (recommendation) for *both* Clients and<br class="">Printers should be in the document.<br class=""><br class="">Because the title of section 4 says it's about Clients, any MUST/SHOULD<br class="">for Printers should be via a point to section 7.<br class=""><br class="">While this document mostly contains the first-ever guidance for Clients, the<br class="">original IG v1 was all about Printer implementations, and IG v2 certainly<br class="">should add best practices (especially strong SHOULD statements) about<br class="">Printer behavior, when they haven't already been specified in other IETF<br class="">or PWG standards-track IPP specs.<br class=""><br class="">It's also appropriate for IG v2 to recommend updates/tightening of other<br class="">existing PWG IPP specs, when those are updated.<br class=""><br class="">Cheers,<br class="">- Ira<br class=""><br clear="all" class=""><div class=""><div class="gmail_signature"><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="">Winter 579 Park Place Saline, MI 48176 734-944-0094<br class="">Summer 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>
<br class=""><div class="gmail_quote">On Mon, Dec 8, 2014 at 12:16 PM, Kennedy, Smith (Wireless Architect) <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"><div style="word-wrap:break-word" class="">Greetings,<div class=""><br class=""></div><div class="">The IPP Implementor’s Guide v2 has a number of comments identifying issues that need to be resolved, some of which require discussion. I wanted to raise each topic in its own email thread to the reflector rather than relying on members of the WG finding on their own, or raising them in the meeting and hoping attendees can develop a position on the fly.</div><div class=""><br class=""></div><div class="">Topic #1: Normative Statements in section 4</div><div class=""><p class="">In the minutes from
“ippv2-concall-minutes-20140428.pdf” :</p><p class=""><a href="http://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20140428.pdf" target="_blank" class="">http://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20140428.pdf</a></p><div class="">Item 5d says “4.x: Remove any
hidden conformance requirements for Printers - basically this document is about
recommendations for existing standards, which define those conformance
requirements”. I’m not sure that I agree with this, because that seems to remove any demand to qualitatively evaluate the different options in the subsections of section 4. I think it isn’t a question of “pass / fail” but rather evaluation using the qualitative labels in section 4. I know this makes section 4 unique when compared with the typical conventions of using RFC 2119 normative language and generating conformance requirements and test plans from that. But I pretty strongly believe an IPP Implementor’s Guide v2 test suite needs to evaluate Clients and Printers for their quality.</div><p class=""><u class=""></u><u class=""></u></p>
</div><div class="">Thoughts?</div><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""><div class="">
Smith<br class=""><br class=""><br class="">
</div>
<br class=""></div></font></span></div><br 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" target="_blank" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class="">
<br class=""></blockquote></div><br class="">
_______________________________________________<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 class="">
<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; " class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br class=""></div></div></body></html>