Am I correct in assuming that if a client includes job-k-octets, it behaves
like other job-template attributes, namely (the model document is silent)
a) fidelity is true: if job-k-octets-supported is undefined in the
printer or job-k-octets is out of range, reject the job and
return job-k-octets in the unsupported-job-attributes group.
b) fidelity is false: the job is accepted regardless of the value
of job-k-octets or the presence or absence of
job-k-octets-supported, but if the job-k-octets-supported is
undefined in the printer or job-k-octets is out of range, return
job-k-octets in the unsupported-job-attributes group.
This behavior is perhaps a bit surprising in the fidelity = false case,
because the job-k-octets-supported is intended to be a way for a printer
to control the sizes allowed.
So this means that someone with a really big job can bypass the job-size
limit by setting fidelity = false.
It would seem that job-k-octets and the other two related attributes don't
really follow the rules of other job-template attributes.