[IPP] RFC: Obsolete "page-order-received" and related attributes
Michael Sweet via ipp <ipp@pwg.org> Thu, 09 May 2019 21:14 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 10A68120156 for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 9 May 2019 14:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 6DWoDCrIYcAp for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 9 May 2019 14:14:43 -0700 (PDT)
Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 3A223120132 for <ipp-archive2@ietf.org>; Thu, 9 May 2019 14:14:43 -0700 (PDT)
Received: by www.pwg.org (Postfix, from userid 1002) id 0249D3F51; Thu, 9 May 2019 21:14:40 +0000 (UTC)
Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 555CB269F; Thu, 9 May 2019 21:14:37 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by www.pwg.org (Postfix, from userid 1002) id 33A693BC2; Thu, 9 May 2019 21:14:36 +0000 (UTC)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) by www.pwg.org (Postfix) with ESMTPS id A13BD2688 for <ipp@pwg.org>; Thu, 9 May 2019 21:14:33 +0000 (UTC)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x49LDWLk033381 for <ipp@pwg.org>; Thu, 9 May 2019 14:14:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=bVBHOZxtKtFvfa9277MMNCGHAWFE8aNN/Ga+L3nxNXI=; b=daxRXLhoKE8Qi2b1+ZllJqI7XZ8WIbnVJist1MIL0NjCYhVDyQP7E+rOe0j3H/mTM6ok 7ftUnhe2Xru+FXDEhLVRc3s6eQiSAytuvIOUI2Vb81KL/bwzq8uQJkbFNQILF3gITPky xOGwa7K1l8IvKDPFJ9dPgNpeYtzn1xA6E0lB7eK3O352ZnBREkxDGaiBS4Bh9FKnkBeL NGd7eocGfxxtNDjJQpKTru5dBJ/FOZspW7+2y5OIA5Mj32jcsm3tfB+2BbO1OA9daxHC zUYiI+P1PomSdOkVu54+csBqwcr5St+0j+yjO88oTr5YIe+EJw15Tsn/jnKQVy6175XX Cw==
Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2s99qxkyt4-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ipp@pwg.org>; Thu, 09 May 2019 14:14:32 -0700
MIME-version: 1.0
Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PR900GPX9O849C0@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Thu, 09 May 2019 14:14:32 -0700 (PDT)
Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PR900J0096EVD00@nwk-mmpp-sz09.apple.com>; Thu, 09 May 2019 14:14:32 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8
X-Va-E-CD: 121900d7a981bee05928298470ea0916
X-Va-R-CD: b0b7de2b1a4661c7a223582b39dfae2e
X-Va-CD: 0
X-Va-ID: 67493395-cad0-43f0-9ae1-00dff21d6e43
X-V-A:
X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8
X-V-E-CD: 121900d7a981bee05928298470ea0916
X-V-R-CD: b0b7de2b1a4661c7a223582b39dfae2e
X-V-CD: 0
X-V-ID: 90bc0be0-bcf7-454e-a352-2a9029722150
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-05-09_02:,, signatures=0
Received: from [17.235.59.178] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PR9005QD9O5CI50@nwk-mmpp-sz09.apple.com>; Thu, 09 May 2019 14:14:32 -0700 (PDT)
Date: Thu, 09 May 2019 17:14:29 -0400
Message-id: <764A6D1B-2814-41B8-B2F5-9C6FBA82D5F5@apple.com>
To: PWG IPP Workgroup <ipp@pwg.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-09_02:, , signatures=0
Subject: [IPP] RFC: Obsolete "page-order-received" and related attributes
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@apple.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
All, As previously noted in the posting of the first draft of the PWG 5100.3 update, the "page-order-received" attribute extends the IPP model to support reverse-page-order documents and requires significant changes to the semantics of the "page-ranges" and "number-up" attributes from STD92 and the "overrides" attribute in PWG 5100.6. During today's IPP workgroup conference call, we discussed the disposition of this attribute: - Nobody on the call was aware of a shipping implementation of this attribute, but 5100.3 was approved in 2003 - 16 years ago... - If we keep this functionality, we need to also update 5100.6 to correctly handle reverse-page-order documents - Keeping this functionality adds unnecessary complexity to IPP since the page-delivery attribute provides a way for the Client to request the pages be reversed for printing while preserving the logical numbering of input pages in the document data The consensus was to obsolete "page-order-received" and its related attributes. Please provide feedback ASAP if you disagree with this decision, as it has significant impact to the development and schedule of the PWG 5100.3 (IPP Production Printing Extensions) update. Thank you! ........ Registration template: Document Description attributes: Reference -------------------------- --------- current-page-order(obsolete) (type2 keyword) [PWG5100.5] Document Template attributes: Reference -------------------------- --------- page-order-received(obsolete) (type2 keyword) [PWG5100.5] Job Description attributes: Reference -------------------------- --------- current-page-order(obsolete) (type2 keyword) [PWG5100.3] Job Status attributes: Reference -------------------------- --------- page-order-received-actual(obsolete) (type2 keyword) [PWG5100.8] Job Template attributes: Reference -------------------------- --------- page-order-received(obsolete) (type2 keyword) [PWG5100.3] Printer Description attributes: Reference ------------------------------ --------- page-order-received-default(obsolete) (type2 keyword) [PWG5100.3] page-order-received-supported(obsolete) (1setOf type2 keyword) [PWG5100.3] _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] RFC: Obsolete "page-order-received" and rel… Michael Sweet via ipp