Thanks for the clarification. I missed the 4.1.5 MUST and future mDNS specification would be great here.
Regards,
Michael
-----Original Message-----
From: Michael Sweet <msweet at msweet.org>
Sent: Tuesday, August 13, 2024 2:48 PM
To: PWG IPP Workgroup <ipp at pwg.org>
Cc: Michael Ziller <mziller at microsoft.com>
Subject: [EXTERNAL] Re: [IPP] IppFaxOut specification missing mDNS resource path information
Michael,
> On Aug 13, 2024, at 2:19 PM, Michael Ziller via ipp <ipp at pwg.org> wrote:
>> The IppFaxOut spec Microsoft Word - cs-ippfaxout10-20140618-5100.15.docx (pwg.org) makes no mention of mDNS discovery for fax out support. Is the intent that all printers will use a resource path of “/ipp/faxout” or is the spec missing mention of the “rfo=/ipp/faxout” mDNS TXT record for determining the IppFaxOut resource path to use?
The FaxOut spec was written before the TXT record variable was defined/used, and then for AirPrint. I've filed an errata issue against 5100.15 to add a DNS-SD section:
https://www.pwg.org/dynamo/issues.php?U131
FWIW, except for print servers (where there would be multiple "queues") the resource path is expected to be "/ipp/faxout". From 5100.15:
4.1.5 Printer URIs
Each instance of an IPP FaxOut service is identified by a URI. The path component of an IPP FaxOut URI MUST be “/ipp/faxout” for the only (or default) instance of the service on an Imaging Device and “/ipp/faxout/instance-name” for each additional, non-default instance on the Imaging Device.
Thanks for noticing this and speaking up!
________________________
Michael Sweet