From ipp-bounces@pwg.org Sun Jan 1 17:29:43 2012 Return-Path: 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 DD54411E8096 for ; Sun, 1 Jan 2012 17:29:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.798 X-Spam-Level: X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=-1.800, BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VccGOSbcvUgB for ; Sun, 1 Jan 2012 17:29:43 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 213C611E808C for ; Sun, 1 Jan 2012 17:29:42 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C876D793C2; Sun, 1 Jan 2012 20:29:24 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by pwg.org (Postfix) with ESMTP id B7C8A79199 for ; Sun, 1 Jan 2012 20:29:07 -0500 (EST) Received: by wgbdt13 with SMTP id dt13so23470696wgb.11 for ; Sun, 01 Jan 2012 17:29:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=1QmL1Z0GwVRdt79aAVIH42MqbbZR8mMPwMvZ8kDTwFo=; b=KQqPqV4M1lEEy/QvYIXAePRswyWqbbZ4YsPm7gVEvI0O0kkbLYbnJ9dO9Ip3yj72Ph xJEAt0X4yZBSSQjn0IJWRfymuzcdGpMZMYaK2Rxopauixnf+ZlhHnXBa8qNrNdkJiNDl B9JMr/vwawXpMNwGFeeVOo4tatZ4rC74ZW60A= MIME-Version: 1.0 Received: by 10.227.60.68 with SMTP id o4mr17610111wbh.22.1325467746554; Sun, 01 Jan 2012 17:29:06 -0800 (PST) Received: by 10.223.158.13 with HTTP; Sun, 1 Jan 2012 17:29:06 -0800 (PST) Date: Sun, 1 Jan 2012 20:29:06 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Reminder - IPP WG - Monday 9 January 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1555990731==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: C876D793C2.A9636 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1555990731== Content-Type: multipart/alternative; boundary=000e0cd6387231d55104b58182e1 --000e0cd6387231d55104b58182e1 Content-Type: text/plain; charset=ISO-8859-1 Hi, Happy New Year everyone. Reminder that our next IPP WG telecon will be: Monday 9 January 2012 1-3pm US EST Agenda TBD - review PWG Raster - review IPPS URI Scheme Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --000e0cd6387231d55104b58182e1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Happy New Year everyone.

Reminder that our next IPP WG te= lecon will be:

Monday 9 January 2012 1-3pm US EST

Agenda TBD<= br>- review PWG Raster
- review IPPS URI Scheme

Cheers,
- Ira<= br>

Ira McDonald (Musician / Software Architect)
Chair= - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Worki= ng Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobil= ity Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --000e0cd6387231d55104b58182e1-- --===============1555990731== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1555990731==-- From ipp-bounces@pwg.org Wed Jan 4 10:48:10 2012 Return-Path: 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 17A1B11E8091 for ; Wed, 4 Jan 2012 10:48:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.854 X-Spam-Level: X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtxiSZea5H4r for ; Wed, 4 Jan 2012 10:48:09 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB8221F87A1 for ; Wed, 4 Jan 2012 10:48:08 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 908A579510; Wed, 4 Jan 2012 13:47:51 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by pwg.org (Postfix) with ESMTP id B41C5794A2 for ; Wed, 4 Jan 2012 13:47:35 -0500 (EST) Received: by wibhm6 with SMTP id hm6so13010488wib.5 for ; Wed, 04 Jan 2012 10:47:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=wF+x3Jb4/3X4Nez5Odk737lVfv5SNO7zRsTJ8VeDsio=; b=AmoYzR+SRkpQOcpJAub4/ND0TeWq3l5Q3SoMCABaov8AuK95xV9c0TeD4yQcYe2VO8 VSdqI5ynE67RPtnuEXOnwrtgN/3h1MwuYSuvgDXtL4WFNPYhtPyY+Ww4jmqHBJEAmves 8jHEAVZvP7QWlvpoSb9A4axDw9VEB5prskAJM= MIME-Version: 1.0 Received: by 10.180.107.134 with SMTP id hc6mr122097219wib.21.1325702854673; Wed, 04 Jan 2012 10:47:34 -0800 (PST) Received: by 10.223.158.13 with HTTP; Wed, 4 Jan 2012 10:47:34 -0800 (PST) Date: Wed, 4 Jan 2012 13:47:34 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - 1-3pm EST Monday 9 January 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0182352569==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 908A579510.A973F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0182352569== Content-Type: multipart/alternative; boundary=e89a8f23443bbb035704b5b83f50 --e89a8f23443bbb035704b5b83f50 Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be next Monday for TWO HOURS! Monday 9 January 10am-12pm US PST / 1-3pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. Live Meeting Info (courtesy of Pete Zehler): Link: https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn URL: https://www.livemeeting.com/cc/xerox/join Meeting ID: PwgSemanticModel Entry Code: LetMeIn *** Main Objective - Review PWG Raster & IPPS URI *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20111206.pdf (3) Status of IANA IPP Registry corrections - http://www.iana.org/assignments/ipp-registrations - Amanda Baber (IANA) completed these on 20 December 2011 (4) Status of other IPP Everywhere specs - if available (5) Review of PWG Raster - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20111202-rev.pdf (6) Review of IPP over HTTPS Transport Binding and 'ipps' URI Scheme - ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf (7) Next Steps - IPP WG on Monday 23 January - prepare for February PWG F2F at Canon - IPP WG on Tuesday 7 February 1-5pm US PST - at Canon in Irvine, CA - IPP WG on Wednesday 8 February 1-5pm US PST - at Canon in Irvine, CA Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e89a8f23443bbb035704b5b83f50 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our next IPP WG call will be next Monday for TWO HOURS!

=A0 Monday 9 January 10am-12pm US PST / 1-3pm US EST

=A0 Call-in toll-free number (US/Canada): 1-866-469-3239
=A0 Call-in toll number (US/Canada): 1-650-429-3300 (Primary)
=A0 Call-in toll number (US/Canada): 1-408-856-9570 (Backup)

=A0 Attendee Access Code: *******#
=A0 Attendee ID Code: # (empty)

If you need the Attendee Access code, please email me a request.

Live Meeting Info (courtesy of Pete Zehler):

=A0 Link: https://www.livemeeting.com/cc/xerox/join?id=3DPwgSemanticModel&role= =3Dattend&pw=3DLetMeIn
=A0 URL: https://www.livemeeting.com/cc/xerox/join
=A0 Meeting ID: PwgS= emanticModel
=A0 Entry Code: LetMeIn


*** Main Objective - Review PWG Raster & IPPS URI ***

Agenda:

(1) PWG IP Policy and Minute Taker
=A0 =A0=A0 - Mike?

(2) Approve IPP minutes from previous meeting
=A0=A0 =A0 - = ftp://ftp.pwg.org/pu= b/pwg/ipp/minutes/ippv2-f2f-minutes-20111206.pdf

(3) Status of IANA IPP Registry corrections
=A0=A0=A0=A0 - ht= tp://www.iana.org/assignments/ipp-registrations
=A0=A0=A0=A0 - Amand= a Baber (IANA) completed these on 20 December 2011

(4) Status of other IPP Everywhere specs
=A0=A0=A0=A0 - if available=

(5) Review of PWG Raster
=A0=A0=A0=A0 - ftp://ft= p.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20111202-rev.pdf
=A0=A0
(6) Review of IPP over HTTPS Transport Binding and 'ipps'= ; URI Scheme
=A0=A0=A0=A0 - ftp://ftp= .pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf= =A0=A0 =A0=A0

(7) Next Steps
=A0=A0=A0=A0 - IPP WG on Monday 23 January - prepare = for February PWG F2F at Canon
=A0=A0=A0=A0 - IPP WG on Tuesday 7 Februar= y 1-5pm US PST - at Canon in Irvine, CA
=A0=A0=A0=A0 - IPP WG on Wednesd= ay 8 February 1-5pm US PST - at Canon in Irvine, CA

Cheers,
- Ira


Ira McDonald (Musician / Soft= ware Architect)
Chair - Linux Foundation Open Printing WG
Secretary -= IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-C= hair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e89a8f23443bbb035704b5b83f50-- --===============0182352569== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0182352569==-- From ipp-bounces@pwg.org Wed Jan 4 11:57:36 2012 Return-Path: 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 540BF11E8088 for ; Wed, 4 Jan 2012 11:57:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.298 X-Spam-Level: X-Spam-Status: No, score=-101.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rbhQwu5UFw6 for ; Wed, 4 Jan 2012 11:57:35 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCF211E8079 for ; Wed, 4 Jan 2012 11:57:34 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 85B987952C; Wed, 4 Jan 2012 14:57:15 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id C2C5F7951F for ; Wed, 4 Jan 2012 14:56:59 -0500 (EST) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXA00JXZI1JRWH1@mail-out.apple.com> for ipp@pwg.org; Wed, 04 Jan 2012 11:56:16 -0800 (PST) X-AuditID: 1180711d-b7cb9ae000005c76-26-4f04aedf52cf Received: from [17.151.81.169] (Unknown_Domain [17.151.81.169]) by relay13.apple.com (Apple SCV relay) with SMTP id F9.34.23670.FDEA40F4; Wed, 04 Jan 2012 11:56:15 -0800 (PST) From: Michael Sweet Date: Wed, 04 Jan 2012 11:56:16 -0800 References: <20120104175741.413D672E004@rfc-editor.org> To: ipp@pwg.org Message-id: <4C5C2450-1046-41B3-AABA-0D319287BF13@apple.com> X-Mailer: Apple Mail (2.1255) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLLMWRmVeSWpSXmKPExsUiOD1wpe79dSz+Br++qlgc2/eSxeLIt1gH Jo+tJ3+wecxbPJ0pgCmKyyYlNSezLLVI3y6BK2P+rGcsBb8CK9Yt3svUwHjPvYuRk0NCwETi zufFzBC2mMSFe+vZuhi5OIQENjJKPLtynh0kwSagJvF7Uh9rFyMHB6+AocSDQzogJrNAgsT+ /z4gJouAisSSs/UgxcICFhKvZ7QygdhCAuYSG/buAbNFBPglJl4EGcIJNMRGYvrxPnaIrbIS z2btYJ/AyDMLYf4shPmzgIqYBbQlli18zQwR1pGYvJARVRjC/nj+CNMCRrZVjIJFqTmJlYbG eokFBTmpesn5uZsYQYHWUCi7g3H/T/5DjAIcjEo8vJbNLP5CrIllxZW5hxglOJiVRHi3zgQK 8aYkVlalFuXHF5XmpBYfYpTmYFES5/WbA5QSSE8sSc1OTS1ILYLJMnFwSjUw5jbo7r7y4c3i j99/nygumOy8qtfv9oHze+KPFSw3fVmzrqjCqKzibZbyxOtiObE/+Xum5Mm0O1/Y22zhnr3H 58MBv943/A83nHI3Paul4cJY+GVG5gSlL6peulFmXIcnP922XtFJQ/1w6OYJfFU/pio8qFsr FP5VaJ2vDVvCab2SQ9a9Z7fGKrEUZyQaajEXFScCANQMI9kwAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Fwd: [Technical Errata Reported] RFC2911 (3072) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0138716455==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 85B987952C.AA094 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0138716455== Content-type: multipart/alternative; boundary="Boundary_(ID_vZ7gRwemqEUuHMsk4rg/hQ)" --Boundary_(ID_vZ7gRwemqEUuHMsk4rg/hQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT FWIW, filed this errata based on the consensus that multiple-document-handling is the attribute to use for collated copies, so 2911 needs a minor correction... Begin forwarded message: > From: RFC Errata System > Subject: [Technical Errata Reported] RFC2911 (3072) > Date: January 4, 2012 9:57:41 AM PST > To: sisaacson@novell.com, tom.hastings@alum.mit.edu, robert.herriot@pahv.xerox.com, debryro@uvsc.edu, papowell@astart.com, presnick@qualcomm.com, stpeter@stpeter.im, carl@manros.com > Cc: msweet@apple.com, rfc-editor@rfc-editor.org > > > The following errata report has been submitted for RFC2911, > "Internet Printing Protocol/1.1: Model and Semantics". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=2911&eid=3072 > > -------------------------------------- > Type: Technical > Reported by: Michael Sweet > > Section: 4.2.4 > > Original Text > ------------- > This attribute is relevant only if a job consists of two or more > documents. This attribute MUST be supported with at least one value > > > Corrected Text > -------------- > This attribute is relevant to jobs consisting of one or more > documents. This attribute MUST be supported with at least one value > > > Notes > ----- > Per consensus of the IPP working group in the Printer Working Group, the "multiple-document-handling" attribute *is* applicable to single-document jobs since it is the only common attribute that can be used to request copy collation. > > The other collation attribute ("sheet-collate" from RFC3381])interacts with "multiple-document-handling" in some non-obvious ways and requires clients and printers to support two different attributes for simple collation. The "sheet-collate" attribute also does not address how finishing options are applied to copies while "multiple-document-handling" does. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC2911 (draft-ietf-ipp-model-v11-07) > -------------------------------------- > Title : Internet Printing Protocol/1.1: Model and Semantics > Publication Date : September 2000 > Author(s) : T. Hastings, Ed., R. Herriot, R. deBry, S. Isaacson, P. Powell > Category : PROPOSED STANDARD > Source : Internet Printing Protocol > Area : Applications > Stream : IETF > Verifying Party : IESG _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_vZ7gRwemqEUuHMsk4rg/hQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable FWIW, filed this errata ba= sed on the consensus that multiple-document-handling is the attribute to us= e for collated copies, so 2911 needs a minor correction...

Begin forwarded message:

From: RFC Errata System &l= t;rfc-editor@rfc-editor.org>


The following erra= ta report has been submitted for RFC2911,
"Internet Printing Protocol/1.= 1: Model and Semantics".

--------------------------------------
Y= ou may review the report below and at:
http://www.rfc-editor.org/= errata_search.php?rfc=3D2911&eid=3D3072

--------------------= ------------------
Type: Technical
Reported by: Michael Sweet <msw= eet@apple.com>

Section: 4.2.4

Original Text
-----------= --
This attribute is relevant only if a job consists of two or more
d= ocuments. This attribute MUST be supported with at least one value

<= br>Corrected Text
--------------
This attribute is relevant to jobs c= onsisting of one or more
documents. This attribute MUST be supported wit= h at least one value


Notes
-----
Per consensus of the IPP = working group in the Printer Working Group, the "multiple-document-handling= " attribute *is* applicable to single-document jobs since it is the only co= mmon attribute that can be used to request copy collation.

The other= collation attribute ("sheet-collate" from RFC3381])interacts with "multipl= e-document-handling" in some non-obvious ways and requires clients and prin= ters to support two different attributes for simple collation. The "sheet-c= ollate" attribute also does not address how finishing options are applied t= o copies while "multiple-document-handling" does.

Instructions:
-= ------------
This errata is currently posted as "Reported". If necessary= , please
use "Reply All" to discuss whether it should be verified or
= rejected. When a decision is reached, the verifying party (IESG)
can log= in to change the status and edit the report, if necessary.

-------= -------------------------------
RFC2911 (draft-ietf-ipp-model-v11-07)--------------------------------------
Title     &n= bsp;         : Internet Printi= ng Protocol/1.1: Model and Semantics
Publication Date    = : September 2000
Author(s)        &nb= sp;  : T. Hastings, Ed., R. Herriot, R. deBry, S. Isaacson, P. Po= well
Category          &nbs= p; : PROPOSED STANDARD
Source       &= nbsp;      : Internet Printing Protocol
Ar= ea             =    : Applications
Stream      &n= bsp;       : IETF
Verifying Party &nb= sp;   : IESG

_________________________________________________= ________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_vZ7gRwemqEUuHMsk4rg/hQ)-- --===============0138716455== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0138716455==-- From pwg-announce-bounces@pwg.org Thu Jan 5 06:17:17 2012 Return-Path: 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 33AA521F85D5 for ; Thu, 5 Jan 2012 06:17:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.298 X-Spam-Level: X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QNOXuFznJzf for ; Thu, 5 Jan 2012 06:17:16 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id F03A721F85D2 for ; Thu, 5 Jan 2012 06:17:15 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A4AEB79554; Thu, 5 Jan 2012 09:16:46 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from USA7109MR003.ACS-INC.COM (usa7109mr003.acs-inc.com [63.101.151.12]) by pwg.org (Postfix) with ESMTP id 6547C7953A; Thu, 5 Jan 2012 09:16:31 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUCAAKwBU8Nh9IPmWdsb2JhbAA/A4JOqFeBVyIBAQEBAQgLCwcUJYF0AwIPAQwRAy8aEgEqBgwLAQdFEgEEEwgBh3mjMAGSIIhygjxjBIJbhV6Ee5oo Received: from usa0300gw002.na.xerox.net ([13.135.210.15]) by USA7109MR003.ACS-INC.COM with ESMTP; 05 Jan 2012 08:16:29 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 5 Jan 2012 09:16:06 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 5 Jan 2012 06:16:04 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: System Object and System Control Service Semantics specification Formal Vote (5 Jan to 10 Feb 2012) Thread-Index: AczLtIa0hOhqow8/Tw+zJ+PJFi3sEw== From: "Zehler, Peter" To: X-OriginalArrivalTime: 05 Jan 2012 14:16:06.0714 (UTC) FILETIME=[909509A0:01CCCBB4] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: mfd@pwg.org Subject: [Pwg-Announce] System Object and System Control Service Semantics specification Formal Vote (5 Jan to 10 Feb 2012) X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0288219400==" Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: A4AEB79554.AD489 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============0288219400== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCCBB4.8FD51452" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCCBB4.8FD51452 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings: =20 VOTES ARE CONFIDENTIAL! See voting instructions below. =20 This email initiates the Formal Approval vote by the PWG membership on the System Object and System Control Service Semantics specification, which is located at: =20 ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdsystemcontrolservicemodel10-20111 215.pdf =20 The complete list of PWG Last Call issues and resolutions is located at: =20 ftp://ftp.pwg.org/pub/pwg/mfd/wd/SystemServiceLastCallComment-resolution -20111215.pdf =20 =20 =20 VOTING PERIOD: This Formal Vote will start today on Thursday January 5, 2012 and will end at 10pm (US Pacific Time) on Friday February 10, 2012. =20 Valid votes are: Yes, No, No (with Strong Objection), Abstain. =20 =20 PWG Privacy Policy: Your vote is confidential and will not be disclosed by PWG officers or document editors. =20 =20 HOW TO VOTE: Send an email with *exactly* the following subject line format: System Formal Vote--- =20 Example: System Formal Vote -Acme-McGee-Yes =20 =20 Rules: (1) Any "No" vote MUST state the reason for the "No" vote and MUST contain a description of the *technical* changes required to turn the "No" vote into a "Yes" vote - otherwise the "No" vote will NOT be counted, per PWG Process/3.0. =20 (2) Any "No" vote MUST NOT contain *editorial* comments, per PWG Process/3.0. =20 (3) Any "Yes" vote MAY contain "editorial" comments, per PWG Process/3.0. =20 (4) Any "Yes" vote MUST NOT contain any *technical* comments, per PWG Process/3.0. =20 (5) Any "Abstain" vote counts toward quorum, but not approval. =20 =20 WHERE TO SEND YOUR VOTE: Please send your vote to *all* of the following email addresses (replacing "dot" with '.' and "at" with '@'): =20 msweet"at"apple"dot"com (Mike Sweet, PWG Chair) blueroofmusic"at"gmail"dot"com (Ira McDonald, PWG Secretary) Peter"dot"Zehler"at"Xerox"dot"com (Peter Zehler, MFD WG -Chair) =20 =20 Please do NOT simply reply to this note on PWG-Announce or the MFD WG list (to preserve the confidentiality of your vote). =20 =20 Notes: (1) This Formal Vote is being conducted under the rules of the PWG Process/3.0 and the current PWG Policy on Intellectual Property and Confidentiality agreement. The 2011 PWG Membership Agreement calls out both of these documents and the links are provided below. =20 (2) To be eligible to vote the member MUST have submitted a signed copy of the 2011 PWG Membership Agreement and paid their dues. =20 The PWG Definition of the Standards Development Process Version 3.0 is located at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf =20 The PWG Policy on Intellectual Property and Confidentiality is located at: http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf =20 Cheers, - Pete (Chair Semantic Model WG) =20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCCBB4.8FD51452 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
Greetings:
 
VOTES ARE CONFIDENTIAL!  See voting =
instructions below.
 
This email initiates the Formal Approval vote by =
the PWG membership on the System Object and System Control Service Semantic=
s specification, which is located at:
  ftp://ftp.p=
wg.org/pub/pwg/mfd/wd/wd-mfdsystemcontrolservicemodel10-20111215.pdf
=
 
The complete list of PWG Last Call issues and resolutions is located at=
:
 ftp://ftp.pwg.org/pub/pwg/mfd/wd/SystemServiceL=
astCallComment-resolution-20111215.pdf
 
= 
 
 =

VOTING P=
ERIOD:  This Formal Vote will start today on Thursday January 5, 2012 =
and will end at 10pm (US Pacific Time) on Friday February 10, 2012.
 
V=
alid votes are: Yes, No, No (with Strong Objection), Abstain.
 
 <=
o:p>
PWG Privacy Policy:  Your vote is confidential and will not be discl=
osed by PWG officers or document editors.
 
<=
span style=3D'font-family:"Arial","sans-serif"'> 
HOW TO VOTE:<=
/o:p>
Sen=
d an email with *exactly* the following subject line format:
System Forma=
l Vote-<company name>-<voter's last name>-<Yes/No/Abstain>=
;
 
Example:
  System Formal Vote -Acme-McGee-Yes
 =

 
Rules:
(1) Any "No" vote MUST state the reason for the "N=
o" vote and MUST contain a description of the *technical* changes requ=
ired to turn the "No" vote into a "Yes" vote - otherwis=
e the "No" vote will NOT be counted, per PWG Process/3.0.
 
(=
2) Any "No" vote MUST NOT contain *editorial* comments, per PWG P=
rocess/3.0.
 
(3) Any "Yes" vote MAY contain "editorial&=
quot; comments, per PWG Process/3.0.
 
(4) Any "Yes" vote MUS=
T NOT contain any  *technical* comments, per PWG Process/3.0.
 =

(5=
) Any "Abstain" vote counts toward quorum, but not approval.=

 <=
o:p>
 
WHERE TO SEND YOUR VOTE:
Please send your vote to *all* of the=
 following email addresses (replacing "dot" with '.' and "at=
" with '@'):
 
msweet"at"apple"dot"com (Mike S=
weet, PWG Chair)
blueroofmusic"at"gmail"dot"com (Ira =
McDonald, PWG Secretary)
Peter"dot"Zehler"at"Xerox&qu=
ot;dot"com (Peter Zehler, MFD WG -Chair)
<=
span style=3D'font-family:"Arial","sans-serif"'> 
 
Please do NOT =
simply reply to this note on PWG-Announce or the MFD WG list (to preserve t=
he confidentiality of your vote).
 
 
Notes:=

(1) This Formal=
 Vote is being conducted under the rules of the PWG Process/3.0 and the cur=
rent PWG Policy on Intellectual Property and Confidentiality agreement.&nbs=
p; The 2011 PWG Membership Agreement calls out both  of these document=
s and the links are provided below.
 
(2) To be eligible to vote the me=
mber MUST have submitted a signed copy of the 2011 PWG Membership Agreement=
 and paid their dues.
 
The PWG Definition of the Standards Development=
 Process Version 3.0 is located at:
  http://www.pwg.org/chair/membershi=
p_docs/pwg-process30.pdf
 
The PWG Policy on Intellectual Property =
and Confidentiality is located at:
  http://www.pwg.org/chair/membershi=
p_docs/pwg-ip-policy.pdf
 
Cheers,
- Pete (Chair Semantic Model W=
G)

 

 

 =

Peter Zehler

= Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com<= span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F49= 7D'>
Voice: (585) 265-8755
FAX: (585) 2= 65-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCCBB4.8FD51452-- --===============0288219400== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --===============0288219400==-- From pwg-announce-bounces@pwg.org Thu Jan 5 21:33:21 2012 Return-Path: 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 2D5F321F864E for ; Thu, 5 Jan 2012 21:33:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.948 X-Spam-Level: X-Spam-Status: No, score=-101.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nzi1kvtjnQV for ; Thu, 5 Jan 2012 21:33:19 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD1621F862C for ; Thu, 5 Jan 2012 21:33:19 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 424EB7958D; Fri, 6 Jan 2012 00:32:55 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 6C8AD7956E for ; Fri, 6 Jan 2012 00:32:36 -0500 (EST) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LXD00M293E3CX75@mail-out.apple.com> for pwg-announce@pwg.org; Thu, 05 Jan 2012 21:32:35 -0800 (PST) X-AuditID: 11807136-b7c0dae00000279d-b7-4f06877314c5 Received: from [17.151.79.21] (Unknown_Domain [17.151.79.21]) by relay15.apple.com (Apple SCV relay) with SMTP id C2.D6.10141.377860F4; Thu, 05 Jan 2012 21:32:35 -0800 (PST) From: Michael Sweet Date: Thu, 05 Jan 2012 21:32:35 -0800 Message-id: <96355497-3EBB-4C5C-BA81-CDEF9C1261C6@apple.com> To: pwg-announce@pwg.org X-Mailer: Apple Mail (2.1255) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmluLIzCtJLcpLzFFi42IRnO4vqlvczuZv8PmetsW61tXMDowe8xZP ZwpgjOKySUnNySxLLdK3S+DK+HJiNlvBQ+WKhh+v2RoYF8t3MXJySAiYSJy+upQVwhaTuHBv PVsXIxeHkMB6RonVK/6ygyTYBNQkfk/qAytiFkiQWLTrBlhcWMBdouPVdLA4i4CKxK7zv5hB bF4BG4mvRxeC2SICEhLTuucB1XAAxQ0lHhzSgdglK/Fs1g72CYzcs5BMnYVQBRHWlli28DUz SJhZQEdi8kJGVGEI++P5I0wLGNlWMQoWpeYkVhqa6iUWFOSk6iXn525iBAVRQ6HZDsYdf+UO MQpwMCrx8M5kZvMXYk0sK67MPcQowcGsJMK7ygYoxJuSWFmVWpQfX1Sak1p8iFGag0VJnPfM f1Z/IYH0xJLU7NTUgtQimCwTB6dUA+P6vi+mu3MS75mt1Jpg4Rb8njtxsdnXjIJLui9tFwnW eVoahLDFpMqWMi80TEkKYvfSv7PyEYeFYV/E4a+3Imrsd194oWVUs0E49K/vBt17u5/X2i74 3Lz9g9D/z8dl/5cztqsbB3/PldhePUVs1xK1KgftNlZdW7mL9p9016+wrbk+p0OuTYmlOCPR UIu5qDgRAMZEJZceAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] REMINDER: PWG February 2012 Face-to-Face meeting in Irvine, CA X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1827151204==" Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 424EB7958D.AC6A9 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1827151204== Content-type: multipart/alternative; boundary="Boundary_(ID_KimLxgL3iVPQ1y+QmjhWQg)" --Boundary_(ID_KimLxgL3iVPQ1y+QmjhWQg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT [This is just a reminder - if you haven't already filled out the survey, please do so now...] All, The February 2012 PWG face-to-face meeting page is now available. The agenda and venue information can be found at: http://www.pwg.org/chair/meeting-info/february_2012_irvine.html This page will be updated with document links as the material becomes available. Please visit the February 2012 survey page PRIOR TO FEBRUARY 4, 2012 and indicate whether you plan to participate in person or call in: http://www.surveymonkey.com/s/C3WF3XK For those not able to attend in person, the usual telephone bridge number will be provided. The details of the conference call are: Call-in toll-free number (US/Canada): +1 866 469-3239 Call-in toll number (US/Canada): +1 650 429-3300 Call-in toll number (US/Canada): +1 408 856-9570 Attendee access code: Please request from the PWG Chair (msweet@apple.com) if you need it. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_KimLxgL3iVPQ1y+QmjhWQg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable
[This is just a remin= der - if you haven't already filled out the survey, please do so now...]

All,

The February 2012 PWG face-to-fac= e meeting page is now available. The agenda and venue information can be fo= und at:


This page will be updated with= document links as the material becomes available.

Please visit the February 2012 survey page PRIOR TO FEBRUARY 4, 2012 and i= ndicate whether you plan to participate in person or call in:

For those not able to= attend in person, the usual telephone bridge number will be provided.=  The details of the conference call are:

Call-in tol= l-free number (US/Canada): +1 866 469-3239
Call-in toll number (US/Canad= a): +1 650 429-3300
Call-in toll number (US/Canada): +1 408 856-9570
=
Attendee access code: Please request from the PWG Chair (msweet@apple.com) if you need it.

_________________________________________________= ________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_KimLxgL3iVPQ1y+QmjhWQg)-- --===============1827151204== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --===============1827151204==-- From info@webmaster.pl Fri Jan 6 01:01:37 2012 Return-Path: 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 9F36021F8798; Fri, 6 Jan 2012 01:01:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.852 X-Spam-Level: *** X-Spam-Status: No, score=3.852 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_50=0.001, FH_RELAY_NODNS=1.451, MANGLED_TAKE=2.3, RDNS_NONE=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axG8Sgqun8K4; Fri, 6 Jan 2012 01:01:37 -0800 (PST) Received: from mail.solca.med.ec (unknown [200.105.240.90]) by ietfa.amsl.com (Postfix) with ESMTP id 1F46E21F878F; Fri, 6 Jan 2012 01:01:34 -0800 (PST) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 1253B19C0310; Fri, 6 Jan 2012 04:07:42 -0500 (ECT) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by mail.solca.med.ec (Postfix) with ESMTP id C6A6F19C02E8; Fri, 6 Jan 2012 04:07:41 -0500 (ECT) Received: from 41.71.147.245 (SquirrelMail authenticated user aacosta) by mail.solca.med.ec with HTTP; Fri, 6 Jan 2012 04:07:41 -0500 (ECT) Message-ID: <50112.41.71.147.245.1325840861.squirrel@mail.solca.med.ec> Date: Fri, 6 Jan 2012 04:07:41 -0500 (ECT) Subject: Webmaster Powiadomienie Code #04KV6f0 From: "Webmaster Upgrading Department" Reply-To: customercarewebdept40@w.cn User-Agent: SquirrelMail/1.4.8-5.el5.centos.10 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal To: undisclosed-recipients:; X-TM-AS-Product-Ver: IMSS-7.1.0.1302-6.8.0.1017-18628.006 X-TM-AS-Result: No--1.774-4.5-31-10 X-imss-scan-details: No--1.774-4.5-31-10 X-TM-AS-User-Approved-Sender: No X-TMASE-MatchedRID: Q6QF7or1Ap7oEmtXXZT7KgDPuhU4P53KI9yVcHNDU7Z4cj3zcdxHt4o9 JDEyKOWGe7nQjwn391uLSHl2wluIWVCnpnvgOFGXgxsfzkNRlfKltRcNkC3a6RkBcDGzbZwbt0T fTryqxQi3AXhx3VgvxY3XZ9GLfO7WHp/xox1y/dwxSB/Jyvs6EWVcLxtnLW0onNs1CBxaaWVz/7 mmIg7apa+uf5/vyEbyRXiaEKR5pZ9pY2iUG1DXBsMdhJlZhFQKT2jcE+1/SHZ+3BndfXUhXQ== Drogi użytkowniku konto e-mail, Ten komunikat jest od poczty centrum wiadomości do wszystkich właścicieli kont webmail. W pierwszym kwartale 2012 r. Obecnie jest przeprowadzenie usługi aktualizacji do naszej bazy danych i e-mail centrum konta. Jesteśmy usunięcie wszystkich niewykorzystanych konto poczty internetowej, aby utworzyć więcej miejsca dla nowych kont. Aby zapobiec koncie od usuwania i Aby kontynuować korzystanie z naszych usług, które są wymagane do aktualizacji i potwierdzenia konta webmail. Aby zakończyć potwierdzenia konta za pierwszy kwartał 2012 r., Jesteś odpowiedzieć na tę wiadomość natychmiast i wprowadź dane swojego konta w wymienionych poniżej. Potwierdzenie informacji o koncie Nazwa użytkownika: .................. E-mail Login .............. Hasło: .................. Potwierdź hasło :............ Data urodzenia: ............... Zostanie wysłany nowy potwierdzenie hasło alfanumeryczne tak, że tylko będzie jest ważne w tym okresie i może być zmieniony po zakończeniu procesu. Dziękujemy za zrozumienie. Webmaster Upgrading Department Prawa autorskie 2012 - Komunikacja Webmail - Wszelkie prawa zastrzeżone. From ipp-bounces@pwg.org Fri Jan 6 03:29:23 2012 Return-Path: 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 2DCBE21F8872 for ; Fri, 6 Jan 2012 03:29:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.948 X-Spam-Level: X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVdVWkotEUxp for ; Fri, 6 Jan 2012 03:29:21 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 741A921F886C for ; Fri, 6 Jan 2012 03:29:21 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 7E887795BD; Fri, 6 Jan 2012 06:28:53 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 0ADE97953C; Fri, 6 Jan 2012 06:28:38 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMAADLaBk8Nh9IPmWdsb2JhbABAA4JOmTWQRSIBAQEBAQgLCwcUJYFyAQEBAgIPAQwBEAMkCywBGQQBAQsGDAcEAQdFCQkBBAESCKtzAZI1iHKCPGMEiDmEe5op Received: from usa0300gw002.na.xerox.net ([13.135.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 06 Jan 2012 05:28:37 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 6 Jan 2012 06:28:37 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 6 Jan 2012 03:28:35 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Reminder: Working Group Last Call for PWG Print Job Ticket and Associated Capabilities specification ends January 8 2012 Thread-Index: AczMZlEzwKQwYFczS/uruFpgTpr7GQ== From: "Zehler, Peter" To: , , X-OriginalArrivalTime: 06 Jan 2012 11:28:37.0529 (UTC) FILETIME=[5536D890:01CCCC66] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Reminder: Working Group Last Call for PWG Print Job Ticket and Associated Capabilities specification ends January 8 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0010883160==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 7E887795BD.A9FD5 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0010883160== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCCC66.546173F4" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCCC66.546173F4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, I've received a few comments. I plan on starting the PWG wide Last Call on Monday unless there is an objection. Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Zehler, Peter=20 Sent: Tuesday, December 20, 2011 9:06 AM To: cloud@pwg.org; IPP@pwg.org; mfd@pwg.org Subject: Working Group Last Call for PWG Print Job Ticket and Associated Capabilities specification ends January 8 2012 =20 All, The updated PWG Print Job Ticket and Associated Capabilities specification is available at =2E The Working Group Last call will complete the second week of January. The PWG wide Last Call will begin shortly after any Working Group comments are integrated. =20 Please send any comments you have to mailto:mfd@pwg.com=20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCCC66.546173F4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

I’ve received a few comments.  I plan on startin= g the PWG wide Last Call on Monday unless there is an objection.=

Pete

 =

 

Peter Zehler

Xerox Research Center Webster
Email: <= a href=3D"mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com<= span style=3D'color:#1F497D'>
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster N= Y, 14580-9701

 

From: Zehler, Pe= ter
Sent: Tuesday, December 20, 2011 9:06 AM
To: cloud= @pwg.org; IPP@pwg.org; mfd@pwg.org
Subject: Working Group Last Ca= ll for PWG Print Job Ticket and Associated Capabilities specification ends = January 8 2012

&= nbsp;

All,

The updated PWG Print Job Ticket and Associated Capabilities specification= is available at

<ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-sm20-printjobticket10-= 20111220.pdf>.

The Working= Group Last call will complete the second week of January.  The PWG wi= de Last Call will begin shortly after any Working Group comments are integr= ated.

 

Please send any comments you have to mailto:mfd@pwg.com

 

 

Peter Zehler

Xerox Research Center Webster=
Email: Peter.Zehler@= Xerox.com
Voice: (585)= 265-8755
FAX: (585) 265-7= 441
US Mail: Peter Zehler<= /span>
Xerox Corp.
800 Phillips Rd.
M/S 128-25E<= br>Webster NY, 14580-9701

 <= /p>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCCC66.546173F4-- --===============0010883160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0010883160==-- From ipp-bounces@pwg.org Sun Jan 8 04:19:29 2012 Return-Path: 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 22A7521F845C for ; Sun, 8 Jan 2012 04:19:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.42 X-Spam-Level: X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[AWL=-0.312, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTsiKsL5+9Hm for ; Sun, 8 Jan 2012 04:19:27 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 601C321F845B for ; Sun, 8 Jan 2012 04:19:27 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id AD3CB795AC; Sun, 8 Jan 2012 07:18:49 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR004.ACS-INC.COM (usa7109mr004.acs-inc.com [63.101.151.13]) by pwg.org (Postfix) with ESMTP id 4AF727953E; Sun, 8 Jan 2012 07:18:33 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtoAAC2ICU8Nl9IPmWdsb2JhbABAA4JOqXYiAQEBAQEICwsHFCWBcgEBAQQPAQwRAy8RCRIBCBEEAQELBgwEBwEHRQkJAQQBEgirOAGRVYhygjxjBIgGM4R9mi0 Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR004.ACS-INC.COM with ESMTP; 08 Jan 2012 06:18:32 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 8 Jan 2012 04:18:31 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 8 Jan 2012 04:18:31 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MFD] A couple of question on Job Ticket 2.0 (+ Issue for JPS3) thread-index: AczN/Q/LBF4WnbTITDuVerfmQfztpg== From: "Zehler, Peter" To: "Petrie, Glen" , X-OriginalArrivalTime: 08 Jan 2012 12:18:31.0837 (UTC) FILETIME=[A2C97CD0:01CCCDFF] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: IPP@pwg.org Subject: [IPP] RE: [MFD] A couple of question on Job Ticket 2.0 (+ Issue for JPS3) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0851269443==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: AD3CB795AC.A92C7 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0851269443== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCCDFF.A2980B6F" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCCDFF.A2980B6F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Media is defined in RFC2911 =A74.2.11 and MediaSizeName is defined in PWG51= 08.02 =A78.1.3.1.15.3. The semantic difference is that Media is a named me= dium upon which the impressions will be printed and MediaSizeName is a name= d size of the canvas for an image. For both elements PWG5101.1 =A75 is the= reference for the standard values. =20 The issue for JPS3, and PJT, is associated with the MediaCol. The MediaCol= has an explicit size for the media (i.e., MediaSize) and a named location = to obtain the media (i.e., MediaSource). Is there a named media size in Me= diaCol? If there is, will it be Media or MediaSizeName?=20=20 =20 I have removed MediaSizeName from MediaCol and the PJT specification for no= w. =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Friday, January 06, 2012 1:48 PM To: Zehler, Peter; mfd@pwg.org Subject: RE: [MFD] A couple of question on Job Ticket 2.0 =20 So is "Media" (from page 50 of pwg:pjt) the same as "MediaSizeName" (from p= age 51 of pwg:pjt)? =20 Actually, the reference for MediaSizeName (pwg 5100.5 $8.1) appears to be w= rong. MediaSizeName is also defined in the 5105.1 /pg 35 and has the same = references pwg 5100.5 $8.1. Maybe MediaSizeName is defined somewhere else. =20 Glen =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCCDFF.A2980B6F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Media is = defined in RFC2911 =A74.2.11 and MediaSizeName is defined in PWG5108.02 =A7= 8.1.3.1.15.3.=A0 The semantic difference is that Media is a named medium up= on which the impressions will be printed and MediaSizeName is a named size = of the canvas for an image.=A0 For both elements PWG5101.1 =A75 is the refe= rence for the standard values.

 

The issue for = JPS3, and PJT, is associated with the MediaCol.=A0 The MediaCol has an expl= icit size for the media (i.e., MediaSize) and a named location to obtain th= e media (i.e., MediaSource).=A0 Is there a named media size in MediaCol?=A0= If there is, will it be Media or MediaSizeName?=A0

<= p class=3DMsoNormal> 

I have removed MediaSizeName from MediaCol and the PJT specificatio= n for now.

 

 

<= p class=3DMsoNormal>Peter Zehler

Xerox Re= search Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 2= 65-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

From: Petrie= , Glen [mailto:glen.petrie@eitc.epson.com]
Sent: Friday, January= 06, 2012 1:48 PM
To: Zehler, Peter; mfd@pwg.org
Subject: RE: [MFD] A couple of question on Job Ticket 2.0

 

So is “Media&#= 8221; (from page 50 of pwg:pjt) the same as “MediaSizeName” (fr= om page 51 of pwg:pjt)?

 

Actually, the reference for MediaSizeName (pwg 5100.5 $8.1) appears to = be wrong.  MediaSizeName is also defined in the 5105.1 /pg 35 and has = the same references pwg 5100.5 $8.1.   Maybe MediaSizeName is def= ined somewhere else.

 

<= p class=3DMsoNormal>Glen

 

</snip&= gt;


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCCDFF.A2980B6F-- --===============0851269443== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0851269443==-- From ipp-bounces@pwg.org Mon Jan 9 09:14:11 2012 Return-Path: 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 8F28511E80A3 for ; Mon, 9 Jan 2012 09:14:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.991 X-Spam-Level: X-Spam-Status: No, score=-0.991 tagged_above=-999 required=5 tests=[AWL=-0.807, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajtursQXJg6D for ; Mon, 9 Jan 2012 09:14:06 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id F1B7711E80A2 for ; Mon, 9 Jan 2012 09:14:05 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 54C5C795B8; Mon, 9 Jan 2012 12:13:30 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by pwg.org (Postfix) with ESMTP id 00499795AD for ; Mon, 9 Jan 2012 12:13:10 -0500 (EST) Received: by werm1 with SMTP id m1so3694412wer.5 for ; Mon, 09 Jan 2012 09:13:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=8/Q9toa5sGgqdfeD2BQYnsVSPyVebLY8BezHysCmivI=; b=EKHMzX4L4yL12cSg+cqzHPruFD8BIHbD4eD78lKhzPcA3hcEL9iQN/bDLBiOimcM4y JRG8QHoRpJltkraLe2i4CmIqQR15LVnvXZbQ6XJOX+sHKGH/qaPnfb2xKAFOSDEJyRwh 1QCObXwWXiGqLbz+NzHin13iFWiFtIwwg+4e8= MIME-Version: 1.0 Received: by 10.216.137.155 with SMTP id y27mr4009184wei.53.1326129190150; Mon, 09 Jan 2012 09:13:10 -0800 (PST) Received: by 10.223.155.10 with HTTP; Mon, 9 Jan 2012 09:13:10 -0800 (PST) Date: Mon, 9 Jan 2012 12:13:10 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] REVISED - IPP Agenda - 1-3pm EST Monday 9 January 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1015682875==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 54C5C795B8.A8D0C X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1015682875== Content-Type: multipart/alternative; boundary=0016e6d564c84e236a04b61b8348 --0016e6d564c84e236a04b61b8348 Content-Type: text/plain; charset=ISO-8859-1 Hi, [New topic from Pete Zehler for PWG Print Job Ticket] Our next IPP WG call will be next Monday for TWO HOURS! Monday 9 January 10am-12pm US PST / 1-3pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. Live Meeting Info (courtesy of Pete Zehler): Link: https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn URL: https://www.livemeeting.com/cc/xerox/join Meeting ID: PwgSemanticModel Entry Code: LetMeIn *** Main Objective - Review PWG Raster & IPPS URI *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20111206.pdf (3) Status of IANA IPP Registry corrections - http://www.iana.org/assignments/ipp-registrations - Amanda Baber (IANA) completed these on 20 December 2011 (4) Status of other IPP Everywhere specs - if available (5a) PWG Print Job Ticket - conditional PWG Raster requirements - should these be in PJT at all? or just in PWG Raster? - Pete Zehler needs closure to move PJT into PWG Last Call (5b) Review of PWG Raster - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20111202-rev.pdf (6) Review of IPP over HTTPS Transport Binding and 'ipps' URI Scheme - ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf (7) Next Steps - IPP WG on Monday 23 January - prepare for February PWG F2F at Canon - IPP WG on Tuesday 7 February 1-5pm US PST - at Canon in Irvine, CA - IPP WG on Wednesday 8 February 1-5pm US PST - at Canon in Irvine, CA Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --0016e6d564c84e236a04b61b8348 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

[New topic from Pete Zehler for PWG Print Job Ticket]

Our next IPP WG call will be next Monday for TWO HOURS!

=A0 Monday 9 January 10am-12pm US PST / 1-3pm US EST

=A0 Call-in toll-free number (US/Canada): 1-866-469-3239
=A0 Call-in toll number (US/Canada): 1-650-429-3300 (Primary)
=A0 Call-in toll number (US/Canada): 1-408-856-9570 (Backup)

=A0 Attendee Access Code: *******#
=A0 Attendee ID Code: # (empty)

If you need the Attendee Access code, please email me a request.

Live Meeting Info (courtesy of Pete Zehler):

=A0 Link: https://www.livemeeting.com/cc/xerox/join?id=3DPwgSemanticModel&role= =3Dattend&pw=3DLetMeIn
=A0 URL: https://www.livemeeting.com/cc/xerox/join
=A0 Meeting ID: PwgS= emanticModel
=A0 Entry Code: LetMeIn


*** Main Objective - Review PWG Raster & IPPS URI ***

Agenda:

(1) PWG IP Policy and Minute Taker
=A0 =A0=A0 - Mike?

(2) Approve IPP minutes from previous meeting
=A0=A0 =A0 - = ftp://ftp.pwg.org/pu= b/pwg/ipp/minutes/ippv2-f2f-minutes-20111206.pdf

(3) Status of IANA IPP Registry corrections
=A0=A0=A0=A0 - ht= tp://www.iana.org/assignments/ipp-registrations
=A0=A0=A0=A0 - Amand= a Baber (IANA) completed these on 20 December 2011

(4) Status of other IPP Everywhere specs
=A0=A0=A0=A0 - if available=

(5a) PWG Print Job Ticket - conditional PWG Raster requirements
=A0= =A0=A0=A0 - should these be in PJT at all?=A0 or just in PWG Raster?
=A0= =A0=A0=A0 - Pete Zehler needs closure to move PJT into PWG Last Call
(5b) Review of PWG Raster
=A0=A0=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippr= aster10-20111202-rev.pdf
=A0=A0
(6) Review of IPP over HTTPS Transport Binding and 'ipps'= ; URI Scheme
=A0=A0=A0=A0 - ftp://ftp= .pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf= =A0=A0 =A0=A0

(7) Next Steps
=A0=A0=A0=A0 - IPP WG on Monday 23 January - prepare = for February PWG F2F at Canon
=A0=A0=A0=A0 - IPP WG on Tuesday 7 Februar= y 1-5pm US PST - at Canon in Irvine, CA
=A0=A0=A0=A0 - IPP WG on Wednesd= ay 8 February 1-5pm US PST - at Canon in Irvine, CA

Cheers,
- Ira

Ira McDonald (Musician / Software= Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEE= E-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair= - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --0016e6d564c84e236a04b61b8348-- --===============1015682875== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1015682875==-- From ipp-bounces@pwg.org Mon Jan 9 16:34:29 2012 Return-Path: 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 E445321F8462 for ; Mon, 9 Jan 2012 16:34:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.165 X-Spam-Level: X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vc9xEAuLEDJZ for ; Mon, 9 Jan 2012 16:34:29 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5D44621F841B for ; Mon, 9 Jan 2012 16:34:29 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C836979554; Mon, 9 Jan 2012 19:34:11 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 0EDA37953A for ; Mon, 9 Jan 2012 19:33:57 -0500 (EST) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXK00BQY46HZ340@mail-out.apple.com> for ipp@pwg.org; Mon, 09 Jan 2012 16:32:54 -0800 (PST) X-AuditID: 11807130-b7cc9ae000005ce6-fe-4f0b87358cd6 Received: from [17.151.81.138] (Unknown_Domain [17.151.81.138]) by relay11.apple.com (Apple SCV relay) with SMTP id E2.24.23782.5378B0F4; Mon, 09 Jan 2012 16:32:54 -0800 (PST) From: Michael Sweet Date: Mon, 09 Jan 2012 16:32:53 -0800 To: ipp@pwg.org Message-id: <2291C597-28DE-40E3-99D5-3CED3E1B5CF9@apple.com> X-Mailer: Apple Mail (2.1255) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLJMWRmVeSWpSXmKPExsUiOD2wS9esndvf4O9qVotj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZZw/vY654A5bRcO3LtYGxmOsXYycHBICJhJN La/YIWwxiQv31rN1MXJxCAlsZJT4+fokWIJNQE3i96Q+sAZmAS2JG/9eMkHY2hLLFr5mBrFZ BFQkXi9dxghiCwMNXX/3CxuILSLALzHxIkQvr4CNxN3j64BsDiDbUOLBIR2IvbISz2btYJ/A yDMLyYZZSDbMQuhYwMi8ilGwKDUnsdLQUC+xoCAnVS85P3cTIyhQGgoNdjCu/cl/iFGAg1GJ h/ekBre/EGtiWXFl7iFGCQ5mJRHelXFAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rx1hez+QgLp iSWp2ampBalFMFkmDk6pBkZH1Z5Vj5muhd/aJixUl5ZwtEn457znTIl7T11lvOUpl6X16MyN xmp5c7tVetvnBN568cauZE/bh5t3mU23TP479/zuxF31hRX7HnZxWVpe7vdO5bkuyrLn2Yov s4+FHjgbVtI6U6ophSFL427Lm0ef66fOklux9q3wYe8JpyL6VB7P2WfgkzRdiaU4I9FQi7mo OBEALgZYbRACAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's conference call X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: C836979554.A8183 X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted the minutes from today's conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120109.pdf We plan to continue reviewing the current PWG Raster draft during the second hour of next week's Cloud Imaging conference call, approximately 2pm Eastern Time. New action items: - Mike to add "media-size-name" member attribute to "media-col" in JPS3 - Pete to add "MediaSizeName" to MediaCol in PJT, move MediaSource out of the MediaSize/SizeName/Source choice since source is often used in conjunction with size on non-production printers (i.e. print envelopes from bypass tray) - Pete to generate XML spy picture for Figure 4 PwgRasterDocument elements _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From test@impactro.net Tue Jan 10 11:13:20 2012 Return-Path: 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 1EF5F21F8644 for ; Tue, 10 Jan 2012 11:13:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.501 X-Spam-Level: *** X-Spam-Status: No, score=3.501 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67-2c8bAzXAq for ; Tue, 10 Jan 2012 11:13:19 -0800 (PST) Received: from mail1.impactro.net (server14.impactro.net [184.173.239.50]) by ietfa.amsl.com (Postfix) with ESMTP id 7CBE621F862D for ; Tue, 10 Jan 2012 11:13:19 -0800 (PST) Received: from lm ([113.104.192.180]) by impactro.net with MailEnable ESMTP; Tue, 10 Jan 2012 17:13:14 -0200 Reply-To: Message-ID: <0AEC26165D8AFC779462382659F7550F@lm> From: "Holly" To: Subject: All the blessings Date: Wed, 11 Jan 2012 03:12:44 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02E2_01E9DE36.1CEB28A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 This is a multi-part message in MIME format. ------=_NextPart_000_02E2_01E9DE36.1CEB28A0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBQdXJjaGFzaW5nIE1hbmFnZXIsDQoNCg0KR29vZCBtb3JuaW5nIG15IGZyaWVuZCANClRo YW5rcyBmb3IgeW91ciB0aW1lIHRvIHJlYWQgbXkgZW1haWwNCkdsYWQgdG8ga25vdyB5b3UgYXJl IGxlYWRpbmcgcmV0YWlsIG9mIHRhYmxldCBwYy4gDQpXZSBhcmUgYSB0YWJsZXQgcGMgbWFudWZh Y3R1cmVyIHdoaWNoIGV4cG9ydGVkIHRvIE5vcnRoIEFtZXJpY2EgYW5kIEV1cm9wZSBpbiBDaGlu YS4NCg0KVGFibGV0IFBDIDcgaW5jaCB3aGljaCBpcyBzZWxsaW5nIHdlbGwgaW4gb3VyIG1hcmtl dCBhcyBmb2xsb3dzOg0KMSlQcmljZToNCiAgIDUwMCBwaWVjZXM6ICAg44CA44CA44CAVVNEIDUx LjkwKEZPQiBTSEVOWkhFTikNCiAgIDEwMDAgcGllY2VzOiDjgIDjgIDjgIBVU0QgNTEuMDAoRk9C IFNIRU5aSEVOKQ0KMilhLlZvbHVtZTrjgIDjgIDjgIDjgIDjgIAwLjAwMDRDdWJpYyBtZXRlcnMv cGNzDQogICBiLldlaWdodDrjgIDjgIDjgIDjgIDjgIAzLjY1a2dzL2NhdG9uDQogICBjLlBhY2tp bmc644CA44CA44CAIOOAgDEwcGNzL2NhcnRvbg0KMylNaW5pbXVtIE9yZGVyOiDjgIDjgIA1MDAg cGllY2VzDQo0KUxlYWRpbmcgdGltZTog44CA44CA44CAMjAtMjUgd29ya2luZ2RheXMNCjUpUGF5 bWVudCBUZXJtczog44CAICBUL1QgKDMwJSBkZXBvc2l0IGJlZm9yZSBwcm9kdWN0aW9uLCA3MCUg YmFsYW5jZSBiZWZvcmUgc2hpcG1lbnQpDQo2KVF1YWxpdHk6IOOAgOOAgOOAgOOAgOOAgCAgV2Fy cmFudHkgZm9yIG9uZSB5ZWFyDQo3KU9yZGVyOuOAgOOAgOOAgOOAgOOAgOOAgCAgV2VsY29tZSBP RU0gb3JkZXJzDQoNCg0KSGF2ZSBhIG5pY2UgZGF5IQ0KDQpLaW5kIHJlZ2FyZHMsDQpIb2xseQ0K RS1tYWlsOiAgICBob2xseUBob3RuZXduZXQuY29tOw== ------=_NextPart_000_02E2_01E9DE36.1CEB28A0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAw LjM3OTAuMzk1OSIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFk+DQo8UCBjbGFzcz1Nc29O b3JtYWwgc3R5bGU9Ik1BUkdJTjogMGNtIDBjbSAwcHQiPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZh bWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3 IFJvbWFuJyI+RGVhciANClB1cmNoYXNpbmcgTWFuYWdlciw8L1NQQU4+PFNQQU4gbGFuZz1FTi1V Uz48QlIgDQpzdHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOiBsaW5lLWJyZWFrIj48QlIgDQpz dHlsZT0ibXNvLXNwZWNpYWwtY2hhcmFjdGVyOiBsaW5lLWJyZWFrIj48L1NQQU4+PC9QPg0KPFAg Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSJNQVJHSU46IDBjbSAwY20gMHB0Ij48U1BBTiBsYW5nPUVO LVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsOyBtc28taGFu c2ktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYmlkaS1mb250LWZhbWlseTog J1RpbWVzIE5ldyBSb21hbiciPkdvb2QgDQptb3JuaW5nIG15IGZyaWVuZCA8L1NQQU4+PC9QPg0K PFAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSJNQVJHSU46IDBjbSAwY20gMHB0Ij48U1BBTiBsYW5n PUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsOyBtc28t aGFuc2ktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYmlkaS1mb250LWZhbWls eTogJ1RpbWVzIE5ldyBSb21hbiciPlRoYW5rcyANCmZvciB5b3VyIHRpbWUgdG8gcmVhZCBteSBl bWFpbDwvU1BBTj48L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9Ik1BUkdJTjogMGNtIDBj bSAwcHQiPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZB TUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1z by1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+R2xhZCANCnRvIGtub3cgeW91 IGFyZSBsZWFkaW5nIHJldGFpbCBvZiB0YWJsZXQgcGMuIDwvU1BBTj48L1A+DQo8UCBjbGFzcz1N c29Ob3JtYWwgc3R5bGU9Ik1BUkdJTjogMGNtIDBjbSAwcHQiPjxTUEFOIGxhbmc9RU4tVVMgDQpz dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250 LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMg TmV3IFJvbWFuJyI+V2UgDQphcmUgYSB0YWJsZXQgcGMgbWFudWZhY3R1cmVyIHdoaWNoIGV4cG9y dGVkIHRvIE5vcnRoIEFtZXJpY2EgYW5kIEV1cm9wZSBpbiANCkNoaW5hLjwvU1BBTj48L1A+DQo8 UCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9Ik1BUkdJTjogMGNtIDBjbSAwcHQiPjxTUEFOIGxhbmc9 RU4tVVM+PFNQQU4gDQpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPjwvU1BBTj48L1NQQU4+Jm5i c3A7PC9QPg0KPFAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSJNQVJHSU46IDBjbSAwY20gMHB0Ij48 QiANCnN0eWxlPSJtc28tYmlkaS1mb250LXdlaWdodDogbm9ybWFsIj48U1BBTiBsYW5nPUVOLVVT IA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsOyBtc28taGFuc2kt Zm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYmlkaS1mb250LWZhbWlseTogJ1Rp bWVzIE5ldyBSb21hbiciPlRhYmxldCANClBDIDcgaW5jaCB3aGljaCBpcyBzZWxsaW5nIHdlbGwg aW4gb3VyIG1hcmtldCA8L1NQQU4+PC9CPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1T SVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1Rp bWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+ YXMgDQpmb2xsb3dzOjxCUj48QiBzdHlsZT0ibXNvLWJpZGktZm9udC13ZWlnaHQ6IG5vcm1hbCI+ MSlQcmljZTo8L0I+PEJSPjxCIA0Kc3R5bGU9Im1zby1iaWRpLWZvbnQtd2VpZ2h0OiBub3JtYWwi PjxTUEFOIA0Kc3R5bGU9Im1zby1zcGFjZXJ1bjogeWVzIj4mbmJzcDsmbmJzcDsgPC9TUEFOPjUw MCBwaWVjZXM6PFNQQU4gDQpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPiZuYnNwOyZuYnNwOyA8 L1NQQU4+PC9CPjwvU1BBTj48QiANCnN0eWxlPSJtc28tYmlkaS1mb250LXdlaWdodDogbm9ybWFs Ij48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiDlrovkvZM7IG1z by1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1hc2NpaS1mb250LWZh bWlseTogQXJpYWwiPuOAgOOAgOOAgDwvU1BBTj48L0I+PEIgDQpzdHlsZT0ibXNvLWJpZGktZm9u dC13ZWlnaHQ6IG5vcm1hbCI+PFU+PFNQQU4gbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6 IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMg TmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj5VU0Qg DQo1MS45MChGT0IgU0hFTlpIRU4pPC9TUEFOPjwvVT48L0I+PFNQQU4gbGFuZz1FTi1VUyANCnN0 eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZvbnQt ZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1lcyBO ZXcgUm9tYW4nIj48QlI+PEIgDQpzdHlsZT0ibXNvLWJpZGktZm9udC13ZWlnaHQ6IG5vcm1hbCI+ PFNQQU4gDQpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPiZuYnNwOyZuYnNwOyA8L1NQQU4+MTAw MCBwaWVjZXM6IDwvQj48L1NQQU4+PEIgDQpzdHlsZT0ibXNvLWJpZGktZm9udC13ZWlnaHQ6IG5v cm1hbCI+PFNQQU4gDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTog5a6L5L2T OyBtc28taGFuc2ktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYXNjaWktZm9u dC1mYW1pbHk6IEFyaWFsIj7jgIDjgIDjgIA8L1NQQU4+PC9CPjxCIA0Kc3R5bGU9Im1zby1iaWRp LWZvbnQtd2VpZ2h0OiBub3JtYWwiPjxVPjxTUEFOIGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1T SVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1Rp bWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+ VVNEIA0KNTEuMDAoRk9CIFNIRU5aSEVOPC9TUEFOPjwvVT48L0I+PEIgc3R5bGU9Im1zby1iaWRp LWZvbnQtd2VpZ2h0OiBub3JtYWwiPjxTUEFOIA0KbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJ WkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGlt ZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj4p PC9TUEFOPjwvQj48U1BBTiANCmxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBG T05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21h bic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+PEJSPjIpYS5Wb2x1 bWU6PC9TUEFOPjxTUEFOIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IOWu i+S9kzsgbXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWFzY2lp LWZvbnQtZmFtaWx5OiBBcmlhbCI+44CA44CA44CA44CA44CAPC9TUEFOPjxTUEFOIA0KbGFuZz1F Ti1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhh bnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6 ICdUaW1lcyBOZXcgUm9tYW4nIj4wLjAwMDRDdWJpYyANCm1ldGVycy9wY3M8QlI+PFNQQU4gc3R5 bGU9Im1zby1zcGFjZXJ1bjogeWVzIj4mbmJzcDsmbmJzcDsgDQo8L1NQQU4+Yi5XZWlnaHQ6PC9T UEFOPjxTUEFOIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IOWui+S9kzsg bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWFzY2lpLWZvbnQt ZmFtaWx5OiBBcmlhbCI+44CA44CA44CA44CA44CAPC9TUEFOPjxTUEFOIA0KbGFuZz1FTi1VUyAN CnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZv bnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1l cyBOZXcgUm9tYW4nIj4zLjY1a2dzL2NhdG9uPEJSPjxTUEFOIA0Kc3R5bGU9Im1zby1zcGFjZXJ1 bjogeWVzIj4mbmJzcDsmbmJzcDsgPC9TUEFOPmMuUGFja2luZzo8L1NQQU4+PFNQQU4gDQpzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTog5a6L5L2TOyBtc28taGFuc2ktZm9udC1m YW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYXNjaWktZm9udC1mYW1pbHk6IEFyaWFsIj7j gIDjgIDjgIA8L1NQQU4+PFNQQU4gDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlM WTogQXJpYWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1i aWRpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+IA0KPC9TUEFOPjxTUEFOIA0Kc3R5 bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IOWui+S9kzsgbXNvLWhhbnNpLWZvbnQt ZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWFzY2lpLWZvbnQtZmFtaWx5OiBBcmlhbCI+ 44CAPC9TUEFOPjxTUEFOIA0KbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZP TlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFu JzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj4xMHBjcy9jYXJ0b248 QlI+MylNaW5pbXVtIA0KT3JkZXI6IDwvU1BBTj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDEw cHQ7IEZPTlQtRkFNSUxZOiDlrovkvZM7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5l dyBSb21hbic7IG1zby1hc2NpaS1mb250LWZhbWlseTogQXJpYWwiPuOAgOOAgDwvU1BBTj48U1BB TiANCmxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJp YWw7IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZv bnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+NTAwIA0KcGllY2VzPC9TUEFOPjwvUD4NCjxQ IGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOOiAwY20gMGNtIDBwdCI+PFNQQU4gbGFuZz1F Ti1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhh bnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1pbHk6 ICdUaW1lcyBOZXcgUm9tYW4nIj40KUxlYWRpbmcgDQp0aW1lOiA8L1NQQU4+PFNQQU4gDQpzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTog5a6L5L2TOyBtc28taGFuc2ktZm9udC1m YW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYXNjaWktZm9udC1mYW1pbHk6IEFyaWFsIj7j gIDjgIDjgIA8L1NQQU4+PFNQQU4gDQpsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBw dDsgRk9OVC1GQU1JTFk6IEFyaWFsOyBtc28taGFuc2ktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcg Um9tYW4nOyBtc28tYmlkaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbiciPjIwLTI1IA0K d29ya2luZ2RheXM8QlI+NSlQYXltZW50IFRlcm1zOiA8L1NQQU4+PFNQQU4gDQpzdHlsZT0iRk9O VC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTog5a6L5L2TOyBtc28taGFuc2ktZm9udC1mYW1pbHk6 ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYXNjaWktZm9udC1mYW1pbHk6IEFyaWFsIj7jgIA8L1NQ QU4+PFNQQU4gDQpsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1J TFk6IEFyaWFsOyBtc28taGFuc2ktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28t YmlkaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbiciPjxTUEFOIA0Kc3R5bGU9Im1zby1z cGFjZXJ1bjogeWVzIj4mbmJzcDsgPC9TUEFOPlQvVCAoMzAlIGRlcG9zaXQgYmVmb3JlIHByb2R1 Y3Rpb24sIDcwJSANCmJhbGFuY2UgYmVmb3JlIHNoaXBtZW50KTxCUj42KVF1YWxpdHk6IDwvU1BB Tj48U1BBTiANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiDlrovkvZM7IG1z by1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1hc2NpaS1mb250LWZh bWlseTogQXJpYWwiPuOAgOOAgOOAgOOAgOOAgDwvU1BBTj48U1BBTiANCmxhbmc9RU4tVVMgDQpz dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7IG1zby1oYW5zaS1mb250 LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAnVGltZXMg TmV3IFJvbWFuJyI+PFNQQU4gDQpzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPiZuYnNwOyA8L1NQ QU4+V2FycmFudHkgZm9yIG9uZSANCnllYXI8QlI+NylPcmRlcjo8L1NQQU4+PFNQQU4gDQpzdHls ZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTog5a6L5L2TOyBtc28taGFuc2ktZm9udC1m YW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nOyBtc28tYXNjaWktZm9udC1mYW1pbHk6IEFyaWFsIj7j gIDjgIDjgIDjgIDjgIDjgIA8L1NQQU4+PFNQQU4gDQpsYW5nPUVOLVVTIA0Kc3R5bGU9IkZPTlQt U0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsOyBtc28taGFuc2ktZm9udC1mYW1pbHk6ICdU aW1lcyBOZXcgUm9tYW4nOyBtc28tYmlkaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbici PjxTUEFOIA0Kc3R5bGU9Im1zby1zcGFjZXJ1bjogeWVzIj4mbmJzcDsgPC9TUEFOPldlbGNvbWUg T0VNIG9yZGVyczxCUiANCnN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6IGxpbmUtYnJlYWsi PjxCUiANCnN0eWxlPSJtc28tc3BlY2lhbC1jaGFyYWN0ZXI6IGxpbmUtYnJlYWsiPjwvU1BBTj48 L1A+DQo8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9Ik1BUkdJTjogMGNtIDBjbSAwcHQiPjxTUEFO IGxhbmc9RU4tVVMgDQpzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZBTUlMWTogQXJpYWw7 IG1zby1oYW5zaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbic7IG1zby1iaWRpLWZvbnQt ZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+SGF2ZSANCmEgbmljZSBkYXkhPC9TUEFOPjwvUD4N CjxQIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOOiAwY20gMGNtIDBwdCI+PFNQQU4gbGFu Zz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbDsgbXNv LWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1mYW1p bHk6ICdUaW1lcyBOZXcgUm9tYW4nIj48QlI+S2luZCANCnJlZ2FyZHMsPEJSPkhvbGx5PEJSPkUt bWFpbDo8U1BBTiBzdHlsZT0ibXNvLXNwYWNlcnVuOiB5ZXMiPiZuYnNwOyZuYnNwOyZuYnNwOyAN CjwvU1BBTj48L1NQQU4+PFU+PFNQQU4gbGFuZz1FTi1VUyBzdHlsZT0iQ09MT1I6IGJsdWUiPjxB IA0KaHJlZj0ibWFpbHRvOmhvbGx5QGhvdG5ld25ldC5jb20iPjwvQT48QSANCmhyZWY9Im1haWx0 bzpob2xseUBob3RuZXduZXQuY29tO2plc3NpMDA3MzFAaG90bWFpbC5jb20iPjxTUEFOIA0Kc3R5 bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6ICMwMDY4Y2Y7IEZPTlQtRkFNSUxZOiBBcmlhbDsg bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJzsgbXNvLWJpZGktZm9udC1m YW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj5ob2xseUBob3RuZXduZXQuY29tPC9TUEFOPjwvQT48 L1NQQU4+PC9VPjxTUEFOIA0KbGFuZz1FTi1VUyANCnN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZP TlQtRkFNSUxZOiBBcmlhbDsgbXNvLWhhbnNpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFu JzsgbXNvLWJpZGktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj47PC9TUEFOPjwvUD4N CjxQPiZuYnNwOzwvUD48L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_02E2_01E9DE36.1CEB28A0-- From info@webmaster.pl Wed Jan 11 00:13:20 2012 Return-Path: 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 5F9C221F879E; Wed, 11 Jan 2012 00:13:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.973 X-Spam-Level: **** X-Spam-Status: No, score=4.973 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_95=3, FH_RELAY_NODNS=1.451, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1, SARE_SUB_ENC_UTF8=0.152] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjow8CwaV4XR; Wed, 11 Jan 2012 00:13:20 -0800 (PST) Received: from mail.solca.med.ec (unknown [200.105.240.90]) by ietfa.amsl.com (Postfix) with ESMTP id 155C821F8772; Wed, 11 Jan 2012 00:13:18 -0800 (PST) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 7577119C012F; Wed, 11 Jan 2012 03:03:26 -0500 (ECT) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by mail.solca.med.ec (Postfix) with ESMTP id ADAC019C0AF3; Wed, 11 Jan 2012 03:03:06 -0500 (ECT) Received: from 41.138.191.14 (SquirrelMail authenticated user aacosta) by mail.solca.med.ec with HTTP; Wed, 11 Jan 2012 03:03:06 -0500 (ECT) Message-ID: <54418.41.138.191.14.1326268986.squirrel@mail.solca.med.ec> Date: Wed, 11 Jan 2012 03:03:06 -0500 (ECT) Subject: =?utf-8?B?V2VibWFzdGVyIHBvd2lhZG9taWXFhCEh4oCP4oCP4oCPICA=?= From: =?utf-8?B?V2VibWFzdGVyIEFrdHVhbGl6YWNqYSBXeWR6aWHFgg==?= Reply-To: customercarewebdept40@w.cn User-Agent: SquirrelMail/1.4.8-5.el5.centos.10 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal To: undisclosed-recipients:; X-TM-AS-Product-Ver: IMSS-7.1.0.1302-6.8.0.1017-18638.005 X-TM-AS-Result: No-0.555-4.5-31-10 X-imss-scan-details: No-0.555-4.5-31-10 X-TM-AS-User-Approved-Sender: No X-TMASE-MatchedRID: bF/ftEib5FfmR+RxuU2vfUwAZYE2FMixerJCitPoIIzfUZT83lbkEMWm DR829mMW+SihPPY9VI/SFZyaJmMIRq4HyN5VK32o3QfwsVk0UbsIoUKaF27lxe9ttG7ej8LDTf7 84XTH6n02i1vZX3Gk8jR5DBXp0fyKfL+lEnWkaa1YMZmn2SPR7wADRaWctxCv9lwBnJvrqCOKFQ bGqG+X5kV4mhCkeaWfaWNolBtQ1wbDHYSZWYRUCk9o3BPtf0h2+rL5VW+ofZc= Drodzy Widzowie konto e-mail, Ten komunikat jest od poczty centrum wiadomości do wszystkich na nasze konto poczty owners.As pierwszym kwartale 2012 r. Obecnie jest przeprowadzenie usługi aktualizacji dla naszej bazy i e-mail centrum konta. Jesteśmy usunięcie wszystkich niewykorzystanych konto poczty internetowej, aby utworzyć więcej miejsca dla nowych kont. Aby zapobiec koncie od usuwania i Aby kontynuować korzystanie z naszych usług, które są wymagane do aktualizacji i potwierdzenia konta webmail. Aby zakończyć potwierdzenia konta za pierwszy kwartał 2012 r. Jesteś odpowiedzieć na tę wiadomość natychmiast i wprowadź dane swojego konta w wymienionych poniżej. Potwierdzenie informacji o koncie Nazwa użytkownika: ...... E-mail Login ............ Hasło: .................. Potwierdź hasło :........ Data urodzenia: ......... Ważne * Proszę podać wszystkie te informacje kompletnie i prawidłowo w przeciwnym razie ze względów bezpieczeństwa być może będziemy musieli zamknąć temporarily.We konto poczty dziękuję za szybkie zajęcie się tą matter.Please zrozumieć, że jest to środek bezpieczeństwa przeznaczonych do ochrony użytkowników i konta poczty internetowej. Przepraszamy za wszelkie niedogodności. From ipp-bounces@pwg.org Wed Jan 11 04:38:27 2012 Return-Path: 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 3ED4621F8806 for ; Wed, 11 Jan 2012 04:38:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.157 X-Spam-Level: X-Spam-Status: No, score=-1.157 tagged_above=-999 required=5 tests=[AWL=-0.418, BAYES_20=-0.74, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEwVgZyitbB6 for ; Wed, 11 Jan 2012 04:38:26 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2B57821F866E for ; Wed, 11 Jan 2012 04:38:26 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 66CC97953C; Wed, 11 Jan 2012 07:38:02 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 7004779518 for ; Wed, 11 Jan 2012 07:37:46 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AigBAKKBDU8Nl9IPmWdsb2JhbAA/A4JOqhoiAQEBAQEICwsHFCWBdAUPAQwRAyQLLAEqBgwLAQdFEgEEEwifT40fAZJEiHwFgjljBIg6hH+aMA Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 11 Jan 2012 06:37:45 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 11 Jan 2012 04:37:32 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 11 Jan 2012 04:37:32 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: JPS3 comment on job-uuid thread-index: AczQXcmXsvWD0r0NTYKnufosFiOqAA== From: "Zehler, Peter" To: X-OriginalArrivalTime: 11 Jan 2012 12:37:32.0909 (UTC) FILETIME=[CA2881D0:01CCD05D] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] JPS3 comment on job-uuid X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2049574140==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 66CC97953C.A9134 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============2049574140== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCD05D.C9E6A3E5" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCD05D.C9E6A3E5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable For section 5.3.1 Can you add the clarification "The Printer, on receipt of a new job, generates the globally-unique identifier"? =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCD05D.C9E6A3E5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

For section 5.3.= 1

Can you add the clarification  &#= 8220;The Printer, on receipt of a new job, generates the globally-unique id= entifier”?

 

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441<= span style=3D'color:#1F497D'>
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
<= span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'= >Webster NY, 14580-9701

 

--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCD05D.C9E6A3E5-- --===============2049574140== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2049574140==-- From ipp-bounces@pwg.org Wed Jan 11 09:14:03 2012 Return-Path: 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 D580521F874A for ; Wed, 11 Jan 2012 09:14:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3NBA2HjwhYtk for ; Wed, 11 Jan 2012 09:14:02 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 880D021F8637 for ; Wed, 11 Jan 2012 09:14:02 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 74C1279591; Wed, 11 Jan 2012 12:13:45 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 2D8817958D for ; Wed, 11 Jan 2012 12:13:31 -0500 (EST) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXN009PC8PUPL41@mail-out.apple.com> for IPP@pwg.org; Wed, 11 Jan 2012 09:13:23 -0800 (PST) X-AuditID: 1180711d-b7b41ae000004823-ea-4f0dc333956f Received: from da0704a-dhcp197.apple.com (da0704a-dhcp197.apple.com [17.197.43.197]) by relay13.apple.com (Apple SCV relay) with SMTP id 52.DA.18467.333CD0F4; Wed, 11 Jan 2012 09:13:23 -0800 (PST) Subject: Re: [IPP] JPS3 comment on job-uuid From: Michael Sweet In-reply-to: Date: Wed, 11 Jan 2012 09:13:24 -0800 Message-id: <422F07AA-478F-4528-BC05-160839CAA727@apple.com> References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1255) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUieFT7qK7xYV5/gzfNBhbH9r1ksTjyLdai 48lKVgdmj60nf7B5zFs8nclj+an1bAHMUVw2Kak5mWWpRfp2CVwZv/4WF0y2rXh6ehZjA2OP WRcjJ4eEgInElr0LWSBsMYkL99azdTFycQgJHGOU+L/1FlhCWEBb4vGbHUAJDg5eAUOJB4d0 QMLMAgkSR641M4HYbAJqEr8n9bGC2JwCARILf95mBrFZBFQlXn1qZoOo55f49u4LI4jNK2Aj cfrHQrAaIQF/idOXVoHNERHQkdj4cD8zxD2yEs9m7WCfwMg3C2HzLCSbIWxtiWULXzND2AYS TztfsWKK60u8eTeHaQEj2ypGwaLUnMRKQ2O9xIKCnFS95PzcTYygkG0olN3BuP8n/yFGAQ5G JR7eHXt5/YVYE8uKK3MPMUpwMCuJ8DrVAIV4UxIrq1KL8uOLSnNSiw8xSnOwKInz1hay+wsJ pCeWpGanphakFsFkmTg4pRoY0xy+3CgUWhRmJrHI70iN0OvLGfnhZv3t0sadCpo+L+snXvKN WNd/sWvtJnOLctPnO3Z3CmgtcP+SxaR6yq3ytS3X1b7cPwWC+vpuvL8TY6x5pZu3WL35W3rw /0RPmcaUH4721/fNzi9hFjHe/Mzw/ZHmMwp3XA74O5nk3XW7O+uG46fjRWeUWIozEg21mIuK EwH25LI+VQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: IPP@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1742930781==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 74C1279591.A88BE X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1742930781== Content-type: multipart/alternative; boundary="Boundary_(ID_dZpFTEXTSCOR+oTtsTWNyg)" --Boundary_(ID_dZpFTEXTSCOR+oTtsTWNyg) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Pete, Sure. I'll also make the same clarification for document-uuid and subscrip= tion-uuid. On Jan 11, 2012, at 4:37 AM, Zehler, Peter wrote: > For section 5.3.1 > Can you add the clarification =93The Printer, on receipt of a new job, g= enerates the globally-unique identifier=94? >=20=20 >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_dZpFTEXTSCOR+oTtsTWNyg) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Pete,

Sure.  I'll also make the same clarification= for document-uuid and subscription-uuid.


On Jan 11, 2012, at 4:37 AM, Zehler, Peter wrote:
For section 5.3.1<= o:p>
Can you add the clarification  =93The Printer, on receipt = of a new job, generates the globally-unique identifier=94?
=
 
 <= /span>

-- 
This message has been scanned f= or viruses and 
danger= ous content by MailScanner, and is 
believed to be clean. ___________________________________= ____________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

_________________________________________________= ________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_dZpFTEXTSCOR+oTtsTWNyg)-- --===============1742930781== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1742930781==-- From ipp-bounces@pwg.org Fri Jan 13 09:43:11 2012 Return-Path: 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 36D1C21F8518 for ; Fri, 13 Jan 2012 09:43:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93i2dvWmsFe2 for ; Fri, 13 Jan 2012 09:43:10 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1186E21F8539 for ; Fri, 13 Jan 2012 09:43:09 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 216417956E; Fri, 13 Jan 2012 12:42:44 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from g6t0187.atlanta.hp.com (g6t0187.atlanta.hp.com [15.193.32.64]) by pwg.org (Postfix) with ESMTP id 26A897952C for ; Fri, 13 Jan 2012 12:42:28 -0500 (EST) Received: from G4W3011G.americas.hpqcorp.net (g4w3011g.houston.hp.com [16.234.25.125]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0187.atlanta.hp.com (Postfix) with ESMTPS id 662EE284EA for ; Fri, 13 Jan 2012 17:42:28 +0000 (UTC) Received: from G9W1579G.americas.hpqcorp.net (16.216.212.153) by G4W3011G.americas.hpqcorp.net (16.234.25.125) with Microsoft SMTP Server (TLS) id 14.1.289.1; Fri, 13 Jan 2012 17:41:47 +0000 Received: from G9W0725.americas.hpqcorp.net ([169.254.8.28]) by G9W1579G.americas.hpqcorp.net ([16.216.212.153]) with mapi id 14.01.0289.001; Fri, 13 Jan 2012 17:41:47 +0000 From: "Berkema, Alan C (R&D Roseville)" To: "ipp@pwg.org" Thread-Topic: USB-IF DWG IPP over USB Participation Thread-Index: AczRb/N2X9m4jLpXTn6NQ0UXbl8ekQAqlc+Q Date: Fri, 13 Jan 2012 17:41:46 +0000 Message-ID: <89DCC0994718FC40817B8AAD0ED3386007EFC6@G9W0725.americas.hpqcorp.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-hashedpuzzle: AZOg BM08 BNPx BZO9 Bgch Cbrn Cjhm C2Bb EqbP E7sH IHa/ J7Pr KM// KPcB KQZ6 L/8W; 1; aQBwAHAAQABwAHcAZwAuAG8AcgBnAA==; Sosha1_v1; 7; {4A494F01-F994-4F9E-987D-2A61E8C164DA}; YQBsAGEAbgAtAGMALgBiAGUAcgBrAGUAbQBhAEAAaABwAC4AYwBvAG0A; Fri, 13 Jan 2012 17:41:44 GMT; VQBTAEIALQBJAEYAIABEAFcARwAgAEkAUABQACAAbwB2AGUAcgAgAFUAUwBCACAAUABhAHIAdABpAGMAaQBwAGEAdABpAG8AbgA= x-cr-puzzleid: {4A494F01-F994-4F9E-987D-2A61E8C164DA} x-originating-ip: [16.216.12.10] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] USB-IF DWG IPP over USB Participation X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1792797519==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 216417956E.A9EF5 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1792797519== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_89DCC0994718FC40817B8AAD0ED3386007EFC6G9W0725americashp_" --_000_89DCC0994718FC40817B8AAD0ED3386007EFC6G9W0725americashp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, We have been making progress on the IPP over USB specification since an ear= ly draft was posted to the PWG site some time ago. The IPP over USB specification will an Amendment to the Universal Serial Bus Device Class Definition for Printing Devices version 1.1 The Amendment adds Protocol Interface type 4 for IPP Defines Device Descriptors for IPP Requires that Devices Implement at least two Interfaces We are very close to critical mass and plan on working on the specification= in the USB-IF very soon. Of course we welcome additional input. To join the group, please execute the USB-IF IP agreement at: https://www.usb.org/apps/org/workgroup/dwg/documents.php The title of the document is: USB - IP Agreement IPP Over USB.pdf Thanks, Alan Berkema Hewlett Packard --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_89DCC0994718FC40817B8AAD0ED3386007EFC6G9W0725americashp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

We have been making prog= ress on the IPP over USB specification since an early draft was posted to t= he PWG site some time ago.

The IPP over USB specification will an Amendment to the Universal Serial Bus

Device Class Definition for Printing Devices version 1.1=

 

The Amendment adds

 

           Pro= tocol Interface type 4 for IPP

           Def= ines Device Descriptors for IPP

           Req= uires that Devices Implement at least two Interfaces

 

We are very close to critical mass and plan on working on the sp= ecification in the USB-IF very soon.

 

Of course we welcome additional input.

 

To join the group, please execute the USB-IF IP agreement at:

https://www.usb.org/apps/org/workgroup/dwg/d= ocuments.php

 

The title of the document is:

USB - IP Agreement IPP Over USB.pdf

 

Thanks,

Alan Berkema

Hewlett Packard

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_89DCC0994718FC40817B8AAD0ED3386007EFC6G9W0725americashp_-- --===============1792797519== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1792797519==-- From ipp-bounces@pwg.org Sat Jan 14 05:06:57 2012 Return-Path: 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 1EDF321F852D for ; Sat, 14 Jan 2012 05:06:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.003 X-Spam-Level: X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[AWL=0.595, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8+RAeawGry2 for ; Sat, 14 Jan 2012 05:06:56 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1444D21F84BD for ; Sat, 14 Jan 2012 05:06:56 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CB066795BD; Sat, 14 Jan 2012 08:06:28 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR002.ACS-INC.COM (usa7109mr002.acs-inc.com [63.101.151.11]) by pwg.org (Postfix) with ESMTP id B535179591 for ; Sat, 14 Jan 2012 08:06:12 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjMBAN18EU8Nh9IPmWdsb2JhbABAA4JNqmgiAQEBAQEICwsHFCWBdAUPAQwRAyQLLAEqBgwLAQdFEgEEEwiecY0fAZIgiHYFgjljBIg7hQCaOA Received: from usa0300gw002.na.xerox.net ([13.135.210.15]) by USA7109MR002.ACS-INC.COM with ESMTP; 14 Jan 2012 07:05:28 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 14 Jan 2012 08:05:28 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 14 Jan 2012 05:05:38 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: JPS3 comment thread-index: AczSvS+1a3blpj6aRcmWBYC59rfVCA== From: "Zehler, Peter" To: X-OriginalArrivalTime: 14 Jan 2012 13:05:28.0371 (UTC) FILETIME=[300CF830:01CCD2BD] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] JPS3 comment X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1903916987==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: CB066795BD.A9A7D X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1903916987== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCD2BD.2F4E7ABB" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCD2BD.2F4E7ABB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Is the intention of "requesting-user-uri" to be used in place of "requesting-user-name". If it is, then section 5.1.5 should clarify. If not, then section 5.1.5 should clarify what happens when both are supplied. I favor making it one or the other.=20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCD2BD.2F4E7ABB Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Is the intention= of “requesting-user-uri” to be used in place of “request= ing-user-name”.  If it is, then section 5.1.5 should clarify.&nb= sp; If not, then section 5.1.5 should clarify what happens when both are su= pplied.  I favor making it one or the other.

 

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com=
Voice: (585) 265-8755
= FAX: (585) 265-7441
US Mail: Peter Zehler
X= erox Corp.
800 Phillips Rd= .
M/S 128-25E
Webster NY, 14580-9701

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCD2BD.2F4E7ABB-- --===============1903916987== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1903916987==-- From ipp-bounces@pwg.org Sat Jan 14 09:36:43 2012 Return-Path: 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 88B2A21F8545 for ; Sat, 14 Jan 2012 09:36:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.929 X-Spam-Level: X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.669, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49FkNEu-zfFd for ; Sat, 14 Jan 2012 09:36:42 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 192CA21F850D for ; Sat, 14 Jan 2012 09:36:42 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8178F795C6; Sat, 14 Jan 2012 12:36:18 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by pwg.org (Postfix) with ESMTP id ECDFE795C2 for ; Sat, 14 Jan 2012 12:36:03 -0500 (EST) Received: by werb13 with SMTP id b13so1411008wer.5 for ; Sat, 14 Jan 2012 09:36:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=iViIPbet8/VMHDxhvjXclN/F1sx9fMn/SyHz96vZoq0=; b=tcxPBfrCpqqpRnJbIhnYN34OhupDEPD3RFKRw73S33qxbBw0Za4+wgqmmOPV7t9UUU wUO0zibUJzuoZTk3CY0+XVmyEbj/RUriAMtCR6sOKcHmoAVfzrowsHjdPvAct1C9cavs GhcEpYzMPknAY0NfKR+RjoV7mClrymnzfSpUE= MIME-Version: 1.0 Received: by 10.216.134.137 with SMTP id s9mr2371141wei.16.1326562563057; Sat, 14 Jan 2012 09:36:03 -0800 (PST) Received: by 10.223.155.10 with HTTP; Sat, 14 Jan 2012 09:36:00 -0800 (PST) Date: Sat, 14 Jan 2012 12:36:00 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - 2-3pm EST Monday 16 January 2012 (after Cloud) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1856004855==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 8178F795C6.A9E81 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1856004855== Content-Type: multipart/alternative; boundary=001636ef0ccf57e83904b6806afd --001636ef0ccf57e83904b6806afd Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be next Monday for ONE HOUR, immediately following the Cloud Imaging WG call. Monday 16 January 11am-12pm US PST / 2-3pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. Live Meeting Info (courtesy of Pete Zehler): Link: https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn URL: https://www.livemeeting.com/cc/xerox/join Meeting ID: PwgSemanticModel Entry Code: LetMeIn *** Main Objective - Complete review of PWG Raster *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120109.pdf (3) Complete review of PWG Raster - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20111202-rev.pdf - resume at section 5.1.2 (4) Next Steps - IPP WG on Monday 23 January - prepare for February PWG F2F at Canon - IPP WG on Tuesday 7 February 1-5pm US PST - at Canon in Irvine, CA - IPP WG on Wednesday 8 February 1-5pm US PST - at Canon in Irvine, CA Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --001636ef0ccf57e83904b6806afd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our next IPP WG call will be next Monday for ONE HOUR,
immedi= ately following the Cloud Imaging WG call.

=A0 Monday 16 January 11am-12pm US PST / 2-3pm US EST

=A0 Call-in toll-free number (US/Canada): 1-866-469-3239
=A0 Call-in toll number (US/Canada): 1-650-429-3300 (Primary)
=A0 Call-in toll number (US/Canada): 1-408-856-9570 (Backup)

=A0 Attendee Access Code: *******#
=A0 Attendee ID Code: # (empty)

If you need the Attendee Access code, please email me a request.

Live Meeting Info (courtesy of Pete Zehler):

=A0 Link: https://www.livemeeting.com/cc/xerox/join?id=3DPwgSemanticModel&role= =3Dattend&pw=3DLetMeIn
=A0 URL: https://www.livemeeting.com/cc/xerox/join
=A0 Meeting ID: PwgS= emanticModel
=A0 Entry Code: LetMeIn


*** Main Objective - Complete review of PWG Raster ***

Agenda:

(1) PWG IP Policy and Minute Taker
=A0 =A0=A0 - Mike?

(2) Approve IPP minutes from previous meeting
=A0=A0 =A0 - = ftp://ftp.pwg.or= g/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120109.pdf

(3) Complete review of PWG Raster
=A0=A0=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippr= aster10-20111202-rev.pdf
=A0=A0=A0=A0 - resume at section 5.1.2
=A0=A0
(4) Next Steps
=A0=A0=A0=A0 - IPP WG on Monday 23 January - p= repare for February PWG F2F at Canon
=A0=A0=A0=A0 - IPP WG on Tuesday 7 = February 1-5pm US PST - at Canon in Irvine, CA
=A0=A0=A0=A0 - IPP WG on = Wednesday 8 February 1-5pm US PST - at Canon in Irvine, CA

Cheers,
- Ira

Ira McDonald (Musician / Software= Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEE= E-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair= - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --001636ef0ccf57e83904b6806afd-- --===============1856004855== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1856004855==-- From ipp-bounces@pwg.org Sun Jan 15 09:21:55 2012 Return-Path: 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 B014021F8480 for ; Sun, 15 Jan 2012 09:21:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.102 X-Spam-Level: X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5BBEdPZI9bZ for ; Sun, 15 Jan 2012 09:21:54 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB0021F8468 for ; Sun, 15 Jan 2012 09:21:54 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B9CF67962B; Sun, 15 Jan 2012 12:21:31 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR003.ACS-INC.COM (usa7109mr003.acs-inc.com [63.101.151.12]) by pwg.org (Postfix) with ESMTP id A818379626 for ; Sun, 15 Jan 2012 12:21:15 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvQBALsJE08Nl9IPmWdsb2JhbABBA4JNqmoiAQEBAQEICwsbJYF0BQ8BDBEDJAssASoGDAsBB0USAQQTCJ1ojR8BkWGIdgWCOWMEiDuFAJo4 Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR003.ACS-INC.COM with ESMTP; 15 Jan 2012 11:21:13 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 15 Jan 2012 09:21:13 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 15 Jan 2012 09:21:22 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: JPS3 comment on xxx-preferred thread-index: AczTqhnnrdsJPZsuS9yOTaH4/KMgDA== From: "Zehler, Peter" To: X-OriginalArrivalTime: 15 Jan 2012 17:21:13.0644 (UTC) FILETIME=[14F58EC0:01CCD3AA] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] JPS3 comment on xxx-preferred X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1614291481==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: B9CF67962B.A935E X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1614291481== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCD3AA.14C07E45" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCD3AA.14C07E45 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Why do we have a bunch of xxx-preferred attributes? It complicates the model with a bunch of attributes and is not general purpose enough to address all the possible conflicting attributes and values.=20 =20 Is there any reason we cannot provide this functionality in a manner similar to "unsupported-attributes". The "unsupported-attributes" is handled in IPP as an out of band group in an IPP response. We could extend the encoding of out of band attributes to include a new group for "xxx-preferred" . That way any substituted or conflicting attributes and values could be returned for a Validate operation. I would prefer to handle "xxx-preferred" using the collection syntax. I think it is easier and requires fewer changes to the IPP encoding. Defining "attributes-preferred" as a collection of attributes and permitting any template attributes to be included would be a simple generalization. It would also allow a client to pick those attribute/values out to correct their request and not rely on printer substitution. =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCD3AA.14C07E45 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Why do we have a= bunch of xxx-preferred attributes?  It complicates the model with a b= unch of attributes and is not general purpose enough to address all the pos= sible conflicting attributes and values.

 

Is there any reason we cannot = provide this functionality in a manner similar to “unsupported-attrib= utes”.  The “unsupported-attributes” is handled in I= PP as an out of band group in an IPP response.   We could extend = the encoding of out of band attributes to include a new group for “xx= x-preferred” .  That way any substituted or conflicting attribut= es and values could be returned for a Validate operation.

I would prefer to ha= ndle “xxx-preferred” using the collection syntax.  I think= it is easier and requires fewer changes to the IPP encoding.  Definin= g “attributes-preferred” as a collection of attributes and perm= itting any template attributes to be included would be a simple generalizat= ion.  It would also allow a client to pick those attribute/values out = to correct their request and not rely on printer substitution.

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-87= 55
FAX: (585) 265-7441
US Mail: Peter Zehler<= span style=3D'color:#1F497D'>
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCD3AA.14C07E45-- --===============1614291481== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1614291481==-- From comercial@francisco-oliveira.com Mon Jan 16 03:43:53 2012 Return-Path: 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 224CF21F85B9 for ; Mon, 16 Jan 2012 03:43:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.401 X-Spam-Level: **** X-Spam-Status: No, score=4.401 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQ0P1kISRPoF for ; Mon, 16 Jan 2012 03:43:51 -0800 (PST) Received: from iberweb-12a.ibername.com (iberweb-12a.ibername.com [188.93.230.135]) by ietfa.amsl.com (Postfix) with ESMTP id A33C321F85C0 for ; Mon, 16 Jan 2012 03:43:50 -0800 (PST) Received: from bl7-251-157.dsl.telepac.pt ([85.240.251.157] helo=fos5mkgugpcpfe) by iberweb-12a.ibername.com with esmtpa (Exim 4.69) (envelope-from ) id 1RmkKd-0001Vr-IB; Mon, 16 Jan 2012 11:02:33 +0000 From: =?iso-8859-1?Q?EasyNet4You_-_Constru=E7=E3o_e_Manuten=E7=E3o_de_Sites?= To: Subject: =?iso-8859-1?Q?Fazemos_Sites_na_Internet_-_6_euros_/_m=EAs_-_N/Ref:_116110?= Date: Mon, 16 Jan 2012 11:00:23 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_3EEF_01CCD43E.0D590360" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AczUPguWNMcs3eckQ9OO7txe8OFpUA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - iberweb-12a.ibername.com X-AntiAbuse: Original Domain - lists.ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - francisco-oliveira.com Message-Id: <20120116114350.A33C321F85C0@ietfa.amsl.com> This is a multi-part message in MIME format. ------=_NextPart_000_3EEF_01CCD43E.0D590360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable EasyNet4You - Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet=20 Website: www.easynet4you.com =20 E-Mail: easynet4you@gmail.com=20 Rua Filipe Folque, N=BA 10 G =96 Apartado 12058=20 1061- 001 Lisboa=20 Assunto: Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet ( 6 euros = / m=EAs ).=20 Podem ter o Site da vossa Empresa na Internet em 5 dias uteis por 6 = euros / m=EAs (este valor inclui a Constru=E7=E3o do Site, Alojamento, Dominio, = E-Mails, e Manuten=E7=E3o), se no entanto n=E3o tiverem neste momento verba = disponivel e se mesmo assim gostassem de ter um Site, n=F3s tamb=E9m disponibilizamos = uma op=E7=E3o de Sites Gratuitos, em que podem ter um Site mais elementar mas = igualmente eficaz, com Design Atrativo, completamente gratuito, totalmente = configur=E1vel com v=E1rios Designs e possibilidade de alterar conte=FAdos, de imediato = e em menos de 15 minutos, basta fazerem o registo no nosso Site ! =C9 fundamental para qualquer Actividade assegurar a sua presen=E7a com = um Site na Internet, pois porporciona:=20 - Melhoria da Imagem Corporativa=20 - Melhoria do Servi=E7o a Clientes=20 - Melhoria da Comunica=E7=E3o=20 - Expans=E3o=20 - Novas oportunidades de neg=F3cio=20 - Transac=E7=F5es On-Line=20 - Redu=E7=E3o de Custos=20 - Informa=E7=E3o sempre disponivel, 24 horas / 7 dias da semana=20 Estas s=E3o apenas algumas das vantagens de estar na Internet. S=E3o = muitos os benef=EDcios que podem ser obtidos utilizando a tecnologia certa e a = grande rede da Internet. Temos experi=EAncia em criar Sites para v=E1rias = =E1reas de neg=F3cio, e em trabalhos, desde Lojas Virtuais e Sites altamente = din=E2micos, at=E9 trabalhos de simples p=E1ginas, est=E1ticas, de presen=E7a na = Internet.=20 Apostamos fortemente em solu=E7=F5es de qualidade feitas =E0 medida, personaliz=E1veis ao gosto do cliente, baixo custo, tempos m=EDnimos de desenvolvimento, rela=E7=E3o f=E1cil e flexivel sem burocracias e = on-line, assist=EAncia 24/7, e servidores dedicados que garantem alta = disponibilidade, e grande velocidade de acesso. Se estiver interessado em saber mais informa=E7=F5es sobre os nossos = servi=E7os poder=E1 consultar o nosso Site www.easynet4you.com, ou entrar em = contacto connosco para o e-mail easynet4you@gmail.com, que teremos todo o gosto = em esclarecer e aprsesentar as nossas melhores solu=E7=F5es para o vosso = caso. Sem outro assunto de momento, e agrade=E7endo antecipadamente a = aten=E7=E3o que V. Exas ir=E3o prestar ao assunto, subscrevo-mos-nos. Com os melhores cumprimentos, e considera=E7=E3o,=20 EasyNet4You =96 Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet=20 www.easynet4you.com=20 easynet4you@gmail.com=20 Nota: Se n=E3o quiser receber mais correspond=EAncia nossa, poder=E1 = retirar o seu endere=E7o desta lista de distribui=E7=E3o no seguinte endere=E7o http://www.francisco-oliveira.com/retirar.htm Note: If don't want to receive more e-mails from us, you will be able to remove your address from this distribution list in the following address http://www.francisco-oliveira.com/retirar.htm ------=_NextPart_000_3EEF_01CCD43E.0D590360 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

EasyNet4You - Constru=E7=E3o e = Manuten=E7=E3o de Sites na Internet
Website: www.easynet4you.com  =
E-Mail: easynet4you@gmail.com
Rua Filipe Folque, N=BA 10 G = – Apartado 12058
1061- 001 Lisboa

Assunto: Constru=E7=E3o e = Manuten=E7=E3o de Sites na Internet ( 6 euros / m=EAs ).

Podem ter o Site da vossa Empresa na = Internet em 5 dias uteis por 6 euros / m=EAs (este valor inclui a = Constru=E7=E3o do Site, Alojamento, Dominio, E-Mails, e Manuten=E7=E3o), = se no entanto n=E3o tiverem neste momento verba disponivel e se mesmo = assim gostassem de ter um Site, n=F3s tamb=E9m disponibilizamos uma = op=E7=E3o de Sites Gratuitos, em que podem ter um Site mais elementar = mas igualmente eficaz, com Design Atrativo, completamente gratuito, = totalmente configur=E1vel com v=E1rios Designs e possibilidade de = alterar conte=FAdos, de imediato e em menos de 15 minutos, basta fazerem = o registo no nosso Site !

=C9 fundamental para qualquer = Actividade assegurar a sua presen=E7a com um Site na Internet, pois = porporciona:

- Melhoria da Imagem Corporativa
- Melhoria do Servi=E7o a = Clientes
- Melhoria da Comunica=E7=E3o
- Expans=E3o
- Novas oportunidades de = neg=F3cio
- Transac=E7=F5es On-Line
- Redu=E7=E3o de Custos
- Informa=E7=E3o sempre disponivel, 24 = horas / 7 dias da semana

Estas s=E3o apenas algumas das = vantagens de estar na Internet. S=E3o muitos os benef=EDcios que podem = ser obtidos utilizando a tecnologia certa e a grande rede da Internet. = Temos experi=EAncia em criar Sites para v=E1rias =E1reas de neg=F3cio, e = em trabalhos, desde Lojas Virtuais e Sites altamente din=E2micos, at=E9 = trabalhos de simples p=E1ginas, est=E1ticas, de presen=E7a na Internet. =

Apostamos fortemente em solu=E7=F5es de = qualidade feitas =E0 medida, personaliz=E1veis ao gosto do cliente, = baixo custo, tempos m=EDnimos de desenvolvimento, rela=E7=E3o f=E1cil e = flexivel sem burocracias e on-line, assist=EAncia 24/7, e servidores = dedicados que garantem alta disponibilidade, e grande velocidade de = acesso.

Se estiver interessado em saber mais = informa=E7=F5es sobre os nossos servi=E7os poder=E1 consultar o nosso = Site www.easynet4you.com, ou entrar em contacto connosco para o e-mail = easynet4you@gmail.com, que teremos todo o gosto em esclarecer e = aprsesentar as nossas melhores solu=E7=F5es para o vosso = caso.

Sem outro assunto de momento, e = agrade=E7endo antecipadamente a aten=E7=E3o que V. Exas ir=E3o prestar = ao assunto, subscrevo-mos-nos.

Com os melhores cumprimentos, e = considera=E7=E3o,
EasyNet4You – = Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet
www.easynet4you.com
easynet4you@gmail.com


Nota: Se n=E3o quiser receber mais = correspond=EAncia nossa, poder=E1 retirar o seu endere=E7o desta lista = de distribui=E7=E3o no seguinte endere=E7o http://www.francis= co-oliveira.com/retirar.htm

Note: If don't want to receive more = e-mails from us, you will be able to remove your address from this = distribution list in the following address http://www.francis= co-oliveira.com/retirar.htm

------=_NextPart_000_3EEF_01CCD43E.0D590360-- From ipp-bounces@pwg.org Mon Jan 16 09:27:20 2012 Return-Path: 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 A833921F86B3 for ; Mon, 16 Jan 2012 09:27:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2CnO0O+2zFr for ; Mon, 16 Jan 2012 09:27:19 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id C012221F86A4 for ; Mon, 16 Jan 2012 09:27:19 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 43FBC79510; Mon, 16 Jan 2012 12:26:59 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 3B124793C2 for ; Mon, 16 Jan 2012 12:26:43 -0500 (EST) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXW00804J4GC1A0@mail-out.apple.com> for IPP@pwg.org; Mon, 16 Jan 2012 09:26:42 -0800 (PST) X-AuditID: 11807130-b7c59ae000007da2-b2-4f145dd28326 Received: from da0704a-dhcp133.apple.com (da0704a-dhcp133.apple.com [17.197.43.133]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 34.E5.32162.2DD541F4; Mon, 16 Jan 2012 09:26:42 -0800 (PST) Subject: Re: [IPP] JPS3 comment on xxx-preferred From: Michael Sweet In-reply-to: Date: Mon, 16 Jan 2012 09:26:42 -0800 Message-id: <2CA31420-E9C7-429D-A8CD-BD9490D5DC66@apple.com> References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1416) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUieFS7VfdSrIi/wYb3AhbH9r1ksTjyLdai 48lKVgdmj60nf7B5zFs8nclj+an1bAHMUVw2Kak5mWWpRfp2CVwZr69+YC94rVvRsWwbawPj XfUuRk4OCQETibafExghbDGJC/fWs3UxcnEICaxikpi9YBUbSEJYwEBi5p7TrF2MHBy8AnoS Z1fEgISZBRIkDk+8zg5iswmoSfye1McKYnMKBEhcvjsdbCaLgKrEmv3tbBD1/BLf3n0Bi/MK 2Ejsu3QFrF5IwF+i++o6ZhBbREBHYuPD/cwgqyQEZCX+ndeYwMg3C2HxLCSLIWxtiWULXzND 2AYSTztfsWKK60u8eTeHaQEj2ypGwaLUnMRKQ0O9xIKCnFS95PzcTYygkG0oNNjBuPYn/yFG AQ5GJR7em94i/kKsiWXFlbmHGCU4mJVEeAV9gEK8KYmVValF+fFFpTmpxYcYpTlYlMR5PRby +QsJpCeWpGanphakFsFkmTg4pRoYZ380/Pykd/G/wq6LRaZC3rlddd8uxUT86YqxEzw3j8G6 N/uN/jL/hv+6nPVyVYKbBU7Ndbzk5l3vlLV4ltf3hyZZbwUW/c/V/MBk1mdc1P5exXKiOE+H U+FWx2+ls50XO534I5l2LWPVn7DddRPZebaUJ25j9areGXT80arc+k7z487Sge+VWIozEg21 mIuKEwFB8RMRVQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: IPP@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0374147351==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 43FBC79510.A945F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0374147351== Content-type: multipart/alternative; boundary="Boundary_(ID_rWgw1g0XrDbd5ICO+ZPGpQ)" --Boundary_(ID_rWgw1g0XrDbd5ICO+ZPGpQ) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable On Jan 15, 2012, at 9:21 AM, Zehler, Peter wrote: > Why do we have a bunch of xxx-preferred attributes? It complicates the m= odel with a bunch of attributes and is not general purpose enough to addres= s all the possible conflicting attributes and values. The idea was to have a -preferred attribute for every job/document template= attribute that could cause a conflict. > ... > I would prefer to handle =93xxx-preferred=94 using the collection syntax.= I think it is easier and requires fewer changes to the IPP encoding. Def= ining =93attributes-preferred=94 as a collection of attributes and permitti= ng any template attributes to be included would be a simple generalization.= It would also allow a client to pick those attribute/values out to correc= t their request and not rely on printer substitution. I prefer (no pun intended) the collection attribute syntax rather than intr= oducing another attribute group tag. In the definition for IPP, would you = envision this being returned in the unsupported attributes group or in the = job/document attributes group? __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_rWgw1g0XrDbd5ICO+ZPGpQ) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable
=
Why do we have a bun= ch of xxx-preferred attributes?  It complicates the model with a bunch= of attributes and is not general purpose enough to address all the possibl= e conflicting attributes and values.
The idea was to have a -preferred attribute for every job/document t= emplate attribute that could cause a conflict.

<= o:p>
...
I would prefer to handle =93xxx-preferred= =94 using the collection syntax.  I think it is easier and requires fe= wer changes to the IPP encoding.  Defining =93attributes-preferred=94 = as a collection of attributes and permitting any template attributes to be = included would be a simple generalization.  It would also allow a clie= nt to pick those attribute/values out to correct their request and not rely= on printer substitution.

I pr= efer (no pun intended) the collection attribute syntax rather than introduc= ing another attribute group tag.  In the definition for IPP, would you= envision this being returned in the unsupported attributes group or in the= job/document attributes group?

_______________________________________________= ___
Michael Sweet, Senior Printing System Engineer, PWG Chai= r


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_rWgw1g0XrDbd5ICO+ZPGpQ)-- --===============0374147351== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0374147351==-- From ipp-bounces@pwg.org Mon Jan 16 10:04:39 2012 Return-Path: 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 1B21A21F86BB for ; Mon, 16 Jan 2012 10:04:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1bZB-dLLxBh for ; Mon, 16 Jan 2012 10:04:38 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7E95A21F86BA for ; Mon, 16 Jan 2012 10:04:37 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B043779628; Mon, 16 Jan 2012 13:04:17 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 30B5B79613 for ; Mon, 16 Jan 2012 13:04:03 -0500 (EST) MIME-version: 1.0 Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LXW00K4TKUQY172@mail-out.apple.com> for IPP@pwg.org; Mon, 16 Jan 2012 10:04:02 -0800 (PST) X-AuditID: 11807137-b7b7fae000005b9a-de-4f14669232d5 Received: from da0704a-dhcp133.apple.com (da0704a-dhcp133.apple.com [17.197.43.133]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 03.AE.23450.296641F4; Mon, 16 Jan 2012 10:04:02 -0800 (PST) Subject: Re: [IPP] JPS3 comment From: Michael Sweet In-reply-to: Date: Mon, 16 Jan 2012 10:03:59 -0800 Message-id: References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1416) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUieFS7VXdSmoi/wbvZahbH9r1ksTjyLdai 48lKVgdmj60nf7B5zFs8nclj+an1bAHMUVw2Kak5mWWpRfp2CVwZRz89YCqY6FAx6+EGlgbG ORZdjJwcEgImEgt7fzBB2GISF+6tZ+ti5OIQEljFJHFkzyM2kISwgLzEw56djF2MHBy8AnoS Z1fEgISZBRIk/vYfB+tlE1CT+D2pjxXE5hQIkNix4BwziM0ioCox4UgvK0Q9v8S3d18YQWxe ARuJNz+fgdlCAv4Sizo2s4DYIgI6Ehsf7mcGWSUhICvx77zGBEa+WQiLZyFZDGFrSyxb+JoZ wjaQeNr5ihVTXF/izbs5TAsY2VYxChal5iRWGprpJRYU5KTqJefnbmIEhWxDofkOxu1/5Q4x CnAwKvHw3vQW8RdiTSwrrsw9xCjBwawkwivoAxTiTUmsrEotyo8vKs1JLT7EKM3BoiTO+yYO KCWQnliSmp2aWpBaBJNl4uCUamA8vOkUjzrvQjWhZduPdxs7Tch7X778bKJTyMkdRu9z2A/o eU/7xfbyzGSZ+4UP+K731DTczp9teOP74bvLPsdd8VqTIy0xoUxKkq+zRaeJefbHhZ0nQtQn HbTrfzN12g6FL7k1/54VJbVf+OS9c+Inw0+p8gk7bp0O2KW0fGl3rLvAjJDTFx0klFiKMxIN tZiLihMBuvp5e1UCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: IPP@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0024702054==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: B043779628.AA623 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0024702054== Content-type: multipart/alternative; boundary="Boundary_(ID_jlxHenFiYUeTh2qWo182Pg)" --Boundary_(ID_jlxHenFiYUeTh2qWo182Pg) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Pete, On Jan 14, 2012, at 5:05 AM, Zehler, Peter wrote: > Is the intention of =93requesting-user-uri=94 to be used in place of =93r= equesting-user-name=94. If it is, then section 5.1.5 should clarify. If n= ot, then section 5.1.5 should clarify what happens when both are supplied. = I favor making it one or the other. requesting-user-uri is the more-specific (i.e. should be unique) value, but= conceptually a client would supply both since the printer may not be able = to map the URI to a human-readable name (like that provided in requesting-u= ser-name...) I can clarify this in the next update of JPS3. >=20=20 >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_jlxHenFiYUeTh2qWo182Pg) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable
Is the = intention of =93requesting-user-uri=94 to be used in place of =93requesting= -user-name=94.  If it is, then section 5.1.5 should clarify.  If = not, then section 5.1.5 should clarify what happens when both are supplied.=   I favor making it one or the other.

requesting-user-uri is the more-specific (i.e. should be uniqu= e) value, but conceptually a client would supply both since the printer may= not be able to map the URI to a human-readable name (like that provided in= requesting-user-name...)

I can clarify this in th= e next update of JPS3.

_______________________________________= ___________
Michael Sweet, Senior Printing System Engineer, = PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_jlxHenFiYUeTh2qWo182Pg)-- --===============0024702054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0024702054==-- From ipp-bounces@pwg.org Mon Jan 16 10:40:51 2012 Return-Path: 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 2528621F8699 for ; Mon, 16 Jan 2012 10:40:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8eIbRfOKNhT5 for ; Mon, 16 Jan 2012 10:40:50 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id D14B921F8697 for ; Mon, 16 Jan 2012 10:40:42 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 267A679637; Mon, 16 Jan 2012 13:40:23 -0500 (EST) X-Original-To: IPP@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 5F92C79631 for ; Mon, 16 Jan 2012 13:40:07 -0500 (EST) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LXW0089FMF8C1I0@mail-out.apple.com> for IPP@pwg.org; Mon, 16 Jan 2012 10:39:52 -0800 (PST) X-AuditID: 11807136-b7b94ae000002733-e5-4f146ef8a560 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id 33.48.10035.8FE641F4; Mon, 16 Jan 2012 10:39:52 -0800 (PST) Subject: Re: [IPP] JPS3 comment on xxx-preferred From: Michael Sweet In-reply-to: Date: Mon, 16 Jan 2012 10:39:52 -0800 Message-id: <7BEFC5AD-0245-47F0-88A8-73BFF5C64ADA@apple.com> References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUieFRTW/dHnoi/we1+MYtj+16yWBz5FmvR 8WQlqwOzx9aTP9g85i2ezuSx/NR6tgDmKC6blNSczLLUIn27BK6MC8eesxQsiam4cq6BqYHx XkAXIyeHhICJxO49LcwQtpjEhXvr2boYuTiEBKYzScx68pwVJCEsYCAxc89pMJtXwFBiav85 MJtZIEFi+4ZXLCA2m4CaxO9JfWBxToEAict3pzOC2CwCqhJbd+9lgajnl/j27gsjxBwbiUUn 3oDVCwn4S3RfXQd2hIiAjsTGh/uBbA6gg2Qlpi0pm8DINwvJ5llINkPY2hLLFr5mhrANJJ52 vmLFFNeXePNuDtMCRrZVjIJFqTmJlYameokFBTmpesn5uZsYQWHbUGi2g3HHX7lDjAIcjEo8 vDe9RfyFWBPLiitzDzFKcDArifAK+gCFeFMSK6tSi/Lji0pzUosPMUpzsCiJ876JA0oJpCeW pGanphakFsFkmTg4pRoYk4/Pe/xXkmeK0iGhWytCgzfst2uUmPavpLMlWJslQuhi3b7souuv j0tcyCjnyHl9xHLNonUz79czcGS/vnv7gQavcMVjwQ8dhndui7syVF/NC+ta3dTQtTfRIfjv ToVfxw/N2693X63mzdEUwSdmYSJW2x0b/9+ezn+8qiVbqyGg/Yde4OEwJZbijERDLeai4kQA 6WKyt1cCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: IPP@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1912265487==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 267A679637.AA12F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1912265487== Content-type: multipart/alternative; boundary="Boundary_(ID_316phQ6d/rK9p/wYw+qqFA)" --Boundary_(ID_316phQ6d/rK9p/wYw+qqFA) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Pete, >From today's Cloud conference call we decided on "preferred-attributes" (co= llection) as the IPP attribute name and "PreferredElements" (group) for the= XML schema. The IPP attribute will be returned in the unsupported attribu= tes group. On Jan 15, 2012, at 9:21 AM, Zehler, Peter wrote: > Why do we have a bunch of xxx-preferred attributes? It complicates the m= odel with a bunch of attributes and is not general purpose enough to addres= s all the possible conflicting attributes and values. >=20=20 > Is there any reason we cannot provide this functionality in a manner simi= lar to =93unsupported-attributes=94. The =93unsupported-attributes=94 is h= andled in IPP as an out of band group in an IPP response. We could extend= the encoding of out of band attributes to include a new group for =93xxx-p= referred=94 . That way any substituted or conflicting attributes and value= s could be returned for a Validate operation. > I would prefer to handle =93xxx-preferred=94 using the collection syntax.= I think it is easier and requires fewer changes to the IPP encoding. Def= ining =93attributes-preferred=94 as a collection of attributes and permitti= ng any template attributes to be included would be a simple generalization.= It would also allow a client to pick those attribute/values out to correc= t their request and not rely on printer substitution. >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_316phQ6d/rK9p/wYw+qqFA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable

On Jan 15, 2012, at 9:21 AM, Zehler, Peter wrote:

Why do we have a bunch of xxx-preferred attributes?  I= t complicates the model with a bunch of attributes and is not general purpo= se enough to address all the possible conflicting attributes and values.
 
Is there any reason we cannot provide this fun= ctionality in a manner similar to =93unsupported-attributes=94.  The = =93unsupported-attributes=94 is handled in IPP as an out of band group in a= n IPP response.   We could extend the encoding of out of band att= ributes to include a new group for =93xxx-preferred=94 .  That way any= substituted or conflicting attributes and values could be returned for a V= alidate operation.
I would prefer to handle =93xxx= -preferred=94 using the collection syntax.  I think it is easier and r= equires fewer changes to the IPP encoding.  Defining =93attributes-pre= ferred=94 as a collection of attributes and permitting any template attribu= tes to be included would be a simple generalization.  It would also al= low a client to pick those attribute/values out to correct their request an= d not rely on printer substitution.
 
Peter Zehler

Xerox Research Center Webster
= Email: Peter.Zehler@Xerox.com=
Voice: (585) 265-8= 755
FAX: (5= 85) 265-7441
US Mail: Peter Zehler
= Xerox Corp.
= 800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
 

-- This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. __= _____________________________________________
ipp mailing list
https://www.pwg.org/mail= man/listinfo/ipp

________________________= ________________________________________________
Michael Sweet, S= enior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_316phQ6d/rK9p/wYw+qqFA)-- --===============1912265487== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1912265487==-- From ipp-bounces@pwg.org Mon Jan 16 11:30:24 2012 Return-Path: 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 B185121F8691 for ; Mon, 16 Jan 2012 11:30:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.424 X-Spam-Level: X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zd5+Sns6XkDN for ; Mon, 16 Jan 2012 11:30:24 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id E28C721F8680 for ; Mon, 16 Jan 2012 11:30:23 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 795777964D; Mon, 16 Jan 2012 14:30:05 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 1553B7964A for ; Mon, 16 Jan 2012 14:29:48 -0500 (EST) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXW00KJDOT1Y1D2@mail-out.apple.com> for ipp@pwg.org; Mon, 16 Jan 2012 11:29:48 -0800 (PST) X-AuditID: 11807134-b7c42ae000000421-2b-4f147aacf3da Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 39.CE.01057.CAA741F4; Mon, 16 Jan 2012 11:29:48 -0800 (PST) From: Michael Sweet Date: Mon, 16 Jan 2012 11:29:48 -0800 To: ipp@pwg.org Message-id: <7C85E9C5-25DE-4C78-8A44-8343C4AA69A2@apple.com> X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUieFRTW3dNlYi/wf3fvBbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyji4ZBdbwUfpiqdH9rM0MD6W6GLk5JAQMJHY eHUbK4QtJnHh3no2EFtIYDqTxJNWdRCbTUBN4vekPrAaZoEEiT+bWlhAbBYBVYlbny6B1QsL WEg0z3zPCGKLCPBLTLwIUc8rYCPxeFYTlG0oMbX/HJDNAbRLVmLakrIJjNyzkEydhaQKIq4t sWzha+ZZQB3MAjoSkxcyogpD2B/PH2FawMi2ilGwKDUnsdLQRC+xoCAnVS85P3cTIyisGgpN djAe/Ml/iFGAg1GJh/eGt4i/EGtiWXFl7iFGCQ5mJRFeQR+gEG9KYmVValF+fFFpTmrxIUZp DhYlcd7XcUApgfTEktTs1NSC1CKYLBMHp1QDo5Hjvmuvvl+5cV5aPNldjVVq897FkhlGR80u P5gbJi7yxMAyq2zCbvaH88QOnrk8VZ1JZHolU+P+mcqzBOY3RB95vaf/6+54q8wFulem3a6K UEq7ERx7u/zMjGNNtdvawwRyjDoPLc29etggYNODaKPi3h9qR4rlnz7dUOnfH3HY3XLnkodT cpRYijMSDbWYi4oTAU7BlfgnAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's IPP conference call X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1279797318==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 795777964D.A822F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1279797318== Content-type: multipart/alternative; boundary="Boundary_(ID_sAdCU68Owztk7tsDUp+yRw)" --Boundary_(ID_sAdCU68Owztk7tsDUp+yRw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the minutes from today's (short!) IPP conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120116.pdf Our next conference call will be January 23, 2012 at 1pm. Action items: - Mike to post PWG Raster for WG last call - Ira to ask steering committee to approve PWG last call not spanning F2F due to large gap between Feb/April F2F. ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_sAdCU68Owztk7tsDUp+yRw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the minutes from today's (short!) IPP conference call to:
=


Our next conference call wil= l be January 23, 2012 at 1pm.

Action items:
<= div>
- Mike to post PWG Raster for WG last call
- Ira to ask steeri= ng committee to approve PWG last call not spanning F2F due to large gap bet= ween Feb/April F2F.

______________________________________________________= __________________
Michael Sweet, Senior Printing System Engineer= , PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_sAdCU68Owztk7tsDUp+yRw)-- --===============1279797318== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1279797318==-- From ipp-bounces@pwg.org Mon Jan 16 11:32:14 2012 Return-Path: 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 AAFD421F8683 for ; Mon, 16 Jan 2012 11:32:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.458 X-Spam-Level: X-Spam-Status: No, score=-102.458 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XO7P7Xx1UvAO for ; Mon, 16 Jan 2012 11:32:13 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B053B21F8682 for ; Mon, 16 Jan 2012 11:32:13 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 950B179655; Mon, 16 Jan 2012 14:31:51 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 6315079655 for ; Mon, 16 Jan 2012 14:31:24 -0500 (EST) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LXW008FSOS2C1O0@mail-out.apple.com> for ipp@pwg.org; Mon, 16 Jan 2012 11:31:23 -0800 (PST) X-AuditID: 11807130-b7c59ae000007da2-0d-4f147b0b6dad Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 81.9B.32162.B0B741F4; Mon, 16 Jan 2012 11:31:23 -0800 (PST) From: Michael Sweet Date: Mon, 16 Jan 2012 11:31:23 -0800 To: ipp@pwg.org Message-id: <259F7F7E-E693-4F21-A5D4-1073A0F3F86C@apple.com> X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprELMWRmVeSWpSXmKPExsUieFRTW5e7WsTfYNk1A4tj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZew/fIat4KRsxa37TSwNjKuluhg5OSQETCS6 vs1kh7DFJC7cW88GYgsJTGeSOL4sGMRmE1CT+D2pj7WLkYODWSBB4vqBHJAwi4CqxOEHp5hB bGEBHYkvbR+ZQGwRAX6JiRdByjk5eAVsJK5NXccOYRtKTO0/BzZGQkBWYtqSsgmM3LMQhs5C UgRiMwtoSyxb+JoZokRHYvJCRlRhCPvj+SNMCxjZVjEKFqXmJFYaGuolFhTkpOol5+duYgSF VEOhwQ7GtT/5DzEKcDAq8fDe9BbxF2JNLCuuzD3EKMHBrCTCK+gDFOJNSaysSi3Kjy8qzUkt PsQozcGiJM77Mg4oJZCeWJKanZpakFoEk2Xi4JRqYDzM/P7X2dVWdbWpT4p85yZsCNnifCRe v2mvzgnz3zOeB3Rv3OX65NAxkxZmLrm1Yc/2nLvS+bDQ4Iu4rc7TUvULbP9MFJ9fWDL10OuU GS1q2ec2Sbwqund2x1LFHbG9s8WlvM6bqNcerJ4p7aXvI/4lf4IKf1e/+7lDwlEVSvn2jy+e 89fWSlRiKc5INNRiLipOBABbo/DWJQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Prototype experience for PWG Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1032058228==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 950B179655.A80C7 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1032058228== Content-type: multipart/alternative; boundary="Boundary_(ID_5cCftLHj+u4BRxlfY2gxlA)" --Boundary_(ID_5cCftLHj+u4BRxlfY2gxlA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, Apple has prototyped all of the PWG Raster Format and associated IPP attributes and found no issues in implementation from the currently posted draft. ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_5cCftLHj+u4BRxlfY2gxlA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

Ap= ple has prototyped all of the PWG Raster Format and associated IPP attribut= es and found no issues in implementation from the currently posted draft.

________________________= ________________________________________________
Michael Sweet, S= enior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_5cCftLHj+u4BRxlfY2gxlA)-- --===============1032058228== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1032058228==-- From pwg-announce-bounces@pwg.org Tue Jan 17 06:35:07 2012 Return-Path: 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 0EC7221F85AE for ; Tue, 17 Jan 2012 06:35:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CX+f2g9wRRCI for ; Tue, 17 Jan 2012 06:35:06 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id F25BE21F85A0 for ; Tue, 17 Jan 2012 06:35:05 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2EBBB7965C; Tue, 17 Jan 2012 09:34:41 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from USA7109MR004.ACS-INC.COM (usa7109mr004.acs-inc.com [63.101.151.13]) by pwg.org (Postfix) with ESMTP id 971D879636 for ; Tue, 17 Jan 2012 09:34:26 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnIBAIKGFU8Nl9IPmWdsb2JhbABBA4JNqXKBBiIBAQEBAQgLCwcUJYFyAQEBAgIBAQEMAQwBEAMvLAEfCwYMCwEHJh8JCQEEEwgBh3mXFY0fAZJJiV0CAQEfHh4IAgcBAQIBAQgBAQEDKA4cCTcFATILAgMHDgEfFgsNHggDH3uCPmMEgluFYIUAmjg Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR004.ACS-INC.COM with ESMTP; 17 Jan 2012 08:34:18 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 17 Jan 2012 06:34:18 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 17 Jan 2012 06:34:16 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PWG Last Call of PWG Print Job Ticket and Associated Capabilities specification (1/17/12 - 2/17/12) thread-index: AczVJRUi73k+jzMhRnm1PmxrEdv3QQ== From: "Zehler, Peter" To: X-OriginalArrivalTime: 17 Jan 2012 14:34:18.0127 (UTC) FILETIME=[181271F0:01CCD525] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] {Disarmed} PWG Last Call of PWG Print Job Ticket and Associated Capabilities specification (1/17/12 - 2/17/12) X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1040988726==" Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 2EBBB7965C.AC388 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============1040988726== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCD525.17DC8AB2" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCD525.17DC8AB2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 [This PWG Last Call will start today on Tuesday January 17, 2012. This PWG Last Call will end Friday February 17, 2012 at 10pm US PDT.] =20 This is the formal announcement of the PWG Last Call for the PWG=20 Print Job Ticket and Associated Capabilities specification, located at: =20 All required attributes and values defined in this document have been prototyped by Xerox and/or other vendors through their deployment of existing protocols such as ISO 10175, IETF/PWG IPP and WS-Print. The MFD WG has completed a working group last call and subsequent revisions of this document. =20 The PWG Process/3.0 requires that a quorum (30%) of PWG voting members must acknowledge a PWG Last Call (with or without comments), before any document can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote but it DOES require your review acknowledgment. =20 Please send your review acknowledgment *exactly* as follows: =20 To: mfd at pwg.org >=20 Subject: has reviewed the Print Job Ticket and Associated=20 Capabilities specification and has [no] comments =20 =20 Please do NOT simply reply to this note on the PWG-Announce list. =20 Note: The PWG Definition of the Standards Development Process Version 3.0 is located at: =20 =20 =20 Peter Zehler PWG Semantic Model Working Group Chair Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCD525.17DC8AB2 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
All,
 =

[This PWG Last Call will start today on Tuesday January 17=
, 2012.
This PWG Last Call will end Friday February 17=
, 2012 at 10pm US PDT.]
 
This is=
 the formal announcement of the PWG Last Call for the PWG
= 
Print Job Ticket and Associated Capabilities specification, located at=
:
<ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-sm20=
-printjobticket10-20120117.pdf>
 
All required attributes and values defined in this document have
been prototyped by Xerox and/or other vendors through th=
eir deployment
of existing protocols such as ISO 10175=
, IETF/PWG IPP and WS-Print.
The MFD WG has completed =
a working group last call and subsequent
revisions of =
this document.
 
The PWG Process/=
3.0 requires that a quorum (30%) of PWG voting members
must acknowledge a PWG Last Call (with or without comments), before any
document can progress to PWG Formal Vote.  This PWG=
 Last Call is NOT a
Formal Vote but it DOES require yo=
ur review acknowledgment.
 
Pleas=
e send your review acknowledgment *exactly* as follows:
To:  mfd at pwg.org <mailto:Mail=
Scanner has detected a possible fraud attempt from "www.pwg.org" claiming t=
o be mfd at pwg.org> 
Subject: =
 <Company Name> has reviewed the Print Job Ticket and Associated 
Capabilities specification and has [no] comments
 
 
Please do N=
OT simply reply to this note on the PWG-Announce list.
Note:  The PWG Definition of the Standards Dev=
elopment Process Version
3.0 is located at:=

  <http://www.pwg.org/chair/membership_docs/pwg-process30.pd=
f>

 

 

 

Peter Zehler

PWG Semantic Model Working Group Chair

Xerox Research Center Webster
Ema= il: Pe= ter.Zehler@Xerox.com
Voice: (585) 265-8755
= FAX: (585) 265-7441
US M= ail: Peter Zehler
Xerox Co= rp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCD525.17DC8AB2-- --===============1040988726== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --===============1040988726==-- From info@webmaster.pl Thu Jan 19 23:50:32 2012 Return-Path: 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 49C4421F8638; Thu, 19 Jan 2012 23:50:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.892 X-Spam-Level: **** X-Spam-Status: No, score=4.892 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_95=3, FH_RELAY_NODNS=1.451, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1, SARE_SUB_ENC_UTF8=0.152] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6v6mXQl3e62; Thu, 19 Jan 2012 23:50:31 -0800 (PST) Received: from mail.solca.med.ec (unknown [200.105.240.90]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7CE21F8628; Thu, 19 Jan 2012 23:50:31 -0800 (PST) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 0410519C05D9; Fri, 20 Jan 2012 02:50:33 -0500 (ECT) Received: from mail.solca.med.ec (localhost.localdomain [127.0.0.1]) by mail.solca.med.ec (Postfix) with ESMTP id B8FAF19C05D6; Fri, 20 Jan 2012 02:50:32 -0500 (ECT) Received: from 41.138.180.207 (SquirrelMail authenticated user mperalta) by mail.solca.med.ec with HTTP; Fri, 20 Jan 2012 02:50:32 -0500 (ECT) Message-ID: <60703.41.138.180.207.1327045832.squirrel@mail.solca.med.ec> Date: Fri, 20 Jan 2012 02:50:32 -0500 (ECT) Subject: =?utf-8?B?V2VibWFzdGVyIHBvd2lhZG9taWXFhCEh4oCP4oCP4oCPICA=?= From: =?utf-8?B?V2VibWFzdGVyIEFrdHVhbGl6YWNqYSBXeWR6aWHFgg==?= Reply-To: customercarewebdept40@w.cn User-Agent: SquirrelMail/1.4.8-5.el5.centos.10 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal To: undisclosed-recipients:; X-TM-AS-Product-Ver: IMSS-7.1.0.1302-6.8.0.1017-18656.005 X-TM-AS-Result: No-0.237-4.5-31-10 X-imss-scan-details: No-0.237-4.5-31-10 X-TM-AS-User-Approved-Sender: No X-TMASE-MatchedRID: bF/ftEib5FfmR+RxuU2vfUwAZYE2FMixerJCitPoIIzfUZT83lbkEMWm DR829mMW+SihPPY9VI/SFZyaJmMIRq4HyN5VK32o3QfwsVk0UbsIoUKaF27lxVFQYAIrTI9WNyn tbJFocoCMBa8Npj7TpPZGqdJJ6r9CB0ZiLk9GkysKige8GupNf4pr/NlGJYu6Fr+z9EnoAxl6vB tqjtop/0V4mhCkeaWfaWNolBtQ1wbDHYSZWYRUCk9o3BPtf0h2+rL5VW+ofZc= Drodzy Widzowie konto e-mail, Ten komunikat jest od poczty centrum wiadomości do wszystkich na nasze konto poczty owners.As pierwszym kwartale 2012 r. Obecnie jest przeprowadzenie usługi aktualizacji dla naszej bazy i e-mail centrum konta. Jesteśmy usunięcie wszystkich niewykorzystanych konto poczty internetowej, aby utworzyć więcej miejsca dla nowych kont. Aby zapobiec koncie od usuwania i Aby kontynuować korzystanie z naszych usług, które są wymagane do aktualizacji i potwierdzenia konta webmail. Aby zakończyć potwierdzenia konta za pierwszy kwartał 2012 r., Jesteś odpowiedzieć na tę wiadomość natychmiast i wprowadź dane swojego konta w wymienionych poniżej. Potwierdzenie informacji o koncie Nazwa użytkownika: ...... E-mail Login ............ Hasło: .................. Potwierdź hasło :........ Data urodzenia: ......... Ważne * Proszę podać wszystkie te informacje kompletnie i prawidłowo w przeciwnym razie ze względów bezpieczeństwa być może będziemy musieli zamknąć temporarily.We konto poczty dziękuję za szybkie zajęcie się tą matter.Please zrozumieć, że jest to środek bezpieczeństwa przeznaczonych do ochrony użytkowników i konta poczty internetowej. Przepraszamy za wszelkie niedogodności. From ipp-bounces@pwg.org Sun Jan 22 13:17:39 2012 Return-Path: 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 22D0F21F8532 for ; Sun, 22 Jan 2012 13:17:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.796 X-Spam-Level: X-Spam-Status: No, score=-0.796 tagged_above=-999 required=5 tests=[AWL=-0.798, BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTqq35Q57NAK for ; Sun, 22 Jan 2012 13:17:38 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE6421F855F for ; Sun, 22 Jan 2012 13:17:37 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B5AB7795C6; Sun, 22 Jan 2012 16:17:17 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by pwg.org (Postfix) with ESMTP id 300B279595 for ; Sun, 22 Jan 2012 16:17:02 -0500 (EST) Received: by werb13 with SMTP id b13so2034474wer.5 for ; Sun, 22 Jan 2012 13:17:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=wLoti0d6d7OkmssPC10VDOM+by1Ce4fZlAUkpv9Hp8g=; b=ZoDs8bN63lCPERefVmLSXAhIfVOtDJGr805ALjcFci48oHIbFs1tKAyiiA1QYZEFsR VQBUC+C9B/FYOY9wG0Sv4KTeVUyCHhUepB0/hPkxo/bIQhVtTLFwmEmXCo+mjhJdyqgw x+22L7FbFb961E6o/V9oLnJQ0gutjIJYZjKYk= MIME-Version: 1.0 Received: by 10.216.135.208 with SMTP id u58mr2854438wei.56.1327267022219; Sun, 22 Jan 2012 13:17:02 -0800 (PST) Received: by 10.223.155.10 with HTTP; Sun, 22 Jan 2012 13:17:02 -0800 (PST) Date: Sun, 22 Jan 2012 16:17:02 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - 1-3pm EST Monday 23 January 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1686880717==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: B5AB7795C6.A996F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1686880717== Content-Type: multipart/alternative; boundary=0016e6de03c461a90e04b7246f09 --0016e6de03c461a90e04b7246f09 Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be next Monday for TWO HOURS! Monday 23 January 10am-12pm US PST / 1-3pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. Live Meeting Info (courtesy of Pete Zehler): Link: https://www.livemeeting.com/cc/xerox/join?id=PwgSemanticModel&role=attend&pw=LetMeIn URL: https://www.livemeeting.com/cc/xerox/join Meeting ID: PwgSemanticModel Entry Code: LetMeIn *** Main Objective - Review of IPPS URI *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120116.pdf (3) Status of 'ipptool' and IPP/2.0 Interop - December Windows binary still has missing libraries - crashes on Win/XP (4) Status of other IPP Everywhere specs - if available (5) Discussion of cleartext security properties in IPP and PWG SM - IPP operation attributes versus "write-once" PWG SM Job Ticket elements - document-password (e.g., for printing PDF documents) - forwarding of cleartext security properties in Cloud? (very weak protection) (6) Review of IPP over HTTPS Transport Binding and 'ipps' URI Scheme - ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf (7) Next Steps - Cloud/IPP WG on Monday 30 January - review slides for PWG F2F - IPP WG on Tuesday 7 February 1-5pm US PST - at Canon in Irvine, CA - IPP WG on Wednesday 8 February 1-5pm US PST - at Canon in Irvine, CA Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --0016e6de03c461a90e04b7246f09 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our next IPP WG call will be next Monday for TWO HOURS!

=A0 Monday 23 January 10am-12pm US PST / 1-3pm US EST

=A0 Call-in toll-free number (US/Canada): 1-866-469-3239
=A0 Call-in toll number (US/Canada): 1-650-429-3300 (Primary)
=A0 Call-in toll number (US/Canada): 1-408-856-9570 (Backup)

=A0 Attendee Access Code: *******#
=A0 Attendee ID Code: # (empty)

If you need the Attendee Access code, please email me a request.

Live Meeting Info (courtesy of Pete Zehler):

=A0 Link: https://www.livemeeting.com/cc/xerox/join?id=3DPwgSemanticModel&role= =3Dattend&pw=3DLetMeIn
=A0 URL: https://www.livemeeting.com/cc/xerox/join
=A0 Meeting ID: PwgS= emanticModel
=A0 Entry Code: LetMeIn


*** Main Objective - Review of IPPS URI ***

Agenda:

(1) PWG IP Policy and Minute Taker
=A0 =A0=A0 - Mike?

(2) Approve IPP minutes from previous meeting
=A0=A0 =A0 - = ftp://ftp.pwg.or= g/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120116.pdf

(3) Status of 'ipptool' and IPP/2.0 Interop
=A0=A0=A0=A0 - D= ecember Windows binary still has missing libraries - crashes on Win/XP
<= br>(4) Status of other IPP Everywhere specs
=A0=A0=A0=A0 - if available<= br>
(5) Discussion of cleartext security properties in IPP and PWG SM
=A0=A0=A0=A0 - IPP operation attributes versus "write-once" PWG S= M Job Ticket elements
=A0=A0=A0=A0 - document-password (e.g., for printi= ng PDF documents)
=A0=A0=A0=A0 - forwarding of cleartext security proper= ties in Cloud? (very weak protection)
=A0
(6) Review of IPP over HTTPS Transport Binding and 'ipps' U= RI Scheme
=A0=A0=A0=A0 - ftp://ftp.pw= g.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-04-20111122.pdf=A0= =A0 =A0=A0

(7) Next Steps
=A0=A0=A0=A0 - Cloud/IPP WG on Monday 30 January - re= view slides for PWG F2F
=A0=A0=A0=A0 - IPP WG on Tuesday 7 February 1-5p= m US PST - at Canon in Irvine, CA
=A0=A0=A0=A0 - IPP WG on Wednesday 8 F= ebruary 1-5pm US PST - at Canon in Irvine, CA

Cheers,
- Ira

Ira McDonald (Musician / Software= Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEE= E-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair= - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --0016e6de03c461a90e04b7246f09-- --===============1686880717== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1686880717==-- From ipp-bounces@pwg.org Mon Jan 23 10:42:08 2012 Return-Path: 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 5413921F8475 for ; Mon, 23 Jan 2012 10:42:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.482 X-Spam-Level: X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xpuM+mfwVMpp for ; Mon, 23 Jan 2012 10:42:07 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 60DF521F847D for ; Mon, 23 Jan 2012 10:42:07 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A2228795D6; Mon, 23 Jan 2012 13:41:49 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 24ADD795C6 for ; Mon, 23 Jan 2012 13:41:34 -0500 (EST) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LY90052JL6HW0D1@mail-out.apple.com> for ipp@pwg.org; Mon, 23 Jan 2012 10:41:34 -0800 (PST) X-AuditID: 11807130-b7c59ae000007da2-72-4f1da9dea379 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id CF.4E.32162.ED9AD1F4; Mon, 23 Jan 2012 10:41:34 -0800 (PST) From: Michael Sweet Date: Mon, 23 Jan 2012 10:41:34 -0800 To: ipp@pwg.org Message-id: X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUieFRTW/feSll/gwfXeSyO7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAlfHg6U+2ghVSFd9aprE3MG4X72Lk5JAQMJF4 9O4vE4QtJnHh3nq2LkYuDiGB6UwSPzrmsoMk2ATUJH5P6mMFsZkFEiQaFx5kBrFZBFQlHm56 B9YsLGAh0TzzPSOILSLALzHxIkQ9r4CNRGfDcxYI21Biav85oDgH0DJZiWlLyiYwcs9CMnUW kiqIuLbEsoWvgeIcQLaOxOSFjKjCEPbH80eYFjCyrWIULErNSaw0NNRLLCjISdVLzs/dxAgK rIZCgx2Ma3/yH2IU4GBU4uGVmCnrL8SaWFZcmXuIUYKDWUmE1+ixjL8Qb0piZVVqUX58UWlO avEhRmkOFiVx3i3rJf2FBNITS1KzU1MLUotgskwcnFINjPxaBd7KDSvsnYtzeKzN9639n+oR Idi6Ysas0+8K5a56vtDm3L4i7+Uqj9054vsa10ndOjafzfn6xXU2oW0yj5vXhse55aSLzFLd kXjNffo7s5WctnOrap4EylQLTT2rEfvt/O4LlZWPHM7Lba2xX2J3/8hjQdGdPxTdt9RMrOfj ue5j4S5YrMRSnJFoqMVcVJwIAMUu7tgoAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's IPP conference call X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0207248663==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: A2228795D6.A8673 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0207248663== Content-type: multipart/alternative; boundary="Boundary_(ID_gTRoMSOSmBkv5mqbAz4/HQ)" --Boundary_(ID_gTRoMSOSmBkv5mqbAz4/HQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the minutes from today's IPP conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120123.pdf Our next conference call will be January 30, 2012 at 1pm ET with the Cloud Imaging WG to go over the F2F slides. Action items: - Mike to send Justin questions WRT MSPS license ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_gTRoMSOSmBkv5mqbAz4/HQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the minutes from today's IPP conference call to:

=

Our next conference call will be Janu= ary 30, 2012 at 1pm ET with the Cloud Imaging WG to go over the F2F slides.=

Action items:

- Mike to send = Justin questions WRT MSPS license

______________________________________________________= __________________
Michael Sweet, Senior Printing System Engineer= , PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_gTRoMSOSmBkv5mqbAz4/HQ)-- --===============0207248663== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0207248663==-- From ipp-bounces@pwg.org Mon Jan 23 10:47:17 2012 Return-Path: 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 615BD21F84A6 for ; Mon, 23 Jan 2012 10:47:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.498 X-Spam-Level: X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMrBLjB-aBxh for ; Mon, 23 Jan 2012 10:47:16 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 607F421F8497 for ; Mon, 23 Jan 2012 10:47:16 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5C8D9795D6; Mon, 23 Jan 2012 13:46:56 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id C3E8E795D4 for ; Mon, 23 Jan 2012 13:46:39 -0500 (EST) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LY9005G5LFAW0D1@mail-out.apple.com> for ipp@pwg.org; Mon, 23 Jan 2012 10:46:39 -0800 (PST) X-AuditID: 1180711d-b7b41ae000004823-49-4f1dab0e96f6 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 7D.6A.18467.F0BAD1F4; Mon, 23 Jan 2012 10:46:39 -0800 (PST) From: Michael Sweet Date: Mon, 23 Jan 2012 10:46:38 -0800 To: ipp@pwg.org Message-id: <9EA981EE-E83A-4484-AF3E-FBF024C79982@apple.com> X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprELMWRmVeSWpSXmKPExsUieFRTW5d/tay/wdZ1AhbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyvjQMp+94K5yxcvGW4wNjCvluxg5OCQETCQm ngztYuQEMsUkLtxbzwZiCwlMZ5J432sFYrMJqEn8ntTHCmIzCyRITH6zEsxmEVCVaH/zlAXE FhbQlHiw+S47iC0iwC8x8SJIPQcHr4CNxPJPHCBhXgFDian951ghtspKTFtSNoGRexaSobOQ VEHEtSWWLXzNPAuog1lAR2LyQkZUYQj74/kjTAsY2VYxChal5iRWGhrrJRYU5KTqJefnbmIE hVRDoewOxv0/+Q8xCnAwKvHwHpom6y/EmlhWXJl7iFGCg1lJhNfosYy/EG9KYmVValF+fFFp TmrxIUZpDhYlcd7N6yX9hQTSE0tSs1NTC1KLYLJMHJxSDYzV50/NeKMnIej6pHOS+lW9w/X5 hrp+2Te/xlxL1g/qfG//lW/ePys2wTb72v3uVbemvjbU2dcx5f5pDf50rYZcru43U6bvWq23 N/PsjJx3UpJGZ7dO+JlqLKOXYGPE2xeu0HxdZTkjv/YZsTbPSX1dHQ0vlOWeyrG+fX/k25Ec hu3GmW/Dm5RYijMSDbWYi4oTAWNpeW4lAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] IPPTOOL interoperability testing X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0899492458==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 5C8D9795D6.A8AFA X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0899492458== Content-type: multipart/alternative; boundary="Boundary_(ID_fubiKTSbsweOux2kxFLWoA)" --Boundary_(ID_fubiKTSbsweOux2kxFLWoA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, So far I have not received any interoperability testing results. Please let me know if you have tried to run the tool but have had problems. I have had one person report they had issues on Windows XP, but after doing a clean install of each major release of Windows I have not been able to reproduce the problem locally. Similarly, if you have been able to run the tool but are just not able to share the results yet, please let me know. Thank you! ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_fubiKTSbsweOux2kxFLWoA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

So= far I have not received any interoperability testing results.
Please let me know if you have tried to run the tool but have = had problems. I have had one person report they had issues on Windows XP, b= ut after doing a clean install of each major release of Windows I have not = been able to reproduce the problem locally.

Simila= rly, if you have been able to run the tool but are just not able to share t= he results yet, please let me know.

Thank you!

_______________________________________________________________= _________
MailScanner, and is
believed to be clean. --Boundary_(ID_fubiKTSbsweOux2kxFLWoA)-- --===============0899492458== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0899492458==-- From ipp-bounces@pwg.org Mon Jan 23 15:14:10 2012 Return-Path: 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 74F4721F85F8 for ; Mon, 23 Jan 2012 15:14:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.511 X-Spam-Level: X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id buYO6+d37lhS for ; Mon, 23 Jan 2012 15:14:09 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7222821F855B for ; Mon, 23 Jan 2012 15:14:09 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 4F4E379603; Mon, 23 Jan 2012 18:13:50 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 09496795EF for ; Mon, 23 Jan 2012 18:13:35 -0500 (EST) MIME-version: 1.0 Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LY900G2BXS1Q4Q1@mail-out.apple.com> for ipp@pwg.org; Mon, 23 Jan 2012 15:13:35 -0800 (PST) X-AuditID: 11807137-b7b7fae000005b9a-7c-4f1de99f7e31 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 79.91.23450.F99ED1F4; Mon, 23 Jan 2012 15:13:35 -0800 (PST) From: Michael Sweet Date: Mon, 23 Jan 2012 15:13:35 -0800 To: ipp@pwg.org Message-id: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUieFRTW3f+S1l/g/Yj3BbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgynjS4lPQZFvx/cVCtgbG0yZdjJwcEgImEvPW zGCBsMUkLtxbz9bFyMUhJDCdSeLCodOMIAk2ATWJ35P6WEFsZoEEiUNz14DFWQRUJSa9mAVm CwuoS7Tffs8OYosI8EtMvAhRzytgI3F66jVGCNtQYmr/OaA4B9AyWYlpS8omMHLPQjJ1FpIq iLi2xLKFr5khbAOJp52vsIjrS7x5N4dpASPbKkbBotScxEpDM73EgoKcVL3k/NxNjKDAaig0 38G4/a/cIUYBDkYlHl6JmbL+QqyJZcWVuYcYJTiYlUR41c4BhXhTEiurUovy44tKc1KLDzFK c7AoifNuXy/pLySQnliSmp2aWpBaBJNl4uCUamDMSHiRm8CRfiDy1Nq7UcL7N8zWOWZ3aeIL 4eBHqY5J12Im3LSXPLohSkc4nO2h+1dtrtOxC8N+sp1ZdDZGLuGH8v7/nx9olf8resXL376m 4QrDw71rtzD/Y2K5tGHS386eQv0q5rux7yvPZDLvcZhx74v2k/9zPxX83OBWofeK6cgxydTS 6fyqSizFGYmGWsxFxYkApz1C9ygCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] media-input-tray-check-default X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1165566910==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 4F4E379603.A899F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1165566910== Content-type: multipart/alternative; boundary="Boundary_(ID_olhU/MZhHwUcFWm85y0ivQ)" --Boundary_(ID_olhU/MZhHwUcFWm85y0ivQ) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable All, I am going through yet another round of updates to the IANA registry (this = time for sure! :), and noticed that I still have the media-input-tray-check= -default attribute tagged as "under review". I would like to resolve this b= efore we submit our next round of updates to the registry. BACKGROUND PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check J= ob Template attribute thusly: The =93media-input-tray-check=94 Job Template attribute indicates that the = Printer MUST check that the characteristics of the media in the identified = input tray are the same as characteristics of the media identified by the J= ob's "media" Job Template attribute or matched (see section 3.13) by the Jo= b's "media- col" Job Template attribute. The keyword values are the same in= put tray keyword values as are defined for the "media" Job Template attribu= te (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top'= , 'middle', 'bottom', etc. Independent of the "ipp-attributes-fidelity" operation attribute supplied b= y the client, if the characteristics differ, the Printer adds the =91resour= ces-are-not-ready=92 value (see section 6.1) to the job's "job-state-reason= s" attribute and MAY either (1) put the job into the =91pending-held=92 sta= te or (2) start to process the job normally, but immediately stop the job (= =93job-state=94 =3D =91processing-stopped=92) and the Printer (=93printer-s= tate=94 =3D =91stopped=92). In either implementation, the operator can chan= ge the media in the input tray to agree with the job or can modify the job= =92s =93media=94 or =93media-col=94 attributes to agree with the input tray= , depending on policy. Table 1 (at the beginning of section 3) defines media-input-tray-check-defa= ult and -supported. The issue is that there should not be a default media-input-tray-check valu= e; like some other Job Template attributes (e.g. overrides), it does not ma= ke sense to have a default value for this particular attribute since it int= eracts with the media in the job ticket. There are two ways to resolve this issue: 1. Drop media-input-tray-check-default from the registry and post an errata= for 5100.3 removing the media-input-tray-check-default attribute from Tabl= e 1. 2. Update the definition of media-input-tray-check-default to include the "= no-value" out-of-band value. I prefer option #1. Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_olhU/MZhHwUcFWm85y0ivQ) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable All,

I = am going through yet another round of updates to the IANA registry (this ti= me for sure! :), and noticed that I still have the media-input-tray-check-d= efault attribute tagged as "under review". I would like to resolve this bef= ore we submit our next round of updates to the registry.

BACKGROUND

PWG 5100.3 (Production Printing = Set 1) defines the media-input-tray-check Job Template attribute thusly:

The =93media-input-tra= y-check=94 Job Template attribute indicates that the Printer MUST check&nbs= p;that the characteristics of the media in the identified input tray a= re the same as characteristics of the media identified by the Job= 's "media" Job Template attribute or matched (see section 3.= 13) by the Job's "media- col" Job Template attribute. The keyword valu= es are the same input tray keyword values as are defined for the = "media" Job Template attribute (see section 6.3 in this document and [= RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.
=
Independent of the "ipp-attributes-fidelity" operation attri= bute supplied by the client, if the characteristics differ, the P= rinter adds the =91resources-are-not-ready=92 value (see section 6.1) to th= e job's "job-state-reasons" attribute and MAY either (1) put the job i= nto the =91pending-held=92 state or (2) start to process the job = normally, but immediately stop the job (=93job-state=94 =3D =91processing-s= topped=92) and the Printer (=93printer-state=94 =3D =91stopped=92). In= either implementation, the operator can change the media in the input= tray to agree with the job or can modify the job=92s =93media=94 or&n= bsp;=93media-col=94 attributes to agree with the input tray, depending on&n= bsp;policy.

Table 1 (at the beginning= of section 3) defines media-input-tray-check-default and -supported.
=

The issue is that there should not be a default media-i= nput-tray-check value; like some other Job Template attributes (e.g. overri= des), it does not make sense to have a default value for this particular at= tribute since it interacts with the media in the job ticket.

=
There are two ways to resolve this issue:

1. Drop media-input-tray-check-default from the registry and post an err= ata for 5100.3 removing the media-input-tray-check-default attribute from T= able 1.

2. Update the definition of media-input-tr= ay-check-default to include the "no-value" out-of-band value.
I prefer option #1.

Comments?
 
______________________________________________________= __________________
Michael Sweet, Senior Printing System Engineer= , PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_olhU/MZhHwUcFWm85y0ivQ)-- --===============1165566910== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1165566910==-- From ipp-bounces@pwg.org Mon Jan 23 15:31:56 2012 Return-Path: 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 4703D21F85D3 for ; Mon, 23 Jan 2012 15:31:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.52 X-Spam-Level: X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTJAHSqBW1Xv for ; Mon, 23 Jan 2012 15:31:55 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4C87321F85AA for ; Mon, 23 Jan 2012 15:31:55 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2C35279605; Mon, 23 Jan 2012 18:31:38 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id BB7E679603 for ; Mon, 23 Jan 2012 18:31:23 -0500 (EST) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LY9005C3YN2W042@mail-out.apple.com> for ipp@pwg.org; Mon, 23 Jan 2012 15:31:07 -0800 (PST) X-AuditID: 11807130-b7c59ae000007da2-82-4f1dedbb5d5c Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 0B.38.32162.BBDED1F4; Mon, 23 Jan 2012 15:31:07 -0800 (PST) From: Michael Sweet Date: Mon, 23 Jan 2012 15:31:07 -0800 To: ipp@pwg.org Message-id: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> X-Mailer: Apple Mail (2.1256) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUieFRTW3f3W1l/g9l/9C2O7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAlbHyW3bBLauKy4t3sjcwXjLqYuTkkBAwkXj1 eT0zhC0mceHeerYuRi4OIYHpTBLP7t4CS7AJqEn8ntTHCmIzCyRIvFo8gwnEZhFQlbhyfglY XFjAWeLoyy/sILaIAL/ExIsQ9bwCNhKT9i2Dsg0lpvafA7I5gJbJSkxbUjaBkXsWkqmzkFRB xLUlli18zTwLqINZQEdi8kJGVGEI++P5I0wLGNlWMQoWpeYkVhoa6iUWFOSk6iXn525iBIVV Q6HBDsa1P/kPMQpwMCrx8ErMlPUXYk0sK67MPcQowcGsJMKrdg4oxJuSWFmVWpQfX1Sak1p8 iFGag0VJnHfLekl/IYH0xJLU7NTUgtQimCwTB6dUAyPf6j1iMpPa/xuq9Nd9eWfr+K3s9dQV KX/Mo574/rKSO5Emxq+978mmPb3Cnzeo1zvNuvcq8JXn6fuqh89FJ7H+3Tw3breV4XSb8Nr8 RVcZ5NnYY1pzkr5cmd5doWJ/a7Nc4bITu+b7lJfuL9q6PWry4iN7a308v5Q0vFy/yFn1tN/P 9NKX7x8psRRnJBpqMRcVJwIApu3t3ycCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0707358872==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 2C35279605.AA844 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0707358872== Content-type: multipart/alternative; boundary="Boundary_(ID_hxPXIGfWiA2QFRLcSEbh4Q)" --Boundary_(ID_hxPXIGfWiA2QFRLcSEbh4Q) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have noticed an inconsistency for how we register xxx-default, xxx-ready, and xxx-supported attributes, and how these attributes are documented in our specifications. I would like to clean up these inconsistencies in the next update of the registry. Typically the xxx-default attributes are included either in the definition and description of the Job Template attributes or in a table at the beginning of the Job Template attributes. xxx-default attributes are part of the Printer Description attributes (printer-attributes-tag) in the protocol but are registered in the Job Template section. xxx-supported attributes are defined in either the Job Template or Printer Description sections of our specifications, and then have be registered in (usually, but not always) the same sections of the registry. The most common convention is to place xxx-supported in the Job Template section when it contains values that can be used directly and in the Printer Description section otherwise (for example, when xxx-supported provides a list of member attributes that can be specified in the xxx Job Template attribute - media-col works this way) Finally, xxx-ready attributes are randomly placed in the Job Template or Printer Description sections of our specifications and the registry. They always contain values that can be used in the corresponding xxx Job Template attribute... MY PROPOSAL 1. Move all xxx-default, xxx-ready, and xxx-supported attributes in the registry to the Printer Description section where they belong (they are Printer attributes, not Job Template). 2. Make sure that JPS3 and all future IPP specs going forward define any Printer Description attributes in that section; no more subsections (or inline text or tables) for xxx-default and xxx-supported that only serve to hide the corresponding definitions. Comments? ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_hxPXIGfWiA2QFRLcSEbh4Q) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have noticed an inconsistency for how we register xxx-default, xxx-ready, a= nd xxx-supported attributes, and how these attributes are documented in our= specifications. I would like to clean up these inconsistencies in the next= update of the registry.

Typically the xxx-default= attributes are included either in the definition and description of the Jo= b Template attributes or in a table at the beginning of the Job Template at= tributes. xxx-default attributes are part of the Printer Description attrib= utes (printer-attributes-tag) in the protocol but are registered in the Job= Template section.

xxx-supported attributes are de= fined in either the Job Template or Printer Description sections of our spe= cifications, and then have be registered in (usually, but not always) the s= ame sections of the registry. The most common convention is to place xxx-su= pported in the Job Template section when it contains values that can be use= d directly and in the Printer Description section otherwise (for example, w= hen xxx-supported provides a list of member attributes that can be specifie= d in the xxx Job Template attribute - media-col works this way)
<= br>
Finally, xxx-ready attributes are randomly placed in the Job = Template or Printer Description sections of our specifications and the regi= stry. They always contain values that can be used in the corresponding xxx = Job Template attribute...

MY PROPOSAL
1. Move all xxx-default, xxx-ready, and xxx-supported attribut= es in the registry to the Printer Description section where they belong (th= ey are Printer attributes, not Job Template).

2. M= ake sure that JPS3 and all future IPP specs going forward define any Printe= r Description attributes in that section; no more subsections (or inline te= xt or tables) for xxx-default and xxx-supported that only serve to hide the= corresponding definitions.

Comments?
________________________= ________________________________________________
Michael Sweet, S= enior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_hxPXIGfWiA2QFRLcSEbh4Q)-- --===============0707358872== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0707358872==-- From ipp-bounces@pwg.org Tue Jan 24 03:01:16 2012 Return-Path: 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 8E63721F851D for ; Tue, 24 Jan 2012 03:01:16 -0800 (PST) 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=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLE4PeXU2Nrz for ; Tue, 24 Jan 2012 03:01:15 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE6B21F8518 for ; Tue, 24 Jan 2012 03:01:15 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9D05679622; Tue, 24 Jan 2012 06:00:56 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr10.networksolutionsemail.com (omr10.networksolutionsemail.com [205.178.146.60]) by pwg.org (Postfix) with ESMTP id 5A1DE7960E for ; Tue, 24 Jan 2012 06:00:40 -0500 (EST) Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr10.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q0OB0bWc027817 for ; Tue, 24 Jan 2012 06:00:37 -0500 Authentication-Results: cm-omr4 smtp.user=ptykodi@tykodi.com; auth=pass (LOGIN) X-Authenticated-UID: ptykodi@tykodi.com Received: from [65.96.244.16] ([65.96.244.16:32837] helo=TCS2010LAPTOP) by cm-omr4 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 72/83-17039-55F8E1F4; Tue, 24 Jan 2012 06:00:37 -0500 From: "Paul Tykodi" To: References: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> In-Reply-To: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> Subject: RE: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported Date: Tue, 24 Jan 2012 06:00:41 -0500 Organization: Tykodi Consulting Services LLC Message-ID: <03eb01ccda87$69ecf9c0$3dc6ed40$@tykodi.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIq7g5W/Cx8FZMFdzEt0e5dDy6hWZVfMRUw Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ptykodi@tykodi.com List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1364028974==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 9D05679622.A9E44 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============1364028974== Content-Type: multipart/alternative; boundary="----=_NextPart_000_03EC_01CCDA5D.8116F1C0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_03EC_01CCDA5D.8116F1C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Mike, In terms of supporting the shift away from depending upon a driver always being available for every imaging device brought to market, I think the xxx attributes class becomes very important because it allows an imaging device to advertise its capabilities and its current status to a client using a technique from a published set of standards. I think your proposal is helpful in this regard and I do not see any negative outcomes to making the proposed changes. Thanks. Best Regards, /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com WWW: http://www.tykodi.com From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:31 PM To: ipp@pwg.org Subject: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported All, I have noticed an inconsistency for how we register xxx-default, xxx-ready, and xxx-supported attributes, and how these attributes are documented in our specifications. I would like to clean up these inconsistencies in the next update of the registry. Typically the xxx-default attributes are included either in the definition and description of the Job Template attributes or in a table at the beginning of the Job Template attributes. xxx-default attributes are part of the Printer Description attributes (printer-attributes-tag) in the protocol but are registered in the Job Template section. xxx-supported attributes are defined in either the Job Template or Printer Description sections of our specifications, and then have be registered in (usually, but not always) the same sections of the registry. The most common convention is to place xxx-supported in the Job Template section when it contains values that can be used directly and in the Printer Description section otherwise (for example, when xxx-supported provides a list of member attributes that can be specified in the xxx Job Template attribute - media-col works this way) Finally, xxx-ready attributes are randomly placed in the Job Template or Printer Description sections of our specifications and the registry. They always contain values that can be used in the corresponding xxx Job Template attribute... MY PROPOSAL 1. Move all xxx-default, xxx-ready, and xxx-supported attributes in the registry to the Printer Description section where they belong (they are Printer attributes, not Job Template). 2. Make sure that JPS3 and all future IPP specs going forward define any Printer Description attributes in that section; no more subsections (or inline text or tables) for xxx-default and xxx-supported that only serve to hide the corresponding definitions. Comments? ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_03EC_01CCDA5D.8116F1C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Mike,<= o:p>

 

In terms of supporting the shift away from de= pending upon a driver always being available for every imaging device broug= ht to market, I think the xxx attributes class becomes very important becau= se it allows an imaging device to advertise its capabilities and its curren= t status to a client using a technique from a published set of standards.

 

I think your proposal is helpful in this regar= d and I do not see any negative outcomes to making the proposed changes.

 

=

Thanks.

 

Best Rega= rds,

 

/Paul

--=

Paul Tykodi
Principal Consultant
= TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile= :  603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  http://www.tykodi.com

From: ipp-bounces@pwg.org [mailto:i= pp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monda= y, January 23, 2012 6:31 PM
To: ipp@pwg.org
Subject: [I= PP] Opinions needed: xxx-default, xxx-ready, and xxx-supported

 

All,

 

=

I have noticed an inconsistency for how we = register xxx-default, xxx-ready, and xxx-supported attributes, and how thes= e attributes are documented in our specifications. I would like to clean up= these inconsistencies in the next update of the registry.

 

Typically the xxx-default attributes are included either in the def= inition and description of the Job Template attributes or in a table at the= beginning of the Job Template attributes. xxx-default attributes are part = of the Printer Description attributes (printer-attributes-tag) in the proto= col but are registered in the Job Template section.

 

xxx-supported attributes are defined in either the Job Template or Printer= Description sections of our specifications, and then have be registered in= (usually, but not always) the same sections of the registry. The most comm= on convention is to place xxx-supported in the Job Template section when it= contains values that can be used directly and in the Printer Description s= ection otherwise (for example, when xxx-supported provides a list of member= attributes that can be specified in the xxx Job Template attribute - media= -col works this way)

&nb= sp;

Finally, xxx-ready attributes = are randomly placed in the Job Template or Printer Description sections of = our specifications and the registry. They always contain values that can be= used in the corresponding xxx Job Template attribute...

 

MY PROPOSAL

 =

1. Move all xxx-default, xxx-read= y, and xxx-supported attributes in the registry to the Printer Description = section where they belong (they are Printer attributes, not Job Template).<= o:p>

 

2. Make sure that JPS3 and all future IPP specs goi= ng forward define any Printer Description attributes in that section; no mo= re subsections (or inline text or tables) for xxx-default and xxx-supported= that only serve to hide the corresponding definitions.

 

Comments?

 

____________= ____________________________________________________________

Michael Sweet, Senior Printing System= Engineer, PWG Chair

 


-- This message has been scanned for viruses and
dangerous content by MailScanner, and is
b= elieved to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_03EC_01CCDA5D.8116F1C0-- --===============1364028974== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1364028974==-- From ipp-bounces@pwg.org Tue Jan 24 03:11:19 2012 Return-Path: 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 CA7CE21F85AA for ; Tue, 24 Jan 2012 03:11:19 -0800 (PST) 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=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzlYb9k9b7s9 for ; Tue, 24 Jan 2012 03:11:17 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id C887A21F8588 for ; Tue, 24 Jan 2012 03:11:16 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6882D79622; Tue, 24 Jan 2012 06:10:48 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr6.networksolutionsemail.com (omr6.networksolutionsemail.com [205.178.146.56]) by pwg.org (Postfix) with ESMTP id 683AA79613 for ; Tue, 24 Jan 2012 06:10:30 -0500 (EST) Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr6.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id q0OBAU8m026708 for ; Tue, 24 Jan 2012 06:10:30 -0500 Authentication-Results: cm-omr4 smtp.user=ptykodi@tykodi.com; auth=pass (LOGIN) X-Authenticated-UID: ptykodi@tykodi.com Received: from [65.96.244.16] ([65.96.244.16:32797] helo=TCS2010LAPTOP) by cm-omr4 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 90/66-17039-5A19E1F4; Tue, 24 Jan 2012 06:10:29 -0500 From: "Paul Tykodi" To: References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> In-Reply-To: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> Subject: RE: [IPP] media-input-tray-check-default Date: Tue, 24 Jan 2012 06:10:34 -0500 Organization: Tykodi Consulting Services LLC Message-ID: <03f001ccda88$cb244120$616cc360$@tykodi.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQMDbWtWW2/OgrR996nx5L7jZgOVzJOuNJsQ Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ptykodi@tykodi.com List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1280573640==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 6882D79622.A981F X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============1280573640== Content-Type: multipart/alternative; boundary="----=_NextPart_000_03F1_01CCDA5E.E250AA20" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_03F1_01CCDA5E.E250AA20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Mike, For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket. I therefore prefer option #2 to resolve this issue. Best Regards, /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com WWW: http://www.tykodi.com From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org Subject: [IPP] media-input-tray-check-default All, I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. BACKGROUND PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" = 'processing-stopped') and the Printer ("printer-state" = 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. There are two ways to resolve this issue: 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. I prefer option #1. Comments? ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_03F1_01CCDA5E.E250AA20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Mike,<= o:p>

 

For production printing, I have found during = my career that it is critical to have automatic checks and balances within = the job submission workflow so that a very large job (with a significant co= st of production) is not released such that it will be printed on incorrect= media and thus be a total loss (i.e. must be destroyed and cannot be distr= ibuted – job must be run again). The AFP Consortium has the same type= of intelligence in their Intelligent Printer Data Stream specification as = we have in IPP.

 = ;

I think it is possible that s= ome vendors may have interpreted the description in the specification to me= an that the default value should refer to the function being enabled or dis= abled. If it is enabled, it then interacts with the media in the job ticket= I therefore prefer option #2 to resolve this issue.

<= p class=3DMsoNormal> 

Best Regards,

 

/Paul=

--<= o:p>

Paul Tykodi
Princip= al Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-3= 43-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  http://www.tykodi.com<= o:p>

From: ipp-bounces@pwg= .org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
S= ent: Monday, January 23, 2012 6:14 PM
To: ipp@pwg.org
S= ubject: [IPP] media-input-tray-check-default

 

All,<= o:p>

 

I am going through yet another round of updates to the IA= NA registry (this time for sure! :), and noticed that I still have the medi= a-input-tray-check-default attribute tagged as "under review". I = would like to resolve this before we submit our next round of updates to th= e registry.

 =

BACKGROUND

 

PWG = 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job T= emplate attribute thusly:

 

The “media-input-tray-check” J= ob Template attribute indicates that the Printer MUST check that the&n= bsp;characteristics of the media in the identified input tray are the same = as characteristics of the media identified by the Job's "med= ia" Job Template attribute or matched (see section 3.13= ) by the Job's "media- col" Job Template attribute. The keyw= ord values are the same input tray keyword values as are defined for&n= bsp;the "media" Job Template attribute (see section 6.3 in t= his document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom= ', etc.

 

=

Independent of the "ipp-attributes-fid= elity" operation attribute supplied by the client, if the charact= eristics differ, the Printer adds the ‘resources-are-not-ready&#= 8217; value (see section 6.1) to the job's "job-state-reasons"&nb= sp;attribute and MAY either (1) put the job into the ‘pending-held= 217; state or (2) start to process the job normally, but immediat= ely stop the job (“job-state” =3D ‘processing-stoppedR= 17;) and the Printer (“printer-state” =3D ‘stopped&#= 8217;). In either implementation, the operator can change the media in= the input tray to agree with the job or can modify the job’s &#= 8220;media” or “media-col” attributes to agree with = the input tray, depending on policy.

=

 

Table 1 (at the beginning of section 3) defines media-input-tray-check-= default and -supported.

=  

The issue is that there sho= uld not be a default media-input-tray-check value; like some other Job Temp= late attributes (e.g. overrides), it does not make sense to have a default = value for this particular attribute since it interacts with the media in th= e job ticket.

 

There are two ways to resolve this is= sue:

 

1. Drop media-input-tray-check-default from th= e registry and post an errata for 5100.3 removing the media-input-tray-chec= k-default attribute from Table 1.

 

2. Update the def= inition of media-input-tray-check-default to include the "no-value&quo= t; out-of-band value.

&n= bsp;

I prefer option #1.

 

Comments?

&nbs= p;

____________= ____________________________________________________________

Michael Sweet, Senior Printing System= Engineer, PWG Chair

 


-- This message has been scanned for viruses and
dangerous content by MailScanner, and is
b= elieved to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_03F1_01CCDA5E.E250AA20-- --===============1280573640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1280573640==-- From ipp-bounces@pwg.org Tue Jan 24 04:34:50 2012 Return-Path: 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 80EC121F855D for ; Tue, 24 Jan 2012 04:34:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.226 X-Spam-Level: X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoNzRho9KdfZ for ; Tue, 24 Jan 2012 04:34:47 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1B87C21F84E7 for ; Tue, 24 Jan 2012 04:34:47 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8FB9F79633; Tue, 24 Jan 2012 07:34:16 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR003.ACS-INC.COM (usa7109mr003.acs-inc.com [63.101.151.12]) by pwg.org (Postfix) with ESMTP id B3EA47962E for ; Tue, 24 Jan 2012 07:33:58 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgwBACikHk8Nl9IPmWdsb2JhbAA/A4JNq2IiAQEBAQEICwsHFCUPgWMBAQEEDwEMEQMlCgYkAgEIBwoEAQELBgwLAQYBRQkIAgQTCK4pAZI2iSYCASaCaz0PBA0OBAQTEQQDBAoIgj5jBIg/hQaaRw Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR003.ACS-INC.COM with ESMTP; 24 Jan 2012 06:33:57 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 24 Jan 2012 04:33:50 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Tue, 24 Jan 2012 04:33:47 -0800 Message-ID: In-Reply-To: <03f001ccda88$cb244120$616cc360$@tykodi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default thread-index: AQMDbWtWW2/OgrR996nx5L7jZgOVzJOuNJsQgAAUlyA= References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Zehler, Peter" To: X-OriginalArrivalTime: 24 Jan 2012 12:33:50.0709 (UTC) FILETIME=[6D163A50:01CCDA94] X-pwg-MailScanner: Found to be clean, Found to be clean X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1486140058==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 8FB9F79633.A9830 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1486140058== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDA94.6CEDE06C" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDA94.6CEDE06C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDA94.6CEDE06C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike,

I prefer option #2.  One= of my reason is that it allows the operator to set policy for underspecifi= ed jobs on the printer.  (If the client is not being careful, then the= printer will.)  It is a very handy feature in production printing.

Pete

 

Peter Zehler

Xerox Research Center W= ebster
Email: Peter.Z= ehler@Xerox.com
Voice: (585) 265-8755<= span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F= 497D'>
FAX: (585) 265-7441
US Mail: = Peter Zehler
Xerox Corp.
= 800 Phillips Rd.
M/S 128-25E
= Webster NY, 14580-9701

 =

From: ipp-bounces@pwg.or= g [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi
Sent:<= /b> Tuesday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subje= ct: RE: [IPP] media-input-tray-check-default

 

Hi Mike,

 

For production printing, I have fo= und during my career that it is critical to have automatic checks and balan= ces within the job submission workflow so that a very large job (with a sig= nificant cost of production) is not released such that it will be printed o= n incorrect media and thus be a total loss (i.e. must be destroyed and cann= ot be distributed – job must be run again). The AFP Consortium has th= e same type of intelligence in their Intelligent Printer Data Stream specif= ication as we have in IPP.

 

I think it is poss= ible that some vendors may have interpreted the description in the specific= ation to mean that the default value should refer to the function being ena= bled or disabled. If it is enabled, it then interacts with the media in the= job ticket I therefore prefer option #2 to resolve this issue.<= /span>

 

Best Regards,

 

/Paul<= /o:p>

--

Paul Tykod= i
Principal Consultant
TCS - Tykodi Consulting Services LLC

Te= l/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com
= WWW:  http://www.tykodi.com=

<= span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From: = ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On = Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 P= M
To: ipp@pwg.org
Subjec= t: [IPP] media-input-tray-check-default

 

All,<= /o:p>

 

I am going through yet another round of updates to the IANA re= gistry (this time for sure! :), and noticed that I still have the media-inp= ut-tray-check-default attribute tagged as "under review". I would= like to resolve this before we submit our next round of updates to the reg= istry.

 

<= /div>

BACKGROUND

 

PWG 5100.= 3 (Production Printing Set 1) defines the media-input-tray-check Job Templa= te attribute thusly:

&nb= sp;

The “= ;media-input-tray-check” Job Template attribute indicates that the Pr= inter MUST check that the characteristics of the media in the ide= ntified input tray are the same as characteristics of the media i= dentified by the Job's "media" Job Template attribute or mat= ched (see section 3.13) by the Job's "media- col" = Job Template attribute. The keyword values are the same input tray key= word values as are defined for the "media" Job Template attr= ibute (see section 6.3 in this document and [RFC2911] Appendix C), i.e= ., 'top', 'middle', 'bottom', etc.

 

Independe= nt of the "ipp-attributes-fidelity" operation attribute supplied = by the client, if the characteristics differ, the Printer adds th= e ‘resources-are-not-ready’ value (see section 6.1) to the job'= s "job-state-reasons" attribute and MAY either (1) put the j= ob into the ‘pending-held’ state or (2) start to process t= he job normally, but immediately stop the job (“job-state”= =3D ‘processing-stopped’) and the Printer (“printer-stat= e” =3D ‘stopped’). In either implementation, the ope= rator can change the media in the input tray to agree with the jo= b or can modify the job’s “media” or “media-co= l” attributes to agree with the input tray, depending on policy.=

 

Table 1 (at the beginning of section = 3) defines media-input-tray-check-default and -supported.

 

The issue is that there should not be a default media-input-tray-che= ck value; like some other Job Template attributes (e.g. overrides), it does= not make sense to have a default value for this particular attribute since= it interacts with the media in the job ticket.

 

The= re are two ways to resolve this issue:

 

1. Drop medi= a-input-tray-check-default from the registry and post an errata for 5100.3 = removing the media-input-tray-check-default attribute from Table 1.

 

2. Update the definition of media-input-tray-check-default= to include the "no-value" out-of-band value.

 

I prefer option #1.

 

Comments?

 

______________________________________________________= __________________

Mich= ael Sweet, Senior Printing System Engineer, PWG Chair

=

 


--
This message has been scanned for viruse= s and
dangerous content by = MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and dangerous content by MailScann= er, and is
believed to be clean.


--= =20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDA94.6CEDE06C-- --===============1486140058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1486140058==-- From ipp-bounces@pwg.org Tue Jan 24 04:46:34 2012 Return-Path: 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 DB04B21F8568 for ; Tue, 24 Jan 2012 04:46:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.267 X-Spam-Level: X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[AWL=0.331, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qb6yM2M1G8qT for ; Tue, 24 Jan 2012 04:46:33 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id A958621F8567 for ; Tue, 24 Jan 2012 04:46:26 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id DF40979635; Tue, 24 Jan 2012 07:46:09 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 86DD77962E for ; Tue, 24 Jan 2012 07:45:55 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArkDAGWnHk8Nh9IPdWdsb2JhbAA/A4JNq2IiAQwKDAcUJQ+BYwEBAQQPAQwRAy8qAgEIDgMEAQELBgwLAQYBRQkIAQEEARIIriIBkjeJJgIBJgiCYz0PBA0OCBMcEoI+YwSIP4UGmkc Received: from usa0300gw002.na.xerox.net ([13.135.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 24 Jan 2012 06:45:54 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 24 Jan 2012 07:45:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported Date: Tue, 24 Jan 2012 04:45:48 -0800 Message-ID: In-Reply-To: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported thread-index: AczaJzNd6hMhk2j9TemzvomdDpbMZwAbod7Q References: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> From: "Zehler, Peter" To: "Michael Sweet" , X-OriginalArrivalTime: 24 Jan 2012 12:45:52.0980 (UTC) FILETIME=[1B980940:01CCDA96] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0583965557==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: DF40979635.AA30D X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0583965557== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDA96.1AAD0AAC" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDA96.1AAD0AAC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike, I support your proposal. It also clarifies the mapping between IPP and the Semantic Model. Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:31 PM To: ipp@pwg.org Subject: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported =20 All, =20 I have noticed an inconsistency for how we register xxx-default, xxx-ready, and xxx-supported attributes, and how these attributes are documented in our specifications. I would like to clean up these inconsistencies in the next update of the registry. =20 Typically the xxx-default attributes are included either in the definition and description of the Job Template attributes or in a table at the beginning of the Job Template attributes. xxx-default attributes are part of the Printer Description attributes (printer-attributes-tag) in the protocol but are registered in the Job Template section. =20 xxx-supported attributes are defined in either the Job Template or Printer Description sections of our specifications, and then have be registered in (usually, but not always) the same sections of the registry. The most common convention is to place xxx-supported in the Job Template section when it contains values that can be used directly and in the Printer Description section otherwise (for example, when xxx-supported provides a list of member attributes that can be specified in the xxx Job Template attribute - media-col works this way) =20 Finally, xxx-ready attributes are randomly placed in the Job Template or Printer Description sections of our specifications and the registry. They always contain values that can be used in the corresponding xxx Job Template attribute... =20 MY PROPOSAL =20 1. Move all xxx-default, xxx-ready, and xxx-supported attributes in the registry to the Printer Description section where they belong (they are Printer attributes, not Job Template). =20 2. Make sure that JPS3 and all future IPP specs going forward define any Printer Description attributes in that section; no more subsections (or inline text or tables) for xxx-default and xxx-supported that only serve to hide the corresponding definitions. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDA96.1AAD0AAC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike,

I support your proposal. = ; It also clarifies the mapping between IPP and the Semantic Model.

Pete

 

=  

Peter Zehler

Xerox Research Center Webster
Email= : Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: = (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.=
M/S 128-25E
Webster NY, 14580= -9701 =

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.o= rg] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2= 012 6:31 PM
To: ipp@pwg.org
Subject: [IPP] Opinions nee= ded: xxx-default, xxx-ready, and xxx-supported

<= /div>

 

All,

 

I have noticed an inconsistency for how we register xxx-def= ault, xxx-ready, and xxx-supported attributes, and how these attributes are= documented in our specifications. I would like to clean up these inconsist= encies in the next update of the registry.

 

Typicall= y the xxx-default attributes are included either in the definition and desc= ription of the Job Template attributes or in a table at the beginning of th= e Job Template attributes. xxx-default attributes are part of the Printer D= escription attributes (printer-attributes-tag) in the protocol but are regi= stered in the Job Template section.

 

xxx-supported a= ttributes are defined in either the Job Template or Printer Description sec= tions of our specifications, and then have be registered in (usually, but n= ot always) the same sections of the registry. The most common convention is= to place xxx-supported in the Job Template section when it contains values= that can be used directly and in the Printer Description section otherwise= (for example, when xxx-supported provides a list of member attributes that= can be specified in the xxx Job Template attribute - media-col works this = way)

 

Finally, xxx-ready attributes are randomly pla= ced in the Job Template or Printer Description sections of our specificatio= ns and the registry. They always contain values that can be used in the cor= responding xxx Job Template attribute...

 

MY PROPOS= AL

 

1. Move all xxx-default, xxx-ready, and xxx-supp= orted attributes in the registry to the Printer Description section where t= hey belong (they are Printer attributes, not Job Template).

<= /div>

 

2. Make sure that JPS3 and all future IPP specs going forward defi= ne any Printer Description attributes in that section; no more subsections = (or inline text or tables) for xxx-default and xxx-supported that only serv= e to hide the corresponding definitions.

 

Comments?=

 

<= div>

__________________________= ______________________________________________

<= div>

Michael Sweet, Senior Printing System Engineer, PWG= Chair

 


--
This message= has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be = clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDA96.1AAD0AAC-- --===============0583965557== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0583965557==-- From ipp-bounces@pwg.org Tue Jan 24 08:54:00 2012 Return-Path: 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 D096A21F855D for ; Tue, 24 Jan 2012 08:54:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.273 X-Spam-Level: X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.324, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IUPzm3B9P-tc for ; Tue, 24 Jan 2012 08:53:59 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 014B021F8543 for ; Tue, 24 Jan 2012 08:53:59 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id AC3AB79640; Tue, 24 Jan 2012 11:53:37 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 3A4D77963C for ; Tue, 24 Jan 2012 11:53:23 -0500 (EST) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LYB004WWAV76Q11@mail-out.apple.com> for ipp@pwg.org; Tue, 24 Jan 2012 08:52:51 -0800 (PST) X-AuditID: 1180711d-b7b41ae000004823-40-4f1ee1e1c379 Received: from [17.151.80.175] (Unknown_Domain [17.151.80.175]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id D8.8E.18467.2E1EE1F4; Tue, 24 Jan 2012 08:52:50 -0800 (PST) Subject: Re: [IPP] media-input-tray-check-default From: Michael Sweet In-reply-to: Date: Tue, 24 Jan 2012 08:52:52 -0800 Message-id: References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> To: "Zehler, Peter" X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUiOD1gve6jh3L+Bl9OaVkc2/eSxeLIt1iL jicrWR2YPbae/MHmMW/xdCaP5afWswUwR3HZpKTmZJalFunbJXBlfG26wVyw4xNjxfaLe9gb GPsuM3YxcnJICJhIfLjwnBnCFpO4cG89WxcjF4eQwFQmif4d51lBEsIChhIzHk9mB7F5BfQk 9p2dB9bMLJAgsbdjFZjNJqAm8XtSH1g9p0CAxLJX78HqWQRUJSbsWcwMUc8vcbD3AzPEHBuJ lydfsEAsW8so8eTPMbCEiICOxMaH+6EukpW4eGAS6wRGvllIds9CshvC1pZYtvA1M4RtIPG0 8xUrpri+xJt3c5gWMLKtYhQsSs1JrDQ01kssKMhJ1UvOz93ECArfhkLZHYz7f/IfYhTgYFTi 4T00TdZfiDWxrLgy9xCjBAezkgjvygY5fyHelMTKqtSi/Pii0pzU4kOM0hwsSuK8m9dL+gsJ pCeWpGanphakFsFkmTg4pRoYS3bskvB9uH3D5aoo8UPHLXnWbWGa+U4y6Ky2y1XO78s2F3Jf 1k94sIzjRtgOL7dOFk8dV0WDe8xHHrPkRV500lUV/S724VvepUf5XgkWNf9/9k2RiJ2c0PNi u4Gpl+lmLeazmQ6vd6VafLGzOGjn0jz3pvfabrW7rWdkXKKCZTKeFl77bciqxFKckWioxVxU nAgAy7Od8lsCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0912905720==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: AC3AB79640.A9489 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0912905720== Content-type: multipart/alternative; boundary="Boundary_(ID_Dbkv6Uyt0sszdvqwq15Qbw)" --Boundary_(ID_Dbkv6Uyt0sszdvqwq15Qbw) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable OK, I'm convinced. I'll add "no-value" to this one and any others like it = where it would not always make sense to force a default value. On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: > Mike, > I prefer option #2. One of my reason is that it allows the operator to s= et policy for underspecified jobs on the printer. (If the client is not be= ing careful, then the printer will.) It is a very handy feature in product= ion printing. > Pete >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul = Tykodi > Sent: Tuesday, January 24, 2012 6:11 AM > To: ipp@pwg.org > Subject: RE: [IPP] media-input-tray-check-default >=20=20 > Hi Mike, >=20=20 > For production printing, I have found during my career that it is critica= l to have automatic checks and balances within the job submission workflow = so that a very large job (with a significant cost of production) is not rel= eased such that it will be printed on incorrect media and thus be a total l= oss (i.e. must be destroyed and cannot be distributed =96 job must be run a= gain). The AFP Consortium has the same type of intelligence in their Intell= igent Printer Data Stream specification as we have in IPP. >=20=20 > I think it is possible that some vendors may have interpreted the descrip= tion in the specification to mean that the default value should refer to th= e function being enabled or disabled. If it is enabled, it then interacts w= ith the media in the job ticket I therefore prefer option #2 to resolve thi= s issue. >=20=20 > Best Regards, >=20=20 > /Paul > -- > Paul Tykodi > Principal Consultant > TCS - Tykodi Consulting Services LLC >=20 > Tel/Fax: 603-343-1820 > Mobile: 603-866-0712 > E-mail: ptykodi@tykodi.com > WWW: http://www.tykodi.com > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Monday, January 23, 2012 6:14 PM > To: ipp@pwg.org > Subject: [IPP] media-input-tray-check-default >=20=20 > All, >=20=20 > I am going through yet another round of updates to the IANA registry (thi= s time for sure! :), and noticed that I still have the media-input-tray-che= ck-default attribute tagged as "under review". I would like to resolve this= before we submit our next round of updates to the registry. >=20=20 > BACKGROUND >=20=20 > PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check= Job Template attribute thusly: >=20=20 > The =93media-input-tray-check=94 Job Template attribute indicates that th= e Printer MUST check that the characteristics of the media in the identifie= d input tray are the same as characteristics of the media identified by the= Job's "media" Job Template attribute or matched (see section 3.13) by the = Job's "media- col" Job Template attribute. The keyword values are the same = input tray keyword values as are defined for the "media" Job Template attri= bute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'to= p', 'middle', 'bottom', etc. >=20=20 > Independent of the "ipp-attributes-fidelity" operation attribute supplied= by the client, if the characteristics differ, the Printer adds the =91reso= urces-are-not-ready=92 value (see section 6.1) to the job's "job-state-reas= ons" attribute and MAY either (1) put the job into the =91pending-held=92 s= tate or (2) start to process the job normally, but immediately stop the job= (=93job-state=94 =3D =91processing-stopped=92) and the Printer (=93printer= -state=94 =3D =91stopped=92). In either implementation, the operator can ch= ange the media in the input tray to agree with the job or can modify the jo= b=92s =93media=94 or =93media-col=94 attributes to agree with the input tra= y, depending on policy. >=20=20 > Table 1 (at the beginning of section 3) defines media-input-tray-check-de= fault and -supported. >=20=20 > The issue is that there should not be a default media-input-tray-check va= lue; like some other Job Template attributes (e.g. overrides), it does not = make sense to have a default value for this particular attribute since it i= nteracts with the media in the job ticket. >=20=20 > There are two ways to resolve this issue: >=20=20 > 1. Drop media-input-tray-check-default from the registry and post an erra= ta for 5100.3 removing the media-input-tray-check-default attribute from Ta= ble 1. >=20=20 > 2. Update the definition of media-input-tray-check-default to include the= "no-value" out-of-band value. >=20=20 > I prefer option #1. >=20=20 > Comments? >=20=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_Dbkv6Uyt0sszdvqwq15Qbw) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable OK, I'm convinced.  I'll add "no-value" to this one and any others li= ke it where it would not always make sense to force a default value.

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:
Mike,<= /div>
I prefer option #2.  One of my reason is that = it allows the operator to set policy for underspecified jobs on the printer= .  (If the client is not being careful, then the printer will.)  = It is a very handy feature in production printing.
<= div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-b= ottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">= Pete
=  
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler@X= erox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.=
M/S 128-25E
Webster NY, 14580-9701
 
<= b>From:<= /span> ipp-= bounces@pwg.org [mail= to:ipp-bounces@pwg.org] <= b>On Behalf Of Paul T= ykodi
Sent: Tue= sday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-de= fault
 
Hi Mike,
 
For production printing, I have found dur= ing my career that it is critical to have automatic checks and balances wit= hin the job submission workflow so that a very large job (with a significan= t cost of production) is not released such that it will be printed on incor= rect media and thus be a total loss (i.e. must be destroyed and cannot be d= istributed =96 job must be run again). The AFP Consortium has the same type= of intelligence in their Intelligent Printer Data Stream specification as = we have in IPP.
 =
I think it is possible that some vendors ma= y have interpreted the description in the specification to mean that the de= fault value should refer to the function being enabled or disabled. If it i= s enabled, it then interacts with the media in the job ticket I therefore p= refer option #2 to resolve this issue.
 
Best Regards,<= /o:p>
 
/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Se= rvices LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-= mail:  ptykodi@tykodi.com
WW= W:  http://www.tykodi.com
From: ipp-bounces@pwg.org [mai= lto:ipp-bounces@pwg.org] On Behalf Of M= ichael Sweet
Sent: Monday, January 23, 2012 6:14 PM
To: ipp@pwg.org
Subject: [IPP] media-input-tray-check-= default
 
All,
 
I am going through y= et another round of updates to the IANA registry (this time for sure! :), a= nd noticed that I still have the media-input-tray-check-default attribute t= agged as "under review". I would like to resolve this before we submit our = next round of updates to the registry.
&nb= sp;
BACKGROUND
&nbs= p;
PWG 5100.3 (Production Printing Set 1) defines th= e media-input-tray-check Job Template attribute thusly:
 
The =93m= edia-input-tray-check=94 Job Template attribute indicates that the Printer = MUST check that the characteristics of the media in the identifie= d input tray are the same as characteristics of the media identif= ied by the Job's "media" Job Template attribute or matched (see s= ection 3.13) by the Job's "media- col" Job Template attribute. Th= e keyword values are the same input tray keyword values as are defined= for the "media" Job Template attribute (see section 6.3 in this = document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', e= tc.
 
Independ= ent of the "ipp-attributes-fidelity" operation attribute supplied by the cl= ient, if the characteristics differ, the Printer adds the =91reso= urces-are-not-ready=92 value (see section 6.1) to the job's "job-state-reas= ons" attribute and MAY either (1) put the job into the =91pending-held= =92 state or (2) start to process the job normally, but immediate= ly stop the job (=93job-state=94 =3D =91processing-stopped=92) and the Prin= ter (=93printer-state=94 =3D =91stopped=92). In either implementation,= the operator can change the media in the input tray to agree with&nbs= p;the job or can modify the job=92s =93media=94 or =93media-col=94 att= ributes to agree with the input tray, depending on policy.<= /div>
 
Table 1 (= at the beginning of section 3) defines media-input-tray-check-default and -= supported.
 
T= he issue is that there should not be a default media-input-tray-check value= ; like some other Job Template attributes (e.g. overrides), it does not mak= e sense to have a default value for this particular attribute since it inte= racts with the media in the job ticket.
&n= bsp;
There are two ways to resolve this issue:<= /o:p>
 
1. Drop media-inp= ut-tray-check-default from the registry and post an errata for 5100.3 remov= ing the media-input-tray-check-default attribute from Table 1.
 
2. Update the definition= of media-input-tray-check-default to include the "no-value" out-of-band va= lue.
 
I prefe= r option #1.
 
=
Comments?
 
___________________________________________________________= _____________
Michael Sweet, Senior P= rinting System Engineer, PWG Chair
 

-- 
This message has been scanned for viruses and=  
dangerous content by=  M= ailScanner, and is 
believed to be clean.

-- 
This message has been scanned for viruses an= d 
dangerous content b= y = MailScanner, and is 
believed to be clean.

-- 
This message has been scanned for viru= ses and 
dangerous con= tent by &nbs= p;
believed to be clean. ________________________________________= _______
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

_______________________________________= ___________
Michael Sweet, Senior Printing System Engineer, = PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_Dbkv6Uyt0sszdvqwq15Qbw)-- --===============0912905720== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0912905720==-- From ipp-bounces@pwg.org Tue Jan 24 09:40:23 2012 Return-Path: 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 7C3F121F84F4 for ; Tue, 24 Jan 2012 09:40:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.937 X-Spam-Level: X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[AWL=0.661, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OCU9V5Mo+FD for ; Tue, 24 Jan 2012 09:40:22 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3F42C21F84E2 for ; Tue, 24 Jan 2012 09:40:22 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 46F1D7964D; Tue, 24 Jan 2012 12:40:05 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by pwg.org (Postfix) with ESMTP id 867267963D for ; Tue, 24 Jan 2012 12:39:50 -0500 (EST) Received: by wgbds10 with SMTP id ds10so2818567wgb.11 for ; Tue, 24 Jan 2012 09:39:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mYIbGSZh7IwQ0VCyr3k/urRSTwKonpsSb5FrtiELOB8=; b=UF3sjndc2aVrJjhAuf3kZKPP4X8J9a338nmbcRzFN+qKuJQvThHNMjcAADIWMhPBF5 ol4pX5azdHoePQumCSV1891ivrx33P6ztqO2N/YFn8miykCZIqMfIwgQka8jXoVYGmGJ NSV+W2zcC+KUAQ0ahEJf0Uvo2Kw4eGEJ+Wa6o= MIME-Version: 1.0 Received: by 10.180.97.166 with SMTP id eb6mr22726499wib.5.1327426789543; Tue, 24 Jan 2012 09:39:49 -0800 (PST) Received: by 10.223.96.73 with HTTP; Tue, 24 Jan 2012 09:39:49 -0800 (PST) In-Reply-To: References: <1127B339-855B-4729-855D-6186C3892E7A@apple.com> Date: Tue, 24 Jan 2012 12:39:49 -0500 Message-ID: Subject: Re: [IPP] Opinions needed: xxx-default, xxx-ready, and xxx-supported From: Ira McDonald To: "Zehler, Peter" , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2101570099==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 46F1D7964D.A9B86 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2101570099== Content-Type: multipart/alternative; boundary=f46d0443066441905b04b749a2dd --f46d0443066441905b04b749a2dd Content-Type: text/plain; charset=ISO-8859-1 Hi Mike, I also support your proposal - a good clarification of an originally confusing aspect of IPP/1.1 spec. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Jan 24, 2012 at 7:45 AM, Zehler, Peter wrote: > Mike,**** > > I support your proposal. It also clarifies the mapping between IPP and > the Semantic Model.**** > > Pete**** > > ** ** > > ** ** > > Peter Zehler > > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 **** > > ** ** > > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] *On Behalf Of *Michael > Sweet > *Sent:* Monday, January 23, 2012 6:31 PM > *To:* ipp@pwg.org > *Subject:* [IPP] Opinions needed: xxx-default, xxx-ready, and > xxx-supported**** > > ** ** > > All,**** > > ** ** > > I have noticed an inconsistency for how we register xxx-default, > xxx-ready, and xxx-supported attributes, and how these attributes are > documented in our specifications. I would like to clean up these > inconsistencies in the next update of the registry.**** > > ** ** > > Typically the xxx-default attributes are included either in the definition > and description of the Job Template attributes or in a table at the > beginning of the Job Template attributes. xxx-default attributes are part > of the Printer Description attributes (printer-attributes-tag) in the > protocol but are registered in the Job Template section.**** > > ** ** > > xxx-supported attributes are defined in either the Job Template or Printer > Description sections of our specifications, and then have be registered in > (usually, but not always) the same sections of the registry. The most > common convention is to place xxx-supported in the Job Template section > when it contains values that can be used directly and in the Printer > Description section otherwise (for example, when xxx-supported provides a > list of member attributes that can be specified in the xxx Job Template > attribute - media-col works this way)**** > > ** ** > > Finally, xxx-ready attributes are randomly placed in the Job Template or > Printer Description sections of our specifications and the registry. They > always contain values that can be used in the corresponding xxx Job > Template attribute...**** > > ** ** > > MY PROPOSAL**** > > ** ** > > 1. Move all xxx-default, xxx-ready, and xxx-supported attributes in the > registry to the Printer Description section where they belong (they are > Printer attributes, not Job Template).**** > > ** ** > > 2. Make sure that JPS3 and all future IPP specs going forward define any > Printer Description attributes in that section; no more subsections (or > inline text or tables) for xxx-default and xxx-supported that only serve to > hide the corresponding definitions.**** > > ** ** > > Comments?**** > > ** ** > > ________________________________________________________________________** > ** > > Michael Sweet, Senior Printing System Engineer, PWG Chair**** > > ** ** > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. **** > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d0443066441905b04b749a2dd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Mike,

I also support your proposal - a good clarification
of a= n originally confusing aspect of IPP/1.1 spec.

Cheers,
- Ira
<= br clear=3D"all">Ira McDonald (Musician / Software Architect)
Chair - Li= nux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP= WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded= Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites= .google.com/site/blueroofmusic
http://si= tes.google.com/site/highnorthinc
mailto:blueroo= fmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 = 734-944-0094
Summer=A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2= 434



On Tue, Jan 24, 2012 at 7:45 AM, Zehler,= Peter <Pete= r.Zehler@xerox.com> wrote:

Mike,

I support your proposal.=A0 It also clarifies th= e mapping between IPP and the Semantic Model.

Pete

=A0

=A0

Peter Zehler

Xerox Research Center Webster
<= span style=3D"font-size:10.0pt;font-family:"Arial","sans-ser= if";color:navy">Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.<= br> 800 Phillips Rd.
M/S 128-25E<= br> Webster NY, 14580-9701

<= u>=A0

From: ipp-bounces@pwg.org [= mailto:ipp-bounces= @pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:31 PM
To: ipp@pwg.org
Subject: [IPP] = Opinions needed: xxx-default, xxx-ready, and xxx-supported

=A0

All,

=A0

I have notic= ed an inconsistency for how we register xxx-default, xxx-ready, and xxx-sup= ported attributes, and how these attributes are documented in our specifica= tions. I would like to clean up these inconsistencies in the next update of= the registry.

=A0

Typically the xxx-default attributes are included either in = the definition and description of the Job Template attributes or in a table= at the beginning of the Job Template attributes. xxx-default attributes ar= e part of the Printer Description attributes (printer-attributes-tag) in th= e protocol but are registered in the Job Template section.

=A0

xxx-supported attributes are defined in either the Job Templ= ate or Printer Description sections of our specifications, and then have be= registered in (usually, but not always) the same sections of the registry.= The most common convention is to place xxx-supported in the Job Template s= ection when it contains values that can be used directly and in the Printer= Description section otherwise (for example, when xxx-supported provides a = list of member attributes that can be specified in the xxx Job Template att= ribute - media-col works this way)

=A0

Finally, xxx-ready attributes are randomly placed in the Job= Template or Printer Description sections of our specifications and the reg= istry. They always contain values that can be used in the corresponding xxx= Job Template attribute...

=A0

MY PROPOSAL

=A0

1. Move all xxx-d= efault, xxx-ready, and xxx-supported attributes in the registry to the Prin= ter Description section where they belong (they are Printer attributes, not= Job Template).

=A0

2. Make sure that JPS3 and all future IPP specs going forwar= d define any Printer Description attributes in that section; no more subsec= tions (or inline text or tables) for xxx-default and xxx-supported that onl= y serve to hide the corresponding definitions.

=A0

Comments?

=A0

______________________________________________________________= __________

Michael Sweet, Senior Printing Sys= tem Engineer, PWG Chair

=A0

--
This message has been scanned for viruses and
dangerous conten= t by MailScan= ner, and is
believed to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
ipp mailing list
ipp@pwg.org
http= s://www.pwg.org/mailman/listinfo/ipp



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d0443066441905b04b749a2dd-- --===============2101570099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2101570099==-- From ipp-bounces@pwg.org Tue Jan 24 09:45:54 2012 Return-Path: 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 349BA21F8574 for ; Tue, 24 Jan 2012 09:45:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2s+U9QHFXM3T for ; Tue, 24 Jan 2012 09:45:52 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 69C2221F8573 for ; Tue, 24 Jan 2012 09:45:52 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 3930B7965A; Tue, 24 Jan 2012 12:45:27 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by pwg.org (Postfix) with ESMTP id C3C267964D for ; Tue, 24 Jan 2012 12:45:08 -0500 (EST) Received: by wgbgn7 with SMTP id gn7so567647wgb.5 for ; Tue, 24 Jan 2012 09:45:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7RNvECZ20+d3GSvOtkgKS2h3hqbFH1loF+5YdS+xEMM=; b=A7KhmJt1gozICRZ0QzrMn+8PPDfDkjiAJUU7GmbwZejrDzhjzDsvRIGTbxCq7JhLcM JX21H4epfug+AD6T8t13VQt37AgFZGCsqkLJjl/66F3LN0AbJStCVid0slDBTnk7gdBM cINke22woCF/6a2b2l1PJO05rUt5tIP1yaK1E= MIME-Version: 1.0 Received: by 10.180.100.234 with SMTP id fb10mr5497823wib.5.1327427107941; Tue, 24 Jan 2012 09:45:07 -0800 (PST) Received: by 10.223.96.73 with HTTP; Tue, 24 Jan 2012 09:45:07 -0800 (PST) In-Reply-To: References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> Date: Tue, 24 Jan 2012 12:45:07 -0500 Message-ID: Subject: Re: [IPP] media-input-tray-check-default From: Ira McDonald To: Michael Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0942353706==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 3930B7965A.A9642 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0942353706== Content-Type: multipart/alternative; boundary=f46d043748f33bee4304b749b5e2 --f46d043748f33bee4304b749b5e2 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Mike, Thanks - I agree w/ Pete about the advantages of option 2 - and this is a more backward compatible solution than actually deleting a previously registered (and apparently implemented) IPP attribute. The 'no-value' approach to special "xxx-default" attributes is elegant. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Jan 24, 2012 at 11:52 AM, Michael Sweet wrote: > OK, I'm convinced. I'll add "no-value" to this one and any others like it > where it would not always make sense to force a default value. > > > On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: > > Mike,**** > I prefer option #2. One of my reason is that it allows the operator to > set policy for underspecified jobs on the printer. (If the client is not > being careful, then the printer will.) It is a very handy feature in > production printing.**** > Pete**** > ** ** > Peter Zehler > > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701**** > ** ** > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] *On Behalf Of *P= aul > Tykodi > *Sent:* Tuesday, January 24, 2012 6:11 AM > *To:* ipp@pwg.org > *Subject:* RE: [IPP] media-input-tray-check-default**** > ** ** > Hi Mike,**** > ** ** > For production printing, I have found during my career that it is critical > to have automatic checks and balances within the job submission workflow = so > that a very large job (with a significant cost of production) is not > released such that it will be printed on incorrect media and thus be a > total loss (i.e. must be destroyed and cannot be distributed =96 job must= be > run again). The AFP Consortium has the same type of intelligence in their > Intelligent Printer Data Stream specification as we have in IPP.**** > ** ** > I think it is possible that some vendors may have interpreted the > description in the specification to mean that the default value should > refer to the function being enabled or disabled. If it is enabled, it then > interacts with the media in the job ticket I therefore prefer option #2 to > resolve this issue.**** > ** ** > Best Regards,**** > ** ** > /Paul**** > --**** > Paul Tykodi > Principal Consultant > TCS - Tykodi Consulting Services LLC > > Tel/Fax: 603-343-1820 > Mobile: 603-866-0712 > E-mail: ptykodi@tykodi.com > WWW: http://www.tykodi.com**** > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] *On Behalf Of *M= ichael > Sweet > *Sent:* Monday, January 23, 2012 6:14 PM > *To:* ipp@pwg.org > *Subject:* [IPP] media-input-tray-check-default**** > ** ** > All,**** > ** ** > I am going through yet another round of updates to the IANA registry (this > time for sure! :), and noticed that I still have the > media-input-tray-check-default attribute tagged as "under review". I would > like to resolve this before we submit our next round of updates to the > registry.**** > ** ** > BACKGROUND**** > ** ** > PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check > Job Template attribute thusly:**** > ** ** > > The =93media-input-tray-check=94 Job Template attribute indicates that the > Printer MUST check that the characteristics of the media in the identified > input tray are the same as characteristics of the media identified by the > Job's "media" Job Template attribute or matched (see section 3.13) by the > Job's "media- col" Job Template attribute. The keyword values are the same > input tray keyword values as are defined for the "media" Job Template > attribute (see section 6.3 in this document and [RFC2911] Appendix C), > i.e., 'top', 'middle', 'bottom', etc.**** > ** ** > Independent of the "ipp-attributes-fidelity" operation attribute supplied > by the client, if the characteristics differ, the Printer adds the > =91resources-are-not-ready=92 value (see section 6.1) to the job's > "job-state-reasons" attribute and MAY either (1) put the job into the > =91pending-held=92 state or (2) start to process the job normally, but > immediately stop the job (=93job-state=94 =3D =91processing-stopped=92) a= nd the > Printer (=93printer-state=94 =3D =91stopped=92). In either implementation= , the > operator can change the media in the input tray to agree with the job or > can modify the job=92s =93media=94 or =93media-col=94 attributes to agree= with the > input tray, depending on policy.**** > > ** ** > Table 1 (at the beginning of section 3) defines > media-input-tray-check-default and -supported.**** > ** ** > The issue is that there should not be a default media-input-tray-check > value; like some other Job Template attributes (e.g. overrides), it does > not make sense to have a default value for this particular attribute since > it interacts with the media in the job ticket.**** > ** ** > There are two ways to resolve this issue:**** > ** ** > 1. Drop media-input-tray-check-default from the registry and post an > errata for 5100.3 removing the media-input-tray-check-default attribute > from Table 1.**** > ** ** > 2. Update the definition of media-input-tray-check-default to include the > "no-value" out-of-band value.**** > ** ** > I prefer option #1.**** > ** ** > Comments?**** > **** > ________________________________________________________________________** > ** > Michael Sweet, Senior Printing System Engineer, PWG Chair**** > ** ** > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean.**** > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean.**** > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > > __________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d043748f33bee4304b749b5e2 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Mike,

Thanks - I agree w/ Pete about the advantages of
option = 2 - and this is a more backward compatible
solution than actually deleti= ng a previously registered
(and apparently implemented) IPP attribute.
The 'no-value' approach to special "xxx-default"
a= ttributes is elegant.

Cheers,
- Ira



Ira McDonald (= Musician / Software Architect)
Chair - Linux Foundation Open Printing WG=
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP= WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded= Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites= .google.com/site/blueroofmusic
http://si= tes.google.com/site/highnorthinc
mailto:blueroo= fmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 = 734-944-0094
Summer=A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2= 434



On Tue, Jan 24, 2012 at 11:52 AM, Michae= l Sweet <msweet@ap= ple.com> wrote:
OK, I'm convinced. =A0I'll add = "no-value" to this one and any others like it where it would not = always make sense to force a default value.


On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:

Mike,
I prefer option #2.=A0 One of my reason is that it allows the operator t= o set policy for underspecified jobs on the printer.=A0 (If the client is n= ot being careful, then the printer will.)=A0 It is a very handy feature in = production printing.
Pete
= =A0
Peter Ze= hler

Xerox Research Center Webster
Email:=A0Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
=A0
From:= =A0ipp-bounces@pwg.org=A0[ma= ilto:ipp-bounces@p= wg.org]=A0On Behalf Of=A0Paul Tykodi Sent:=A0Tuesday, January 24, 2012 6:11 AM
To:= =A0ipp@pwg.org
Subject:=A0RE: [IPP] media-input-tray-check-default=
=A0
Hi Mike,
=A0
For production printing, I have found during my career that it is c= ritical to have automatic checks and balances within the job submission wor= kflow so that a very large job (with a significant cost of production) is n= ot released such that it will be printed on incorrect media and thus be a t= otal loss (i.e. must be destroyed and cannot be distributed =96 job must be= run again). The AFP Consortium has the same type of intelligence in their = Intelligent Printer Data Stream specification as we have in IPP.<= /u>
=A0
I think it is possible that some vendors may have interpreted the descri= ption in the specification to mean that the default value should refer to t= he function being enabled or disabled. If it is enabled, it then interacts = with the media in the job ticket I therefore prefer option #2 to resolve th= is issue.
=A0
Best Regards,
=A0
/Paul
= --
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax= : 603= -343-1820
Mobile:=A0 603-866-0712
E-mail:=A0=A0ptykodi@tykodi.com<= /a>
WWW:=A0=A0http://www.tykodi.com
From:= =A0ipp-bounces@pwg.org=A0[mailto:ipp-bounces@pwg.org]= =A0On Behalf Of=A0Michael Sweet
Sent:=A0Monday, January 23, 2012 6:14 PM
To:<= span>=A0ipp@pwg.org
Subject:=A0[IPP] media-input-tray-check-default
=A0
All,
=A0
I am going through yet another round of updates to the IANA registry (this = time for sure! :), and noticed that I still have the media-input-tray-check= -default attribute tagged as "under review". I would like to reso= lve this before we submit our next round of updates to the registry.=
=A0
BACKGROUND
=A0
PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check J= ob Template attribute thusly:
=A0
The =93media-input-tray-check=94 Job Template attribute indicates that the = Printer MUST check=A0that the=A0characteristics of the media in the identif= ied input tray are the same as characteristics=A0of the media=A0identified = by the Job's "media" Job Template attribute or=A0matched=A0(s= ee section=A03.13) by the Job's "media-=A0col" Job Template a= ttribute. The keyword values are the same input=A0tray keyword values as ar= e defined for=A0the "media" Job Template attribute (see section 6= .3 in=A0this document and [RFC2911] Appendix C), i.e.,=A0'top', = 9;middle', 'bottom', etc.
=A0
Independent of the "ipp-attributes-fidelity" operation attribute = supplied by the client, if the=A0characteristics=A0differ, the Printer adds= the =91resources-are-not-ready=92 value (see section 6.1) to the job's= "job-state-reasons"=A0attribute and MAY either (1) put the job i= nto the =91pending-held=92 state or (2)=A0start to process the job=A0normal= ly, but immediately stop the job (=93job-state=94 =3D =91processing-stopped= =92) and the Printer (=93printer-state=94=A0=3D =91stopped=92). In either i= mplementation, the operator=A0can change the media in the input tray to agr= ee with=A0the job or can modify the job=92s =93media=94 or=A0=93media-col= =94 attributes to agree with the input tray, depending on=A0policy.<= u>
=A0
Table 1 (at the beginning of section 3) defines media-input-tray-check-defa= ult and -supported.
=A0
The issue is that there should not be a defaul= t media-input-tray-check value; like some other Job Template attributes (e.= g. overrides), it does not make sense to have a default value for this part= icular attribute since it interacts with the media in the job ticket.
=A0
There are two ways to resolve this issue:
= =A0
1. Drop media-input-tray-check-default from the registry and post an = errata for 5100.3 removing the media-input-tray-check-default attribute fro= m Table 1.
=A0
2. Update the definition of media-input-tray-check-default to include the &= quot;no-value" out-of-band value.
=A0
I prefer option #1.
<= div>
=A0
Comments?
=A0
= _________________= _______________________________________________________
Michael Swe= et, Senior Printing System Engineer, PWG Chair
=A0

--=A0
This message has been scanned for viruses and=A0
dangerous content by=A0MailScanner, and is=A0
believed to be clean.

--=A0
This message = has been scanned for viruses and=A0
dangerous content by=A0Mai= lScanner, and is=A0
believed to be clean.=

--=A0
This message has been scanned for viruses a= nd=A0
dangerous content by=A0MailScanner, and is=A0
believed to be clean. _________________________________________= ______
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listi= nfo/ipp

__________________________________________________
Michael Sweet,= Senior Printing System=A0Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
ipp mailing list
ipp@pwg.org
http= s://www.pwg.org/mailman/listinfo/ipp



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d043748f33bee4304b749b5e2-- --===============0942353706== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0942353706==-- From ipp-bounces@pwg.org Tue Jan 24 14:34:39 2012 Return-Path: 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 BE82311E8085 for ; Tue, 24 Jan 2012 14:34:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.54 X-Spam-Level: X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENmx34hp1+ao for ; Tue, 24 Jan 2012 14:34:35 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB0211E8079 for ; Tue, 24 Jan 2012 14:34:35 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 39A5979662; Tue, 24 Jan 2012 17:34:04 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 2B69479661 for ; Tue, 24 Jan 2012 17:33:42 -0500 (EST) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Jan 2012 14:33:41 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Tue, 24 Jan 2012 14:33:39 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: AczauMkXWqam3NUJQZq+ujspdYVxewALyZTg References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com><03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Petrie, Glen" To: "Michael Sweet" , "Zehler, Peter" X-OriginalArrivalTime: 24 Jan 2012 22:33:41.0886 (UTC) FILETIME=[398001E0:01CCDAE8] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1035774103==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 39A5979662.A9AD4 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1035774103== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDAE8.38E4A0EA" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDAE8.38E4A0EA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDAE8.38E4A0EA Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Should the value of “Unknown&#= 8221; be used?   Below is the statement from rfc2911

 

Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band"= value 'unknown'.  See the description of the "out-of-=

   band" values at th= e beginning of Section 4.1.  Therefore, attributes

   of type 'enum' start at= '3'.

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one = and any others like it where it would not always make sense to force a default value.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=



Mike,

I prefer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production prin= ting.

Pete

 

Peter Zehler

Xerox Research Center Webster
Email:&nb= sp;Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul T= ykodi
Sent: Tuesday, January 24, 2012 6:11 A= M
To: <= font color=3Dpurple>ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default

=  

Hi Mike,=

 

For production printing, I have found during my career that it is critical to have automat= ic checks and balances within the job submission workflow so that a very large= job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed= and cannot be distributed – job must be run again). The AFP Consortium ha= s the same type of intelligence in their Intelligent Printer Data Stream specification= as we have in IPP.

 

I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function b= eing enabled or disabled. If it is enabled, it then interacts with the media in = the job ticket I therefore prefer option #2 to resolve this issue.=

 

Best Regards,<= u1:p>

 

/Paul

--=

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:=   603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  = http://www.tykodi.com

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 PM=
To: <= font color=3Dpurple>ipp@pwg.org Subject: [IPP] media-input-tray-check-def= ault

=  

= All,

=  

= I am going through yet another round= of updates to the IANA registry (this time for sure! :), and noticed that I st= ill have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round = of updates to the registry.

=  

= BACKGROUND<= /p>

=  

= PWG 5100.3 (Production Printing Set = 1) defines the media-input-tray-check Job Template attribute thusly:

=  

= The “media-input-tray-check= 221; Job Template attribute indicates that the Printer MUST check that the characte= ristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see sect= ion 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.

=  

= Independent of the "ipp-attributes-fidelity" operation attribute supplied by the cli= ent, if the characteristics differ, the Printer adds the ‘resources-are-not-ready’ value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the ‘pending-held’ state or (2) start to process the = job normally, but immediately stop the job (“job-state” =3D ‘processing= -stopped’) and the Printer (“printer-state” =3D ‘stopped’). In ei= ther implementation, the operator can change the media in the input tray to agree with the= job or can modify the job’s “media” or “media-col&= #8221; attributes to agree with the input tray, depending on policy.

=  

= Table 1 (at the beginning of section= 3) defines media-input-tray-check-default and -supported.

=  

= The issue is that there should not b= e a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket.

=  

= There are two ways to resolve this i= ssue:

=  

= 1. Drop media-input-tray-check-defau= lt from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.

=  

= 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-b= and value.

=  

= I prefer option #1.

=  

= Comments?

=  

= ____________________________________= ____________________________________

= Michael Sweet, Senior Printing System Engineer, PWG Chair

=  

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
<= span style=3D'color:purple'>https://www.pwg.org/mailman/listinfo/ipp

 

______________= ____________________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDAE8.38E4A0EA-- --===============1035774103== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1035774103==-- From ipp-bounces@pwg.org Tue Jan 24 14:59:14 2012 Return-Path: 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 1F45A21F85B5 for ; Tue, 24 Jan 2012 14:59:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.54 X-Spam-Level: X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyRfAiTeMtBy for ; Tue, 24 Jan 2012 14:59:10 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id AE0F821F85AE for ; Tue, 24 Jan 2012 14:59:09 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 117E97966B; Tue, 24 Jan 2012 17:58:35 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 986B079669; Tue, 24 Jan 2012 17:58:15 -0500 (EST) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Jan 2012 14:58:14 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Tue, 24 Jan 2012 14:58:12 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: AczauMkXWqam3NUJQZq+ujspdYVxewALyZTgAADWGNA= References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com><03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Petrie, Glen" To: "Petrie, Glen" , "Michael Sweet" , "Zehler, Peter" X-OriginalArrivalTime: 24 Jan 2012 22:58:14.0685 (UTC) FILETIME=[A75B4CD0:01CCDAEB] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0398728146==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 117E97966B.AA727 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0398728146== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDAEB.A6E6CB84" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDAEB.A6E6CB84 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Pete, Mike =20 In the PJT the MediaInputTray is (I believe) is called MediaSource; so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Tuesday, January 24, 2012 2:34 PM To: Michael Sweet; Zehler, Peter Cc: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: =20 Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDAEB.A6E6CB84 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Pete, Mike<= /p>

 

In the PJT the MediaInputTray is (I believe) is called MediaSource;  so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck??

 

Glen

 

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Tuesday, January 24, 2= 012 2:34 PM
To: Michael Sweet; Zehler, P= eter
Cc: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Should the value of “Unknown” be used?   Below is the statement from rfc2= 911

 

Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band" value 'unknown'.  See the description of the "out-of-<= /span>

   band" values at the beginning of Section 4.1.  Therefore, attributes

   of type 'enum' start at '3'.

 

From: ipp-boun= ces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf = Of Michael Sweet
Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one = and any others like it where it would not always make sense to force a default valu= e.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=

 =

Mike,

I prefer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production prin= ting.

Pete

 

Peter Zehler

Xerox Research Center Webster
Email:&nb= sp;Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul T= ykodi
Sent: Tuesday, January 24, 2012 6:11 A= M
To: <= font color=3Dpurple>ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default

=  

Hi Mike,=

 

For production printing, I have found during my career that it is critical to have automat= ic checks and balances within the job submission workflow so that a very large= job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed= and cannot be distributed – job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP.

 

I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function b= eing enabled or disabled. If it is enabled, it then interacts with the media in = the job ticket I therefore prefer option #2 to resolve this issue.=

 

Best Regards,<= u1:p>

 

/Paul

--=

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:=   603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  = http://www.tykodi.com

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 PM=
To: <= font color=3Dpurple>ipp@pwg.org Subject: [IPP] media-input-tray-check-def= ault

=  

= All,

=  

= I am going through yet another round= of updates to the IANA registry (this time for sure! :), and noticed that I st= ill have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round = of updates to the registry.

=  

= BACKGROUND<= /p>

=  

= PWG 5100.3 (Production Printing Set = 1) defines the media-input-tray-check Job Template attribute thusly:

=  

= The “media-input-tray-check= 221; Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the = same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section&= nbsp;3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for = the "media" Job Template attribute (see section 6.3 in this docu= ment and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.<= /o:p>

=  =

= Independent of the "ipp-= attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the ‘resources-are-not-ready’ value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the ‘pending-held’ state or (2) start to process the job normally, but immediately stop the job (“job-state” = =3D ‘processing-stopped’) and the Printer (“printer-state” =3D ‘stopped’). In either imp= lementation, the operator can change the media in the input tray to agree with = ;the job or can modify the job’s “media” or “media-col” attributes to agree with the input tray, depending on policy.

=  

= Table 1 (at the beginning of section= 3) defines media-input-tray-check-default and -supported.

=  

= The issue is that there should not b= e a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket.

=  

= There are two ways to resolve this i= ssue:

=  

= 1. Drop media-input-tray-check-defau= lt from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.

=  

= 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-b= and value.

=  

= I prefer option #1.

=  

= Comments?

=  

= ____________________________________= ____________________________________

= Michael Sweet, Senior Printing System Engineer, PWG Chair

=  

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
<= span style=3D'color:purple'>https://www.pwg.org/mailman/listinfo/ipp

 

______________= ____________________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDAEB.A6E6CB84-- --===============0398728146== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0398728146==-- From ipp-bounces@pwg.org Tue Jan 24 15:50:46 2012 Return-Path: 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 1AEA711E809A for ; Tue, 24 Jan 2012 15:50:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.309 X-Spam-Level: X-Spam-Status: No, score=-102.309 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cs29r93Yj5Wu for ; Tue, 24 Jan 2012 15:50:39 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5210A11E809D for ; Tue, 24 Jan 2012 15:50:39 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 95C8379672; Tue, 24 Jan 2012 18:50:17 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 0A2A779672 for ; Tue, 24 Jan 2012 18:49:57 -0500 (EST) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LYB00EYJU69W362@mail-out.apple.com> for ipp@pwg.org; Tue, 24 Jan 2012 15:49:57 -0800 (PST) X-AuditID: 1180711d-b7b41ae000004823-c3-4f1f43a3f007 Received: from [17.151.80.175] (Unknown_Domain [17.151.80.175]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id F2.B6.18467.3A34F1F4; Tue, 24 Jan 2012 15:49:56 -0800 (PST) Subject: Re: [IPP] media-input-tray-check-default From: Michael Sweet In-reply-to: Date: Tue, 24 Jan 2012 15:49:54 -0800 Message-id: <955316D5-329E-48E1-9092-E66A26BBFCD1@apple.com> References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUiOD1gve4SZ3l/g1vbpCy2n/3FYnFs30sW iyPfYi06nqxkdWDx2HryB5vHwfmz2D3mLZ7O5LH81Hq2AJYoLpuU1JzMstQifbsEroy+a21s BQeuMVcsefiUtYHx2zzmLkZODgkBE4lZXfuZIGwxiQv31rN1MXJxCAlMZZJY8u8mWJGwgKHE jMeT2UFsXgE9iX1n5zGC2MwCCRLn1j5hAbHZBNQkfk/qYwWxOQW8JFb+OQFWzyKgKrH/4CQm iHpriemdfVBzbCRm3H/NArFsDpPEtT0/2UASIgL6Ep8+boa6SFbi4oFJrBMY+WYh2T0LyW4I W1ti2cLXzBC2gcTTzlesmOL6Em/ezWFawMi2ilGwKDUnsdLQWC+xoCAnVS85P3cTIyikGwpl dzDu/8l/iFGAg1GJh7dBQd5fiDWxrLgy9xCjBAezkgjvygY5fyHelMTKqtSi/Pii0pzU4kOM 0hwsSuK8m9dL+gsJpCeWpGanphakFsFkmTg4pRoYo5k/L/COlLKcvyPu6dK1Uot2p+/hjBXa E7ha1aO/8I/cBDElxlPJCx9WL397KvuiwKRwJv2zMmy/Tran7ivm+8Rws22novDynxf3OSkq Zz5Yll7gYBF7+7Erf96kSYvSvhlFL+4MyrPleefeEHzdeOab2UW9ZocXX1nH/b502daUgmX5 ChkrlFiKMxINtZiLihMBO2snY2UCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1884916685==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 95C8379672.A99AD X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1884916685== Content-type: multipart/alternative; boundary="Boundary_(ID_OWnyMZxPGsVkD178m26VGA)" --Boundary_(ID_OWnyMZxPGsVkD178m26VGA) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Glen, "unknown" is generally used for values that are produced by the printer/aut= omata. "no-value" is generally used for things that are configured by a human bein= g. For xxx-default attributes, "no-value" makes more sense than "unknown". On Jan 24, 2012, at 2:33 PM, Petrie, Glen wrote: > Should the value of =93Unknown=94 be used? Below is the statement from = rfc2911 >=20=20 > Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP > "out-of-band" value 'unknown'. See the description of the "out-of- > band" values at the beginning of Section 4.1. Therefore, attributes > of type 'enum' start at '3'. >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Tuesday, January 24, 2012 8:53 AM > To: Zehler, Peter > Cc: ipp@pwg.org > Subject: Re: [IPP] media-input-tray-check-default >=20=20 > OK, I'm convinced. I'll add "no-value" to this one and any others like i= t where it would not always make sense to force a default value. >=20=20 >=20=20 > On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: >=20 >=20 > Mike, > I prefer option #2. One of my reason is that it allows the operator to s= et policy for underspecified jobs on the printer. (If the client is not be= ing careful, then the printer will.) It is a very handy feature in product= ion printing. > Pete >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul = Tykodi > Sent: Tuesday, January 24, 2012 6:11 AM > To: ipp@pwg.org > Subject: RE: [IPP] media-input-tray-check-default >=20=20 > Hi Mike, >=20=20 > For production printing, I have found during my career that it is critica= l to have automatic checks and balances within the job submission workflow = so that a very large job (with a significant cost of production) is not rel= eased such that it will be printed on incorrect media and thus be a total l= oss (i.e. must be destroyed and cannot be distributed =96 job must be run a= gain). The AFP Consortium has the same type of intelligence in their Intell= igent Printer Data Stream specification as we have in IPP. >=20=20 > I think it is possible that some vendors may have interpreted the descrip= tion in the specification to mean that the default value should refer to th= e function being enabled or disabled. If it is enabled, it then interacts w= ith the media in the job ticket I therefore prefer option #2 to resolve thi= s issue. >=20=20 > Best Regards, >=20=20 > /Paul > -- > Paul Tykodi > Principal Consultant > TCS - Tykodi Consulting Services LLC >=20 > Tel/Fax: 603-343-1820 > Mobile: 603-866-0712 > E-mail: ptykodi@tykodi.com > WWW: http://www.tykodi.com > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Monday, January 23, 2012 6:14 PM > To: ipp@pwg.org > Subject: [IPP] media-input-tray-check-default >=20=20 > All, >=20=20 > I am going through yet another round of updates to the IANA registry (thi= s time for sure! :), and noticed that I still have the media-input-tray-che= ck-default attribute tagged as "under review". I would like to resolve this= before we submit our next round of updates to the registry. >=20=20 > BACKGROUND >=20=20 > PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check= Job Template attribute thusly: >=20=20 > The =93media-input-tray-check=94 Job Template attribute indicates that th= e Printer MUST check that the characteristics of the media in the identifie= d input tray are the same as characteristics of the media identified by the= Job's "media" Job Template attribute or matched (see section 3.13) by the = Job's "media- col" Job Template attribute. The keyword values are the same = input tray keyword values as are defined for the "media" Job Template attri= bute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'to= p', 'middle', 'bottom', etc. >=20=20 > Independent of the "ipp-attributes-fidelity" operation attribute supplied= by the client, if the characteristics differ, the Printer adds the =91reso= urces-are-not-ready=92 value (see section 6.1) to the job's "job-state-reas= ons" attribute and MAY either (1) put the job into the =91pending-held=92 s= tate or (2) start to process the job normally, but immediately stop the job= (=93job-state=94 =3D =91processing-stopped=92) and the Printer (=93printer= -state=94 =3D =91stopped=92). In either implementation, the operator can ch= ange the media in the input tray to agree with the job or can modify the jo= b=92s =93media=94 or =93media-col=94 attributes to agree with the input tra= y, depending on policy. >=20=20 > Table 1 (at the beginning of section 3) defines media-input-tray-check-de= fault and -supported. >=20=20 > The issue is that there should not be a default media-input-tray-check va= lue; like some other Job Template attributes (e.g. overrides), it does not = make sense to have a default value for this particular attribute since it i= nteracts with the media in the job ticket. >=20=20 > There are two ways to resolve this issue: >=20=20 > 1. Drop media-input-tray-check-default from the registry and post an erra= ta for 5100.3 removing the media-input-tray-check-default attribute from Ta= ble 1. >=20=20 > 2. Update the definition of media-input-tray-check-default to include the= "no-value" out-of-band value. >=20=20 > I prefer option #1. >=20=20 > Comments? >=20=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20=20 > __________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_OWnyMZxPGsVkD178m26VGA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Glen,

"= unknown" is generally used for values that are produced by the printer/auto= mata.

"no-value" is generally used for things that= are configured by a human being.

For xxx-default = attributes, "no-value" makes more sense than "unknown".


On Jan 24, 2012, at 2:33 PM, Petrie, Glen wr= ote:

Should the value of =93Unknown=94 be= used?   Below is the statement from rfc2911

 

<= p class=3D"MsoNormal">Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band" value 'unknown'.  See the description of the "out-of-

   band" values at the beg= inning of Section 4.1.  Therefore, attributes

   of type 'enum' start at= '3'.

 

From: ipp-bounces@pwg.org [mailto:ipp-= bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=



Mik= e,

I p= refer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production prin= ting.

Pet= e

 

Peter Zehler

Xerox Research Center Webster
Email:&= nbsp;Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

From: = ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul= Tykodi
Sent: Tuesday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Hi = Mike,

 

For= production printing, I have found during my career that it is critical to have automat= ic checks and balances within the job submission workflow so that a very large= job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed= and cannot be distributed =96 job must be run again). The AFP Consortium has th= e same type of intelligence in their Intelligent Printer Data Stream specification= as we have in IPP.

 

I t= hink it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function b= eing enabled or disabled. If it is enabled, it then interacts with the media in = the job ticket I therefore prefer option #2 to resolve this issue.= =

 

Bes= t Regards,

 

/Pa= ul

--

Paul Ty= kodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:=   603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  http://www.tykodi.com

From: = ipp-bounces@pwg.org [mai= lto:ipp-bounces@pwg.org] On Behalf Of Mich= ael Sweet
Sent: Monday, January 23, 2012 6:14 PM
To: ipp@pwg.org
Subject: [IPP] media-input-tray-check-default<= /o:p>

 

All,

 

I am going through = yet another round of updates to the IANA registry (this time for sure! :), and noticed that I st= ill have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry.

 

BACKGROUND

 

PWG 5100.3 (Product= ion Printing Set 1) defines the media-input-tray-check Job Template attribute thusly:

 

The =93media-input-= tray-check=94 Job Template attribute indicates that the Printer MUST check that the characte= ristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.

 

Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the =91resources-are-not-ready=92 value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the =91pending-held=92 state or (2) start to process the job = ;normally, but immediately stop the job (=93job-state=94 =3D =91processing-stopped=92)= and the Printer (=93printer-state=94 =3D =91stopped=92). In either implementat= ion, the operator can change the media in the input tray to agree with the= job or can modify the job=92s =93media=94 or =93media-col=94 attributes to= agree with the input tray, depending on policy.

 

Table 1 (at the beg= inning of section 3) defines media-input-tray-check-default and -supported.

 

The issue is that t= here should not be a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket.

 

There are two ways = to resolve this issue:

 

1. Drop media-input= -tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.

 

2. Update the defin= ition of media-input-tray-check-default to include the "no-value" out-of-band value.

 

I prefer option #1.=

 

Comments?

 

___________________= _____________________________________________________

Michael Sweet, Seni= or Printing System Engineer, PWG Chair

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

 

___= _______________________________________________

Mic= hael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________= ___
Michael Sweet, Senior Printing System Engineer, PWG Chai= r


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_OWnyMZxPGsVkD178m26VGA)-- --===============1884916685== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1884916685==-- From ipp-bounces@pwg.org Tue Jan 24 15:57:29 2012 Return-Path: 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 A5C7321F8559 for ; Tue, 24 Jan 2012 15:57:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.347 X-Spam-Level: X-Spam-Status: No, score=-102.347 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltAmSV4I265Z for ; Tue, 24 Jan 2012 15:57:28 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id E190911E809D for ; Tue, 24 Jan 2012 15:57:27 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8580779678; Tue, 24 Jan 2012 18:56:59 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 48AC279672; Tue, 24 Jan 2012 18:56:44 -0500 (EST) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LYB0047IUIB6Q22@mail-out.apple.com>; Tue, 24 Jan 2012 15:56:43 -0800 (PST) X-AuditID: 11807134-b7c42ae000000421-aa-4f1f45385bc0 Received: from [17.151.80.175] (Unknown_Domain [17.151.80.175]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 1F.27.01057.9354F1F4; Tue, 24 Jan 2012 15:56:42 -0800 (PST) Subject: Re: [IPP] media-input-tray-check-default From: Michael Sweet In-reply-to: Date: Tue, 24 Jan 2012 15:56:40 -0800 Message-id: References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUiOD1gva6Vq7y/we63rBbbz/5isTi27yWL xdb+M0wWR77FWnQ8WcnqwOqx9eQPNo+D82exe8xbPJ3JY/mp9WwBLFFcNimpOZllqUX6dglc GZuWnmYuuNDIUvF3/irmBsb+I8xdjJwcEgImEh+amqFsMYkL99azdTFycQgJTGWSmHvwEjtI QljAUGLG48lgNq+AnsS+s/MYQWxmgQSJ4yd3s4DYbAJqEr8n9bGC2JwCXhJzHnxg6mLk4GAR UJVY9cgdotxLYnf3cxaQMK+AjcSs7b4Qq24xSczv+wo2XkRAX+LTx81MEPfISlw8MIl1AiPf LCSbZyHZDGFrSyxb+JoZwjaQeNr5ihVTXF/izbs5TAsY2VYxChal5iRWGproJRYU5KTqJefn bmIEBXZDockOxoM/+Q8xCnAwKvHwNijI+wuxJpYVV+YeYpTgYFYS4V3ZIOcvxJuSWFmVWpQf X1Sak1p8iFGag0VJnHfrekl/IYH0xJLU7NTUgtQimCwTB6dUA6NW1BypL2FcsdsY3TJWxrZf VZN3nbB60dNVM2Y+Ovpib2OPwYsJXxu7k11FZZ8q6F94oN6p4Lv2wiO7m7Om8evyr/Xt3daa eN9tod2SajObzjfNjdF/p2i4sexasPHZMYPlGxgMrv9lYwiLnK3OU+ZU4b6h9H5wI98T5iWc N3sE2z6G8e+8YqHEUpyRaKjFXFScCADRU/TJaAIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2134958413==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 8580779678.AA873 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2134958413== Content-type: multipart/alternative; boundary="Boundary_(ID_XHSvRkWtr84MxCrF0177Yg)" --Boundary_(ID_XHSvRkWtr84MxCrF0177Yg) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Glen, MediaInputTrayCheck and 5100.3's media-input-tray-check use the older Print= er MIB naming convention, even though roll and slot names can be used. MediaSource comes from JPS3's media-source - "source" as a more general wor= d than "input tray" since it covers slots and rolls. We had a lot of discu= ssion about this early in the definition of media-source for JPS3 and concl= uded that we should break the chain and use the new name. (oh, and realizi= ng that we have printer-input-tray and printer-output-tray mapped from the = MIB, I may propose to change those names accordingly for the final JPS3; "m= edia-source" is widely implemented already but "printer-input-tray" and "pr= inter-output-tray" are not...) On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote: > Pete, Mike >=20=20 > In the PJT the MediaInputTray is (I believe) is called MediaSource; so, = at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? >=20=20 > Glen >=20=20 >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petri= e, Glen > Sent: Tuesday, January 24, 2012 2:34 PM > To: Michael Sweet; Zehler, Peter > Cc: ipp@pwg.org > Subject: RE: [IPP] media-input-tray-check-default >=20=20 > Should the value of =93Unknown=94 be used? Below is the statement from = rfc2911 >=20=20 > Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP > "out-of-band" value 'unknown'. See the description of the "out-of- > band" values at the beginning of Section 4.1. Therefore, attributes > of type 'enum' start at '3'. >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Tuesday, January 24, 2012 8:53 AM > To: Zehler, Peter > Cc: ipp@pwg.org > Subject: Re: [IPP] media-input-tray-check-default >=20=20 > OK, I'm convinced. I'll add "no-value" to this one and any others like i= t where it would not always make sense to force a default value. >=20=20 >=20=20 > On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: >=20=20 >=20 > Mike, > I prefer option #2. One of my reason is that it allows the operator to s= et policy for underspecified jobs on the printer. (If the client is not be= ing careful, then the printer will.) It is a very handy feature in product= ion printing. > Pete >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul = Tykodi > Sent: Tuesday, January 24, 2012 6:11 AM > To: ipp@pwg.org > Subject: RE: [IPP] media-input-tray-check-default >=20=20 > Hi Mike, >=20=20 > For production printing, I have found during my career that it is critica= l to have automatic checks and balances within the job submission workflow = so that a very large job (with a significant cost of production) is not rel= eased such that it will be printed on incorrect media and thus be a total l= oss (i.e. must be destroyed and cannot be distributed =96 job must be run a= gain). The AFP Consortium has the same type of intelligence in their Intell= igent Printer Data Stream specification as we have in IPP. >=20=20 > I think it is possible that some vendors may have interpreted the descrip= tion in the specification to mean that the default value should refer to th= e function being enabled or disabled. If it is enabled, it then interacts w= ith the media in the job ticket I therefore prefer option #2 to resolve thi= s issue. >=20=20 > Best Regards, >=20=20 > /Paul > -- > Paul Tykodi > Principal Consultant > TCS - Tykodi Consulting Services LLC >=20 > Tel/Fax: 603-343-1820 > Mobile: 603-866-0712 > E-mail: ptykodi@tykodi.com > WWW: http://www.tykodi.com > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Monday, January 23, 2012 6:14 PM > To: ipp@pwg.org > Subject: [IPP] media-input-tray-check-default >=20=20 > All, >=20=20 > I am going through yet another round of updates to the IANA registry (thi= s time for sure! :), and noticed that I still have the media-input-tray-che= ck-default attribute tagged as "under review". I would like to resolve this= before we submit our next round of updates to the registry. >=20=20 > BACKGROUND >=20=20 > PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check= Job Template attribute thusly: >=20=20 > The =93media-input-tray-check=94 Job Template attribute indicates that th= e Printer MUST check that the characteristics of the media in the identifie= d input tray are the same as characteristics of the media identified by the= Job's "media" Job Template attribute or matched (see section 3.13) by the = Job's "media- col" Job Template attribute. The keyword values are the same = input tray keyword values as are defined for the "media" Job Template attri= bute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'to= p', 'middle', 'bottom', etc. >=20=20 > Independent of the "ipp-attributes-fidelity" operation attribute supplied= by the client, if the characteristics differ, the Printer adds the =91reso= urces-are-not-ready=92 value (see section 6.1) to the job's "job-state-reas= ons" attribute and MAY either (1) put the job into the =91pending-held=92 s= tate or (2) start to process the job normally, but immediately stop the job= (=93job-state=94 =3D =91processing-stopped=92) and the Printer (=93printer= -state=94 =3D =91stopped=92). In either implementation, the operator can ch= ange the media in the input tray to agree with the job or can modify the jo= b=92s =93media=94 or =93media-col=94 attributes to agree with the input tra= y, depending on policy. >=20=20 > Table 1 (at the beginning of section 3) defines media-input-tray-check-de= fault and -supported. >=20=20 > The issue is that there should not be a default media-input-tray-check va= lue; like some other Job Template attributes (e.g. overrides), it does not = make sense to have a default value for this particular attribute since it i= nteracts with the media in the job ticket. >=20=20 > There are two ways to resolve this issue: >=20=20 > 1. Drop media-input-tray-check-default from the registry and post an erra= ta for 5100.3 removing the media-input-tray-check-default attribute from Ta= ble 1. >=20=20 > 2. Update the definition of media-input-tray-check-default to include the= "no-value" out-of-band value. >=20=20 > I prefer option #1. >=20=20 > Comments? >=20=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20=20 > __________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_XHSvRkWtr84MxCrF0177Yg) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Glen,

<= div>MediaInputTrayCheck and 5100.3's media-input-tray-check use the older P= rinter MIB naming convention, even though roll and slot names can be used.<= /div>

MediaSource comes from JPS3's media-source -= "source" as a more general word than "input tray" since it covers slots an= d rolls.  We had a lot of discussion about this early in the definitio= n of media-source for JPS3 and concluded that we should break the chain and= use the new name.  (oh, and realizing that we have printer-input-tray= and printer-output-tray mapped from the MIB, I may propose to change those= names accordingly for the final JPS3; "media-source" is widely implemented= already but "printer-input-tray" and "printer-output-tray" are not...)


On Jan 24, 2012, at 2:58 PM,= Petrie, Glen wrote:

Pete, Mike<= /p>

=  

<= p class=3D"MsoNormal">In the PJT the MediaInputTray is (I believe) is called MediaSource;  so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck??

<= p class=3D"MsoNormal"> 

<= p class=3D"MsoNormal">Glen

 

<= p class=3D"MsoNormal"> 

From: ipp-bounces@pwg.org [mailto:ipp-= bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Tuesday, January 24, 2= 012 2:34 PM
To: Michael Sweet; Zehler, P= eter
Cc: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Should the value of =93Unknown=94 be used?   Below is the statement from rfc2911=

 

<= p class=3D"MsoNormal">Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band" value 'unknown'.  See the description of the "out-of-

   band" values at the beginning of Section 4.1.  Therefore, attributes

   of type 'enum' start at '3'.

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf = Of Michael Sweet
Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one and any others like it where it would not always make sense to force a default valu= e.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=

 

Mik= e,

I p= refer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production prin= ting.

Pet= e

 

Peter Zehler

Xerox Research Center Webster
Email:&= nbsp;Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

From: = ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul= Tykodi
Sent: Tuesday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Hi = Mike,

 

For= production printing, I have found during my career that it is critical to have automat= ic checks and balances within the job submission workflow so that a very large= job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed= and cannot be distributed =96 job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP.

 

I t= hink it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function b= eing enabled or disabled. If it is enabled, it then interacts with the media in = the job ticket I therefore prefer option #2 to resolve this issue.= =

 

Bes= t Regards,

 

/Pa= ul

--

Paul Ty= kodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:=   603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  http://www.tykodi.com

From: = ipp-bounces@pwg.org [mai= lto:ipp-bounces@pwg.org] On Behalf Of Mich= ael Sweet
Sent: Monday, January 23, 2012 6:14 PM
To: ipp@pwg.org
Subject: [IPP] media-input-tray-check-default<= /o:p>

 

All,

 

I am going through = yet another round of updates to the IANA registry (this time for sure! :), and noticed that I st= ill have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry.

 

BACKGROUND

 

PWG 5100.3 (Product= ion Printing Set 1) defines the media-input-tray-check Job Template attribute thusly:

 

The =93media-input-= tray-check=94 Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the = same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for = the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.<= /o:p>

=  

Independent of the = "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the =91resources-are-not-ready=92 value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the =91pending-held=92 state or (2) start to process the job normally, but immediately stop the job (=93job-state=94 =3D =91processing-stopped=92) and the Printer (=93printer-state=94 =3D =91stopped=92). In either implementation, the operator can change the media in the input tray to agree with = ;the job or can modify the job=92s =93media=94 or =93media-col=94 attributes to agree with the input tray, depending on policy.

 

Table 1 (at the beg= inning of section 3) defines media-input-tray-check-default and -supported.

 

The issue is that t= here should not be a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket.

 

There are two ways = to resolve this issue:

 

1. Drop media-input= -tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.

 

2. Update the defin= ition of media-input-tray-check-default to include the "no-value" out-of-band value.

 

I prefer option #1.=

 

Comments?

 

___________________= _____________________________________________________

Michael Sweet, Seni= or Printing System Engineer, PWG Chair

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and i= s 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

 

___= _______________________________________________

Mic= hael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

<= font size=3D"3" face=3D"Times New Roman">
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________= ___
Michael Sweet, Senior Printing System Engineer, PWG Chai= r


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_XHSvRkWtr84MxCrF0177Yg)-- --===============2134958413== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2134958413==-- From ipp-bounces@pwg.org Wed Jan 25 06:00:04 2012 Return-Path: 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 746E021F86A8 for ; Wed, 25 Jan 2012 06:00:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.54 X-Spam-Level: X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jCHdImm17ZH for ; Wed, 25 Jan 2012 05:59:59 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2739621F86A7 for ; Wed, 25 Jan 2012 05:59:59 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1937C7963A; Wed, 25 Jan 2012 08:58:56 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 4B1F379686; Wed, 25 Jan 2012 08:58:36 -0500 (EST) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Jan 2012 05:58:36 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Wed, 25 Jan 2012 05:58:34 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: Acza89cuHRtDT5YJQ1u/vIlKcWs35wAdTmdQ References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 25 Jan 2012 13:58:36.0363 (UTC) FILETIME=[6EC931B0:01CCDB69] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0483217918==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 1937C7963A.AB1E4 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0483217918== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDB69.6E4F00A4" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDB69.6E4F00A4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike =20 I am ok with either name; but in PJT, if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck. =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Tuesday, January 24, 2012 3:57 PM To: Petrie, Glen Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 Glen, =20 MediaInputTrayCheck and 5100.3's media-input-tray-check use the older Printer MIB naming convention, even though roll and slot names can be used. =20 MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rolls. We had a lot of discussion about this early in the definition of media-source for JPS3 and concluded that we should break the chain and use the new name. (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemented already but "printer-input-tray" and "printer-output-tray" are not...) =20 =20 On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote: Pete, Mike =20 In the PJT the MediaInputTray is (I believe) is called MediaSource; so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Tuesday, January 24, 2012 2:34 PM To: Michael Sweet; Zehler, Peter Cc: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: =20 Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDB69.6E4F00A4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike

 

I am ok with either name; but in PJT= , if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck.

 

From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Tuesday, January 24, 2= 012 3:57 PM
To: Petrie, Glen
Cc: Zehler, Peter; ipp@pwg.o= rg; mfd@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

Glen,

 

MediaInputTrayCheck and 5100.3's media-input-tray-check use the old= er Printer MIB naming convention, even though roll and slot names can be used.=

 

MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rol= ls.  We had a lot of discussion about this early in the definition of medi= a-source for JPS3 and concluded that we should break the chain and use the new name.  (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemen= ted already but "printer-input-tray" and "printer-output-tray&qu= ot; are not...)

 

 

On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote:<= /font>



Pete, Mike

 

In the PJT the MediaInputTray is (I believe) is called MediaSource;  so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck??

 

Glen=

 

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf = Of Petrie, Glen
Sent: Tuesday, January 24, 2= 012 2:34 PM
To: Michael Sweet; Zehler, P= eter
Cc: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Should the value of “Unknown&#= 8221; be used?   Below is the statement from rfc2911

 

Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band" value 'unknown'.  See the description of the "out-of-

   band" values at the beginning of Section 4.1.  Therefore, attributes

   of type 'enum' start at= '3'.

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf = Of Michael Sweet
Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one = and any others like it where it would not always make sense to force a default value.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=

 

Mike,

I prefer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production prin= ting.

Pete

 

Peter Zehler

Xerox Research Center Webster
Email:&nb= sp;Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Philli= ps Rd.<= font size=3D2 color=3D"#1f497d" face=3DCalibri>
M/S 128-25E
Webster NY, 14580-9701

 

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul T= ykodi
Sent: Tuesday, January 24, 2012 6:11 A= M
To: <= font color=3Dpurple>ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default

=  

Hi Mike,=

 

For production= printing, I have found during my career that it is critical to have automatic checks = and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printe= d on incorrect media and thus be a total loss (i.e. must be destroyed and cannot= be distributed – job must be run again). The AFP Consortium has the same= type of intelligence in their Intelligent Printer Data Stream specification as we h= ave in IPP.

 

I think it is = possible that some vendors may have interpreted the description in the specification= to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job tic= ket I therefore prefer option #2 to resolve this issue.

 

Best Regards,<= u4:p>

 

/Paul

--=

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com
WWW:  = http://www.tykodi.com

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 PM=
To: <= font color=3Dpurple>ipp@pwg.org Subject: [IPP] media-input-tray-check-def= ault

=  

= All,=

=  

= I am going through yet another round= of updates to the IANA registry (this time for sure! :), and noticed that I still have= the media-input-tray-check-default attribute tagged as "under review"= . I would like to resolve this before we submit our next round of updates to the registry.

=  

= BACKGROUND

=  

= PWG 5100.3 (Production Printing Set = 1) defines the media-input-tray-check Job Template attribute thusly:

=  

= The “media-input-tray-check= 221; Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the = same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see sect= ion 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.

=  

= Independent of the "ipp-attributes-fidelity" operation attribute supplied by the cli= ent, if the characteristics differ, the Printer adds the ‘resources-are-not-ready’ value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the ‘pending-held’ state or (2) start to process the = job normally, but immediately stop the job (“job-state” =3D ‘processing= -stopped’) and the Printer (“printer-state” =3D ‘stopped’). In ei= ther implementation, the operator can change the media in the input tray to agree with the= job or can modify the job’s “media” or “media-col&= #8221; attributes to agree with the input tray, depending on policy.

=  

= Table 1 (at the beginning of section= 3) defines media-input-tray-check-default and -supported.<= /font>

=  

= The issue is that there should not b= e a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particu= lar attribute since it interacts with the media in the job ticket.=

=  

= There are two ways to resolve this i= ssue:

=  

= 1. Drop media-input-tray-check-defau= lt from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.<= /font>

=  

= 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-b= and value.

=  

= I prefer option #1.

=  

= Comments?=

=  

= ____________________________________= ____________________________________<= /p>

= Michael Sweet, Senior Printing System Engineer, PWG Chair

=  

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
<= span style=3D'color:purple'>https://www.pwg.org/mailman/listinfo/ipp

 

______________= ____________________________________<= /p>

Michael Sweet, Senior Printing System Engineer, PWG Chair<= o:p>

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

 

__________________________________________________

Michael Sweet, Senior Printing System Engineer,= PWG Chair

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDB69.6E4F00A4-- --===============0483217918== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0483217918==-- From ipp-bounces@pwg.org Wed Jan 25 06:58:43 2012 Return-Path: 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 BA96821F86C3 for ; Wed, 25 Jan 2012 06:58:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.3 X-Spam-Level: X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.297, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uv1iihCgUR0G for ; Wed, 25 Jan 2012 06:58:38 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9716821F86B4 for ; Wed, 25 Jan 2012 06:58:37 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1809C7967D; Wed, 25 Jan 2012 09:57:36 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 841977967A; Wed, 25 Jan 2012 09:57:12 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AswDALsWIE8Nh9IPdWdsb2JhbABAA4JNq3EiAQoMDBslDwGBYgEBAQQBAQEMAQwRAyUKBgkLEAIBCAcKBAEBCwYMBAEGAQYBJh8JCAEBBAESCId8pWgBkkiJKwIBJoJrLQ8BAg0EDQoEBAQFDhwKCII+YwSIP4UHmko Received: from usa0300gw002.na.xerox.net ([13.135.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 25 Jan 2012 08:57:09 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 Jan 2012 09:57:05 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Wed, 25 Jan 2012 06:57:08 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: Acza89cuHRtDT5YJQ1u/vIlKcWs35wAdTmdQAAEg7ZA= References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Zehler, Peter" To: "Petrie, Glen" , "Michael Sweet" X-OriginalArrivalTime: 25 Jan 2012 14:57:05.0175 (UTC) FILETIME=[9A336A70:01CCDB71] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1657162019==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 1809C7967D.A9648 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1657162019== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDB71.9957998A" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDB71.9957998A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Glen, I want a cleaner mapping to IPP whenever possible. I'd prefer MediaInputTrayCheck with a clarifying clauses in the descriptions of MediaSource and MediaInputTrayCheck.=20=20 Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Wednesday, January 25, 2012 8:59 AM To: Michael Sweet Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Mike =20 I am ok with either name; but in PJT, if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck. =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Tuesday, January 24, 2012 3:57 PM To: Petrie, Glen Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 Glen, =20 MediaInputTrayCheck and 5100.3's media-input-tray-check use the older Printer MIB naming convention, even though roll and slot names can be used. =20 MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rolls. We had a lot of discussion about this early in the definition of media-source for JPS3 and concluded that we should break the chain and use the new name. (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemented already but "printer-input-tray" and "printer-output-tray" are not...) =20 =20 On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote: =20 Pete, Mike =20 In the PJT the MediaInputTray is (I believe) is called MediaSource; so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Tuesday, January 24, 2012 2:34 PM To: Michael Sweet; Zehler, Peter Cc: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: =20 Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDB71.9957998A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Glen,<= /o:p>

I want a cleaner mapping to IPP= whenever possible.  I’d prefer MediaInputTrayCheck with a clari= fying clauses in the descriptions of MediaSource and MediaInputTrayCheck.&n= bsp;

Pete

 

 

Pet= er Zehler

Xerox Research Center Webster
<= /span>Email: Peter.Zehler@Xerox= .com
Voice: (585) 265-8755
= FAX: (585) 265-7441
US Mail: Peter Zehle= r
Xerox Corp.
800 Phill= ips Rd.
M/S 128-25E
Web= ster NY, 14580-9701

 

From: Petrie, Glen [mailto:glen.petri= e@eitc.epson.com]
Sent: Wednesday, January 25, 2012 8:59 AM
<= b>To: Michael Sweet
Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.o= rg
Subject: RE: [IPP] media-input-tray-check-default

 

Mike=

 

I am ok with either name= ; but in PJT, if the convention is to use MediaSource; then I believe we sh= ould use MediaSourceCheck and not MediaInputTrayCheck.

 

From: Michael Sweet [mailto:msweet@apple.com]
Sent: Tuesday, January = 24, 2012 3:57 PM
To: Petrie, Glen
Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org
Subject: Re: [IPP] media-input-tray-check-defau= lt

 

Glen,

 =

MediaInputTrayCheck and 5100= .3's media-input-tray-check use the older Printer MIB naming convention, ev= en though roll and slot names can be used.

<= p class=3DMsoNormal> 

Me= diaSource comes from JPS3's media-source - "source" as a more gen= eral word than "input tray" since it covers slots and rolls. &nbs= p;We had a lot of discussion about this early in the definition of media-so= urce for JPS3 and concluded that we should break the chain and use the new = name.  (oh, and realizing that we have printer-input-tray and printer-= output-tray mapped from the MIB, I may propose to change those names accord= ingly for the final JPS3; "media-source" is widely implemented al= ready but "printer-input-tray" and "printer-output-tray"= ; are not...)

 

 

=

On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote:<= o:p>

 

Pete, Mike

 <= o:p>

In the PJT the MediaInputTray is (I believe) is called Med= iaSource;  so, at least in the PJT, should MediaInputTrayCheck become = MediaSourceCheck??

 

G= len

 

 

Fr= om: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org]= On Behalf Of Petrie, Glen
Sent: Tuesday, January 24, 2012= 2:34 PM
To: Michael Sweet; Zehler, Peter
Cc: ipp@pwg.org
Subject: RE: [IPP] media-= input-tray-check-default

&n= bsp;

Should the value of “Unknown” be used?&nb= sp;  Below is the statement from rfc2911

 = ;

Note: SNMP MIBs use '2' for 'unknown' which corre= sponds to the IPP

   "out-of-band&qu= ot; value 'unknown'.  See the description of the "out-of-<= o:p>

   band" values at the beginning of Section= 4.1.  Therefore, attributes

   of t= ype 'enum' start at '3'.

 

From:= ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Beh= alf Of Michael Sweet
Sent: Tuesday, January 24, 2012 8:53 AM<= br>To: Zehler, Peter
Cc: ip= p@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to thi= s one and any others like it where it would not always make sense to force = a default value.

 <= /p>

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:

 

<= div>

Mike,

=

I prefer option #2.  One of my reason is t= hat it allows the operator to set policy for underspecified jobs on the pri= nter.  (If the client is not being careful, then the printer will.)&nb= sp; It is a very handy feature in production printing.

Pete

 

<= p class=3DMsoNormal>Peter Zehler

Xerox<= span style=3D'color:navy'> Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xer= ox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701=

 

From: ipp-bounces@pwg.org<= /a> [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi
Sent: Tuesday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-ch= eck-default

 

Hi Mike,

 

For production printing, I have found during my career that it is c= ritical to have automatic checks and balances within the job submission wor= kflow so that a very large job (with a significant cost of production) is n= ot released such that it will be printed on incorrect media and thus be a t= otal loss (i.e. must be destroyed and cannot be distributed – job mus= t be run again). The AFP Consortium has the same type of intelligence in th= eir Intelligent Printer Data Stream specification as we have in IPP.=

 

I think it is possible that s= ome vendors may have interpreted the description in the specification to me= an that the default value should refer to the function being enabled or dis= abled. If it is enabled, it then interacts with the media in the job ticket= I therefore prefer option #2 to resolve this issue.

<= /div>

 

Best Regards,

 

/Paul

--

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Servi= ces LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com
WWW: = ; http://www.tykodi.com

<= /div>

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.or= g] On Behalf = Of Michael Sweet
= Sent: Monday, January 2= 3, 2012 6:14 PM
To: ipp@pwg.org<= /span>
Subject: [IPP] media-input-tray-check-default

 

All,=

 

I am going through yet another round of= updates to the IANA registry (this time for sure! :), and noticed that I s= till have the media-input-tray-check-default attribute tagged as "unde= r review". I would like to resolve this before we submit our next roun= d of updates to the registry.

 

=

BACK= GROUND

 

<= p class=3DMsoNormal>PWG 5100.3 (Production Prin= ting Set 1) defines the media-input-tray-check Job Template attribute thusl= y:

 

The “= media-input-tray-check” Job Template attribute indicates that the Pri= nter MUST check that the characteristics of the media in the iden= tified input tray are the same as characteristics of the media id= entified by the Job's "media" Job Template attribute or matc= hed (see section 3.13) by the Job's "media- col" J= ob Template attribute. The keyword values are the same input tray keyw= ord values as are defined for the "media" Job Template attri= bute (see section 6.3 in this document and [RFC2911] Appendix C), i.e.= , 'top', 'middle', 'bottom', etc.

 <= /o:p>

Independent of the "ipp-attributes-fidelity" operation attri= bute supplied by the client, if the characteristics differ, the P= rinter adds the ‘resources-are-not-ready’ value (see section 6.= 1) to the job's "job-state-reasons" attribute and MAY either= (1) put the job into the ‘pending-held’ state or (2) star= t to process the job normally, but immediately stop the job (“jo= b-state” =3D ‘processing-stopped’) and the Printer (̶= 0;printer-state” =3D ‘stopped’). In either implement= ation, the operator can change the media in the input tray to agree wi= th the job or can modify the job’s “media” or &= #8220;media-col” attributes to agree with the input tray, depending o= n policy.

 

Table = 1 (at the beginning of section 3) defines media-input-tray-check-default an= d -supported.

 

The issue is that th= ere should not be a default media-input-tray-check value; like some other J= ob Template attributes (e.g. overrides), it does not make sense to have a d= efault value for this particular attribute since it interacts with the medi= a in the job ticket.

 

There are two= ways to resolve this issue:

 

<= /div>

1. Dr= op media-input-tray-check-default from the registry and post an errata for = 5100.3 removing the media-input-tray-check-default attribute from Table 1.<= /span>

 

2. Update the definition of media-= input-tray-check-default to include the "no-value" out-of-band va= lue.

 

I prefer option #1.

 

Comments?

=

 

____________________________________= ____________________________________

=

Mich= ael Sweet, Senior Printing System Engineer, PWG Chair

=

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean.


-- 
This message ha= s been scanned for viruses and 
dangerous content by = MailScanner, and is = ;
believed to be clean.


-- 
This message = has been scanned for viruses and <= /span>
dangerous content by MailScanner, and is&nb= sp;
believed to be clean. _______________________________________= ________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mail= man/listinfo/ipp

 

_________= _________________________________________

<= p class=3DMsoNormal>Michael Sweet, Senior Printing System Engin= eer, PWG Chair

 =


--
This message has= been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clea= n.


--
This message has been sca= nned for viruses and
dangerous content by MailScanner, and is
believed to be clean. <= /o:p>

 

___= _______________________________________________

=

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDB71.9957998A-- --===============1657162019== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1657162019==-- From ipp-bounces@pwg.org Wed Jan 25 07:13:48 2012 Return-Path: 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 DED7721F864F for ; Wed, 25 Jan 2012 07:13:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.54 X-Spam-Level: X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vzdCMUY2wrbH for ; Wed, 25 Jan 2012 07:13:40 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3A70021F85CC for ; Wed, 25 Jan 2012 07:13:40 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 756D77967D; Wed, 25 Jan 2012 10:12:37 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 7D4187967D; Wed, 25 Jan 2012 10:12:15 -0500 (EST) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 25 Jan 2012 07:12:14 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Wed, 25 Jan 2012 07:12:12 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: Acza89cuHRtDT5YJQ1u/vIlKcWs35wAdTmdQAAEg7ZAAAU8rkA== References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Petrie, Glen" To: "Zehler, Peter" , "Michael Sweet" X-OriginalArrivalTime: 25 Jan 2012 15:12:14.0962 (UTC) FILETIME=[B879E520:01CCDB73] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0683828825==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 756D77967D.AA168 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0683828825== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDB73.B7FCDA64" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDB73.B7FCDA64 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Pete =20 Ok, but .... people who will start using PJT and not real background with or using IPP may find it confusing. i.e. "Is it source?" "Is it tray?" "Is it input tray?" "Are they the same thing?". Does a client display a label called "Media Source" or "Input Tray" or "Media Tray" or "Media Input Tray". One more push to use MediaSourceCheck and have a note stating that new specifications have changed from Input Tray to Media Source. =20 [If we change (input) tray to source; does output bin have a new name?] =20 Glen =20 =20 ________________________________ From: Zehler, Peter [mailto:Peter.Zehler@xerox.com]=20 Sent: Wednesday, January 25, 2012 6:57 AM To: Petrie, Glen; Michael Sweet Cc: ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Glen, I want a cleaner mapping to IPP whenever possible. I'd prefer MediaInputTrayCheck with a clarifying clauses in the descriptions of MediaSource and MediaInputTrayCheck.=20=20 Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Wednesday, January 25, 2012 8:59 AM To: Michael Sweet Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Mike =20 I am ok with either name; but in PJT, if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck. =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com] =20=20 Sent: Tuesday, January 24, 2012 3:57 PM To: Petrie, Glen Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 Glen, =20 MediaInputTrayCheck and 5100.3's media-input-tray-check use the older Printer MIB naming convention, even though roll and slot names can be used. =20 MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rolls. We had a lot of discussion about this early in the definition of media-source for JPS3 and concluded that we should break the chain and use the new name. (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemented already but "printer-input-tray" and "printer-output-tray" are not...) =20 =20 On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote: =20 Pete, Mike =20 In the PJT the MediaInputTray is (I believe) is called MediaSource; so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Tuesday, January 24, 2012 2:34 PM To: Michael Sweet; Zehler, Peter Cc: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: =20 Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDB73.B7FCDA64 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Pete

 

Ok, but ….  people who wi= ll start using PJT and not real background with or using IPP may find it confusing.&= nbsp; i.e. “Is it source?”  “Is it tray?”  “Is= it input tray?” “Are they the same thing?”.   Does a client display a= label called “Media Source” or “Input Tray” or “Media Tray” or &#= 8220;Media Input Tray”.   One more push to use MediaSourceCheck and ha= ve a note stating that new specifications have changed from Input Tray to Media Source.<= /o:p>

 

[If we change (input) tray to source= ; does output bin have a new name?]

 

Glen

 

 

From: Zehler, = Peter [mailto:Peter.Zehler@xerox.com]
Sent: Wednesday, January 25,= 2012 6:57 AM
To: Petrie, Glen; Michael Sw= eet
Cc: ipp@pwg.org; mfd@pwg.org=
Subject: RE: [IPP] media-input-tray-check-default

 

Glen,

I want a clean= er mapping to IPP whenever possible.  I’d prefer MediaInputTrayCheck with a clarifying clauses in the descriptions of MediaSource and MediaInputTrayCheck. 

Pete

 

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

From: Petrie, = Glen [mailto:glen.petrie@eitc.epson.com]
Sent: Wednesday, January 25,= 2012 8:59 AM
To: Michael Sweet
Cc: Zehler, Peter; ipp@pwg.o= rg; mfd@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Mike

 

I am ok with either name; but in PJT= , if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck.

 

From: Michael = Sweet [mailto:msweet@apple.com]=
Sent: Tuesday, January 24, 2= 012 3:57 PM
To: Petrie, Glen
Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

Glen,

 

MediaInputTrayCheck and 5100.3's media-input-tray-check use the old= er Printer MIB naming convention, even though roll and slot names can be used.=

 

MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rol= ls.  We had a lot of discussion about this early in the definition of media-source for JPS3 and concluded that we should break the chain and use = the new name.  (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemen= ted already but "printer-input-tray" and "printer-output-tray&qu= ot; are not...)

 

 

On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote:<= /font>

 =

Pete, Mike<= /p>

 

In the PJT the MediaInputTray is (I believe) is called MediaSource;  so, at least in the PJT, should Media= InputTrayCheck become MediaSourceCheck??

 

Glen

 

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.or= g] On Behalf Of Petrie, Glen
Sent: Tuesday, January 24, 2= 012 2:34 PM
To: Michael Sweet; Zehler, P= eter
Cc: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Should the value of “Unknown” be used?   Below is the statement from rfc2= 911

 

Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP

   "out-of-band" value 'unknown'.  See the description of the "out-of-

   band" values at the beginning of Section 4.1.  Therefore, attributes

   of type 'enum' start at '3'.

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.or= g] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2= 012 8:53 AM
To: Zehler, Peter
Cc: ipp@pwg.org
Subject: Re: [IPP] media-input-tray-check-default

 

OK, I'm convinced.  I'll add "no-value" to this one = and any others like it where it would not always make sense to force a default value.

 

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:=

 =

Mike,

I prefer option #2.  One of my reason is that it allows the operator to set policy for underspecified jobs on the printer.  (If the client is not being caref= ul, then the printer will.)  It is a very handy feature in production printing.

Pete

 <= /font>

Peter Zehler

Xerox Research Center= Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 <= /font>

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.or= g] On Behalf Of Paul T= ykodi
Sent: Tuesday, January 24, 2012 6:11 A= M
To: <= font color=3Dpurple>ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default

=  

Hi Mike,

 <= /font>

For production printing, I have found during my career that it is critical to have automat= ic checks and balances within the job submission workflow so that a very large= job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed= and cannot be distributed – job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP.

 <= /font>

I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function b= eing enabled or disabled. If it is enabled, it then interacts with the media in = the job ticket I therefore prefer option #2 to resolve this issue.

 <= /font>

Best Regards,<= /span>

 <= /font>

/Paul

--=

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com<= font size=3D7 color=3D"#1f497d" face=3D"Courier New">
WWW:  = http://www.tykodi.com

= From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 PM=
To: <= font color=3Dpurple>ipp@pwg.org Subject: [IPP] media-input-tray-check-def= ault

=  

= All,

=  

= I am going through yet another round= of updates to the IANA registry (this time for sure! :), and noticed that I st= ill have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round = of updates to the registry.

=  

= BACKGROUND<= /p>

=  

= PWG 5100.3 (Production Printing Set = 1) defines the media-input-tray-check Job Template attribute thusly:

=  

= The “media-input-tray-check= 221; Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the = same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see sect= ion 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc.

=  

= Independent of the "ipp-attributes-fidelity" operation attribute supplied by the cli= ent, if the characteristics differ, the Printer adds the ‘resources-are-not-ready’ value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the ‘pending-held’ state or (2) start to process the = job normally, but immediately stop the job (“job-state” =3D ‘processing-stopped’) and the Printer (“printer-state” =3D ‘stopped’). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job’s “media” or “media-col” attributes to agree with the input tray, depending on policy.

=  

= Table 1 (at the beginning of section= 3) defines media-input-tray-check-default and -supported.

=  

= The issue is that there should not b= e a default media-input-tray-check value; like some other Job Template attribut= es (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket.

=  

= There are two ways to resolve this i= ssue:

=  

= 1. Drop media-input-tray-check-defau= lt from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1.

=  

= 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-b= and value.

=  

= I prefer option #1.

=  

= Comments?

=  

= ____________________________________= ____________________________________

= Michael Sweet, Senior Printing System Engineer, PWG Chair

=  

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.

=
-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean.


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
<= span style=3D'color:purple'>https://www.pwg.org/mailman/listinfo/ipp

 

______________= ____________________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

 

__________________________________________________

Michael Sweet, Senior Printing System Engineer,= PWG Chair

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDB73.B7FCDA64-- --===============0683828825== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0683828825==-- From ipp-bounces@pwg.org Wed Jan 25 08:14:35 2012 Return-Path: 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 ACC5B21F85F1 for ; Wed, 25 Jan 2012 08:14:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.327 X-Spam-Level: X-Spam-Status: No, score=-2.327 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sv18csBQGMNA for ; Wed, 25 Jan 2012 08:14:28 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7033421F85EE for ; Wed, 25 Jan 2012 08:14:28 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 453497969B; Wed, 25 Jan 2012 11:13:21 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 406BF79679; Wed, 25 Jan 2012 11:12:59 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmkBAOMpIE8Nl9IPmWdsb2JhbABAA4JNq3MiAQEBAQEICwsbJQ8BgWIBAQEEAQEBDAEKAhEDJQoGCQQHEAIBCAcKBAEBCwYMBAEGAQYBJh8JCAEBBAESCId8pVoBkkSJKwIBJoJrLQ8BAg0EDQoEBAQFDhwKCII+YwSIP4UHmko Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 25 Jan 2012 10:12:46 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 Jan 2012 08:12:46 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] media-input-tray-check-default Date: Wed, 25 Jan 2012 08:12:50 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] media-input-tray-check-default Thread-Index: Acza89cuHRtDT5YJQ1u/vIlKcWs35wAdTmdQAAEg7ZAAAU8rkAAAU2CA References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> From: "Zehler, Peter" To: "Petrie, Glen" , "Michael Sweet" X-OriginalArrivalTime: 25 Jan 2012 16:12:46.0175 (UTC) FILETIME=[2CD906F0:01CCDB7C] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0528322701==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 453497969B.A91B5 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0528322701== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCDB7C.2C958418" This is a multi-part message in MIME format. ------_=_NextPart_001_01CCDB7C.2C958418 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Glen, =20 I really hate arguments over names of attributes/elements. We are talking about tags in a protocol. We could change the attribute name "media-input-tray-check" and the element name "MediaInputTrayCheck" to "Appletree" and it would not change its semantics. An application, used by people, can use any nomenclature deemed acceptable for the environment. A picture of a tray works just as well as any of the terms you suggested below. The objective of the model is not standardization of user interfaces across the industry. The goal is standardization definitions of the semantics. If the semantics contain a links between "MediaSource", "MediaInputTrayCheck" and "InputTray" then the Semantic Model should clarify the relationship. I would expect JPS3 to do the same. =20 Note that the IPP and Semantic Model have mappings to the Printer MIB's prtInputTable(1.3.6.1.2.1.43.8.2) and prtOutputTable (1.3.6.1.2.1.43.9.2) subunits. The Semantic Model represents the complete subunits while IPP chose a subset of objects of interest. The Semantic Model choose the tags "InputTrays" and "OutputTrays" to map to the MIB objects and documented those mappings in PWG5108.1. There is no direct mapping from IPP's representation of these MIB objects since the Semantic Model maps its subunit elements (i.e., "Configuration" elements) to the standard object definitions (i.e., RFC3805). =20 If you are seeking a standard name to put in a UI, perhaps a standard message catalogue may be the answer. It could also have standard names in multiple languages. =20 Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Wednesday, January 25, 2012 10:12 AM To: Zehler, Peter; Michael Sweet Cc: ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Pete =20 Ok, but .... people who will start using PJT and not real background with or using IPP may find it confusing. i.e. "Is it source?" "Is it tray?" "Is it input tray?" "Are they the same thing?". Does a client display a label called "Media Source" or "Input Tray" or "Media Tray" or "Media Input Tray". One more push to use MediaSourceCheck and have a note stating that new specifications have changed from Input Tray to Media Source. =20 [If we change (input) tray to source; does output bin have a new name?] =20 Glen =20 =20 ________________________________ From: Zehler, Peter [mailto:Peter.Zehler@xerox.com]=20 Sent: Wednesday, January 25, 2012 6:57 AM To: Petrie, Glen; Michael Sweet Cc: ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Glen, I want a cleaner mapping to IPP whenever possible. I'd prefer MediaInputTrayCheck with a clarifying clauses in the descriptions of MediaSource and MediaInputTrayCheck.=20=20 Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Wednesday, January 25, 2012 8:59 AM To: Michael Sweet Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Mike =20 I am ok with either name; but in PJT, if the convention is to use MediaSource; then I believe we should use MediaSourceCheck and not MediaInputTrayCheck. =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com] =20=20 Sent: Tuesday, January 24, 2012 3:57 PM To: Petrie, Glen Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 Glen, =20 MediaInputTrayCheck and 5100.3's media-input-tray-check use the older Printer MIB naming convention, even though roll and slot names can be used. =20 MediaSource comes from JPS3's media-source - "source" as a more general word than "input tray" since it covers slots and rolls. We had a lot of discussion about this early in the definition of media-source for JPS3 and concluded that we should break the chain and use the new name. (oh, and realizing that we have printer-input-tray and printer-output-tray mapped from the MIB, I may propose to change those names accordingly for the final JPS3; "media-source" is widely implemented already but "printer-input-tray" and "printer-output-tray" are not...) =20 =20 On Jan 24, 2012, at 2:58 PM, Petrie, Glen wrote: =20 Pete, Mike =20 In the PJT the MediaInputTray is (I believe) is called MediaSource; so, at least in the PJT, should MediaInputTrayCheck become MediaSourceCheck?? =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Tuesday, January 24, 2012 2:34 PM To: Michael Sweet; Zehler, Peter Cc: ipp@pwg.org Subject: RE: [IPP] media-input-tray-check-default =20 Should the value of "Unknown" be used? Below is the statement from rfc2911 =20 Note: SNMP MIBs use '2' for 'unknown' which corresponds to the IPP "out-of-band" value 'unknown'. See the description of the "out-of- band" values at the beginning of Section 4.1. Therefore, attributes of type 'enum' start at '3'. =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Tuesday, January 24, 2012 8:53 AM To: Zehler, Peter Cc: ipp@pwg.org Subject: Re: [IPP] media-input-tray-check-default =20 OK, I'm convinced. I'll add "no-value" to this one and any others like it where it would not always make sense to force a default value. =20 =20 On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote: =20 Mike, I prefer option #2. One of my reason is that it allows the operator to set policy for underspecified jobs on the printer. (If the client is not being careful, then the printer will.) It is a very handy feature in production printing. Pete =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Paul Tykodi Sent: Tuesday, January 24, 2012 6:11 AM To: ipp@pwg.org =20 Subject: RE: [IPP] media-input-tray-check-default =20 Hi Mike, =20 For production printing, I have found during my career that it is critical to have automatic checks and balances within the job submission workflow so that a very large job (with a significant cost of production) is not released such that it will be printed on incorrect media and thus be a total loss (i.e. must be destroyed and cannot be distributed - job must be run again). The AFP Consortium has the same type of intelligence in their Intelligent Printer Data Stream specification as we have in IPP. =20 I think it is possible that some vendors may have interpreted the description in the specification to mean that the default value should refer to the function being enabled or disabled. If it is enabled, it then interacts with the media in the job ticket I therefore prefer option #2 to resolve this issue. =20 Best Regards, =20 /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com =20 WWW: http://www.tykodi.com =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, January 23, 2012 6:14 PM To: ipp@pwg.org =20 Subject: [IPP] media-input-tray-check-default =20 All, =20 I am going through yet another round of updates to the IANA registry (this time for sure! :), and noticed that I still have the media-input-tray-check-default attribute tagged as "under review". I would like to resolve this before we submit our next round of updates to the registry. =20 BACKGROUND =20 PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check Job Template attribute thusly: =20 The "media-input-tray-check" Job Template attribute indicates that the Printer MUST check that the characteristics of the media in the identified input tray are the same as characteristics of the media identified by the Job's "media" Job Template attribute or matched (see section 3.13) by the Job's "media- col" Job Template attribute. The keyword values are the same input tray keyword values as are defined for the "media" Job Template attribute (see section 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'middle', 'bottom', etc. =09=20 Independent of the "ipp-attributes-fidelity" operation attribute supplied by the client, if the characteristics differ, the Printer adds the 'resources-are-not-ready' value (see section 6.1) to the job's "job-state-reasons" attribute and MAY either (1) put the job into the 'pending-held' state or (2) start to process the job normally, but immediately stop the job ("job-state" =3D 'processing-stopped') and the Printer ("printer-state" =3D 'stopped'). In either implementation, the operator can change the media in the input tray to agree with the job or can modify the job's "media" or "media-col" attributes to agree with the input tray, depending on policy. =20 Table 1 (at the beginning of section 3) defines media-input-tray-check-default and -supported. =20 The issue is that there should not be a default media-input-tray-check value; like some other Job Template attributes (e.g. overrides), it does not make sense to have a default value for this particular attribute since it interacts with the media in the job ticket. =20 There are two ways to resolve this issue: =20 1. Drop media-input-tray-check-default from the registry and post an errata for 5100.3 removing the media-input-tray-check-default attribute from Table 1. =20 2. Update the definition of media-input-tray-check-default to include the "no-value" out-of-band value. =20 I prefer option #1. =20 Comments? =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CCDB7C.2C958418 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Glen,<= /o:p>

 

I really hate arguments over names of attributes/e= lements.  We are talking about tags in a protocol.  We could chan= ge the attribute name “media-input-tray-check” and the element = name ”MediaInputTrayCheck” to “Appletree” and it wo= uld not change its semantics.  An application, used by people,  c= an use any nomenclature deemed acceptable for the environment.  A pict= ure of a tray works just as well as any of the terms you suggested below.&n= bsp; The objective of the model is not standardization of user interfaces a= cross the industry.  The goal is standardization definitions of the se= mantics.  If the semantics contain a links between “MediaSource&= #8221;, “MediaInputTrayCheck” and  “InputTray”= then the Semantic Model should clarify the relationship.  I would exp= ect JPS3 to do the same.

<= o:p> 

Note that the IPP an= d Semantic Model have mappings to the Printer MIB’s prtInputTable(1.3= .6.1.2.1.43.8.2) and prtOutputTable (1.3.6.1.2.1.43.9.2) subunits.  Th= e Semantic Model represents the complete subunits while IPP chose a subset = of objects of interest.  The Semantic Model choose the tags “Inp= utTrays” and “OutputTrays” to map to the MIB objects and = documented those mappings in PWG5108.1.  There is no direct mapping fr= om IPP’s representation of these MIB objects since the Semantic Model= maps its subunit elements (i.e., “Configuration” elements) to = the standard object definitions (i.e., RFC3805).

 

If you are seeking a standard name to put in a UI, perhaps a standard m= essage catalogue may be the answer.  It could also have standard names= in multiple languages.

 

Pete

 

 

Pet= er Zehler

Xerox Research Center Webster
<= /span>Email: Peter.Zehler@Xerox= .com
Voice: (585) 265-8755
= FAX: (585) 265-7441
US Mail: Peter Zehle= r
Xerox Corp.
800 Phill= ips Rd.
M/S 128-25E
Web= ster NY, 14580-9701

 

From: Petrie, Glen [mailto:glen.petri= e@eitc.epson.com]
Sent: Wednesday, January 25, 2012 10:12 AM
= To: Zehler, Peter; Michael Sweet
Cc: ipp@pwg.org; mfd@pwg.= org
Subject: RE: [IPP] media-input-tray-check-default<= /span>

 

Pete

 

Ok, but ….  = people who will start using PJT and not real background with or using IPP m= ay find it confusing.  i.e. “Is it source?”  “I= s it tray?”  “Is it input tray?” “Are they the= same thing?”.   Does a client display a label called ̶= 0;Media Source” or “Input Tray” or “Media Tray̶= 1; or “Media Input Tray”.   One more push to use Medi= aSourceCheck and have a note stating that new specifications have changed f= rom Input Tray to Media Source.

<= span style=3D'font-family:"Cambria","serif";color:blue'> 

[If we change (input) tray to source; does output bin have a ne= w name?]

 

Glen

 

 

From:= Zeh= ler, Peter [mailto:Peter= .Zehler@xerox.com]
Sent: Wednesday, January 25, 2012 6:57 AM=
To: Petrie, Glen; Michael Sweet
Cc: ipp@pwg.org; mfd@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Glen,

I want a cl= eaner mapping to IPP whenever possible.  I’d prefer MediaInputTr= ayCheck with a clarifying clauses in the descriptions of MediaSource and Me= diaInputTrayCheck. 

= Pete

 

 

Peter Zehler

Xerox Research= Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-875= 5
FAX: (585) 265-7441
U= S Mail: Peter Zehler
Xerox Corp.800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 

From: Petrie, Gl= en [mailto:glen.petr= ie@eitc.epson.com]
Sent: Wednesday, January 25, 2012 8:59 AM=
To: Michael Sweet
Cc: Zehler, Peter; ipp@pwg.org; mfd@pwg.org
Subject: RE: [IPP] media-input-tray-check-default

 

Mike=

 

I am ok with either name= ; but in PJT, if the convention is to use MediaSource; then I believe we sh= ould use MediaSourceCheck and not MediaInputTrayCheck.

 

From: Michael Sweet [mailto:msweet@apple.com]
Sent: Tuesday, Janu= ary 24, 2012 3:57 PM
To: Petrie, Glen
Cc: Zehler, Peter= ; ipp@pwg.org; mfd@pwg.org
Subject: Re: [IPP] media-input-tray-check-d= efault

 

Glen,

&n= bsp;

MediaInputTrayCheck and = 5100.3's media-input-tray-check use the older Printer MIB naming convention= , even though roll and slot names can be used.

 

MediaSource comes from JPS3's media-source - "source" as a more= general word than "input tray" since it covers slots and rolls. =  We had a lot of discussion about this early in the definition of medi= a-source for JPS3 and concluded that we should break the chain and use the = new name.  (oh, and realizing that we have printer-input-tray and prin= ter-output-tray mapped from the MIB, I may propose to change those names ac= cordingly for the final JPS3; "media-source" is widely implemente= d already but "printer-input-tray" and "printer-output-tray&= quot; are not...)

 =

 

<= div>

On Jan 24, 2012, at 2:58 PM, Petrie, Glen wro= te:

 

Pete, Mike

 

In the PJT the MediaInputTray is (I believe) is called= MediaSource;  so, at least in the PJT, should MediaInputTrayCheck bec= ome MediaSourceCheck??

 

=

Glen

 

 

From: ipp-bounces@pwg.org <= a href=3D"mailto:%5bmailto:ipp-bounces@pwg.org%5d">[mailto:ipp-bounces@pwg.= org] On Behalf Of Petrie, Glen
Sent: Tuesday, January = 24, 2012 2:34 PM
To: Michael Sweet; Zehler, Peter
Cc: <= a href=3D"mailto:ipp@pwg.org">ipp@pwg.org
Subject: RE: [IPP] = media-input-tray-check-default

 

Should the value of “Unknown” be us= ed?   Below is the statement from rfc2911

 

Note: SNMP MIBs use '2' for 'unknown' which= corresponds to the IPP

   "out-of-b= and" value 'unknown'.  See the description of the "out-of-

   band" values at the beginning of S= ection 4.1.  Therefore, attributes

  = ; of type 'enum' start at '3'.

 

 

OK, I'm convinced.  I'll add "no-value&= quot; to this one and any others like it where it would not always make sen= se to force a default value.

 =

 

On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:

 

Mike,

I prefer option #2.  One of my= reason is that it allows the operator to set policy for underspecified job= s on the printer.  (If the client is not being careful, then the print= er will.)  It is a very handy feature in production printing.

Pete<= /p>

 

=

Peter Zehler

Xerox<= /span> Research Center Webster
= Email: Peter.Zehler@Xe= rox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: = Peter Zehler
Xerox Corp.
= 800 Phill= ips Rd.
M/S 128-25E
Webster NY, 14580-9701

=

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of&nb= sp;Paul Tykodi
Sent: Tuesday, January 24, 2012 6:11 AM
To: ipp@pwg.org
Subject: RE: [IPP] media-input-tray-check-defa= ult

 

Hi Mike,

 

= For production printing, I have found during my career that it is critical = to have automatic checks and balances within the job submission workflow so= that a very large job (with a significant cost of production) is not relea= sed such that it will be printed on incorrect media and thus be a total los= s (i.e. must be destroyed and cannot be distributed – job must be run= again). The AFP Consortium has the same type of intelligence in their Inte= lligent Printer Data Stream specification as we have in IPP.

 

<= /div>

I think it is possible that some vend= ors may have interpreted the description in the specification to mean that = the default value should refer to the function being enabled or disabled. I= f it is enabled, it then interacts with the media in the job ticket I there= fore prefer option #2 to resolve this issue.

 

Best Regards,

 

/Paul

--

P= aul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC<= br>
Tel/Fax: 603-343-1820
Mobile:&nb= sp; 603-866-0712
E-mail:  = p= tykodi@tykodi.com
WWW:  http://www.tykodi.com

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, January 23, 2012 6:14 PM<= br>To: ipp@pwg.org
Subject: [IPP] media-i= nput-tray-check-default

 

All,

&nbs= p;

I am going through yet another round of updates to the = IANA registry (this time for sure! :), and noticed that I still have the me= dia-input-tray-check-default attribute tagged as "under review". = I would like to resolve this before we submit our next round of updates to = the registry.

 

BACKGROUND

 

PWG 5100.3 (Production Printing Set 1) defi= nes the media-input-tray-check Job Template attribute thusly:

 

<= p class=3DMsoNormal>The “media-input-tray= -check” Job Template attribute indicates that the Printer MUST check&= nbsp;that the characteristics of the media in the identified input tra= y are the same as characteristics of the media identified by the = Job's "media" Job Template attribute or matched (see se= ction 3.13) by the Job's "media- col" Job Template attr= ibute. The keyword values are the same input tray keyword values as ar= e defined for the "media" Job Template attribute (see sectio= n 6.3 in this document and [RFC2911] Appendix C), i.e., 'top', 'm= iddle', 'bottom', etc.

 

=

Independen= t of the "ipp-attributes-fidelity" operation attribute supplied b= y the client, if the characteristics differ, the Printer adds the= ‘resources-are-not-ready’ value (see section 6.1) to the job's= "job-state-reasons" attribute and MAY either (1) put the jo= b into the ‘pending-held’ state or (2) start to process th= e job normally, but immediately stop the job (“job-state” = =3D ‘processing-stopped’) and the Printer (“printer-state= ” =3D ‘stopped’). In either implementation, the oper= ator can change the media in the input tray to agree with the job= or can modify the job’s “media” or “media-col= ” attributes to agree with the input tray, depending on policy.<= /span>

 

=

Table 1 (at the begin= ning of section 3) defines media-input-tray-check-default and -supported.

 

The issue is that there should not= be a default media-input-tray-check value; like some other Job Template at= tributes (e.g. overrides), it does not make sense to have a default value f= or this particular attribute since it interacts with the media in the job t= icket.

 

<= p class=3DMsoNormal>There are two ways to resol= ve this issue:

 

1. Drop media-input= -tray-check-default from the registry and post an errata for 5100.3 removin= g the media-input-tray-check-default attribute from Table 1.

 

<= span style=3D'color:black'>2. Update the definition of media-input-tray-che= ck-default to include the "no-value" out-of-band value.

 

I prefer option #1.

 =

Comments?

 

__________________________________________________= ______________________

Michael Sweet, Se= nior Printing System Engineer, PWG Chair

<= /div>

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean.

=


-- 
This message has been scanned f= or viruses and 
dangerou= s content by MailScanner, and is 
beli= eved to be clean.


-- 
This message has been scanned= for viruses and 
danger= ous content by MailScanner, and is 
be= lieved to be clean. _______________________________________________
ipp = mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp<= /span>

 

__________________________= ________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


--
This message has been scanned for= viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses = and
dangerous content by Ma= ilScanner, and is
believed to be clean.

 

____________________= ______________________________

Michael Sweet= , Senior Printing System Engineer, PWG Chair

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CCDB7C.2C958418-- --===============0528322701== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0528322701==-- From ipp-bounces@pwg.org Wed Jan 25 08:17:37 2012 Return-Path: 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 43ABA21F8631 for ; Wed, 25 Jan 2012 08:17:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.404 X-Spam-Level: X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gewdVALd7f2C for ; Wed, 25 Jan 2012 08:17:36 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3242721F862D for ; Wed, 25 Jan 2012 08:17:36 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 23E54796AE; Wed, 25 Jan 2012 11:17:05 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 5B24E79679; Wed, 25 Jan 2012 11:16:34 -0500 (EST) MIME-version: 1.0 Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYD00MKN3S7WEK0@mail-out.apple.com>; Wed, 25 Jan 2012 08:16:33 -0800 (PST) X-AuditID: 11807112-b7b14ae00000798e-5a-4f202ad845fa Received: from [17.151.73.235] (Unknown_Domain [17.151.73.235]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay17.apple.com (Apple SCV relay) with SMTP id 00.CF.31118.EDA202F4; Wed, 25 Jan 2012 08:16:33 -0800 (PST) Subject: Re: [IPP] media-input-tray-check-default From: Michael Sweet In-reply-to: Date: Wed, 25 Jan 2012 08:16:25 -0800 Message-id: References: <45FF3748-CED0-44EC-8201-F84EECDF5B0D@apple.com> <03f001ccda88$cb244120$616cc360$@tykodi.com> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUiON3zte5DLQV/g+/3JS22n/3FYnFs30sW i639Z5gsjnyLteh4spLVgdVj68kfbB4H589i95i3eDqTx/JT69kCWKK4bFJSczLLUov07RK4 MloOtDEX9ElVrH75mq2BcZl4FyMnh4SAicTDgy9YIGwxiQv31rN1MXJxCAlMZZJYPXk/K0hC WMBQYsbjyewgNq+AnsS+s/MYQWxmgQSJp5POs4HYbAJqEr8n9YHVcwp4SXRMWcwMYrMIqEr8 WHUAqt5LYnf3cxaIOTYS67ftYYJYdppF4safXWDNIgL6Ep8+bmaCuEhW4uKBSawTGPlmIdk9 C8luCFtbYtnC18yzGDmAbB2JyQsZUYUh7I/njzAtYGRbxShYlJqTWGlorpdYUJCTqpecn7uJ ERTWDYVCOxjv79I7xCjAwajEw9ugIO8vxJpYVlyZe4hRgoNZSYR3qrqCvxBvSmJlVWpRfnxR aU5q8SFGaQ4WJXHe7esl/YUE0hNLUrNTUwtSi2CyTBycUg2Mzma9BS1852yXR/0rOfl0rfLU NDPZqc8XSdcaeCbJ3H38Slme1+TfVblm3ontrkoi8hfefLzj6bvs5qoitYlttzbHOU11ahQp 13miqnq3r/S67sSVB1KF/1r4//98Qef4x7CpirY2/CcP1zeWXffiPd59/8Vik5TtzSort27Y v/Ny9I/9uQcllFiKMxINtZiLihMBD6GihmcCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0541814802==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 23E54796AE.A8A01 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0541814802== Content-type: multipart/alternative; boundary="Boundary_(ID_/8jQfG1ZReXqXQaEeMgfnw)" --Boundary_(ID_/8jQfG1ZReXqXQaEeMgfnw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Glen, On Jan 25, 2012, at 7:12 AM, Petrie, Glen wrote: > ... > > [If we change (input) tray to source; does output bin have a new name?] > Since output-bin and OutputBin are a ship that sailed a long long time ago, I think we should stick with it with the appropriate documentation ("bin" refers to a tray, mailbox, pickup roll, etc.) __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_/8jQfG1ZReXqXQaEeMgfnw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable
Glen,
=
On Jan 25, 2012, at 7:12 AM, Petrie, Glen wrote:

... 

[If we change (input) tray to source= ; does output bin have a new name?]

=

Since output-bin and OutputBin = are a ship that sailed a long long time ago, I think we should stick with i= t with the appropriate documentation ("bin" refers to a tray, mailbox, pick= up roll, etc.)

_______________________________________= ___________
Michael Sweet, Senior Printing System Engineer, = PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_/8jQfG1ZReXqXQaEeMgfnw)-- --===============0541814802== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0541814802==-- From comercial@francisco-oliveira.com Wed Jan 25 12:22:04 2012 Return-Path: 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 7DEA911E809C for ; Wed, 25 Jan 2012 12:22:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.401 X-Spam-Level: **** X-Spam-Status: No, score=4.401 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_99=3.5, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmcEGTAC73xn for ; Wed, 25 Jan 2012 12:22:02 -0800 (PST) Received: from iberweb-12a.ibername.com (iberweb-12a.ibername.com [188.93.230.135]) by ietfa.amsl.com (Postfix) with ESMTP id 58E2311E80B9 for ; Wed, 25 Jan 2012 12:21:59 -0800 (PST) Received: from bl14-58-47.dsl.telepac.pt ([85.247.58.47] helo=fos5mkgugpcpfe) by iberweb-12a.ibername.com with esmtpa (Exim 4.69) (envelope-from ) id 1Rq9LZ-0000C9-8n; Wed, 25 Jan 2012 20:21:33 +0000 From: =?iso-8859-1?Q?EasyNet4You_-_Constru=E7=E3o_e_Manuten=E7=E3o_de_Sites?= To: Subject: =?iso-8859-1?Q?Fazemos_Sites_na_Internet_-_6_euros_/_m=EAs_-_N/Ref:_12520?= =?iso-8859-1?Q?20?= Date: Wed, 25 Jan 2012 20:21:39 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_100E3_01CCDB9E.F42E6A20" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aczbntv82SLR542kRzqkDiQ3JBoXRQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - iberweb-12a.ibername.com X-AntiAbuse: Original Domain - megatron.ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - francisco-oliveira.com Message-Id: <20120125202200.58E2311E80B9@ietfa.amsl.com> This is a multi-part message in MIME format. ------=_NextPart_000_100E3_01CCDB9E.F42E6A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable EasyNet4You - Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet=20 Website: www.easynet4you.com =20 E-Mail: easynet4you@gmail.com=20 Rua Filipe Folque, N=BA 10 G =96 Apartado 12058=20 1061- 001 Lisboa=20 Assunto: Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet ( 6 euros = / m=EAs ).=20 Podem ter o Site da vossa Empresa na Internet em 5 dias uteis por 6 = euros / m=EAs (este valor inclui a Constru=E7=E3o do Site, Alojamento, Dominio, = E-Mails, e Manuten=E7=E3o), se no entanto n=E3o tiverem neste momento verba = disponivel e se mesmo assim gostassem de ter um Site, n=F3s tamb=E9m disponibilizamos = uma op=E7=E3o de Sites Gratuitos, em que podem ter um Site mais elementar mas = igualmente eficaz, com Design Atrativo, completamente gratuito, totalmente = configur=E1vel com v=E1rios Designs e possibilidade de alterar conte=FAdos, de imediato = e em menos de 15 minutos, basta fazerem o registo no nosso Site ! =C9 fundamental para qualquer Actividade assegurar a sua presen=E7a com = um Site na Internet, pois porporciona:=20 - Melhoria da Imagem Corporativa=20 - Melhoria do Servi=E7o a Clientes=20 - Melhoria da Comunica=E7=E3o=20 - Expans=E3o=20 - Novas oportunidades de neg=F3cio=20 - Transac=E7=F5es On-Line=20 - Redu=E7=E3o de Custos=20 - Informa=E7=E3o sempre disponivel, 24 horas / 7 dias da semana=20 Estas s=E3o apenas algumas das vantagens de estar na Internet. S=E3o = muitos os benef=EDcios que podem ser obtidos utilizando a tecnologia certa e a = grande rede da Internet. Temos experi=EAncia em criar Sites para v=E1rias = =E1reas de neg=F3cio, e em trabalhos, desde Lojas Virtuais e Sites altamente = din=E2micos, at=E9 trabalhos de simples p=E1ginas, est=E1ticas, de presen=E7a na = Internet.=20 Apostamos fortemente em solu=E7=F5es de qualidade feitas =E0 medida, personaliz=E1veis ao gosto do cliente, baixo custo, tempos m=EDnimos de desenvolvimento, rela=E7=E3o f=E1cil e flexivel sem burocracias e = on-line, assist=EAncia 24/7, e servidores dedicados que garantem alta = disponibilidade, e grande velocidade de acesso. Se estiver interessado em saber mais informa=E7=F5es sobre os nossos = servi=E7os poder=E1 consultar o nosso Site www.easynet4you.com, ou entrar em = contacto connosco para o e-mail easynet4you@gmail.com, que teremos todo o gosto = em esclarecer e aprsesentar as nossas melhores solu=E7=F5es para o vosso = caso. Sem outro assunto de momento, e agrade=E7endo antecipadamente a = aten=E7=E3o que V. Exas ir=E3o prestar ao assunto, subscrevo-mos-nos. Com os melhores cumprimentos, e considera=E7=E3o,=20 EasyNet4You =96 Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet=20 www.easynet4you.com=20 easynet4you@gmail.com=20 Nota: Se n=E3o quiser receber mais correspond=EAncia nossa, poder=E1 = retirar o seu endere=E7o desta lista de distribui=E7=E3o no seguinte endere=E7o http://www.francisco-oliveira.com/retirar.htm Note: If don't want to receive more e-mails from us, you will be able to remove your address from this distribution list in the following address http://www.francisco-oliveira.com/retirar.htm ------=_NextPart_000_100E3_01CCDB9E.F42E6A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

EasyNet4You - Constru=E7=E3o e = Manuten=E7=E3o de Sites na Internet
Website: www.easynet4you.com  =
E-Mail: easynet4you@gmail.com
Rua Filipe Folque, N=BA 10 G = – Apartado 12058
1061- 001 Lisboa

Assunto: Constru=E7=E3o e = Manuten=E7=E3o de Sites na Internet ( 6 euros / m=EAs ).

Podem ter o Site da vossa Empresa na = Internet em 5 dias uteis por 6 euros / m=EAs (este valor inclui a = Constru=E7=E3o do Site, Alojamento, Dominio, E-Mails, e Manuten=E7=E3o), = se no entanto n=E3o tiverem neste momento verba disponivel e se mesmo = assim gostassem de ter um Site, n=F3s tamb=E9m disponibilizamos uma = op=E7=E3o de Sites Gratuitos, em que podem ter um Site mais elementar = mas igualmente eficaz, com Design Atrativo, completamente gratuito, = totalmente configur=E1vel com v=E1rios Designs e possibilidade de = alterar conte=FAdos, de imediato e em menos de 15 minutos, basta fazerem = o registo no nosso Site !

=C9 fundamental para qualquer = Actividade assegurar a sua presen=E7a com um Site na Internet, pois = porporciona:

- Melhoria da Imagem Corporativa
- Melhoria do Servi=E7o a = Clientes
- Melhoria da Comunica=E7=E3o
- Expans=E3o
- Novas oportunidades de = neg=F3cio
- Transac=E7=F5es On-Line
- Redu=E7=E3o de Custos
- Informa=E7=E3o sempre disponivel, 24 = horas / 7 dias da semana

Estas s=E3o apenas algumas das = vantagens de estar na Internet. S=E3o muitos os benef=EDcios que podem = ser obtidos utilizando a tecnologia certa e a grande rede da Internet. = Temos experi=EAncia em criar Sites para v=E1rias =E1reas de neg=F3cio, e = em trabalhos, desde Lojas Virtuais e Sites altamente din=E2micos, at=E9 = trabalhos de simples p=E1ginas, est=E1ticas, de presen=E7a na Internet. =

Apostamos fortemente em solu=E7=F5es de = qualidade feitas =E0 medida, personaliz=E1veis ao gosto do cliente, = baixo custo, tempos m=EDnimos de desenvolvimento, rela=E7=E3o f=E1cil e = flexivel sem burocracias e on-line, assist=EAncia 24/7, e servidores = dedicados que garantem alta disponibilidade, e grande velocidade de = acesso.

Se estiver interessado em saber mais = informa=E7=F5es sobre os nossos servi=E7os poder=E1 consultar o nosso = Site www.easynet4you.com, ou entrar em contacto connosco para o e-mail = easynet4you@gmail.com, que teremos todo o gosto em esclarecer e = aprsesentar as nossas melhores solu=E7=F5es para o vosso = caso.

Sem outro assunto de momento, e = agrade=E7endo antecipadamente a aten=E7=E3o que V. Exas ir=E3o prestar = ao assunto, subscrevo-mos-nos.

Com os melhores cumprimentos, e = considera=E7=E3o,
EasyNet4You – = Constru=E7=E3o e Manuten=E7=E3o de Sites na Internet
www.easynet4you.com
easynet4you@gmail.com


Nota: Se n=E3o quiser receber mais = correspond=EAncia nossa, poder=E1 retirar o seu endere=E7o desta lista = de distribui=E7=E3o no seguinte endere=E7o http://www.francis= co-oliveira.com/retirar.htm

Note: If don't want to receive more = e-mails from us, you will be able to remove your address from this = distribution list in the following address http://www.francis= co-oliveira.com/retirar.htm

------=_NextPart_000_100E3_01CCDB9E.F42E6A20-- From pwg-announce-bounces@pwg.org Thu Jan 26 14:38:10 2012 Return-Path: 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 A23EE21F8630 for ; Thu, 26 Jan 2012 14:38:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.919 X-Spam-Level: X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[AWL=-0.735, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CugW+J5uF1QI for ; Thu, 26 Jan 2012 14:38:09 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B97D621F8603 for ; Thu, 26 Jan 2012 14:38:09 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 3A3EB7964A; Thu, 26 Jan 2012 17:37:50 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by pwg.org (Postfix) with ESMTP id 137B179640 for ; Thu, 26 Jan 2012 17:37:35 -0500 (EST) Received: by werb13 with SMTP id b13so1023330wer.5 for ; Thu, 26 Jan 2012 14:37:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=C3TUH48s93RvozXjEQlxbJFH0ieO+CjZoyC4SsNEfGM=; b=NeploHBnJNuGT46B3c1hQSpt11qlkqbYQLd//F8tMOMaw67akN0cEBlGKm7Pm40sjO UogiUcakKmAbCFZG+0fRCxOjuNKuqDpLep6+zxDj38YVU5cTbwsbEN/kmzh2hVeVU1GD j5IR1B+soSGXms+gOfnu/we9ZdsUf7T2ZPwSk= MIME-Version: 1.0 Received: by 10.216.131.78 with SMTP id l56mr2338248wei.56.1327617455126; Thu, 26 Jan 2012 14:37:35 -0800 (PST) Received: by 10.223.96.73 with HTTP; Thu, 26 Jan 2012 14:37:35 -0800 (PST) Date: Thu, 26 Jan 2012 17:37:35 -0500 Message-ID: From: Ira McDonald To: pwg-announce@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [Pwg-Announce] PWG Approved - Cloud Imaging WG Charter - 26 January 2012 X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1941217602==" Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 3A3EB7964A.AC44F X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1941217602== Content-Type: multipart/alternative; boundary=0016e6d460a6cf7a1f04b776065b --0016e6d460a6cf7a1f04b776065b Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm pleased to announce that at today's PWG Steering Committee meeting, the updated charter for Cloud Imaging WG was approved unanimously: ftp://ftp.pwg.org/pub/pwg/cloud/charter/ch-cloud-charter-20120126.pdf This updated charter adds the Mapping of MSPS, PPD, and JDF to/from PWG Print Job Ticket (CLOUDMAP) and adjusts dates of other existing work items. Cheers, - Ira (PWG Secretary) PS - Mike - please update the charter link on the Cloud Imaging WG web page - thanks. Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --0016e6d460a6cf7a1f04b776065b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm pleased to announce that at today's PWG Steering Com= mittee
meeting, the updated charter for Cloud Imaging WG was approvedunanimously:

=A0 ftp://ftp.pwg.org/pub/pwg/cloud/charter/ch-= cloud-charter-20120126.pdf

This updated charter adds the Mapping of MSPS, PPD, and JDF
to/from= =A0PWG Print Job Ticket (CLOUDMAP) and adjusts dates of
other existing = work items.

Cheers,
- Ira (PWG Secretary)

PS - Mike - plea= se update the charter link on the Cloud Imaging WG
web page - thanks.

Ira McDonald (Musician / Software A= rchitect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-= ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair -= TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --0016e6d460a6cf7a1f04b776065b-- --===============1941217602== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --===============1941217602==-- From pwg-announce-bounces@pwg.org Thu Jan 26 16:16:26 2012 Return-Path: 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 4C92921F86B2 for ; Thu, 26 Jan 2012 16:16:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.429 X-Spam-Level: X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kKL8xIzqsSo for ; Thu, 26 Jan 2012 16:16:25 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id A184521F8686 for ; Thu, 26 Jan 2012 16:16:25 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6FB7E79662; Thu, 26 Jan 2012 19:16:09 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id DA2A579593 for ; Thu, 26 Jan 2012 19:15:51 -0500 (EST) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYF002XMKPDEDM2@mail-out.apple.com> for pwg-announce@pwg.org; Thu, 26 Jan 2012 16:15:51 -0800 (PST) X-AuditID: 11807112-b7b14ae00000798e-5b-4f21ecb612e8 Received: from [17.151.69.13] (Unknown_Domain [17.151.69.13]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay17.apple.com (Apple SCV relay) with SMTP id E9.F7.31118.6BCE12F4; Thu, 26 Jan 2012 16:15:51 -0800 (PST) From: Michael Sweet Date: Thu, 26 Jan 2012 16:15:50 -0800 To: pwg-announce@pwg.org Message-id: <4CFF7CC8-6950-4767-99FE-E4A5C134D0D2@apple.com> X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHJMWRmVeSWpSXmKPExsUiON2VV3f7G0V/g2+7mC2OfIu1WNe6mtmB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyujufsFUsJq74vPLs6wNjPM4uxg5OCQETCTW dtd3MXICmWISF+6tZ+ti5OIQEpjMJPHg63lWkASbgJrE70l9YDazgJbEjX8vmSBsbYllC18z g9gsAqoSW55uBrOFBXwlljf0sYHYIgISEtO654H18grYSNy8vpYNwtaT2Hd2HiPEYlmJiwcm sU5g5JmFZMUsJCtmIWlZwMi8ilGwKDUnsdLQXC+xoCAnVS85P3cTIyhUGgqFdjDe36V3iFGA g1GJh9dzkqK/EGtiWXFl7iFGCQ5mJRHeO15AId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rzz7yr4 CwmkJ5akZqemFqQWwWSZODilGhibJqiHskyOOFbiYMhTfiPBb1GSV/6ixEtfum55mm2VW3hP c0qW5ues/p7ZWws579+wPu67NujupM/vhXbnM32Ud8tzDprTONcmLsjvgEjsrVimo1zvOtVF Hf6oqzZOCJlxLNxoo/T6zV9e1p/tkdSbHhdnKS2/dkn8yRV3/e9H/2aYpHX6qZgSS3FGoqEW c1FxIgD9uSvxEQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG Last Call of PWG Raster Format specification (1/26/12 - 2/24/12) X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 6FB7E79662.AC636 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org All, [This PWG Last Call starts today, Thursday January 26, 2012 and ends Friday February 24, 2012 at 10pm US PDT.] This is the formal announcement of the PWG Last Call for the PWG Raster Format specification, located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20120123.pdf All required attributes and values defined in this document have been prototyped by Apple and/or other vendors. The IPP WG has completed extensive review of the various revisions of this document and the PWG Steering Committee has approved moving it to PWG Last Call without a working group last call. The PWG Process/3.0 requires that a quorum (30%) of PWG voting members must acknowledge a PWG Last Call (with or without comments), before any document can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote but it DOES require your review acknowledgment. Please send your review acknowledgment to the IPP WG list as follows: To: ipp at pwg.org Subject: has reviewed the PWG Raster Format specification and has [no] comments Please do NOT simply reply to this note on the PWG-Announce list. Note: The PWG Definition of the Standards Development Process Version 3.0 is located at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From ipp-bounces@pwg.org Thu Jan 26 21:56:50 2012 Return-Path: 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 2A18421F85CE for ; Thu, 26 Jan 2012 21:56:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.447 X-Spam-Level: X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMaeKgROuxXJ for ; Thu, 26 Jan 2012 21:56:49 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8AE21F85C7 for ; Thu, 26 Jan 2012 21:56:49 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D37327967E; Fri, 27 Jan 2012 00:56:24 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 657477967D for ; Fri, 27 Jan 2012 00:56:08 -0500 (EST) MIME-version: 1.0 Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYG00A3A0HEHX70@mail-out.apple.com> for ipp@pwg.org; Thu, 26 Jan 2012 21:56:08 -0800 (PST) X-AuditID: 11807137-b7b7fae000005b9a-fe-4f223c776866 Received: from [17.151.71.107] (Unknown_Domain [17.151.71.107]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id F0.2C.23450.87C322F4; Thu, 26 Jan 2012 21:56:08 -0800 (PST) From: Michael Sweet Date: Thu, 26 Jan 2012 21:56:08 -0800 To: "ipp@pwg.org" Message-id: <05DAC99A-8D88-4279-9825-A3064F670368@apple.com> X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUiON09W7fCRsnf4FWXosWxfS9ZLI58i3Vg 8th68gebx7zF05kCmKK4bFJSczLLUov07RK4Mn527WYvOMxf0fnrGnMD42veLkZODgkBE4m/ ByYxQ9hiEhfurWfrYuTiEBKYyiSx7cJkdpAEm4CaxO9JfawgNrNAgsTCFz1gDSwCqhLbljSw gNjCAvoSK/dvYQSxRQTkJda2TWUCsXkFbCT6TkxghbD1JPadnccIsUxW4uKBSawTGLlnIRk7 C0kZRFxbYtnC10BxDiBbR2LyQqiwvMT2t3OYYUo+nj/CtICRbRWjYFFqTmKloZleYkFBTqpe cn7uJkZQaDUUmu9g3P5X7hCjAAejEg+v5yRFfyHWxLLiytxDjBIczEoivHe8gEK8KYmVValF +fFFpTmpxYcYpTlYlMR5599V8BcSSE8sSc1OTS1ILYLJMnFwSjUwuh7U2JP31+ocQ8a+xXca 1ZX7LN/v+LOSy+DzhAVfWd5uKL33zn3BtLDLv2VUdy7zCq7WqSzv0fVrWLzq2UXRUsfpCo8f K2kuDpjopzDl9bOey5OnahpvTZ0/bfqeWxyC4XcO/Fw7YxI3s+DZ/ze9f3zf/vf+tCn+Tzhy TVf4578xvurrbh951VOJpTgj0VCLuag4EQCZICfcKQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] output-bin (type2 keyword | name(MAX)) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0958895967==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: D37327967E.A9239 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0958895967== Content-type: multipart/alternative; boundary="Boundary_(ID_yndNuGhU7u8cw7zpSn+h6A)" --Boundary_(ID_yndNuGhU7u8cw7zpSn+h6A) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, Currently PWG 5100.2 defines the output-bin attribute as "type2 keyword | name(MAX)", however we normally define such things as "type3 keyword | name(MAX)". What do people think about amending the registration of output-bin to be "type3 keyword | name(MAX)" and doing an errata for 5100.2? __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_yndNuGhU7u8cw7zpSn+h6A) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All,

Currently PWG 5100.2 defines the output-bin attribute as "type2 keyword | name(MAX)", however we normally define such things as "type3 keyword | name(MAX)".

What do people think about amending the registration of output-bin to be "type3 keyword | name(MAX)" and doing an errata for 5100.2?

__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_yndNuGhU7u8cw7zpSn+h6A)-- --===============0958895967== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0958895967==-- From ipp-bounces@pwg.org Thu Jan 26 22:38:47 2012 Return-Path: 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 362C021F8541 for ; Thu, 26 Jan 2012 22:38:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.462 X-Spam-Level: X-Spam-Status: No, score=-102.462 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9K6hNfEYbuw for ; Thu, 26 Jan 2012 22:38:46 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE7421F853F for ; Thu, 26 Jan 2012 22:38:46 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A67E47967D; Fri, 27 Jan 2012 01:38:28 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id D2A857967A for ; Fri, 27 Jan 2012 01:38:14 -0500 (EST) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYG00BZZ2EZ1I30@mail-out.apple.com> for ipp@pwg.org; Thu, 26 Jan 2012 22:38:14 -0800 (PST) X-AuditID: 11807136-b7b94ae000002733-ea-4f22465556c5 Received: from [17.151.71.107] (Unknown_Domain [17.151.71.107]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id 17.BF.10035.656422F4; Thu, 26 Jan 2012 22:38:14 -0800 (PST) From: Michael Sweet Date: Thu, 26 Jan 2012 22:38:13 -0800 To: "ipp@pwg.org" Message-id: <609D2D2A-D62F-47D3-A0B9-E6E5FE5F1FEC@apple.com> X-Mailer: Apple Mail (2.1419) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUiON09WzfMTcnfYNs9IYtj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZbTO28ZYsMW+4v7dacwNjIvMuhg5OSQETCR6 u3pZIWwxiQv31rOB2EICU5kk+m+ogthsAmoSvyf1gdUwCyRItD49wAJiswioSqycc40dxBYW MJT4tfYVWFxEQF5ibdtUJhCbV8BG4u3xs1C2nsS+s/MYIXbJSlw8MIl1AiP3LCRjZyEpg4hr Syxb+Jp5FiMHkK0jMXkhmjCE/fH8EaYFjGyrGAWLUnMSKw1N9RILCnJS9ZLzczcxggKrodBs B+OOv3KHGAU4GJV4eD0nKfoLsSaWFVfmHmKU4GBWEuG94wUU4k1JrKxKLcqPLyrNSS0+xCjN waIkzjvvroK/kEB6YklqdmpqQWoRTJaJg1OqgXHF16O3hO4JGB0wW7vJ471I1sfZq+zVZ2/f G5PYeeyAcrDFRp3FMfvTtY/c7RNS4P581EC/5sx9gcbIN4bnueac3+sSa/conE8ufts7T7+z V1V0OGcaduzZmL/eMZS91fb04hfnJzEt5Za6UuBsKiD89llhZoCs1wqRyas2K6uzrGq6zuQY 1qDEUpyRaKjFXFScCAA8HLKnKAIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Updated IANA registrations now online... X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0357133773==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: A67E47967D.A9748 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0357133773== Content-type: multipart/alternative; boundary="Boundary_(ID_8cY/3tQ1mf4QWuT+56DVFA)" --Boundary_(ID_8cY/3tQ1mf4QWuT+56DVFA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have just finished another round of review and fixes to the IANA registrations and put the results up on the IPP WG page: http://www.pwg.org/ipp Aside from the open issue on the "output-bin" job template attribute, I think the updated registry is now completely up-to-date and accurate (famous last words! :) Changes include: - Global change: "Document Template" to "Document Template" - Global: Fixed keywords to define values for main attribute, references for -foo - Global: Fixed enums to define values for main attribute, references for -foo - Global: Fixed sorting of many attributes. - Global: xxx-default, xxx-ready, and xxx-supported attributes belong in the Printer Description collection since they are Printer attributes. - Global: xxx-actual attributes belong in the Job/Document Description collections - Global: Fix collections to define members for main attribute, references for -foo - overrides.pages appeared multiple times in document template - There was no "" for overrides in document template - Added missing presentation-direction-number-up-default and -supported - Added print-content-optimize/-actual to Document Template/Description collections - Added media-grain, media-thickness, and media-tooth member attributes from PWG 5100.11 (accidentally deleted) - Added missing cover-back-supported and cover-front-supported keyword values from PWG 5100.3 - Added missing page-delivery-default/-supported keyword registrations from PWG 5100.3 - Added missing page-order-received-default/-supported keyword registrations from PWG 5100.3 - Added missing presentation-direction-number-up-default/-supported keyword registrations from PWG 5100.3 - Added missing print-content-optimize-default/-supported keyword registrations from PWG 5100.7 - Added missing separator-sheets-default/-supported keyword registrations from PWG 5100.3 - Added missing stitching-supported keyword registrations from PWG 5100.3 - Added missing stitching-reference-edge-default/-supported keyword registrations from PWG 5100.3 - Added missing x-image-position-default/-supported keyword registrations from PWG 5100.3 - Added missing y-image-position-default/-supported keyword registrations from PWG 5100.3 - Removed page-overrides-actual and pages-per-subset-actual since the dependent spec (5100.4) is obsoleted - Removed operations-supported value 0 (not a valid enum) - Fixed the registration of job-error-sheet (missing media and media-col) - Fixed the registration of job-finishings-col-ready (was "1setOf type2 enum" but should have been "1setOf collection") - Fixed the registration of media-input-tray-check-default to also have the "no-value" out-of-band value - Fixed the registration of pdl-init-file-* (and all -supported attributes are Printer Description) - Fixed the registration of save-xxx-supported attributes __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_8cY/3tQ1mf4QWuT+56DVFA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have just finished another round of review and fixes to the IANA registrati= ons and put the results up on the IPP WG page:


A= side from the open issue on the "output-bin" job template attribute, I thin= k the updated registry is now completely up-to-date and accurate (famous la= st words! :)

Changes include:

=
    - Global change: "Document Template" to "Document T= emplate"
    - Global: Fixed keywords to define values = for main attribute, references for -foo
    - Global: F= ixed enums to define values for main attribute, references for -foo
    - Global: Fixed sorting of many attributes.
&nbs= p;   - Global: xxx-default, xxx-ready, and xxx-supported attributes be= long in the Printer Description collection since they are Printer attribute= s.
    - Global: xxx-actual attributes belong in the Jo= b/Document Description collections
    - Global: Fix co= llections to define members for main attribute, references for -foo
    - overrides.pages appeared multiple times in document temp= late
    - There was no "<Any other Template attribu= te affecting pages>" for overrides in document template
 =   - Added missing presentation-direction-number-up-default and -suppo= rted
    - Added print-content-optimize/-actual to Docu= ment Template/Description collections
    - Added media= -grain, media-thickness, and media-tooth member attributes from PWG 5100.11= (accidentally deleted)
    - Added missing cover-back-= supported and cover-front-supported keyword values from PWG 5100.3
    - Added missing page-delivery-default/-supported keyword re= gistrations from PWG 5100.3
    - Added missing page-or= der-received-default/-supported keyword registrations from PWG 5100.3
=
    - Added missing presentation-direction-number-up-default= /-supported keyword registrations from PWG 5100.3
    -= Added missing print-content-optimize-default/-supported keyword registrati= ons from PWG 5100.7
    - Added missing separator-sheet= s-default/-supported keyword registrations from PWG 5100.3
 =   - Added missing stitching-supported keyword registrations from PWG = 5100.3
    - Added missing stitching-reference-edge-def= ault/-supported keyword registrations from PWG 5100.3
  &nbs= p; - Added missing x-image-position-default/-supported keyword registration= s from PWG 5100.3
    - Added missing y-image-position-= default/-supported keyword registrations from PWG 5100.3
  &= nbsp; - Removed page-overrides-actual and pages-per-subset-actual since the= dependent spec (5100.4) is obsoleted
    - Removed ope= rations-supported value 0 (not a valid enum)
    - Fixe= d the registration of job-error-sheet (missing media and media-col)
    - Fixed the registration of job-finishings-col-ready (was = "1setOf type2 enum" but should have been "1setOf collection")
&nb= sp;   - Fixed the registration of media-input-tray-check-default to al= so have the "no-value" out-of-band value
    - Fixed th= e registration of pdl-init-file-* (and all -supported attributes are Printe= r Description)
    - Fixed the registration of save-xxx= -supported attributes

_______________________________________________= ___
Michael Sweet, Senior Printing System Engineer, PWG Chai= r


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_8cY/3tQ1mf4QWuT+56DVFA)-- --===============0357133773== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0357133773==-- From ipp-bounces@pwg.org Fri Jan 27 10:33:22 2012 Return-Path: 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 7885E21F8526 for ; Fri, 27 Jan 2012 10:33:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.517 X-Spam-Level: X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrLnXvojRgFK for ; Fri, 27 Jan 2012 10:33:21 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5C90E21F84DD for ; Fri, 27 Jan 2012 10:33:21 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B1F90796A2; Fri, 27 Jan 2012 13:33:05 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by pwg.org (Postfix) with ESMTP id 1E8DB7969D for ; Fri, 27 Jan 2012 13:32:47 -0500 (EST) Received: by wics10 with SMTP id s10so1885125wic.5 for ; Fri, 27 Jan 2012 10:32:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DxWtPzKQc3DOO0Q7b3wyyPJ4mbbrqzY3b/lfYnOwnAE=; b=PnIwvSgkGhtcKtUe5y/hQMNClGuv+kbXy6hZUeV9SlqcbzXMOOSKdgGEwr7JO0chSC zS65o+9855FZSNbuUuY6bfjT5Cmp+L5fZiQugt30tYD9QWFvzSvMY9Kazt6TJ96ZUERC tPAv9sYZCnzq5g18zICZSXTYgsrR7bJejGmfM= MIME-Version: 1.0 Received: by 10.180.99.225 with SMTP id et1mr12927895wib.2.1327689166935; Fri, 27 Jan 2012 10:32:46 -0800 (PST) Received: by 10.223.96.73 with HTTP; Fri, 27 Jan 2012 10:32:46 -0800 (PST) In-Reply-To: <05DAC99A-8D88-4279-9825-A3064F670368@apple.com> References: <05DAC99A-8D88-4279-9825-A3064F670368@apple.com> Date: Fri, 27 Jan 2012 13:32:46 -0500 Message-ID: Subject: Re: [IPP] output-bin (type2 keyword | name(MAX)) From: Ira McDonald To: Michael Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "ipp@pwg.org" X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1444719480==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: B1F90796A2.A9D7D X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1444719480== Content-Type: multipart/alternative; boundary=f46d041826942ad74f04b786b9a8 --f46d041826942ad74f04b786b9a8 Content-Type: text/plain; charset=ISO-8859-1 Hi Mike, It's OK w/ me, but... I would note that the IESG did NOT accept the distinction between Type 2 (reviewed) and Type 3 (no review) keywords and has always directed IANA to require the Designated Experts (Mike/Ira) to review all registrations. So I'm not sure this is an important correction to make. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG 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 Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Jan 27, 2012 at 12:56 AM, Michael Sweet wrote: > All, > > Currently PWG 5100.2 defines the output-bin attribute as "type2 keyword | > name(MAX)", however we normally define such things as "type3 keyword | > name(MAX)". > > What do people think about amending the registration of output-bin to be > "type3 keyword | name(MAX)" and doing an errata for 5100.2? > > __________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d041826942ad74f04b786b9a8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Mike,

It's OK w/ me, but...

I would note that the IESG= did NOT accept the distinction
between Type 2 (reviewed) and Type 3 (no= review)
keywords and has always directed IANA to require the
Designa= ted Experts (Mike/Ira) to review all registrations.

So I'm not sure this is an important correction to make.

Che= ers,
- Ira

Ira McDonald (Musician / Software Archit= ect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO = Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solution= s WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert = - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter=A0 579 Park Place=A0 Saline, MI=A0 48176=A0 734-944-0094
Summer= =A0 PO Box 221=A0 Grand Marais, MI 49839=A0 906-494-2434



On Fri, Jan 27, 2012 at 12:56 AM, Michae= l Sweet <msweet@ap= ple.com> wrote:
All,

Currently PWG 5= 100.2 defines the output-bin attribute as "type2 keyword | name(MAX)&q= uot;, however we normally define such things as "type3 keyword | name(= MAX)".

What do people think about amending the registration of= output-bin to be "type3 keyword | name(MAX)" and doing an errata= for 5100.2?

__________________________________________________
Michael Sweet,= Senior Printing System=A0Engineer, PWG Chair


= --=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
ipp mailing list
ipp@pwg.org
http= s://www.pwg.org/mailman/listinfo/ipp



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d041826942ad74f04b786b9a8-- --===============1444719480== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1444719480==-- From ipp-bounces@pwg.org Sun Jan 29 13:27:16 2012 Return-Path: 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 CC3A921F8472 for ; Sun, 29 Jan 2012 13:27:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.475 X-Spam-Level: X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsEU7tAO1Hrh for ; Sun, 29 Jan 2012 13:27:16 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCEC21F8474 for ; Sun, 29 Jan 2012 13:27:15 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D4A76795E8; Sun, 29 Jan 2012 16:26:53 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 02464795DC; Sun, 29 Jan 2012 16:26:33 -0500 (EST) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LYK00MRLWVHFM90@mail-out.apple.com>; Sun, 29 Jan 2012 13:26:06 -0800 (PST) X-AuditID: 11807134-b7c42ae000000421-66-4f25b96df245 Received: from [17.151.70.59] (Unknown_Domain [17.151.70.59]) by relay14.apple.com (Apple SCV relay) with SMTP id 5A.D4.01057.D69B52F4; Sun, 29 Jan 2012 13:26:06 -0800 (PST) From: Michael Sweet Date: Sun, 29 Jan 2012 13:26:07 -0800 To: ipp@pwg.org Message-id: <8B86E785-2547-495F-A03A-283A0D20EA71@apple.com> X-Mailer: Apple Mail (2.1255) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUiON3NWjdvp6q/wSlni8vbD7BaHNv3ksXi yLdYB2aPrSd/sHnMWzydKYApissmJTUnsyy1SN8ugSvj0voDrAXzRCv+bnjL3sDYJNzFyMkh IWAi0fd7ChuELSZx4d56IJuLQ0hgPaPE66s7mUESbAJqEr8n9bF2MXJw8AoYSjw4pAMSZhZI kNi24ilYmEVAVeLwviiQsLCAlMS6/ffYIEoEJb62NjCB2CIC/BITL4JM4QSaYiNx8/cJJoi1 shLPZu1gn8DIMwthwSwkCyBseYntb+cwg5QwC+hITF7ICBHWlli28DUzjP3x/BGmBYxsqxgF i1JzEisNTfQSCwpyUvWS83M3MYKCrqHQZAfjwZ/8hxgFOBiVeHgLF6v4C7EmlhVX5h5ilOBg VhLhnbNM1V+INyWxsiq1KD++qDQntfgQozQHi5I47xZrZX8hgfTEktTs1NSC1CKYLBMHp1QD o3JRgadlZKRN81vZa2sX58yVOfOqgHfCErHpM7Q8VLbX7qhTv7HAoFBezr+b+SfrvQMFOyau fnpdUvnriw2CPTsO3Hvzv9o+uMwn5WsBb+ZTz7Z1Qk/KmbfN+PZ76r11HYunHg4+0Tsx6v5Z c42Sde56HqwH2WZMaEgoOXlZnLdI+2zhF9+UrUosxRmJhlrMRcWJAK5ejhc2AgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: cloud@pwg.org Subject: [IPP] IPP Slides posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0549513872==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: D4A76795E8.A84BE X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0549513872== Content-type: multipart/alternative; boundary="Boundary_(ID_gn09eiINFEBVafpozwLW4A)" --Boundary_(ID_gn09eiINFEBVafpozwLW4A) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the draft slides for the February 2012 F2F to: ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-february-12d1.pdf For review at Monday's combined Cloud/IPP conference call... _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_gn09eiINFEBVafpozwLW4A) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the draft slides for the February 2012 F2F to:

<= a href=3D"ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-february-12d1.= pdf">ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-february-12d1.pdf

For review at Monday's combined Cloud/IPP confe= rence call...

_________________________________________________= ________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_gn09eiINFEBVafpozwLW4A)-- --===============0549513872== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0549513872==-- From ipp-bounces@pwg.org Tue Jan 31 00:20:09 2012 Return-Path: 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 889BB21F8713 for ; Tue, 31 Jan 2012 00:20:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.485 X-Spam-Level: X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsfSOViBJJcH for ; Tue, 31 Jan 2012 00:20:08 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4023021F84CF for ; Tue, 31 Jan 2012 00:20:08 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E247D79591; Tue, 31 Jan 2012 03:19:45 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 0B5C679535 for ; Tue, 31 Jan 2012 03:19:29 -0500 (EST) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LYN00ARDLSFB7G0@mail-out.apple.com> for ipp@pwg.org; Tue, 31 Jan 2012 00:19:29 -0800 (PST) X-AuditID: 11807130-b7c1cae000001024-e4-4f27a4102280 Received: from [17.151.68.101] (Unknown_Domain [17.151.68.101]) by relay11.apple.com (Apple SCV relay) with SMTP id 62.02.04132.014A72F4; Tue, 31 Jan 2012 00:19:29 -0800 (PST) From: Michael Sweet Date: Tue, 31 Jan 2012 00:19:29 -0800 To: ipp@pwg.org Message-id: <8798F319-0886-4B74-BD96-FA58BA91FE94@apple.com> X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiON0lVVdwibq/wc+rXBbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyth006Og1aJi46ZTTA2Mk426GDk4JARMJDZ8 K+hi5AQyxSQu3FvP1sXIxSEksJFRYsXx+WwgCTYBNYnfk/pYQWxmgQSJCVMesIPYLAKqEv/u d7OA2MICdhLzFn4Gs0UE+CUmXoSo5xWwkfjeMZ0FwjaUmPmqnRVimazE7YP7mSYwcs9CMnYW kjKIuLbEsoWvmWcBncosoCMxeSEjqjCE/fH8EaYFjGyrGAWLUnMSKw0N9RILCnJS9ZLzczcx gsKqodBgB+Pan/yHGAU4GJV4eAU/qfkLsSaWFVfmHmKU4GBWEuF9sxooxJuSWFmVWpQfX1Sa k1p8iFGag0VJnHeztbK/kEB6YklqdmpqQWoRTJaJg1OqgZGr7P+9Yzpb/0t9DghcJbmS226B e271e68/BStPMdjOuz1PROOUxAnT1k3ddhWOJp/3TrjSF++58N5JUSveFy07Ny7ZeLDj6Den +plzT6bNU3zBydrNe2fpr1eGSrufzYh/LVtxdn1aWPWSPFO7I+nPNFVOiRV7PWxU+Bzry8zj s3uxr9Ot3I1KLMUZiYZazEXFiQCyRE58JwIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Updated IPP Job and Printer Extensions - Set 3 Posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1692264614==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: E247D79591.AAF4F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1692264614== Content-type: multipart/alternative; boundary="Boundary_(ID_wq3xx7kBZkPKxieLhHlovA)" --Boundary_(ID_wq3xx7kBZkPKxieLhHlovA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the updated draft of the IPP Job and Printer Extensions - Set 3 specification to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120131.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120131.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120131-rev.pdf For review at next week's F2F meeting... _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_wq3xx7kBZkPKxieLhHlovA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the updated draft of the IPP Job and Printer Extensions - Set 3= specification to:

<= div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-= break: after-white-space; "> ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprin= terext3v10-20120131.docx
ftp://ftp.pwg.org/pub/pwg/ipp/= wd/wd-ippjobprinterext3v10-20120131.pdf
ftp://ftp.pwg.org/= pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120131-rev.pdf

For review at next we= ek's F2F meeting...

_________________________________________________________
Michael Sw= eet, Senior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_wq3xx7kBZkPKxieLhHlovA)-- --===============1692264614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1692264614==-- From ipp-bounces@pwg.org Tue Jan 31 15:48:34 2012 Return-Path: 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 22E7411E8073 for ; Tue, 31 Jan 2012 15:48:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.494 X-Spam-Level: X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqD4FRAoRAal for ; Tue, 31 Jan 2012 15:48:33 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6393B21F8548 for ; Tue, 31 Jan 2012 15:48:33 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B0F9179561; Tue, 31 Jan 2012 18:48:15 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id DE531793C2 for ; Tue, 31 Jan 2012 18:48:00 -0500 (EST) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0LYO00A0TSR7B7V2@mail-out.apple.com> for ipp@pwg.org; Tue, 31 Jan 2012 15:47:56 -0800 (PST) X-AuditID: 11807136-b7cd6ae000007787-ee-4f287daa359d Received: from [17.151.71.234] (Unknown_Domain [17.151.71.234]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id 64.C8.30599.BAD782F4; Tue, 31 Jan 2012 15:47:56 -0800 (PST) From: Michael Sweet Date: Tue, 31 Jan 2012 15:47:54 -0800 To: "ipp@pwg.org" Message-id: <1B78C61D-B2E5-417F-A7BF-6932744607F7@apple.com> X-Mailer: Apple Mail (2.1422) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiON39le6aWg1/g5eb+CyO7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAlXF8wiy2gg98FZdnuzUwHubtYuTgkBAwkXh9 XruLkRPIFJO4cG89WxcjF4eQwFQmicdnjzCBJNgE1CR+T+pjBbGZBRIkGrbeYgSxWQRUJe5t 2cQOYgsLGEh0bT8FViMiIC+xtm0qWC+vgI3Ejit/WCBsPYkTa86yQSyTldh/6xXjBEbuWUjG zkJSBhGXl9j+dg7zLKBTmQV0JCYvZEQVBrG1JT6eP8K0gJFtFaNgUWpOYqWhqV5iQUFOql5y fu4mRlBYNRSa7WDc8VfuEKMAB6MSD+8uaQ1/IdbEsuLK3EOMEhzMSiK8b1ar+QvxpiRWVqUW 5ccXleakFh9ilOZgURLn3Wqt7C8kkJ5YkpqdmlqQWgSTZeLglGpg3JrN78k35dSuj39WtT9O 1+v9Zbsu2d591T/pRyIbflblbJjunxxzxWWXzrdNS/a/FFQ68efXoV3HpmjzeU2rFAg/xxwU NmGm0Autqwv0FJTrvuwy9QsV5bL+kP3z7fNVnzMm1V+M6ano/hr+7W+55RFlZ9+seg33FwkW pbY5pSH2Pk8ixaLmKrEUZyQaajEXFScCAA/TAFsnAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] February 2012 F2F slides are now posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0768656168==" Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: B0F9179561.A93C9 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0768656168== Content-type: multipart/alternative; boundary="Boundary_(ID_s+wJI4DwubHIgAO7ascYqQ)" --Boundary_(ID_s+wJI4DwubHIgAO7ascYqQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the "final" F2F slides for next week to: ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-february-12.pdf Please let me know if you see any errors or omissions... __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_s+wJI4DwubHIgAO7ascYqQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All,

I have posted the "final" F2F slides for next week to:


Please let me know if you see any errors or omissions...

__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_s+wJI4DwubHIgAO7ascYqQ)-- --===============0768656168== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0768656168==--