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

Anton Thomasson via ipp <ipp@pwg.org> Wed, 12 June 2024 18:40 UTC

Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27A64C18DBAD for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 12 Jun 2024 11:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.006
X-Spam-Level:
X-Spam-Status: No, score=-8.006 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pwg.org header.b="DWe0guM6"; dkim=pass (1024-bit key) header.d=pwg.org header.b="dN8AZrzA"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com header.b="Fnk3NNcs"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wk8cnhxz74Kp for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 12 Jun 2024 11:39:56 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id C715AC15108F for <ipp-archive2@ietf.org>; Wed, 12 Jun 2024 11:39:55 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 0F439E5C6; Wed, 12 Jun 2024 18:39:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 0F439E5C6
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1718217595; bh=57VWddM+xuywwtEVGQGM8yUpAVZGvjX22VJ1amMDXiU=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=DWe0guM6rlJM4cns2mZeRUbi6zsfSTg56JvtBYfk0D/lUYt2pUaLcfaRsAMiursR/ SRTZNwmduKzJY03Sw8TWIhjLkjbHlZybe35hIVHIIOVYjXZU+dinhVQWEI4I4nq6tJ e0IKF2+j5MgF4/x7WPBcIIAIyA/l2uwFJZqX9r/I=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id EAB3A33AB; Wed, 12 Jun 2024 18:39:51 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org EAB3A33AB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1718217592; bh=57VWddM+xuywwtEVGQGM8yUpAVZGvjX22VJ1amMDXiU=; h=References:In-Reply-To:Date:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=dN8AZrzAPkJpzeopunukTvpaAklZ+ZKTg6AmAu+hGYZml5aW0zkhHFaSVP8pz0uCG RfFrcDkKMwySzkyYsg2N2CCI0fAyXt6AxuwnWF7MP7v+llYFfPX9I8Gl/s0yVLOOoL ICQiDAUtP2vw5JVxSb8A9WzLS/Z5xwSKJsX0THBA=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 50A3E3A41; Wed, 12 Jun 2024 18:39:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 50A3E3A41
Authentication-Results: mail.pwg.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Fnk3NNcs"
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by mail.pwg.org (Postfix) with ESMTPS id 41D1533AB for <ipp@pwg.org>; Wed, 12 Jun 2024 18:39:45 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 41D1533AB
Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-52bc121fb1eso323391e87.1 for <ipp@pwg.org>; Wed, 12 Jun 2024 11:39:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718217584; x=1718822384; darn=pwg.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=T4oGOnU4kwQPn7nSTReFEcD68u/xqvW98G/tiRAJ0kU=; b=Fnk3NNcs6RBNQXz+UsSNP0HZQLVm3iSd3bVcSPxeyhB+d4rYqNZsHq8SWixMmdLf3R T4ZNo4KqM7t8uCnDcEKV7HMJb94B4psPPN2xr1IZ9PtSN5L+CGtWXbXRs/RhNL2nfiqN WePJFUEmSOu/70df+i1J7muxHGcM9CUJL0Sm2xOJehT8Uhm450lEuNmMdkpTOFrsesZx itDL0RamTNM0GyUHFkynAMivbOrYQoEyCtNPrkH8GyTbrJMochgxHdk6EhOwxnvfiRvY Kpw0ganFHuXvZAuSfozJjcqfuRxD0AYG1vlGgNwa6u2DsfJ35+L8tYMD3WXbmDo+5x7e 3Tng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718217584; x=1718822384; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=T4oGOnU4kwQPn7nSTReFEcD68u/xqvW98G/tiRAJ0kU=; b=YtGJ+pjFy4UM1ZBg1dAe0Zwy3xAotpSUqPB+twIfgkHXu16TER2iDXE62+YOAsg8Mk 3rQEr6SEu0Pdmal+WT1iN2j1rhfwv8UXKnvnd5X/KIPTIpJzw5klIRG3ncpIAk3G9Gq8 mLbovmNPA4piZa+ehkKB2ScP6IineI0DW2llSE1pJLmkGhYNdqd697ZmRFuRPiDSRCi4 7c/67u1YqBHwOLp49jhjfL2alTWd6Y9fJkVjadIsZS65X/QA1jEYoH3kRT6fcag7BvD2 lZbQHij7UMRj9ESRk+2G4SZEIVL8Ne8mA7wSbLyw6er9nwhVDS7z/LVxKWHafJe+RO7S m10Q==
X-Gm-Message-State: AOJu0YycxHlFWpceYg5XTKR1zq2MeakP3V6/poGL6oWOt9gI6Rn4vz3P Zb+jpmYJjNnLns3JIB2uLOPSFT3PsSwhHYZmukzSoJvtzmMttasruKSQi6I6b1UEX4T/W3auoQM jCJXtzkiwsk6iM95HeEUNfcOQ+HHtp/DK588jzw==
X-Google-Smtp-Source: AGHT+IEITqOnXHRvU5bzeTuaV73rjGG8+d1Kq/Z704O5IqbzgfA7bYWmmlFpjtqg/gzxunYT8t4KcVMQwjEIaHPu4zs=
X-Received: by 2002:ac2:5b4a:0:b0:52c:805a:f829 with SMTP id 2adb3069b0e04-52c9a3c7a15mr1369030e87.26.1718217583729; Wed, 12 Jun 2024 11:39:43 -0700 (PDT)
MIME-Version: 1.0
References: <4D8663F2-82C6-45D5-879C-7282F9587884@hp.com> <12C5EF2E-27DF-4C55-9352-5858DD84D60E@msweet.org> <541C3F9B-0DB5-4880-87BF-9BB1DBB81F46@hp.com> <826064B5-8388-4292-81A1-72059D2426A0@msweet.org> <FFDDDC98-97F3-4289-9226-1ECF6D52DB74@xerox.com> <407DB673-6CE6-4981-8E6E-A9C59C86CF72@hp.com> <688BF75C-0863-4ECC-A1A0-75F77F91A8BD@xerox.com> <689B72E4-A748-4921-BAD5-920081A836B7@xerox.com> <MW4PR15MB4508D9E9EEB291655B3F82C194C02@MW4PR15MB4508.namprd15.prod.outlook.com>
In-Reply-To: <MW4PR15MB4508D9E9EEB291655B3F82C194C02@MW4PR15MB4508.namprd15.prod.outlook.com>
Date: Wed, 12 Jun 2024 20:39:28 +0200
Message-ID: <CABFDNXR08TpCDdoZ9sHYrGjfp=ZiA0bXZh4X9n1v2mOBY55RMw@mail.gmail.com>
To: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Subject: Re: [IPP] What value do IPP Printers provide for "printer-name"?
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Anton Thomasson via ipp <ipp@pwg.org>
Reply-To: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Cc: Anton Thomasson <antonthomasson@gmail.com>
Content-Type: multipart/mixed; boundary="===============6757708003862481626=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Hi

