[IPP] RFC: Consensus on new "output-bin" values: 'collator' and 'job-separator', issue for "output-bin-actual"
Michael Sweet
msweet at apple.com
Tue Jul 15 17:04:10 UTC 2014
Smith,
True about output-bin-actual being optional, so I agree with the proposed tweaks.
On Jul 15, 2014, at 12:14 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com> wrote:
> Hi Mike,
>
> A few tweaks:
>
> '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.
>
> '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.
>
> 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.
>
> Smith
>
> /**
> Smith Kennedy
> ATB Wireless Architect - PPS
> Hewlett-Packard Co.
> */
>
>
>
> On 2014-07-14, at 3:11 PM, Michael Sweet <msweet at apple.com> wrote:
>
>> All,
>>
>> 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.
>>
>> 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)))".
>>
>> Thus, I would like to update the definition of the "output-bin" values to be as follows:
>>
>> '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.
>>
>> '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.
>>
>> That would also imply that the 'auto' value should assign the chosen tray as well:
>>
>> '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.
>>
>> ....
>>
>> 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:
>>
>> 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.
>>
>> 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.)
>>
>> 3. The same behavior should be applied to "printer-input-tray" for the "media-source" value of 'auto'.
>>
>> Comments?
>>
>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>
>> _______________________________________________
>> ipp mailing list
>> ipp at pwg.org
>> https://www.pwg.org/mailman/listinfo/ipp
>
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4881 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140715/9249f8ec/attachment.p7s>
More information about the ipp
mailing list