Re: What value do IPP Printers provide for "printer-name"?

Michael Sweet via ipp <[email protected]> Mon, 30 Sep 2024 11:59:07 -0400
Newsgroups	gmane.ietf.ipp
Message-ID	<[email protected]>
Smith,

<cups-hat>

CUPS doesn't currently use printer-name from an IPP printer at all right now.  We *do* use the discovered DNS-SD service instance name (printer-dns-sd-name) which at least should be consistent going forward, and if we ever bring back LDAP support then we'll use the printer-name value there.

We have a pending feature request for CUPS 2.5/3.0 that adds support for configuration profiles (a la iOS/macOS's mobile config files) which specify a printer's printer-uri-supported, printer-uuid, printer-make-and-model, and printer-name values, and the queue name will be created from the name and (if necessary) UUID.

</cups-hat>



> On Sep 29, 2024, at 11:17 PM, Kennedy, Smith (Wireless & IPP Standards) <[email protected]> wrote:
> 
> Hi Mike, 
> 
> (Trying to make sure this doesn't evaporate from our awareness.)
> 
> I think this guidance is reasonable. I don't know if there are clients for whom this may break things, but it sounds like there are enough printers that already conform to the basics of this model that it shouldn't cause too many problems. 
> 
> If there are any client vendors other that Microsoft that could comment on this, that would help allay concerns.
> 
> Smith
> 
> /**
>     Smith Kennedy
>     HP Inc.
> */ 
> 
>> On Jun 22, 2024, at 11:06 AM, Michael Sweet via ipp <[email protected]> wrote:
>> 
>> CAUTION: External Email
>> 
>> Michael,
>> 
>>> On Jun 21, 2024, at 5:06 PM, Michael Ziller via ipp <[email protected]> wrote:
>>> 
>>> But if the user connects using the IP, 192.168.1.37, are they really expecting the print queue name to show up as “192.168.1.37”?
>>> We have precedent for this for TCP ports in Windows and it queries the device for the queue name to use and displays “Manufacturer Model” just like with DNS-SD/mDNS.
>>> Wouldn’t it make sense to use printer-dns-sd-name here as well then?
>> 
>> The DNS-SD name's scope is (generally) the printer's local subnet and so might conflict if you are accessing it from a different subnet, which might be the case if you are using an IP address or hostname instead of finding it via DNS-SD lookup.
>> 
>> The recommendation I am thinking of putting in IPP Everywhere (subject to review of course) is that "printer-name" defaults to "MAKE MODEL (SERIAL-NUMBER-OR-MAC-ADDRESS)" and "printer-dns-sd-name" defaults to the "printer-name" value.  Thus, "printer-name" retains the semantics of being the user friendly name to identify the printer with and "printer-dns-sd-name" tracks the current DNS-SD service instance name with any conflicts resolved.
>> 
>> We can also talk about how the other IPP attributes ("printer-geo-location", "printer-info", "printer-location", "printer-make-and-model", and "printer-serial-number") are presented/used, with examples to clarify the semantics of each.
>> 
>> ________________________
>> Michael Sweet
>> 
>> _______________________________________________
>> ipp mailing list
>> [email protected]
>> https://www.pwg.org/mailman/listinfo/ipp
> 

________________________
Michael Sweet

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc (application/pgp-signature, 833 B)