I too expect something human-useful here.
Looking through my user-supplied attribute dumps, i see most printers doing
something decent; mostly model-based.

Some interesting outliers:

   - Xerox WorkCentre 6515: "192.168.1.74"
   - Various Brother printers: "" (empty string)
   - Brother VC-500W: "print" (from /ipp/print presumably)
   - EPSON SC-P900: "ipp/print"

Br,
Anton

Den ons 12 juni 2024 kl 12:38 skrev Arun Holla via ipp <ipp@pwg.org>:

> Hi Smith,
>
>
>
> For the Fiery Digital Front End servers, here are the IPP attribute values
> being populated:
>
>
>
>    - printer-name à ‘hostname’
>    - printer-make-and-model à Specific printer manufacturer and model
>    name, and is fixed.
>    - printer-dns-sd-name à Bonjour Service Name concatenated with the
>    last 3 octets of the Mac address (similar to Xerox). Default is the printer
>    manufacturer and model name concatenated with the 3 octets of Mac address.
>    This helps to keep it unique as it is used during the printer discovery.
>    This value changes when the Bonjour service name is changed by the user.
>
>
>
> Thanks,
>
> -Arun-
>
> *From:* ipp <ipp-bounces@pwg.org> *On Behalf Of *Rizzo, Christopher via
> ipp
> *Sent:* Wednesday, June 12, 2024 4:44 AM
> *To:* Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com>
> *Cc:* Rizzo, Christopher <christopher.rizzo@xerox.com>; PWG IPP WG
> Reflector <ipp@pwg.org>
> *Subject:* Re: [IPP] What value do IPP Printers provide for
> "printer-name"?
>
>
>
> *[EXTERNAL] *
>
> Of course - I just thought of what happens when there is a name conflict
> with another device on the network, and tested it.
>
>
>
> The conflict caused the registered name via MDNS to have "(2)" appended to
> it, but neither printer-name nor printer-dns-sd-name were updated to match.
>
>
>
> So now I'm wondering if that is a bug. Is that a bug?  I think that is as
> I read PWG 5100.13 - printer-dns-sd-name at a minumum should have changed
> to match the MDNS (updated) registered name.
>
>
>
> Chris
>
>
>
> *Christopher Rizzo*
>
> *Engineer II, Software Engineering*
>
> *Design & Development Engineering*
>
>
>
> [image: signature_965322133] <http://www.xerox.com/>
>
>
>
> Xerox Corporation
>
> Virtual Office Employee
>
> 26600 SW Parkway Ave
>
> Wilsonville, OR 97070
>
>
>
> [image: signature_444176381] <https://www.linkedin.com/company/xerox/>   [image:
> signature_1244739495] <https://www.youtube.com/user/XeroxCorp>   [image:
> signature_4095302439] <https://twitter.com/Xerox>   [image:
> signature_510884951] <https://www.instagram.com/xerox/>   [image:
> signature_496444296] <https://www.facebook.com/XeroxCorp>
>
>
>
>
>
> *From: *Christopher Rizzo <christopher.rizzo@xerox.com>
> *Date: *Tuesday, June 11, 2024 at 4:03 PM
> *To: *Kennedy Smith <smith.kennedy@hp.com>
> *Cc: *PWG Workgroup <ipp@pwg.org>, Michael Sweet <msweet@msweet.org>
> *Subject: *Re: [IPP] What value do IPP Printers provide for
> "printer-name"?
>
>
>
> Yes, both are updated together.
>
>
>
> And they are independent of the hostname
>
>
>
> Chris
>
>
>
> *Christopher Rizzo*
>
> *Engineer II, Software Engineering*
>
> *Design & Development Engineering*
>
>
>
> [image: signature_2133543743] <http://www.xerox.com/>
>
>
>
> Xerox Corporation
>
> Virtual Office Employee
>
> 26600 SW Parkway Ave
>
> Wilsonville, OR 97070
>
>
>
> [image: signature_379100592] <https://www.linkedin.com/company/xerox/>   [image:
> signature_3069953614] <https://www.youtube.com/user/XeroxCorp>   [image:
> signature_2858899317] <https://twitter.com/Xerox>   [image:
> signature_3573846891] <https://www.instagram.com/xerox/>   [image:
> signature_2872972201] <https://www.facebook.com/XeroxCorp>
>
>
>
>
>
> *From: *Kennedy Smith <smith.kennedy@hp.com>
> *Date: *Tuesday, June 11, 2024 at 3:49 PM
> *To: *Christopher Rizzo <Christopher.Rizzo@xerox.com>
> *Cc: *PWG Workgroup <ipp@pwg.org>, Michael Sweet <msweet@msweet.org>
> *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 <
> Christopher.Rizzo@xerox.com> 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/>
>
> Xerox Corporation
> Virtual Office Employee
> 26600 SW Parkway Ave
> Wilsonville, OR 97070
>
> <https://www.linkedin.com/company/xerox/> <
> https://www.youtube.com/user/XeroxCorp> <https://twitter.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" <ipp-bounces@pwg.org
> <mailto:ipp-bounces@pwg.org> on behalf of ipp@pwg.org <mailto:ipp@pwg.org
> <ipp@pwg.org>>> wrote:
>
>
> Smith,
>
>
> > On Jun 11, 2024, at 3:22 PM, Kennedy, Smith (Wireless & IPP Standards) <smith.kennedy@hp.com
> <mailto:smith.kennedy@hp.com>> 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
> ipp@pwg.org
> https://www.pwg.org/mailman/listinfo/ipp
>
_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp