[IPP] RFC: Job Accounting and Managed Printing Solutions

Michael Sweet via ipp <ipp@pwg.org> Fri, 27 September 2019 15:07 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 AC401120869 for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 27 Sep 2019 08:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ML3s_IYvFGm for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 27 Sep 2019 08:07:30 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 0805D120855 for <ipp-archive2@ietf.org>; Fri, 27 Sep 2019 08:07:22 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 67774C3E2; Fri, 27 Sep 2019 15:07:19 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id C43B34891; Fri, 27 Sep 2019 15:07:15 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id D61134891; Fri, 27 Sep 2019 15:07:14 +0000 (UTC)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTP id 54E392652; Fri, 27 Sep 2019 15:07:14 +0000 (UTC)
Received: from imacpro.lan (67-204-236-184.eastlink.ca [67.204.236.184]) by mail.msweet.org (Postfix) with ESMTPSA id 7A4A580439; Fri, 27 Sep 2019 15:07:13 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 27 Sep 2019 11:07:11 -0400
To: PWG Announcements <pwg-announce@pwg.org>
Message-Id: <EA527945-FE54-433C-82CF-E6E71EC44665@msweet.org>
X-Mailer: Apple Mail (2.3445.104.11)
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: [IPP] RFC: Job Accounting and Managed Printing Solutions
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
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: Michael Sweet <msweet@msweet.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

All,

The IPP workgroup is working on a Best Practice document on job accounting and managed printing solutions and would like your help in identifying key functionality and data elements needed to support those solutions.  The ultimate goal is to determine any gaps and have specifications and best practices in place to better support job accounting and managed printing through IPP, rather than depending on vendor MIBs and network protocols, which will allow all types of IPP clients to utilize these solutions seamlessly.

To this end, I am asking that any member that has a job accounting or managed printing solution to send me a list of data elements/attributes that your solution(s) depend on along with any special requirements or use cases that are addressed.  Of particular importance is information that you currently gather outside of IPP since we want IPP to provide everything that is needed.  All solution-specific information can be kept confidential if necessary - I will be using it to identify any deficiencies that need to be addressed in IPP or common use cases that should be highlighted in our Best Practice document.

Also, I would be very interested to know whether your solutions use IPP or some other protocol(s), and the reasons for doing so - again so that we can make sure that IPP can satisfy as many printing requirements and use cases as possible.

We plan to next discuss this topic at the November 2019 Face-to-Face, and your participation in this effort would be greatly appreciated!  Please send all information to "msweet@msweet.org" and I will summarize what I receive at the F2F.

Thank you!

________________________
Michael Sweet



_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp