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

"Rizzo, Christopher via ipp" <[email protected]>
Newsgroups gmane.ietf.ipp
Message-ID <[email protected]>
Yes, both are updated together.

And they are independent of the hostname

Chris

Christopher Rizzo
Engineer II, Software Engineering
Design & Development Engineering

[signature_2133543743]<http://www.xerox.com/>

Xerox Corporation
Virtual Office Employee
26600 SW Parkway Ave
Wilsonville, OR 97070

[signature_379100592]<https://www.linkedin.com/company/xerox/>   [signature_3069953614] <https://www.youtube.com/user/XeroxCorp>    [signature_2858899317] <https://twitter.com/Xerox>    [signature_3573846891] <https://www.instagram.com/xerox/>    [signature_2872972201] <https://www.facebook.com/XeroxCorp>


From: Kennedy Smith <[email protected]>
Date: Tuesday, June 11, 2024 at 3:49 PM
To: Christopher Rizzo <[email protected]>
Cc: PWG Workgroup <[email protected]>, Michael Sweet <[email protected]>
Subject: Re: [IPP] What value do IPP Printers provide for "printer-name"?

CAUTION:   This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks Chris! HP printers do something similar for the default DNS-SD Instance Name. If Xerox printers provide the same value for "printer-name" as "printer-dns-sd-name", if one changes then so does the other?

Smith



On Jun 11, 2024, at 3:21 PM, Rizzo, Christopher <[email protected]> wrote:

CAUTION: External Email
The Xerox devices that I work on use the Bonjour advertisement name for IPP printer-name. I cannot speak for all Xerox products.

The factory default for this is "Xerox <model> (<last 3 bytes of eth mac addr>)".

Reason for the mac addr append is for customers that purchase more than one device they can be identified while avoiding the need for initial conflicts in name resolution.

Chris

Christopher Rizzo
Engineer II, Software Engineering
Design & Development Engineering

<http://www.xerox.com/<http://www.xerox.com>>

Xerox Corporation
Virtual Office Employee
26600 SW Parkway Ave
Wilsonville, OR 97070

<https://www.linkedin.com/company/xerox/<https://www.linkedin.com/company/xerox>> <https://www.youtube.com/user/XeroxCorp> <https://twitter.com/Xerox> <https://www.instagram.com/xerox/<https://www.instagram.com/xerox>> <https://www.facebook.com/XeroxCorp>





On 6/11/24, 12:46 PM, "ipp on behalf of Michael Sweet via ipp" <[email protected] <mailto:[email protected]> on behalf of [email protected] <mailto:[email protected]>> wrote:


Smith,


> On Jun 11, 2024, at 3:22 PM, Kennedy, Smith (Wireless & IPP Standards) <[email protected] <mailto:[email protected]>> wrote:
> ...
> So the attributes involved in a discussion were:
>
> printer-name (RFC 2911 / 8011 - required)
> printer-make-and-model (RFC 2911 / 8011 - recommended)
> printer-dns-sd-name (PWG 5100.13 - required)
>
> The wording of "printer-name" makes it sound like it should be a unique name, not a model name...


A printer by any other name would smell as sweet?


From RFC 8011, "printer-name" is *not* a unique name, just a more friendly one:


5.4.4. printer-name (name(127))


This REQUIRED Printer attribute contains the name of the Printer. It
is a name that is more End User friendly than a URI. An
Administrator determines a Printer's name and sets this attribute to
that name. This name can be the last part of the Printer's URI, or
it can be unrelated. In non-US-English locales, a name can contain
characters that are not allowed in a URI.


________________________
Michael Sweet

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
image001.png (image/png, 8.9 KB) - not displayed
image002.png (image/png, 1.4 KB) - not displayed
image003.png (image/png, 1.4 KB) - not displayed
image004.png (image/png, 1.5 KB) - not displayed
image005.png (image/png, 1.6 KB) - not displayed
image006.png (image/png, 1.4 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.