attachment
<div dir="ltr"><div><div><div>Hi Smith,<br><br></div>Tricky. The "identify action duration" would be a new attribute (which<br>would require a revision of JPS3 spec - yuck).<br><br></div>Mike's right that IPPSIX is the wrong place to do this - the conformance<br>
</div><div>shouldn't have anything to do with IPPSIX.<br><br></div><div>I also don't think that System Control Service should get into this business<br></div><div>- or maybe I'm crazy and that actually is the *right* place? Should SCS,<br>
</div><div>rather than an individual service, be the target of this device-level operation?<br><br></div><div>Someday, we need a lightweight IPP registration for whole new attributes<br></div><div>(in an existing attribute group), I suspect.<br>
</div><div><br></div><div>Cheers,<br></div><div>- Ira<br><br></div></div><div class="gmail_extra"><br clear="all"><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 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>
<br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 5:28 PM, Kennedy, Smith (Wireless Architect) <span dir="ltr"><<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">IMHO, these look fine. I wonder if the “identify action duration” needs to be covered by something? Does the System Control Service need to concern itself with this domain?<br>
<span class="HOEnZb"><font color="#888888"><br>
Smith<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 2013-12-09, at 12:53 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
<br>
> All,<br>
><br>
> During our last Cloud Imaging Model WG meeting, we discussed having the ability to explicitly cancel a previous Identify-Printer operation. The consensus during that meeting was to add a new "identify-actions" keyword ('cancel') that would cancel any active identification mechanism.<br>
><br>
> In addition, a new "printer-state-reasons" keyword ('identifying-printer' was proposed, although given the existing 'identify-printer-requested' value I like adding 'identify-printer-active' instead) would be added to allow a Client to discover whether a printer is currently identifying itself using an action other than 'cancel', which by definition stops any active identification and removes the new keyword from the "printer-state-reasons" attribute...<br>
><br>
> The official registration would look like this:<br>
><br>
> Attributes (attribute syntax)<br>
> Keyword Attribute Value Reference<br>
> ----------------------- ---------<br>
> identify-actions (1setOf type2 keyword) [PWG5100.13]<br>
> cancel<br>
><br>
> printer-state-reasons (1setOf type2 keyword) [RFC2911]<br>
> identify-printer-active<br>
><br>
> Thoughts?<br>
><br>
> (I considered adding this to IPPSIX, but since this has application outside of shared infrastructure/cloud deployments I think we should register it separately...)<br>
><br>
> _______________________________________________________________<br>
> Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
><br>
> _______________________________________________<br>
> ipp mailing list<br>
> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br>
</div></div><br>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br></div>