If not, why not design the protocol so that resource requirements can
be attached to the *end* of the print request?
OTOH, I personally think that it would probably be better in version
1.0 to take the "do or die approach": let the human or driver negotiate
some resources (like A4 paper) up front, and then the job either prints
or crashes. Just make sure the error report is right..... There's no
way I can think of where one can negotiate on *every* resource one
can think of - for instance, some *ancient* PostScript printers allowed
you to put 68000 machine code into PostScript files; do you want to
include negotiation on the CPU type in the printer?
KISS.....
Harald A