IETF Logo Mail Archive

Re: [IPP] IppFaxOut specification missing mDNS resource path information

Michael Sweet via ipp <ipp@pwg.org> Tue, 13 August 2024 21:48 UTC

Received: by ietfa.amsl.com (Postfix) id 660E0C1CAF28; Tue, 13 Aug 2024 14:48:16 -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 654D3C1CAE8E for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 13 Aug 2024 14:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.106
X-Spam-Level:
X-Spam-Status: No, score=-3.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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="nC/0MIuD"; dkim=pass (1024-bit key) header.d=pwg.org header.b="m65rLDmv"; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=msweet.org header.b="mxXYdZi2"
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 EyeR2JKdfCyI for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 13 Aug 2024 14:48:12 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [172.104.19.21]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6DFC1CAE91 for <ipp-archive2@ietf.org>; Tue, 13 Aug 2024 14:48:11 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 18B4E4895; Tue, 13 Aug 2024 21:48:11 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 18B4E4895
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1723585691; bh=V5jhNmohD9g7T7TOEtfhw392f5krijh8CPgBq/WPlLM=; 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=nC/0MIuDdEbpb8sBYn6VaqhSezLCKzvedcYO+AcTY4A7s2wO1W4ziJqpK0GQ6pRNT iCu4/xIPAjIZc4H/kZUWXsliiZaG50GYfqRM/jt2brZR94kTHdT6f06Lrgb5M4xTVN n7k+8Pv+ovj9g2oUcA6AeTBhj5I9itF9fxYojrQU=
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id E2C70344E; Tue, 13 Aug 2024 21:48:07 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org E2C70344E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pwg.org; s=default; t=1723585687; bh=V5jhNmohD9g7T7TOEtfhw392f5krijh8CPgBq/WPlLM=; 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=m65rLDmvqGjhqlQ3ThKMDzH6xgnANEdzdbPaMXoT7rqPn6CNyuCNtxtKJYOek25km jcX4dAZsgaGWYZIutJ+M6TkzC9EY8VQ+8Br049IdcM0YC9iKqyjr9AxKvh440vQtF3 klMqj/AuS19zxsbK+a8UJAG3djjP7k1XCNDHsVBM=
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 025473A4F; Tue, 13 Aug 2024 21:48:06 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org 025473A4F
Authentication-Results: mail.pwg.org; dkim=pass (1024-bit key) header.d=msweet.org header.i=@msweet.org header.b="mxXYdZi2"
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTPS id E4384344E for <ipp@pwg.org>; Tue, 13 Aug 2024 21:48:03 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.pwg.org E4384344E
Received: from smtpclient.apple (unknown [129.222.136.142]) (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 30D94803DC; Tue, 13 Aug 2024 21:48:02 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 30D94803DC
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1723585682; bh=AYFUyo9nmVmqxvRle5smt3LHgqU5s0pU8qvp8RVBf3M=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=mxXYdZi2W1MbNfPOneOzAmSko8rD7EE5w25fhI38Cf3pXbYSpQjoSFGCXf+D48skA 7UUUiLEgz+B8Nn3y1kjFO3ypZ+UA4AfUl75N+c6xkdBYCM6hBzJuNNHct7AqC24ubF X4VvA2RfRbKnLluiHYhycUxlt4EMFu5Xox208o20=
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3816.100.2.1.1\))
In-Reply-To: <DM4PR21MB341909E054BC1A26B293D2A5A8862@DM4PR21MB3419.namprd21.prod.outlook.com>
Date: Tue, 13 Aug 2024 17:47:50 -0400
Message-Id: <22347AE3-A8CF-4AB4-BBD6-C94B9887D901@msweet.org>
References: <DM4PR21MB341909E054BC1A26B293D2A5A8862@DM4PR21MB3419.namprd21.prod.outlook.com>
To: PWG IPP Workgroup <ipp@pwg.org>
X-Mailer: Apple Mail (2.3816.100.2.1.1)
Subject: Re: [IPP] IppFaxOut specification missing mDNS resource path information
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 Aug 13, 2024, at 2:19 PM, Michael Ziller via ipp <ipp@pwg.org> wrote:
> 
> The IppFaxOut spec Microsoft Word - cs-ippfaxout10-20140618-5100.15.docx (pwg.org) makes no mention of mDNS discovery for fax out support. Is the intent that all printers will use a resource path of “/ipp/faxout” or is the spec missing mention of the “rfo=/ipp/faxout” mDNS TXT record for determining the IppFaxOut resource path to use?

The FaxOut spec was written before the TXT record variable was defined/used, and then for AirPrint. I've filed an errata issue against 5100.15 to add a DNS-SD section:

    https://www.pwg.org/dynamo/issues.php?U131

FWIW, except for print servers (where there would be multiple "queues") the resource path is expected to be "/ipp/faxout".  From 5100.15:

4.1.5 Printer URIs

Each instance of an IPP FaxOut service is identified by a URI. The path component of an IPP FaxOut URI MUST be “/ipp/faxout” for the only (or default) instance of the service on an Imaging Device and “/ipp/faxout/instance-name” for each additional, non-default instance on the Imaging Device.

Thanks for noticing this and speaking up!

________________________
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