Before I continue, I would like to say that I found the IPP documents
well-written and complete. I was also surprised at how robust the protocol
was. Even with my first buggy "Friday afternoon" attempt at a server I was
still able to print from the IPP clients that are around on the net.
Many high-end printers (including the high-end of the Xerox range) have a
separate RIP unit. They usually also have a cantankerous operator who steps
in and interferes with the natural order of things.
Incoming jobs are RIPped as soon as possible and then wait in the RIPped
state until they are printed. The job goes through states like this:
If the printer catches up with the RIP it might start printing a job while
it is still being RIPped. The operator may also hold a job after it has
been ripped but before it is printed, perhaps to batch jobs requiring the
same print media.
This means that many jobs might be in the processing state, even if the
print unit itself has stopped, and that is in contradiction to the MOD 4.3.7
and 4.4.10 (and perhaps other sections).
There are two solutions.
Solution 1 is to assume that the Ripping --> Ripped --> Printing states are
all processing, and to have job-state-reasons for the sub-states. There is
already a job-interpreting and job-printing state reason, so we only need
job-interpreted as an extra state. If a job is held after it is Ripped, it
would go from processing/job-interpreted to held. When it is released, it
would go from held to processing/job-interpreted . It would then have to be
legal to hold a job that is in processing/job-interpreted.
Solution 2 is to let the job go back from processing to pending after it has
been ripped, but with the state reason job-interpreted. That makes it
easier to hold and release jobs that have been ripped, and might appear more
logical to a user, especially if the client does not distinguish between the
Either way, the client should expect to see more than one job in the
processing state, even if the printer has stopped. It is also possible to
have more than one job in each of the job-interpreting and job-printing
If a job produces a large amount of output, the operator might hold the job
after a while, in order to clear the backlog of higher priority jobs. In
this case the job has not been aborted, and the printer has not stopped, so
the job has passed from processing/job-printing to
I lean towards solution 2, but the most important thing is remove the
restriction on having only one job in the processing state.
From: Manros, Carl-Uno B [mailto:email@example.com]
Sent: Wednesday, 31 March, 1999 10:11 PM
To: firstname.lastname@example.org; 'Hastings, Tom N'; 'ipp'
Subject: RE: IPP> MOD - IPP/1.1 Issue Status - Issues Raised at Bake Off
Your issue is as valid as any discovered in the bake-off. It will be added
as issue #31.
Can you please come back with a detailed suggestion for which additional
job-state-reasons you think we need to resolve your problem?
> -----Original Message-----
> From: Anthony Porter [mailto:email@example.com]
> Sent: Tuesday, March 30, 1999 12:58 AM
> To: 'Hastings, Tom N'; 'ipp'
> Subject: RE: IPP> MOD - IPP/1.1 Issue Status - Issues Raised
> at Bake Off
> For issue 17 (Time attributes) You might consider having the
> printer return
> the number of seconds since the event occurred instead of the
> up-time at the
> event. This allows the client to display absolute time
> without the server
> needing a clock.
> I am disappointed that there has been no comment on my
> concerns regarding
> printers with a separate RIP processor. It is not possible to make a
> conformant IPP server for these machines until these issues
> are resolved.
> I think that this ought to be added to the issues list even
> though I was
> unable to attend the bake-off.
> Anthony Porter
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]On Behalf
> Of Hastings,
> Tom N
> Sent: Tuesday, 30 March, 1999 3:02 AM
> To: ipp
> Subject: IPP> MOD - IPP/1.1 Issue Status - Issues Raised at Bake Off 2
> I've copied this issue summary to:
> >> Text deleted
baan 72=3D0D=3D0AMortsel, B-2640=3D0D=3D0ABelgium
LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Kerkedelle 30=3D0D=3D0ABrussels, =