[IPP] RFC: Release Printing and INFRA

[IPP] RFC: Release Printing and INFRA

Michael Sweet msweet at msweet.org
Fri Mar 1 20:17:53 UTC 2024


All,

The current draft of the IPP Shared Infrastructure Extensions v1.1 (INFRA) intends to add support for Release Printing:

    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippinfra11-20240226.pdf

The goal is to allow an Infrastructure Printer to operate in "Release Printing mode" and have a Proxy honor that mode automatically without additional configuration.  The following options are currently being considered:

OPTION 1 (what is in the current draft):

- Define new "printer-mode-configured (type2 keyword)" and "printer-mode-supported (1setOf type2 keyword)" Printer Description attributes. The value 'immediate' means the Printer is configured to schedule and print jobs immediately while 'release-printing' means that the Printer is configured to hold jobs until they are released at the printer console.
- The Proxy looks for the value of the "printer-mode-configured" attribute and either accepts all queued jobs immediately ('immediate') or waits to accept jobs until the end user releases them from the printer console.


OPTION 2:

- Document that the "job-release-action-default" and "job-release-action-supported" Printer Description attributes control whether jobs are printed immediately or held for release. The "job-password" and "job-password-encryption" operation attributes can also be used for PIN/password printing.
- The Proxy accepts any job in the 'pending' state immediately but waits until the end user releases any 'pending-held' jobs from the printer console before printing those.


Option 1 is a simple mode switch and doesn't give the end user an opportunity to choose a different mode.

Option 2 is more flexible, allowing both immediate and release printing with the same printer. But if the xxx-default/supported values are not configured correctly an end user could bypass the mode wanted by the administrator.


Please let me know what your thoughts are about this before the next IPP conference call (March 14th) so we can move forward with the INFRA errata update.

Thanks!

________________________
Michael Sweet



More information about the ipp mailing list