Re: [IPP] IPP Enterprise Printing Extensions: Feature Names and Job Types

Ira McDonald via ipp <ipp@pwg.org> Wed, 18 December 2019 19:37 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 E9A8D12088C for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 11:37:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 vQOdD4VC9mBW for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 11:37:25 -0800 (PST)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 7E77712023E for <ipp-archive2@ietf.org>; Wed, 18 Dec 2019 11:37:25 -0800 (PST)
Received: by mail.pwg.org (Postfix, from userid 1002) id 3DB60C218; Wed, 18 Dec 2019 19:37:25 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 7FEE81502; Wed, 18 Dec 2019 19:37:20 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 14FBB2635; Wed, 18 Dec 2019 19:37:19 +0000 (UTC)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) by mail.pwg.org (Postfix) with ESMTPS id 347C42635 for <ipp@pwg.org>; Wed, 18 Dec 2019 19:37:18 +0000 (UTC)
Received: by mail-vs1-xe2b.google.com with SMTP id x18so2181683vsq.4 for <ipp@pwg.org>; Wed, 18 Dec 2019 11:37:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y4zQTuQO0aYPUUXZBQ793VxLHa+FB2PKeZMwqrEYYFA=; b=h95B3cVQ0TmW2QElh2+wspqzqWgMXh2dcEzkPx4awhTi793oZTq4ViTdnEgZRtEEPT vLQCHyOw3Oam4su/+o8cCOng25ze+U7P/X9Z57oKpSKNG1j1k2y+mn9clccsogwONMDw qrz6xD96YcDWmvoYp9zGYPcc+xx2gMJxDtr1V8ya8E6JAgVorakyumzZrkBQzuosNe+d l6gmThjx6ENTfvB6SjV95JiVE0Dv8qhK5Jz2ODPOy9X8KvA/qmuxc7pBHkIFwyTLOT6Q 27+vftlc41heQySrt8nxXMg0zLePqpxfNfKZ/4RfLQUMSXDQQZ5AdizoUcjc10ZzNUkV ITpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y4zQTuQO0aYPUUXZBQ793VxLHa+FB2PKeZMwqrEYYFA=; b=BeQsyaNWcze+ESbz6hSIu4Z3pduT9K2nQFtCB+IjkUSfKc8hr+Ebbp+rJVGZuB3DRz E9kExwb68oL4BcP3Ux65kokVzcF9paL4idZsoaXO1Qb19sc5r5cx5bEPvF1rvTGmoyNm fibcpCCIFSm9JQivfCiQO11OKp3nR/yHzw00dmnF/0OA3Nv33xhvFGZreDmInZjBXHmC jHdlJFATMbO78sJQ3A2wddyxxOpYq44BeDKwnH3VdOntjVDWSkZRdIXHhsEqJ9GiXa3O ed8y2gW6rAn4ily9scIOVG0I1XVd9CB69dQKrLLa/qmBbUEyuGE1+bcr3xOyWgzf1oD6 ewoQ==
X-Gm-Message-State: APjAAAUTWcgqb3KWB+Uq1y7o+z+ZedGStI1wGIz+Nmw3DXOZ7//Jht1u cJrb/uTds768Y0+JaN3httrXQzYUNOEWAcYTXUk=
X-Google-Smtp-Source: APXvYqzJHWqoZi/hMFUS/+2prep2Nry7Iw/i02tzb7OLkDBkw7vmMdXsZHvYstl9zFT5l28TUVVCZmhjOuqc5jQHJaQ=
X-Received: by 2002:a67:fbcf:: with SMTP id o15mr2715259vsr.13.1576697837119; Wed, 18 Dec 2019 11:37:17 -0800 (PST)
MIME-Version: 1.0
References: <7FAD4B6B-056C-4025-91C2-E7FECEA2D1B6@hp.com> <85F58E4B-9661-4402-81E9-B54C328C03BB@msweet.org>
In-Reply-To: <85F58E4B-9661-4402-81E9-B54C328C03BB@msweet.org>
Date: Wed, 18 Dec 2019 14:37:03 -0500
Message-ID: <CAN40gSse9utBV8QLKd3ADhi0ScxR_Z9JGkNi3KhJR5X1Cub7Kg@mail.gmail.com>
To: Michael Sweet <msweet@msweet.org>, Ira McDonald <blueroofmusic@gmail.com>
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] IPP Enterprise Printing Extensions: Feature Names and Job Types
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: Ira McDonald via ipp <ipp@pwg.org>
Reply-To: Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/mixed; boundary="===============3676621316671660136=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Hi,

Two comments:

(1) I definitely prefer "Release Printing" (and not saying anything about
Authentication in the title).

(2) The actual keyword names of all these features of course have to be
all lowercase and use hyphens (but not underscores or spaces).

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Co-Chair - TCG Metadata Access Protocol SG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
PO Box 221  Grand Marais, MI 49839  906-494-2434



On Wed, Dec 18, 2019 at 1:53 PM Michael Sweet via ipp <ipp@pwg.org> wrote:

> Smith,
>
> Most of these look fine to me.  One comment at the end...
>
> > On Dec 18, 2019, at 12:12 PM, Kennedy, Smith (Wireless & IPP Standards)
> via ipp <ipp@pwg.org> wrote:
> >
> > Hi there,
> >
> > I'm in the process of producing a new draft of IPP Enterprise Printing
> Extensions v2.0 (EPX) and I'm trying to nail down the "feature names" and
> "job types" for the several features defined therein.
> >
> > What I have thus far is this:
> >
> > Job Password
> >       • Feature: Password Job Protection
> >       • Job Type: Password Protected Job
> >       • Use Case: Protecting a Job with a Password
> >
> > Job Storage
> >       • Feature: Job Storage
> >       • Job Type: Stored Job
> >       • Use Case: Storing a Job for Later Reprinting, Reprinting a
> Stored Job
> >
> > Proof Print
> >       • Feature: Proof Print
> >       • Job Type: Proof Job
> >       • Use Case: Proof Printing
> >
> > Authenticated Release
> >       • Feature: Authenticated Release? Credential Job Protection?
> >       • Job Type: User Credential Protected Job?
> >       • Use Case: Protecting a Job with User Authentication Credentials
>
> I've been calling this Release Printing in the Job Accounting document -
> the kind of authentication varies widely but functionally it is Print then
> Release at the printer.  Some vendors call their implementation Follow Me
> or Pull Printing, although those have the additional wrinkle of releasing
> from any of several output devices, vs. from a single output device
> associated with the Printer.
>
> I've avoided using Follow Me since it is a trademarked term.  Pull
> Printing seems to be safe, and I'd have no objection to using it here (even
> for a single output device).  Whatever we settle on, I'll update the Job
> Accounting document accordingly...
>
> ________________________
> 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