From pwg-announce-bounces@pwg.org Tue Jun 4 10:17:08 2013 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 0832E21E8193 for ; Tue, 4 Jun 2013 10:17:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.854 X-Spam-Level: X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=-3.256, 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 OGy4EfYagw2k for ; Tue, 4 Jun 2013 10:17:01 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2716E21F9C68 for ; Tue, 4 Jun 2013 08:20:05 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id DD48D791CA; Tue, 4 Jun 2013 11:19:19 -0400 (EDT) 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.49]) by pwg.org (Postfix) with ESMTP id C812D791A6 for ; Tue, 4 Jun 2013 11:18:54 -0400 (EDT) MIME-version: 1.0 Received: from relay3.apple.com ([17.128.113.83]) 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 <0MNV00C3AJVB8YO0@mail-out.apple.com> for pwg-announce@pwg.org; Tue, 04 Jun 2013 08:18:53 -0700 (PDT) X-AuditID: 11807153-b7f3c6d000007b32-f5-51ae055c9860 Received: from [17.153.40.110] (Unknown_Domain [17.153.40.110]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id F4.14.31538.D550EA15; Tue, 04 Jun 2013 08:18:53 -0700 (PDT) From: Michael Sweet Date: Tue, 04 Jun 2013 11:18:52 -0400 To: "PWG Announcements Inc." Message-id: X-Mailer: Apple Mail (2.1503) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiOFMjTzeWdV2gwcGzphZHvsVarGtdzezA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZfw6/ou9YJpkxdTm28wNjNfEuhg5OSQETCR+ 3nrODGGLSVy4t56ti5GLQ0igl0ni395bYAk2ATWJ35P6WEFsZoEEifv7ZjN2MXJwsAioSFzb yA0SFhYwlniybRFYiQiQvaN9LxuIzStgI7HqxixGCFtP4tq3r+wQu2QlXj9/wzKBkXsWkqmz kJRBxLUlli18zTwLaBuzgI7E5IWMqMIQ9sfzR5gWMLKtYhQoSs1JrDTWSywoyEnVS87P3cQI CquGwuAdjH+WWR1iFOBgVOLhffBpbaAQa2JZcWXuIUYJDmYlEV7la0Ah3pTEyqrUovz4otKc 1OJDjNIcLErivEY2SwOFBNITS1KzU1MLUotgskwcnFINjIbpWz//rMgp4JIJWvRq3oQ8teWP d99k+rdM3NgyL55n7ovLWuEFDdI75cvlS+Rj90Q5uNw+qv9034O6Wxa81Wqu0fduP4zzXsqy 1EWnJehrQXns0x5P2aDS7xEa1n+jOVOM72264bPlcZP2kbMRxV8LCtf/k/myblbnOlvvcOlN fPlbuD0XKrEUZyQaajEXFScCAGAgfnonAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] Updated templates posted with new PWG logo 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="===============2040968500==" 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: DD48D791CA.AD0F8 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============2040968500== Content-type: multipart/alternative; boundary="Boundary_(ID_A71E/vgyWuLtgvlsZd3+XQ)" --Boundary_(ID_A71E/vgyWuLtgvlsZd3+XQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted updated Powerpoint, Keynote, and Word templates that use the new PWG logo to: ftp://ftp.pwg.org/pub/pwg/general/templates/f2f-template.key ftp://ftp.pwg.org/pub/pwg/general/templates/f2f-template.ppt ftp://ftp.pwg.org/pub/pwg/general/templates/wd-template.dot ftp://ftp.pwg.org/pub/pwg/general/templates/wd-template.dotx The working draft templates also include a new Exceptions section (3.3) based on our discussions at the May 2013 face-to-face. _________________________________________________________ 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_A71E/vgyWuLtgvlsZd3+XQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I= have posted updated Powerpoint, Keynote, and Word templates that use the n= ew PWG logo to:


The working draft templates also include a new Except= ions section (3.3) based on our discussions at the May 2013 face-to-face.

____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_A71E/vgyWuLtgvlsZd3+XQ)-- --===============2040968500== 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 --===============2040968500==-- From pwg-announce-bounces@pwg.org Tue Jun 4 14:38:29 2013 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 F099E21F918C for ; Tue, 4 Jun 2013 14:38:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 6E-6o7RKMTYC for ; Tue, 4 Jun 2013 14:38:24 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 025CF21F9BC8 for ; Tue, 4 Jun 2013 14:03:54 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D1A3F791FE; Tue, 4 Jun 2013 17:03:20 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by pwg.org (Postfix) with ESMTP id 7CA39791FE for ; Tue, 4 Jun 2013 17:02:56 -0400 (EDT) Received: by mail-ie0-f173.google.com with SMTP id k13so1622146iea.32 for ; Tue, 04 Jun 2013 14:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=D8uXBKO9BTJrlBGOkn0qORtck9HCeWrKgOWufSoP0rI=; b=M9lwN5uAQE5qAjycrJle+KKHGgTyWZPM8Z51jTx6ZvpVDgnEgX5aMfKe7vtm2bVdGB n0+NFDk9s4krsDbX5G+k/wD2Ur6B2rfpB6kGrPzjxqpi8PR1Qc57kJgCNUNDhC5VpE1h /1fR1C4tgAw8Bn4lyb8S/HyOye8nO5QP24Ggmtqvw7rZKbe0bmhW8Syy41DqwAEeBzeN 9egYqphThsB5q/5199Fuwx2FHrwtW1RCZu5Fh624d/V+6BjyqQH00xknFUfClyMR4Exj FRSzoILwAPKUKZDlZ8NtWvO1klZOS1MfLPv0t/trJ+qIQOvDNLjNqb42Nm3a+qyYwK7i pFNQ== MIME-Version: 1.0 X-Received: by 10.50.128.132 with SMTP id no4mr1933496igb.38.1370379776462; Tue, 04 Jun 2013 14:02:56 -0700 (PDT) Received: by 10.50.207.103 with HTTP; Tue, 4 Jun 2013 14:02:56 -0700 (PDT) Date: Tue, 4 Jun 2013 17:02:56 -0400 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] Fwd: IETF approves EMAN Requirements as Informational RFC 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="===============0817522513==" 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: D1A3F791FE.AD242 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0817522513== Content-Type: multipart/alternative; boundary=047d7b10cee1c8a49b04de5a674c --047d7b10cee1c8a49b04de5a674c Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: The IESG Date: Tue, Jun 4, 2013 at 10:01 AM Subject: [eman] Document Action: 'Requirements for Energy Management' to Informational RFC (draft-ietf-eman-requirements-14.txt) To: IETF-Announce Cc: eman mailing list , eman chair < eman-chairs@tools.ietf.org>, RFC Editor The IESG has approved the following document: - 'Requirements for Energy Management' (draft-ietf-eman-requirements-14.txt) as Informational RFC This document is the product of the Energy Management Working Group. The IESG contact persons are Joel Jaeggli and Benoit Claise. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-eman-requirements/ Technical Summary: This document defines requirements for standards specifications for energy management. These concern monitoring functions as well as control functions: Monitoring functions include identification of energy-managed devices and their components, monitoring of their power states, power inlets, power outlets, actual power, power properties, received energy, provided energy, and contained batteries. Control functions serve for controlling power supply and power state of energy-managed devices and their components. Working Group Summary: Version -08 of this draft was presented in the EMAN session at IETF 84 (Vancouver). The authors published -09, resolving the open issues discussed at that meeting. The draft's Working Group Last Call ran from 4 October to 22 October this year, and raised several more issues. After IETF-85, the authors published its -10 version; we believe it is now ready to submit to IESG. Document Quality: Are there existing implementations of the protocol? This is a requirements draft, not a protocol. Have a significant number of vendors indicated their plan to implement the specification? At least two vendors have implemented Energy Management systems, and - presumably - will make them EMAN-compliant. Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? Since September the following have contributed comments on the EMAN list: Ira McDonald, John Parello, Brad Schoening, Georgios Karagian. However, the draft's authors/editors have done most of the work in developing it. If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? The draft hasn't had any kind of expert review. Personnel: Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: Nevil Brownlee Area Director: Joel Jaeggli _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --047d7b10cee1c8a49b04de5a674c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



---------- Forwarded message ----------<= br>From: The IESG <<= a href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org>
Date: Tue, Jun 4, 2013 at 10:01 AM
Subject: [eman] Document Action: '= ;Requirements for Energy Management' to Informational RFC (draft-ietf-e= man-requirements-14.txt)
To: IETF-Announce <ietf-announce@ietf.org>
Cc: eman mailing list <eman@ietf.org>, eman chair <eman-ch= airs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>


The IESG has approved the following document:
- 'Requirements for Energy Management'
=A0 (draft-ietf-eman-requirements-14.txt) as Informational RFC

This document is the product of the Energy Management Working Group.

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-eman-requiremen= ts/




Technical Summary:

This document defines requirements for standards specifications for
energy management. =A0These concern monitoring functions as well as
control functions: Monitoring functions include identification of
energy-managed devices and their components, monitoring of their power
states, power inlets, power outlets, actual power, power properties,
received energy, provided energy, and contained batteries. =A0Control
functions serve for controlling power supply and power state of
energy-managed devices and their components.

Working Group Summary:

Version -08 of this draft was presented in the EMAN session at
IETF 84 (Vancouver). =A0The authors published -09, resolving the
open issues discussed at that meeting. =A0The draft's Working Group
Last Call ran from 4 October to 22 October this year, and raised
several more issues. =A0After IETF-85, the authors published its
-10 version; we believe it is now ready to submit to IESG.

Document Quality:

Are there existing implementations of the protocol?
=A0 This is a requirements draft, not a protocol.
Have a significant number of vendors indicated their plan to implement
the specification?
=A0 At least two vendors have implemented Energy Management systems,
=A0 and - presumably - will make them EMAN-compliant.
Are there any reviewers that merit special mention as having done a
thorough review, e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues?
=A0 Since September the following have contributed comments on the
=A0 EMAN list: =A0Ira McDonald, John Parello, Brad Schoening, Georgios
Karagian.
=A0 However, the draft's authors/editors have done most of the work
=A0 in developing it.
If there was a MIB Doctor, Media Type or other expert review, what was
its course (briefly)?
=A0 The draft hasn't had any kind of expert review.

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?
=A0 =A0Shepherd: =A0 =A0 =A0Nevil Brownlee
=A0 =A0Area Director: Joel Jaeggli


_______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --047d7b10cee1c8a49b04de5a674c-- --===============0817522513== 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 --===============0817522513==-- From ipp-bounces@pwg.org Fri Jun 7 17:47:56 2013 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 671EE21F99E0 for ; Fri, 7 Jun 2013 17:47:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[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 sPplhUhHcrqM for ; Fri, 7 Jun 2013 17:47:51 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB6221F89EB for ; Fri, 7 Jun 2013 17:47:50 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B3E597920B; Fri, 7 Jun 2013 20:47:14 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from edge.dda.kyocera.com (edge.dda.kyocera.com [69.42.25.201]) by pwg.org (Postfix) with ESMTP id B75E879206 for ; Fri, 7 Jun 2013 20:46:52 -0400 (EDT) Received: from LISA.ktd.com (10.10.10.75) by edge.dda.kyocera.com (69.42.25.201) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 7 Jun 2013 17:49:14 -0700 Received: from LISA.ktd.com ([10.10.10.75]) by lisa ([10.10.10.75]) with mapi id 14.01.0438.000; Fri, 7 Jun 2013 17:46:42 -0700 From: Lida Wang To: Michael Sweet , "ipp@pwg.org" , "blueroofmusic@gmail.com" , "ptykodi@tykodi.com" Thread-Topic: Kyocera Document Solution has reviewed the IPP FAXout specification and has the comments Thread-Index: Ac5j3zJlQS8CG4RsSzOgGInEB0kMLw== Date: Sat, 8 Jun 2013 00:46:41 +0000 Message-ID: <9E0A2C000B94894B8DCBA9E1354112DB1D9B9258@lisa> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.8.68] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Kyocera Document Solution has reviewed the IPP FAXout specification and has the comments 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="===============1778044781==" 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: B3E597920B.AA0E8 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1778044781== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_9E0A2C000B94894B8DCBA9E1354112DB1D9B9258lisa_" --_000_9E0A2C000B94894B8DCBA9E1354112DB1D9B9258lisa_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable All, The following are comments from Kyocera on IPP Faxout specification. =B7 Line 362. 4.1.4 Job History "IPP FaxOut Jobs MUST be retained f= or a minimum of 300 seconds." is actually difficult because of limitation of real memory capacity. A poss= ible alternative is "IPP FaxOut MUST retains for a minimum of xxx Jobs." =B7 Line 406 Table 2 - Required Printer Description Attributes number-of-retries-default PWG 5100.FAX number-of-retries-supported (note 6) PWG 5100.FAX This 2 items should not be included because there are individual upper limi= ts on retry number in each countries legally. For example, the following are from FCC68, line standard of North America: =A7 68.318 Additional limitations. (b) Registered terminal equipment with automatic dialing capability. (1) Au= tomatic dialing to any individual number is limited to two successive attem= pts. Automatic dialing equipment which employ means for detecting both busy= and reorder signals shall be permitted an additional 13 attempts if a busy= or reorder signal is encountered on each attempt. The dialer shall be unab= le to re-attempt a call to the same number for at least 60 minutes followin= g either the second or fifteenth successive attempt, whichever applies, unl= ess the dialer is reactivated by either manual or external means. This rule= does not apply to manually activated dialers that dial a number once follo= wing each activation. =B7 Line 406 Table 2 - Required Printer Description Attributes printer-fax-modem-info PWG 5100.FAX printer-fax-modem-name PWG 5100.FAX printer-fax-modem-number PWG 5100.FAX This 3 items seems to be unnecessary and should be deleted, No user needs t= o see this kind of modem info. =B7 Line 406 Table 2 - Required Printer Description Attributes retry-interval-default (note 6) PWG 5100.FAX retry-interval-supported (note 6) PWG 5100.FAX retry-timeout-default (note 6) PWG 5100.FAX retry-timeout-supported (note 6) PWG 5100.FAX This 3 items should not be included, Some countries assign a restriction fo= r automatic retry interval in consideration for avoiding the overload of th= eir switching devices. =B7 Line 656 7.2.6 retry-time-out (integer(1:MAX)) What is the difference between "7.2.6 retry-time-out (integer(1:MAX))" and = "7.2.5 retry-interval (integer(1:MAX))"? what is the reason both items are= needed? Best regards, Lida From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On= Behalf Of Michael Sweet Sent: Wednesday, May 01, 2013 11:42 AM To: PWG Announcements Inc. Subject: [Pwg-Announce] PWG Last Call of IPP FaxOut Service (05/01/13 to 06= /07/13) All, [This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June= 7, 2013 at 10pm US PST.] This is the formal announcement of the PWG Last Call for the IPP FaxOut Ser= vice specification, located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf All required attributes and values defined in this document have been proto= typed by Apple and/or other vendors. The IPP WG has completed extensive rev= iew of the various revisions of this document and an IPP WG 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 documen= t can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote= but it DOES require your review acknowledgment. HOW TO RESPOND Send an email with *exactly* the following subject line format: Subject: has reviewed the IPP FaxOut specification and has [= no] comments WHERE TO SEND YOUR RESPONSE Please send your response to *all* of the following email addresses (replac= ing "dot" with '.' and "at" with '@'): ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!) blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP FaxOut= Editor) Note that you must be subscribed to the IPP WG mailing list to send email t= here - otherwise your email will be silently discarded. 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 i= s 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. --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_9E0A2C000B94894B8DCBA9E1354112DB1D9B9258lisa_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

All,

 <= /p>

The following are comment= s from Kyocera on IPP Faxout specification.

 <= /p>

=B7      &nbs= p;  Line 362. 4.1.4 J= ob History "IPP FaxOut Jobs MUST be retained for a minimum of 300 seco= nds."

 <= /p>

=B7      &nbs= p;  Line 406 Table 2 = - Required Printer Description Attributes

=B7      &nbs= p;  Line 406 Table 2 = - Required Printer Description Attributes

=B7      &nbs= p;  Line 406 Table 2 = - Required Printer Description Attributes

 <= /p>

=B7      &nbs= p;  Line 656 7.2.6 re= try-time-out (integer(1:MAX))

 <= /p>

Best regards,<= /span>

Lida

 <= /p>

From: pwg-anno= unce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, May 01, 2013 11:42 AM
To: PWG Announcements Inc.
Subject: [Pwg-Announce] PWG Last Call of IPP FaxOut Service (05/01/1= 3 to 06/07/13)

 

All,

[This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June= 7, 2013 at 10pm US PST.]

This is the formal announcement of the PWG Last Call for the IPP FaxOut Ser= vice specification, located at:

       &n= bsp;    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10= -20130501.pdf

All required attributes and values defined in this document have been proto= typed by Apple and/or other vendors. The IPP WG has completed extensiv= e review of the various revisions of this document and an IPP WG 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 do= cument can progress to PWG Formal Vote.  This PWG Last Call is NO= T a Formal Vote but it DOES require your review acknowledgment.


HOW TO RESPOND

Send an email with *exactly* the following subject line format:
Subject: <Company Name> has reviewed the IPP FaxOut specification and= has [no] comments


WHERE TO SEND YOUR RESPONSE

Please send your response to *all* of the following email addresses (replac= ing "dot" with '.' and "at" with '@'):

ipp "at" pwg "dot" org (IPP WG mailing list - you must = be subscribed!)
blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP W= G Co-Chair)
ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-C= hair)
msweet "at" apple "dot" com (Michael Sweet, IPP WG Secr= etary and IPP FaxOut Editor)

Note that you must be subscribed to the IPP WG mailing list to send email t= here - otherwise your email will be silently discarded.

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 i= s located at:

       &n= bsp;    http://www.pwg.org/chair/membership_docs/pwg-proc= ess30.pdf

____________________________________________________= _____
Michael Sweet, Senior Printing System Engineer, PWG Chair



--
This message has been scanned for viruses and
dangerous content by MailScanne= r, 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. --_000_9E0A2C000B94894B8DCBA9E1354112DB1D9B9258lisa_-- --===============1778044781== 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 --===============1778044781==-- From ipp-bounces@pwg.org Sun Jun 9 17:39:55 2013 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 A694821F8900 for ; Sun, 9 Jun 2013 17:39:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.184 X-Spam-Level: X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[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 2Q+NckmsAIDb for ; Sun, 9 Jun 2013 17:39:51 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2909821F8DDD for ; Sun, 9 Jun 2013 17:39:50 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 95F287919C; Sun, 9 Jun 2013 20:39:18 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) by pwg.org (Postfix) with ESMTP id 7193A79199 for ; Sun, 9 Jun 2013 20:38:55 -0400 (EDT) Received: by mail-ie0-f177.google.com with SMTP id u16so14246202iet.8 for ; Sun, 09 Jun 2013 17:38:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=z36Mmidib+khhrEL6rmIUbNvCZAOQp9Ia0WLNjZyKSg=; b=esjcpt6pAMg2F8zUKq3S1/DlbeBWxLTraLhaj3I6kE1oxfXLGFo2K5CFMs97qk9i5W HuSMWpaI/WdFLDtL/QMz554QLhCqpxhCw/t6A29DnU3G1obIgjB/S2Gis0f743zD583s xn1qsGRrGPz6UpFA6HlaKqnXJLFlVJpfASGtVRcnv2q8pvGNcXLu80AOlF+IFhB8WLxp uACIjUNhflJW69vaX/kos0ZkNA8UoJTEB3Fa4sJhCmshhmMGMV76N3Q4TJYE7Fcowtok yOTtjekgWJ8mtXH1RMfEB4Ao+D9xNTjFFWum0BSsFj1ohsOWZwbRhAvNN5FSKKeIZNnx xGxA== MIME-Version: 1.0 X-Received: by 10.50.128.132 with SMTP id no4mr3097248igb.38.1370824734649; Sun, 09 Jun 2013 17:38:54 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Sun, 9 Jun 2013 17:38:54 -0700 (PDT) Date: Sun, 9 Jun 2013 20:38:54 -0400 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] IPP Agenda - 3-5pm EDT 10 June 2013 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="===============1975654332==" 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: 95F287919C.A9BA4 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1975654332== Content-Type: multipart/alternative; boundary=047d7b10cee15bb22d04dec201e2 --047d7b10cee15bb22d04dec201e2 Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call is this week Monday 10 June 12-2pm US Pacific / 3-5pm US Eastern 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) ------------------------------------------------------- Meeting information ------------------------------------------------------- Date: Every Monday, from Monday, July 9, 2012 to no end date Time: 12:00 pm, Pacific Daylight Time (San Francisco) Meeting Number: 624 587 312 Meeting Password: pwg123 ------------------------------------------------------- To start or join the online meeting ------------------------------------------------------- Go to https://appleinc.webex.com/appleinc/j.php?ED=204995427&UID=504472682&PW=NNzM5MmRlMzBl&RT=MiM0 ------------------------------------------------------- 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-20130516.pdf (3) Status of IPP Paid Printing Extensions (Mike) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipppaid10-20130501-rev.pdf - Apple prototype report posted (4) Status of IPP Fax Out (Mike) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf - PWG Last Call - ended 7 June - quorum not achieved - extend PWG LC? (5) Status of IPP Shared Infrastructure Extensions (Mike) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130328.pdf - model issues from Cloud WG? (6) Next steps - IPP WG telecon on Monday 24 June - IPP WG telecon on Monday 8 July 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. --047d7b10cee15bb22d04dec201e2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
Our next IPP WG call is this week Monday 10 Ju= ne 12-2pm US Pacific / 3-5pm US Eastern

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 Ac= cess Code: *******#
Attendee ID Code: # (empty)

-----------------= --------------------------------------
Meeting information
----------= ---------------------------------------------
Date: Every Monday, from Monday, July 9, 2012 to no end date
Time: 12:00= pm, Pacific Daylight Time (San Francisco)
Meeting Number: 624 587 312Meeting Password: pwg123
---------------------------------------------= ----------
To start or join the online meeting
------------------------------------= -------------------
Go to https://appleinc.webex.com/appleinc/j.php?ED=3D204995427&UID=3D504= 472682&PW=3DNNzM5MmRlMzBl&RT=3DMiM0
-------------------------------------------------------
Agenda:
(1) P= WG IP Policy and Minute Taker
- Mike

(2) Approve IPP minutes from= previous meeting
- ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ip= pv2-f2f-minutes-20130516.pdf

(3) Status of IPP Paid Printing Extensions (Mike)
- ftp://ftp.pwg.or= g/pub/pwg/ipp/wd/wd-ipppaid10-20130501-rev.pdf
- Apple prototype rep= ort posted

(4) Status of IPP Fax Out (Mike)
- ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf
- PWG Last Call - ended 7 June - quorum not achieved
- e= xtend PWG LC?

(5) Status of IPP Shared Infrast= ructure Extensions (Mike)
- model issues from Cloud WG?

(6) Next steps- IPP WG telecon on Monday 24 June
- IPP WG telecon on Mond= ay 8 July

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Op= en 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. --047d7b10cee15bb22d04dec201e2-- --===============1975654332== 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 --===============1975654332==-- From pwg-announce-bounces@pwg.org Mon Jun 10 12:36:43 2013 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 7C1FC21F9A44 for ; Mon, 10 Jun 2013 12:36:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 ipm2F8pt56Cr for ; Mon, 10 Jun 2013 12:36:37 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDE721F9AE7 for ; Mon, 10 Jun 2013 12:36:37 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 087F0791A5; Mon, 10 Jun 2013 15:36:07 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 225C07919E for ; Mon, 10 Jun 2013 15:35:43 -0400 (EDT) MIME-version: 1.0 Received: from relay7.apple.com ([17.128.113.101]) 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 <0MO600L85ZQX4L51@mail-out.apple.com> for pwg-announce@pwg.org; Mon, 10 Jun 2013 12:35:42 -0700 (PDT) X-AuditID: 11807165-b7f496d000000613-fb-51b62a8ce6f5 Received: from [17.153.43.157] (Unknown_Domain [17.153.43.157]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay7.apple.com (Apple SCV relay) with SMTP id 0F.E0.01555.D8A26B15; Mon, 10 Jun 2013 12:35:42 -0700 (PDT) From: Michael Sweet In-reply-to: <591A6DAC-036E-459F-A78E-AE75EDADCC59@apple.com> Date: Mon, 10 Jun 2013 15:35:38 -0400 Message-id: References: <591A6DAC-036E-459F-A78E-AE75EDADCC59@apple.com> To: "PWG Announcements Inc." X-Mailer: Apple Mail (2.1763) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUiOFN7rm6f1rZAg+M/DC2OfIu1WNe6mtmB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgytg/7SJTwWW3innfLrI3MN6y6WLk5JAQMJG4 27yfGcIWk7hwbz1bFyMXh5BAL5PEjk/X2EESzAIJEnOvvgGzeQX0JH7/WQhmCwv4Sqy4/oYJ xGYTUJP4PamPFcTmFLCVaD65EizOIqAq0fjtGFA9B1CvjcSaHYYgYSEg88nW+WwgtoiAocSl Hw3sEDfISkx79JN5AiPvLCSbZyHZDBHXlli28DXzLKCpzAI6EpMXMqIKQ9gfzx9hWsDItopR oCg1J7HSXC+xoCAnVS85P3cTIygMGwpTdzA2Lrc6xCjAwajEw5vAuC1QiDWxrLgy9xCjBAez kgjvVyWgEG9KYmVValF+fFFpTmrxIUZpDhYlcd6owk2BQgLpiSWp2ampBalFMFkmDk6pBsZY c7sTBSqPTLZvsbY5vrhh+zuRftZbkTxMZv4ntD85rI+e2Kb7c2NZxZTpCz78Tb2W9Na/hXFD a8TLc2EpfxMzDizSZSl/3s1Qk3h7/lERY+nvS+9aPpnKPut3u/eJCwn34qTyZRJ2CKb6v65+ fj6k6d7fJ4E8n3O3LPB1y/nf8KF72vpk81YlluKMREMt5qLiRAC13RnkPwIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] EXTENDED: PWG Last Call of IPP FaxOut Service (05/01/13 to 06/28/13) 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="===============0350515202==" 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: 087F0791A5.AE217 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0350515202== Content-type: multipart/alternative; boundary="Boundary_(ID_xmL3ilLKZhyVHeLT1UM9Rg)" --Boundary_(ID_xmL3ilLKZhyVHeLT1UM9Rg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, Because we have not yet reached quorum, we need to extend the PWG Last Call of the IPP FaxOut Service specification to Friday, June 28, 2013 at 10pm US PT. Thank you everyone that has already responded to the last call. If you have not yet provided your acknowledgement for the IPP FaxOut Service specification, please do so at your earliest convenience. Thank you! On May 1, 2013, at 2:41 PM, Michael Sweet wrote: > All, > > [This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June 7, 2013 at 10pm US PST.] > > This is the formal announcement of the PWG Last Call for the IPP FaxOut Service specification, located at: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.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 an IPP WG 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. > > > HOW TO RESPOND > > Send an email with *exactly* the following subject line format: > Subject: has reviewed the IPP FaxOut specification and has [no] comments > > > WHERE TO SEND YOUR RESPONSE > > Please send your response to *all* of the following email addresses (replacing "dot" with '.' and "at" with '@'): > > ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!) > blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) > ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) > msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP FaxOut Editor) > > Note that you must be subscribed to the IPP WG mailing list to send email there - otherwise your email will be silently discarded. > > 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 _________________________________________________________ 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_xmL3ilLKZhyVHeLT1UM9Rg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

Be= cause we have not yet reached quorum, we need to extend the PWG Last Call o= f the IPP FaxOut Service specification to Friday, June 28, 2013 at 10pm US = PT.

Thank you everyone that has already responded = to the last call.  If you have not yet provided your acknowledgement f= or the IPP FaxOut Service specification, please do so at your earliest conv= enience.

Thank you!


<= div>
On May 1, 2013, at 2:41 PM, Michael Sweet <msweet@apple.com> wrote:

Al= l,

[This PWG Last Call starts today Wednesday May 1, 2013 and ends F= riday June 7, 2013 at 10pm US PST.]

This is the formal announce= ment of the PWG Last Call for the IPP FaxOut Service specification, lo= cated at:

= ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf
All required attributes and values defined in this document have been pro= totyped by Apple and/or other vendors. The IPP WG has completed extens= ive review of the various revisions of this document and an IPP WG las= t call.

The PWG Process/3.0 requires that a quorum (30%) of PWG voti= ng 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 acknowl= edgment.


HOW TO RESPOND

Send an email with *exactly* the = following subject line format:
Subject: <Company Name> has reviewe= d the IPP FaxOut specification and has [no] comments


WHERE TO SE= ND YOUR RESPONSE

Please send your response to *all* of the following= email addresses (replacing "dot" with '.' and "at" with '@'):

= ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!)
b= lueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair)
ptykod= i "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair)
msweet "at" apple= "dot" com (Michael Sweet, IPP WG Secretary and IPP FaxOut Editor)

N= ote that you must be subscribed to the IPP WG mailing list to send email th= ere - otherwise your email will be silently discarded.

Please d= o 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:

htt= p://www.pwg.org/chair/membership_docs/pwg-process30.pdf

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
pwg-announce mailing lis= t
pwg-announce@pwg.org
ht= tps://www.pwg.org/mailman/listinfo/pwg-announce

<= div>
____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_xmL3ilLKZhyVHeLT1UM9Rg)-- --===============0350515202== 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 --===============0350515202==-- From ipp-bounces@pwg.org Mon Jun 10 12:40:40 2013 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 5F04821F9A5C for ; Mon, 10 Jun 2013 12:40:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599] 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 MOmk0bMRVW4P for ; Mon, 10 Jun 2013 12:40:34 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB9121F9A57 for ; Mon, 10 Jun 2013 12:40:34 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E2271791CD; Mon, 10 Jun 2013 15:39:54 -0400 (EDT) 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 43722791A8 for ; Mon, 10 Jun 2013 15:39:30 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay7.apple.com ([17.128.113.101]) 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 <0MO600DORZXRDZK0@mail-out.apple.com> for ipp@pwg.org; Mon, 10 Jun 2013 12:39:30 -0700 (PDT) X-AuditID: 11807165-b7f496d000000613-64-51b62b6f498c Received: from [17.153.43.157] (Unknown_Domain [17.153.43.157]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay7.apple.com (Apple SCV relay) with SMTP id 4B.62.01555.07B26B15; Mon, 10 Jun 2013 12:39:29 -0700 (PDT) From: Michael Sweet Date: Mon, 10 Jun 2013 15:39:27 -0400 To: ipp@pwg.org, Michael Sweet , Paul Tykodi , Ira Mcdonald Message-id: <63716BD0-E082-493E-BA80-82E1A492A641@apple.com> X-Mailer: Apple Mail (2.1763) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42IRnKk9V7dQe1ugwf4LFhavXy1ltzi27yWL xZFvsRad36wdWDy2nvzB5rFz1l12j3mLpzN5bL7ynCWAJYrLJiU1J7MstUjfLoEr40bXK7aC ior2SVeZGhizuxg5OSQETCSmfrnIAmGLSVy4t54NxBYS6GWSmDNTHsRmE1CT+D2pjxXEZhbQ krjx7yUThC0vsf3tHGYQm0VAVWJh12dGEFtYwEfix5P9QDYXh4hAI6PE/V33gIo4OHgFbCQ+ zXQBqeEV0JP4/WchO8ReWYlpj34yT2DkmYVkxSwkK2YhaVnAyLyKUaAoNSex0lwvsaAgJ1Uv OT93EyMolBoKU3cwNi63OsQowMGoxMObwLgtUIg1say4MvcQowQHs5II71cloBBvSmJlVWpR fnxRaU5q8SFGaQ4WJXHeqMJNgUIC6YklqdmpqQWpRTBZJg5OqQbGE02H1vOm9fcl2fx8abmn T17b0PtE7eZQhmUdB+V67+WnHD0/d07jhGh1iXAZuTrl63IezsIFJculFuwNfRN2m+trgfVj L5U5LfdNFh9ylw/yKVzT237m6NkW2YNHnk0POW2289/zf93bLvF9vDHv8LINCzkfV+/pvJQT IvNudX+mfNtD969WSizFGYmGWsxFxYkA4t/wfiECAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has no comments 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: E2271791CD.A8E70 X-pwg-MailScanner-From: ipp-bounces@pwg.org _________________________________________________________ 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 ipp-bounces@pwg.org Mon Jun 10 13:09:53 2013 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 2F1F221F8616 for ; Mon, 10 Jun 2013 13:09:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] 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 T7biumJ0jX7X for ; Mon, 10 Jun 2013 13:09:47 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 48C7721F96E4 for ; Mon, 10 Jun 2013 13:09:47 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2B041791D0; Mon, 10 Jun 2013 16:09:05 -0400 (EDT) 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 008D3791CF for ; Mon, 10 Jun 2013 16:08:38 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay3.apple.com ([17.128.113.83]) 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 <0MO700DX519SDZM0@mail-out.apple.com> for ipp@pwg.org; Mon, 10 Jun 2013 13:08:38 -0700 (PDT) X-AuditID: 11807153-b7f3c6d000007b32-63-51b632439a9e Received: from [17.153.43.157] (Unknown_Domain [17.153.43.157]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 60.03.31538.54236B15; Mon, 10 Jun 2013 13:08:38 -0700 (PDT) From: Michael Sweet Date: Mon, 10 Jun 2013 16:08:34 -0400 To: ipp@pwg.org Message-id: X-Mailer: Apple Mail (2.1763) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLJMWRmVeSWpSXmKPExsUiOFN7rq6b0bZAg12bhSyO7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAldH3/yVTwXqWii3tnWwNjCeZuxg5OSQETCT+ L53ABGGLSVy4t56ti5GLQ0igl0nix9weNpAEm4CaxO9JfawgNrOAlsSNfy+ZIGx5ie1v5wAN 4uBgEVCV2HfTDCQsLGAg8bV9L1iJiAC/xMSLEK28AjYSvw+sYoew9SR+/1nIDrFXVmLao5/M Exh5ZiHZMAvJhllIWhYwMq9iFChKzUmsNNZLLCjISdVLzs/dxAgKlIbC4B2Mf5ZZHWIU4GBU 4uFNZNwWKMSaWFZcmXuIUYKDWUmE96sSUIg3JbGyKrUoP76oNCe1+BCjNAeLkjhvZOGmQCGB 9MSS1OzU1ILUIpgsEwenVANjWGjoHWPR5e+XJywLOOo07/0Hm+e7++6JHn35Mux/YkXTg/kP 0z59O3FaRGvfwzsXS+ezKvDWrPvy4LnupG05x7/m/do383fP8k33vijxno0MPP5dabmxZ0qG bPgHNw4X597m+067ZvYWNTFM3r+5Nm7iKXMJzf1s3sVGfdkbD2tdOPd9XefMM0osxRmJhlrM RcWJABVB+coQAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's IPP concall 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: 2B041791D0.A95E4 X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted the minutes from today's IPP WG conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20130610.pdf Our next conference call is June 24, 2013 at 3pm ET. New action items: - Paul to post summary of finishing-template investigation to IPP WG list - Mike to issue PWG Last Call of IPP Paid Printing Extensions - Mike to extend IPP FaxOut Service Last Call to June 28 (DONE) _________________________________________________________ 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 ipp-bounces@pwg.org Mon Jun 10 13:13:01 2013 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 CD20621F9A24 for ; Mon, 10 Jun 2013 13:13:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.391 X-Spam-Level: X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=1.207, 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 cr9Af4ZrSvZP for ; Mon, 10 Jun 2013 13:12:56 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 33EB421F9A29 for ; Mon, 10 Jun 2013 13:12:55 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CCA7D791D8; Mon, 10 Jun 2013 16:12:20 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by pwg.org (Postfix) with ESMTP id D15ED791E2 for ; Mon, 10 Jun 2013 16:11:57 -0400 (EDT) Received: by mail-ie0-f174.google.com with SMTP id 9so2149909iec.19 for ; Mon, 10 Jun 2013 13:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=dC0HgzSrnP7KXtrNocGgoaZS/zpbNQQ2wkws3kDEoFU=; b=vNe/ACQlv7jnz1BjeaCn/NwWXbr/kvQL01yVrekZGBALmIDJlPabdLinOgk/QwSwa0 wgirem4WwBKdO5jt7UvOr5vBtzDvolxNu6Nkx8L8gFAAQmiCVrlbf6pitQk762cCiseb z8+Gi2MUl0G27f6kfsP3ECKYW9arj/UHwncyPt1HvS++Hl7nzzfEN7cg92EJz6utqNyx tyjbSA+dJMeKh/Mx0x+AGYiQBoICvHNo5nlF7lo9Yd5fMkjozuqw3Qok9IasrHWj4FnN yW87r74PrWPjfDHqidnPs7ccHIQ3AcRcndjzIkhSKFkkVKfNJwb9QIWIT+EM87FG7xEO 2FJA== MIME-Version: 1.0 X-Received: by 10.42.79.205 with SMTP id s13mr4449882ick.41.1370895117326; Mon, 10 Jun 2013 13:11:57 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Mon, 10 Jun 2013 13:11:57 -0700 (PDT) Date: Mon, 10 Jun 2013 16:11:57 -0400 Message-ID: From: Ira McDonald To: "ipp@pwg.org" , Paul Tykodi , Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] High North has reviewed the IPP FaxOut specification and has no comments 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="===============0475385828==" 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: CCA7D791D8.A869E X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0475385828== Content-Type: multipart/alternative; boundary=20cf3011e3457e228f04ded2646b --20cf3011e3457e228f04ded2646b Content-Type: text/plain; charset=ISO-8859-1 Hi, No comments - good job Mike! 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. --20cf3011e3457e228f04ded2646b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

No comments - good job Mik= e!

Cheers,
- Ira

=
Ira McDonald (Musician / Software Architect)
Chair - Linux Fou= ndation 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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --20cf3011e3457e228f04ded2646b-- --===============0475385828== 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 --===============0475385828==-- From ipp-bounces@pwg.org Mon Jun 10 14:48:23 2013 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 5E1C321F95D7 for ; Mon, 10 Jun 2013 14:48:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 151NYYQZVngF for ; Mon, 10 Jun 2013 14:48:17 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC3D21F9A94 for ; Mon, 10 Jun 2013 14:48:17 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C72BC791E4; Mon, 10 Jun 2013 17:47:42 -0400 (EDT) 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 A362F791DC for ; Mon, 10 Jun 2013 17:47:18 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 10 Jun 2013 14:47:17 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 10 Jun 2013 14:47:17 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comments and Idea for paid printing Thread-Index: Ac5mJBNTdLSBCvPgQ6iFBOJzbo96NA== From: "Petrie, Glen" To: X-OriginalArrivalTime: 10 Jun 2013 21:47:17.0463 (UTC) FILETIME=[13A30670:01CE6624] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Comments and Idea for paid printing 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="===============1929361179==" 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: C72BC791E4.A88E4 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1929361179== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE6624.1377753E" This is a multi-part message in MIME format. ------_=_NextPart_001_01CE6624.1377753E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello As with the IPP FaxOut, I have unable to review the IPP Paid Printing docum= ent until now. Overall, I was concerned that "Extension for Paid Printing" is being extend= ed through 'finishings" while the concept of "paid-printing" is a business = or commerce notion and not a finishing step. While I need to study the doc= ument in more detail; how does the current paid-printing model support a pr= int job where a set of differently priced transform service are needed.=20= =20 Having recently reviewed the PrintTalk specification of JDF; this is an int= eresting model to explore for PWG (independent of just IPP) "paid-prinitng"= for several reason. Instead of modifying/extending JDF, PrintTalk wraps = JDF in a business transaction or commerce transaction. With it's relative= ly simple set API calls it supports very complex set of operations ranging = from Quoting, Notations, etc.; again with out modification to the print job= JDF. PrintTalk can itemize items and provide a quote for each item. And,= finally, PrintTalk is already widely used and deployed. PWG could creat= e a version of PrintTalk, called IppPrintTalk (or PrintTalkIpp or PrintTalk= Pwg) by simply replacing JDF with PWG (or IPP) in the existing PrintTalk sp= ecification. Now IPP stays the same while extending an existing "paid pri= nting" API and implementations which could be applied to any PWG model (Clo= ud?) Other comments on the specification itself The attribute "printer-charge-info-uri" is not defined in this document (pe= rhaps somewhere else). But my concern that a discussion about how a User i= s associated with a paid (payment) service is out-of-scope. Section 4.2 PIN/Passcode Printing Section 4.3 Release Printing I believe these sections are out-of-scope for paid-printing since there= is not "payment" requirement for these types of printing functionalities. Section 4.5 Job Review I believe this section is out-of-scope for paid-printing. "Job Review"= could be applied to any print scenario and not specific relevance to paid-= printing. In fact, if a User submits a print job for (100,000 copies) and= payment is confirmed; then print the 100,000 copies.=20=20=20 (Mike I assume specification are written to American English notation so 10= 0.000 should be 100,000?) glen --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CE6624.1377753E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comments and Idea for paid printing

Hello

As with the IPP FaxOut, I have unable to review the IPP Paid Printing docum= ent until now.

Overall, I was concerned that "Extension for Paid Printing" is be= ing extended through 'finishings" while the concept of "paid-prin= ting" is a business or commerce notion and not a finishing step. = While I need to study the document in more detail; how does the current pa= id-printing model support a print job where a set of differently priced tra= nsform service are needed. 

Having recently reviewed the PrintTalk specification of JDF; this is an int= eresting model to explore for PWG (independent of just IPP) "paid-prin= itng" for several reason.   Instead of modifying/extending J= DF, PrintTalk wraps JDF in a business transaction or commerce transaction.&= nbsp;  With it's relatively simple set API calls it supports very comp= lex set of operations ranging from Quoting, Notations, etc.; again with out= modification to the print job JDF.  PrintTalk can itemize items and p= rovide a quote for each item.  And, finally, PrintTalk is already wide= ly used and deployed.    PWG could create a version of Print= Talk, called IppPrintTalk (or PrintTalkIpp or PrintTalkPwg) by simply repla= cing JDF with PWG (or IPP) in the existing PrintTalk specification. &n= bsp; Now IPP stays the same while extending an existing "paid printing= " API and implementations which could be applied to any PWG model (Clo= ud?)

Other comments on the specification itself

The attribute "printer-charge-info-uri" is not defined in this do= cument (perhaps somewhere else).  But my concern that a discussion abo= ut how a User is associated with a paid (payment) service is out-of-scope.<= BR>

Section 4.2 PIN/Passcode Printing
Section 4.3 Release Printing
    I believe these sections are out-of-scope for paid-print= ing since there is not "payment" requirement for these types of p= rinting functionalities.

Section 4.5 Job Review
    I believe this section is out-of-scope for paid-printing= .  "Job Review" could be applied to any print scenario and n= ot specific relevance to paid-printing.   In fact, if a User subm= its a print job for (100,000 copies) and payment is confirmed; then print t= he 100,000 copies.  

(Mike I assume specification are written to American English notation so 10= 0.000 should be 100,000?)

 glen




--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CE6624.1377753E-- --===============1929361179== 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 --===============1929361179==-- From ipp-bounces@pwg.org Thu Jun 20 13:16:40 2013 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 D301321F9FA2 for ; Thu, 20 Jun 2013 13:16:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[AWL=-1.600, 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 eIYyy3v4u0k4 for ; Thu, 20 Jun 2013 13:16:35 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 09AF921F9FA1 for ; Thu, 20 Jun 2013 13:16:34 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 48E2D791D3; Thu, 20 Jun 2013 16:15:57 -0400 (EDT) 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 A2D7C791D1 for ; Thu, 20 Jun 2013 16:15:31 -0400 (EDT) MIME-version: 1.0 Received: from relay8.apple.com ([17.128.113.102]) 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 <0MOP00IMIK9G58Q0@mail-out.apple.com> for ipp@pwg.org; Thu, 20 Jun 2013 13:15:31 -0700 (PDT) X-AuditID: 11807166-b7faa6d000003acb-8a-51c362e0070b Received: from [17.153.17.37] (Unknown_Domain [17.153.17.37]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay8.apple.com (Apple SCV relay) with SMTP id 16.8E.15051.1E263C15; Thu, 20 Jun 2013 13:15:30 -0700 (PDT) Subject: Re: [IPP] Comments and Idea for paid printing From: Michael Sweet In-reply-to: Date: Thu, 20 Jun 2013 16:15:26 -0400 Message-id: <8C05122D-8073-4862-93CB-CD1AA8679EAC@apple.com> References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1764) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUiOFNQVfdR0uFAg1vftS22n/3FYnFs30sW iyPfYh2YPbae/MHmcXD+LHaPeYunMwUwR3HZpKTmZJalFunbJXBlnN30hb3gxATGiv+vn7A3 MH6u6GLk5JAQMJE4MXcvK4QtJnHh3nq2LkYuDiGBbiaJWS1PgBIcHMICZhILzquB1PAK6Els W3iAHcRmFkiQ+L/mMxuIzSagJvF7Uh/YHE4BL4kDX/4xgdgsAqoSqw+/Z4Oo55c42PuBGWQk r4CNxO3jJiBhIQFPiY4ra8DKRQT0JT593MwEcY6sxMS+a4wTGPlmIdk8C8lmCFtbYtnC18wQ tp7Ey6Z37JjiuhIX101iXMDItopRoCg1J7HSQi+xoCAnVS85P3cTIyhoGwrTdjA2Lbc6xCjA wajEwxugdDhQiDWxrLgy9xCjBAezkgjvo2CgEG9KYmVValF+fFFpTmrxIUZpDhYlcd7Nrw4G CgmkJ5akZqemFqQWwWSZODilGhjnT/kRvyZc9GZk94c1jfq17h5BCYd2nd9968/cz/7BU7Oz zlf29Syzmum+x0fqw52IJ2+22+1VeFhSOkX/hnefuf+kSetLXRYW6JpPTV+3jq1lnXKewsPQ 9GUb/x3Idjur0drO9c6o/9CtBeGCUbJy/z4d1Bb+vvq10MEvX5YXZMfXXaz9kjJXiaU4I9FQ i7moOBEAZcBFu1YCAAA= 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="===============0318673630==" 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: 48E2D791D3.AAC2E X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0318673630== Content-type: multipart/alternative; boundary="Boundary_(ID_FSby5OLG8agK0WaPc9wnXQ)" --Boundary_(ID_FSby5OLG8agK0WaPc9wnXQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Glen, On Jun 10, 2013, at 5:47 PM, "Petrie, Glen" wrote: > Hello > > As with the IPP FaxOut, I have unable to review the IPP Paid Printing document until now. > > Overall, I was concerned that "Extension for Paid Printing" is being extended through 'finishings" while the concept of "paid-printing" is a business or commerce notion and not a finishing step. > Well, no. While I did dump some additional finishing values in there since they are generally needed when specifying print intent to a third-party print service, they aren't the focus and I have no problem pulling those out and introducing them with the additions for the finishings-col attribute. The core meat of the spec is in defining a simple transactional model for printing. The transactions may be for money, for internal accounting/metrics, for output tracking. Perhaps the name should be "IPP Transactional Printing Extensions", but we aren't just talking print-for-cash here. The rest is supporting material to ensure that common use cases can be satisfied. > While I need to study the document in more detail; how does the current paid-printing model support a print job where a set of differently priced transform service are needed. > The extensions don't expose the itemized pricing, but rather address a more general "I want to print X, here are my credentials, please pre-approve me". As in prior trips down this path, we are avoiding any notion of describing currency, pricing, or billing, but instead are focusing on the transaction itself: how can a client say "I want to do the following work", get back an authorization for that work (generally tied to the supplied job ticket and document format in some way, e.g., a hash), and then submit a job and documents associated with that authorization? > Having recently reviewed the PrintTalk specification of JDF; this is an interesting model to explore for PWG (independent of just IPP) "paid-prinitng" for several reason. Instead of modifying/extending JDF, PrintTalk wraps JDF in a business transaction or commerce transaction. With it's relatively simple set API calls it supports very complex set of operations ranging from Quoting, Notations, etc.; again with out modification to the print job JDF. PrintTalk can itemize items and provide a quote for each item. And, finally, PrintTalk is already widely used and deployed. > This is interesting for a number of reasons; first, until you mentioned it I had never heard of PrintTalk - if it is widely implemented and supported, there is very little mention of it online (I see a bunch of press releases in 2003 and 2004, and possibly one company - PrintTalk Ltd) and nobody (that I can find) selling or developing PrintTalk-based solutions. I also found this article: http://www.piworld.com/article/in-search-printtalk-jdf-mcilroy-18362/1 I'm happy to be wrong here, but so far I'm not sold on PrintTalk. But moreover, in looking at the specification it is far beyond the scope of anything we have ever wanted to do, collectively, for paid printing services. It deals with currencies and itemized costs. It passes around credit card information and other payment information. And it looks to be a fairly complicated service of its own separate from the actual print service. That said, the basics of the RFQ/Quote and PurchaseOrder/Invoice pairs match the model outlined in the IPP Paid Printing Extensions, and in fact an IPP Printer *could* very easily map the IPP Job Ticket, user, and authorization information to PrintTalk transactions. But that would be an implementation detail that I would not want to enforce in this document. > PWG could create a version of PrintTalk, called IppPrintTalk (or PrintTalkIpp or PrintTalkPwg) by simply replacing JDF with PWG (or IPP) in the existing PrintTalk specification. Now IPP stays the same while extending an existing "paid printing" API and implementations which could be applied to any PWG model (Cloud?) > Except that we don't have the data types for currencies, don't have the security model for handling credit cards, and IMHO don't want to limit ourselves to the cash-based reprographic work order process that PrintTalk appears to be based on. > Other comments on the specification itself > > The attribute "printer-charge-info-uri" is not defined in this document (perhaps somewhere else). But my concern that a discussion about how a User is associated with a paid (payment) service is out-of-scope. > printer-charge-info-uri was defined in JPS3. It and printer-charge-info tell the Client that the Printer is not "free" (for some value or definition of "free"). As for not associating a User with a payment service, that is what the job-authorization-uri is for. It identifies the pairing of the user to a job ticket and document (format). The Client gets an authorization URI by sending a Validate-Job operation (RFQ in PrintTalk), whose response (the Quote in PrintTalk) contains the authorization URI (Authorization in PrintTalk). The Client then sends a job creation request (Create-Job/Print-Job/Print-URI) with the authorization (PurchaseOrder in PrintTalk), and the transaction information (charges) is recorded in the Job's job-charge-info and other Job Description attributes (the Invoice in PrintTalk). > Section 4.2 PIN/Passcode Printing > Section 4.3 Release Printing > I believe these sections are out-of-scope for paid-printing since there is not "payment" requirement for these types of printing functionalities. > PIN printing is often enforced by an organization's infrastructure, and metrics are collected as jobs are released at the printer using the PIN. This allows for correct departmental billing of services (no billing if nobody enters the PIN at the printer...) Similarly, release printing may involve different costs depending on which printer is used at print time. Again, existing solutions collect metrics and perform billing at time-of-print. Both may or may not be combined with a transaction identifier (the job-authorization-uri) but are still considered transactions and often involve some form of payment. > Section 4.5 Job Review > I believe this section is out-of-scope for paid-printing. "Job Review" could be applied to any print scenario and not specific relevance to paid-printing. In fact, if a User submits a print job for (100,000 copies) and payment is confirmed; then print the 100,000 copies. > This section came out of WG discussions (that you were present at) of likely things that a Printer or authorization service might do before providing an authorization URI or printing a Job. While it certainly is not limited to paid or transactional printing, Job Review *is* IMHO specifically relevant to it (companies have been sued for facilitating the mistakes made by their customers) and we have never held ourselves to a standard of "must be only needed for the specific use cases or title of the document". > (Mike I assume specification are written to American English notation so 100.000 should be 100,000?) > Looks like a comma in my copy of the document, but I can just remove it (100000) or use words for a really big value ("print one million copies of a brochure") for clarity. _________________________________________________________ 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_FSby5OLG8agK0WaPc9wnXQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Glen,

= On Jun 10, 2013, at 5:47 PM, "Petrie, Glen" <glen.petrie@eitc.epson.com> wrote:
Comments and Idea for paid printing

Hello

As with the IPP FaxOut, I have unable to review the IPP Paid Printing docum= ent until now.

Overall, I was concerned that "Extension for Paid Printing" is being extend= ed through 'finishings" while the concept of "paid-printing" is a business = or commerce notion and not a finishing step.

<= div dir=3D"auto">Well, no.  While I did dump some additional finishing= values in there since they are generally needed when specifying print inte= nt to a third-party print service, they aren't the focus and I have no prob= lem pulling those out and introducing them with the additions for the finis= hings-col attribute.

The core meat of the spec is in de= fining a simple transactional model for printing. The transactions may be f= or money, for internal accounting/metrics, for output tracking. Perhaps the= name should be "IPP Transactional Printing Extensions", but we aren't just= talking print-for-cash here.  The rest is supporting material to ensu= re that common use cases can be satisfied.

While I need to study the document in more det= ail; how does the current paid-printing model support a print job where a s= et of differently priced transform service are needed. 

=
The extensions don't expose the itemized pricing, b= ut rather address a more general "I want to print X, here are my credential= s, please pre-approve me".  As in prior trips down this path, we are a= voiding any notion of describing currency, pricing, or billing, but instead= are focusing on the transaction itself: how can a client say "I want to do= the following work", get back an authorization for that work (generally ti= ed to the supplied job ticket and document format in some way, e.g., a hash= ), and then submit a job and documents associated with that authorization?<= /div>

Having recently rev= iewed the PrintTalk specification of JDF; this is an interesting model to e= xplore for PWG (independent of just IPP) "paid-prinitng" for several reason= .   Instead of modifying/extending JDF, PrintTalk wraps JDF in a = business transaction or commerce transaction.   With it's relativ= ely simple set API calls it supports very complex set of operations ranging= from Quoting, Notations, etc.; again with out modification to the print jo= b JDF.  PrintTalk can itemize items and provide a quote for each item.=   And, finally, PrintTalk is already widely used and deployed.<= /p>

This is interesting for a number of reasons; fir= st, until you mentioned it I had never heard of PrintTalk - if it is widely= implemented and supported, there is very little mention of it online (I se= e a bunch of press releases in 2003 and 2004, and possibly one company - Pr= intTalk Ltd) and nobody (that I can find) selling or developing PrintTalk-b= ased solutions.  I also found this article:


I'm happy to be wrong here, b= ut so far I'm not sold on PrintTalk.

But moreover,= in looking at the specification it is far beyond the scope of anything we = have ever wanted to do, collectively, for paid printing services.  It = deals with currencies and itemized costs.  It passes around credit car= d information and other payment information. And it looks to be a fairly co= mplicated service of its own separate from the actual print service.
<= div>
That said, the basics of the RFQ/Quote and PurchaseOrder= /Invoice pairs match the model outlined in the IPP Paid Printing Extensions= , and in fact an IPP Printer *could* very easily map the IPP Job Ticket, us= er, and authorization information to PrintTalk transactions. But that would= be an implementation detail that I would not want to enforce in this docum= ent.

  &n= bsp; PWG could create a version of PrintTalk, called IppPrintTalk (or Print= TalkIpp or PrintTalkPwg) by simply replacing JDF with PWG (or IPP) in the e= xisting PrintTalk specification.   Now IPP stays the same while e= xtending an existing "paid printing" API and implementations which could be= applied to any PWG model (Cloud?)

Ex= cept that we don't have the data types for currencies, don't have the secur= ity model for handling credit cards, and IMHO don't want to limit ourselves= to the cash-based reprographic work order process that PrintTalk appears t= o be based on.

Othe= r comments on the specification itself

The attribute "printer-charge-info-uri" is not defined in this document (pe= rhaps somewhere else).  But my concern that a discussion about how a U= ser is associated with a paid (payment) service is out-of-scope.

=
printer-charge-info-uri was defined in JPS3.  It an= d printer-charge-info tell the Client that the Printer is not "free" (for s= ome value or definition of "free").

As for not ass= ociating a User with a payment service, that is what the job-authorization-= uri is for.  It identifies the pairing of the user to a job ticket and= document (format).  The Client gets an authorization URI by sending a= Validate-Job operation (RFQ in PrintTalk), whose response (the Quote in Pr= intTalk) contains the authorization URI (Authorization in PrintTalk).  = ;The Client then sends a job creation request (Create-Job/Print-Job/Print-U= RI) with the authorization (PurchaseOrder in PrintTalk), and the transactio= n information (charges) is recorded in the Job's job-charge-info and other = Job Description attributes (the Invoice in PrintTalk).

Section 4.2 PIN/Passcode Printing<= br> Section 4.3 Release Printing
    I believe these sections are out-of-scope for paid-print= ing since there is not "payment" requirement for these types of printing fu= nctionalities.

PIN printing is often = enforced by an organization's infrastructure, and metrics are collected as = jobs are released at the printer using the PIN.  This allows for corre= ct departmental billing of services (no billing if nobody enters the PIN at= the printer...)

Similarly, release printing may i= nvolve different costs depending on which printer is used at print time. &n= bsp;Again, existing solutions collect metrics and perform billing at time-o= f-print.

Both may or may not be combined with a tr= ansaction identifier (the job-authorization-uri) but are still considered t= ransactions and often involve some form of payment.

Section 4.5 Job Review
    I believe this section is out-of-scope for paid-printing= .  "Job Review" could be applied to any print scenario and not specifi= c relevance to paid-printing.   In fact, if a User submits a prin= t job for (100,000 copies) and payment is confirmed; then print the 100,000= copies. 

This section came out of W= G discussions (that you were present at) of likely things that a Printer or= authorization service might do before providing an authorization URI or pr= inting a Job.  While it certainly is not limited to paid or transactio= nal printing, Job Review *is* IMHO specifically relevant to it (companies h= ave been sued for facilitating the mistakes made by their customers) and we= have never held ourselves to a standard of "must be only needed for the sp= ecific use cases or title of the document".
=

(Mike I assume specification are written to American English notation so 10= 0.000 should be 100,000?)

Looks like = a comma in my copy of the document, but I can just remove it (100000) or us= e words for a really big value ("print one million copies of a brochure") f= or clarity.

_________________________________________________________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_FSby5OLG8agK0WaPc9wnXQ)-- --===============0318673630== 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 --===============0318673630==-- From ipp-bounces@pwg.org Fri Jun 21 08:18:31 2013 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 E558921F9E76 for ; Fri, 21 Jun 2013 08:18:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.994 X-Spam-Level: X-Spam-Status: No, score=-1.994 tagged_above=-999 required=5 tests=[AWL=0.603, 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 4I9KNGYAIrgF for ; Fri, 21 Jun 2013 08:18:27 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2472221F9E04 for ; Fri, 21 Jun 2013 08:18:25 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 56B71791D4; Fri, 21 Jun 2013 11:17:49 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by pwg.org (Postfix) with ESMTP id 0F8FD791D2 for ; Fri, 21 Jun 2013 11:17:26 -0400 (EDT) Received: by mail-ie0-f182.google.com with SMTP id s9so19765064iec.13 for ; Fri, 21 Jun 2013 08:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tKT7zN02u3B7F2UoDvyPlIKakkz/z3dlp6U+UE2xpGA=; b=t8Qx69GnBkoihp+VwzLv7AFzqwbx3XtTFjdhM4vxxDGXkkHVqV6K09efKvPcDLnEtq Cdz8DTYOuukpbDOwZtWdW0FCfMBfjmjm/FdUB3E4N3Whj6DeZizWL6g8d4MyBMIvWJwQ l4AMuRlP6GErBPYX3CYUvTKBATGHjZopYm5EV6PGhgGS8/1mjWykdZ+8qcDvDhIRw/22 XBRMAIeSflweaSXsJgR2dcUWilZOAjY29GclHVULOD/+KdhAI3BUMVO42AU2XpnqQCUp qetfh3K0ANqQj3dfDmDPV0sBHOYySwqaGp8BJj+jPb2eSdUM1Cw3e04jOTe1+uLCDSk0 ISjQ== MIME-Version: 1.0 X-Received: by 10.50.3.103 with SMTP id b7mr2579562igb.54.1371827846566; Fri, 21 Jun 2013 08:17:26 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Fri, 21 Jun 2013 08:17:26 -0700 (PDT) In-Reply-To: <8C05122D-8073-4862-93CB-CD1AA8679EAC@apple.com> References: <8C05122D-8073-4862-93CB-CD1AA8679EAC@apple.com> Date: Fri, 21 Jun 2013 11:17:26 -0400 Message-ID: Subject: Re: [IPP] Comments and Idea for paid printing 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="===============0402147152==" 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: 56B71791D4.AA87B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0402147152== Content-Type: multipart/alternative; boundary=089e013c61e07cda3f04dfab8f00 --089e013c61e07cda3f04dfab8f00 Content-Type: text/plain; charset=ISO-8859-1 Hi Mike, I like taking "Paid" out of the title of this spec - you're right about the wider scope. 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 Thu, Jun 20, 2013 at 4:15 PM, Michael Sweet wrote: > Glen, > > On Jun 10, 2013, at 5:47 PM, "Petrie, Glen" > wrote: > > Hello > > As with the IPP FaxOut, I have unable to review the IPP Paid Printing > document until now. > > Overall, I was concerned that "Extension for Paid Printing" is being > extended through 'finishings" while the concept of "paid-printing" is a > business or commerce notion and not a finishing step. > > Well, no. While I did dump some additional finishing values in there > since they are generally needed when specifying print intent to a > third-party print service, they aren't the focus and I have no problem > pulling those out and introducing them with the additions for the > finishings-col attribute. > > The core meat of the spec is in defining a simple transactional model for > printing. The transactions may be for money, for internal > accounting/metrics, for output tracking. Perhaps the name should be "IPP > Transactional Printing Extensions", but we aren't just talking > print-for-cash here. The rest is supporting material to ensure that common > use cases can be satisfied. > > While I need to study the document in more detail; how does the current > paid-printing model support a print job where a set of differently priced > transform service are needed. > > The extensions don't expose the itemized pricing, but rather address a > more general "I want to print X, here are my credentials, please > pre-approve me". As in prior trips down this path, we are avoiding any > notion of describing currency, pricing, or billing, but instead are > focusing on the transaction itself: how can a client say "I want to do the > following work", get back an authorization for that work (generally tied to > the supplied job ticket and document format in some way, e.g., a hash), and > then submit a job and documents associated with that authorization? > > Having recently reviewed the PrintTalk specification of JDF; this is an > interesting model to explore for PWG (independent of just IPP) > "paid-prinitng" for several reason. Instead of modifying/extending JDF, > PrintTalk wraps JDF in a business transaction or commerce transaction. > With it's relatively simple set API calls it supports very complex set of > operations ranging from Quoting, Notations, etc.; again with out > modification to the print job JDF. PrintTalk can itemize items and provide > a quote for each item. And, finally, PrintTalk is already widely used and > deployed. > > This is interesting for a number of reasons; first, until you mentioned it > I had never heard of PrintTalk - if it is widely implemented and supported, > there is very little mention of it online (I see a bunch of press releases > in 2003 and 2004, and possibly one company - PrintTalk Ltd) and nobody > (that I can find) selling or developing PrintTalk-based solutions. I also > found this article: > > http://www.piworld.com/article/in-search-printtalk-jdf-mcilroy-18362/1 > > I'm happy to be wrong here, but so far I'm not sold on PrintTalk. > > But moreover, in looking at the specification it is far beyond the scope > of anything we have ever wanted to do, collectively, for paid printing > services. It deals with currencies and itemized costs. It passes around > credit card information and other payment information. And it looks to be a > fairly complicated service of its own separate from the actual print > service. > > That said, the basics of the RFQ/Quote and PurchaseOrder/Invoice pairs > match the model outlined in the IPP Paid Printing Extensions, and in fact > an IPP Printer *could* very easily map the IPP Job Ticket, user, and > authorization information to PrintTalk transactions. But that would be an > implementation detail that I would not want to enforce in this document. > > PWG could create a version of PrintTalk, called IppPrintTalk (or > PrintTalkIpp or PrintTalkPwg) by simply replacing JDF with PWG (or IPP) in > the existing PrintTalk specification. Now IPP stays the same while > extending an existing "paid printing" API and implementations which could > be applied to any PWG model (Cloud?) > > Except that we don't have the data types for currencies, don't have the > security model for handling credit cards, and IMHO don't want to limit > ourselves to the cash-based reprographic work order process that PrintTalk > appears to be based on. > > Other comments on the specification itself > > The attribute "printer-charge-info-uri" is not defined in this document > (perhaps somewhere else). But my concern that a discussion about how a > User is associated with a paid (payment) service is out-of-scope. > > printer-charge-info-uri was defined in JPS3. It and printer-charge-info > tell the Client that the Printer is not "free" (for some value or > definition of "free"). > > As for not associating a User with a payment service, that is what the > job-authorization-uri is for. It identifies the pairing of the user to a > job ticket and document (format). The Client gets an authorization URI by > sending a Validate-Job operation (RFQ in PrintTalk), whose response (the > Quote in PrintTalk) contains the authorization URI (Authorization in > PrintTalk). The Client then sends a job creation request > (Create-Job/Print-Job/Print-URI) with the authorization (PurchaseOrder in > PrintTalk), and the transaction information (charges) is recorded in the > Job's job-charge-info and other Job Description attributes (the Invoice in > PrintTalk). > > Section 4.2 PIN/Passcode Printing > Section 4.3 Release Printing > I believe these sections are out-of-scope for paid-printing since > there is not "payment" requirement for these types of printing > functionalities. > > PIN printing is often enforced by an organization's infrastructure, and > metrics are collected as jobs are released at the printer using the PIN. > This allows for correct departmental billing of services (no billing if > nobody enters the PIN at the printer...) > > Similarly, release printing may involve different costs depending on which > printer is used at print time. Again, existing solutions collect metrics > and perform billing at time-of-print. > > Both may or may not be combined with a transaction identifier (the > job-authorization-uri) but are still considered transactions and often > involve some form of payment. > > Section 4.5 Job Review > I believe this section is out-of-scope for paid-printing. "Job > Review" could be applied to any print scenario and not specific relevance > to paid-printing. In fact, if a User submits a print job for (100,000 > copies) and payment is confirmed; then print the 100,000 copies. > > This section came out of WG discussions (that you were present at) of > likely things that a Printer or authorization service might do before > providing an authorization URI or printing a Job. While it certainly is > not limited to paid or transactional printing, Job Review *is* IMHO > specifically relevant to it (companies have been sued for facilitating the > mistakes made by their customers) and we have never held ourselves to a > standard of "must be only needed for the specific use cases or title of the > document". > > (Mike I assume specification are written to American English notation so > 100.000 should be 100,000?) > > Looks like a comma in my copy of the document, but I can just remove it > (100000) or use words for a really big value ("print one million copies of > a brochure") for clarity. > > _________________________________________________________ > 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. --089e013c61e07cda3f04dfab8f00 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Mike,

I like taking "Paid&q= uot; out of the title of this spec - you're right about the wider scope= .

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chai= r - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Work= ing Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobi= lity 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



On Thu, Jun 20, 2013 at 4:15 PM, Michael= Sweet <msweet@apple.com> wrote:
Glen,

On Jun 10, 2013, at 5:47 PM, "Petrie, Glen" <glen.petrie@eitc.epson.co= m> wrote:

Hello

As with the IPP FaxOut, I have unable to review the IPP Paid Printing docum= ent until now.

Overall, I was concerned that "Extension for Paid Printing" is be= ing extended through 'finishings" while the concept of "paid-= printing" is a business or commerce notion and not a finishing step.

Well, no. =A0While I did dump so= me additional finishing values in there since they are generally needed whe= n specifying print intent to a third-party print service, they aren't t= he focus and I have no problem pulling those out and introducing them with = the additions for the finishings-col attribute.

The core meat of the spec is in defining a simple transactio= nal model for printing. The transactions may be for money, for internal acc= ounting/metrics, for output tracking. Perhaps the name should be "IPP = Transactional Printing Extensions", but we aren't just talking pri= nt-for-cash here. =A0The rest is supporting material to ensure that common = use cases can be satisfied.

While I need= to study the document in more detail; how does the current paid-printing m= odel support a print job where a set of differently priced transform servic= e are needed.=A0

The extensions don't expose th= e itemized pricing, but rather address a more general "I want to print= X, here are my credentials, please pre-approve me". =A0As in prior tr= ips down this path, we are avoiding any notion of describing currency, pric= ing, or billing, but instead are focusing on the transaction itself: how ca= n a client say "I want to do the following work", get back an aut= horization for that work (generally tied to the supplied job ticket and doc= ument format in some way, e.g., a hash), and then submit a job and document= s associated with that authorization?

Having recently r= eviewed the PrintTalk specification of JDF; this is an interesting model to= explore for PWG (independent of just IPP) "paid-prinitng" for se= veral reason.=A0=A0 Instead of modifying/extending JDF, PrintTalk wraps JDF= in a business transaction or commerce transaction.=A0=A0 With it's rel= atively simple set API calls it supports very complex set of operations ran= ging from Quoting, Notations, etc.; again with out modification to the prin= t job JDF.=A0 PrintTalk can itemize items and provide a quote for each item= .=A0 And, finally, PrintTalk is already widely used and deployed.

This is interesting for a number of reasons; = first, until you mentioned it I had never heard of PrintTalk - if it is wid= ely implemented and supported, there is very little mention of it online (I= see a bunch of press releases in 2003 and 2004, and possibly one company -= PrintTalk Ltd) and nobody (that I can find) selling or developing PrintTal= k-based solutions. =A0I also found this article:


<= div> I'm happy to be wrong here, but so far I'm not sold on PrintTalk.

But moreover, in looking at the specification it is= far beyond the scope of anything we have ever wanted to do, collectively, = for paid printing services. =A0It deals with currencies and itemized costs.= =A0It passes around credit card information and other payment information.= And it looks to be a fairly complicated service of its own separate from t= he actual print service.

That said, the basics of the RFQ/Quote and PurchaseOrde= r/Invoice pairs match the model outlined in the IPP Paid Printing Extension= s, and in fact an IPP Printer *could* very easily map the IPP Job Ticket, u= ser, and authorization information to PrintTalk transactions. But that woul= d be an implementation detail that I would not want to enforce in this docu= ment.

=A0=A0=A0 PWG cou= ld create a version of PrintTalk, called IppPrintTalk (or PrintTalkIpp or P= rintTalkPwg) by simply replacing JDF with PWG (or IPP) in the existing Prin= tTalk specification.=A0=A0 Now IPP stays the same while extending an existi= ng "paid printing" API and implementations which could be applied= to any PWG model (Cloud?)

Except that we don't have the = data types for currencies, don't have the security model for handling c= redit cards, and IMHO don't want to limit ourselves to the cash-based r= eprographic work order process that PrintTalk appears to be based on.

Other comments on= the specification itself

The attribute "printer-charge-info-uri" is not defined in this do= cument (perhaps somewhere else).=A0 But my concern that a discussion about = how a User is associated with a paid (payment) service is out-of-scope.

printer-charge-info-uri was defined in JPS3. =A0It= and printer-charge-info tell the Client that the Printer is not "free= " (for some value or definition of "free").

As for not associating a User with a payment service, that is wh= at the job-authorization-uri is for. =A0It identifies the pairing of the us= er to a job ticket and document (format). =A0The Client gets an authorizati= on URI by sending a Validate-Job operation (RFQ in PrintTalk), whose respon= se (the Quote in PrintTalk) contains the authorization URI (Authorization i= n PrintTalk). =A0The Client then sends a job creation request (Create-Job/P= rint-Job/Print-URI) with the authorization (PurchaseOrder in PrintTalk), an= d the transaction information (charges) is recorded in the Job's job-ch= arge-info and other Job Description attributes (the Invoice in PrintTalk).<= /div>

Section 4.2 = PIN/Passcode Printing
Section 4.3 Release Printing
=A0=A0=A0 I believe these sections are out-of-scope for paid-printing since= there is not "payment" requirement for these types of printing f= unctionalities.

PIN printing is= often enforced by an organization's infrastructure, and metrics are co= llected as jobs are released at the printer using the PIN. =A0This allows f= or correct departmental billing of services (no billing if nobody enters th= e PIN at the printer...)

Similarly, release printing may involve different costs= depending on which printer is used at print time. =A0Again, existing solut= ions collect metrics and perform billing at time-of-print.

Both may or may not be combined with a transaction identifier (t= he job-authorization-uri) but are still considered transactions and often i= nvolve some form of payment.

Section 4.5 Job Review
=A0=A0=A0 I believe this section is out-of-scope for paid-printing.=A0 &quo= t;Job Review" could be applied to any print scenario and not specific = relevance to paid-printing.=A0=A0 In fact, if a User submits a print job fo= r (100,000 copies) and payment is confirmed; then print the 100,000 copies.= =A0

This section came out of WG discussions (that= you were present at) of likely things that a Printer or authorization serv= ice might do before providing an authorization URI or printing a Job. =A0Wh= ile it certainly is not limited to paid or transactional printing, Job Revi= ew *is* IMHO specifically relevant to it (companies have been sued for faci= litating the mistakes made by their customers) and we have never held ourse= lves to a standard of "must be only needed for the specific use cases = or title of the document".

(Mike I assume specification are written to American English notation so 10= 0.000 should be 100,000?)

Looks= like a comma in my copy of the document, but I can just remove it (100000)= or use words for a really big value ("print one million copies of a b= rochure") for clarity.

_________________________________________________________
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. --089e013c61e07cda3f04dfab8f00-- --===============0402147152== 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 --===============0402147152==-- From pwg-announce-bounces@pwg.org Mon Jun 24 04:48:23 2013 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 0C6D621F9AD9 for ; Mon, 24 Jun 2013 04:48:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.998 X-Spam-Level: X-Spam-Status: No, score=-4.998 tagged_above=-999 required=5 tests=[AWL=-2.400, 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 rvXWQPzT38HG for ; Mon, 24 Jun 2013 04:48:17 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9CB21F9AEE for ; Mon, 24 Jun 2013 04:48:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2A563791AB; Mon, 24 Jun 2013 07:47:28 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id F3D23791AA for ; Mon, 24 Jun 2013 07:47:03 -0400 (EDT) MIME-version: 1.0 Received: from relay6.apple.com ([17.128.113.90]) 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 <0MOW00D06BDZMY00@mail-out.apple.com> for pwg-announce@pwg.org; Mon, 24 Jun 2013 04:46:53 -0700 (PDT) X-AuditID: 1180715a-b7f506d000007d18-90-51c831abd947 Received: from [17.153.100.182] (Unknown_Domain [17.153.100.182]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay6.apple.com (Apple SCV relay) with SMTP id 1B.7E.32024.CA138C15; Mon, 24 Jun 2013 04:46:53 -0700 (PDT) From: Michael Sweet Date: Mon, 24 Jun 2013 07:46:51 -0400 To: "PWG Announcements Inc." Message-id: <51C4B421-6794-4B56-9126-7B3B88385AAA@apple.com> X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMLMWRmVeSWpSXmKPExsUiODNlm+5awxOBBm2TWCyOfIu1WNe6mtmB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyni9bzpjwUbJig+rNzA2MPaIdTFyckgImEj0 7LjECGGLSVy4t54NxBYS6GeS2NzlDWKzCahJ/J7UxwpiMwskSJzaeYkJxGYRUJV49/MsWFxY wEri46vNYL0iAsYSO9r3gtm8AjYSy++dh7L1JJb+mwO0iwNol6zEzt9JExi5ZyGZOgtJFURc W2LZwtfMs4A6mAV0JCYvRBOGsD+eP8K0gJFtFaNAUWpOYqWZXmJBQU6qXnJ+7iZGUFA1FEbt YGxYbnWIUYCDUYmHd4H58UAh1sSy4srcQ4wSHMxKIryhIicChXhTEiurUovy44tKc1KLDzFK c7AoifNKeQFVC6QnlqRmp6YWpBbBZJk4OKUaGBel3hW5ejPdpTu2VGfq+7B2ieqVPnuKufiF 0+c6/s+auFVr9lEZ5v/5s9ueOmyvD+97ujgnoLt7DptVmv3Hq/azljIsqLbo3vLEgo9xD99F NyW1TfotXrHL54eeuDCfybG3xSb/0sFHv1Ze5kqZERHjI7xng3BZzU1VKbU/i2pTnq6cVi5k psRSnJFoqMVcVJwIAJsLP8AmAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG August 2013 Face-to-Face Meeting in Camas, WA 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="===============1015660784==" 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: 2A563791AB.AD289 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1015660784== Content-type: multipart/alternative; boundary="Boundary_(ID_clzbB/Z3q9m0UCS+bBIz2w)" --Boundary_(ID_clzbB/Z3q9m0UCS+bBIz2w) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, The August 2013 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/august_2013_camas.html This page will be updated with document links as the material becomes available. Please visit the August 2013 survey page PRIOR TO August 2, 2013 and indicate whether you plan to participate in person or call in: http://www.surveymonkey.com/s/HD7Q5X8 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_clzbB/Z3q9m0UCS+bBIz2w) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

The August 20= 13 PWG face-to-face meeting page is now available. The agenda and venue&nbs= p;information can be found at:

http://www.pwg.org/chair/meeting-info/august_201= 3_camas.html

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

Please visit the August 2013 survey pa= ge PRIOR TO August 2, 2013 and indicate whether you plan to participat= e in person or call in:

http://www.surveymonkey.com/s/HD7Q5X8

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

Call-in toll-fr= ee 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 Sys= tem Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_clzbB/Z3q9m0UCS+bBIz2w)-- --===============1015660784== 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 --===============1015660784==-- From ipp-bounces@pwg.org Mon Jun 24 08:19:09 2013 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 3DCC511E813F for ; Mon, 24 Jun 2013 08:19:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.861 X-Spam-Level: X-Spam-Status: No, score=-4.861 tagged_above=-999 required=5 tests=[AWL=-2.263, 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 pJkiNPj4Xw+d for ; Mon, 24 Jun 2013 08:19:03 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBF611E8155 for ; Mon, 24 Jun 2013 08:18:54 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 3A81D791DF; Mon, 24 Jun 2013 11:18:10 -0400 (EDT) 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 6298C791D4 for ; Mon, 24 Jun 2013 11:17:46 -0400 (EDT) MIME-version: 1.0 Received: from relay5.apple.com ([17.128.113.88]) 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 <0MOW00FEWL24TZ21@mail-out.apple.com> for ipp@pwg.org; Mon, 24 Jun 2013 08:17:28 -0700 (PDT) X-AuditID: 11807158-b7f486d0000079b6-22-51c86307757b Received: from [17.153.53.43] (Unknown_Domain [17.153.53.43]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay5.apple.com (Apple SCV relay) with SMTP id FF.C3.31158.70368C15; Mon, 24 Jun 2013 08:17:28 -0700 (PDT) From: Michael Sweet Date: Mon, 24 Jun 2013 11:17:27 -0400 To: "ipp@pwg.org" Message-id: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprELMWRmVeSWpSXmKPExsUiONNUW5cj+USgQeNSAYtj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZayYcZCt4KVkRWvzIZYGxh7xLkYODgkBE4nX vzy7GDmBTDGJC/fWs3UxcnEICXQzSSzr2sACkmATUJP4PamPFcRmFkiQePHiHDuIzSKgKvFv 9x4wW1ggWWLxhPeMILaIgLzE2rapTCDzeQVsJN4fDgYJ8wroSSz9N4cRYq2sxM7fSRMYuWch GToLSRVEXFti2cLXzLOAOpgFdCQmL0QThrA/nj/CtICRbRWjQFFqTmKlqV5iQUFOql5yfu4m RlBINRRG7GD8v8zqEKMAB6MSD++HuBOBQqyJZcWVuYcYJTiYlUR4Q0WAQrwpiZVVqUX58UWl OanFhxilOViUxHklvY4HCgmkJ5akZqemFqQWwWSZODilGhhDgyaLC/1ZeOtljdfMw0+61/QV 3k0ICC2b8upDfXybmcDd1498In+tvm/QsLfuvfvKExfF5p1l/dgbOdvtZ1WizY7qYsZHa3h7 331t7I94E8+3KEyuTH5D8SZrjSj1mbkzr+do2J945TTxafepaauXL44NCGVunpN5sWiezIsv doXb1B7/0g1VYinOSDTUYi4qTgQAPmOzwyUCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) 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="===============1223026183==" 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: 3A81D791DF.A94F0 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1223026183== Content-type: multipart/alternative; boundary="Boundary_(ID_Jh8APXnQB1tvETiDecoegw)" --Boundary_(ID_Jh8APXnQB1tvETiDecoegw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. _________________________________________________________ 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_Jh8APXnQB1tvETiDecoegw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I= have posted an updated stable draft of the IPP Transactional Printing Exte= nsions (formerly the IPP Paid Printing Extensions) to:

=
Aside from the name change and some template changes, I'v= e added additional terms, explanatory text, and references (including an in= formative reference to CIP4's PrintTalk specification) to hopefully allay a= ny confusion and tie everything together cleanly.

=
____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_Jh8APXnQB1tvETiDecoegw)-- --===============1223026183== 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 --===============1223026183==-- From ipp-bounces@pwg.org Mon Jun 24 09:22:49 2013 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 0B59121E8122 for ; Mon, 24 Jun 2013 09:22:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=0.999, BAYES_00=-2.599, GB_I_LETTER=-2, 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 3v6kXrlwH+p3 for ; Mon, 24 Jun 2013 09:22:43 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 619F121E811A for ; Mon, 24 Jun 2013 09:22:42 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BA10B791E5; Mon, 24 Jun 2013 12:22:00 -0400 (EDT) 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 6AEBF791DF for ; Mon, 24 Jun 2013 12:21:36 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jun 2013 09:21:35 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Date: Mon, 24 Jun 2013 09:20:06 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Thread-Index: Ac5w7iNHAopGFEokSAm88swSAB7ahgAB9zag References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> From: "Petrie, Glen" To: "Michael Sweet" , X-OriginalArrivalTime: 24 Jun 2013 16:21:35.0352 (UTC) FILETIME=[E56A0780:01CE70F6] 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="===============0612342471==" 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: BA10B791E5.A9506 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0612342471== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE70F6.E551554A" This is a multi-part message in MIME format. ------_=_NextPart_001_01CE70F6.E551554A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike =20 I was a little surprised at your new title. "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.". While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion. =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, June 24, 2013 8:17 AM To: ipp@pwg.org Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) =20 All, =20 I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf =20 Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. =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_01CE70F6.E551554A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike

 

I was a little surprised at your new title.  "Transactional Printing" has for a very, very long t= ime meant the "printing of voices, bills, statements, notices, checks, letters, etc.".    While I have noted that it is= not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion.=

 

Glen

 

 


From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, June 24, 2013 = 8:17 AM
To: ipp@pwg.org
Subject: [IPP] Updated draft= of IPP Transactional Printing Extensions (formerly Paid Printing Extensions)

 

All,

 

I have posted an updated stable draft of the IPP Transactional Prin= ting Extensions (formerly the IPP Paid Printing Extensions) to:

 

 

Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusi= on and tie everything together cleanly.

 

__________= _______________________________________________
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_01CE70F6.E551554A-- --===============0612342471== 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 --===============0612342471==-- From ipp-bounces@pwg.org Mon Jun 24 09:40:51 2013 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 A2B0F21E8127 for ; Mon, 24 Jun 2013 09:40:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.196 X-Spam-Level: X-Spam-Status: No, score=-3.196 tagged_above=-999 required=5 tests=[AWL=1.402, BAYES_00=-2.599, GB_I_LETTER=-2, 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 GvJKMBQPIhkT for ; Mon, 24 Jun 2013 09:40:46 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 33C0F21E811E for ; Mon, 24 Jun 2013 09:40:46 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 79456791EC; Mon, 24 Jun 2013 12:40:12 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-qc0-f170.google.com (mail-qc0-f170.google.com [209.85.216.170]) by pwg.org (Postfix) with ESMTP id EB70E791A5 for ; Mon, 24 Jun 2013 12:39:48 -0400 (EDT) Received: by mail-qc0-f170.google.com with SMTP id s1so6578343qcw.1 for ; Mon, 24 Jun 2013 09:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jywS7pIg0vc6Bmiptcjmk2RI6MHKz4l9+hi1uCLOm+8=; b=NPpWu0kaqbpnV92XdQiZhYtHvNynlckPRuWLvYEZJM4QPdjzdzQwg4z1fATuRgK8dY g0kWKX8Pyr3pEL9onFcDA1LYAR2J4dOsbWAMyekG4NNayhDuwAbpZD9eeP0MYUH0qLVc 7pGIoqACfKSehn2XWYXrhCo8+5wszkJDV9zmDzP8l6HqQoF/sKEq6lwG5bPwL+LV5H5k yb4UQbASKvDSaQYzMyxJ7TG53Uf0hnjc6Z2Q4XT6DjhCzP/HRIigJ1vXrHw6aMMtWvi2 N7+/IyqNlwnEUPY2WKnqaDtMzE8xgW2f1jkR6/E0Fk6WrOlyZGskTMLk6IkGjaaMK6BM N/Zg== MIME-Version: 1.0 X-Received: by 10.224.59.142 with SMTP id l14mr27404208qah.22.1372091988269; Mon, 24 Jun 2013 09:39:48 -0700 (PDT) Received: by 10.49.64.230 with HTTP; Mon, 24 Jun 2013 09:39:48 -0700 (PDT) In-Reply-To: References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> Date: Mon, 24 Jun 2013 12:39:48 -0400 Message-ID: Subject: Re: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) From: Ira McDonald To: "Petrie, Glen" , 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="===============0297506004==" 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: 79456791EC.A9291 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0297506004== Content-Type: multipart/alternative; boundary=20cf3074b02c8f624d04dfe90f62 --20cf3074b02c8f624d04dfe90f62 Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm happier w/ simple "Transaction". But the only term I've ever seen used for printing phone bills, et al, is "variable data printing" which is very different from transaction-based. 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 Mon, Jun 24, 2013 at 12:20 PM, Petrie, Glen wrote: > Mike**** > > ** ** > > I was a little surprised at your new title. "Transactional Printing" has > for a very, very long time meant the "printing of voices, bills, > statements, notices, checks, letters, etc.". While I have noted that > it is not uncommon for PWG to "extent" the meaning of terms; might I > suggest "Transaction" versus Transactional to avoid confusion.**** > > ** ** > > Glen**** > > ** ** > > ** ** > ------------------------------ > > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] *On Behalf Of *Michael > Sweet > *Sent:* Monday, June 24, 2013 8:17 AM > *To:* ipp@pwg.org > *Subject:* [IPP] Updated draft of IPP Transactional Printing Extensions > (formerly Paid Printing Extensions)**** > > ** ** > > All,**** > > ** ** > > I have posted an updated stable draft of the IPP Transactional Printing > Extensions (formerly the IPP Paid Printing Extensions) to:**** > > ** ** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx**** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf**** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf**** > > ** ** > > Aside from the name change and some template changes, I've added > additional terms, explanatory text, and references (including an > informative reference to CIP4's PrintTalk specification) to hopefully allay > any confusion and tie everything together cleanly.**** > > ** ** > > _________________________________________________________ > 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. --20cf3074b02c8f624d04dfe90f62 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I'm happier = w/ simple "Transaction".

But the only term I've = ever seen used for printing phone bills, et al, is
"variable = data printing" which is very different from transaction-based.

Cheers,
- Ira


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --20cf3074b02c8f624d04dfe90f62-- --===============0297506004== 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 --===============0297506004==-- From ipp-bounces@pwg.org Mon Jun 24 10:03:15 2013 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 28F2311E8163 for ; Mon, 24 Jun 2013 10:03:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.546 X-Spam-Level: X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.052, 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 oOwbxeU66zKb for ; Mon, 24 Jun 2013 10:03:10 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4113D21E8148 for ; Mon, 24 Jun 2013 10:03:07 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 440E2791F3; Mon, 24 Jun 2013 13:02:34 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176]) by pwg.org (Postfix) with ESMTP id C10B6791F1 for ; Mon, 24 Jun 2013 13:02:09 -0400 (EDT) Received: by mail-qc0-f176.google.com with SMTP id z10so6397984qcx.7 for ; Mon, 24 Jun 2013 10:02:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=flFMxcGQderbOccPmM8is6IQS9G3uNlkVLGq9eAC2zo=; b=WDdhM5XaYgw6dXauy3jFYvm/IMZeciLQrXIDszhHcxL7XbTWQKyHjqlmvP4WxIvPa0 BEW5pozg5acW8e8YCmzmSPsLl2boXKDrWCHJI6sm4ylimj3/TNuDc/wKkOuBBA7yXn7H Jkr3ngvUgHY+hBj45UPPbp4Oq6XgLchX6FJpL8iF7VtgPMmP3cww9TmSoLw2YIdHStEz cmzaJ5s65eu3Wm3dbalelC9GwPVYbYCCGAaKVpNJsCb6EVN3SuKgtOzpELwzSY7Q3N/f HzKByNVF7eiDON/vpLqEFwkFf+7P4LQ+xR9CQDISKgiblMALDC9RyXzgBwX8oTl8jkbx grYA== MIME-Version: 1.0 X-Received: by 10.49.12.145 with SMTP id y17mr28566235qeb.7.1372093329055; Mon, 24 Jun 2013 10:02:09 -0700 (PDT) Received: by 10.49.64.230 with HTTP; Mon, 24 Jun 2013 10:02:09 -0700 (PDT) Date: Mon, 24 Jun 2013 13:02:09 -0400 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] IPP WG Agenda (24 June 2013) 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="===============0481880427==" 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: 440E2791F3.A84D9 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0481880427== Content-Type: multipart/alternative; boundary=047d7b6dd1887a263e04dfe95fe0 --047d7b6dd1887a263e04dfe95fe0 Content-Type: text/plain; charset=ISO-8859-1 Hi, No time for a pretty agenda. Please use the regular IPP conference bridge and WebEx. (1) PWG IP Policy and Minute Taker (2) Approve previous minutes (10 June 2013) (3) Status of various IPP specs (4) Review of updated IPP Transaction(al) Printing draft (5) Next steps - IPP WG telecon on Monday 8 July 2013 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. --047d7b6dd1887a263e04dfe95fe0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
<= br>
No time for a pretty agenda.=A0 Please use the regular
I= PP conference bridge and WebEx.

(1) PWG IP Policy and Minute T= aker

(2) Approve previous minutes (10 June 2013)

(3) Stat= us of various IPP specs

(4) Review of updated IPP Transaction(= al) Printing draft

(5) Next steps
- IPP WG telecon on= Monday 8 July 2013

Cheers,
- Ira

<= div>
Ira McDonald (Musician / Softwa= re Architect)
Chair - Linux Foundation Open Printing WG
Secretary - I= EEE-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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --047d7b6dd1887a263e04dfe95fe0-- --===============0481880427== 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 --===============0481880427==-- From ipp-bounces@pwg.org Mon Jun 24 11:41:22 2013 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 BD7AB11E8174 for ; Mon, 24 Jun 2013 11:41:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.686 X-Spam-Level: X-Spam-Status: No, score=-5.686 tagged_above=-999 required=5 tests=[AWL=-1.089, BAYES_00=-2.599, GB_I_LETTER=-2, 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 yFGp8+P6fyWi for ; Mon, 24 Jun 2013 11:41:16 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 53C8621E8120 for ; Mon, 24 Jun 2013 11:41:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8D80A791FF; Mon, 24 Jun 2013 14:40:37 -0400 (EDT) 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 E20CA791FE for ; Mon, 24 Jun 2013 14:40:14 -0400 (EDT) MIME-version: 1.0 Received: from relay4.apple.com ([17.128.113.87]) 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 <0MOW00FV3UHNTZO1@mail-out.apple.com> for ipp@pwg.org; Mon, 24 Jun 2013 11:40:10 -0700 (PDT) X-AuditID: 11807157-b7f706d0000006c6-fb-51c8928814fa Received: from [17.153.53.43] (Unknown_Domain [17.153.53.43]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id 83.61.01734.98298C15; Mon, 24 Jun 2013 11:40:10 -0700 (PDT) Subject: Re: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) From: Michael Sweet In-reply-to: Date: Mon, 24 Jun 2013 14:40:09 -0400 Message-id: <54474A61-83C5-487D-97D5-47EEB806C4D7@apple.com> References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUiONNUW7dr0olAg5lfuS22n/3FYnFs30sW iyPfYh2YPbae/MHmcXD+LHaPeYunMwUwR3HZpKTmZJalFunbJXBlrDy6mLFgdn7F2lMPWBsY 9yZ1MXJySAiYSBzadJsJwhaTuHBvPRuILSTQzSSx5okwiC0skCtxac8lsBpeAT2Jpf/mMILY zAIJEle6/rCC2GwCahK/J/WB2ZwCXhI3XpxkAbFZBFQl5h6ewAJRzy9xsPcDM8QcG4kLCw6z QOyqkng0fytYXERAX+LTx81AuziA7pGV2Pk7aQIj3ywkm2ch2Qxha0ssW/iaeRZQB7OAjsTk hYyowhD2x/NHmBYwsq1iFChKzUmsNNFLLCjISdVLzs/dxAgK2IbC8B2M/5ZZHWIU4GBU4uH9 EHciUIg1say4MvcQowQHs5IIb6gIUIg3JbGyKrUoP76oNCe1+BCjNAeLkjivhNfxQCGB9MSS 1OzU1ILUIpgsEwenVANjWYB7X+/2uS9NGAQsw5746/AH3hQO+ap7Nnlu6IWeqZc/L1IW3LVh 0wR96wVaXdb59d9uaYufcbFldVG8Zb8t3HmJ/YUDy/Yfnvbs3ImzLnualn2q9uA79XN9rVla iX1joLRd5MYNAjxrJALvxv1Lv9ZdqNTNVruqRPlqR3UD/5LvEzVbWvyUWIozEg21mIuKEwEt XpD6VAIAAA== 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="===============0616728908==" 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: 8D80A791FF.AA989 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0616728908== Content-type: multipart/alternative; boundary="Boundary_(ID_NB7OcLjs4sfnugUw18cIeg)" --Boundary_(ID_NB7OcLjs4sfnugUw18cIeg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT "IPP Transaction Printing Extensions" doesn't help; in fact, it makes me think specifically of bills, statements, etc... "IPP Transaction-Based Printing Extensions"??? On 2013-06-24, at 12:20 PM, "Petrie, Glen" wrote: > Mike > > I was a little surprised at your new title. "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.". While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion. > > Glen > > > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet > Sent: Monday, June 24, 2013 8:17 AM > To: ipp@pwg.org > Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) > > All, > > I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf > > Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. > > _________________________________________________________ > 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. _________________________________________________________ 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_NB7OcLjs4sfnugUw18cIeg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable "IPP Transaction Printing Extensions" doesn't help; in fact, it makes m= e think specifically of bills, statements, etc...

"IPP T= ransaction-Based Printing Extensions"???

Ira McDonald (Musician / Software Architect)
Chair = - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Workin= g 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 Mon, Jun 24, 2013 at 12:20 PM, Petrie= , Glen <glen.petrie@eitc.epson.com> wrote:

Mike=

=A0<= /u>

I was a little= surprised at your new title.=A0 "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.".=A0 =A0=A0While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion.<= /u>

=A0<= /u>

Glen=

=A0<= /u>

=A0<= /u>


From: ipp-bounces@pwg.or= g [mailto:ipp-= bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, June 24, 2013 = 8:17 AM
To: ipp@pwg.org
Subject: [IPP] Updated draft= of IPP Transactional Printing Extensions (formerly Paid Printing Extensions)

=A0

All,

=A0

I have posted an updated stable draft of the IPP Tra= nsactional Printing Extensions (formerly the IPP Paid Printing Extensions) to:

=A0

=A0

Aside from the name change and some template changes= , I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any con= fusion and tie everything together cleanly.

=A0

____= _____________________________________________________
Michael Sweet, Senior Printing System=A0Engineer, PWG Chair

=A0


--
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.

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



=
On 2013-06-24, at 12:20 PM, "Petrie, Glen" <glen.petrie@eitc.epson.com> wrote:

Mike
 
I was a little surprised at your new title.  "Tra= nsactional Printing" has for a very, very long time meant the "printing of = voices, bills, statements, notices, checks, letters, etc.".  &n= bsp; While I have noted that it is not uncommon for PWG to "extent" th= e meaning of terms; might I suggest "Transaction" versus Transactional to a= void confusion.
 
Glen
 
 =

From:=  ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of = Michael Sweet
Sent: Monday, June 24,= 2013 8:17 AM
To: ipp@pwg.org
Subject: [IPP] Updated draft of IPP Transactional Pr= inting Extensions (formerly Paid Printing Extensions)
 
<= font size=3D"3" face=3D"Times New Roman">= All,
 
I have posted an updated stable draft o= f the IPP Transactional Printing Extensions (formerly the IPP Paid Printing= Extensions) to:
<= font size=3D"3" face=3D"Times New Roman">=  
 
 
_= ________________________________________________________
Michael Sweet, = Senior Printing System Engineer, PWG Chair
<= span style=3D"font-size: 12pt; "> 

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

____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_NB7OcLjs4sfnugUw18cIeg)-- --===============0616728908== 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 --===============0616728908==-- From ipp-bounces@pwg.org Mon Jun 24 12:00:03 2013 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 70F1F21E8159 for ; Mon, 24 Jun 2013 12:00:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.097 X-Spam-Level: X-Spam-Status: No, score=-4.097 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, GB_I_LETTER=-2, 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 CAlzueGIPHnx for ; Mon, 24 Jun 2013 11:59:57 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7724621E8169 for ; Mon, 24 Jun 2013 11:59:57 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 85A06791F3; Mon, 24 Jun 2013 14:59:28 -0400 (EDT) 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 DFF41791E6 for ; Mon, 24 Jun 2013 14:59:04 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jun 2013 11:59:03 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Date: Mon, 24 Jun 2013 11:57:33 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Thread-Index: Ac5xCkSjYMnaAQESTHKTqvG7WVBkigAAmFAg References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> <54474A61-83C5-487D-97D5-47EEB806C4D7@apple.com> From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 24 Jun 2013 18:59:03.0555 (UTC) FILETIME=[E4FB6530:01CE710C] 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="===============0309702927==" 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: 85A06791F3.A8CD9 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0309702927== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE710C.E4B7B088" This is a multi-part message in MIME format. ------_=_NextPart_001_01CE710C.E4B7B088 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable How about what it is " Print for Pay" =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Monday, June 24, 2013 11:40 AM To: Petrie, Glen Cc: ipp@pwg.org Subject: Re: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) =20 "IPP Transaction Printing Extensions" doesn't help; in fact, it makes me think specifically of bills, statements, etc... =20 "IPP Transaction-Based Printing Extensions"??? =20 =20 On 2013-06-24, at 12:20 PM, "Petrie, Glen" wrote: Mike =20 I was a little surprised at your new title. "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.". While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion. =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, June 24, 2013 8:17 AM To: ipp@pwg.org Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) =20 All, =20 I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf =20 Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. =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 _________________________________________________________ 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_01CE710C.E4B7B088 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

How about what it is " Print for Pay"

 


From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Monday, June 24, 2013 = 11:40 AM
To: Petrie, Glen
Cc: ipp@pwg.org
Subject: Re: [IPP] Updated d= raft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions= )

 

"IPP Transaction Printing Extensions" doesn't help; in fa= ct, it makes me think specifically of bills, statements, etc...

 

"IPP Transaction-Based Printing Extensions"???=

 

 

On 2013-06-24, at 12:20 PM, "Petrie, Glen" <glen.petrie@eitc.epson.com&g= t; wrote:



Mike=

 

I was a little surprised at your new title.  "Transactional Printing" has for a very, very long t= ime meant the "printing of voices, bills, statements, notices, checks, letters, etc.".    While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion.

 

Glen=

 

 


From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, June 24, 2013 8:17 AM
To: i= pp@pwg.org
Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions)

 

All,

 

I have posted an updated stable draft of the IPP Transactional Prin= ting Extensions (formerly the IPP Paid Printing Extensions) to:

 

 

Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusi= on and tie everything together cleanly.<= /p>

 

________________________________________________= _________
Michael Sweet, Senior Printing System Engineer, PWG Chair=

 


-- 
This message has been scanned for viruses and 
dangerous content by M= ailScanner, 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_01CE710C.E4B7B088-- --===============0309702927== 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 --===============0309702927==-- From ipp-bounces@pwg.org Mon Jun 24 12:16:01 2013 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 5B62321E8170 for ; Mon, 24 Jun 2013 12:16:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.264 X-Spam-Level: X-Spam-Status: No, score=-4.264 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, GB_I_LETTER=-2, 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 aMeHxHVfcZal for ; Mon, 24 Jun 2013 12:15:55 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 68AA921F90DC for ; Mon, 24 Jun 2013 12:15:55 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9C14A79205; Mon, 24 Jun 2013 15:15:29 -0400 (EDT) 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 E50A579195 for ; Mon, 24 Jun 2013 15:15:04 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jun 2013 12:15:03 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions(formerly Paid Printing Extensions) Date: Mon, 24 Jun 2013 12:13:38 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Updated draft of IPP Transactional Printing Extensions(formerly Paid Printing Extensions) Thread-Index: Ac5xCkSjYMnaAQESTHKTqvG7WVBkigAAmFAgAACOaIA= References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com><54474A61-83C5-487D-97D5-47EEB806C4D7@apple.com> From: "Petrie, Glen" To: "Petrie, Glen" , "Michael Sweet" X-OriginalArrivalTime: 24 Jun 2013 19:15:03.0931 (UTC) FILETIME=[216924B0:01CE710F] 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="===============2022879635==" 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: 9C14A79205.AA02E X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============2022879635== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE710F.21368F8E" This is a multi-part message in MIME format. ------_=_NextPart_001_01CE710F.21368F8E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ops "Pay for Print" =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Monday, June 24, 2013 11:58 AM To: Michael Sweet Cc: ipp@pwg.org Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions(formerly Paid Printing Extensions) =20 How about what it is " Print for Pay" =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Monday, June 24, 2013 11:40 AM To: Petrie, Glen Cc: ipp@pwg.org Subject: Re: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) =20 "IPP Transaction Printing Extensions" doesn't help; in fact, it makes me think specifically of bills, statements, etc... =20 "IPP Transaction-Based Printing Extensions"??? =20 =20 On 2013-06-24, at 12:20 PM, "Petrie, Glen" wrote: =20 Mike =20 I was a little surprised at your new title. "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.". While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion. =20 Glen =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, June 24, 2013 8:17 AM To: ipp@pwg.org Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) =20 All, =20 I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf =20 Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. =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 _________________________________________________________ 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_01CE710F.21368F8E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ops  "Pay for Print"<= o:p>

 


From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Monday, June 24, 2013 = 11:58 AM
To: Michael Sweet
Cc: ipp@pwg.org
Subject: RE: [IPP] Updated d= raft of IPP Transactional Printing Extensions(formerly Paid Printing Extensions)=

 

How about what it is " Print for Pay"

 


From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Monday, June 24, 2013 = 11:40 AM
To: Petrie, Glen
Cc: ipp@pwg.org
Subject: Re: [IPP] Updated d= raft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions= )

 

"IPP Transaction Printing Extensions" doesn't help; in fa= ct, it makes me think specifically of bills, statements, etc...

 

"IPP Transaction-Based Printing Extensions"???=

 

 

On 2013-06-24, at 12:20 PM, "Petrie, Glen" <glen.petrie@eitc.epson.com&g= t; wrote:

 =

Mike=

 

I was a little surprised at your new title.  "Transactional Printing" has for a very, very long t= ime meant the "printing of voices, bills, statements, notices, checks, letters, etc.".    While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion.

 

Glen=

 

 


From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Monday, June 24, 2013 8:17 AM
To: i= pp@pwg.org
Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions)

 

All,

 

I have posted an updated stable draft of the IPP Transactional Prin= ting Extensions (formerly the IPP Paid Printing Extensions) to:

 

 

Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusi= on and tie everything together cleanly.<= /p>

 

________________________________________________= _________
Michael Sweet, Senior Printing System Engineer, PWG Chair=

 


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

 

__________= _______________________________________________
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_01CE710F.21368F8E-- --===============2022879635== 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 --===============2022879635==-- From ipp-bounces@pwg.org Mon Jun 24 13:24:51 2013 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 8B31A21E817C for ; Mon, 24 Jun 2013 13:24:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.609 X-Spam-Level: X-Spam-Status: No, score=-4.609 tagged_above=-999 required=5 tests=[AWL=-2.010, BAYES_00=-2.599] 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 lGzeQrH5N-qp for ; Mon, 24 Jun 2013 13:24:41 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B636211E8186 for ; Mon, 24 Jun 2013 13:24:30 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 610D779212; Mon, 24 Jun 2013 16:23:54 -0400 (EDT) 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 1F39979205 for ; Mon, 24 Jun 2013 16:23:30 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay8.apple.com ([17.128.113.102]) 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 <0MOW00I4AZAB92H0@mail-out.apple.com> for ipp@pwg.org; Mon, 24 Jun 2013 13:23:29 -0700 (PDT) X-AuditID: 11807166-b7faa6d000003acb-5b-51c8aabfe8ed Received: from [17.153.45.7] (Unknown_Domain [17.153.45.7]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay8.apple.com (Apple SCV relay) with SMTP id BD.60.15051.0CAA8C15; Mon, 24 Jun 2013 13:23:29 -0700 (PDT) From: Michael Sweet Date: Mon, 24 Jun 2013 16:23:04 -0400 To: "ipp@pwg.org" Message-id: <845E907E-57F7-4844-988C-DB11235D0A7C@apple.com> X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLJMWRmVeSWpSXmKPExsUiOFOXXffgqhOBBh+P8Fsc2/eSxeLIt1gH Jo+tJ3+wecxbPJ0pgCmKyyYlNSezLLVI3y6BK6Ot5zRTwR7mipNP1jE2ML5n6mLk5JAQMJF4 +2kvM4QtJnHh3nq2LkYuDiGBTiaJx+vusoAk2ATUJH5P6mMFsZkFtCRu/HvJBGHLS2x/Owes mUVAVWL9tKdsILYw0ND1d7+A2SJANWvbpoLV8wrYSEzePoMRwtaTWPpvDpDNAbRYVmLn76QJ jDyzkGyYhWTDLCQdCxiZVzEKFKXmJFZa6CUWFOSk6iXn525iBAVKQ2HaDsam5VaHGAU4GJV4 eD/EnQgUYk0sK67MPcQowcGsJMIbKgIU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzivtdTxQSCA9 sSQ1OzW1ILUIJsvEwSnVwJi7LLEpZ+rLFxwtwhxWggk7b9u0/3qetnN62m/HR5OTtxzaJ1hb rNiYadG/rsB4q4VT6G+mhzpXLweLiF+yf92+rutumhT3zlN/GS6u2hP/XmDGEtd/F5uX7Ciq r193LV7iipPn08Ayx01pnJ6GGcJdPnbOJ+KM/3Ir7ExeovvVMOb2pzsb1imxFGckGmoxFxUn AgDUY8JYEAIAAA== 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: 610D779212.A7BF0 X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted the minutes from today's IPP WG conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20130624.pdf Our next conference call is July 8, 2013 at 3pm ET. There was one new action item: - Mike to post initial draft of IPP FInishings Extensions (update of 5100.1) _________________________________________________________ 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 ipp-bounces@pwg.org Mon Jun 24 15:54:03 2013 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 A3A6921E80C9 for ; Mon, 24 Jun 2013 15:54:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.597 X-Spam-Level: X-Spam-Status: No, score=-4.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, 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 mwzKqIXC-Ehy for ; Mon, 24 Jun 2013 15:53:57 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id E7FA321F9E95 for ; Mon, 24 Jun 2013 15:53:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id AABA879219; Mon, 24 Jun 2013 18:53:21 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by pwg.org (Postfix) with ESMTP id 3B398791A7 for ; Mon, 24 Jun 2013 18:52:54 -0400 (EDT) Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta12.westchester.pa.mail.comcast.net with comcast id sMMa1l0040xGWP85CNsuUT; Mon, 24 Jun 2013 22:52:54 +0000 Received: from TCS2010LAPTOP ([24.34.47.110]) by omta12.westchester.pa.mail.comcast.net with comcast id sNqt1l00C2NeFBL3YNqtg4; Mon, 24 Jun 2013 22:50:54 +0000 From: "Paul Tykodi" To: "'Michael Sweet'" References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> In-Reply-To: Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Date: Mon, 24 Jun 2013 18:50:53 -0400 Organization: Tykodi Consulting Services LLC Message-ID: <036401ce712d$4898bf00$d9ca3d00$@tykodi.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJN7MClLHpGWTRGpYQw8mjh1lOFmgGAf+KDmDp8ZOA= Content-Language: en-us DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372114374; bh=boWyQxTq2p7P67NIWaSEki6H16SdqiHDRF83M0PGAs8=; h=Received:Received:Reply-To:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=Pnbl1ELdAbrds0RnZWdLPcBIW3cnZT/3Jk19pxNs0LwcE76hrzadnWjs+69Cw725r RyXPoPUYYXhiDA1QgFdFMEZcE2gURiTq+yEYdR8GjYkxP+H6kfSuRpkIIdUGoXXvAh GEjQTdXnjlKO0xN2sjYe3a8/DNza/PizoWf+6wC6KZvNKen4PMmLZtStPNUMSZ6cab mgkgvoeeC1WAEnpnNEEgLT9ZyZBUpUrexZvujI8X4RWUf8PCfv/L5dbSSQUQtKs6xI H+v8a6pLgP4eos+Ij66Tzqrp8GWXF3u8CUPU6zRXyQjSguX5nAEKq4Jhx+hyJFfZDf ctynntvijJafA== 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 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="===============1826313977==" 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: AABA879219.A8AA8 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============1826313977== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0365_01CE710B.C18EC020" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0365_01CE710B.C18EC020 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Mike, I agree with Glen's comment that Transactional Printing has a different meaning than what we want to convey in this specification. I think that "Transaction" will be understood correctly. 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 Petrie, Glen Sent: Monday, June 24, 2013 12:20 PM To: Michael Sweet; ipp@pwg.org Subject: RE: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) Mike I was a little surprised at your new title. "Transactional Printing" has for a very, very long time meant the "printing of voices, bills, statements, notices, checks, letters, etc.". While I have noted that it is not uncommon for PWG to "extent" the meaning of terms; might I suggest "Transaction" versus Transactional to avoid confusion. Glen _____ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, June 24, 2013 8:17 AM To: ipp@pwg.org Subject: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) All, I have posted an updated stable draft of the IPP Transactional Printing Extensions (formerly the IPP Paid Printing Extensions) to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf Aside from the name change and some template changes, I've added additional terms, explanatory text, and references (including an informative reference to CIP4's PrintTalk specification) to hopefully allay any confusion and tie everything together cleanly. _________________________________________________________ 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. ------=_NextPart_000_0365_01CE710B.C18EC020 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Mike,

 

=

I agree with Glen’s comment that Transact= ional Printing has a different meaning than what we want to convey in this = specification. I think that “Transaction” will be understood co= rrectly.

 =

Best Regards,

<= p class=3DMsoNormal> 

/Paul

--=

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Ser= vices LLC

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

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Be= half Of Petrie, Glen
Sent: Monday, June 24, 2013 12:20 PM
= To: Michael Sweet; ipp@pwg.org
Subject: RE: [IPP] Updated = draft of IPP Transactional Printing Extensions (formerly Paid Printing Exte= nsions)

 

Mike

 

I wa= s a little surprised at your new title.  "Transactional Printing&= quot; has for a very, very long time meant the "printing of voices, bi= lls, statements, notices, checks, letters, etc.".    Wh= ile I have noted that it is not uncommon for PWG to "extent" the = meaning of terms; might I suggest "Transaction" versus Transactio= nal to avoid confusion.

 

Glen

 

 =


From: ipp-bounces@pwg.org = [mailto:ipp-bounces@pwg.org] = On Behalf Of Michael Sweet
Sent: Monday, June 24, 2013 8:17 A= M
To: ipp@pwg.org
Subjec= t: [IPP] Updated draft of IPP Transactional Printing Extensions (former= ly Paid Printing Extensions)

 

All,

 

I have p= osted an updated stable draft of the IPP Transactional Printing Extensions = (formerly the IPP Paid Printing Extensions) to:

 

 

Aside from the name change and some template changes, I've added addi= tional terms, explanatory text, and references (including an informative re= ference to CIP4's PrintTalk specification) to hopefully allay any confusion= and tie everything together cleanly.

 

________________________= _________________________________
Michael Sweet, Senior Printing System&= nbsp;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_000_0365_01CE710B.C18EC020-- --===============1826313977== 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 --===============1826313977==-- From ipp-bounces@pwg.org Mon Jun 24 16:08:21 2013 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 DABA411E817F for ; Mon, 24 Jun 2013 16:08:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.557 X-Spam-Level: X-Spam-Status: No, score=-3.557 tagged_above=-999 required=5 tests=[AWL=1.042, BAYES_00=-2.599, GB_I_LETTER=-2, 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 9NngHm506QFh for ; Mon, 24 Jun 2013 16:08:17 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id DA43321F9F8A for ; Mon, 24 Jun 2013 16:08:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B66EB79218; Mon, 24 Jun 2013 19:07:46 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by pwg.org (Postfix) with ESMTP id 42418791FA for ; Mon, 24 Jun 2013 19:07:22 -0400 (EDT) Received: by mail-ie0-f173.google.com with SMTP id k13so26416915iea.32 for ; Mon, 24 Jun 2013 16:07:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ePDddCM6qLwlTTHcfNKgXwHMfviMXI4TbLWurl0QMBQ=; b=pB4W59H5pwW+dj1/VdNEB5qlXmGHsCTxhPHckDj8fxiURZbbr+aXHh68ehA2nkD9ge 63XVNojtRtRVBZkZBYgUZU6u9F4uwXi+Lhw0Btp9Atn7HgDGaa9/wi+DaGgS2t7E+N7M 3OjIr37UiWYyKHo/Tahio/AglG4Y8KXopTfmvQJtONgUnfr07UP9QBoUr1ItFcoSTfjx w/ASqu+h/vXCFe1hzQZjkCWQ2JwSEo9svQigDOT9l+RyZZnzg0OS+08KXz7QbJ6cWqo8 8BBw4MR41nGp8eElJtMLjw88XLfNEL8uiquUuCupSJ6S1Zp6Q7HNefIF+kvIK+dc6EY1 9+ew== MIME-Version: 1.0 X-Received: by 10.50.3.103 with SMTP id b7mr6859356igb.54.1372115242046; Mon, 24 Jun 2013 16:07:22 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Mon, 24 Jun 2013 16:07:21 -0700 (PDT) In-Reply-To: <036401ce712d$4898bf00$d9ca3d00$@tykodi.com> References: <090E09A8-B564-42AD-B781-A1308429B972@apple.com> <036401ce712d$4898bf00$d9ca3d00$@tykodi.com> Date: Mon, 24 Jun 2013 19:07:21 -0400 Message-ID: Subject: Re: [IPP] Updated draft of IPP Transactional Printing Extensions (formerly Paid Printing Extensions) From: Ira McDonald To: Paul Tykodi , 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="===============0076520596==" 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: B66EB79218.A95B4 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0076520596== Content-Type: multipart/alternative; boundary=089e013c61e097dd4a04dfee7988 --089e013c61e097dd4a04dfee7988 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Paul, The working decision (subject to change) at today's IPP call was "IPP Transaction-based Printing Extensions" and we agreed to take the new finishings out and update PWG 5100.1 (similar to what we did w/ MSN2). 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 Mon, Jun 24, 2013 at 6:50 PM, Paul Tykodi wrote: > Hi Mike,**** > > ** ** > > I agree with Glen=92s comment that Transactional Printing has a different > meaning than what we want to convey in this specification. I think that > =93Transaction=94 will be understood correctly.**** > > ** ** > > 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 *P= etrie, > Glen > *Sent:* Monday, June 24, 2013 12:20 PM > *To:* Michael Sweet; ipp@pwg.org > *Subject:* RE: [IPP] Updated draft of IPP Transactional Printing > Extensions (formerly Paid Printing Extensions)**** > > ** ** > > Mike**** > > ** ** > > I was a little surprised at your new title. "Transactional Printing" has > for a very, very long time meant the "printing of voices, bills, > statements, notices, checks, letters, etc.". While I have noted that it > is not uncommon for PWG to "extent" the meaning of terms; might I suggest > "Transaction" versus Transactional to avoid confusion.**** > > ** ** > > Glen**** > > ** ** > > ** ** > ------------------------------ > > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] > *On Behalf Of *Michael Sweet > *Sent:* Monday, June 24, 2013 8:17 AM > *To:* ipp@pwg.org > *Subject:* [IPP] Updated draft of IPP Transactional Printing Extensions > (formerly Paid Printing Extensions)**** > > ** ** > > All,**** > > ** ** > > I have posted an updated stable draft of the IPP Transactional Printing > Extensions (formerly the IPP Paid Printing Extensions) to:**** > > ** ** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.docx**** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624.pdf**** > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrans10-20130624-rev.pdf**** > > ** ** > > Aside from the name change and some template changes, I've added > additional terms, explanatory text, and references (including an > informative reference to CIP4's PrintTalk specification) to hopefully all= ay > any confusion and tie everything together cleanly.**** > > ** ** > > _________________________________________________________ > 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 > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --089e013c61e097dd4a04dfee7988 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi Paul,

The w= orking decision (subject to change) at today's IPP call was
&q= uot;IPP Transaction-based Printing Extensions" and we agreed to
tak= e the new finishings out and update PWG 5100.1 (similar to
what we did w/ MSN2).

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-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 Mon, Jun 24, 2013 at 6:50 PM, Paul Ty= kodi <ptykodi@tykodi.com> wrote:

Hi Mike,

=A0

I agree with Glen=92s comment that Transactio= nal Printing has a different meaning than what we want to convey in this sp= ecification. I think that =93Transaction=94 will be understood correctly.

=A0<= /p>

Best Regards,

=A0<= /p>

/Paul

--

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

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

From: ipp-bounces@= pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Monday, June 24, 2013 12:20 PM
To: Michael Sweet; ipp@pwg.org
Subjec= t: RE: [IPP] Updated draft of IPP Transactional Printing Extensions (fo= rmerly Paid Printing Extensions)

=A0=

Mike

=A0

I was a little surprised at your new title.=A0 &qu= ot;Transactional Printing" has for a very, very long time meant the &q= uot;printing of voices, bills, statements, notices, checks, letters, etc.&q= uot;.=A0 =A0=A0While I have noted that it is not uncommon for PWG to "= extent" the meaning of terms; might I suggest "Transaction" = versus Transactional to avoid confusion.

=A0

Glen

=A0

=A0

=

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Beh= alf Of Michael Sweet
Sent: Monday, June 24, 2013 8:17 AM
To: ipp@pwg.org
Subject: [IPP] Upd= ated draft of IPP Transactional Printing Extensions (formerly Paid Printing= Extensions)

=A0

Al= l,

=A0

=

I have posted an updated stable draft of the IP= P Transactional Printing Extensions (formerly the IPP Paid Printing Extensi= ons) to:

=A0

=A0

Aside from the name change and some template changes, I've adde= d additional terms, explanatory text, and references (including an informat= ive reference to CIP4's PrintTalk specification) to hopefully allay any= confusion and tie everything together cleanly.

=A0

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

=A0


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


--
T= his 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. --089e013c61e097dd4a04dfee7988-- --===============0076520596== 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 --===============0076520596==-- From ipp-bounces@pwg.org Mon Jun 24 20:48:00 2013 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 71B5221F9007 for ; Mon, 24 Jun 2013 20:48:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 M5FmDfWXoZJR for ; Mon, 24 Jun 2013 20:47:55 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA4A21F9CE5 for ; Mon, 24 Jun 2013 20:47:49 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1AFEB79224; Mon, 24 Jun 2013 23:47:24 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from inet-gw1.brother.co.jp (brother-gw1.brother.co.jp [211.125.189.57]) by pwg.org (Postfix) with ESMTP id 218A67921F for ; Mon, 24 Jun 2013 23:46:58 -0400 (EDT) Received: from apbilex12.ap.brothergroup.net ([10.113.10.11]) by inet-gw1.brother.co.jp (8.11.7p1+Sun/8.11.7) with ESMTP id r5P3kkn13853 for ; Tue, 25 Jun 2013 12:46:46 +0900 (JST) Received: from APBILEX03.ap.brothergroup.net ([10.113.10.15]) by apbilex12.ap.brothergroup.net ([10.113.10.11]) with mapi; Tue, 25 Jun 2013 12:46:46 +0900 From: To: Date: Tue, 25 Jun 2013 12:46:45 +0900 Subject: [IPP] Brother has reviewed the IPP FaxOut specification and has one comment Thread-Topic: [IPP] Brother has reviewed the IPP FaxOut specification and has one comment Thread-Index: Ac5xVUIBubjmCEtdSIOHcLGXXWRzWA== Message-ID: <6703CFED36A3AC41B08E356DF9C11982233D1240DB@APBILEX03.ap.brothergroup.net> Accept-Language: en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: , 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: 1AFEB79224.A78C8 X-pwg-MailScanner-From: ipp-bounces@pwg.org Dear All, Brother found two different attribute names for retry timeout. Section 7.2.6, 7.4.28 and 7.4.29 "retry-time-out" Section 4.3 and 4.5 "retry-timeout" It should be "retry-time-out" (a hyphen is required between "time" and "out= ") to match with the Semantic Model's "RetryTimeOut". =20 Regards, =20 O'Hara =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D Kiyotaka O'Hara Software Development Dept. 1 Brother Industries, ltd mailto: kiyotaka.ohara@brother.co.jp TEL +81-52-824-2345 ext 5090 FAX +81-52-811-3030 --=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 https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Tue Jun 25 10:22:30 2013 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 07E2611E8114 for ; Tue, 25 Jun 2013 10:22:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.534 X-Spam-Level: X-Spam-Status: No, score=0.534 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, UNRESOLVED_TEMPLATE=3.132] 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 J0qwC16s8EiZ for ; Tue, 25 Jun 2013 10:22:20 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7C021F9A86 for ; Tue, 25 Jun 2013 10:22:17 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0E2937922B; Tue, 25 Jun 2013 13:21:34 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by pwg.org (Postfix) with ESMTP id D290579227 for ; Tue, 25 Jun 2013 13:21:09 -0400 (EDT) Received: from BY2FFO11FD019.protection.gbl (10.1.15.200) by BY2FFO11HUB009.protection.gbl (10.1.14.167) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 25 Jun 2013 17:20:55 +0000 Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD019.mail.protection.outlook.com (10.1.14.107) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 25 Jun 2013 17:20:55 +0000 Received: from co1outboundpool.messaging.microsoft.com (157.54.51.80) by mail.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.3.136.1; Tue, 25 Jun 2013 17:19:44 +0000 Received: from mail109-co1-R.bigfish.com (10.243.78.242) by CO1EHSOBE008.bigfish.com (10.243.66.71) with Microsoft SMTP Server id 14.1.225.23; Tue, 25 Jun 2013 17:19:01 +0000 Received: from mail109-co1 (localhost [127.0.0.1]) by mail109-co1-R.bigfish.com (Postfix) with ESMTP id 2584460028E for ; Tue, 25 Jun 2013 17:19:01 +0000 (UTC) X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT002.namprd03.prod.outlook.com; R:internal; EFV:INT X-SpamScore: 5 X-BigFish: PS5(zzc85fhzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hz31iz1d7338h17326ah18c673h8275bh8275dhz31h2a8h668h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh17ej9a9j1155h) Received-SPF: softfail (mail109-co1: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=justhu@microsoft.com; helo=BL2PRD0310HT002.namprd03.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(189002)(199002)(47446002)(79102001)(47976001)(15202345003)(49866001)(54356001)(31966008)(54316002)(76796001)(16236675002)(76482001)(56816003)(74366001)(76786001)(76176001)(56776001)(59766001)(76576001)(50986001)(19300405004)(47736001)(77096001)(53806001)(69226001)(74502001)(63696002)(81342001)(16406001)(74316001)(74662001)(51856001)(81542001)(46102001)(73894003)(74706001)(77982001)(33646001)(65816001)(4396001)(80022001)(74876001)(24736002)(3826001)(491001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB134; H:BLUPR03MB133.namprd03.prod.outlook.com; RD:InfoNoRecords; MX:1; A:1; LANG:; Received: from mail109-co1 (localhost.localdomain [127.0.0.1]) by mail109-co1 (MessageSwitch) id 13721807409526_20048; Tue, 25 Jun 2013 17:19:00 +0000 (UTC) Received: from CO1EHSMHS005.bigfish.com (unknown [10.243.78.226]) by mail109-co1.bigfish.com (Postfix) with ESMTP id EA8B016006C; Tue, 25 Jun 2013 17:18:59 +0000 (UTC) Received: from BL2PRD0310HT002.namprd03.prod.outlook.com (157.56.240.21) by CO1EHSMHS005.bigfish.com (10.243.66.15) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 25 Jun 2013 17:18:59 +0000 Received: from BLUPR03MB134.namprd03.prod.outlook.com (10.255.212.14) by BL2PRD0310HT002.namprd03.prod.outlook.com (10.255.97.37) with Microsoft SMTP Server (TLS) id 14.16.324.0; Tue, 25 Jun 2013 17:18:58 +0000 Received: from BLUPR03MB133.namprd03.prod.outlook.com (10.255.212.11) by BLUPR03MB134.namprd03.prod.outlook.com (10.255.212.14) with Microsoft SMTP Server (TLS) id 15.0.702.21; Tue, 25 Jun 2013 17:18:57 +0000 Received: from BLUPR03MB133.namprd03.prod.outlook.com ([169.254.2.117]) by BLUPR03MB133.namprd03.prod.outlook.com ([169.254.2.117]) with mapi id 15.00.0702.005; Tue, 25 Jun 2013 17:18:57 +0000 From: Justin Hutchings To: "'ipp@pwg.org'" , Ira McDonald , "ptykodi@tykodi.com" , Michael R Sweet Thread-Topic: Microsoft has reviewed the IPP FaxOut specification and has no comments Thread-Index: Ac5xyAAAJadKVY7hSIerBhs0+aay1g== Date: Tue, 25 Jun 2013 17:18:56 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:4898:1b:2:25a6:e8ca:b8e:1754] x-forefront-prvs: 0888B1D284 MIME-Version: 1.0 X-OrganizationHeadersPreserved: BLUPR03MB134.namprd03.prod.outlook.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%TYKODI.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%APPLE.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%PWG.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%GMAIL.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn% X-CrossPremisesHeadersPromoted: TK5EX14MLTC103.redmond.corp.microsoft.com X-CrossPremisesHeadersFiltered: TK5EX14MLTC103.redmond.corp.microsoft.com X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(77982001)(74502001)(19300405004)(71186001)(81542001)(31966008)(74316001)(59766001)(44976004)(6806003)(47446002)(76482001)(16676001)(564344003)(79102001)(33646001)(76576001)(15202345003)(54316002)(54356001)(76796001)(46102001)(74366001)(77096001)(76176001)(512954002)(56776001)(81342001)(76786001)(56816003)(53806001)(51856001)(74662001)(50986001)(16236675002)(74706001)(65816001)(63696002)(20776003)(74876001)(4396001)(47976001)(49866001)(69226001)(80022001)(47736001)(3826001)(24736002)(491001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB009; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:; X-OriginatorOrg: microsoft.onmicrosoft.com X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY) X-Forefront-PRVS: 0888B1D284 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Microsoft has reviewed the IPP FaxOut specification and has no comments 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="===============1363733714==" 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: 0E2937922B.A9777 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1363733714== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_a8b0ed37bdb64426a1becec39e0ed0deBLUPR03MB133namprd03pro_" --_000_a8b0ed37bdb64426a1becec39e0ed0deBLUPR03MB133namprd03pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_a8b0ed37bdb64426a1becec39e0ed0deBLUPR03MB133namprd03pro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_a8b0ed37bdb64426a1becec39e0ed0deBLUPR03MB133namprd03pro_-- --===============1363733714== 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 --===============1363733714==-- From ipp-bounces@pwg.org Tue Jun 25 22:42:46 2013 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 5298521E80A6 for ; Tue, 25 Jun 2013 22:42:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 T1IiS22xgovW for ; Tue, 25 Jun 2013 22:42:40 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 14D5221E8053 for ; Tue, 25 Jun 2013 22:42:40 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1BC9379219; Wed, 26 Jun 2013 01:41:57 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from g4t0017.houston.hp.com (g4t0017.houston.hp.com [15.201.24.20]) by pwg.org (Postfix) with ESMTP id 82AA0791F9 for ; Wed, 26 Jun 2013 01:41:31 -0400 (EDT) Received: from G4W6310.americas.hpqcorp.net (g4w6310.houston.hp.com [16.210.26.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t0017.houston.hp.com (Postfix) with ESMTPS id E35FA3855B; Wed, 26 Jun 2013 05:41:30 +0000 (UTC) Received: from G4W6301.americas.hpqcorp.net (16.210.26.226) by G4W6310.americas.hpqcorp.net (16.210.26.217) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 26 Jun 2013 05:39:56 +0000 Received: from G4W3295.americas.hpqcorp.net ([169.254.3.144]) by G4W6301.americas.hpqcorp.net ([16.210.26.226]) with mapi id 14.03.0123.003; Wed, 26 Jun 2013 05:39:56 +0000 From: "Kennedy, Smith (Wireless Architect)" To: "ipp@pwg.org" , Ira McDonald , Paul Tykodi , Michael Sweet Thread-Topic: Hewlett-Packard has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOci+WWghHbVx4ZUW16B+Hbnrb6A== Date: Wed, 26 Jun 2013 05:39:55 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [15.201.58.15] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Hewlett-Packard has reviewed the IPP FaxOut specification and has comments 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="===============0394586334==" 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: 1BC9379219.A96D6 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0394586334== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_E867EB01-3629-43A7-96F5-0D483253DEA5"; protocol="application/pkcs7-signature"; micalg=sha1 --Apple-Mail=_E867EB01-3629-43A7-96F5-0D483253DEA5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Greetings, Below are comments from HP regarding the IPP FaxOut specification final cal= l (wd-ippfaxout10-20130501.pdf). Cheers, Smith /** Smith Kennedy Hewlett-Packard Co. smith.kennedy@hp.com */ 4.1.2: - The notion of "spooling vs. streaming" seems to assume that a device is o= ne or the other, regardless of the job size. I don't think this is necessa= rily the case. Some spooling devices may have expansive secondary storage = such as a hard disk. But some spooling devices may support spooling up to = some much more restricted limit, such as 5-10 pages, if they are storing it= in RAM. For these devices, one might expect spooling support up to some j= ob size, and beyond that it should be used as a streaming device. But how = should this be handled and enforced? Client side, or FaxOut service side? = Or should such devices always present themselves as streaming devices to c= lients, and not try to spool small fax jobs?=20=20 - Exactly how does the IPP FaxOut Printer Object communicate to the IPP cli= ent that it is streaming vs. spooling? Should it be done using the maximum= size of an incoming fax job, using one of the following? - job-k-octets-supported (RFC 2911) - *-k-octets-supported if it depends on the format? If not in this manner, which seems non-optimal because it is basically an i= mplied interpolation, an explicit attribute seems necessary. - Is the error handling described here adequate? Under what conditions wou= ld there need to be "larger portions of the job" retransmitted? Only in th= e event of a phone line connection failure? In that case, would the sendin= g fax only send the pages unsent? Or would it be expected to resend the en= tire job? Are retries in the "processing" state? 4.1.4: - Why must the job be retained for 300 seconds? A streaming device will on= ly retain the last page. - Feedback: "(section 7.4.21)" should be "(section 7.4.22)". This logging = facility is confusing and seems incompletely described, here or in 7.4.22. 4.2: - Note 1: "MUST NOT" for Print-Job operation? That seems a bit extreme=85 = Is this expected to be only true for the /ipp/faxout Printer Object but no= t for the /ipp/print Printer Object (if present)? 4.3: - What is the purpose of margins here? Is this just for rendering local to= the IPP Faxout device? (Guessing the answer is yes=85) - "pages-per-minute" and "pages-per-minute-color" - how will this be determ= ined for fax? - Should there be an "include-fax-header" job attribute? (this is a page he= ader with the sender's name & #, date, time, page X of Y, etc.) Legal req= uirements around this? - "Note 4" seems to not have any attributes that reference it. Was this su= pposed to be referenced by the "input-source-supported" attribute? 6.1: - Send-Hardcopy-Document operation and streaming devices and a resend - wil= l the client be expected to resend if the job included a Send-Hardcopy-Docu= ment operation? 7.2.2.3: - What document formats must be supported by the printer for the logo? Siz= e limits? JPS3 had the printer-icons attribute defined in such a way that = the icon must be in a particular format (PNG) and particular sizes. - Guessing that the schemes supported could be determined by "reference-uri= -schemes-supported" but that attribute is not listed in the IPP FaxOut spec= at all 7.4.22: - How is this intended to work? Can this be a URI to a service on a host o= ther than the one hosting the IPP FaxOut Printer Object? What should happe= n if the fax log hits a size limit? Is the size limit advertised? 7.4.26: - Should this value be the country-defined value? 7.4.27: - What is the point of retry-interval-supported for streaming devices? And= which entity is responsible for keeping count for the retries? Is it the = IPP FaxOut device, or the client?= --Apple-Mail=_E867EB01-3629-43A7-96F5-0D483253DEA5 Content-Disposition: attachment; filename="smime.p7s" Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIH2zCCB9cwgga/oAMCAQICEDzl31FCOqLzbMj/pfKLsWUwDQYJKoZI hvcNAQEFBQAwgfcxCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdIZXdsZXR0LVBh Y2thcmQgQ29tcGFueTEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxNTAzBgNVBAsTLENsYXNzIDIgTWFuYWdlZCBQ S0kgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBMTEwLwYDVQQDEyhDb2xsYWJv cmF0aW9uIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IEcyMB4XDTEyMTEyNjAw MDAwMFoXDTE0MTEyNjIzNTk1OVowgZgxIDAeBgNVBAoUF0hld2xldHQtUGFj a2FyZCBDb21wYW55MSYwJAYDVQQLFB1FbXBsb3ltZW50IFN0YXR1cyAtIEVt cGxveWVlczEPMA0GA1UECxMGUy9NSU1FMRYwFAYDVQQDEw1TbWl0aCBLZW5u ZWR5MSMwIQYJKoZIhvcNAQkBFhRzbWl0aC5rZW5uZWR5QGhwLmNvbTCCASIw DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmoHmmwCMk0tCSI1w6tYppe JX3YINwFC5wUIhCt8HcRW/Ass9n7BxP1MpBUScmYpaQOjFI+n6JueqNNlmHy sW9wFG8FiSxowAf2C6cN+kmrV1MOzprrpjZZTB979lqRD/UG5RCo4BNy3aTT tqMFk7JkrL1QH8yLa5IOgUd36N7bK3+nSz6W3X3jo5G8Eax5xJvwCioOQzzm clRKpoDRKFT35bHptUCD0VR7IY749Ik7+A4RBp52w7zKYrs6N59Hy0PxxEzO sQImUC7++mhRJtg5AdX75wAKb665v3b4RZjJBMQhjYdU8Al3e/iq362nUqJm rFbNhpM9LSapjpbCm7ECAwEAAaOCA7owggO2MB8GA1UdEQQYMBaBFHNtaXRo Lmtlbm5lZHlAaHAuY29tMAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/BAQDAgWg MFkGA1UdHwRSMFAwTqBMoEqGSGh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24u Y29tL0hld2xldHRQYWNrYXJkQ29tcGFueVNNSU1FRzIvTGF0ZXN0Q1JMLmNy bDAfBgNVHSMEGDAWgBQifdOkq1esVn+pf0FEGpW8W/ir7jAdBgNVHQ4EFgQU 2ugcyk1Ph3Uvd67i/95+2TE174IwggEyBggrBgEFBQcBAQSCASQwggEgMCcG CCsGAQUFBzABhhtodHRwOi8vaHAtb2NzcC52ZXJpc2lnbi5jb20wgfQGCCsG AQUFBzACpIHnMIHkMTEwLwYDVQQDEyhDb2xsYWJvcmF0aW9uIENlcnRpZmlj YXRpb24gQXV0aG9yaXR5IEcyMTAwLgYDVQQLEydDbGFzcyAyIE9uU2l0ZSBJ bmRpdmlkdWFsIFN1YnNjcmliZXIgQ0ExOjA4BgNVBAsTMVRlcm1zIG9mIHVz ZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhKGMpMDkxHzAdBgNV BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxIDAeBgNVBAoTF0hld2xldHQt UGFja2FyZCBDb21wYW55MIIBPQYDVR0gBIIBNDCCATAwggEsBgtghkgBhvhF AQcXAjCCARswKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv bS9ycGEwge4GCCsGAQUFBwICMIHhMB4WF0hld2xldHQtUGFja2FyZCBDb21w YW55MAMCAQIagb5BdXRob3JpdHkgdG8gYmluZCBIUCBkb2VzIG5vdCBjb3Jy ZXNwb25kIHdpdGggdXNlIG9yIHBvc3Nlc3Npb24gb2YgdGhpcyBjZXJ0aWZp Y2F0ZS4gSXNzdWVkIHRvIGZhY2lsaXRhdGUgY29tbXVuaWNhdGlvbiB3aXRo IEhQLiBWZXJpU2lnbidzIENQUyBpbmNvcnAuIEJ5IHJlZmVyZW5jZSBsaWFi LiBsdGQuIChjKTk3IFZlcmlTaWduMBYGA1UdJQEB/wQMMAoGCCsGAQUFBwME MEsGCSqGSIb3DQEJDwQ+MDwwDgYIKoZIhvcNAwICAgCAMA4GCCqGSIb3DQMC AgIAQDAOBggqhkiG9w0DBAICAIAwCgYIKoZIhvcNAwcwDQYJKoZIhvcNAQEF BQADggEBAImyDkwpuUnbTsboOwpQAPQ4M1jbZkfWS/mLo6oj6XOWApq9IQ1j kwowCWwwCA3F3wCbKQGphJ8HdLaVGY9AznOEQoixLHx9rnITaq9lFeagCZiq tFq6/i33etWRb6dXp3FZYn9ikhYv74Ewil/ue61VqW9vOAZq51Wt9JznLmVS kJN11A4oJxNL8/jiK82tSXMkUHe07VbZUUF+t609D979rvVK68sw6P+cDe+4 6gy6oM9LHtINt8Fclro/45hQe0FdW1A1dmyx4dyKW/SbRK4uw5c0nXvaZn0W rlnq2Rxm/wCNKnGxAtp0ir7/7ubR6GjB3xufBjNLp57JgbuFIg4xggTeMIIE 2gIBATCCAQwwgfcxCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdIZXdsZXR0LVBh Y2thcmQgQ29tcGFueTEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxNTAzBgNVBAsTLENsYXNzIDIgTWFuYWdlZCBQ S0kgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBMTEwLwYDVQQDEyhDb2xsYWJv cmF0aW9uIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IEcyAhA85d9RQjqi82zI /6Xyi7FlMAkGBSsOAwIaBQCgggKlMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDYyNjA1Mzk1NlowIwYJKoZIhvcNAQkE MRYEFP+8MjDgOsBPO8YIgwGPKwA9cD7vMIIBHwYJKwYBBAGCNxAEMYIBEDCC AQwwgfcxCzAJBgNVBAYTAlVTMSAwHgYDVQQKExdIZXdsZXR0LVBhY2thcmQg Q29tcGFueTEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkG A1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv bS9ycGEgKGMpMDkxNTAzBgNVBAsTLENsYXNzIDIgTWFuYWdlZCBQS0kgSW5k aXZpZHVhbCBTdWJzY3JpYmVyIENBMTEwLwYDVQQDEyhDb2xsYWJvcmF0aW9u IENlcnRpZmljYXRpb24gQXV0aG9yaXR5IEcyAhA85d9RQjqi82zI/6Xyi7Fl MIIBIQYLKoZIhvcNAQkQAgsxggEQoIIBDDCB9zELMAkGA1UEBhMCVVMxIDAe BgNVBAoTF0hld2xldHQtUGFja2FyZCBDb21wYW55MR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQg aHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTE1MDMGA1UECxMs Q2xhc3MgMiBNYW5hZ2VkIFBLSSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0Ex MTAvBgNVBAMTKENvbGxhYm9yYXRpb24gQ2VydGlmaWNhdGlvbiBBdXRob3Jp dHkgRzICEDzl31FCOqLzbMj/pfKLsWUwDQYJKoZIhvcNAQEBBQAEggEAhaQ/ H868UTYyCh8Za1vD4WARK5RbIjnyfMYCtka7QYZZb5LQzuvxK9CnDKR3tPil 8R+n0MunUW79xxTfSVFEDdjmtFt5Tr1rb/oVPqUOY0w5pz/bQyj/uCnGuX2z Yc5yTWZBuIxOythFvzZf6a4jKPhqeVVvpQiGESKSTQRkUF59rpcVfiBGnsJa JJCnsavs1+Nd7y9Jk4E6lxsO9gHUBWGr5mfstNCTcys2IVI2sdKQ7u7xWhwk y3qs9MmA0Pmr0be/PD67kcmw0xjVGnDfN8rjlk3Z81otuqx8A/NxfBy/c4xM 4LVCokFPA5sJ/lxZuOKrV+3J9a7aKT7SFnXd7QAAAAAAAA== --Apple-Mail=_E867EB01-3629-43A7-96F5-0D483253DEA5-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --===============0394586334== 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 --===============0394586334==-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From pwg-announce-bounces@pwg.org Wed Jun 26 01:54:53 2013 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 36A2A21E80FC for ; Wed, 26 Jun 2013 01:54:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 quwNXJy9SqUI for ; Wed, 26 Jun 2013 01:54:48 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id BD6FE11E81A4 for ; Wed, 26 Jun 2013 01:54:47 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 4598579231; Wed, 26 Jun 2013 04:54:02 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by pwg.org (Postfix) with ESMTP id A34D379230 for ; Wed, 26 Jun 2013 04:53:39 -0400 (EDT) Received: by mail-ie0-f169.google.com with SMTP id 10so31080182ied.28 for ; Wed, 26 Jun 2013 01:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=AyC7YWLgK3uqv1paTvdjtCrCzRL8eVKWDxnWXwCUKao=; b=tuWcRmkZtDL5LVhJ6Vv1lmZ6n5fpjaIpfNhyyvO17EPHiYshIal/AxV8BzWSZG0BKE 3nALjBAkcxQsUJ7ufaLnuT0Txdeui0Sf0d3LuGOGI2U9Nk4XbWGQ2Lo7M4Aw3tX6k3x6 u2QRaiBQH46tLTagf5IOnMSL9rKLTvUZOYztaQLB2o9NhwuaSmtTv5NVQmzkLq2+PrK3 cWoqSUSctOpB+sYLTX8NPL63HY0GPD5fvYXNYAenxLf/gCl4IE0539APNHX/QeYSYQlr jxoDxhGruVjJT7TC91YJA7s4cTgPUN+mje+RoY5ZhYwDByePliKx49lD5JHf5nFrJdNj C+uA== MIME-Version: 1.0 X-Received: by 10.50.176.166 with SMTP id cj6mr1643627igc.56.1372236818967; Wed, 26 Jun 2013 01:53:38 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Wed, 26 Jun 2013 01:53:38 -0700 (PDT) Date: Wed, 26 Jun 2013 04:53:38 -0400 Message-ID: From: Ira McDonald To: Michael Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "PWG Announcements Inc." Subject: [Pwg-Announce] REMINDER - EXTENDED: PWG Last Call of IPP FaxOut Service (05/01/13 to 06/28/13) 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="===============1716786201==" 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: 4598579231.AD329 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1716786201== Content-Type: multipart/alternative; boundary=e89a8f6435a22474ef04e00ac8f1 --e89a8f6435a22474ef04e00ac8f1 Content-Type: text/plain; charset=ISO-8859-1 Hi, We now need ONE more PWG member to acknowledge this PWG Last Call on IPP FaxOut (with or without comments) in order to reach quorum by the close of this PWG Last Call this Friday 28 June. Please exercise your membership privileges and help out. Cheers, - Ira (PWG Secretary) 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 Mon, Jun 10, 2013 at 3:35 PM, Michael Sweet wrote: > All, > > Because we have not yet reached quorum, we need to extend the PWG Last > Call of the IPP FaxOut Service specification to Friday, June 28, 2013 at > 10pm US PT. > > Thank you everyone that has already responded to the last call. If you > have not yet provided your acknowledgement for the IPP FaxOut Service > specification, please do so at your earliest convenience. > > Thank you! > > > On May 1, 2013, at 2:41 PM, Michael Sweet wrote: > > All, > > [This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday > June 7, 2013 at 10pm US PST.] > > This is the formal announcement of the PWG Last Call for the IPP FaxOut > Service specification, located at: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.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 an IPP WG > 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. > > > HOW TO RESPOND > > Send an email with *exactly* the following subject line format: > Subject: has reviewed the IPP FaxOut specification and has > [no] comments > > > WHERE TO SEND YOUR RESPONSE > > Please send your response to *all* of the following email addresses > (replacing "dot" with '.' and "at" with '@'): > > ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!) > blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) > ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) > msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP > FaxOut Editor) > > Note that you must be subscribed to the IPP WG mailing list to send email > there - otherwise your email will be silently discarded. > > 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 > > > _________________________________________________________ > 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 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e89a8f6435a22474ef04e00ac8f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

We now need= ONE more PWG member to acknowledge this PWG Last Call
on IPP FaxO= ut (with or without comments) in order to reach quorum by the
clos= e of this PWG Last Call this Friday 28 June.

Please exercise your membership privileges and help out.

<= /div>Cheers,
- Ira (PWG Secretary)



Ira McDonald (Musician / Software Architect)<= br> 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 D= esignated 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 Mon, Jun 10, 2013 at 3:35 PM, Michael= Sweet <msweet@apple.com> wrote:
All,

Because we have= not yet reached quorum, we need to extend the PWG Last Call of the IPP Fax= Out Service specification to Friday, June 28, 2013 at 10pm US PT.

Thank you everyone that has already responded to the last ca= ll. =A0If you have not yet provided your acknowledgement for the IPP FaxOut= Service specification, please do so at your earliest convenience.

Thank you!


On May 1, = 2013, at 2:41 PM, Michael Sweet <msweet@apple.com> wrote:

All,

[This PWG Last Call starts = today Wednesday May 1, 2013 and ends Friday June 7, 2013=A0at 10pm US PST.]=

This is the formal announcement of the PWG Last Call for the IPP Fa= xOut Service=A0specification, located at:

ftp://ftp.= pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf

All required = attributes and values defined in this document have been prototyped by Appl= e=A0and/or other vendors. The IPP WG has completed extensive review of the = various revisions=A0of this document and an IPP WG last call.

The PWG Process/3.0 requires that a quorum (30%) of PWG voting members = must acknowledge a=A0PWG Last Call (with or without comments), before any d= ocument can progress to PWG Formal=A0Vote. =A0This PWG Last Call is NOT a F= ormal Vote but it DOES require your review=A0acknowledgment.


HOW TO RESPOND

Send an email with *exactly* the following su= bject line format:
Subject: <Company Name> has reviewed the IPP Fa= xOut specification and has [no] comments


WHERE TO SEND YOUR RESP= ONSE

Please send your response to *all* of the following email addresses (re= placing "dot" with=A0'.' and "at" with '@&#= 39;):

ipp "at" pwg "dot" org (IPP WG mailing lis= t - you must be subscribed!)
blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP W= G Co-Chair)
ptykodi "at" tykodi "dot" com (Paul Tyko= di, IPP WG Co-Chair)
msweet "at" apple "dot" com (Mi= chael Sweet, IPP WG Secretary and IPP FaxOut Editor)

Note that you must be subscribed to the IPP WG mailing list to send ema= il there -=A0otherwise your email will be silently discarded.

Please= do NOT simply reply to this note on the PWG-Announce list.

Note: Th= e PWG Definition of the Standards Development Process Version 3.0 is locate= d at:

http://www.p= wg.org/chair/membership_docs/pwg-process30.pdf

_____________________________= ____________________________
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.
_______________________________________________
pwg-announce mailing lis= t
pwg-announce= @pwg.org
https://www.pwg.org/mailman/listinfo/pwg-announce<= br>

_________________________________________________________
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.

_______________________________________________
pwg-announce mailing list
pwg-announce@pwg.org
https://www.pwg.org/mailman/listinfo/pwg-announce



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e89a8f6435a22474ef04e00ac8f1-- --===============1716786201== 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 --===============1716786201==-- From pwg-announce-bounces@pwg.org Wed Jun 26 03:15:10 2013 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 70C1121E8128 for ; Wed, 26 Jun 2013 03:15:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 IB53aCiKkfS6 for ; Wed, 26 Jun 2013 03:15:04 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id CD6D921E812C for ; Wed, 26 Jun 2013 03:15:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1A8647923E; Wed, 26 Jun 2013 06:14:13 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from USA7109MR002.ACS-INC.COM (usa7109mr002.acs-inc.com [63.101.151.11]) by pwg.org (Postfix) with ESMTP id 8B75E7923D for ; Wed, 26 Jun 2013 06:13:48 -0400 (EDT) Received: from usa7109ht003.na.xerox.net ([13.41.230.29]) by USA7109MR002.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 26 Jun 2013 05:13:39 -0500 Received: from USA7109MB006.na.xerox.net ([169.254.5.152]) by USA7109HT003.na.xerox.net ([13.41.230.29]) with mapi id 14.02.0309.002; Wed, 26 Jun 2013 05:13:38 -0500 From: "Sukert, Alan" To: Ira McDonald , Michael Sweet Subject: RE: [Pwg-Announce] REMINDER - EXTENDED: PWG Last Call of IPP FaxOut Service (05/01/13 to 06/28/13) Thread-Topic: [Pwg-Announce] REMINDER - EXTENDED: PWG Last Call of IPP FaxOut Service (05/01/13 to 06/28/13) Thread-Index: AQHOckrSYJKzXCcV9kOqtu20CPk89ZlHxsAg Date: Wed, 26 Jun 2013 10:13:38 +0000 Message-ID: <772924F5A52E6846866619AB345D308832F0F3@USA7109MB006.na.xerox.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.83] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "PWG Announcements Inc." 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="===============0684755340==" 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: 1A8647923E.AC6CB X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0684755340== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_772924F5A52E6846866619AB345D308832F0F3USA7109MB006naxer_" --_000_772924F5A52E6846866619AB345D308832F0F3USA7109MB006naxer_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ira - I'll give it a review and vote. Just may not be able to do it until Friday = if that's OK. Alan From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On= Behalf Of Ira McDonald Sent: Wednesday, June 26, 2013 4:54 AM To: Michael Sweet; Ira McDonald Cc: PWG Announcements Inc. Subject: [Pwg-Announce] REMINDER - EXTENDED: PWG Last Call of IPP FaxOut Se= rvice (05/01/13 to 06/28/13) Hi, We now need ONE more PWG member to acknowledge this PWG Last Call on IPP FaxOut (with or without comments) in order to reach quorum by the close of this PWG Last Call this Friday 28 June. Please exercise your membership privileges and help out. Cheers, - Ira (PWG Secretary) 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 Mon, Jun 10, 2013 at 3:35 PM, Michael Sweet > wrote: All, Because we have not yet reached quorum, we need to extend the PWG Last Call= of the IPP FaxOut Service specification to Friday, June 28, 2013 at 10pm U= S PT. Thank you everyone that has already responded to the last call. If you hav= e not yet provided your acknowledgement for the IPP FaxOut Service specific= ation, please do so at your earliest convenience. Thank you! On May 1, 2013, at 2:41 PM, Michael Sweet > wrote: All, [This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June= 7, 2013 at 10pm US PST.] This is the formal announcement of the PWG Last Call for the IPP FaxOut Ser= vice specification, located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf All required attributes and values defined in this document have been proto= typed by Apple and/or other vendors. The IPP WG has completed extensive rev= iew of the various revisions of this document and an IPP WG 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 documen= t can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote= but it DOES require your review acknowledgment. HOW TO RESPOND Send an email with *exactly* the following subject line format: Subject: has reviewed the IPP FaxOut specification and has [= no] comments WHERE TO SEND YOUR RESPONSE Please send your response to *all* of the following email addresses (replac= ing "dot" with '.' and "at" with '@'): ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!) blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP FaxOut= Editor) Note that you must be subscribed to the IPP WG mailing list to send email t= here - otherwise your email will be silently discarded. 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 i= s 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 _________________________________________________________ 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 -- 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. --_000_772924F5A52E6846866619AB345D308832F0F3USA7109MB006naxer_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ira –

 <= /p>

I’ll give it a revi= ew and vote. Just may not be able to do it until Friday if that’s OK.=

 <= /p>

Alan

 <= /p>

From: pwg-anno= unce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Ira McDonald
Sent: Wednesday, June 26, 2013 4:54 AM
To: Michael Sweet; Ira McDonald
Cc: PWG Announcements Inc.
Subject: [Pwg-Announce] REMINDER - EXTENDED: PWG Last Call of IPP Fa= xOut Service (05/01/13 to 06/28/13)

 

Hi,

We now need ONE more PWG member to acknowledge this = PWG Last Call

on IPP FaxOut (with or without comments) in order to= reach quorum by the

close of this PWG Las= t Call this Friday 28 June.

Please exercise your = membership privileges and help out.

Cheers,

- Ira (PWG Secretary)=


Ira McDonald (Musicia= n / 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:blueroo= fmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094=
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434

 

On Mon, Jun 10, 2013 at 3:35 PM, Michael Sweet <<= a href=3D"mailto:msweet@apple.com" target=3D"_blank">msweet@apple.com&g= t; wrote:

All,

 

Because we have not yet reached quorum, we need to e= xtend the PWG Last Call of the IPP FaxOut Service specification to Friday, = June 28, 2013 at 10pm US PT.

 

Thank you everyone that has already responded to the= last call.  If you have not yet provided your acknowledgement for the= IPP FaxOut Service specification, please do so at your earliest convenienc= e.

 

Thank you!

 

 

On May 1, 2013, at 2:41 PM, Michael Sweet <msweet@apple.com> wr= ote:



All,

[This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June= 7, 2013 at 10pm US PST.]

This is the formal announcement of the PWG Last Call for the IPP FaxOut Ser= vice specification, located at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pd= f

All required attributes and values defined in this document have been proto= typed by Apple and/or other vendors. The IPP WG has completed extensiv= e review of the various revisions of this document and an IPP WG 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 do= cument can progress to PWG Formal Vote.  This PWG Last Call is NO= T a Formal Vote but it DOES require your review acknowledgment.


HOW TO RESPOND

Send an email with *exactly* the following subject line format:
Subject: <Company Name> has reviewed the IPP FaxOut specification and= has [no] comments


WHERE TO SEND YOUR RESPONSE

Please send your response to *all* of the following email addresses (replac= ing "dot" with '.' and "at" with '@'):

ipp "at" pwg "dot" org (IPP WG mailing list - you must = be subscribed!)
blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP W= G Co-Chair)
ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-C= hair)
msweet "at" apple "dot" com (Michael Sweet, IPP WG Secr= etary and IPP FaxOut Editor)

Note that you must be subscribed to the IPP WG mailing list to send email t= here - otherwise your email will be silently discarded.

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 i= s 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

 

_________________________________________________________=
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

 


--
This message has been scanned for viruses and
dangerous content by MailScanne= r, 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. --_000_772924F5A52E6846866619AB345D308832F0F3USA7109MB006naxer_-- --===============0684755340== 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 --===============0684755340==-- From ipp-bounces@pwg.org Wed Jun 26 09:05:51 2013 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 2EA8D21E80AB for ; Wed, 26 Jun 2013 09:05:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.303 X-Spam-Level: X-Spam-Status: No, score=-1.303 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MARKETING_PARTNERS=1.295] 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 G-UIqd5OOU-K for ; Wed, 26 Jun 2013 09:05:46 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id E458D11E81C6 for ; Wed, 26 Jun 2013 09:05:45 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D8215791DC; Wed, 26 Jun 2013 12:05:12 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from bware1.sdsamerica.net (bware1.sdsamerica.net [206.67.236.191]) by pwg.org (Postfix) with ESMTP id 4EEBC791DC for ; Wed, 26 Jun 2013 12:04:50 -0400 (EDT) From: Ron Nevo To: "'ipp@pwg.org'" Subject: [IPP] Samsung has reviewed the IPP Fax Out specification and has no comments Thread-Topic: [IPP] Samsung has reviewed the IPP Fax Out specification and has no comments Thread-Index: Ac5yhuKKBQFn2+LzSE+YhhqiG5vMoQ== Date: Wed, 26 Jun 2013 16:04:49 +0000 Message-ID: <1C6085AE4073A9448F7C718CC7EE1DEB0E2457@SEAMBX2.sea.samsung.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: MIME-Version: 1.0 Received-SPF: none 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="===============0660518789==" 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: D8215791DC.AA423 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0660518789== Content-Language: en-US Content-Type: multipart/related; boundary="_005_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_"; type="multipart/alternative" --_005_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_ Content-Type: multipart/alternative; boundary="_000_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_" --_000_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thank You, [Description: Description: samsung] Ron Nevo | Senior Manager | Product Marketing Partners, Solutions, Information Security, MPS, Standards and Certifications Chair IEEE/ISTO Printer Working Group-Cloud Imaging Samsung Electronics America, Inc. Enterprise Business Division 85 Challenger Road | Ridgefield Park, NJ 07660 P 201.329.6231 C 201.220.6348 rnevo@sea.samsung.com http://www.samsung.com/us/printersolutions/ [Print Plus Logo email version] --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

Thank You,<= /span>

 

Ron Nevo | Senior Manager | Product Marketing

Partn= ers, Solutions, Information Security, MPS, Standards and Certifications

Chair = IEEE/ISTO Printer Working Group-Cloud Imaging

Samsu= ng Electronics America, Inc.

Enter= prise Business Division

&nb= sp;

85 Chall= enger Road | Ridgefield Park, NJ 07660

P 201.329.6231   C 201.220.6348

rnevo@sea.sams= ung.com
http://= www.samsung.com/us/printersolutions/

3D"Print


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_-- --_005_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_ Content-Type: image/jpeg; name="image001.jpg" Content-Description: image001.jpg Content-Disposition: inline; filename="image001.jpg"; size=2235; creation-date="Wed, 26 Jun 2013 16:04:49 GMT"; modification-date="Wed, 26 Jun 2013 16:04:49 GMT" Content-ID: Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0N Dh0VFhEYIx8lJCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/ 2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7 Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAwAIADASIAAhEBAxEB/8QA HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1 dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU 1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2aiiigAop KxNW8ZaDouVu9QjMo/5ZRfO/5Dp+NVGMpO0VcTkoq7ZuUV5hqfxeYkppWmgD tJct/wCyj/GuV1Dxz4k1EkS6pJCh/ggxGP05/WuyGAqy30OWWLprbU9yub21 s133VzDAvrI4X+dYd34/8MWeQ2qxysP4YVL/AMhXhksjzPvmkaRj/E7Fj+tN 7V1xy6C+KRhLGy6I9dufi1osfFvZ3k/uVVB+prMn+ML/APLvooHvJP8A4CvN QQehBozW6wNBdDF4qq+p30nxd1c/6vTbJfqXP9RUB+LGvk8W1iP+AN/jXEZH rRketaLC0V9kn6xV7ndJ8WtdU/PZ2L/8BYf1q3B8YLoEfadHiYd/KmI/mK86 oBB6EGk8JQf2QWIqrqexaf8AFXQbpgl2lxZMe7ruUfiv+FdfZ3trqFutxZ3E c8LdHjYMK+bq3/BWs3mkeJbNbZ28q5mWKaLPDhjjOPUZzmuStgIcrcGdFLFy vaR7zXK+JPiBpOgM1uh+23i8GGI8If8AaboPp1rnviH45nguJND0mUxsgxcz qfmB/uKe3ufwrzKssNguZKdTbsaV8Vyvlge12HiPUtc8IJqOmW9rdXvmYubU nAVdxyoyeu3GM9a861qPTdW8a21vpenTWCzSxxz28sewh93Py9uK1/DMeiPo dtPp2sRaPrkLj7RJNKQJFBORtJwQRirmpa7oN78TNOvheQrbWcJ8256K7jO0 A98ZFaU17KcuVPr/AF5+RE3zwjzPt/X+ZqeI9H0e40jX7Wy0u1huNPiR1kii AYZXf1HsDWN8PrLS38M3t9f2FvcmO7VA00YYgHaO/wBan0jxPpUnirxKby/i is75QsUjn5XABXj8DWPoerWFh8OtYsGvYlvZJi0MWfmfG3BH5UKFRU3DXeP4 7jcoOalp1Oh0HQdMs9X1oXmn280bamltbrLGGCAjdgenDfpWRZaZozfFi7sb 2GFLVWPkQEARl9q4GOnqcVs6p4q0OS+0WS2v4dsl8Lm8IPEZEe3n9PyrnZrv w1qHxHvZ9UkWfTbjHlzKzBVfauCSOccEUU/aPmcr6r/gBPkVkrbmh4za3ttJ urTVfDsdpd+afsF3ZwgRFcjGW9cZyDVe/wBNsU+GmiXi2cK3MtzGskoQbmBZ sgnvWjq+q6dYeC9R0u412DV3nYiyRG3tGmRtBPPT1NVdOvNH13wLp2jzavb6 fc2M6vIJ+NwViePXINOLkoJ2dk/PsJpObXkP8U6Vp1t8R9Cs4LGCO3l2eZEk YCvlyOR3rT17Q9Ik1XTJbTTreJbXVEtrqNIwA6uARkdxyPzrC8ReI9Lv/iNp V9Bcq1nZtGsk/O3hiSR6gZrTtPFWif8ACZax9ov4/wCzroQTRTYOPMjA6cf5 xUuNRRi9dF+v+Q04NtablMaDpl38XJdOe0jFnHGJBAq4QkIOw7ZOak1S5sNT 0nWIbnwy0P2aSRLO6s7Q7RsyMs46cjntVYeJ9KtvirJq5uQ9hLGI/OQEgZQD OOuMiuv03QJToetR2upC5i1Z5Ht96lUiD57fU54pVJOHK5dl3+Y4RUuZR7v/ AIB4kO3v6V6b8PPA08FxHrmrRGMpzbQMPmB/vsO3sPxrofDXw/0nw+UuHH22 8XpNKOFP+yvQfXrXVVOJxvMnCnt3HQwvK+aZ4P410a80jxLeNco3lXUzSwy4 +VwxzjPqM4xXP19I3lla6hbtb3lvHPC3VJFDCuQ1D4VaDdMXtHuLJj2jbco/ Bv8AGtaOPhypTRnVwkr3ieOkA9RRXotx8H7oE/ZtYiYf9NYSP5Gqj/CXXVPy Xli//AmH9K61i6D+0c7w9VdDhaK7cfCfXyebmxH/AANv8Knj+EWrn/WalZL9 Fc/0FH1qj/MH1er2OBor0qD4PP8A8vGtAe0cH+JrTtvhLosfNxeXk/sGVB+g qHjqC6lLC1X0PIuBTo43ncJFG0rHoqKWP6V7naeAPDFngrpUcrD+KZi/8zW5 bWVrZrttbaGBfSNAv8qwlmMV8MTaOCl1Z4bp/gfxJqWDFpckSH+O4IjH68/p XV6Z8InJD6rqYA7x2y/+zH/CvTqK5J4+rLbQ3jhKcd9TD0jwdoOikPaWEZlH /LaX53/M9PwrcoorjlKUneTudSioqyQUUUVIz//Z --_005_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_ Content-Type: image/jpeg; name="image002.jpg" Content-Description: image002.jpg Content-Disposition: inline; filename="image002.jpg"; size=4649; creation-date="Wed, 26 Jun 2013 16:04:49 GMT"; modification-date="Wed, 26 Jun 2013 16:04:49 GMT" Content-ID: Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4O Dx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQyNjs9QEBAJjBGS0U+Sjk/QD3/ 2wBDAQsLCw8NDx0QEB09KSMpPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT3/wAARCABeAPQDASIAAhEBAxEB/8QA HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1 dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU 1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0rxN4ni8O Q22baS5uLqTy4YkIG4+5PTqPzpvh3xQNclvbeeylsrqyYLLHIwYd+hH0NZXx Il09LCyi1Szmkglm2i5ifabY8fN0OeM8d8Vi+HvEN5DoviOF71tQsbGA/Zrt gckkEAZP4VvGmnTvbUm+pvaJ8Q7bW9YgsEsZ4fPLiOV2Uq20E/0qXU/Hdvpf iX+yJLOZiHjRplYbV34wcde9cPaQDR9O8F6lgjdcybz7M4/pmrPiaA3PizxM 6gl7a1inX6oYz/LNaeyhzeX/AAbCu7HXHx5b/wDCUjRRZTFjcfZ/P3Dbuxk8 de9M1fx6un6neWdppdxe/YUD3MiOFCDjoDyeorjbDdNrfhvUpBh9Q1K4nP0L qB/KrHi68sovE+ozRNcaNqtqgaOcPlbzgYG3HBI79OOaFSjzJW6fqF3Y7O+8 a2tnY6RdpbTSx6o4RBwpTOOufrU9l4pivdb1XTVtpFfTl3M5YYf6Vxvii9ur zwz4V1TUYyjLcK9wwTAXkYJHbIGateFZ01HxV4q1C0JltJY8JKAdrf5xU+zj y3/rcd9TT074k2moWGoXK2M8Zs4BP5bMuZFzg4PsauX3ja3stB07URZzSy6j gQWykbiT2J6f/rrzWOJ7TwZZahGjYmFzYzYHZjuXP4g1u6vmDwl4MvJEb7Pb SI0rhSQg4PP5GrdGF/mLmZ2nhzxXHr11eWUtnLZXtmR5sMjBsA+4roK4bwPq d3qfiPWHF7Ne6bHgQTSIFBJOeuB2/TFdzXPUjyysUmFFFFZjCiiigAooooAK KKKACiiigApM0E1k6r4i07R5kiv7jynkXco2McjOOwpqLk7JClKMVeTsauaX Ncz/AMJ1of8Az/f+Qn/wrbtL2K8to54G3RSqGRsYyDTlCcfiViY1IT0i0y3S 01TmnVJYUUUUAFFFFAGT4h1/SfD9kkutzLFbzP5a7oy4Y4zjAB9KwY/if4Lh i8uLUESP+6trIB+W2sb45/8AItad/wBfn/sjVy3gL4aWfi/QH1C5v7m3dZ2i 2RKpGAAc8j3oA9Hj+J3g6XCf2rEoHTfC4H6rXR6fqGn6tB9o0+5t7qJuC8TB h9DivNbn4E2hhb7LrVysuOPNiVl/HGDXnqSaz8N/FrqG8u6t2HmIrfu7iM88 +oI/EH3FAH0o4jjQuyqFjBOcdK46T4neCpyrS6hHIV+6WtZDj6fLXSxX0Wp+ H1vrc5iuLbzUz6Fc184eC9Ai8T+JbXSp5pIY5kcl4wCw2qT3+lAHtrfFPwdI pR9UVlbghreQj/0GtTRfF3hvVnFtpOpWbuekKnYx+inBNcZ/worTP+gvff8A fCf4Vxnjj4Z3XhC2S/guvtljvCs+3ZJEx6E47Z7jvQB9BbVxjAx6YrC1/wAY 6D4cuI7TWLsQSSx71QxM4K5x2BHUVz/wk8W3HiHRJ7PUJDLeWBVfNY/NJGfu k+pGCM/SuN+OX/I1af8A9eX/ALO1AHs+mXdrf6dBd2DK1rOgkjZV2gqehxWT rfjnQPDt+LPVb7yLgoJNnlO3ynODkAjsaPAX/Ih6J/16R/yryT40f8j0n/Xn H/6E9AHuWn6hbarYQ3tjMs1tOu+ORehFWa8O+EXjP+ydS/sK+kxZ3b5t2Y8R ynt9G/n9a9xoAoazrVj4f05r7U5/JtlYKX2luScDgAmq+geKNJ8Txzvo919o WAhZDsZdpPI6gVznxi/5J9cf9d4v/QhWF8CP+PHWv+u0X/oJoA6qb4o+E4J5 IZNUw8bFGHkScEHB/hpn/C1vCH/QV/8AJeT/AOJrDuvgjpt1dzTtq16plkaQ gKmASc+nvXO+M/hVY+F/DFzqkGo3U0kJQBJFUKdzAdh70Ad9/wALW8If9BX/ AMl5P/iaP+FreEP+gr/5Lyf/ABNeV/DvwHa+NY9Qa6vJ7Y2rRhfKCnduDdcj 2rs/+FFaZ/0F77/vhP8ACgD0mxvYNSsYLy0fzLedBJG+CNynkHB5qeqWj6cm jaPZ6dHI0iWsSxK7YywAxk1Hf3qZaBZArD7wPf8AGgCxJcqUzEQwzgn0rzT4 iyNJqloWOT5J/wDQjXaeaUGUPX8jXC+O5Vm1C0Zf+eJyPT5q6sF/GRxZj/u7 +Ry9eleHdTmg0qzTh0ESjae1ea13egNvtLVB0EYLGu7Gq8Vc87LHacvQ7+3m WVR2YDlfSrFYloWLqUOCO57VsLIGGQc15ElY91O5JRSZopDFooooA8y+Of8A yLWnf9fn/sjVa+Cf/Ijy/wDX7J/6CtVfjn/yLWnf9fn/ALI1cD4V+JeoeD9J bT7O0s5o2labdMW3ZIA7HpxQB9F14P8AGuWF/GsCRkeZHZoJcepZiP0NLdfH DXpoGSC2063c9JArMR9ATisnw54P1zx5rJursXAtpX33N9MCNw7hc9TjgY4F AHsXgdXT4Y6YJAQ32LPPpg4/TFeQfCT/AJKJpv8A1zl/9Fmvf3t4rTSGt4FC RQwFEUdlC4Ar5e0G71Oy1SGfRPO+3qreX5Me9sEc4GD2zQB9WVxHxd1C3tPA V3BKy+bdukUSZ5JDBifwANeWXnjvxzYMqXt/e2zOCVE1sqEj2ytN0vwv4q+I U630krzw5KG8upflTB5AXr+AAoA6f4E20h1DWLnB8pYo48/7RJP8v51T+OX/ ACNWn/8AXl/7O1er+FPDFp4S0SPT7MlznfLKww0rnqx/kB2Aryj45f8AI1af /wBeX/s7UAeo+Av+RD0T/r0j/lXkfxq48cL/ANeUf/oT1654C/5EPRP+vSP+ VeR/Gv8A5Hdf+vKP/wBCegCh418Htoun6TrNmhFjfW0Rfb/yymKAn6Buo98+ 1erfDLxn/wAJTofkXcgOp2YCTZPMi/wyfj39/rWpZaTa678P7HTr5N8Fxp8K t6j5Bgj3B5H0rwtG1P4a+N+QTNavgjotxCf6EfkR7UAet/GL/kn1x/13i/8A QhWF8CP+PHWv+u0X/oJrS+JuqW2tfCr+0LGTzLe4khdD/wACHB9weDWb8CP+ PHWv+u0X/oJoA9XrjPi3/wAk7v8A/fi/9GLXZ1xnxb/5J3f/AO/F/wCjFoA5 f4D/AOp1z/fh/k9etE15L8B/9Trn+/D/ACevWW6UAc74q8aad4QS2bUluG+0 lhH5KbuVxnPI9RXByfFHRZHZ2W9LMcn9yP8AGrPxjVZbzw0kihka6ZWB6EEx gisDVLHSdWl1uw0TTYp9RtIpQDb2vlAYnjCqq5O5lXeC3GQaANA/E3SUOYft gB6qYhj+dZeo+JrPxHdo1rvVo0wVcYJ56ioR4ejghF1caXGbYaPEhL4RWvPN VWTd2kPzA9xyaqeM7CSDUtNksrFLOS5LiG0jthDOhDYCsqkhhzhXH3hnNa0a vspqZjiKPtqbgWQMniuo0rWrextI43Em8AAkLmsuXQb/AEuyt5r9U8x1HmGM 5CN6H/OKr11TxdPFRUqTvHudOVZL7ODqVnq+i6HbweMdOhXGLgnudg5/WrUX j3TY87luce0Y/wAa8+pD901i4JnsLL6Pme2wziVFYdGAI/GrAOayNPcm3h/3 F/lWqnQVzHivckooooEeZfHP/kWtO/6/P/ZGpPg7pOn33gyWW7sbWeQXki75 YVY4wvGSKX45/wDItad/1+f+yNVr4J/8iPL/ANfsn/oK0AdpHoWlQuHi0yyR h3W3QH+VXgMDA6ClooAgvP8Ajxn/AOubfyr58+En/JRNN/65y/8Aos19B3n/ AB4z/wDXNv5V8+fCT/komm/9c5f/AEWaAPYPiH4SXxZ4beKFR9vtsy2rHu2O V+jDj649K8r+FXi1vDviE6besUsr5xGwfjypugJ9M/dP4ele/V4d8YfCH9ma oNcs48Wl622cL/BL6/8AAv5g+tAHuNeHfHL/AJGrT/8Ary/9nau7+F/i/wD4 Sbw8ILqTdqNiBHNk8yL/AAv+OMH3BrhPjl/yNWn/APXl/wCztQB6j4C/5EPR P+vSP+VeR/Gv/kd1/wCvKP8A9CevXPAX/Ih6J/16R/yryP41/wDI7r/15R/+ hPQB7T4Z/wCRV0j/AK8of/QBXNfFDwZ/wk+ifa7OPOp2SlogBzKnVk/qPf61 0vhn/kVdI/68of8A0AVp0AfLlt4huIfCt9oUmXtriVJo8n/VOrAt+BHb1H1r 0z4Ef8eOtf8AXaL/ANBNYPxb8Gf2Nqn9tWMeLG9f96qjiKU/0br9c+ore+BH /HjrX/XaL/0E0Aer1xnxb/5J3f8A+/F/6MWuzrjPi3/yTu//AN+L/wBGLQBy /wAB/wDU65/vw/yevWW6V5N8B/8AU65/vw/yevWjQByfjHwXZ+L0tVvbi4h+ ylinkled2M5yD6VyD/B/SkPF/qH5p/8AE16uyZqCWAYyBUSbSuNHlD/CTTBx 9tvyM5wSmP5VreGvBeneHrqW5hMs9yRtWWYglB3C4HFdvLbgIcDms54/LbFe PmlWX1dpM6aEVzojliSaJo5VDo4wynoRXIzeHkW4kWJnKKxAGRkCuxqoLbNw 7qOp5Fc2QVJKpOKeljrq1ZU0uVnNp4fhcf6yUHuOP8KuWfhCC6LbppwoHUY6 /lXSwWgkZRsDE9q17exS3j2oOM55r6dzZzyxVVL4iK0g8pEUdFAFaCDApqx4 qQCszjHUUUUxGXrvhzTPEtrHb6tbefFE/mIu9lw2CM8Ediafoegad4csTZ6V b+Rbs5kK72b5jjJySfQVo0UAFFFFADXRZEZGGVYEEe1c7pHw/wDDug6jFf6b p/k3MQIR/NdsAjB4Jx0NdJRQAVU1PTLTWdOmsdQhWa2mG10ORnv1HIq3RQBz 2i+BdB8PX/23SrNrefYULCZyCp7EE4PQVJrvgvQ/Et3Hc6tZefNGnlq3mOuF znHBHc1u0UAV9PsLfS7CCys4/Lt4EEcaZJwo6DJ5rH1vwLoHiO++2arY+fcb BHu811+UZwMAj1NdBRQBFa20VnaQ20C7YYUWNFznCgYA/IVLRRQBV1LTbXV9 Pmsb+FZraZdro3cVS0DwvpPhiOdNHtfs6zsGkG9myRwOpNa9FABVHV9Hste0 2Sw1KHzraQgsm4rnByORz1FXqKAMfQPCukeGBONHtfs4uCpk/eM27GcdSfU1 sUUUAJijFLRQBXniyvy4+lY12pWUAjHFbzDIqhdWqytuIOQPWvOx+DeIpOMN zejUUJXZk0+1hZpCRwM9anNpz3q1bwbcVzZZgKuFnKVS2q6GletGaSiWreFE ywADN1NWcVHGMCpK9o5QxS0UUCCiiigAooooAKKKKACiiigAooooAKKKKACi iigAooooAKKKKACiiigAooooAKKKKAEIpjJmpKSgCDyR6U9YwKkxRikMQDFO oopiCiiigAooooA//9k= --_005_1C6085AE4073A9448F7C718CC7EE1DEB0E2457SEAMBX2seasamsung_-- --===============0660518789== 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 --===============0660518789==-- From ipp-bounces@pwg.org Wed Jun 26 16:30:21 2013 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 50E4111E814F for ; Wed, 26 Jun 2013 16:30:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 5XIuzFvALIqh for ; Wed, 26 Jun 2013 16:30:13 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5F31B11E814B for ; Wed, 26 Jun 2013 16:30:13 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D949379247; Wed, 26 Jun 2013 19:29:51 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from cusa.canon.com (mailgrd17.cusa.canon.com [146.184.152.232]) by pwg.org (Postfix) with ESMTP id 1296279245 for ; Wed, 26 Jun 2013 19:29:26 -0400 (EDT) Received: from ([146.184.20.22]) by mailgrd17.cusa.canon.com with ESMTP with TLS id 4BB4XL1.47224468; Wed, 26 Jun 2013 19:29:19 -0400 Received: from RDEXCHMAIL01.sc.rd.canon.com ([fe80::15a8:cc66:e35:f508]) by RDEXCHMAIL02.sc.rd.canon.com ([169.254.1.25]) with mapi id 14.01.0289.001; Wed, 26 Jun 2013 16:28:58 -0700 From: "Yardumian, Rick" To: "" , "blueroofmusic@gmail.com" , "ptykodi@tykodi.com" , "Michael Sweet (msweet@apple.com)" Thread-Topic: Canon has reviewed the IPP FaxOut specification and has no comments Thread-Index: Ac5yxLHyH5as7XDCQ36kRlX6fKUaLA== Date: Wed, 26 Jun 2013 23:28:57 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [146.184.26.15] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Canon has reviewed the IPP FaxOut specification and has no comments 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="===============0260803599==" 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: D949379247.A87E0 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0260803599== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B09B928B11A36543865AFB7D94C2393DC99E8883RDEXCHMAIL01scr_" --_000_B09B928B11A36543865AFB7D94C2393DC99E8883RDEXCHMAIL01scr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_B09B928B11A36543865AFB7D94C2393DC99E8883RDEXCHMAIL01scr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_B09B928B11A36543865AFB7D94C2393DC99E8883RDEXCHMAIL01scr_-- --===============0260803599== 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 --===============0260803599==-- From ipp-bounces@pwg.org Wed Jun 26 19:26:36 2013 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 80A0221F995B for ; Wed, 26 Jun 2013 19:26:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_41=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 qPrO2N-ux+nY for ; Wed, 26 Jun 2013 19:26:30 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0AC21F9929 for ; Wed, 26 Jun 2013 19:26:29 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 03FBC7924D; Wed, 26 Jun 2013 22:25:45 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mo.mxl.2iij.net (mo1502.mxl.2iij.net [203.180.99.20]) by pwg.org (Postfix) with ESMTP id 9F92D7924C for ; Wed, 26 Jun 2013 22:25:20 -0400 (EDT) Received: by mo.mxl.2iij.net (mxl-mo1502) id r5R2PF7g028975; Thu, 27 Jun 2013 11:25:15 +0900 Received: from unknown [210.173.21.247] (EHLO mx03.fujixerox.co.jp) by mas1502a.mxl.2iij.net(mxl_mta-6.15.0-3) over TLS secured channel with ESMTP id b82abc15.0.177147.00-2359.307130.mas1502a.mxl.2iij.net (envelope-from ); Thu, 27 Jun 2013 11:25:15 +0900 (JST) X-MXL-Hash: 51cba28b0d4e3adb-8dafe2da7c1c91b91a7ffec144bd91acf9fc9166 Received: from ma10.fujixerox.co.jp ([143.94.100.181]) by mx03.fujixerox.co.jp with ESMTP id r5R2PD1Z020444; Thu, 27 Jun 2013 11:25:14 +0900 Received: from ma10.fujixerox.co.jp (root@localhost) by ma10.fujixerox.co.jp with ESMTP id r5R2PDqK006835; Thu, 27 Jun 2013 11:25:13 +0900 Received: from unknown [143.94.100.180] by ma10.fujixerox.co.jp with ESMTP id MAA06834; Thu, 27 Jun 2013 11:25:13 +0900 Received: from exg01.kdc.fujixerox.co.jp ([143.94.250.170]) by ms2.dc.fxis.co.jp (8.13.8/8.13.8) with ESMTP id r5R2PCNM011177; Thu, 27 Jun 2013 11:25:13 +0900 (JST) Received: from FX-JPN-EXMBV03.dc00.fujixerox.net ([143.94.250.54]) by FX-JPN-EXHCS11.dc00.fujixerox.net ([172.25.1.200]) with mapi; Thu, 27 Jun 2013 11:25:12 +0900 From: fx OHTAKE SHIN To: "ipp@pwg.org" , "blueroofmusic@gmail.com" , "ptykodi@tykodi.com" , "msweet@apple.com" Date: Thu, 27 Jun 2013 11:25:23 +0900 Thread-Topic: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Index: Ac5y3ZOVm/OhrRFDSsqqJuzN4F2zGw== Message-ID: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> Accept-Language: ja-JP Content-Language: ja-JP X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: ja-JP MIME-Version: 1.0 X-Spam: exempt X-MAIL-FROM: X-SOURCE-IP: [210.173.21.247] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Fuji Xerox has reviewed the IPP FaxOut specification and has comments 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="===============1203081569==" 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: 03FBC7924D.A9F43 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1203081569== Content-Language: ja-JP Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0194_01CE7329.03840480" ------=_NextPart_000_0194_01CE7329.03840480 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Greetings, Fuji Xerox has comments for the IPP FaxOut specification final call. ---- 8.2 job-state-reasons 1. fax-modem-carrier-lost See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost by Called terminal. We think fax-modem-carrier-lost should be removed from the specification. If the specification supposes another case, tell us an example on the facsimile protocol sequence. 2. fax-modem-training-failure See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is detected by Called terminal. We think fax-modem-training-failure should be removed from the specification. If the specification supposes another case, tell us an example on the facsimile protocol sequence. 3. fax-modem-voice-detected If fax-modem-voice-detected specified as a job state, it should change name to job-calling. Facsimile always detect sound other than a carrier tone while facsimile dialing numbers to detecting any facsimile signals, because facsimile may hear ringing tone or machine's voice(voice answer system), human's voice(fax manual receive). Therefore, fax-modem-voice-detected cannot specify as an error job reason, because of ringing tone. --- Thanks, Shin // --------------------------------------------------------------------- Shin Ohtake CTPF4D, Fuji Xerox Co.,Ltd. phone: +81-45-755-5474 (direct) mail: shin.ohtake@fujixerox.co.jp --------------------------------------------------------------------- ------=_NextPart_000_0194_01CE7329.03840480 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIPQzCCA1owggJCoAMCAQICAQAwDQYJKoZIhvcNAQEFBQAwUDELMAkG A1UEBhMCSlAxGDAWBgNVBAoTD1NFQ09NIFRydXN0Lm5ldDEnMCUGA1UECxMe U2VjdXJpdHkgQ29tbXVuaWNhdGlvbiBSb290Q0ExMB4XDTAzMDkzMDA0MjA0 OVoXDTIzMDkzMDA0MjA0OVowUDELMAkGA1UEBhMCSlAxGDAWBgNVBAoTD1NF Q09NIFRydXN0Lm5ldDEnMCUGA1UECxMeU2VjdXJpdHkgQ29tbXVuaWNhdGlv biBSb290Q0ExMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs7P+ f9Ntse8WfFelDG12ii9Lv2T7TO6K8PMpfPX/7irg6em6W2QimppvLDomaVEF mSbc1RxqccaafR6d3XxsxoxnZ0o++HGwGSepCQymlb9LjAz6VZg72OgioUtx OHmsl5Jps4l+6iFoBpgUlofSYTa8bSdWnlfuwMBW/TLPpNmOwiPXjajz2CWs l+RwOPS2OrSdO5cmQ6OhvElZckwjMIcBWPZOvhxoVmavzUFdyLNNKlVGqx/a HuJAPdvNfbmSgJw33QyWZJ3cIvdki99h3hWUUhWgfVLJS6ghycax7cvDlWDR D/CrcPjfy01+7Nb6q9m9f1Typel5+tnWdiQocwIDAQABoz8wPTAdBgNVHQ4E FgQUoHNJmWjchVtl45soL1efvTO8B0gwCwYDVR0PBAQDAgEGMA8GA1UdEwEB /wQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAGhAqai75E9debMFtRezYBPr xpJd4NHTav77vpttv8cFbVkgxBzwt9qEWAJj+kgW70+lC/dKmPI/nhutR2tj zghH61I/eJyvTa741U/PmpgqEEE5UsTd2ZsO75MBrrIuymhCJEJssLM6Ps3p 2kjEFcvp+QcPklBJit0xl1/J6TeqO1lll5QyybOfPjpiWMVJrWIOcaUyqi/G iXZDQBMTZz2iVCUQy/E68tn620lWu6b+p0E1w+CIYcmIx982ECKYWeqwSvtW FnNurE33IqFPrR16LUUn5TDBXvLaE8slQlGVRwOMbCHMdELtU/8zi48PVwEW L8+m7slwIhS9/b5sCwMwggOoMIICkKADAgECAghDZzmIviunRjANBgkqhkiG 9w0BAQUFADA/MQswCQYDVQQGEwJKUDETMBEGA1UEChMKRnVqaSBYZXJveDEb MBkGA1UEAxMSRnVqaSBYZXJveCBYbmV0IENBMB4XDTEyMDQwMjA4MjY1N1oX DTE0MDQwMTE0NTk1OVowSDELMAkGA1UEBhMCSlAxHTAbBgNVBAoTFEZ1amkg WGVyb3ggQ28uLCBMdGQuMRowGAYDVQQDExEyMjE0NiBTaGluIE9odGFrZTCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoyYpIZWaOHMB3ikbUlamQSCT y1neW2nOWCamO5N96DwcKvnQ2EHZQfpDDmhZAjzQQ5IGpM/iuH4eQo2sZ+2E Q8gevzVDJW5nU2ypvT+yteWg/Qq6MzJjZLa4+Apt+rQVBrXBZeywXEI8vA/R 4HWIEVM/EqbxhIDssJNQYz2Foy8CAwEAAaOCASEwggEdMB8GA1UdIwQYMBaA FE2I1t2VWHXrrYgbTTIISciCBGCOMAkGA1UdEwQCMAAwPQYDVR0fBDYwNDAy oDCgLoYsaHR0cDovL2NhcHMuZnVqaXhlcm94LmNvLmpwL2NybC9meHhuZXRj YS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMAsGA1UdDwQE AwIFoDBcBgNVHSAEVTBTMFEGCysGAQQBgikBBQEGMEIwQAYIKwYBBQUHAgEW NGh0dHA6Ly93d3cuZnVqaXhlcm94LmNvLmpwL3Byb2R1Y3QvY2FwL2Z4eG5l dGNhLmh0bWwwJgYDVR0RBB8wHYEbc2hpbi5vaHRha2VAZnVqaXhlcm94LmNv LmpwMA0GCSqGSIb3DQEBBQUAA4IBAQA9Uba8PJmVy+YCm0MRvfwSjE869c9o VrUj8KmXtOdkRp5A/wsVl1wJwSY95Zo97NzLgOynIp9k8ra4cKuqkirhJFOw lE6DUWpKi05fsZtHkgG/lhuv3b6haJMkjWlYikXWIRJ7TTK0cNIxsY8wobAG mMAwASc9bzKjs6GLkPFFuqOBUNL/k2NGbvNLlstrM6wN928GZWffgFm0aLM9 OOvdhQeZanEqoBWwhCI/2n3GmYA27W/V8Guf+a/E9nhcCKZIKR5+h8tXCaox D2tx3kV9xpO1NymsQsyLrHTpwwgvZNU0+TH1nUNFNlqLmxELy+X9ORzaMYqk PeGa9jQLvUWyMIIECzCCAvOgAwIBAgIJAUWZhr9bgFB4MA0GCSqGSIb3DQEB BQUAME8xCzAJBgNVBAYTAkpQMRMwEQYDVQQKEwpGdWppIFhlcm94MSswKQYD VQQDEyJGdWppIFhlcm94IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA4 MDQyOTE1MDAwMFoXDTE0MTIxNzAyMTMzMlowPzELMAkGA1UEBhMCSlAxEzAR BgNVBAoTCkZ1amkgWGVyb3gxGzAZBgNVBAMTEkZ1amkgWGVyb3ggWG5ldCBD QTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALV3iwzXlyB/xU98 aMEFsuTOg+ogQ903jg9N3md69FGcOgR4hN6f3n90z1d3yfy2CY/p11X2KIMm xth6CZYiporeXYwOGqgCie2cbZV09YISemQjKbavqk9wqsTR+IE/5+bdnY7s sbN0F06m+UmktqrcLl5AwTBb/fIA4NPy1gaFkFCub4zOnUHF9meIzkxq63LK Tmif48ZbI1frSF7HBGuJGaqTsHtBqvetbe+Nn15OcXrNwT7YdniukhqEWYSc qUnfNCjNWGp0viZB6a3wY7gOvsAT41OlWUrb5rCnDPbzCBojdWBBZB/QSNJq fgFgEhsLQh52/abm6f5d5UM9O10CAwEAAaOB+TCB9jALBgNVHQ8EBAMCAQYw HQYDVR0OBBYEFE2I1t2VWHXrrYgbTTIISciCBGCOMB8GA1UdIwQYMBaAFOrF p1bEKFI+gqXs9VAWY4/hiC15MFgGA1UdIARRME8wTQYLKwYBBAGCKQEFAQEw PjA8BggrBgEFBQcCARYwaHR0cDovL3d3dy5mdWppeGVyb3guY28uanAvcHJv ZHVjdC9jYXAvZnhjYS5odG1sMBIGA1UdEwEB/wQIMAYBAf8CAQAwOQYDVR0f BDIwMDAuoCygKoYoaHR0cDovL2NhcHMuZnVqaXhlcm94LmNvLmpwL2NybC9m eGNhLmNybDANBgkqhkiG9w0BAQUFAAOCAQEAFfsmaMGjMqu0zTEvvAg/vkiP wzwCS3JwvTaH2R40sjZryCCN4e6yvm4aZHb86vzl/ngARXPh7lm3EMbMIMp9 M3EJhgvPgwxKH153+F31rKEPwaNWo3pQGxR7P8JxIOujZfSBoNL/bAqz+OZc I3B/LGhW6DTB4Qpatt4GZuf139CeMtW/qncnfY1snLHMlWsYzYn64+h69FwO B9ngfM6boxV3/sYAPGzjBH4IIlQ/1rpAWlIyEHoxQ15S/lVqclw7QC9D9giB Wv4/sy+80ZXsjVmhtTs42vJY3OWCy+3k0QDWNaDKlVzcmiAKWbd5jh2Ju8Im +PdmzsrEr4oEKHZyuTCCBCYwggMOoAMCAQICBBK5sKcwDQYJKoZIhvcNAQEF BQAwUDELMAkGA1UEBhMCSlAxGDAWBgNVBAoTD1NFQ09NIFRydXN0Lm5ldDEn MCUGA1UECxMeU2VjdXJpdHkgQ29tbXVuaWNhdGlvbiBSb290Q0ExMB4XDTA0 MTIxNzAyMTMzMloXDTE0MTIxNzAyMTMzMlowTzELMAkGA1UEBhMCSlAxEzAR BgNVBAoTCkZ1amkgWGVyb3gxKzApBgNVBAMTIkZ1amkgWGVyb3ggQ2VydGlm aWNhdGlvbiBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK AoIBAQC3JDX7X4x3kY0YJbxMy2IbuJf7EshbOGJRnAQ3kT3GjMYdIHJM1+27 Mf+BO8XeSQx3FL0kExFylc1hkreCJ0CtZ3dpm/VGOxtIFgdySgi4XVp0qnnA QSjUk9amAXHUNs52UqkTPKPOq9UPkLhcw5XEOZptkHAsmNdla1aDB/iTr2m9 n/8IKAY+BLM3FhW4tBbbV5wPlDq71B7yTtnHdJqarPBp/lvngARpHWvbcQ4m fRRb1JaiiWKLHW+0V0ojwN754unS9fGY+WqM3l9gb26AYDI3JPzthJpxyhtu c5EmP3FjFmuRpK/Unqt8h8nBlqJ90GgY09qQvULrG36uiweZAgMBAAGjggEH MIIBAzAdBgNVHQ4EFgQU6sWnVsQoUj6Cpez1UBZjj+GILXkwHwYDVR0jBBgw FoAUoHNJmWjchVtl45soL1efvTO8B0gwEgYDVR0TAQH/BAgwBgEB/wIBATAO BgNVHQ8BAf8EBAMCAQYwSQYDVR0fBEIwQDA+oDygOoY4aHR0cDovL3JlcG9z aXRvcnkuc2Vjb210cnVzdC5uZXQvU0MtUm9vdDEvU0NSb290MUNSTC5jcmww UgYDVR0gBEswSTBHBgoqgwiMmxtkhwUBMDkwNwYIKwYBBQUHAgEWK2h0dHBz Oi8vcmVwb3NpdG9yeS5zZWNvbXRydXN0Lm5ldC9TQy1Sb290MS8wDQYJKoZI hvcNAQEFBQADggEBAC3KeO2cIQO9t9UJXBPA4rbR4uxVxoqm8E4V34Em3CTB ZqZCJi1H9nkHBJ1dfRHctmb9vqG7LcPDMpSRHtKHYrOZAK/X4PTa7sK8ahVI 0+LaKmMnicff0xicQeVvPm6vbk7VKFRGqgaHm34AFy1Mb+Wp8W2XFZVwnBcZ RRgqfHsrYf4tkyGCMVh8H/f5QmExhyIGu9wS52rQPeLzA4BtIhC47a6aGgSx wfFK0ccMZlR974bDma+6Vb4hqzi1u9Aj5WtPiJ5x2+uRwWPlD0qjS0BMZ8x3 YvWfo5vB2pWz/jaT2fefw4WQiWFBKVPMXA2oE0v6T98qkSNEoGxMJ3eMS6Ax ggJ1MIICcQIBATBLMD8xCzAJBgNVBAYTAkpQMRMwEQYDVQQKEwpGdWppIFhl cm94MRswGQYDVQQDExJGdWppIFhlcm94IFhuZXQgQ0ECCENnOYi+K6dGMAkG BSsOAwIaBQCgggGAMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTEzMDYyNzAyMjUyM1owIwYJKoZIhvcNAQkEMRYEFMzf1t48 R0DnU0w5n851XBMKHed0MFoGCSsGAQQBgjcQBDFNMEswPzELMAkGA1UEBhMC SlAxEzARBgNVBAoTCkZ1amkgWGVyb3gxGzAZBgNVBAMTEkZ1amkgWGVyb3gg WG5ldCBDQQIIQ2c5iL4rp0YwXAYLKoZIhvcNAQkQAgsxTaBLMD8xCzAJBgNV BAYTAkpQMRMwEQYDVQQKEwpGdWppIFhlcm94MRswGQYDVQQDExJGdWppIFhl cm94IFhuZXQgQ0ECCENnOYi+K6dGMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZI hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIH MA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMA0GCSqGSIb3 DQEBAQUABIGACnhXFF5ZTN3AifPs23RvWwxLqKxi9DKCimb4FdqpTx67desn /fuWY2jsvOgiD2wGDH7Qp4CjF5P+pHiPcyaQJEyt3g8WnEdmC9irP26UyA1o 0z7L5vhP+TQiHfEsHXmnGdOSYWAbERYgyV5Gn9mNvUeIABrDE7vige6xi3FU nh0AAAAAAAA= ------=_NextPart_000_0194_01CE7329.03840480-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --===============1203081569== 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 --===============1203081569==-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From jockstrapii52@heinemann.com Wed Jun 26 23:41:07 2013 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 6FAEA11E810B for ; Wed, 26 Jun 2013 23:41:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.635 X-Spam-Level: *** X-Spam-Status: No, score=3.635 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_XBL=3.033] 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 7kxQMcs0YUPS for ; Wed, 26 Jun 2013 23:40:51 -0700 (PDT) Received: from ip64-244.cbn.net.id (ip64-244.cbn.net.id [202.158.64.244]) by ietfa.amsl.com (Postfix) with ESMTP id 18A5121F9C53 for ; Wed, 26 Jun 2013 23:40:47 -0700 (PDT) Envelope-to: Delivery-date: Thu, 27 Jun 2013 13:40:47 +0700 Received: from [125.242.152.154] (port=44433 helo=[192.168.6.47]) by 202.158.64.244 with asmtp id 6SLIEc-21148 Y-HP; Thu, 27 Jun 2013 13:40:47 +0700 Message-ID: <9208E08E.118961@heinemann.com> Date: Thu, 27 Jun 2013 13:40:47 +0700 From: "Salvador Briggs" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101026 Thunderbird/3.1.6 MIME-Version: 1.0 To: Subject: Attractive faces, the most beautiful girls are ready to communicate today! Content-Type: multipart/alternative; boundary="------------08030600301090505050709" X-Spam: Not detected X-Mras: Ok This is a multi-part message in MIME format. --------------08030600301090505050709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Charming person, mature girls are ready to correspondence today!These ladies are always talking about what they like sex positions, neither of which they are not shy, believe they have something to tell you and what you hit.Register with us, and the woman with whom you have corresponded will send you my photos in the nude, and most likely you will have sex -Registration!!! >> --------------08030600301090505050709 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Charming person, mature girls are ready to correspondence today!

These ladies are always talking about what they like sex positions, neither of which they are not shy, believe they have something to tell you and what you hit.

Register with us, and the woman with whom you have corresponded will send you my photos in the nude, and most likely you will have sex -Registration!!! >>

--------------08030600301090505050709-- From ipp-bounces@pwg.org Thu Jun 27 05:08:28 2013 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 B900321F997A for ; Thu, 27 Jun 2013 05:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 rTRo9jYBuQCE for ; Thu, 27 Jun 2013 05:08:23 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2802621F99AA for ; Thu, 27 Jun 2013 05:08:20 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8A56579253; Thu, 27 Jun 2013 08:07:43 -0400 (EDT) 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 86EBC79251 for ; Thu, 27 Jun 2013 08:07:19 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=iso-2022-jp Received: from relay7.apple.com ([17.128.113.101]) 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 <0MP10039OWAM9BF2@mail-out.apple.com> for ipp@pwg.org; Thu, 27 Jun 2013 05:07:15 -0700 (PDT) X-AuditID: 11807165-b7f496d000000613-d5-51cc2af28218 Received: from [17.153.105.11] (Unknown_Domain [17.153.105.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay7.apple.com (Apple SCV relay) with SMTP id A2.7A.01555.3FA2CC15; Thu, 27 Jun 2013 05:07:15 -0700 (PDT) From: Michael Sweet In-reply-to: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> Date: Thu, 27 Jun 2013 08:07:13 -0400 Message-id: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> To: fx OHTAKE SHIN X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUiODOTW/ez1plAg0cLNC1ev1rKbnFs30sW iyPfYi06v1lbTL+zgsmB1WPryR9sHh/XH2X22DnrLrvHvMXTmTw2X3nOEsAaxWWTkpqTWZZa pG+XwJWxbO0/poLXMhXn3z5hbWA8LN7FyMEhIWAiMX9FfhcjJ5ApJnHh3nq2LkYuDiGBXiaJ +13L2EESwgJBEs++vGQDsXkF9CSW/pvDCGIzC+hKPHzQyApiswmoSfye1McKMpNTIFri08tA kDCLgKrErBsr2CDKmxklnt91hrC1JZYtfM0MMdJG4uKrk2AjhQSiJD6d280CYosIGEjcn9bC BHGmrMTO30kTGPlnITliFpIjZiGZuoCReRWjQFFqTmKluV5iQUFOql5yfu4mRlCYNhSm7mBs XG51iFGAg1GJh9eD5XSgEGtiWXFl7iFGCQ5mJRHemcJnAoV4UxIrq1KL8uOLSnNSiw8xSnOw KInzSnkdDxQSSE8sSc1OTS1ILYLJMnFwSjUwTj0RtykiS8V/zVqtBdN+1PAsiPe9XDTD4GTq j7TfhWJB5yuP7plSU23xcIK0h27JsXADRinZ3pOM1yMfXnP+WXeZLXjX5Gf2ovP1zxdPEtzd slj0w8HGoHMLZnjN3ZSet0h934HX184+WX25V3dfbOE3y6jm00GrVus3ue1aP79V6ImrPPuS z0osxRmJhlrMRcWJAIXhjrRPAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "ipp@pwg.org" Subject: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments 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: 8A56579253.A8339 X-pwg-MailScanner-From: ipp-bounces@pwg.org Shin, Thanks for your comments! Responses inline... On 2013-06-26, at 10:25 PM, fx OHTAKE SHIN wrote: > Greetings, > > Fuji Xerox has comments for the IPP FaxOut specification final call. > > ---- > 8.2 job-state-reasons > 1. fax-modem-carrier-lost > See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost by Called terminal. We think fax-modem-carrier-lost should be > removed from the specification. > If the specification supposes another case, tell us an example on the facsimile protocol sequence. But on the sending end we still need an indication that we lost the connection to the receiver. Would changing the definition here to something like "Lost connection to the receiver during send." be more descriptive? (in AT command set parlance, this would be a "NO CARRIER" response, received when the connection is lost) > 2. fax-modem-training-failure > See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is detected by Called terminal. We think fax-modem-training-failure > should be removed from the specification. > If the specification supposes another case, tell us an example on the facsimile protocol sequence. But on the sending end we still need an indication that we were unable to connect to the receiver after the receiver answered the call. This definition has already been updated once, but I am happy to reword it again to make this clear - basically, 'fax-modem-training-failure' means that the receiver answered, the sender got the carrier tone, but the sender and receiver were unable to successfully negotiate a data rate. (in AT command set parlance, this is also a "NO CARRIER" response, received after dialing) > 3. fax-modem-voice-detected > If fax-modem-voice-detected specified as a job state, it should change name to job-calling. Facsimile always detect sound other than > a carrier tone while facsimile dialing numbers to detecting any facsimile signals, because facsimile may hear ringing tone or > machine's voice(voice answer system), human's voice(fax manual receive). Therefore, fax-modem-voice-detected cannot specify as an > error job reason, because of ringing tone. I'm not sure I understand your comment, but a couple things: 1. We can't change the names of these keywords: they were defined and approved last year as part of the Printer MIB and IPP MFD Alerts spec (PWG 5107.3-2012). Which of course I don't have referenced and am re-defining the names in the IANA section (editorial changes at least...) [NOTE TO SELF: Add 5107.3 IANA definitions to IPP registrations] 2. We do want a way to indicate when the receiver answers but does not respond with a carrier within the connection timeout setup in the modem. Again, falling back on the AT command set I would probably just get a "NO CARRIER" response and a hang-up, but some modems did/do report "DELAYED" for the additional rings - we *could* add a keyword for that ("fax-modem-delayed"? "fax-modem-waiting"?) but I'd like to leave this one as-is even if many implementations can't support 'fax-modem-voice-detected'. 3. None of these are unconditionally required to implement - certain keywords depend on hardware features that may not be supported by your products, and so naturally you won't report those (similar to how you might not have a duplexing unit in your printer and thus don't have to report or support the "sides" attribute...) _________________________________________________________ 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 ipp-bounces@pwg.org Thu Jun 27 05:13:29 2013 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 8F7E621F9C3A for ; Thu, 27 Jun 2013 05:13:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.599, 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 2b7RsGZvfqrS for ; Thu, 27 Jun 2013 05:13:23 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8837021F9C03 for ; Thu, 27 Jun 2013 05:13:23 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 611B979255; Thu, 27 Jun 2013 08:12:41 -0400 (EDT) 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 6C82379252 for ; Thu, 27 Jun 2013 08:12:17 -0400 (EDT) MIME-version: 1.0 Received: from relay4.apple.com ([17.128.113.87]) 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 <0MP100I1AWGH4NE1@mail-out.apple.com> for ipp@pwg.org; Thu, 27 Jun 2013 05:12:16 -0700 (PDT) X-AuditID: 11807157-b7f706d0000006c6-c9-51cc2c1f71c8 Received: from [17.153.105.11] (Unknown_Domain [17.153.105.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id AF.2B.01734.02C2CC15; Thu, 27 Jun 2013 05:12:16 -0700 (PDT) From: Michael Sweet Date: Thu, 27 Jun 2013 08:12:14 -0400 To: "ipp@pwg.org" Message-id: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprELMWRmVeSWpSXmKPExsUiODOTW1dB50ygwecGDYtj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZWw+spy1YLZExd4d3awNjKtFuxg5OSQETCTu rJrDBmGLSVy4tx7MFhLoZZK4/roQxGYTUJP4PamPFcRmFkiQmLb+AguIzSKgKnFt5jugeg4O YQFPif6WOJCwiIC8xNq2qUwgNq+AjUTbq1WMELaexNJ/cxhByiUEZCV2/k6awMg9C8nQWUiq IOLaEssWvmaeBdTBLKAjMXkhmjCE/fH8EaYFjGyrGAWKUnMSK030EgsKclL1kvNzNzGCQqqh MHwH479lVocYBTgYlXh4PzCeDhRiTSwrrsw9xCjBwawkwjtT+EygEG9KYmVValF+fFFpTmrx IUZpDhYlcV4Jr+OBQgLpiSWp2ampBalFMFkmDk6pBkbH3hONF+7clwpM32HqcUiVffbVW2LZ cfffPDry4/K2u6suHRIuu3X52H1mcVEFuWkLpk4y3FMRWGp0Xyc0kO2MkejFPbGehx2WeCYk RxdcEvrtIWF2udPnguI9h4qFYuvL2r+kaXRvzXtwyD1we7J9xqGr12qDV0dXX1A/eMnT70ZC jUJU/SMlluKMREMt5qLiRACVNb43JQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has comments 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="===============0784827331==" 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: 611B979255.A89B8 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0784827331== Content-type: multipart/alternative; boundary="Boundary_(ID_cUSupNb6h/SVfK26QdcB3g)" --Boundary_(ID_cUSupNb6h/SVfK26QdcB3g) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Follow-up comments based on the feedback we have gotten so far: Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined in PWG 5107.3. Section 8.2 does not define the equivalent of the 'connecting-to-defice' value from "printer-state-reasons". Should we define keyword(s) to describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected? Section 12.2 should not re-register PWG 5107.3 keyword values for "job-state-reasons". Section 13.1 is missing a reference to PWG 5107.3. _________________________________________________________ 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_cUSupNb6h/SVfK26QdcB3g) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Follow-up comments based = on the feedback we have gotten so far:

Section 8.2 does = not mention that the 'fax-modem-xxx' keywords are defined in PWG 5107.3.

Section 8.2 does not define the equivalent of t= he 'connecting-to-defice' value from "printer-state-reasons". Should we def= ine keyword(s) to describe th= is and/or the following intermediate states: Dialing, Answered, Training, and Connected?

Section 12.2 should not re-register PWG 5107.3 keyword values for "job-s= tate-reasons".

Section 13.1 is missing a reference= to PWG 5107.3.

__________________________________= _______________________
Michael Sweet, Sen= ior 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_cUSupNb6h/SVfK26QdcB3g)-- --===============0784827331== 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 --===============0784827331==-- From ipp-bounces@pwg.org Thu Jun 27 13:49:38 2013 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 3BD1C21F9D11 for ; Thu, 27 Jun 2013 13:49:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 I+yszbM2vb0H for ; Thu, 27 Jun 2013 13:49:32 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 295E221F9CFE for ; Thu, 27 Jun 2013 13:49:29 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 442B879260; Thu, 27 Jun 2013 16:48:54 -0400 (EDT) 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 7C5D77925D for ; Thu, 27 Jun 2013 16:48:28 -0400 (EDT) MIME-version: 1.0 Content-type: text/plain; charset=windows-1252 Received: from relay2.apple.com ([17.128.113.67]) 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 <0MP200625KGLSGH0@mail-out.apple.com> for ipp@pwg.org; Thu, 27 Jun 2013 13:48:27 -0700 (PDT) X-AuditID: 11807143-b7f856d000000818-df-51cca518a76f Received: from [17.153.102.103] (Unknown_Domain [17.153.102.103]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay2.apple.com (Apple SCV relay) with SMTP id 64.01.02072.A15ACC15; Thu, 27 Jun 2013 13:48:27 -0700 (PDT) From: Michael Sweet In-reply-to: Date: Thu, 27 Jun 2013 16:48:23 -0400 Content-transfer-encoding: quoted-printable Message-id: <16CBCEA4-C5BF-4C50-B2F9-4D07B3183A17@apple.com> References: To: "Kennedy, Smith (Wireless Architect)" X-Mailer: Apple Mail (2.1782) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPLMWRmVeSWpSXmKPExsUiODMtXVd66ZlAg3enVCxev1rKbnFs30sW iyPfYi06v1lbvOraxezA6rH15A82j52z7rJ77Nq2k8lj3uLpTB6brzxnCWCN4rJJSc3JLEst 0rdL4MrY+a2JveC5bcXxzhb2BsZ1hl2MnBwSAiYSjbN2sEPYYhIX7q1n62Lk4hAS6GeSePHh IzNIQlggXOLN8Q1gNq+AnsTSI08YQWxmIHvH9V+sIDabgJrE70l9YDangJXEn+kTmEBsFgFV iT1Pd0PVZ0u0/HrHDGFrSyxb+Bpqpo3E/Y9X2EBsIQFLiWsPFrGA2CICDhLPl3xigThOVuLd z1mMExj5ZyE5YxaSM2YhGbuAkXkVo0BRak5ipZFeYkFBTqpecn7uJkZQsDYUOu9gPLbM6hCj AAejEg/vzeQzgUKsiWXFlbmHGCU4mJVEeO8sAArxpiRWVqUW5ccXleakFh9ilOZgURLnlfA6 HigkkJ5YkpqdmlqQWgSTZeLglGpg1Nz9OO7Fmp7vCcd2PE9geHg6lPd/Y9Pyu29964X3Hnm8 xTewq+TApVD/6n+zl21dyFxfOPvU12MWZyZFTv2x70bgpOK/t2Rct8vX3p2QmbiBa8EEtwKm TQF34tc3ff29vk5p+oTfKnGH0s+0zrJUP2L5dolmO1vi7K45n9kuGT0yqV9mNmunhYwSS3FG oqEWc1FxIgB+TvGzUgIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "ipp@pwg.org" Subject: [IPP] Re: Hewlett-Packard has reviewed the IPP FaxOut specification and has comments 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: 442B879260.A9546 X-pwg-MailScanner-From: ipp-bounces@pwg.org Smith, Thank you for your comments, some responses inline below: On Jun 26, 2013, at 1:39 AM, Kennedy, Smith (Wireless Architect) wrote: > ... > 4.1.2: > - The notion of "spooling vs. streaming" seems to assume that a device is= one or the other, regardless of the job size. I don't think this is neces= sarily the case. Some ... > FaxOut service side? Or should such devices always present themselves as= streaming devices to clients, and not try to spool small fax jobs?=20=20 Some media types, e.g., PWG Raster, are considered to be streaming formats,= while others are basically always spooled formats, e.g., PDF and OpenXPS. = JPEG is in that middle-ground - you can stream it but generally you "spool"= in memory and decode in bands. It might be useful to talk a bit about this, but a FaxOut printer can adver= tise its exact spool/stream capabilities by looking at any document-format = attribute provided in a Get-Printer-Attributes request. > - Exactly how does the IPP FaxOut Printer Object communicate to the IPP c= lient that it is streaming vs. spooling? Should it be done using the maxim= um size of an incoming fax job, using one of the following? > - job-k-octets-supported (RFC 2911) > - *-k-octets-supported if it depends on the format? These generally communicate the maximum size document that can be spooled. = For a streaming format like PWG Raster, I would not expect the printer to = have a maximum size limit beyond the physical limits of the printer that it= advertises (resolution and media size). The job-spooling-supported Printer attribute can be used to explicitly iden= tify which modes a printer supports, with the returned values being filtere= d by the printer in the Get-Printer-Attributes response (see above). If if= can retransmit an entire job, it is a spooling device. Otherwise it is a = streaming device (for purposes of fax). I think we could also make a statement in the FaxOut spec about PWG Raster = being stream-only and JPEG/OpenXPS/PDF being spool-only. > If not in this manner, which seems non-optimal because it is basically an= implied interpolation, an explicit attribute seems necessary. >=20 > - Is the error handling described here adequate? Under what conditions w= ould there need to be "larger portions of the job" retransmitted? Only in = the event of a phone line connection failure? In that case, would the send= ing fax only send the pages unsent? Or would it be expected to resend the = entire job? Are retries in the "processing" state? Conceptually a printer might have accepted multiple pages and get a late er= ror over the fax line. In most cases I wouldn't expect the printer to get = more than 1 page buffered up at a time... > 4.1.4: > - Why must the job be retained for 300 seconds? A streaming device will = only retain the last page. It is just the job history (not the document data), and the 300 seconds com= es from the Semantic Model FaxOut Service spec (section 7). I will clarify that the Job *History* MUST be retained. > - Feedback: "(section 7.4.21)" should be "(section 7.4.22)". This loggin= g facility is confusing and seems incompletely described, here or in 7.4.22. I can add a reference to the Common Log Format spec, now that it is approve= d. And of course fix the cross reference to the right section... > 4.2: > - Note 1: "MUST NOT" for Print-Job operation? That seems a bit extreme= =85 Is this expected to be only true for the /ipp/faxout Printer Object bu= t not for the /ipp/print Printer Object (if present)? Correct. The point is to have a hard deprecation - the Semantic Model does= not provide Print-Job or Print-URI, so the IPP/SM FaxOut service doesn't o= ffer these operations either. (historically the existence of Print-Job/Pri= nt-URI was a compromise for some companies that didn't want to provide a jo= b history for anything but the currently printing job...) > 4.3: > - What is the purpose of margins here? Is this just for rendering local = to the IPP Faxout device? (Guessing the answer is yes=85) It is more for making the FaxOut service look as much like an IPP Everywher= e printer as possible. > - "pages-per-minute" and "pages-per-minute-color" - how will this be dete= rmined for fax? We should define this; probably as a function of the fax modem technology b= eing used. (i.e. maximum bit rate / constant for page bit size =3D pages-per-minute) > - Should there be an "include-fax-header" job attribute? (this is a page = header with the sender's name & #, date, time, page X of Y, etc.) Legal r= equirements around this? Yeah, legal requirements (I think) pretty much make this mandatory, and the= re is no control over it in the SM FaxOut spec. > - "Note 4" seems to not have any attributes that reference it. Was this = supposed to be referenced by the "input-source-supported" attribute? Yes, good catch, but I am also missing: input-attributes-default input-attributes-supported input-color-mode-supported input-media-supported input-orientation-requested-supported input-quality-supported input-resolution-supported input-sides-supported > 6.1: > - Send-Hardcopy-Document operation and streaming devices and a resend - w= ill the client be expected to resend if the job included a Send-Hardcopy-Do= cument operation? Yes, but then the client will need to provide instructions to the user (rep= lace the document to be faxed and try again). But for hardcopy documents t= he printer should be able to control the buffering/scan rate to allow for r= etries of the current page. Also, pretty much every MFP I've used has scann= ed the entire document into memory before faxing... A client resubmission would use Create-Job + Send-Hardcopy-Document... > 7.2.2.3: > - What document formats must be supported by the printer for the logo? S= ize limits? JPS3 had the printer-icons attribute defined in such a way tha= t the icon must be in a particular format (PNG) and particular sizes. We don't say, here or in SM FaxOut. Maybe we should add a logo-uri-formats= -supported (1setOf mimeMediaType) Printer attribute? And require JPEG? > - Guessing that the schemes supported could be determined by "reference-u= ri-schemes-supported" but that attribute is not listed in the IPP FaxOut sp= ec at all logo-uri-schemes-supported tells you what URIs can be used. > 7.4.22: > - How is this intended to work? Can this be a URI to a service on a host= other than the one hosting the IPP FaxOut Printer Object? What should hap= pen if the fax log hits a size limit? Is the size limit advertised? It *can* point to an external host. We should probably include an example,= including a syslog URI (probably the most common case). Oh, and I need to= document it is READ-WRITE and MUST be listed in the printer-settable-attri= butes-supported attribute... We should discuss the size limit issue on the mailing list (right now it is= an imaginary durable log of infinite length, constructed from pixie dust..= .) > 7.4.26: > - Should this value be the country-defined value? Yes, and I should add the "MUST reflect any local regulatory requirements" = bit to the end. > 7.4.27: > - What is the point of retry-interval-supported for streaming devices? A= nd which entity is responsible for keeping count for the retries? Is it th= e IPP FaxOut device, or the client? Retry-interval still could control the interval between retries to retransm= it the current page. The FaxOut device is responsible for keeping count of= its own retries. _________________________________________________________ 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. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Jun 27 17:27:17 2013 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 C326121F99FC for ; Thu, 27 Jun 2013 17:27:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 4ZlDqVVWFRlk for ; Thu, 27 Jun 2013 17:27:12 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id D634821F9A03 for ; Thu, 27 Jun 2013 17:27:11 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 59CD879267; Thu, 27 Jun 2013 20:26:32 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR006.ACS-INC.COM (usa7109mr006.acs-inc.com [63.87.171.175]) by pwg.org (Postfix) with ESMTP id 12AB679266 for ; Thu, 27 Jun 2013 20:26:07 -0400 (EDT) Received: from usa7109ht001.na.xerox.net ([13.41.230.31]) by USA7109MR006.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 27 Jun 2013 19:26:06 -0500 Received: from USA7109MB013.na.xerox.net ([169.254.5.17]) by USA7109HT001.na.xerox.net ([13.41.230.31]) with mapi id 14.02.0309.002; Thu, 27 Jun 2013 19:26:05 -0500 From: "Manchala, Daniel" To: 'Michael Sweet' , 'fx OHTAKE SHIN' Subject: RE: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Topic: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOcy8sFnxybsXCXEi7eA5d/S5ZC5lJ6xqg Date: Fri, 28 Jun 2013 00:26:04 +0000 Message-ID: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.90] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: , 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: 59CD879267.A909F X-pwg-MailScanner-From: ipp-bounces@pwg.org I think renaming both 'fax-modem-carrier-lost' and 'fax-modem-training-fail= ure' to something like 'fax-modem-confirmation-not-received' or 'fax-out-mo= dem-confirmation-not-received' would help. The reasoning is as follows: As part of training (speed or data rate such as 9600bps) and at the end of = it, a TCF (Training Check Flag) is sent from the fax-out (sending) device t= o a fax-in (receiving) device. If there is a training failure, an FTT (Fail= ure to Train) is sent back from the fax-in receiving device to the fax-out = sending device. If there is no training failure, a CFR (Confirmation to Rec= eive) is sent from the fax-in receiving device to the fax-out sending devic= e. After sufficient number of training failures (usually 3), a DCN (Disconn= ect) signal is sent from fax-out device to fax-in device and the transmissi= on stops. Likewise, if carrier is lost, there is no response received in terms of MCF= (Message Confirmation) from fax-in device at the fax-out device.=20 In either of the two cases, a failure to detect/receive CFR or MCF from the= fax-in device at the fax-out device can trigger 'fax-out-modem-confirmatio= n-not-received'. This is how the sending end will indicate that it lost it= s connection to the receiver. We still could have 'fax-modem-carrier-lost', but on the receiving device, = and probably it is good to rename it as 'fax-in-modem-carrier-lost' indicat= ing that this is an error on the fax-in device. Likewise, we could have 'fa= x-modem-training-failure' but on the receiving device only and it is good t= o rename it (something) as 'fax-in-modem-training-failure' or 'fax-in-modem= -failure-to-train. I like to have the 'fax-out-*' and 'fax-in-*' syntax as it would be less co= nfusing as to what mode a device is acting (as a sender or receiver). Thanks, Daniel. -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael= Sweet Sent: Thursday, June 27, 2013 5:07 AM To: fx OHTAKE SHIN Cc: ipp@pwg.org Subject: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and= has comments Shin, Thanks for your comments! Responses inline... On 2013-06-26, at 10:25 PM, fx OHTAKE SHIN wr= ote: > Greetings, >=20 > Fuji Xerox has comments for the IPP FaxOut specification final call. >=20 > ---- > 8.2 job-state-reasons > 1. fax-modem-carrier-lost > See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost=20 > by Called terminal. We think fax-modem-carrier-lost should be removed fro= m the specification. > If the specification supposes another case, tell us an example on the fac= simile protocol sequence. But on the sending end we still need an indication that we lost the connect= ion to the receiver. Would changing the definition here to something like = "Lost connection to the receiver during send." be more descriptive? (in AT command set parlance, this would be a "NO CARRIER" response, receive= d when the connection is lost) > 2. fax-modem-training-failure > See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is=20 > detected by Called terminal. We think fax-modem-training-failure should b= e removed from the specification. > If the specification supposes another case, tell us an example on the fac= simile protocol sequence. But on the sending end we still need an indication that we were unable to c= onnect to the receiver after the receiver answered the call. This definitio= n has already been updated once, but I am happy to reword it again to make = this clear - basically, 'fax-modem-training-failure' means that the receive= r answered, the sender got the carrier tone, but the sender and receiver we= re unable to successfully negotiate a data rate. (in AT command set parlance, this is also a "NO CARRIER" response, received= after dialing) > 3. fax-modem-voice-detected > If fax-modem-voice-detected specified as a job state, it should change=20 > name to job-calling. Facsimile always detect sound other than a=20 > carrier tone while facsimile dialing numbers to detecting any=20 > facsimile signals, because facsimile may hear ringing tone or machine's v= oice(voice answer system), human's voice(fax manual receive). Therefore, fa= x-modem-voice-detected cannot specify as an error job reason, because of ri= nging tone. I'm not sure I understand your comment, but a couple things: 1. We can't change the names of these keywords: they were defined and appro= ved last year as part of the Printer MIB and IPP MFD Alerts spec (PWG 5107.= 3-2012). Which of course I don't have referenced and am re-defining the nam= es in the IANA section (editorial changes at least...) [NOTE TO SELF: Add 5= 107.3 IANA definitions to IPP registrations] 2. We do want a way to indicate when the receiver answers but does not resp= ond with a carrier within the connection timeout setup in the modem. Again,= falling back on the AT command set I would probably just get a "NO CARRIER= " response and a hang-up, but some modems did/do report "DELAYED" for the a= dditional rings - we *could* add a keyword for that ("fax-modem-delayed"? "= fax-modem-waiting"?) but I'd like to leave this one as-is even if many impl= ementations can't support 'fax-modem-voice-detected'. 3. None of these are unconditionally required to implement - certain keywor= ds depend on hardware features that may not be supported by your products, = and so naturally you won't report those (similar to how you might not have = a duplexing unit in your printer and thus don't have to report or support t= he "sides" attribute...) _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScan= ner, 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. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Jun 27 17:59:49 2013 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 1C6EC11E8111 for ; Thu, 27 Jun 2013 17:59:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.599, 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 dM7MN4VTKCsv for ; Thu, 27 Jun 2013 17:59:43 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9FA21F9A50 for ; Thu, 27 Jun 2013 17:59:43 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 74C527926D; Thu, 27 Jun 2013 20:59:02 -0400 (EDT) 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 3A24E7926C for ; Thu, 27 Jun 2013 20:58:36 -0400 (EDT) Received: from usa7109ht004.na.xerox.net ([13.41.230.30]) by USA7109MR001.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 27 Jun 2013 19:58:36 -0500 Received: from USA7109MB013.na.xerox.net ([169.254.5.17]) by USA7109HT004.na.xerox.net ([13.41.230.30]) with mapi id 14.02.0309.002; Thu, 27 Jun 2013 19:58:35 -0500 From: "Manchala, Daniel" To: 'Michael Sweet' Subject: RE: [IPP] Apple has reviewed the IPP FaxOut specification and has comments Thread-Topic: [IPP] Apple has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOcy/DJ9MpWIf2AE6ONXQT8cSYnJlKTikw Date: Fri, 28 Jun 2013 00:58:35 +0000 Message-ID: References: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> In-Reply-To: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.90] MIME-Version: 1.0 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="===============0245379855==" 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: 74C527926D.A8706 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0245379855== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1963usa7109mb013nax_" --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1963usa7109mb013nax_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike, Yes, one of the states we would like to have is 'fax-out-modem-dialing' or = 'fax-modem-dialing'. Thanks, Daniel. From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael= Sweet Sent: Thursday, June 27, 2013 5:12 AM To: ipp@pwg.org Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has comm= ents Follow-up comments based on the feedback we have gotten so far: Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined = in PWG 5107.3. Section 8.2 does not define the equivalent of the 'connecting-to-defice' va= lue from "printer-state-reasons". Should we define keyword(s) to describe t= his and/or the following intermediate states: Dialing, Answered, Training, = and Connected? Section 12.2 should not re-register PWG 5107.3 keyword values for "job-stat= e-reasons". Section 13.1 is missing a reference to PWG 5107.3. _________________________________________________________ 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. --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1963usa7109mb013nax_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike,

 <= /p>

Yes, one of the states we= would like to have is ‘fax-out-modem-dialing’ or ‘fax-mo= dem-dialing’.

 <= /p>

Thanks,=

Daniel.=

 <= /p>

From: ipp-boun= ces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Thursday, June 27, 2013 5:12 AM
To: ipp@pwg.org
Subject: [IPP] Apple has reviewed the IPP FaxOut specification and h= as comments

 

Follow-up comments based on the feedback we have got= ten so far:

 

Section 8.2 does not mention that the 'fax-modem-xxx= ' keywords are defined in PWG 5107.3.

 

Section 8.2 does not define the equivalent of the 'c= onnecting-to-defice' value from "printer-state-reasons". Should w= e define keyword(s= ) to describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected?

 

Section 12.2 should not re-register PWG 5107.3 keywo= rd values for "job-state-reasons".

 

Section 13.1 is missing a reference to PWG 5107.3.

 

____________________________________________________= _____

Michael Sweet, Senior Printing System En= gineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous content by MailScanne= r, 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. --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1963usa7109mb013nax_-- --===============0245379855== 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 --===============0245379855==-- From ipp-bounces@pwg.org Thu Jun 27 18:23:54 2013 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 A61A821F9D6A for ; Thu, 27 Jun 2013 18:23:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 qpq5xvMLOHr5 for ; Thu, 27 Jun 2013 18:23:41 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 465C821F9C63 for ; Thu, 27 Jun 2013 18:23:41 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 79B0379270; Thu, 27 Jun 2013 21:23:06 -0400 (EDT) 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 A82C47926E for ; Thu, 27 Jun 2013 21:22:39 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay7.apple.com ([17.128.113.101]) 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 <0MP200386X4QKHH0@mail-out.apple.com> for ipp@pwg.org; Thu, 27 Jun 2013 18:22:09 -0700 (PDT) X-AuditID: 11807165-b7f496d000000613-77-51cce53ff706 Received: from [17.153.36.251] (Unknown_Domain [17.153.36.251]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay7.apple.com (Apple SCV relay) with SMTP id A6.70.01555.045ECC15; Thu, 27 Jun 2013 18:22:08 -0700 (PDT) Subject: Re: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments From: Michael Sweet In-reply-to: Date: Thu, 27 Jun 2013 21:22:06 -0400 Message-id: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> To: "Manchala, Daniel" X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUiOFPlt67D0zOBBo1PTSwe75jManFs30sW iyPfYi2m31nB5MDisfXkDzaPj+uPMnvMWzydyWP5qfVsASxRXDYpqTmZZalF+nYJXBlvX/1g KdhtXnFgRzdrA+Na3S5GTg4JAROJ9W2fWCFsMYkL99azgdhCAr1MEk3PFUBsYYEYiUWrdoPV 8AroSSz9N4cRxGYW0JK48e8lE4jNJqAm8XtSH1gNp0CgxI6ec0BxDg4WAVWJT70xEOXBEu0X lrNB2NoSyxa+ZoYYaSPxau4doDgX0NoLjBJTZ8wBmykiYCTxYNViFpA5EgKyEjt/J01g5J+F 5IpZSK6YhWTsAkbmVYwCRak5iZXmeokFBTmpesn5uZsYQWHZUJi6g7FxudUhRgEORiUe3hvJ ZwKFWBPLiitzDzFKcDArifDeWQAU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzivldTxQSCA9sSQ1 OzW1ILUIJsvEwSnVwJj3y5M96UCFojar3qX/tvaG+x6Z2ly8/PvSnVnyT97q3eQRPqx6bGLS 31ymGnnxpbI5c+fWccgln9ow0SG3UzEtSiOZhaPhkP78i76evckrl70p01VmvxY/IUZT2vcB 17rmdwZsOXUmK5OOPGh62b3oib3csXz73ryWK8JrElccmbrDdeNqSSWW4oxEQy3mouJEAMrV a01HAgAA 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: , 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: 79B0379270.A9F8F X-pwg-MailScanner-From: ipp-bounces@pwg.org Daniel, On 2013-06-27, at 8:26 PM, "Manchala, Daniel" wrote: > I think renaming both 'fax-modem-carrier-lost' and 'fax-modem-training-failure' to something like 'fax-modem-confirmation-not-received' or 'fax-out-modem-confirmation-not-received' would help. The reasoning is as follows: These names have already been approved (5107.3) and are in use (CUPS, which provided prototyping specifically for the preliminary fax support via efax). Like I've said on many occasions, we can change the definitions all we like, but unless we want the mess of supporting deprecated old names plus semantically identical new names I don't see the point in continuing discussion of changing the names. As for fax-in-* and fax-out-*, there are enough common states between receiver and sender that I would not want to double things up. > As part of training (speed or data rate such as 9600bps) and at the end of it, a TCF (Training Check Flag) is sent from the fax-out (sending) device to a fax-in (receiving) device. If there is a training failure, an FTT (Failure to Train) is sent back from the fax-in receiving device to the fax-out sending device. If there is no training failure, a CFR (Confirmation to Receive) is sent from the fax-in receiving device to the fax-out sending device. After sufficient number of training failures (usually 3), a DCN (Disconnect) signal is sent from fax-out device to fax-in device and the transmission stops. > > Likewise, if carrier is lost, there is no response received in terms of MCF (Message Confirmation) from fax-in device at the fax-out device. > > In either of the two cases, a failure to detect/receive CFR or MCF from the fax-in device at the fax-out device can trigger 'fax-out-modem-confirmation-not-received'. This is how the sending end will indicate that it lost its connection to the receiver. > > We still could have 'fax-modem-carrier-lost', but on the receiving device, and probably it is good to rename it as 'fax-in-modem-carrier-lost' indicating that this is an error on the fax-in device. Likewise, we could have 'fax-modem-training-failure' but on the receiving device only and it is good to rename it (something) as 'fax-in-modem-training-failure' or 'fax-in-modem-failure-to-train. > > I like to have the 'fax-out-*' and 'fax-in-*' syntax as it would be less confusing as to what mode a device is acting (as a sender or receiver). > > Thanks, > Daniel. > > > > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet > Sent: Thursday, June 27, 2013 5:07 AM > To: fx OHTAKE SHIN > Cc: ipp@pwg.org > Subject: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments > > Shin, > > Thanks for your comments! > > Responses inline... > > On 2013-06-26, at 10:25 PM, fx OHTAKE SHIN wrote: >> Greetings, >> >> Fuji Xerox has comments for the IPP FaxOut specification final call. >> >> ---- >> 8.2 job-state-reasons >> 1. fax-modem-carrier-lost >> See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost >> by Called terminal. We think fax-modem-carrier-lost should be removed from the specification. >> If the specification supposes another case, tell us an example on the facsimile protocol sequence. > > But on the sending end we still need an indication that we lost the connection to the receiver. Would changing the definition here to something like "Lost connection to the receiver during send." be more descriptive? > > (in AT command set parlance, this would be a "NO CARRIER" response, received when the connection is lost) > >> 2. fax-modem-training-failure >> See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is >> detected by Called terminal. We think fax-modem-training-failure should be removed from the specification. >> If the specification supposes another case, tell us an example on the facsimile protocol sequence. > > But on the sending end we still need an indication that we were unable to connect to the receiver after the receiver answered the call. This definition has already been updated once, but I am happy to reword it again to make this clear - basically, 'fax-modem-training-failure' means that the receiver answered, the sender got the carrier tone, but the sender and receiver were unable to successfully negotiate a data rate. > > (in AT command set parlance, this is also a "NO CARRIER" response, received after dialing) > >> 3. fax-modem-voice-detected >> If fax-modem-voice-detected specified as a job state, it should change >> name to job-calling. Facsimile always detect sound other than a >> carrier tone while facsimile dialing numbers to detecting any >> facsimile signals, because facsimile may hear ringing tone or machine's voice(voice answer system), human's voice(fax manual receive). Therefore, fax-modem-voice-detected cannot specify as an error job reason, because of ringing tone. > > I'm not sure I understand your comment, but a couple things: > > 1. We can't change the names of these keywords: they were defined and approved last year as part of the Printer MIB and IPP MFD Alerts spec (PWG 5107.3-2012). Which of course I don't have referenced and am re-defining the names in the IANA section (editorial changes at least...) [NOTE TO SELF: Add 5107.3 IANA definitions to IPP registrations] > > 2. We do want a way to indicate when the receiver answers but does not respond with a carrier within the connection timeout setup in the modem. Again, falling back on the AT command set I would probably just get a "NO CARRIER" response and a hang-up, but some modems did/do report "DELAYED" for the additional rings - we *could* add a keyword for that ("fax-modem-delayed"? "fax-modem-waiting"?) but I'd like to leave this one as-is even if many implementations can't support 'fax-modem-voice-detected'. > > 3. None of these are unconditionally required to implement - certain keywords depend on hardware features that may not be supported by your products, and so naturally you won't report those (similar to how you might not have a duplexing unit in your printer and thus don't have to report or support the "sides" attribute...) > > _________________________________________________________ > 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 _________________________________________________________ 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 ipp-bounces@pwg.org Thu Jun 27 19:38:55 2013 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 0AE5C11E8155 for ; Thu, 27 Jun 2013 19:38:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599] 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 wIYV-zMFiwwd for ; Thu, 27 Jun 2013 19:38:49 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6A211E8135 for ; Thu, 27 Jun 2013 19:38:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 77F5B7927D; Thu, 27 Jun 2013 22:37:37 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR005.ACS-INC.COM (usa7109mr005.acs-inc.com [63.87.171.174]) by pwg.org (Postfix) with ESMTP id A195479279 for ; Thu, 27 Jun 2013 22:37:10 -0400 (EDT) Received: from usa7109ht004.na.xerox.net ([13.41.230.30]) by USA7109MR005.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 27 Jun 2013 21:37:10 -0500 Received: from USA7109MB013.na.xerox.net ([169.254.5.17]) by USA7109HT004.na.xerox.net ([13.41.230.30]) with mapi id 14.02.0309.002; Thu, 27 Jun 2013 21:37:10 -0500 From: "Manchala, Daniel" To: "'ipp@pwg.org'" Thread-Topic: Xerox has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOc6AlcRxZeWynRU6/PHGUvkfrNg== Date: Fri, 28 Jun 2013 02:37:09 +0000 Message-ID: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.90] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Xerox has reviewed the IPP FaxOut specification and has comments 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: 77F5B7927D.A8B19 X-pwg-MailScanner-From: ipp-bounces@pwg.org Section 6.1 Send-Hardcopy-Document Operation This is a CONDITIONALLY REQUIRED Operation. The condition is that Printers = with one or more scanning accessories MUST support this operation. At the s= ame time, it requires that a client (SHOULD) check if the Printer supports = the operation by querying the "operation-supported" Printer Description, an= d clients discover the available input sources by querying "input-source-su= pported" Printer Description. Is it the case that the *client* (MUST or SHO= ULD ?) specify that the job input comes from a hard copy via the scan input= device? This requirement makes sense for small devices which are driven fr= om a client driver on their PC but doesn't make sense for an enterprise or = work group device which is shared by many users. Enterprise or work group d= evices have a local user interface which allow the user to program and subm= it jobs.=20 Section 7.1 - These are all new attributes which go along with the new oper= ation defined in section 6. As such they should be exempt (SHOULD as oppose= d to REQUIRED) if supplied by the user at client station. Section 7.2.2 - This attribute is specified as being "CONDITIONALLY REQUIRE= D". Does the REQUIRED apply to each of the member attributes? There are a n= umber of member attributes in this section which are not supposed to be ove= rridden by the user or client (reference to section 6 about clients gives t= he impression that the user supplies the values that override values from s= ystem), and some which can be optionally supplied.=20 * 7.2.2.1 date-time - this is not able to be overridden by the submitting u= ser. The system defines the submission time. * 7.2.2.2 from-name - this is filled in with the submitting user name (job-= originating-user-name) for the job. * 7.2.2.3 logo - This should be optional. * 7.2.2.4 message - This should be optional. * 7.2.2.5 organization-name - This should be optional. * 7.2.2.6 subject * 7.2.2.7 to-name - This should be optional. Section 7.2.4 - 7.2.6 all three of these are CONDITIONALLY REQUIRED for spo= oling devices. The number-of-retries, retry-interval, and retry-time-out ar= e all system level attributes that belong to the fax card and are not adjus= table on a job per job basis. Are we suggesting that the settings for these= attributes be exposed at a job level? Section 7.3.1 The destination-status for each recipient is contained comple= tely within the fax card and is only made available to the user through the= confirmation sheet. The job level status reported to the UI's and job hist= ory only give the overall status of the entire job. This attribute should b= e changed to SHOULD.=20 Sections 7.4.23 - 7.4.25 (printer-fax-modem-info, printer-fax-modem-name, p= rinter-fax-modem-number) Wish that these were SHOULD as opposed to REQUIRE= D as this will require the gathering of the information and make it availab= le to IPP (also privacy issues ...) - but otherwise ok.=20 --=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 https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Jun 27 20:01:28 2013 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 2C7E311E8135 for ; Thu, 27 Jun 2013 20:01:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.799 X-Spam-Level: X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 EKkJcRt12FBO for ; Thu, 27 Jun 2013 20:01:22 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3C33711E80ED for ; Thu, 27 Jun 2013 20:01:22 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B114C79281; Thu, 27 Jun 2013 23:00:46 -0400 (EDT) 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 5078B79279 for ; Thu, 27 Jun 2013 23:00:22 -0400 (EDT) Received: from usa7109ht001.na.xerox.net ([13.41.230.31]) by USA7109MR004.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 27 Jun 2013 22:00:13 -0500 Received: from USA7109MB013.na.xerox.net ([169.254.5.17]) by USA7109HT001.na.xerox.net ([13.41.230.31]) with mapi id 14.02.0309.002; Thu, 27 Jun 2013 22:00:13 -0500 From: "Manchala, Daniel" To: 'Michael Sweet' Subject: RE: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Topic: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOc537RxkjofuiIkemjjHji9ajYplKamFA Date: Fri, 28 Jun 2013 03:00:12 +0000 Message-ID: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.90] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: , 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: B114C79281.AA143 X-pwg-MailScanner-From: ipp-bounces@pwg.org Mike, Yea, rewording the definitions makes sense then. Paraphrasing -- fax-modem-carrier-lost: Lost connection to the receiver during send. (Recei= ver detected loss of carrier and could not acknowledge reception of carrier= ). fax-modem-training-failure: The sender and receiver were unable to successf= ully negotiate a data rate. (Receiver was unable to agree with the data rat= e suggested by the sender (or) Receiver unable to receive the facsimile per= the suggested data rate) Or something better .... Daniel. -----Original Message----- From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Thursday, June 27, 2013 6:22 PM To: Manchala, Daniel Cc: 'fx OHTAKE SHIN'; 'ipp@pwg.org' Subject: Re: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification= and has comments Daniel, On 2013-06-27, at 8:26 PM, "Manchala, Daniel" w= rote: > I think renaming both 'fax-modem-carrier-lost' and 'fax-modem-training-fa= ilure' to something like 'fax-modem-confirmation-not-received' or 'fax-out-= modem-confirmation-not-received' would help. The reasoning is as follows: These names have already been approved (5107.3) and are in use (CUPS, which= provided prototyping specifically for the preliminary fax support via efax= ). Like I've said on many occasions, we can change the definitions all we like= , but unless we want the mess of supporting deprecated old names plus seman= tically identical new names I don't see the point in continuing discussion = of changing the names. As for fax-in-* and fax-out-*, there are enough common states between recei= ver and sender that I would not want to double things up. > As part of training (speed or data rate such as 9600bps) and at the end o= f it, a TCF (Training Check Flag) is sent from the fax-out (sending) device= to a fax-in (receiving) device. If there is a training failure, an FTT (Fa= ilure to Train) is sent back from the fax-in receiving device to the fax-ou= t sending device. If there is no training failure, a CFR (Confirmation to R= eceive) is sent from the fax-in receiving device to the fax-out sending dev= ice. After sufficient number of training failures (usually 3), a DCN (Disco= nnect) signal is sent from fax-out device to fax-in device and the transmis= sion stops. >=20 > Likewise, if carrier is lost, there is no response received in terms of M= CF (Message Confirmation) from fax-in device at the fax-out device.=20 >=20 > In either of the two cases, a failure to detect/receive CFR or MCF from t= he fax-in device at the fax-out device can trigger 'fax-out-modem-confirmat= ion-not-received'. This is how the sending end will indicate that it lost = its connection to the receiver. >=20 > We still could have 'fax-modem-carrier-lost', but on the receiving device= , and probably it is good to rename it as 'fax-in-modem-carrier-lost' indic= ating that this is an error on the fax-in device. Likewise, we could have '= fax-modem-training-failure' but on the receiving device only and it is good= to rename it (something) as 'fax-in-modem-training-failure' or 'fax-in-mod= em-failure-to-train. >=20 > I like to have the 'fax-out-*' and 'fax-in-*' syntax as it would be less = confusing as to what mode a device is acting (as a sender or receiver). >=20 > Thanks, > Daniel. >=20 >=20 >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of=20 > Michael Sweet > Sent: Thursday, June 27, 2013 5:07 AM > To: fx OHTAKE SHIN > Cc: ipp@pwg.org > Subject: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut=20 > specification and has comments >=20 > Shin, >=20 > Thanks for your comments! >=20 > Responses inline... >=20 > On 2013-06-26, at 10:25 PM, fx OHTAKE SHIN = wrote: >> Greetings, >>=20 >> Fuji Xerox has comments for the IPP FaxOut specification final call. >>=20 >> ---- >> 8.2 job-state-reasons >> 1. fax-modem-carrier-lost >> See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost=20 >> by Called terminal. We think fax-modem-carrier-lost should be removed fr= om the specification. >> If the specification supposes another case, tell us an example on the fa= csimile protocol sequence. >=20 > But on the sending end we still need an indication that we lost the conne= ction to the receiver. Would changing the definition here to something lik= e "Lost connection to the receiver during send." be more descriptive? >=20 > (in AT command set parlance, this would be a "NO CARRIER" response,=20 > received when the connection is lost) >=20 >> 2. fax-modem-training-failure >> See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is=20 >> detected by Called terminal. We think fax-modem-training-failure should = be removed from the specification. >> If the specification supposes another case, tell us an example on the fa= csimile protocol sequence. >=20 > But on the sending end we still need an indication that we were unable to= connect to the receiver after the receiver answered the call. This definit= ion has already been updated once, but I am happy to reword it again to mak= e this clear - basically, 'fax-modem-training-failure' means that the recei= ver answered, the sender got the carrier tone, but the sender and receiver = were unable to successfully negotiate a data rate. >=20 > (in AT command set parlance, this is also a "NO CARRIER" response,=20 > received after dialing) >=20 >> 3. fax-modem-voice-detected >> If fax-modem-voice-detected specified as a job state, it should=20 >> change name to job-calling. Facsimile always detect sound other than=20 >> a carrier tone while facsimile dialing numbers to detecting any=20 >> facsimile signals, because facsimile may hear ringing tone or machine's = voice(voice answer system), human's voice(fax manual receive). Therefore, f= ax-modem-voice-detected cannot specify as an error job reason, because of r= inging tone. >=20 > I'm not sure I understand your comment, but a couple things: >=20 > 1. We can't change the names of these keywords: they were defined and=20 > approved last year as part of the Printer MIB and IPP MFD Alerts spec=20 > (PWG 5107.3-2012). Which of course I don't have referenced and am=20 > re-defining the names in the IANA section (editorial changes at=20 > least...) [NOTE TO SELF: Add 5107.3 IANA definitions to IPP=20 > registrations] >=20 > 2. We do want a way to indicate when the receiver answers but does not re= spond with a carrier within the connection timeout setup in the modem. Agai= n, falling back on the AT command set I would probably just get a "NO CARRI= ER" response and a hang-up, but some modems did/do report "DELAYED" for the= additional rings - we *could* add a keyword for that ("fax-modem-delayed"?= "fax-modem-waiting"?) but I'd like to leave this one as-is even if many im= plementations can't support 'fax-modem-voice-detected'. >=20 > 3. None of these are unconditionally required to implement - certain=20 > keywords depend on hardware features that may not be supported by your=20 > products, and so naturally you won't report those (similar to how you=20 > might not have a duplexing unit in your printer and thus don't have to=20 > report or support the "sides" attribute...) >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 > -- > This message has been scanned for viruses and dangerous content by MailSc= anner, and is believed to be clean. >=20 > _______________________________________________ > 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. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Jun 27 23:25:24 2013 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 BB49D21F9E17 for ; Thu, 27 Jun 2013 23:25:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.8 X-Spam-Level: * X-Spam-Status: No, score=1.8 tagged_above=-999 required=5 tests=[J_CHICKENPOX_41=0.6, J_CHICKENPOX_53=0.6, J_CHICKENPOX_55=0.6] 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 WROSC9vRmZze for ; Thu, 27 Jun 2013 23:25:13 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id CF96521F9E14 for ; Thu, 27 Jun 2013 23:25:09 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CAFC07926E; Fri, 28 Jun 2013 02:24:24 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mo.mxl.2iij.net (mo1501.mxl.2iij.net [203.180.99.27]) by pwg.org (Postfix) with ESMTP id 21BB779264 for ; Fri, 28 Jun 2013 02:23:59 -0400 (EDT) Received: by mo.mxl.2iij.net (mxl-mo1501) id r5S6Nuv8017509; Fri, 28 Jun 2013 15:23:56 +0900 Received: from unknown [210.173.21.247] (EHLO mx03.fujixerox.co.jp) by mas1500a.mxl.2iij.net(mxl_mta-6.15.0-3) over TLS secured channel with ESMTP id cfb2dc15.0.245537.00-2335.438593.mas1500a.mxl.2iij.net (envelope-from ); Fri, 28 Jun 2013 15:23:56 +0900 (JST) X-MXL-Hash: 51cd2bfc0adc00d4-3e29951cd8a180e09a1e0213cf0e000a48416ccf Received: from ma10.fujixerox.co.jp ([143.94.100.181]) by mx03.fujixerox.co.jp with ESMTP id r5S6NtKd018478; Fri, 28 Jun 2013 15:23:55 +0900 Received: from ma10.fujixerox.co.jp (root@localhost) by ma10.fujixerox.co.jp with ESMTP id r5S6NtXU013139; Fri, 28 Jun 2013 15:23:55 +0900 Received: from unknown [143.94.100.180] by ma10.fujixerox.co.jp with ESMTP id RAA13135; Fri, 28 Jun 2013 15:23:55 +0900 Received: from exg01.kdc.fujixerox.co.jp ([143.94.250.171]) by ms2.dc.fxis.co.jp (8.13.8/8.13.8) with ESMTP id r5S6NY3o010441; Fri, 28 Jun 2013 15:23:55 +0900 (JST) Received: from FX-JPN-EXMBV03.dc00.fujixerox.net ([143.94.250.54]) by FX-JPN-EXHCS12.dc00.fujixerox.net ([172.25.1.201]) with mapi; Fri, 28 Jun 2013 15:23:46 +0900 From: fx OHTAKE SHIN To: "Manchala, Daniel" , "'Michael Sweet'" Date: Fri, 28 Jun 2013 15:23:44 +0900 Subject: RE: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Topic: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments Thread-Index: AQHOc537RxkjofuiIkemjjHji9ajYplKamFAgAA9b4A= Message-ID: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAC6B@FX-JPN-EXMBV03.dc00.fujixerox.net> References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> In-Reply-To: Accept-Language: ja-JP Content-Language: ja-JP X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: ja-JP MIME-Version: 1.0 X-Spam: exempt X-MAIL-FROM: X-SOURCE-IP: [210.173.21.247] 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="===============1035302478==" 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: CAFC07926E.A9C94 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1035302478== Content-Language: ja-JP Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0188_01CE7413.7A3FB840" ------=_NextPart_000_0188_01CE7413.7A3FB840 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Mike-san and Daniel-san, I'll be out of office for bossiness trip, so Akiko Mochizuki of Fuji Xerox will continue this discussion next week. Thanks, Shin // --------------------------------------------------------------------- Shin Ohtake CTPF4D, Fuji Xerox Co.,Ltd. phone: +81-45-755-5474 (direct) mail: shin.ohtake@fujixerox.co.jp --------------------------------------------------------------------- > -----Original Message----- > From: Manchala, Daniel [mailto:Daniel.Manchala@xerox.com] > Sent: Friday, June 28, 2013 12:00 PM > To: 'Michael Sweet' > Cc: fx OHTAKE SHIN; 'ipp@pwg.org' > Subject: RE: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments > > Mike, > > Yea, rewording the definitions makes sense then. > > Paraphrasing -- > > fax-modem-carrier-lost: Lost connection to the receiver during send. (Receiver detected loss of carrier and could > not acknowledge reception of carrier). > > fax-modem-training-failure: The sender and receiver were unable to successfully negotiate a data rate. (Receiver was > unable to agree with the data rate suggested by the sender (or) Receiver unable to receive the facsimile per the suggested > data rate) > > Or something better .... > > Daniel. > > > -----Original Message----- > From: Michael Sweet [mailto:msweet@apple.com] > Sent: Thursday, June 27, 2013 6:22 PM > To: Manchala, Daniel > Cc: 'fx OHTAKE SHIN'; 'ipp@pwg.org' > Subject: Re: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut specification and has comments > > Daniel, > > On 2013-06-27, at 8:26 PM, "Manchala, Daniel" wrote: > > I think renaming both 'fax-modem-carrier-lost' and 'fax-modem-training-failure' to something like > 'fax-modem-confirmation-not-received' or 'fax-out-modem-confirmation-not-received' would help. The reasoning is as > follows: > > These names have already been approved (5107.3) and are in use (CUPS, which provided prototyping specifically for > the preliminary fax support via efax). > > Like I've said on many occasions, we can change the definitions all we like, but unless we want the mess of supporting > deprecated old names plus semantically identical new names I don't see the point in continuing discussion of changing > the names. > > As for fax-in-* and fax-out-*, there are enough common states between receiver and sender that I would not want to > double things up. > > > > As part of training (speed or data rate such as 9600bps) and at the end of it, a TCF (Training Check Flag) is sent > from the fax-out (sending) device to a fax-in (receiving) device. If there is a training failure, an FTT (Failure > to Train) is sent back from the fax-in receiving device to the fax-out sending device. If there is no training failure, > a CFR (Confirmation to Receive) is sent from the fax-in receiving device to the fax-out sending device. After sufficient > number of training failures (usually 3), a DCN (Disconnect) signal is sent from fax-out device to fax-in device and > the transmission stops. > > > > Likewise, if carrier is lost, there is no response received in terms of MCF (Message Confirmation) from fax-in device > at the fax-out device. > > > > In either of the two cases, a failure to detect/receive CFR or MCF from the fax-in device at the fax-out device > can trigger 'fax-out-modem-confirmation-not-received'. This is how the sending end will indicate that it lost its > connection to the receiver. > > > > We still could have 'fax-modem-carrier-lost', but on the receiving device, and probably it is good to rename it > as 'fax-in-modem-carrier-lost' indicating that this is an error on the fax-in device. Likewise, we could have > 'fax-modem-training-failure' but on the receiving device only and it is good to rename it (something) as > 'fax-in-modem-training-failure' or 'fax-in-modem-failure-to-train. > > > > I like to have the 'fax-out-*' and 'fax-in-*' syntax as it would be less confusing as to what mode a device is acting > (as a sender or receiver). > > > > Thanks, > > Daniel. > > > > > > > > -----Original Message----- > > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of > > Michael Sweet > > Sent: Thursday, June 27, 2013 5:07 AM > > To: fx OHTAKE SHIN > > Cc: ipp@pwg.org > > Subject: [IPP] Re: Fuji Xerox has reviewed the IPP FaxOut > > specification and has comments > > > > Shin, > > > > Thanks for your comments! > > > > Responses inline... > > > > On 2013-06-26, at 10:25 PM, fx OHTAKE SHIN wrote: > >> Greetings, > >> > >> Fuji Xerox has comments for the IPP FaxOut specification final call. > >> > >> ---- > >> 8.2 job-state-reasons > >> 1. fax-modem-carrier-lost > >> See ITU-T T.30(09/2005)- Annex A Examples 13, FAX MSG carrier is lost > >> by Called terminal. We think fax-modem-carrier-lost should be removed from the specification. > >> If the specification supposes another case, tell us an example on the facsimile protocol sequence. > > > > But on the sending end we still need an indication that we lost the connection to the receiver. Would changing > the definition here to something like "Lost connection to the receiver during send." be more descriptive? > > > > (in AT command set parlance, this would be a "NO CARRIER" response, > > received when the connection is lost) > > > >> 2. fax-modem-training-failure > >> See ITU-T T.30(09/2005)-Appendix IV Examples 4, Training failure is > >> detected by Called terminal. We think fax-modem-training-failure should be removed from the specification. > >> If the specification supposes another case, tell us an example on the facsimile protocol sequence. > > > > But on the sending end we still need an indication that we were unable to connect to the receiver after the receiver > answered the call. This definition has already been updated once, but I am happy to reword it again to make this clear > - basically, 'fax-modem-training-failure' means that the receiver answered, the sender got the carrier tone, but the > sender and receiver were unable to successfully negotiate a data rate. > > > > (in AT command set parlance, this is also a "NO CARRIER" response, > > received after dialing) > > > >> 3. fax-modem-voice-detected > >> If fax-modem-voice-detected specified as a job state, it should > >> change name to job-calling. Facsimile always detect sound other than > >> a carrier tone while facsimile dialing numbers to detecting any > >> facsimile signals, because facsimile may hear ringing tone or machine's voice(voice answer system), human's voice(fax > manual receive). Therefore, fax-modem-voice-detected cannot specify as an error job reason, because of ringing tone. > > > > I'm not sure I understand your comment, but a couple things: > > > > 1. We can't change the names of these keywords: they were defined and > > approved last year as part of the Printer MIB and IPP MFD Alerts spec > > (PWG 5107.3-2012). Which of course I don't have referenced and am > > re-defining the names in the IANA section (editorial changes at > > least...) [NOTE TO SELF: Add 5107.3 IANA definitions to IPP > > registrations] > > > > 2. We do want a way to indicate when the receiver answers but does not respond with a carrier within the connection > timeout setup in the modem. Again, falling back on the AT command set I would probably just get a "NO CARRIER" response > and a hang-up, but some modems did/do report "DELAYED" for the additional rings - we *could* add a keyword for that > ("fax-modem-delayed"? "fax-modem-waiting"?) but I'd like to leave this one as-is even if many implementations can't > support 'fax-modem-voice-detected'. > > > > 3. None of these are unconditionally required to implement - certain > > keywords depend on hardware features that may not be supported by your > > products, and so naturally you won't report those (similar to how you > > might not have a duplexing unit in your printer and thus don't have to > > report or support the "sides" attribute...) > > > > _________________________________________________________ > > 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 > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair ------=_NextPart_000_0188_01CE7413.7A3FB840 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIPQzCCA1owggJCoAMCAQICAQAwDQYJKoZIhvcNAQEFBQAwUDELMAkG A1UEBhMCSlAxGDAWBgNVBAoTD1NFQ09NIFRydXN0Lm5ldDEnMCUGA1UECxMe U2VjdXJpdHkgQ29tbXVuaWNhdGlvbiBSb290Q0ExMB4XDTAzMDkzMDA0MjA0 OVoXDTIzMDkzMDA0MjA0OVowUDELMAkGA1UEBhMCSlAxGDAWBgNVBAoTD1NF Q09NIFRydXN0Lm5ldDEnMCUGA1UECxMeU2VjdXJpdHkgQ29tbXVuaWNhdGlv biBSb290Q0ExMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs7P+ f9Ntse8WfFelDG12ii9Lv2T7TO6K8PMpfPX/7irg6em6W2QimppvLDomaVEF mSbc1RxqccaafR6d3XxsxoxnZ0o++HGwGSepCQymlb9LjAz6VZg72OgioUtx OHmsl5Jps4l+6iFoBpgUlofSYTa8bSdWnlfuwMBW/TLPpNmOwiPXjajz2CWs l+RwOPS2OrSdO5cmQ6OhvElZckwjMIcBWPZOvhxoVmavzUFdyLNNKlVGqx/a HuJAPdvNfbmSgJw33QyWZJ3cIvdki99h3hWUUhWgfVLJS6ghycax7cvDlWDR D/CrcPjfy01+7Nb6q9m9f1Typel5+tnWdiQocwIDAQABoz8wPTAdBgNVHQ4E FgQUoHNJmWjchVtl45soL1efvTO8B0gwCwYDVR0PBAQDAgEGMA8GA1UdEwEB /wQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAGhAqai75E9debMFtRezYBPr xpJd4NHTav77vpttv8cFbVkgxBzwt9qEWAJj+kgW70+lC/dKmPI/nhutR2tj zghH61I/eJyvTa741U/PmpgqEEE5UsTd2ZsO75MBrrIuymhCJEJssLM6Ps3p 2kjEFcvp+QcPklBJit0xl1/J6TeqO1lll5QyybOfPjpiWMVJrWIOcaUyqi/G iXZDQBMTZz2iVCUQy/E68tn620lWu6b+p0E1w+CIYcmIx982ECKYWeqwSvtW FnNurE33IqFPrR16LUUn5TDBXvLaE8slQlGVRwOMbCHMdELtU/8zi48PVwEW L8+m7slwIhS9/b5sCwMwggOoMIICkKADAgECAghDZzmIviunRjANBgkqhkiG 9w0BAQUFADA/MQswCQYDVQQGEwJKUDETMBEGA1UEChMKRnVqaSBYZXJveDEb MBkGA1UEAxMSRnVqaSBYZXJveCBYbmV0IENBMB4XDTEyMDQwMjA4MjY1N1oX DTE0MDQwMTE0NTk1OVowSDELMAkGA1UEBhMCSlAxHTAbBgNVBAoTFEZ1amkg WGVyb3ggQ28uLCBMdGQuMRowGAYDVQQDExEyMjE0NiBTaGluIE9odGFrZTCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoyYpIZWaOHMB3ikbUlamQSCT y1neW2nOWCamO5N96DwcKvnQ2EHZQfpDDmhZAjzQQ5IGpM/iuH4eQo2sZ+2E Q8gevzVDJW5nU2ypvT+yteWg/Qq6MzJjZLa4+Apt+rQVBrXBZeywXEI8vA/R 4HWIEVM/EqbxhIDssJNQYz2Foy8CAwEAAaOCASEwggEdMB8GA1UdIwQYMBaA FE2I1t2VWHXrrYgbTTIISciCBGCOMAkGA1UdEwQCMAAwPQYDVR0fBDYwNDAy oDCgLoYsaHR0cDovL2NhcHMuZnVqaXhlcm94LmNvLmpwL2NybC9meHhuZXRj YS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMAsGA1UdDwQE AwIFoDBcBgNVHSAEVTBTMFEGCysGAQQBgikBBQEGMEIwQAYIKwYBBQUHAgEW NGh0dHA6Ly93d3cuZnVqaXhlcm94LmNvLmpwL3Byb2R1Y3QvY2FwL2Z4eG5l dGNhLmh0bWwwJgYDVR0RBB8wHYEbc2hpbi5vaHRha2VAZnVqaXhlcm94LmNv LmpwMA0GCSqGSIb3DQEBBQUAA4IBAQA9Uba8PJmVy+YCm0MRvfwSjE869c9o VrUj8KmXtOdkRp5A/wsVl1wJwSY95Zo97NzLgOynIp9k8ra4cKuqkirhJFOw lE6DUWpKi05fsZtHkgG/lhuv3b6haJMkjWlYikXWIRJ7TTK0cNIxsY8wobAG mMAwASc9bzKjs6GLkPFFuqOBUNL/k2NGbvNLlstrM6wN928GZWffgFm0aLM9 OOvdhQeZanEqoBWwhCI/2n3GmYA27W/V8Guf+a/E9nhcCKZIKR5+h8tXCaox D2tx3kV9xpO1NymsQsyLrHTpwwgvZNU0+TH1nUNFNlqLmxELy+X9ORzaMYqk PeGa9jQLvUWyMIIECzCCAvOgAwIBAgIJAUWZhr9bgFB4MA0GCSqGSIb3DQEB BQUAME8xCzAJBgNVBAYTAkpQMRMwEQYDVQQKEwpGdWppIFhlcm94MSswKQYD VQQDEyJGdWppIFhlcm94IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA4 MDQyOTE1MDAwMFoXDTE0MTIxNzAyMTMzMlowPzELMAkGA1UEBhMCSlAxEzAR BgNVBAoTCkZ1amkgWGVyb3gxGzAZBgNVBAMTEkZ1amkgWGVyb3ggWG5ldCBD QTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALV3iwzXlyB/xU98 aMEFsuTOg+ogQ903jg9N3md69FGcOgR4hN6f3n90z1d3yfy2CY/p11X2KIMm xth6CZYiporeXYwOGqgCie2cbZV09YISemQjKbavqk9wqsTR+IE/5+bdnY7s sbN0F06m+UmktqrcLl5AwTBb/fIA4NPy1gaFkFCub4zOnUHF9meIzkxq63LK Tmif48ZbI1frSF7HBGuJGaqTsHtBqvetbe+Nn15OcXrNwT7YdniukhqEWYSc qUnfNCjNWGp0viZB6a3wY7gOvsAT41OlWUrb5rCnDPbzCBojdWBBZB/QSNJq fgFgEhsLQh52/abm6f5d5UM9O10CAwEAAaOB+TCB9jALBgNVHQ8EBAMCAQYw HQYDVR0OBBYEFE2I1t2VWHXrrYgbTTIISciCBGCOMB8GA1UdIwQYMBaAFOrF p1bEKFI+gqXs9VAWY4/hiC15MFgGA1UdIARRME8wTQYLKwYBBAGCKQEFAQEw PjA8BggrBgEFBQcCARYwaHR0cDovL3d3dy5mdWppeGVyb3guY28uanAvcHJv ZHVjdC9jYXAvZnhjYS5odG1sMBIGA1UdEwEB/wQIMAYBAf8CAQAwOQYDVR0f BDIwMDAuoCygKoYoaHR0cDovL2NhcHMuZnVqaXhlcm94LmNvLmpwL2NybC9m eGNhLmNybDANBgkqhkiG9w0BAQUFAAOCAQEAFfsmaMGjMqu0zTEvvAg/vkiP wzwCS3JwvTaH2R40sjZryCCN4e6yvm4aZHb86vzl/ngARXPh7lm3EMbMIMp9 M3EJhgvPgwxKH153+F31rKEPwaNWo3pQGxR7P8JxIOujZfSBoNL/bAqz+OZc I3B/LGhW6DTB4Qpatt4GZuf139CeMtW/qncnfY1snLHMlWsYzYn64+h69FwO B9ngfM6boxV3/sYAPGzjBH4IIlQ/1rpAWlIyEHoxQ15S/lVqclw7QC9D9giB Wv4/sy+80ZXsjVmhtTs42vJY3OWCy+3k0QDWNaDKlVzcmiAKWbd5jh2Ju8Im +PdmzsrEr4oEKHZyuTCCBCYwggMOoAMCAQICBBK5sKcwDQYJKoZIhvcNAQEF BQAwUDELMAkGA1UEBhMCSlAxGDAWBgNVBAoTD1NFQ09NIFRydXN0Lm5ldDEn MCUGA1UECxMeU2VjdXJpdHkgQ29tbXVuaWNhdGlvbiBSb290Q0ExMB4XDTA0 MTIxNzAyMTMzMloXDTE0MTIxNzAyMTMzMlowTzELMAkGA1UEBhMCSlAxEzAR BgNVBAoTCkZ1amkgWGVyb3gxKzApBgNVBAMTIkZ1amkgWGVyb3ggQ2VydGlm aWNhdGlvbiBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK AoIBAQC3JDX7X4x3kY0YJbxMy2IbuJf7EshbOGJRnAQ3kT3GjMYdIHJM1+27 Mf+BO8XeSQx3FL0kExFylc1hkreCJ0CtZ3dpm/VGOxtIFgdySgi4XVp0qnnA QSjUk9amAXHUNs52UqkTPKPOq9UPkLhcw5XEOZptkHAsmNdla1aDB/iTr2m9 n/8IKAY+BLM3FhW4tBbbV5wPlDq71B7yTtnHdJqarPBp/lvngARpHWvbcQ4m fRRb1JaiiWKLHW+0V0ojwN754unS9fGY+WqM3l9gb26AYDI3JPzthJpxyhtu c5EmP3FjFmuRpK/Unqt8h8nBlqJ90GgY09qQvULrG36uiweZAgMBAAGjggEH MIIBAzAdBgNVHQ4EFgQU6sWnVsQoUj6Cpez1UBZjj+GILXkwHwYDVR0jBBgw FoAUoHNJmWjchVtl45soL1efvTO8B0gwEgYDVR0TAQH/BAgwBgEB/wIBATAO BgNVHQ8BAf8EBAMCAQYwSQYDVR0fBEIwQDA+oDygOoY4aHR0cDovL3JlcG9z aXRvcnkuc2Vjb210cnVzdC5uZXQvU0MtUm9vdDEvU0NSb290MUNSTC5jcmww UgYDVR0gBEswSTBHBgoqgwiMmxtkhwUBMDkwNwYIKwYBBQUHAgEWK2h0dHBz Oi8vcmVwb3NpdG9yeS5zZWNvbXRydXN0Lm5ldC9TQy1Sb290MS8wDQYJKoZI hvcNAQEFBQADggEBAC3KeO2cIQO9t9UJXBPA4rbR4uxVxoqm8E4V34Em3CTB ZqZCJi1H9nkHBJ1dfRHctmb9vqG7LcPDMpSRHtKHYrOZAK/X4PTa7sK8ahVI 0+LaKmMnicff0xicQeVvPm6vbk7VKFRGqgaHm34AFy1Mb+Wp8W2XFZVwnBcZ RRgqfHsrYf4tkyGCMVh8H/f5QmExhyIGu9wS52rQPeLzA4BtIhC47a6aGgSx wfFK0ccMZlR974bDma+6Vb4hqzi1u9Aj5WtPiJ5x2+uRwWPlD0qjS0BMZ8x3 YvWfo5vB2pWz/jaT2fefw4WQiWFBKVPMXA2oE0v6T98qkSNEoGxMJ3eMS6Ax ggJ1MIICcQIBATBLMD8xCzAJBgNVBAYTAkpQMRMwEQYDVQQKEwpGdWppIFhl cm94MRswGQYDVQQDExJGdWppIFhlcm94IFhuZXQgQ0ECCENnOYi+K6dGMAkG BSsOAwIaBQCgggGAMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTEzMDYyODA2MjM0NFowIwYJKoZIhvcNAQkEMRYEFCH20iew hiTVE0nLgIsjSG2YYTJOMFoGCSsGAQQBgjcQBDFNMEswPzELMAkGA1UEBhMC SlAxEzARBgNVBAoTCkZ1amkgWGVyb3gxGzAZBgNVBAMTEkZ1amkgWGVyb3gg WG5ldCBDQQIIQ2c5iL4rp0YwXAYLKoZIhvcNAQkQAgsxTaBLMD8xCzAJBgNV BAYTAkpQMRMwEQYDVQQKEwpGdWppIFhlcm94MRswGQYDVQQDExJGdWppIFhl cm94IFhuZXQgQ0ECCENnOYi+K6dGMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZI hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIH MA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMA0GCSqGSIb3 DQEBAQUABIGAlIZbYilTQwYDvVC3yfmK/Uj3RFvN+4Dnf4bqNdbxmPBpC3bp 3v2AlA7Pl0zcrz1P2KsbXU4uq2du2zc+tnQqfG0w+pIIC3Ud1vDkd/QrSkRV mS6U/KWiXleVRhdt+IEMUas536soZ76QEk4rJm2pKWHwnOBxigdNSgbwHZvm CpQAAAAAAAA= ------=_NextPart_000_0188_01CE7413.7A3FB840-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --===============1035302478== 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 --===============1035302478==-- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From ipp-bounces@pwg.org Fri Jun 28 05:54:43 2013 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 CF43721F994C for ; Fri, 28 Jun 2013 05:54:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 Qv5JzdQq1BN1 for ; Fri, 28 Jun 2013 05:54:32 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 17BA121F9AC6 for ; Fri, 28 Jun 2013 05:49:08 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 69DC679294; Fri, 28 Jun 2013 08:48:25 -0400 (EDT) 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 BB78479293 for ; Fri, 28 Jun 2013 08:47:57 -0400 (EDT) MIME-version: 1.0 Received: from relay3.apple.com ([17.128.113.83]) 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 <0MP300C1YSVLAFH1@mail-out.apple.com> for ipp@pwg.org; Fri, 28 Jun 2013 05:47:51 -0700 (PDT) X-AuditID: 11807153-b7f3c6d000007b32-b8-51cd85f42ab4 Received: from [17.153.102.103] (Unknown_Domain [17.153.102.103]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 90.AF.31538.6F58DC15; Fri, 28 Jun 2013 05:47:51 -0700 (PDT) From: Michael Sweet In-reply-to: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> Date: Fri, 28 Jun 2013 08:47:47 -0400 Message-id: <77730CF6-C3BF-453E-A7EE-FF57DDA0CCA2@apple.com> References: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> To: "ipp@pwg.org" X-Mailer: Apple Mail (2.1782) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUiODMtXfd769lAg4/NfBbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgylgxZSJrwSWXitNPz7A0ML627mLk5JAQMJHY dbKbHcIWk7hwbz1bFyMXh5BAP5NE585WZpAEs0CCxNXP+8BsXgE9iaVHnjCC2MICXhKfN80E a2YTUJP4PamPFcTmFLCVaFzQxQZiswioSvzr+gHVayPxccEOoHoOoAU2Er8fR4KERQRkJVZd WMwEcYOsxLufsxgnMPLOQrJ5FpLNEHFtiWULXwPFOYBsHYnJC9GEIeyP548wLWBkW8UoUJSa k1hprJdYUJCTqpecn7uJERSGDYXBOxj/LLM6xCjAwajEw9uQeCZQiDWxrLgy9xCjBAezkghv V9PZQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8El7HA4UE0hNLUrNTUwtSi2CyTBycUg2MDVx/ zxV9i2QwWydnKv3vVtu/kvZTZcptnY9ebDr/luGjYYrxp6//u/fXi2lpLG+vnXSnVKNm1Wub o7vnt7soer4KviG9esJR2eDjrydVvewVXTVh10Pm/MUhDj/KdtXdfLnsvVvVXqUDAd9X/Lmq qWIwwSFrhtrDf3+FRfV3T+qc/3Va+LHFBUosxRmJhlrMRcWJAFYGRmg/AgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has comments 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="===============1740093576==" 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: 69DC679294.A9B58 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1740093576== Content-type: multipart/alternative; boundary="Boundary_(ID_ngViVhDz22RdEQd4eUcr5g)" --Boundary_(ID_ngViVhDz22RdEQd4eUcr5g) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Additional comments after review of the latest SM 2.0 document: Section 7.1.1: Add the following paragraph: "Note: The Semantic Model defines a single InputSource element, which does not capture all of the necessary input intent. IPP FaxOut instead maps elements from the CopyInTicket group to do so." [I wanted to add something about SM 2.0 adopting this approach, but we usually avoid prognostication in our specs...] Section 7.3: Add input-attributes-actual (1setOf collection), with reference to 7.1.1 for the member attributes. This provides a receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities. Section 7: Add new 7.x Document Description Attributes, 7.x.1 with input-attributes-actual (collection), with reference to 7.1.1 for the member attributes. This provides a per-document receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities and support for the document object. Section 9.2: Add input-attributes-actual job description attribute to list for scan-capable printers, add a new scan + document object paragraph for input-attributes-actual document description attribute. Section 12.1: Add input-attributes-actual job description and document description attributes. Section 13.1: Add reference to 5100.5 (document object) and 5108.04 (copy service) On Jun 27, 2013, at 8:12 AM, Michael Sweet wrote: > Follow-up comments based on the feedback we have gotten so far: > > Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined in PWG 5107.3. > > Section 8.2 does not define the equivalent of the 'connecting-to-defice' value from "printer-state-reasons". Should we define keyword(s) to describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected? > > Section 12.2 should not re-register PWG 5107.3 keyword values for "job-state-reasons". > > Section 13.1 is missing a reference to PWG 5107.3. > > _________________________________________________________ > 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 _________________________________________________________ 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_ngViVhDz22RdEQd4eUcr5g) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Additional comments after = review of the latest SM 2.0 document:

Section 7.1.1: Add= the following paragraph:

    "Note: The= Semantic Model defines a single InputSource element, which does not captur= e all of the necessary input intent. IPP FaxOut instead maps elements from = the CopyInTicket group to do so." [I wanted to add something about SM 2.0 a= dopting this approach, but we usually avoid prognostication in our specs...= ]

Section 7.3: Add input-attributes-actual (1setOf= collection), with reference to 7.1.1 for the member attributes. This provi= des a receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED f= or printers with scan capabilities.

Section 7: Add= new 7.x Document Description Attributes, 7.x.1 with input-attributes-actua= l (collection), with reference to 7.1.1 for the member attributes. This pro= vides a per-document receipt of hardcopy input-attributes values. CONDITION= ALLY REQUIRED for printers with scan capabilities and support for the docum= ent object.

Section 9.2: Add input-attributes-actu= al job description attribute to list for scan-capable printers, add a new s= can + document object paragraph for input-attributes-actual document descri= ption attribute.

Section 12.1: Add input-attribute= s-actual job description and document description attributes.
Section 13.1: Add reference to 5100.5 (document object) and 510= 8.04 (copy service)


On Ju= n 27, 2013, at 8:12 AM, Michael Sweet <msweet@apple.com> wrote:

Follow-up comme= nts based on the feedback we have gotten so far:

Section= 8.2 does not mention that the 'fax-modem-xxx' keywords are defined in PWG = 5107.3.

Section 8.2 does not define the equiv= alent of the 'connecting-to-defice' value from "printer-state-reasons". Sho= uld we define keyword(s) to d= escribe this and/or the following intermediate states: Dialing, Answered, Training, and Connected?

Section 12.2 should not re-register PWG 5107.3 keyword values = for "job-state-reasons".

Section 13.1 is missing a= reference to PWG 5107.3.

________________________= _________________________________
=
Michael Sweet, Senior Printing System Eng= ineer, 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
https://www.pwg.org/mailman/l= istinfo/ipp

____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_ngViVhDz22RdEQd4eUcr5g)-- --===============1740093576== 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 --===============1740093576==-- From ipp-bounces@pwg.org Fri Jun 28 06:07:29 2013 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 C193A21F8B35 for ; Fri, 28 Jun 2013 06:07:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 OI+HaO0fqr33 for ; Fri, 28 Jun 2013 06:07:22 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 46AE721F9C2E for ; Fri, 28 Jun 2013 06:05:15 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6599A7929A; Fri, 28 Jun 2013 09:04:34 -0400 (EDT) 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 DCFDA79298 for ; Fri, 28 Jun 2013 09:04:10 -0400 (EDT) MIME-version: 1.0 Received: from relay3.apple.com ([17.128.113.83]) 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 <0MP300J8XTMXBEC0@mail-out.apple.com> for ipp@pwg.org; Fri, 28 Jun 2013 06:04:09 -0700 (PDT) X-AuditID: 11807153-b7f3c6d000007b32-52-51cd89c7dd42 Received: from [17.153.102.103] (Unknown_Domain [17.153.102.103]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id 26.85.31538.8C98DC15; Fri, 28 Jun 2013 06:04:09 -0700 (PDT) From: Michael Sweet In-reply-to: <77730CF6-C3BF-453E-A7EE-FF57DDA0CCA2@apple.com> Date: Fri, 28 Jun 2013 09:04:06 -0400 Message-id: <80F4BA79-A11A-46A5-ABAF-7E181DD386D1@apple.com> References: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> <77730CF6-C3BF-453E-A7EE-FF57DDA0CCA2@apple.com> To: "ipp@pwg.org" X-Mailer: Apple Mail (2.1782) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUiODMtXfdk59lAg5fX9C2O7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAlbFl4Uv2gkvRFZdm/WduYJwV0MXIySEhYCLx aNo3ZghbTOLCvfVsXYxcHEIC/UwSCzcdZANJMAskSHx51gtWxCugJ7H0yBNGEFtYwEvi86aZ 7CA2m4CaxO9JfaxdjBwcnAK2Er9XhYGEWQRUJWYdecMC0WojMe3jSbASIYFciaW7eEHCIgKy EqsuLGaCOEFW4t3PWYwTGHlnIVk8C8liiLi2xLKFr4HiHEC2jsTkhWjCEPbH80eYFjCyrWIU KErNSaw01kssKMhJ1UvOz93ECArChsLgHYx/llkdYhTgYFTi4W1IPBMoxJpYVlyZe4hRgoNZ SYS3q+lsoBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFeCa/jgUIC6YklqdmpqQWpRTBZJg5OqQbG WnmlqPWu9aHzWyO2v9zsqSeQ7FQn8v191QbBuKL1suoHrBM3z3rU8Exs+4KTXd8/pE03Lnh3 9pPrr7qlta+P+HUsD1Pt50w5/7mPS/TiH9GuulVcZaUR07rFVQu9Q0WXFWSXcDDefnxRVdDm YWy50Q+mb/PUJ2v8PnDt9++pVr9XqumGRq9QYinOSDTUYi4qTgQAMz78fz4CAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has comments 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="===============1857293081==" 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: 6599A7929A.A991D X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1857293081== Content-type: multipart/alternative; boundary="Boundary_(ID_ZoojHyeCkbC5IwXSd+JQfA)" --Boundary_(ID_ZoojHyeCkbC5IwXSd+JQfA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Still more: Section 7.4.3: The required list of cover-sheet-info member attributes was not updated to use the new names "from-name" and "to-name". On Jun 28, 2013, at 8:47 AM, Michael Sweet wrote: > Additional comments after review of the latest SM 2.0 document: > > Section 7.1.1: Add the following paragraph: > > "Note: The Semantic Model defines a single InputSource element, which does not capture all of the necessary input intent. IPP FaxOut instead maps elements from the CopyInTicket group to do so." [I wanted to add something about SM 2.0 adopting this approach, but we usually avoid prognostication in our specs...] > > Section 7.3: Add input-attributes-actual (1setOf collection), with reference to 7.1.1 for the member attributes. This provides a receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities. > > Section 7: Add new 7.x Document Description Attributes, 7.x.1 with input-attributes-actual (collection), with reference to 7.1.1 for the member attributes. This provides a per-document receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities and support for the document object. > > Section 9.2: Add input-attributes-actual job description attribute to list for scan-capable printers, add a new scan + document object paragraph for input-attributes-actual document description attribute. > > Section 12.1: Add input-attributes-actual job description and document description attributes. > > Section 13.1: Add reference to 5100.5 (document object) and 5108.04 (copy service) > > > On Jun 27, 2013, at 8:12 AM, Michael Sweet wrote: > >> Follow-up comments based on the feedback we have gotten so far: >> >> Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined in PWG 5107.3. >> >> Section 8.2 does not define the equivalent of the 'connecting-to-defice' value from "printer-state-reasons". Should we define keyword(s) to describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected? >> >> Section 12.2 should not re-register PWG 5107.3 keyword values for "job-state-reasons". >> >> Section 13.1 is missing a reference to PWG 5107.3. >> >> _________________________________________________________ >> 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 > > _________________________________________________________ > 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 _________________________________________________________ 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_ZoojHyeCkbC5IwXSd+JQfA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Still more:

=
Section 7.4.3: The required list of cover-sheet-info member attributes= was not updated to use the new names "from-name" and "to-name".
=

On Jun 28, 2013, at 8:47 AM, Michael Sweet <= ;msweet@apple.com> wrote:
<= br class=3D"Apple-interchange-newline">
Additional comments after review of the latest SM 2.0 doc= ument:

Section 7.1.1: Add the following paragraph:
=

    "Note: The Semantic Model defines a singl= e InputSource element, which does not capture all of the necessary input in= tent. IPP FaxOut instead maps elements from the CopyInTicket group to do so= ." [I wanted to add something about SM 2.0 adopting this approach, but we u= sually avoid prognostication in our specs...]

Sect= ion 7.3: Add input-attributes-actual (1setOf collection), with reference to= 7.1.1 for the member attributes. This provides a receipt of hardcopy input= -attributes values. CONDITIONALLY REQUIRED for printers with scan capabilit= ies.

Section 7: Add new 7.x Document Description A= ttributes, 7.x.1 with input-attributes-actual (collection), with reference = to 7.1.1 for the member attributes. This provides a per-document receipt of= hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with= scan capabilities and support for the document object.

Section 9.2: Add input-attributes-actual job description attribute to= list for scan-capable printers, add a new scan + document object paragraph= for input-attributes-actual document description attribute.

=
Section 12.1: Add input-attributes-actual job description and do= cument description attributes.

Section 13.1: Add r= eference to 5100.5 (document object) and 5108.04 (copy service)
<= br>

On Jun 27, 2013, at 8:12 AM, Michael= Sweet <msweet@apple.com> wro= te:

= =
Follow-up comments based on the feedback we ha= ve gotten so far:

Section 8.2 does not mention that the = 'fax-modem-xxx' keywords are defined in PWG 5107.3.

Section 8.2 does not define the equivalent of the 'connecting-to-def= ice' value from "printer-state-reasons". Should we define keyword(s) to describe this and/or the follow= ing intermediate states:&nb= sp;Dialing, Answered, Train= ing, and Connected?

Section 12.2 shou= ld not re-register PWG 5107.3 keyword values for "job-state-reasons".
=

Section 13.1 is missing a reference to PWG 5107.3.

______________________________________________________= ___
M= ichael Sweet, Senior Printing System Engineer, PWG Chair
<= /span>


--=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
https://www.pwg.org/mailman/listinfo/ipp

___________= ______________________________________________
Michael Sweet, Senior Pri= nting System Engineer, 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
https://www.pwg.org/mailman/l= istinfo/ipp

____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_ZoojHyeCkbC5IwXSd+JQfA)-- --===============1857293081== 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 --===============1857293081==-- From ipp-bounces@pwg.org Fri Jun 28 06:38:22 2013 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 8647521F881F for ; Fri, 28 Jun 2013 06:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599] 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 8deA+M8rJBww for ; Fri, 28 Jun 2013 06:38:16 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 469FC21F91B4 for ; Fri, 28 Jun 2013 06:38:15 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8FD56792A1; Fri, 28 Jun 2013 09:37:38 -0400 (EDT) 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 62702792A0 for ; Fri, 28 Jun 2013 09:37:11 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay4.apple.com ([17.128.113.87]) 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 <0MP3003EJV52KHV1@mail-out.apple.com> for ipp@pwg.org; Fri, 28 Jun 2013 06:37:11 -0700 (PDT) X-AuditID: 11807157-b7f706d0000006c6-aa-51cd9184c765 Received: from [17.153.102.103] (Unknown_Domain [17.153.102.103]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id E5.39.01734.6819DC15; Fri, 28 Jun 2013 06:37:11 -0700 (PDT) Subject: Re: [IPP] Xerox has reviewed the IPP FaxOut specification and has comments From: Michael Sweet In-reply-to: Date: Fri, 28 Jun 2013 09:37:07 -0400 Message-id: References: <101E5D20AB29744AB6F7A3E58EBC916571AC1CAA0B@FX-JPN-EXMBV03.dc00.fujixerox.net> To: Daniel Manchala X-Mailer: Apple Mail (2.1782) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDLMWRmVeSWpSXmKPExsUiODMtXbd94tlAg8mHBS0e75jManFs30sW iyPfYh2YPbae/MHmMW/xdCaP5afWswUwR3HZpKTmZJalFunbJXBlPF/wlbFgpX5F75xtbA2M S9S6GDk5JARMJP4teMMGYYtJXLi3Hsjm4hAS6GeS+Pi1iR0kISwQLHFtTj+YzSugJ7H0yBNG EJtZQEvixr+XTCA2m4CaxO9JfawgNqdAoMS5yw1gQ1kEVCUWfbzLBFEvKzFt9Q52CFtbYtnC 18wQM20kJlx4D7V4KpPErlfXgIo4OEQE9CXOX1eFOE5W4t3PWYwTGPlnITljFpIzZiEZu4CR eRWjQFFqTmKliV5iQUFOql5yfu4mRlAYNhSG72D8t8zqEKMAB6MSD29D4plAIdbEsuLK3EOM EhzMSiK8hyecDRTiTUmsrEotyo8vKs1JLT7EKM3BoiTOK+F1PFBIID2xJDU7NbUgtQgmy8TB KdXAKLXo7KSC5z2da/oP3bC2+ziNdSKz9kO2h+8DTjbvYvbVEJ+dm531sHX9ytrVVyzXaG38 yymQExF4wnnSR8ZXrzyYn/X9TWZoCHzis8jeUvvymSkyoUr2X/wKnHd+vrtxfmzuI4nlIsLs ufOc3nI9afOd8vbn+3e3L6tvuutluXhD2O6E/GqmP0osxRmJhlrMRcWJAGHks9Q/AgAA 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: , 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: 8FD56792A1.A935A X-pwg-MailScanner-From: ipp-bounces@pwg.org Daniel, On Jun 27, 2013, at 10:37 PM, Manchala, Daniel wrote: > Section 6.1 Send-Hardcopy-Document Operation > > This is a CONDITIONALLY REQUIRED Operation. The condition is that Printers with one or more scanning accessories MUST support this operation. At the same time, it requires that a client (SHOULD) check if the Printer supports the operation by querying the "operation-supported" Printer Description, and clients discover the available input sources by querying "input-source-supported" Printer Description. Is it the case that the *client* (MUST or SHOULD ?) specify that the job input comes from a hard copy via the scan input device? This requirement makes sense for small devices which are driven from a client driver on their PC but doesn't make sense for an enterprise or work group device which is shared by many users. Enterprise or work group devices have a local user interface which allow the user to program and submit jobs. The original SM FaxOut Service spec made this operation REQUIRED (unconditionally). But even for office equipment, I think it makes sense to keep this conditionally required - consider someone at the MFD using their tablet of choice to send a fax. The application could be something created by the organization or something they've purchased as a solution, with the corresponding templates for a cover sheet, looking up of destinations from the user's address book, enforcement of corporate policy (e.g. anything faxed out has a copy sent to a corporate server for regulatory compliance), and so forth. Doing that on the MFD is conceivably possible but is cumbersome, particularly if multiple vendors and generations of products are in use. > Section 7.1 - These are all new attributes which go along with the new operation defined in section 6. As such they should be exempt (SHOULD as opposed to REQUIRED) if supplied by the user at client station. See above. > Section 7.2.2 - This attribute is specified as being "CONDITIONALLY REQUIRED". Does the REQUIRED apply to each of the member attributes? There are a number of member attributes in this section which are not supposed to be overridden by the user or client (reference to section 6 about clients gives the impression that the user supplies the values that override values from system), and some which can be optionally supplied. I can copy the minimum requirements from 7.4.3. > * 7.2.2.1 date-time - this is not able to be overridden by the submitting user. The system defines the submission time. This is part of the Semantic Model elements - if we shouldn't include this then I'll remove here and we should also remove it from the SM 2.0 elements as well. > * 7.2.2.2 from-name - this is filled in with the submitting user name (job-originating-user-name) for the job. This is the human-readable name supplied for the cover sheet. Consider an admin faxing a document for their boss. We could say something about the default from-name being the job-originating-user-name, though. > * 7.2.2.3 logo - This should be optional. It is. > * 7.2.2.4 message - This should be optional. It is. > * 7.2.2.5 organization-name - This should be optional. It is. > * 7.2.2.6 subject > > * 7.2.2.7 to-name - This should be optional. While there are cases where you blindly fax a document to a service center, there are also a lot of cases where you *do* know the recipient. Definitely optional to supply by the Client, but I think we need the Printer to support it if they support cover sheets (now just "from-name", "to-name", and "subject"). > Section 7.2.4 - 7.2.6 all three of these are CONDITIONALLY REQUIRED for spooling devices. The number-of-retries, retry-interval, and retry-time-out are all system level attributes that belong to the fax card and are not adjustable on a job per job basis. Are we suggesting that the settings for these attributes be exposed at a job level? They *are* exposed in the Semantic Model (otherwise I wouldn't have bothered). If the shouldn't be (fine by me) then I'll remove here and we need to remove from SM 2.0. If they stay then I should probably add some verbiage about Printers enforcing local regulatory requirements and reference the appropriate sections for the Printer Description attributes. > Section 7.3.1 The destination-status for each recipient is contained completely within the fax card and is only made available to the user through the confirmation sheet. The job level status reported to the UI's and job history only give the overall status of the entire job. This attribute should be changed to SHOULD. I would tend to disagree since per-destination status is needed to support Client managed retries, and it *is* part of the Semantic Model (though optional for the abstract service specification). While we *could* make this CONDITIONALLY REQUIRED for streaming devices, that seems inverted to me since a) spooling devices typically expose greater functionality and b) spooling devices may still stream for some document formats (e.g. PWG Raster). See the discussion on HP's comments for more info... > Sections 7.4.23 - 7.4.25 (printer-fax-modem-info, printer-fax-modem-name, printer-fax-modem-number) Wish that these were SHOULD as opposed to REQUIRED as this will require the gathering of the information and make it available to IPP (also privacy issues ...) - but otherwise ok. These come from the Semantic Model FaxOutServiceConfiguration group; the schema makes the FaxModems group optional here, but I think that is more a function of FaxOut also supporting non-modem fax delivery? The SM FaxOut spec doesn't say anything about this... _________________________________________________________ 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 ipp-bounces@pwg.org Fri Jun 28 07:42:35 2013 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 7059F21F9BAA for ; Fri, 28 Jun 2013 07:42:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 tWg3Xv1rogsK for ; Fri, 28 Jun 2013 07:42:30 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id AF49B21F9B97 for ; Fri, 28 Jun 2013 07:42:29 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 3C555792A6; Fri, 28 Jun 2013 10:41:47 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from exprod8og104.obsmtp.com (exprod8og104.obsmtp.com [64.18.3.88]) by pwg.org (Postfix) with ESMTP id 356B2792A5 for ; Fri, 28 Jun 2013 10:41:21 -0400 (EDT) Received: from mail-ve0-f181.google.com ([209.85.128.181]) (using TLSv1) by exprod8ob104.postini.com ([64.18.7.12]) with SMTP ID DSNKUc2gkZlDI+PhDjuGKdgR0FKGTmwU/SLL@postini.com; Fri, 28 Jun 2013 07:41:22 PDT Received: by mail-ve0-f181.google.com with SMTP id db10so1851899veb.26 for ; Fri, 28 Jun 2013 07:41:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=8uyKTa1Ad9gmSsJUaxZppIO4ob2haCHvyr9JYQRztck=; b=Q+sm9JLfCOgSjocJjOFoBOtPdPpV8PRGTwA8P5f80fW9iZjHFUC4b6IEKcYVswiiw/ TM4OIAIXHn6629ehKloFDX1+YmFvKLQW/pmCSbTdZp43JzB/XhmDfCTIKi6U1y1tjNXj +bvwQynEbfpTmfU+CYsyyhYuxkVgJWVKEm0CweTqQqpNfnaYxyZwhRW3UvzpT6wvqhJH Z3yGTX/k38FJZXwgNBxMMm5HeAavrn2iPAJZTVDKSM7Tr+7My9DdO5/cod/De0wViQpd Ved2+25b5FA78T30qkkRS6Er1IoZqW6C6A3xvgtrdSE3lSLTPr9nALwQonqz3xBNvlqd d3vA== X-Received: by 10.52.93.34 with SMTP id cr2mr4690691vdb.69.1372430480758; Fri, 28 Jun 2013 07:41:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.52.93.34 with SMTP id cr2mr4690685vdb.69.1372430480568; Fri, 28 Jun 2013 07:41:20 -0700 (PDT) Received: by 10.52.171.170 with HTTP; Fri, 28 Jun 2013 07:41:20 -0700 (PDT) Date: Fri, 28 Jun 2013 10:41:20 -0400 Message-ID: From: Barry Cavill To: ipp@pwg.org, blueroofmusic@gmail.com, ptykodi@tykodi.com, msweet@apple.com X-Gm-Message-State: ALoCoQmd2yDxRLDp+94g1TQ8BYBtFRApFVlvwdzFgBjA9+d0k2yr043PXzXkCfaWjLTTsZvfHubO+N4f4S2aKnv2Ihw0nLgDaw/a6Qz8Sn3iU8pE3P6psZsL0NynDbNw7ito8QqikL7M X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Jeremy Leber Subject: [IPP] Lexmark has reviewed the IPP FaxOut specification and has no comments 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="===============1427354527==" 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: 3C555792A6.A8F8A X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1427354527== Content-Type: multipart/alternative; boundary=20cf307c9cb44600e904e037dff9 --20cf307c9cb44600e904e037dff9 Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: Michael Sweet Date: Mon, Jun 10, 2013 at 3:35 PM Subject: [Pwg-Announce] EXTENDED: PWG Last Call of IPP FaxOut Service (05/01/13 to 06/28/13) To: "PWG Announcements Inc." All, Because we have not yet reached quorum, we need to extend the PWG Last Call of the IPP FaxOut Service specification to Friday, June 28, 2013 at 10pm US PT. Thank you everyone that has already responded to the last call. If you have not yet provided your acknowledgement for the IPP FaxOut Service specification, please do so at your earliest convenience. Thank you! On May 1, 2013, at 2:41 PM, Michael Sweet wrote: All, [This PWG Last Call starts today Wednesday May 1, 2013 and ends Friday June 7, 2013 at 10pm US PST.] This is the formal announcement of the PWG Last Call for the IPP FaxOut Service specification, located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.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 an IPP WG 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. HOW TO RESPOND Send an email with *exactly* the following subject line format: Subject: has reviewed the IPP FaxOut specification and has [no] comments WHERE TO SEND YOUR RESPONSE Please send your response to *all* of the following email addresses (replacing "dot" with '.' and "at" with '@'): ipp "at" pwg "dot" org (IPP WG mailing list - you must be subscribed!) blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP FaxOut Editor) Note that you must be subscribed to the IPP WG mailing list to send email there - otherwise your email will be silently discarded. 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 _________________________________________________________ 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 -- Barry Cavill Lexmark International Phone (859) 232-5613 Bldg 082-2 bcavill@lexmark.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --20cf307c9cb44600e904e037dff9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ----------<= br>From: Michael Sweet = <msweet@apple.com>
= Date: Mon, Jun 10, 2013 at 3:35 PM
Subject: [Pwg-Announce] EXTENDED: PWG Last Call of IPP FaxOut Service (05/0= 1/13 to 06/28/13)
To: "PWG Announcements Inc." <pwg-announce@pwg.org>


All,

Because we have not yet reached quorum, we need to = extend the PWG Last Call of the IPP FaxOut Service specification to Friday,= June 28, 2013 at 10pm US PT.

Thank you everyone t= hat has already responded to the last call. =A0If you have not yet provided= your acknowledgement for the IPP FaxOut Service specification, please do s= o at your earliest convenience.

Thank you!


On Ma= y 1, 2013, at 2:41 PM, Michael Sweet <msweet@apple.com> wrote:

All,

[This PWG Last Call starts = today Wednesday May 1, 2013 and ends Friday June 7, 2013=A0at 10pm US PST.]=

This is the formal announcement of the PWG Last Call for the IPP Fa= xOut Service=A0specification, located at:

ftp://ftp.= pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20130501.pdf

All required = attributes and values defined in this document have been prototyped by Appl= e=A0and/or other vendors. The IPP WG has completed extensive review of the = various revisions=A0of this document and an IPP WG last call.

The PWG Process/3.0 requires that a quorum (30%) of PWG voting members = must acknowledge a=A0PWG Last Call (with or without comments), before any d= ocument can progress to PWG Formal=A0Vote. =A0This PWG Last Call is NOT a F= ormal Vote but it DOES require your review=A0acknowledgment.


HOW TO RESPOND

Send an email with *exactly* the following su= bject line format:
Subject: <Company Name> has reviewed the IPP Fa= xOut specification and has [no] comments


WHERE TO SEND YOUR RESP= ONSE

Please send your response to *all* of the following email addresses (re= placing "dot" with=A0'.' and "at" with '@&#= 39;):

ipp "at" pwg "dot" org (IPP WG mailing lis= t - you must be subscribed!)
blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP W= G Co-Chair)
ptykodi "at" tykodi "dot" com (Paul Tyko= di, IPP WG Co-Chair)
msweet "at" apple "dot" com (Mi= chael Sweet, IPP WG Secretary and IPP FaxOut Editor)

Note that you must be subscribed to the IPP WG mailing list to send ema= il there -=A0otherwise your email will be silently discarded.

Please= do NOT simply reply to this note on the PWG-Announce list.

Note: Th= e PWG Definition of the Standards Development Process Version 3.0 is locate= d at:

http://www.p= wg.org/chair/membership_docs/pwg-process30.pdf

_____________________________= ____________________________
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.
_______________________________________________
pwg-announce mailing lis= t
pwg-announce= @pwg.org
https://www.pwg.org/mailman/listinfo/pwg-announce<= br>

_________________________________________________________
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.

_______________________________________________
pwg-announce mailing list
pwg-announce@pwg.org
https://www.pwg.org/mailman/listinfo/pwg-announce




--
Barry Cavill
Lexmark Internat= ional
Phone (859) 232-5613=A0=A0=A0 Bldg 082-2=A0=A0 bcavill@lexmark.com

--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --20cf307c9cb44600e904e037dff9-- --===============1427354527== 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 --===============1427354527==-- From ipp-bounces@pwg.org Fri Jun 28 10:20:28 2013 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 01C2921F9AFE for ; Fri, 28 Jun 2013 10:20:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 W2rpVxC3rvxj for ; Fri, 28 Jun 2013 10:20:22 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0EECB21F9AF3 for ; Fri, 28 Jun 2013 10:20:20 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 912DE792A8; Fri, 28 Jun 2013 13:19:53 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by pwg.org (Postfix) with ESMTP id 313A7792A5 for ; Fri, 28 Jun 2013 13:19:30 -0400 (EDT) Received: by mail-ie0-f179.google.com with SMTP id c10so4643083ieb.38 for ; Fri, 28 Jun 2013 10:19:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vgUYELujKzqm1ivJDwawu7vksac+skHynHZ1HmThhfk=; b=cE+uNn4csKT6vsHVEDJxnQbgNQOaocr3EFRP6To3bbX1qJJynFgxiM7OyJsPGeM6VD 4SJvEYE7/jcA1qKrHUImh2r18WolqdFOaRaQ7Hd5tmE7Lle3lXUpmDZS7L5Fo6F0JVmX unrfD3sEtnnJX67uvKtaDBLZjRndbjqmTh0JcN56BQer2udKDDSSIxPvP2OLNHsBS8Uz F6EqmOQi34dg52Um2isDpK9FgbhzRcr4NB137RA3r00aJBD3l3qxJem9IfaiNLHnDQ0j Xyjom2XDTpngcxPpq3iJ1E07XVdt3GlYXlJmdokMWcJXk17+FNI/vgcPy4Yyy6XEz/+N cdsA== MIME-Version: 1.0 X-Received: by 10.50.129.4 with SMTP id ns4mr4954811igb.4.1372439970473; Fri, 28 Jun 2013 10:19:30 -0700 (PDT) Received: by 10.50.13.137 with HTTP; Fri, 28 Jun 2013 10:19:30 -0700 (PDT) In-Reply-To: References: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> Date: Fri, 28 Jun 2013 13:19:30 -0400 Message-ID: Subject: Re: [IPP] Apple has reviewed the IPP FaxOut specification and has comments From: Ira McDonald To: "Manchala, Daniel" , 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="===============0888078078==" 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: 912DE792A8.AA707 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0888078078== Content-Type: multipart/alternative; boundary=047d7b1635f7ea6e3004e03a145a --047d7b1635f7ea6e3004e03a145a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Daniel, Perhaps we should add "fax-modem-dialing" as a state reason (for the Service and the FaxModem subunit) - but it's a very short-lived state to be capturing in printer-state-reasons. It's similar to the original IPP/1.1 (RFC 2911) "connecting-to-device", but that one's only intended for passing a whole Job to the output-device, not just the Job data (i.e, the FaxOut document content). BTW - I think we should NOT add "fax-modem-training", because it's a *very* short-lived state. Mike - we'll have to register this (and any other) new Printer MIB Alerts w/ IANA for the Printer MIB TC (as well as in the IPP Registry). 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 Thu, Jun 27, 2013 at 8:58 PM, Manchala, Daniel wrote: > Mike,**** > > ** ** > > Yes, one of the states we would like to have is =91fax-out-modem-dialing= =92 or > =91fax-modem-dialing=92.**** > > ** ** > > Thanks,**** > > Daniel.**** > > ** ** > > *From:* ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] *On Behalf Of *M= ichael > Sweet > *Sent:* Thursday, June 27, 2013 5:12 AM > *To:* ipp@pwg.org > *Subject:* [IPP] Apple has reviewed the IPP FaxOut specification and has > comments**** > > ** ** > > Follow-up comments based on the feedback we have gotten so far:**** > > ** ** > > Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined > in PWG 5107.3.**** > > ** ** > > Section 8.2 does not define the equivalent of the 'connecting-to-defice' > value from "printer-state-reasons". Should we define keyword(s) to > describe this and/or the following intermediate states: Dialing, Answered, > Training, and Connected?**** > > ** ** > > Section 12.2 should not re-register PWG 5107.3 keyword values for > "job-state-reasons".**** > > ** ** > > Section 13.1 is missing a reference to PWG 5107.3.**** > > ** ** > > _________________________________________________________**** > > 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 > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --047d7b1635f7ea6e3004e03a145a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi Daniel,

=
Perhaps we should add "fax-modem-dialing" as a state reason= (for the
Service and the FaxModem subunit) - but it's a very short= -lived state
to be capturing in printer-state-reasons.

It's similar to the original IPP/1.1 (RFC 2911) "connecting-to-d= evice",
but that one's only intended for passing a whole Job to= the output-device,
not just the Job data (i.e, the FaxOut document content).
BTW - I think we should NOT add "fax-modem-training"= , because it's
a *very* short-lived state.

Mike - we'll h= ave to register this (and any other) new Printer MIB Alerts
w/ IANA for the Printer MIB TC (as well as in the IPP Registry)= .

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
C= hair - 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 Thu, Jun 27, 2013 at 8:58 PM, Manchal= a, Daniel <Daniel.Manchala@xerox.com> wrote:

Mike,

=A0<= /p>

Yes, one of the states we= would like to have is =91fax-out-modem-dialing=92 or =91fax-modem-dialing= =92.

=A0<= /p>

Thanks,

Daniel.

=A0<= /p>

From: ipp-bounces@pwg.org [= mailto:ipp-bounces= @pwg.org] On Behalf Of Michael Sweet
Sent: Thursday, June 27, 2013 5:12 AM
To: ipp@pwg.org=
Subject: [IPP] Apple has reviewed the IPP FaxOut specification and h= as comments

=A0

Follow-up comments based on the feedback we have got= ten so far:

=A0

Section 8.2 does not mention that the 'fax-modem= -xxx' keywords are defined in PWG 5107.3.

=A0

Section 8.2 does not define the equivalent of the &#= 39;connecting-to-defice' value from "printer-state-reasons". = Should we define=A0keyw= ord(s) to describe this and/or the following intermediate states:=A0Dialing, Answered, Training, and Connected?

=A0

Section 12.2 should not re-register PWG 5107.3 keywo= rd values for "job-state-reasons".

=A0

Section 13.1 is missing a reference to PWG 5107.3.

=A0

____________________________________________________= _____

Michael Sweet, Senior Printing System=A0Engineer, PWG Cha= ir

=A0


--
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.

_______________________________________________
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. --047d7b1635f7ea6e3004e03a145a-- --===============0888078078== 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 --===============0888078078==-- From ipp-bounces@pwg.org Fri Jun 28 11:08:43 2013 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 4C21A21F9B93 for ; Fri, 28 Jun 2013 11:08:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 TS+hTGVMNOTI for ; Fri, 28 Jun 2013 11:08:37 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id ED08E21F8528 for ; Fri, 28 Jun 2013 11:08:36 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0E838792B2; Fri, 28 Jun 2013 14:07:55 -0400 (EDT) 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 7BBE4792AA for ; Fri, 28 Jun 2013 14:07:29 -0400 (EDT) MIME-version: 1.0 Received: from relay3.apple.com ([17.128.113.83]) 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 <0MP400M9E7O7Q8I1@mail-out.apple.com> for ipp@pwg.org; Fri, 28 Jun 2013 11:07:29 -0700 (PDT) X-AuditID: 11807153-b7f3c6d000007b32-eb-51cdd0dfe202 Received: from [17.153.30.236] (Unknown_Domain [17.153.30.236]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id DB.E2.31538.0E0DDC15; Fri, 28 Jun 2013 11:07:28 -0700 (PDT) Subject: Re: [IPP] Apple has reviewed the IPP FaxOut specification and has comments From: Michael Sweet In-reply-to: Date: Fri, 28 Jun 2013 14:07:27 -0400 Message-id: <90ECC247-FFE6-4D0A-8B38-5E485051DAEE@apple.com> References: <4E81BF05-F6EC-47DF-862E-4A5FC4DC3E61@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUiOFPuje6DC2cDDbpWW1q8frWU3eLxjsms Fsf2vWSxOPIt1oHFY+vJH2weO2fdZfeYt3g6k8fyU+vZAliiuGxSUnMyy1KL9O0SuDJu/PjH WPAqtWL2p0nsDYx9kV2MnBwSAiYS11duYISwxSQu3FvP1sXIxSEk0MskcfzDYWaQhLBAsMSk d7vBbF4BPYml/+aANTALJEisfPoYLM4moCbxe1IfK4jNKRAoMWPpChYQm0VAVWLaj4dQ9YES R7//Y+pi5ACaYyOx/YcNxK5jjBL7vpxlBYmLCGhJLHmuCGJKCMhK7PydNIGRbxaSxbOQLIaw tSWWLXwNZRtIPO18xYopri/x5t0cpgWMbKsYBYpScxIrjfUSCwpyUvWS83M3MYLCuKEweAfj n2VWhxgFOBiVeHhfzD0bKMSaWFZcmXuIUYKDWUmEl3seUIg3JbGyKrUoP76oNCe1+BCjNAeL kjivhNfxQCGB9MSS1OzU1ILUIpgsEwenVAPjhh835maaxR5ZtXrlqdSL/NUcsQ+X7tsawHhN c7b24q1SdRrnGf6aHeCIsb7zaesOOd59+/6XxjWtOmxZs1dtq39Z7qOpb0z0PI1vXHwk8fGM 1Yl983/tYp7K23XkW1XRlbvZfYUbzwh3yLnNNnySnc9bO/m9ZGN1llBt0LzKaxdsRJSCb/xi VWIpzkg01GIuKk4EAEHUFxhfAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "ipp@pwg.org" , "Manchala, Daniel" 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="===============2038976482==" 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: 0E838792B2.A9A5B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2038976482== Content-type: multipart/alternative; boundary="Boundary_(ID_hBCJy3eXiOcjws2bmRKvLQ)" --Boundary_(ID_hBCJy3eXiOcjws2bmRKvLQ) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Ira, Short-lived or not, capturing those states (and eventually, fax-modem-ringi= ng for FaxIn?) allows us to report events/traps that clients can use to pre= sent/update UI. On 2013-06-28, at 1:19 PM, Ira McDonald wrote: > Hi Daniel, >=20 > Perhaps we should add "fax-modem-dialing" as a state reason (for the=20 > Service and the FaxModem subunit) - but it's a very short-lived state > to be capturing in printer-state-reasons. >=20 > It's similar to the original IPP/1.1 (RFC 2911) "connecting-to-device", > but that one's only intended for passing a whole Job to the output-device, > not just the Job data (i.e, the FaxOut document content). >=20 > BTW - I think we should NOT add "fax-modem-training", because it's > a *very* short-lived state. >=20 > Mike - we'll have to register this (and any other) new Printer MIB Alerts > w/ IANA for the Printer MIB TC (as well as in the IPP Registry). >=20 > Cheers, > - Ira >=20 >=20 > 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 >=20 >=20 >=20 > On Thu, Jun 27, 2013 at 8:58 PM, Manchala, Daniel wrote: > Mike, >=20 >=20=20 >=20 > Yes, one of the states we would like to have is =91fax-out-modem-dialing= =92 or =91fax-modem-dialing=92. >=20 >=20=20 >=20 > Thanks, >=20 > Daniel. >=20 >=20=20 >=20 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Thursday, June 27, 2013 5:12 AM > To: ipp@pwg.org > Subject: [IPP] Apple has reviewed the IPP FaxOut specification and has co= mments >=20 >=20=20 >=20 > Follow-up comments based on the feedback we have gotten so far: >=20 >=20=20 >=20 > Section 8.2 does not mention that the 'fax-modem-xxx' keywords are define= d in PWG 5107.3. >=20 >=20=20 >=20 > Section 8.2 does not define the equivalent of the 'connecting-to-defice' = value from "printer-state-reasons". Should we define keyword(s) to describe= this and/or the following intermediate states: Dialing, Answered, Training= , and Connected? >=20 >=20=20 >=20 > Section 12.2 should not re-register PWG 5107.3 keyword values for "job-st= ate-reasons". >=20 >=20=20 >=20 > Section 13.1 is missing a reference to PWG 5107.3. >=20 >=20=20 >=20 > _________________________________________________________ >=20 > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20=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 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 >=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_hBCJy3eXiOcjws2bmRKvLQ) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Ira,

Short-lived or not, capturing those states (and eventually, fax-modem-ri= nging for FaxIn?) allows us to report events/traps that clients can use to = present/update UI.


On 2013-06-28, at= 1:19 PM, Ira McDonald <bluer= oofmusic@gmail.com> wrote:

Hi Daniel,

Perhaps we should add "fax-modem-dialing" as= a state reason (for the
Service and the FaxModem subunit) - but it's a= very short-lived state
to be capturing in printer-state-reasons.

It's similar to the original IPP/1.1 (RFC 2911) "connecting-to-device",but that one's only intended for passing a whole Job to the output-device= ,
not just the Job data (i.e, the FaxOut document content).

BTW - I think we should NOT add "fax-modem-training", because it'sa *very* short-lived state.

Mike - we'll have to register this (an= d any other) new Printer MIB Alerts
w/ IANA for the Printer MIB TC (as well as in the IPP Registry)= .

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
C= hair - 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  579 Park Place  Saline, MI  = 48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI = 49839  906-494-2434



On Thu, Jun 27, 2013 at 8:58 PM, Manchal= a, Daniel <Daniel.Manchala@xerox.com> wrote:

Mike,<= /span>

 

Yes, one = of the states we would like to have is =91fax-out-modem-dialing=92 or =91fa= x-modem-dialing=92.

 

Thanks,

Daniel.

 

From: ipp-bounces@pwg.= org [mailto:ip= p-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Thursday, June 27, 2013 5:12 AM
To: ipp@pwg.org=
Subject: [IPP] Apple has reviewed the IPP FaxOut specification and h= as comments

 

Follow-up comments based on the feedback we have go= tten so far:

 

Section 8.2 does not mention that the 'fax-mode= m-xxx' keywords are defined in PWG 5107.3.

 

Section 8.2 does not define the equivalent of t= he 'connecting-to-defice' value from "printer-state-reasons". Should we def= ine keyword(s) to = describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected?

 

Section 12.2 should not re-register PWG 5107.3 = keyword values for "job-state-reasons".

 

Section 13.1 is missing a reference to PWG 5107= .3.

 

_______________________________________________= __________

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.

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



____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_hBCJy3eXiOcjws2bmRKvLQ)-- --===============2038976482== 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 --===============2038976482==-- From ipp-bounces@pwg.org Fri Jun 28 12:31:02 2013 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 0579621F9C65 for ; Fri, 28 Jun 2013 12:31:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-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 J1A4CckHDd-R for ; Fri, 28 Jun 2013 12:30:56 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 91E6421F9C63 for ; Fri, 28 Jun 2013 12:30:55 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E34F6792B9; Fri, 28 Jun 2013 15:30:13 -0400 (EDT) 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 9D90E792AB for ; Fri, 28 Jun 2013 15:29:48 -0400 (EDT) Received: from usa7109ht003.na.xerox.net ([13.41.230.29]) by USA7109MR003.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 28 Jun 2013 14:29:47 -0500 Received: from USA7109MB013.na.xerox.net ([169.254.5.17]) by USA7109HT003.na.xerox.net ([13.41.230.29]) with mapi id 14.02.0309.002; Fri, 28 Jun 2013 14:29:41 -0500 From: "Manchala, Daniel" To: "'ipp@pwg.org'" Thread-Topic: Does IPP have a float / double attribute syntax? Thread-Index: Ac50NdPBLybyOoOtQyuTbnxIO23aUg== Date: Fri, 28 Jun 2013 19:29:40 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [13.41.230.90] MIME-Version: 1.0 X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Does IPP have a float / double attribute syntax? 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="===============1968271082==" 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: E34F6792B9.A8617 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1968271082== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1A78usa7109mb013nax_" --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1A78usa7109mb013nax_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Does IPP support a float or a double data type attribute syntax? I know it = supports boolean, integer, text, name, uri, etc. I know that CUPS which is = an IPP implementation supports float. Thanks, Daniel. --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1A78usa7109mb013nax_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does IPP support a float or a double data type attri= bute syntax? I know it supports boolean, integer, text, name, uri, etc. I k= now that CUPS which is an IPP implementation supports float.

 

Thanks,

Daniel.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_E4503CD23822BF45A1EAEDA0BC5F107404BF1A78usa7109mb013nax_-- --===============1968271082== 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 --===============1968271082==-- From ipp-bounces@pwg.org Fri Jun 28 12:59:01 2013 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 AE84021F9B89 for ; Fri, 28 Jun 2013 12:59:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.515 X-Spam-Level: X-Spam-Status: No, score=-1.515 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, 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 YYBxwjpPSoav for ; Fri, 28 Jun 2013 12:58:55 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id C2B5C21F9C18 for ; Fri, 28 Jun 2013 12:58:55 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0E1B379296; Fri, 28 Jun 2013 15:58:16 -0400 (EDT) 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 CCE7879290 for ; Fri, 28 Jun 2013 15:57:50 -0400 (EDT) MIME-version: 1.0 Received: from relay2.apple.com ([17.128.113.67]) 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 <0MP400CSCCRQAF72@mail-out.apple.com> for ipp@pwg.org; Fri, 28 Jun 2013 12:57:42 -0700 (PDT) X-AuditID: 11807143-b7f856d000000818-91-51cdeab4474d Received: from [17.153.30.236] (Unknown_Domain [17.153.30.236]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay2.apple.com (Apple SCV relay) with SMTP id DC.09.02072.5BAEDC15; Fri, 28 Jun 2013 12:57:42 -0700 (PDT) Subject: Re: [IPP] Does IPP have a float / double attribute syntax? From: Michael Sweet In-reply-to: Date: Fri, 28 Jun 2013 15:57:40 -0400 Message-id: <70E003B3-BCF7-40F4-8ACA-BE74CD944C07@apple.com> References: To: "Manchala, Daniel" X-Mailer: Apple Mail (2.1508) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUiOFPuje62V2cDDXZP4Ld4vGMyq8WxfS9Z LI58i3Vg9th68gebx7zF05k8lp9azxbAHMVlk5Kak1mWWqRvl8CV0X78JGvBF6WKbWdTGhif yHUxcnBICJhIdOzw6mLkBDLFJC7cW88GYgsJ9DJJrLqmCFIiLOAs8XhRHkiYV0BPYum/OYwg NrNAgsTuRbfBbDYBNYnfk/pYQWxOgUCJHW9XgY1hEVCVePpmKStEvaLEoXmr2SDm2Ej8+3Wa HWJVgMTuN2/B5ogIGEk8WLWYBeIyWYmdv5MmMPLNQrJ5FpLNELa2xLKFr5lnAXUwC+hITF6I Jgxhfzx/hGkBI9sqRoGi1JzESiO9xIKCnFS95PzcTYygUG0odN7BeGyZ1SFGAQ5GJR5ehwVn A4VYE8uKK3MPMUpwMCuJ8HLPAwrxpiRWVqUW5ccXleakFh9ilOZgURLnlfA6HigkkJ5Ykpqd mlqQWgSTZeLglGpgnCuyWTExZj9HkIqfQtI2LVGla9NEP7XJSc9v8txw8+GDn4+eb/2l/KrR vejc/E8/fxgvyjlZfyuvONxjH+/OLbyntSXL7B8/SRSeISyTkFk2W9HS/a2emHnD2/kBTp8i f62WXbmgT/b06vLCpvnF3NznRcPt5vIen7EgcXvv+/QVW3W59wikKrEUZyQaajEXFScCAIRU brVRAgAA 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="===============1641166325==" 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: 0E1B379296.A99DA X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1641166325== Content-type: multipart/alternative; boundary="Boundary_(ID_3MfJADkUI+Siac/cE/Au4Q)" --Boundary_(ID_3MfJADkUI+Siac/cE/Au4Q) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Daniel, On 2013-06-28, at 3:29 PM, "Manchala, Daniel" wrote: > Does IPP support a float or a double data type attribute syntax? I know it supports boolean, integer, text, name, uri, etc. No, there are no floating-point data types in IPP. > I know that CUPS which is an IPP implementation supports float. No, it actually doesn't. CUPS passes floating point numbers as name values (strings). _________________________________________________________ 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_3MfJADkUI+Siac/cE/Au4Q) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Daniel.Manchala@xerox.com<= /a>> wrote:
Does IPP support a float or a double data type attribute syntax? I = know it supports boolean, integer, text, name, uri, etc.
<= /blockquote>

No, there are no floating-point data types in IP= P.

I know that CUPS which is an IPP implementation supports float.
=

No, it actually doesn't.  CUPS= passes floating point numbers as name values (strings).

____________= _____________________________________________
Michael Sweet, Senior Prin= ting 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_3MfJADkUI+Siac/cE/Au4Q)-- --===============1641166325== 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 --===============1641166325==--