[IPP] RFC: Release Printing and INFRA[EXTERNAL]

[IPP] RFC: Release Printing and INFRA[EXTERNAL]

Uli Wehner ulrich.wehner at ricoh-usa.com
Fri Mar 1 20:59:18 UTC 2024


Mike,

Here are my thoughts.

Since this is just release printing rather than pull printing, it is essentially a form of direct printing. (direct as in from a workstation to the printer). I see no need to define multiple "printers".

As such, I feel the user should be able to choose if they need the job to print before they get there, say when it is a large job or if there are many, just to keep the time waiting at the printer down.
If security or privacy is a concern, then release printing would be appropriate. Maybe with a default set by the admin. My choice would be to hold the job.
I feel the job should be held at the printer, rather than at the workstation, just to make sure the job can be released if the user closes the lid on their laptop, for example. Provided the printer has the resources to do that.
For cheaper printers it may be necessary to hold the job at the workstation.

Let me know if I understood your question correctly.


Regards

Uli Wehner
ウリ・ヴェーナー

-----Original Message-----
From: ipp <ipp-bounces at pwg.org> On Behalf Of Michael Sweet via ipp
Sent: Friday, March 1, 2024 3:18 PM
To: PWG IPP Workgroup <ipp at pwg.org>
Cc: Michael Sweet <msweet at msweet.org>
Subject: [IPP] RFC: Release Printing and INFRA[EXTERNAL]

All,

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

    https://urldefense.proofpoint.com/v2/url?u=https-3A__ftp.pwg.org_pub_pwg_ipp_wd_wd-2Dippinfra11-2D20240226.pdf&d=DwICAg&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=QFsrLDGHIhLTGRHMpV-d-hQ6w_Sz4fcTZLvN2R4aJDvC-aGQnibXa29X3EscCpMn&s=TmUOBlmF0KVCLPvaS64bscPlWfo3UqrlooBG2THI7kI&e= 

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

_______________________________________________
ipp mailing list
ipp at pwg.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.pwg.org_mailman_listinfo_ipp&d=DwICAg&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=QFsrLDGHIhLTGRHMpV-d-hQ6w_Sz4fcTZLvN2R4aJDvC-aGQnibXa29X3EscCpMn&s=3ChWcAvU6bY4Kjaof-LvSteiR2bCq_RFQQ1iC42B0gI&e= 


More information about the ipp mailing list