Michael,
> On Jan 12, 2026, at 1:38 PM, Michael Ziller via ipp <ipp at pwg.org> wrote:
>> For local printing RFC8011 allows for clients to submit vendor/custom operations to a printer.
Vendor/custom operations aren't limited to local printing, and we (the PWG and IPP WG) manage reservations for the vendor op code space here:
https://www.pwg.org/ipp/opcodes/ippopcodes.html
Some are documented, some not - public documentation is not required but is encouraged... :)
> For the cloud case, does INFRA support the proxy printer receiving and processing vendor operations from the client? If not, any thoughts on how support for that might be added?
There isn't a way to relay generic requests from a Client to a Proxy, nor to relay responses back from the Proxy to the Client.
We have two existing mechanisms for relaying requests from Client to Proxy:
- Identify-Printer (Client) -> Acknowledge-Identify-Printer (Proxy) from PWG 5100.18 (INFRA): Client sends an Identify-Printer request, Infrastructure Printer saves "identify-xxx" attributes and sets the 'identify-printer-requested' keyword in the "printer-state-reasons" attribute, and the Proxy gets the "identify-xxx" attributes using an Acknowledge-Identify-Printer request.
- Get-Encrypted-Job-Attributes (Client) -> Fetch-Encrypted-Job-Attributes and Acknowledge-Encrypted-Job-Attributes (Proxy) from (unpublished) TRUSTNOONE: Client sends a Get-Encrypted-Job-Attributes request, Infrastructure Printer saves request and sets the 'encrypted-job-attributes-requested' keyword in the "printer-state-reasons" attribute, the Proxy gets the request attributes using the Fetch-Encrypted-Job-Attributes request, and then returns the response for the Client using the Acknowledge-Encrypted-Job-Attributes request.
In both cases, the Proxy is notified (via the existing subscription it should be using to monitor for printer/job events) that it needs to do something and can respond accordingly.
________________________
Michael Sweet