[IPP] IPP WG Last Call: IPP Everywhere v1.1 (Ends March 12, 2020)

[IPP] IPP WG Last Call: IPP Everywhere v1.1 (Ends March 12, 2020)

Michael Sweet msweet at msweet.org
Thu Mar 5 21:57:58 UTC 2020


Smith,

I generally agree with most of your comments.  See below...


> On Mar 5, 2020, at 4:09 PM, Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy at hp.com> wrote:
>> ...
>> 4.2.1 History of Printer Discovery with DNS-SD
>> 
>> The Bonjour Printing Specification defines a discovery mechanism for three different printing protocols which are mapped to DNS-SD service types: "_ipp._tcp" for any version of IPP, "_pdl-datastream._tcp" for direct socket communications, and "_printer._tcp" for the Line Printer Daemon (LPD) [RFC1179] protocol. For historical reasons, the primary ("flagship") protocol used for DNS-SD Printer discovery is LPD regardless of whether the Printer actually supports LPD.
>> 
>> DNS-SD makes use of service "sub-types" to identify specific types of services, and the Bonjour Printing Specification also defines a well-known "_printer._sub._http._tcp" service sub-type for a Printer's embedded web server to differentiate a Printer web page from a regular web page.
> 
> I'm sorry but I really don't agree with having this new section 4.2.1. If we want to avoid future confusion between _print._sub._ipp._tcp and  _printer._tcp and _printer._sub._http._tcp, I might suggest we drop all references to the Bonjour Printing spec and focus solely on what IPP Everywhere uses for its DNS-SD advertisements. Other than the TXT portions, what are we getting by referencing Bonjour Printing at this point? Some of the normative statements above are redundant with the requirements in Bonjour Printing 1.2.1.

The flagship naming stuff is, unfortunately, still relevant.  So even if your printer doesn't support LPD you need to register "printername._printer._tcp.local." to deal with name collisions properly...

________________________
Michael Sweet





More information about the ipp mailing list