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

Willem Groenewald via ipp <ipp@pwg.org> Sun, 05 January 2020 23:36 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 04A4612009C for <ietfarch-ipp-archive@ietfa.amsl.com>; Sun, 5 Jan 2020 15:36:43 -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=papercut-com.20150623.gappssmtp.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 HUhNIsDP4meL for <ietfarch-ipp-archive@ietfa.amsl.com>; Sun, 5 Jan 2020 15:36:41 -0800 (PST)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 07B0E120026 for <ipp-archive2@ietf.org>; Sun, 5 Jan 2020 15:36:41 -0800 (PST)
Received: by mail.pwg.org (Postfix, from userid 1002) id 8D6D83BC7; Sun, 5 Jan 2020 23:36:40 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id A0EC71158; Sun, 5 Jan 2020 23:36:36 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 654F726AA; Sun, 5 Jan 2020 23:36:35 +0000 (UTC)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) by mail.pwg.org (Postfix) with ESMTPS id 4BD861158 for <ipp@pwg.org>; Sun, 5 Jan 2020 23:36:34 +0000 (UTC)
Received: by mail-io1-xd2c.google.com with SMTP id b10so46856565iof.11 for <ipp@pwg.org>; Sun, 05 Jan 2020 15:36:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=papercut-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DzUqTKrkiUvN/nXX6Gw8K8sC1b+Ew/MR7jtMn+bPU08=; b=cEymdJMp8smdZhlNTxjvflsQ3rZ0DI7hK/xzb7aVKRRvb/6Z3GCrHfTasPy2gQAclP MGJHnh5k67s3eoUNiG/DH0sPghb3JDOLpNF51yoMNogSUxgGzKhgR+pccbMAskZ2C85L Rq1LvLtLM/s63CidBzUVYgeVu9Wrps47ppAPmVPSpANe7QLpniKGOVb7Tw6F9D6PcD8X HXytSLHV8wrQ9fUrjleljrxwGF7XwzpAcP1B18pXc2u6QGAD/tNB2o5flPLX9UsWNZh0 FhfuDIBqz53JkiLpnw6Nh03qwUyBbLK+pNOq1jOyBILKUV7MykuwaZG7qwMVm2Z0SuJn z64w==
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=DzUqTKrkiUvN/nXX6Gw8K8sC1b+Ew/MR7jtMn+bPU08=; b=daVtWVwFcKh7IU8RNuz5oA+H9bxd5V1vUUFDOC/10KZUtlO1DQW+S0J1Y4Le6xIY2A XZC252aHRBR8Qb2TXyMkoHFLrzZNWwIvpd31o3P+pPUSfglfD2ZkMhS4P2cQAOwXfY1u xclzwRF2vwe86VUylCabyza4UOz7nncBnq3RriJ7U+kZ75x17KX8GYUOxyL2nzPqGeBz SPSgzHMlKI+2YQ9kbss5F6yI7XaeJIGvEDSZMwScwbrmV1xCkYLC2qzNthavcJDx32Fg AbXK95NCDlJaFJXP0RxpOOlTvWT9f01sQAOIYLdpWTFZDOlTqkQWAH+L2qRYHcnSevZv RDrA==
X-Gm-Message-State: APjAAAU6uBz2eIMphyAfHpK8Be6M3309kblq6VcLPhXtgFymv/GlRBfi qRQV4duUGlClSP65bekWZnlKA9xE3tAa3+TZovhMKA==
X-Google-Smtp-Source: APXvYqyzFltn/M+uCM4WnAeMqvcgO4r86EnRMDt8GXUlS/rJKJROJv3yrIMj08H/DlNuK+6tCcx2XCnZn0UZvC4FD48=
X-Received: by 2002:a5d:8d10:: with SMTP id p16mr62015424ioj.21.1578267393197; Sun, 05 Jan 2020 15:36:33 -0800 (PST)
MIME-Version: 1.0
References: <7FAD4B6B-056C-4025-91C2-E7FECEA2D1B6@hp.com>
In-Reply-To: <7FAD4B6B-056C-4025-91C2-E7FECEA2D1B6@hp.com>
Date: Mon, 06 Jan 2020 10:36:22 +1100
Message-ID: <CAHnR74KtGhF1fTA3xvMrRzuzy7y=8ctDazi4Y5Sj7_F5FoS51g@mail.gmail.com>
To: "Kennedy, Smith (Wireless & IPP Standards)" <smith.kennedy@hp.com>, Chris Dance <chris.dance@papercut.com>, Behzad Mozaffari <behzad.mozaffari@papercut.com>
Cc: PWG IPP WG Reflector <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: Willem Groenewald via ipp <ipp@pwg.org>
Reply-To: Willem Groenewald <willem.groenewald@papercut.com>
Content-Type: multipart/mixed; boundary="===============7240797272370339301=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Hi Smith

Apologies for the delay, just returned from leave.

Here are a few comments on the naming (probably more "thoughts" to spark
some thinking):

1) The use-cases and flows around "Password Protected Job" and "User
Credential Protected Job" are very similar.  The names should be related.
 e.g. both are "release" and path "protect" the job.  It's the means of
protection that are changing.  Hence we'd recommend having very similar
names.  If you're keen to add the word "release", we'd suggest making sure
this also exists on the password protected job too.

2) We've taken a look at the draft of the Enterprise Printing Extensions
v2.0 w.r.t these mentioned features, and would love an opportunity to dive
a little deeper around security. Some immediate thoughts from a quick look,
that may or may not have been considerer, are:

   - The use of hashing methods that are no longer considered "secure".
   Would it make sense for a standard released in 2020 include these as
   options?
   - Requiring these features to be available over TLS connections
   - Have downgrade (or reply) attacks been considered?

Cheers,

Chris & Bez in the PaperCut Dev Team (plus now Willem)



On Thu, 19 Dec 2019 at 04:12, 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
>
> Any feedback on any of these labels? Thanks for any help!
>
> Smith
>
> /**
>     Smith Kennedy
>     HP Inc.
> */
>
> _______________________________________________
> ipp mailing list
> ipp@pwg.org
> https://www.pwg.org/mailman/listinfo/ipp
>


-- 
*Willem Groenewald*
Product Owner
<http://www.papercut.com/>
mob:  +61 439 584 646
web:    www.papercut.com

<https://twitter.com/papercutdev>   <https://facebook.com/papercutsoftware>
   <http://www.linkedin.com/company/papercut-software>
<https://google.com/+PaperCutSoftware>
<https://youtube.com/papercutsoftware>

Please consider the environment before printing this email... or install
PaperCut and let it do the considering for you!
_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp