IETF Logo Mail Archive

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

Michael Sweet via ipp <ipp@pwg.org> Sat, 22 June 2024 17:07 UTC

Received: by ietfa.amsl.com (Postfix) id 7C5EFC14F75F; Sat, 22 Jun 2024 10:07:01 -0700 (PDT)
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2B1C14F704 for <ietfarch-ipp-archive@ietfa.amsl.com>; Sat, 22 Jun 2024 10:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.107
X-Spam-Level:
X-Spam-Status: No, score=-8.107 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, MAILING_LIST_MULTI=-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="M9VPVvDm"; dkim=pass (1024-bit key) header.d=pwg.org header.b="YpHSgvuf"; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=msweet.org header.b="rYTr8JEy"
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 Arw-AshZw0GI for <ietfarch-ipp-archive@ietfa.amsl.com>; Sat, 22 Jun 2024 10:06:57 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 284C5C14F739 for <ipp-archive2@ietf.org>; Sat, 22 Jun 2024 10:06:57 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 9E61E8823; Sat, 22 Jun 2024 17:06:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 9E61E8823
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1719076015; bh=XEUmpOl0UGJ3x/CJXiLZGpcA6TQl+2odq1/TGM3Hubk=; h=In-Reply-To:Date:References:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=M9VPVvDmSzfhNkDrXAqNVpFGSgTZkC0iSl+N5IWYFFSXQQdhkeN4VNvau/uGnbJnD 2bh2BeRCH0uryvfG23E/kTG3EdYBWUZg8Mh4G+lJOGJs2DSGp5rFkZScJ53PeFaWM8 a9KT6MNCJmVdJ6+PQTq8rCV+o8qFtYnFzEj5oYrY=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 77AA121E2; Sat, 22 Jun 2024 17:06:54 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 77AA121E2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1719076014; bh=XEUmpOl0UGJ3x/CJXiLZGpcA6TQl+2odq1/TGM3Hubk=; h=In-Reply-To:Date:References:To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=YpHSgvufVrDWYhXel9K3mmJN0UyGbfOToXCOrJTAo8khzC6Mq40oMr79NcA/hdqjM M4+kiofzzFMz5EXXcjG9dSBUC8hNefzhESBD2fEHPX+LUED+hfkJBTPg4UK1gmoQOj Rsabq+JzqHcAIHG+gRV4HIURNt1y2cxkZF6U1BfI=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 734933A77; Sat, 22 Jun 2024 17:06:53 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 734933A77
Authentication-Results: mail.pwg.org; dkim=pass (1024-bit key) header.d=msweet.org header.i=@msweet.org header.b="rYTr8JEy"
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTPS id 9EC7C3A39 for <ipp@pwg.org>; Sat, 22 Jun 2024 17:06:52 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 9EC7C3A39
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.msweet.org (Postfix) with ESMTPSA id 0B75380445; Sat, 22 Jun 2024 17:06:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 0B75380445
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1719076011; bh=gJ2vrnOD+vZM5quTXeNctStcd0FQWnh64sMg7kwTVA8=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=rYTr8JEyOhfAyivz26TY/St3+NAsgkDSAGCExxlE3Zx6SEtirvziI02aR1tBJSEZW /Ue3Z9FTmk5c9G22GaUPebKoxGxSAKDI+9ffV772N+TCl6o1cMPyswj6XkI1fj6mIZ GptGkOFwLAWMrtMLN9jNKHoJTV/7JiFs2XoqBdKc=
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.11\))
In-Reply-To: <BY1PR21MB38956C58002A0468533359D1A8C92@BY1PR21MB3895.namprd21.prod.outlook.com>
Date: Sat, 22 Jun 2024 13:06:39 -0400
Message-Id: <0FD9B6F3-B342-4741-904C-9BFB0EEB8A68@msweet.org>
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> <CABFDNXR08TpCDdoZ9sHYrGjfp=ZiA0bXZh4X9n1v2mOBY55RMw@mail.gmail.com> <BYAPR16MB395948F91DF424DE5585C17BFCC12@BYAPR16MB3959.namprd16.prod.outlook.com> <BYAPR19MB2630DDF0E5A6D604A8F86513AFC82@BYAPR19MB2630.namprd19.prod.outlook.com> <62E5E595-9A69-4B00-9841-58CD94998F7A@msweet.org> <AA205B01-DE0C-4193-9965-2011AFB7A04E@hp.com> <BY1PR21MB38956C58002A0468533359D1A8C92@BY1PR21MB3895.namprd21.prod.outlook.com>
To: PWG IPP Workgroup <ipp@pwg.org>
X-Mailer: Apple Mail (2.3776.700.11)
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: Michael Sweet via ipp <ipp@pwg.org>
Reply-To: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp@pwg.org>
Cc: Michael Sweet <msweet@msweet.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Michael,

> On Jun 21, 2024, at 5:06 PM, Michael Ziller via ipp <ipp@pwg.org> 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
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

v2.39.1 | Report a Bug | By Email | System Status