attachment
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Ira,</div><div><br></div><div>Yes let's discuss the policy on Monday. But don't hold back on sending the registrations...<br><br>Sent from my iPhone</div><div><br>On Aug 23, 2014, at 3:11 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div>Hi Smith,<br><br></div>Both of these new values for "output-bin" are included in the latest<br></div>IANA registrations file that Mike sent me on Friday.<br><br></div>
Mike - I assume we should talk about IPP deprecation policy on<br></div>Monday? Should I wait to send this latest IANA registrations file<br></div>to Amanda until after our discussion at Monday's IPP meeting?<br><br>
</div>Cheers,<br></div>- Ira<br><br></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 Thu, Aug 21, 2014 at 12:12 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"><div style="word-wrap:break-word">Hi there,<div><br></div><div>Where are we with the IANA registrations for these keywords?</div>
<div><span class="HOEnZb"><font color="#888888"><br><div>
Smith<br><br><br>
</div></font></span><div><div class="h5">
<br><div><div>On 2014-07-15, at 1:06 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div><div><div>Hi,<br>
<br></div>I agree. All of this proposal looks right (with Smith's clarifications).<br><br></div>Cheers,<br></div>- Ira<br><br></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 <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><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, Jul 15, 2014 at 1:04 PM, 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">
Smith,<br>
<br>
True about output-bin-actual being optional, so I agree with the proposed tweaks.<br>
<div><div><br>
<br>
On Jul 15, 2014, at 12:14 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:<br>
<br>
> Hi Mike,<br>
><br>
> A few tweaks:<br>
><br>
> 'collator'; Each copy is placed in an empty output tray. If all trays are full, the Printer cycles through each of the trays in an implementation-defined manner. The chosen output trays MUST be reported in the “output-bin-actual” Job Description attribute if that attribute is supported by the Printer.<br>
><br>
> 'job-separator'; All of the output for the Job is placed in an empty output tray. If no trays are empty, the Printer chooses an output tray in an implementation-defined manner. The chosen output tray MUST be reported in the “output-bin-actual” Job Description attribute if that attribute is supported by the Printer.<br>
><br>
> Since the “xxx-actual” attributes are only required by IPP/2.2 as per 5100.12, it is at least possible that a printer has implemented output bins but hasn’t implemented “xxx-actual” attribute support.<br>
><br>
> Smith<br>
><br>
> /**<br>
> Smith Kennedy<br>
> ATB Wireless Architect - PPS<br>
> Hewlett-Packard Co.<br>
> */<br>
><br>
><br>
><br>
> On 2014-07-14, at 3:11 PM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:<br>
><br>
>> All,<br>
>><br>
>> We discussed the proposed values for the "output-bin" attribute at today's IPP concall and have some minor changes to the definitions along with a larger clarification for the "printer-output-tray" attribute.<br>
>><br>
>> However, one of the conclusions may need to change since after further research it appears that PWG 5100.8 did indeed define the "output-bin-actual" attribute as "1setOf (type2 keyword | name(MAX)))".<br>
>><br>
>> Thus, I would like to update the definition of the "output-bin" values to be as follows:<br>
>><br>
>> 'collator'; Each copy is placed in an empty output tray. If all trays are full, the Printer cycles through each of the trays in an implementation-defined manner. The chosen output trays MUST reported in the "output-bin-actual" Job Description attribute.<br>
>><br>
>> 'job-separator'; All of the output for the Job is placed in an empty output tray. If no trays are empty, the Printer chooses an output tray in an implementation-defined manner. The chosen output tray MUST be reported in the "output-bin-actual" Job Description attribute.<br>
>><br>
>> That would also imply that the 'auto' value should assign the chosen tray as well:<br>
>><br>
>> 'auto'; All of the output for the Job is sent to an implementation-defined output tray based on the Job Template and Document Template attributes. The chosen output tray MUST be reported in the "output-bin-actual" Job Description attribute.<br>
>><br>
>> ....<br>
>><br>
>> Since the "printer-output-tray" attribute is linked to the "output-bin-supported" attribute, we discussed how to report logical trays such as 'auto', 'collator', and 'job-separator'. We decided the following:<br>
>><br>
>> 1. Logical trays are provided by the service, so while they will be listed in the "printer-output-tray" attribute they will NOT be listed in the Printer MIB prtOutputTray table.<br>
>><br>
>> 2. Logical trays are reported in "printer-output-tray" using a 'type' value of 'other' (1). The values of the other fields are calculated in an implementation-defined behavior (roll-up status, etc.)<br>
>><br>
>> 3. The same behavior should be applied to "printer-input-tray" for the "media-source" value of 'auto'.<br>
>><br>
>> Comments?<br>
>><br>
>> _________________________________________________________<br>
>> Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
>><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><br>
><br>
<br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
<br>
</div></div><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><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div>
</div></blockquote></body></html>