IPP INFRA spec mentions the infra printer MUST support validate-job and the proxy printer MUST NOT, implying that the infra printer should not forward/save client validate-job requests to/for the proxy printer. However, it seems the infra printer can't always do as full validation as the proxy printer as part of validate-job requests sent to the infra printer. Is the intent for the proxy printer to do fetch-job, and since it now has the job template attributes, to do the same sort of validation it would be doing for local IPP print validate-job, and then returning any validation failures (or successful-ok-ignored-or-substituted-attributes) in acknowledge-job fetch-status-code?
This seems to me what proxy printers should be doing (job validation on fetch-job), but I'm not sure that's explicitly stated. Is that understanding correct? And if so, would it be useful to capture that expectation of proxy printer job validation, similar to local printer validate-job, explicitly in the spec? Or is JTA validation optional for proxy printers/output devices which want to delegate validation to the infra printer and why it's not really called out?
Thanks,
Michael Ziller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20240507/dba0d3be/attachment.html>