RFC 3998, "Internet Printing Protocol (IPP): Job and Printer Administrative Operations", March 2005Source of RFC: ipp (app)
Errata ID: 2783
Reported By: Peter Zehler
Date Reported: 2011-04-18
Verifier Name: Peter Saint-Andre
Date Verified: 2011-11-14
Section 8.1 says:
8.1. 'hold-new-jobs' Value 'hold-new-jobs': The operator has issued the Hold-New-Jobs operation (see section 3.3.1) or other means, but the output-device(s) are taking an appreciable time to stop. Later, when all output has stopped, the "printer-state" becomes 'stopped', and the 'paused' value replaces the 'moving-to-paused' value in the "printer- state-reasons" attribute. This value MUST be supported if the Hold-New-Jobs operation is supported and the implementation takes significant time to pause a device in certain circumstances.
It should say:
8.1. 'hold-new-jobs' Value 'hold-new-jobs': The operator has issued the Hold-New-Jobs operation (see section 3.3.1) or has initiated the holding of new jobs by other means. This value indicates that all Jobs subsequently submitted to the Printer will be placed into the ‘pending-held’ state. Thus all newly accepted jobs will be automatically held by the Printer. This “printer-state-reasons” value will be removed when the Operator issues the Release-Held-New-Jobs Operation or releases the holding of new jobs by other means.
This is a cut and paste error.
Note that the definition of the Hold-New-Jobs operation (3.3.1) states:
"When the Printer completes all the 'pending' and 'processing' jobs,
it enters the 'idle' state as usual. An operator monitoring Printer
state changes will know when the Printer has completed all current
jobs because the Printer enters the 'idle' state."
Thus the Printer does not enter the ‘stopped’ state as currently indicated in the text. It is the Pause-Printer
and Pause-Printer-After-Current-Job operations that move the state of the Printer to stopped’ and put the
‘moving-to-paused’ or ‘paused’ values into “printer-state-reasons”.