attachment

<div dir="ltr"><div><div><div><div>Hi Bill,<br><br></div>I agree with you - that&#39;s what I was realizing when I wrote my previous note.<br></div>Identify-Xxx is a device-level operation.  <br><br>BTW - what about conflicts between two different services that receive <br>

conflicting Identify-Xxx operations (or cancels)?<br><br></div>Cheers,<br></div>- Ira<br><br><div><div><br></div></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 &amp; 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 Tue, Dec 10, 2013 at 12:34 AM, William A Wagner <span dir="ltr">&lt;<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Ira,<u></u><u></u></span></p><p class="MsoNormal">

<span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I suggest that what is being identified is the physical device, and that the System Control Service is the proper recipient. <u></u><u></u></span></p>

<p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Bill Wagner<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u> <u></u></span></p>

<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a> [mailto:<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>] <b>On Behalf Of </b>Ira McDonald<br>

<b>Sent:</b> Monday, December 09, 2013 5:37 PM<br><b>To:</b> Kennedy, Smith (Wireless Architect)<br><b>Cc:</b> &lt;<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>&gt;<br><b>Subject:</b> Re: [IPP] RFC: Identify-Printer mini-extension<u></u><u></u></span></p>

</div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><div><div><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi Smith,<u></u><u></u></p></div><p class="MsoNormal" style="margin-bottom:12.0pt">
Tricky.  The &quot;identify action duration&quot; would be a new attribute (which<br>
would require a revision of JPS3 spec - yuck).<u></u><u></u></p></div><p class="MsoNormal">Mike&#39;s right that IPPSIX is the wrong place to do this - the conformance<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">

shouldn&#39;t have anything to do with IPPSIX.<u></u><u></u></p></div><div><p class="MsoNormal">I also don&#39;t think that System Control Service should get into this business<u></u><u></u></p></div><div><p class="MsoNormal">

- or maybe I&#39;m crazy and that actually is the *right* place?  Should SCS,<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">rather than an individual service, be the target of this device-level operation?<u></u><u></u></p>

</div><div><p class="MsoNormal">Someday, we need a lightweight IPP registration for whole new attributes<u></u><u></u></p></div><div><p class="MsoNormal">(in an existing attribute group), I suspect.<u></u><u></u></p></div>

<div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Cheers,<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">- Ira<u></u><u></u></p></div></div><div><p class="MsoNormal">

<br clear="all"><u></u><u></u></p><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">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 &amp; Printer MIB<br>Blue Roof Music / High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333ff">http://sites.google.com/site/blueroofmusic</span></a><br>

<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600cc">http://sites.google.com/site/highnorthinc</span></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" value="+17349440094" target="_blank">734-944-0094</a><br>Summer  PO Box 221  Grand Marais, MI 49839  <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><u></u><u></u></p>

</div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p><div><p class="MsoNormal">On Mon, Dec 9, 2013 at 5:28 PM, Kennedy, Smith (Wireless Architect) &lt;<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>&gt; wrote:<u></u><u></u></p>

<p class="MsoNormal">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 style="color:#888888"><br>

<span>Smith</span></span><u></u><u></u></p><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br><br><br>On 2013-12-09, at 12:53 PM, Michael Sweet &lt;<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>&gt; wrote:<br>

<br>&gt; All,<br>&gt;<br>&gt; 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 &quot;identify-actions&quot; keyword (&#39;cancel&#39;) that would cancel any active identification mechanism.<br>

&gt;<br>&gt; In addition, a new &quot;printer-state-reasons&quot; keyword (&#39;identifying-printer&#39; was proposed, although given the existing &#39;identify-printer-requested&#39; value I like adding &#39;identify-printer-active&#39; instead) would be added to allow a Client to discover whether a printer is currently identifying itself using an action other than &#39;cancel&#39;, which by definition stops any active identification and removes the new keyword from the &quot;printer-state-reasons&quot; attribute...<br>

&gt;<br>&gt; The official registration would look like this:<br>&gt;<br>&gt;  Attributes (attribute syntax)<br>&gt;    Keyword Attribute Value                       Reference<br>&gt;    -----------------------                       ---------<br>

&gt;  identify-actions (1setOf type2 keyword)         [PWG5100.13]<br>&gt;    cancel<br>&gt;<br>&gt;  printer-state-reasons (1setOf type2 keyword)    [RFC2911]<br>&gt;    identify-printer-active<br>&gt;<br>&gt; Thoughts?<br>

&gt;<br>&gt; (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>&gt;<br>&gt; _______________________________________________________________<br>

&gt; Michael Sweet, Senior Printing System Engineer, PWG Chair<br>&gt;<br>&gt; _______________________________________________<br>&gt; ipp mailing list<br>&gt; <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>

&gt; <a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><u></u><u></u></p></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>

ipp mailing list<br><a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><u></u><u></u></p></div><p class="MsoNormal">

<u></u> <u></u></p></div></div></div></div></div></blockquote></div><br></div>