I'm trying to get thru the IPP Everywhere self-cert tests and fix any issues with our software. The device under test (DUT) fails the very first test:
B-1 IPP Browse test: Printers appear in a search for "_ipp._tcp,_print" services.
The reason the device I'm testing fails, is because our device does not include ",_print" on the "_ipp._tcp" print service type.
I do not have strong knowledge of Bonjour requirements and MDNS itself, and I cannot find unambiguous requirements that say what "_print" is for and what it means to a client. In addition, the Bonjour Printing spec version 1.2.1 section 7.5 Advertising Services seems ambiguous, because it has an example (Apple LaserWriter) of advertising services without ",_print" in the first paragraph, and then shows "_http._tcp,_printer" service type example in last paragraph.
What specification can I refer to that explicitly explains what the purpose of ",_printer" is and why it is required? (Actually - after writing this question and then reading RFC 6763 section 7.1 Selective Instance Enumeration - "_printer" subtype helps Safari Web Browser distinguish between a printer web page vs. a generic web server apparently, but that should only apply to the "_http" service - correct?) And on top of that, to my knowledge the ability to use Bonjour in Safari has been removed a few years back). Where in the IPP Everywhere specification is the requirement the ",_print" be appended to printing service advertisements, and which service advertisements should it be appended to?
Also, why does the test look for ",_print" when the Bonjour 1.2.1 spec and the RFC refers to ",_printer" as a sub-type on http advertisement?
Thanks,
Chris
Christopher Rizzo
Xerox Corporation
GDG/Discovery/Advance Technology
26600 SW Parkway Ave.
Wilsonville, OR 97070-9251
Phone: (585) 314-6936
Email: Christopher.Rizzo at xerox.com
"The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."
-Maurice Wilkes, Memoirs of a Computer Pioneer
From: ipp <ipp-bounces at pwg.org> on behalf of PWG Workgroup <ipp at pwg.org>
Reply-To: Michael Sweet <msweet at msweet.org>
Date: Thursday, February 27, 2020 at 1:52 PM
To: PWG Announcements <pwg-announce at pwg.org>
Cc: PWG Workgroup <ipp at pwg.org>
Subject: [IPP] PWG Call for Objections: IPP Transaction-Based Printing Extensions v1.1 (TRANS) (ends March 27, 2020)
All,
This PWG Call for Objections starts today, February 27, 2020, and ends Friday March 27, 2020 at 10pm US Pacific time.
This is the formal announcement of the PWG Call for Objections for approval of the IPP Transaction-Based Printing Extensions v1.1 (TRANS), located at:
https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans11-20200226.pdf
The IPP WG has completed a last call of this document.
The PWG Process/3.0 defines the PWG Call for Objections procedure. The PWG Definition of the Standards Development Process Version 3.0 is located at:
https://www.pwg.org/chair/membership_docs/pwg-process30.pdf
HOW TO RESPOND
ONLY if you do NOT approve of this errata update, please send an email with your specific objections and *exactly* the following subject line format:
Subject: <Company Name> has reviewed the IPP Transaction-Based Printing Extensions v1.1 and has objections
WHERE TO SEND YOUR RESPONSE
Please do NOT simply reply to this note on the PWG-Announce list.
Please send your response to *all* of the following email addresses:
ipp at pwg.org (IPP WG mailing list - you must be subscribed!)
blueroofmusic at gmail.com (Ira McDonald, IPP WG Co-Chair)
ptykodi at tykodi.com (Paul Tykodi, IPP WG Co-Chair)
msweet at lakesiderobotics.ca (Michael Sweet, IPP WG Secretary and Document Editor)
Note: You must be subscribed to the IPP workgroup mailing list to send email to that list - otherwise your email will be silently discarded. You can subscribe to this list at:
https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet
_______________________________________________
ipp mailing list
ipp at pwg.org<mailto:ipp at pwg.org>
https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20200302/5e2c35b2/attachment.html>