Re: [IPP] RFC: max-page-ranges-supported (integer(1:MAX)) Printer Description Attribute
"Kennedy, Smith \(Wireless & Standards Architect\) via ipp" <ipp@pwg.org> Thu, 11 July 2019 16:11 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 859B21203AA for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 11 Jul 2019 09:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=hp.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 27nySOaPL1vK for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 11 Jul 2019 09:11:56 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id A4C0A120294 for <ipp-archive2@ietf.org>; Thu, 11 Jul 2019 09:11:40 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 17E06C05C; Thu, 11 Jul 2019 16:11:40 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 07EF64891; Thu, 11 Jul 2019 16:11:36 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 5AAB96178; Thu, 11 Jul 2019 16:11:35 +0000 (UTC)
Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by mail.pwg.org (Postfix) with ESMTPS id DB2632459 for <ipp@pwg.org>; Thu, 11 Jul 2019 16:11:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1562861492; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DtlRi6ksJNq1m9ExAinUnFWR7IXAPjw2dx3gvlKfEYk=; b=WRL0izpgoIFqSIvFthJK+xRktzwrgUGRzEEROeGvYZNXXY2c1aKC0FVyRUOPrYFbl2MfdB dLUA6tJzkmmnjFrToc2Ul97ejI6kwr9SacY86HLS8Kf+WBX17kpWszaaQOgaYvKN22V8Dc I5/MifR3Y8ZcHxbhooUoZEoC8Xh+DtY=
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01lp2057.outbound.protection.outlook.com [104.47.32.57]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-280-hJk0T0j7PGet4j-Phgf3RA-1; Thu, 11 Jul 2019 12:11:27 -0400
X-MC-Unique: hJk0T0j7PGet4j-Phgf3RA-1
Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0456.NAMPRD84.PROD.OUTLOOK.COM (10.169.15.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.17; Thu, 11 Jul 2019 16:11:25 +0000
Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::74c3:1ae4:da68:e2aa]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::74c3:1ae4:da68:e2aa%10]) with mapi id 15.20.2052.020; Thu, 11 Jul 2019 16:11:25 +0000
To: Michael Sweet <msweet@msweet.org>
Thread-Topic: [IPP] RFC: max-page-ranges-supported (integer(1:MAX)) Printer Description Attribute
Thread-Index: AQHVOABfLEB91y5LNEixkmKYs7MDGqbFlpEA
Date: Thu, 11 Jul 2019 16:11:25 +0000
Message-ID: <A86BBE93-9D2A-4611-BDD6-8A14DA258CCE@hp.com>
References: <8B3B1E64-8BB8-49C4-B96A-240540C73E5D@msweet.org>
In-Reply-To: <8B3B1E64-8BB8-49C4-B96A-240540C73E5D@msweet.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=smith.kennedy@hp.com;
x-originating-ip: [174.27.46.49]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0e79a089-a76c-442a-dd16-08d7061a6c9e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(49563074)(7193020); SRVR:CS1PR8401MB0456;
x-ms-traffictypediagnostic: CS1PR8401MB0456:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CS1PR8401MB04568377B5108F9EA8854A3A9EF30@CS1PR8401MB0456.NAMPRD84.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0095BCF226
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(396003)(376002)(346002)(136003)(39860400002)(199004)(189003)(6602003)(3846002)(6116002)(25786009)(66946007)(66446008)(64756008)(99936001)(36756003)(2906002)(71190400001)(71200400001)(91956017)(66556008)(4326008)(14444005)(966005)(76116006)(66616009)(256004)(86362001)(478600001)(6916009)(54896002)(476003)(26005)(81166006)(8676002)(68736007)(81156014)(66066001)(229853002)(6306002)(33656002)(236005)(6512007)(6486002)(7736002)(53546011)(6246003)(6436002)(53936002)(76176011)(316002)(99286004)(486006)(5660300002)(66476007)(446003)(11346002)(102836004)(606006)(8936002)(14454004)(186003)(2616005)(6506007)(21314003); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0456; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: JPcMjqbiA5qG6xR/rr2b1gXMGgdpDXcpEyzTQzVGVkhYuNXO2YkIJtUt3N5wV6xM4vUcJNiINAhZRK3PnwXbYxP8uc80ENk5OIE0d0e7Sb9+FNkR1owKdv0LZtQ2rL8ZFj0o7or8142Z+LQfcR4vD2PugoPG8rTwkRSRdaitoVur6QCbp9gOAAYYrOfK0ivNXDldDmDZq4AaWIwyBQ/8Qk3qWgNE35DhnponpMmQz8YkGDZuuZmEOM7LjMF1GhQ4loWr68NOSO99uB1rEXRodgw8I2ZFE/AVnCNgpiFoWAsKl5oPg7SEortrIhXA8zJRMOaUF+34MVyQSrZlQS4BiEP9jv67nqDnxFfVIScqfStggELbACKLZQIjVX2hTFl/GYhda9arOPAMTryw2eMfeXziyFDuPWQm5HxI53hnroA=
MIME-Version: 1.0
X-OriginatorOrg: hp.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0e79a089-a76c-442a-dd16-08d7061a6c9e
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2019 16:11:25.5159 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: smith.kennedy@hp.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CS1PR8401MB0456
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] RFC: max-page-ranges-supported (integer(1:MAX)) Printer Description Attribute
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: "Kennedy, Smith (Wireless & Standards Architect) via ipp" <ipp@pwg.org>
Reply-To: "Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>
Content-Type: multipart/mixed; boundary="===============0544884094890828422=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
+1 !
Smith
/**
Smith Kennedy
HP Inc.
*/
> On Jul 11, 2019, at 9:49 AM, Michael Sweet via ipp <ipp@pwg.org> wrote:
>
> All,
>
> A recent issue on the Javascript IPP project (https://github.com/williamkapke/ipp/issues/72 <https://protect-us.mimecast.com/s/QAYgC82A5Ah69A6zBI233N3?domain=github.com>) highlights an issue with the "page-ranges (1setOf rangeOfInteger)" Job Template attribute, namely that a Client cannot discover how many ranges a printer supports. The existing "page-ranges-supported (boolean)" attribute only specifies whether the "page-ranges" Job Template attribute is supported and not the maximum number of values a Printer supports. Moreover, existing Printers seem to ignore extra values without reporting this in the unsupported attributes group of the Create-Job/Print-Job/Print-URI/Validate-Job response, so from the perspective of the Client nothing has gone wrong.
>
> For other attributes we have a "max-xxx" Printer Description attribute that tells the Client how many values can be specified, e.g., "max-stitching-locations-supported" and "max-materials-col-supported". I therefore propose to register a new "max-page-ranges-supported (integer(1:MAX))" Printer Description attribute that a Printer can return to specify the number of page ranges the Printer supports.
>
> Here is the registration template:
>
>
> Printer Description attributes: Reference
> ------------------------------ ---------
> max-page-ranges-supported (integer(1:MAX)) [IPP20190711]
>
>
> ________________________
> Michael Sweet
>
>
>
> _______________________________________________
> ipp mailing list
> ipp@pwg.org
> https://www.pwg.org/mailman/listinfo/ipp <https://protect-us.mimecast.com/s/N0TkC9rB5BFk86kMrcOeSX5?domain=pwg.org>
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] RFC: max-page-ranges-supported (integer(1:M… Michael Sweet via ipp
- Re: [IPP] RFC: max-page-ranges-supported (integer… Ira McDonald via ipp
- Re: [IPP] RFC: max-page-ranges-supported (integer… Kennedy, Smith (Wireless & Standards Architect) via ipp