attachment
<div dir="ltr"><div>Hi Mike,</div><div><br></div><div>Thanks for the clarifications.</div><div><br></div><div>I'll make a note to move the *parameter* definitions into a separate explicit</div><div>section in the next System Service update and to clarify that they should</div><div>not be termed attributes.</div><div><br></div><div>I still think the operation request parameters section would benefit from a </div><div>forward reference to the operation response parameters section where the</div><div>registration definitions actually occur, rather than just the obscure reference</div><div>to the 2910 "special encoding rules" (which of course we still need to keep).</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jan 4, 2016 at 8:56 AM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="-ms-word-wrap: break-word;">Ira,<div><br></div><div><div><span><blockquote type="cite"><div>On Jan 3, 2016, at 3:41 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div><div>Hi Mike,<br><br></div>Reviewing IPP minutes from 12/07, I found:<br><br><span style="background-color:rgb(255,255,0)">⁃ status-code isn't a type2 enum attribute, it is a parameter; see the<br>following for example text (although I think I'll swap the status<br>message and natural language paragraphs for the next draft):<br> ⁃ <a href="https://tools.ietf.org/html/draft-sweet-rfc2911bis-05#page-38" target="_blank">https://tools.ietf.org/html/draft-sweet-rfc2911bis-05#page-38</a><br></span><br></div><br>But in the 2911 and your latest 2911bis-06 draft, it says:<br><br><div>4.1.6. Operation Response Status Codes and Status Messages<br><br> Every operation response includes a REQUIRED "status-code" parameter<br> and MAY include the RECOMMENDED "status-message" and OPTIONAL<br> "detailed-status-message" operation attributes. The Print-URI and<br> Send-URI response MAY include an OPTIONAL "document-access-error"<br> operation attribute.<br><br><span style="background-color:rgb(255,255,0)">4.1.6.1. "status-code" (type2 enum)<br><br> The REQUIRED "status-code" parameter provides information on the<br> processing of a request...</span><br><br><br></div><div>So despite the "special encoding rules" for "status-code" with in the earlier <br>section 4.1.1 of 2911bis, the spec later describes it as a parameter but also<br></div><div>specifies its semantics as a type 2 enum in operation responses.<br></div></div></div></blockquote><div><br></div></span>Yes, type2 enum values for purposes of registration (although successful-ok's 0 value isn't strictly allowed for enums) but not an *attribute*. Status codes are part of a separate registry section. The point of my comment in the minutes is not about the registration but that "status-code" is not an attribute, but a parameter that is encoded in a fixed location of every IPP message.</div><div><br></div><div>I'll re-read the sections and see if there is anything I can do to clarify it.</div><span><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>I suggest that it's section 4.1.1 of 2911bis that's wrong (and should forward <br>reference section 4.1.6 below) and that the "special encoding rules" text is <br>gratuitous obscurity.<br><br></div><div>Cheers,<br></div><div>- Ira<br><br clear="all"></div><div><div><div><div><div><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 <a href="tel:734-944-0094" target="_blank" value="+17349440094">734-944-0094</a><br>Summer PO Box 221 Grand Marais, MI 49839 <a href="tel:906-494-2434" target="_blank" value="+19064942434">906-494-2434</a><br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div>
</div></div></div></div></div>
</div></blockquote></div><br></span><div>
<span style="color:rgb(0,0,0);text-transform:none;line-height:normal;text-indent:0px;letter-spacing:normal;font-family:"Andale Mono";font-style:normal;font-variant:normal;font-weight:normal;word-spacing:0px;white-space:normal;border-collapse:separate;border-spacing:0px"><div style="-ms-word-wrap: break-word;"><span style="color:rgb(0,0,0);text-transform:none;line-height:normal;text-indent:0px;letter-spacing:normal;font-family:"Andale Mono";font-style:normal;font-variant:normal;font-weight:normal;word-spacing:0px;white-space:normal;border-collapse:separate;border-spacing:0px"><div style="-ms-word-wrap: break-word;">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br></div></div></blockquote></div><br></div>