From ipp-bounces@pwg.org Tue Feb 1 08:22:25 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7FC3A6959 for ; Tue, 1 Feb 2011 08:22:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.598 X-Spam-Level: X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1a2kJ3I82TL for ; Tue, 1 Feb 2011 08:22:19 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 160173A6E3C for ; Tue, 1 Feb 2011 08:22:19 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E28D7794D1; Tue, 1 Feb 2011 11:25:19 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 48988794B0; Tue, 1 Feb 2011 11:25:01 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 1 Feb 2011 08:25:00 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Date: Tue, 1 Feb 2011 08:24:59 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Thread-Index: Acu98VrP9LA0wPhLQ86OX1TM3DvijgEN/nfQ References: From: "Petrie, Glen" To: "Michael Sweet" , X-OriginalArrivalTime: 01 Feb 2011 16:25:00.0939 (UTC) FILETIME=[92EA9DB0:01CBC22C] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: cloud@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="===============0952371233==" 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: E28D7794D1.AB23A X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0952371233== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC22C.91FBECAD" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC22C.91FBECAD Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster" =20 1. It was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation a. Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is not in line with PWG standards practices. This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with ties to a specific open-source or vendor product. Also, it should not use attribute names or variables that are identified with a specific open-source or vendor product. b. I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity. 2. The specific open-source or vendor product that is being discussed is CUPS. So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL.=20=20 a. I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition. While, I believe that Apple would provide LOA upon request. b. On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/is under GPL before Apple's ownership; then there is the question if GPL license applies. Major print vendors may be at risk of either having to release their source code that is associated with CUPS content or even being sued by GPL proponents.=20=20=20 =20 Glen =20 =20 =20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Wednesday, January 26, 2011 11:10 PM To: ipp@pwg.org Cc: cloud@pwg.org Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted =20 All, =20 I have posted a new version of the IPP Raster specification at: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf =20 This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP... =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. =20 _______________________________________________ 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. ------_=_NextPart_001_01CBC22C.91FBECAD Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster"

 

1.    It was my understand that a IEEE ISTO PWG Standard must not be the standardiza= tion of product or a specific company's implementation

a. = ;   Thus, there is a great need fo= r a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is = not in line with PWG standards practices.  This is not to say that is coul= d not have a normative or informative reference to a specific open-source or vend= or product but it should stand on its own with ties to a specific open-source = or vendor product.  Also, it should not use attribute names or variables = that are identified with a specific open-source or vendor product.

b. = ;   I am aware of other entities t= hat wish to use an established format (i.e. CUPS Raster 2); but if PWG is going= to standardize it, it should be PWG entity.

2.    The specific open-source or vendor product that is being discussed is CUPS.&nbs= p; So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL. 

a. = ;   I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition.  While, I believe that Apple would provide = LOA upon request.

b. = ;   On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/= is under GPL before Apple’s ownership; then there is the question if GPL license applies.  Major print vendors may be at risk of either having = to release their source code that is associated with CUPS content or even being sued by GPL proponents.   

 

Glen

 

 

 

-----Original Message-----
From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 PM
To: ipp@pwg.org
Cc: cloud@pwg.org
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifica= tion posted

 

All,

 

I have posted a new version of the IPP Raster specification at:

 

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-= 20110126.docx

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-= 20110126.pdf

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-= 20110126-rev.pdf

 

This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP...

 

___________________________________________________________________= _____

Michael Sweet, Senior Printing System Engineer, PWG Chair

 

 

--

This message has been scanned for viruses and

dangerous content by MailScanner, and is

believed to be clean.

 

_______________________________________________

ipp mailing list

ipp@pwg.org

https://www.pwg.org/mailman/listinfo/ipp


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC22C.91FBECAD-- --===============0952371233== 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 --===============0952371233==-- From ipp-bounces@pwg.org Tue Feb 1 09:14:18 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 058773A6C56 for ; Tue, 1 Feb 2011 09:14:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.565 X-Spam-Level: X-Spam-Status: No, score=-3.565 tagged_above=-999 required=5 tests=[AWL=1.033, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dbON27IQnt3 for ; Tue, 1 Feb 2011 09:14:16 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id C420B3A6BAE for ; Tue, 1 Feb 2011 09:14:15 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 420CC79514; Tue, 1 Feb 2011 12:17:11 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 35757792E5; Tue, 1 Feb 2011 12:16:56 -0500 (EST) Received: by fxm20 with SMTP id 20so8243149fxm.5 for ; Tue, 01 Feb 2011 09:16:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=U4AT7w3BoPZUHI3gtlzhnwnq9yls6ffWKLOt5vhMqe0=; b=WDLuQT2huhSM4We7KLQn5vtuGwxfXHMif8KUqRRKBjeTeC5+S4yw04dJxv85xNNtmo p+VuTi+8Wl0gcNmvGdRrxfkpLY2O26W0Zcp5I8kTJdtgmiT2VZb70rL9xBF8zJnpR6MJ 9DEywqmqm5+bJyHr9CX30gvoUWwSGqFMaMlzk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QiWM0JlQWqOZJ6RnixeEwJsR8S6eq41/4pyDA/frpP9I3nsB9+keg8w0U1v6QkvmvX Prp4kyHsXmK1dn1nGJuYgRCZiViSB0YzmwzumdHfF0eyA0qHpx08mLDrDNRJAkyaCknR cwmhjCE+JghSrpAVZO3rIuJ092p/5uIy+2cm0= MIME-Version: 1.0 Received: by 10.223.97.2 with SMTP id j2mr7708834fan.23.1296580616146; Tue, 01 Feb 2011 09:16:56 -0800 (PST) Received: by 10.223.123.70 with HTTP; Tue, 1 Feb 2011 09:16:55 -0800 (PST) In-Reply-To: References: Date: Tue, 1 Feb 2011 12:16:55 -0500 Message-ID: Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted From: Ira McDonald To: "Petrie, Glen" , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@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="===============1038347458==" 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: 420CC79514.AAA50 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1038347458== Content-Type: multipart/alternative; boundary=20cf3054ac790c4fe1049b3bb389 --20cf3054ac790c4fe1049b3bb389 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen, I respectfully disagree with your whole premise. The PWG collaborated very successfully with Adobe to develop PWG PDF/is - a subset and a profile of Adobe PDF. While PDF/1.7 later became the ISO 32000 standard, in 2004 the PWG was delighted to collaborate with our lead editor Rick Seeler from Adobe on PDF/is. I see no reason to treat PWG CUPS Raster any differently. Names of attributes (prefixes) are probably suitable discussion topics. But the idea that PWG should only specify a PWG raster format from scratch would set a bad precedent. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen w= rote: > I have reviewed the new proposed standard and have two concerns with > respect to the "IPP Subset of CUPS Raster" > > > > 1. It was my understand that a IEEE ISTO PWG Standard must not be the > standardization of product or a specific company's implementation > > a. Thus, there is a great need for a PWG IPP Image format or PWG IPP > Raster format; however, I believe that specifying it as a subset of the > specific open-source or vendor product is not in line with PWG standards > practices. This is not to say that is could not have a normative or > informative reference to a specific open-source or vendor product but it > should stand on its own with ties to a specific open-source or vendor > product. Also, it should not use attribute names or variables that are > identified with a specific open-source or vendor product. > > b. I am aware of other entities that wish to use an established format > (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be > PWG entity. > > 2. The specific open-source or vendor product that is being discussed > is CUPS. So, the other concern with a standard that directly references > CUPS is that CUPS is licensed by/under Apple and GPL. > > a. I have not heard or know that Apple has provided a Letter of > Assurance on the use by others for the use a subset of CUPS definition. > While, I believe that Apple would provide LOA upon request. > > b. On the other, if any or part of the content PWG is proposing to use > from CUPS was/is part of CUPS that was/is under GPL before Apple=92s > ownership; then there is the question if GPL license applies. Major print > vendors may be at risk of either having to release their source code that= is > associated with CUPS content or even being sued by GPL proponents. > > > > Glen > > > > > > > > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of > Michael Sweet > Sent: Wednesday, January 26, 2011 11:10 PM > To: ipp@pwg.org > Cc: cloud@pwg.org > Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP > Raster)specification posted > > > > All, > > > > I have posted a new version of the IPP Raster specification at: > > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf > > > > This version incorporates all of the feedback from the IPP telecon > including the rename from PWG to 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 > > -- > 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. --20cf3054ac790c4fe1049b3bb389 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen,

I respectfully disagree with your whole premise.

The= PWG collaborated very successfully with Adobe
to develop PWG PDF/is - a= subset and a profile of
Adobe=A0PDF.

While PDF/1.7 later became= the ISO 32000 standard,
in 2004 the PWG was delighted to collaborate with our
lead editor Rick = Seeler from Adobe on PDF/is.

I see no reason to treat PWG CUPS Raste= r any
differently.

Names of attributes (prefixes) are probably su= itable
discussion topics.

But the idea that PWG should only specify a PWG r= aster
format from scratch would set a bad precedent.

Cheers,
= - Ira


Ira McDonald (Musician / Software Architect)
Chair - Li= nux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=A0 PO Box 221=A0 Grand Marais, MI= 49839
=A0 906-494-2434



On Tue, Feb 1, 2011 at 11:24 AM, Petrie,= Glen <g= len.petrie@eitc.epson.com> wrote:

I= have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster"

= =A0

1.=A0=A0=A0 It was my understand that a IEEE ISTO PWG Standard must not be the standardiza= tion of product or a specific company's implementation

a.=A0=A0=A0 Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is = not in line with PWG standards practices.=A0 This is not to say that is could n= ot have a normative or informative reference to a specific open-source or vend= or product but it should stand on its own with ties to a specific open-source = or vendor product.=A0 Also, it should not use attribute names or variables tha= t are identified with a specific open-source or vendor product.

b.=A0=A0=A0 I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going= to standardize it, it should be PWG entity.

2.=A0=A0=A0 The specific open-source or vendor product that is being discussed is CUPS.=A0 = So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL.=A0

a.=A0=A0=A0 I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition.=A0 While, I believe that Apple would provide LOA= upon request.

b.=A0=A0=A0 On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/= is under GPL before Apple=92s ownership; then there is the question if GPL license applies.=A0 Major print vendors may be at risk of either having to = release their source code that is associated with CUPS content or even being sued by GPL proponents.=A0 =A0

= =A0

G= len

= =A0

= =A0

= =A0

-= ----Original Message-----
From: ipp-bounces@= pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 PM
To: ipp@pwg.org
Cc: cloud@pwg.org
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifica= tion posted

= =A0

A= ll,

= =A0

I= have posted a new version of the IPP Raster specification at:

= =A0

= =A0=A0=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-= 20110126.docx

= =A0=A0=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-2= 0110126.pdf

= =A0=A0=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster= 10-20110126-rev.pdf

= =A0

T= his version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP...

= =A0

_= _______________________________________________________________________

M= ichael Sweet, Senior Printing System Engineer, PWG Chair

= =A0

= =A0

-= -

T= his message has been scanned for viruses and

d= angerous content by MailScanner, and is

b= elieved to be clean.

= =A0

_= ______________________________________________

i= pp mailing list

<= a href=3D"mailto:ipp@pwg.org" target=3D"_blank">ipp@pwg.org

<= a href=3D"https://www.pwg.org/mailman/listinfo/ipp" target=3D"_blank">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
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. --20cf3054ac790c4fe1049b3bb389-- --===============1038347458== 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 --===============1038347458==-- From ipp-bounces@pwg.org Tue Feb 1 09:27:16 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 566AB3A6BAE for ; Tue, 1 Feb 2011 09:27:16 -0800 (PST) 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=[AWL=-0.000, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XsArOnSahHK for ; Tue, 1 Feb 2011 09:27:09 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id D4AC63A6959 for ; Tue, 1 Feb 2011 09:27:08 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6F36E79517; Tue, 1 Feb 2011 12:29:55 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 04D80794A2; Tue, 1 Feb 2011 12:29:37 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 1 Feb 2011 09:29:36 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Date: Tue, 1 Feb 2011 09:29:34 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Thread-Index: AcvCM+OZ4AuhD0sgQLe0Bcq4KNvyXgAACktQ References: From: "Petrie, Glen" To: "Ira McDonald" X-OriginalArrivalTime: 01 Feb 2011 17:29:36.0352 (UTC) FILETIME=[98D7B600:01CBC235] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@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="===============1968528148==" 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: 6F36E79517.AAF12 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1968528148== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC235.97C60AF8" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC235.97C60AF8 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable I would like to add this to the agenda as a discussion item during the IPP F2F session. If the group decides, it should not be discussed, I will retract my request. =20 Thanks, Glen =20 =20 ________________________________ From: Ira McDonald [mailto:blueroofmusic@gmail.com]=20 Sent: Tuesday, February 01, 2011 9:17 AM To: Petrie, Glen; Ira McDonald Cc: Michael Sweet; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted =20 Hi Glen, I respectfully disagree with your whole premise. The PWG collaborated very successfully with Adobe to develop PWG PDF/is - a subset and a profile of=20 Adobe PDF. While PDF/1.7 later became the ISO 32000 standard, in 2004 the PWG was delighted to collaborate with our=20 lead editor Rick Seeler from Adobe on PDF/is. I see no reason to treat PWG CUPS Raster any differently. Names of attributes (prefixes) are probably suitable discussion topics. But the idea that PWG should only specify a PWG raster=20 format from scratch would set a bad precedent. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc =20 mailto:blueroofmusic@gmail.com Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen wrote: I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster" =20 1. It was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation a. Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is not in line with PWG standards practices. This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with ties to a specific open-source or vendor product. Also, it should not use attribute names or variables that are identified with a specific open-source or vendor product. b. I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity. 2. The specific open-source or vendor product that is being discussed is CUPS. So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL.=20=20 a. I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition. While, I believe that Apple would provide LOA upon request. b. On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/is under GPL before Apple's ownership; then there is the question if GPL license applies. Major print vendors may be at risk of either having to release their source code that is associated with CUPS content or even being sued by GPL proponents.=20=20=20 =20 Glen =20 =20 =20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Wednesday, January 26, 2011 11:10 PM To: ipp@pwg.org Cc: cloud@pwg.org Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted =20 All, =20 I have posted a new version of the IPP Raster specification at: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf =20 This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP... =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. =20 _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC235.97C60AF8 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

I would like to add this to the agenda= as a discussion item during the IPP F2F session.  If the group decides, it should not be discussed, I will retract my request.

 

Thanks, Glen<= /p>

 

 


From: Ira McDo= nald [mailto:blueroofmusic@gmail.com]
Sent: Tuesday, February 01, = 2011 9:17 AM
To: Petrie, Glen; Ira McDona= ld
Cc: Michael Sweet; ipp@pwg.o= rg; cloud@pwg.org
Subject: Re: [IPP] New draft= of IPP Subset of CUPS Raster (IPP Raster)specification posted

 

Hi Glen,

I respectfully disagree with your whole premise.

The PWG collaborated very successfully with Adobe
to develop PWG PDF/is - a subset and a profile of
Adobe PDF.

While PDF/1.7 later became the ISO 32000 standard,
in 2004 the PWG was delighted to collaborate with our
lead editor Rick Seeler from Adobe on PDF/is.

I see no reason to treat PWG CUPS Raster any
differently.

Names of attributes (prefixes) are probably suitable
discussion topics.

But the idea that PWG should only specify a PWG raster
format from scratch would set a bad precedent.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.google.com/sit= e/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box= 221  Grand Marais, MI 49839
  906-494-2434



On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen <glen.petrie@eitc.epson.com&g= t; wrote:

I have reviewed the new proposed standard and have two conce= rns with respect to the "IPP Subset of CUPS Raster"

 

1.    I= t was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation

a.    T= hus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-sour= ce or vendor product is not in line with PWG standards practices.  This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with = ties to a specific open-source or vendor product.  Also, it should not use attribute names or variables that are identified with a specific open-sourc= e or vendor product.

b.    I= am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity.<= o:p>

2.    T= he specific open-source or vendor product that is being discussed is CUPS.&nbs= p; So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL. 

a.    I= have not heard or know that Apple has provided a Letter of Assurance on the use = by others for the use a subset of CUPS definition.  While, I believe that Apple would provide LOA upon request.

b.    O= n the other, if any or part of the content PWG is proposing to use from CUPS was/= is part of CUPS that was/is under GPL before Apple’s ownership; then the= re is the question if GPL license applies.  Major print vendors may be at risk of either having to release their source code that is associated with = CUPS content or even being sued by GPL proponents.   

 

Glen

 

 

 

-----Original Message-----
From: ipp-bounces@= pwg.org [mailto:ipp-bounce= s@pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 PM
To: ipp@pwg.org
Cc: cloud@pwg.org
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifica= tion posted

 

All,

 

I have posted a new version of the IPP Raster specification = at:

 

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.= docx

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.= pdf

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-= rev.pdf

 

This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP...

 

____________________________________________________________= ____________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 

 

--

This message has been scanned for viruses and<= o:p>

dangerous content by MailScanner, and is<= /o:p>

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.


_______________________________________________
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. ------_=_NextPart_001_01CBC235.97C60AF8-- --===============1968528148== 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 --===============1968528148==-- From ipp-bounces@pwg.org Tue Feb 1 10:46:26 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 278FF3A679F for ; Tue, 1 Feb 2011 10:46:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.598 X-Spam-Level: X-Spam-Status: No, score=-103.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, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRyPPnhUHQiu for ; Tue, 1 Feb 2011 10:46:24 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A89AB3A6FDD for ; Tue, 1 Feb 2011 10:46:05 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BF34F79525; Tue, 1 Feb 2011 13:49:00 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 2578D7951B; Tue, 1 Feb 2011 13:48:42 -0500 (EST) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 2CF9CCBE371B; Tue, 1 Feb 2011 10:48:42 -0800 (PST) X-AuditID: 11807137-b7baaae000007a67-2c-4d485588a9dd Received: from [17.153.100.199] (Unknown_Domain [17.153.100.199]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 9F.F0.31335.985584D4; Tue, 1 Feb 2011 10:48:41 -0800 (PST) Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Tue, 1 Feb 2011 08:48:41 -1000 Message-Id: <47529FA7-9CEF-4CCF-AB9C-0EC020005207@apple.com> References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@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="===============0006131753==" 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: BF34F79525.AB1AF X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0006131753== Content-Type: multipart/alternative; boundary=Apple-Mail-6-451341873 --Apple-Mail-6-451341873 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Glen, I'll add it at lunch today for tomorrow's meeting... On Feb 1, 2011, at 7:29 AM, Petrie, Glen wrote: > I would like to add this to the agenda as a discussion item during the IP= P F2F session. If the group decides, it should not be discussed, I will re= tract my request. >=20=20 > Thanks, Glen >=20=20 >=20=20 > From: Ira McDonald [mailto:blueroofmusic@gmail.com]=20 > Sent: Tuesday, February 01, 2011 9:17 AM > To: Petrie, Glen; Ira McDonald > Cc: Michael Sweet; ipp@pwg.org; cloud@pwg.org > Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)spe= cification posted >=20=20 > Hi Glen, >=20 > I respectfully disagree with your whole premise. >=20 > The PWG collaborated very successfully with Adobe > to develop PWG PDF/is - a subset and a profile of=20 > Adobe PDF. >=20 > While PDF/1.7 later became the ISO 32000 standard, > in 2004 the PWG was delighted to collaborate with our=20 > lead editor Rick Seeler from Adobe on PDF/is. >=20 > I see no reason to treat PWG CUPS Raster any > differently. >=20 > Names of attributes (prefixes) are probably suitable > discussion topics. >=20 > But the idea that PWG should only specify a PWG raster=20 > format from scratch would set a bad precedent. >=20 > Cheers, > - Ira >=20 >=20 > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Hardcopy WG > 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 > Christmas through April: > 579 Park Place Saline, MI 48176 > 734-944-0094 > May to Christmas: > PO Box 221 Grand Marais, MI 49839 > 906-494-2434 >=20 >=20 >=20 > On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen wrote: > I have reviewed the new proposed standard and have two concerns with resp= ect to the "IPP Subset of CUPS Raster" >=20 >=20=20 >=20 > 1. It was my understand that a IEEE ISTO PWG Standard must not be the = standardization of product or a specific company's implementation >=20 > a. Thus, there is a great need for a PWG IPP Image format or PWG IPP R= aster format; however, I believe that specifying it as a subset of the spec= ific open-source or vendor product is not in line with PWG standards practi= ces. This is not to say that is could not have a normative or informative = reference to a specific open-source or vendor product but it should stand o= n its own with ties to a specific open-source or vendor product. Also, it = should not use attribute names or variables that are identified with a spec= ific open-source or vendor product. >=20 > b. I am aware of other entities that wish to use an established format= (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be = PWG entity. >=20 > 2. The specific open-source or vendor product that is being discussed = is CUPS. So, the other concern with a standard that directly references CU= PS is that CUPS is licensed by/under Apple and GPL.=20 >=20 > a. I have not heard or know that Apple has provided a Letter of Assura= nce on the use by others for the use a subset of CUPS definition. While, I= believe that Apple would provide LOA upon request. >=20 > b. On the other, if any or part of the content PWG is proposing to use= from CUPS was/is part of CUPS that was/is under GPL before Apple=92s owner= ship; then there is the question if GPL license applies. Major print vendo= rs may be at risk of either having to release their source code that is ass= ociated with CUPS content or even being sued by GPL proponents.=20=20=20 >=20 >=20=20 >=20 > Glen >=20 >=20=20 >=20 >=20=20 >=20 >=20=20 >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Wednesday, January 26, 2011 11:10 PM > To: ipp@pwg.org > Cc: cloud@pwg.org > Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifi= cation posted >=20 >=20=20 >=20 > All, >=20 >=20=20 >=20 > I have posted a new version of the IPP Raster specification at: >=20 >=20=20 >=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx >=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf >=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf >=20 >=20=20 >=20 > This version incorporates all of the feedback from the IPP telecon includ= ing the rename from PWG to IPP... >=20 >=20=20 >=20 > ________________________________________________________________________ >=20 > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20=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 >=20 > _______________________________________________ >=20 > ipp mailing list >=20 > ipp@pwg.org >=20 > https://www.pwg.org/mailman/listinfo/ipp >=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=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. --Apple-Mail-6-451341873 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Glen,

I= 'll add it at lunch today for tomorrow's meeting...

On Fe= b 1, 2011, at 7:29 AM, Petrie, Glen wrote:

I would like to add this to the agenda= as a discussion item during the IPP F2F session.  If the group decides, it should not be discussed, I will retract my request.

=  

Thanks, Glen<= /p>

 

 


From: Ira = McDonald [mailto:blueroofmusic@gmail.com]
Sent: Tuesday, February 01, = 2011 9:17 AM
To: Petrie, Glen; Ira McDona= ld
Cc: Michael Sweet; ipp@pwg.org; cloud@pwg.org
Subject: Re: [IPP] New draft= of IPP Subset of CUPS Raster (IPP Raster)specification posted

 

Hi Glen,

I respectfully disagree with your whole premise.

The PWG collaborated very successfully with Adobe
to develop PWG PDF/is - a subset and a profile of
Adobe PDF.

While PDF/1.7 later became the ISO 32000 standard,
in 2004 the PWG was delighted to collaborate with our
lead editor Rick Seeler from Adobe on PDF/is.

I see no reason to treat PWG CUPS Raster any
differently.

Names of attributes (prefixes) are probably suitable
discussion topics.

But the idea that PWG should only specify a PWG raster
format from scratch would set a bad precedent.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.google.com/= site/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box= 221  Grand Marais, MI 49839
  906-494-2434



On Tue, Feb 1, 2011 at 11:24 AM, Petrie, Glen <glen.petrie@eitc.epson.com> wrote:

I have reviewed the new proposed standard and have= two concerns with respect to the "IPP Subset of CUPS Raster"

 

1.    It = was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation

a.    Thu= s, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-sour= ce or vendor product is not in line with PWG standards practices.  This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with = ties to a specific open-source or vendor product.  Also, it should not use attribute names or variables that are identified with a specific open-sourc= e or vendor product.

b.    I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity.<= o:p>

2. &nb= sp;  The specific open-source or vendor product that is being discussed is CUPS.&nbs= p; So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL. 

a.    I = have not heard or know that Apple has provided a Letter of Assurance on the use = by others for the use a subset of CUPS definition.  While, I believe that Apple would provide LOA upon request.

b.    On the other, if any or part of the content PWG is proposing to use from CUPS was/= is part of CUPS that was/is under GPL before Apple=92s ownership; then there is the question if GPL license applies.  Major print vendors may be at risk of either having to release their source code that is associated with = CUPS content or even being sued by GPL proponents.   

 

Glen

 

 

 

-----Original Message-----
From: ipp-bounces@= pwg.org [mailto:ipp-bounce= s@pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 PM
To: ipp@pwg.org
Cc: cloud@pwg.org
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifica= tion posted

 

All,

 

I have posted a new version of the IPP Raster spec= ification at:

 

    ftp://ftp.pwg.= org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx

    ftp://ftp.pwg.o= rg/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf<= /p>

    ftp://ftp.p= wg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf

 

This version incorporates all of the feedback from= the IPP telecon including the rename from PWG to IPP...

 

__________________________________________________= ______________________

Michael Sweet, Senior Printing System Engineer, PW= G Chair

 

 

--

This message has been scanned for viruses and

dangerous content by MailScanner, and is

believed to be clean.

=

 

_______________________________________________

ipp mailing list

i= pp@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.


_______________________________________________
ipp mailing list
ipp@pwg.org
http= s://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. --Apple-Mail-6-451341873-- --===============0006131753== 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 --===============0006131753==-- From ipp-bounces@pwg.org Wed Feb 2 00:13:14 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A422B3A6BBC for ; Wed, 2 Feb 2011 00:13:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.798 X-Spam-Level: X-Spam-Status: No, score=-103.798 tagged_above=-999 required=5 tests=[AWL=0.799, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CwcG5ZdjHFb for ; Wed, 2 Feb 2011 00:13:12 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 4C3F03A6AF0 for ; Wed, 2 Feb 2011 00:13:12 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 4D92579532; Wed, 2 Feb 2011 03:16:14 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 67EE979522; Wed, 2 Feb 2011 03:16:00 -0500 (EST) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 7D07DCC0E3AB; Wed, 2 Feb 2011 00:15:59 -0800 (PST) X-AuditID: 11807137-b7baaae000007a67-72-4d4912bd4192 Received: from [17.153.99.193] (Unknown_Domain [17.153.99.193]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 9F.BB.31335.DB2194D4; Wed, 2 Feb 2011 00:15:59 -0800 (PST) Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Tue, 1 Feb 2011 22:15:56 -1000 Message-Id: References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@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="===============1444762629==" 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: 4D92579532.AACB8 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1444762629== Content-Type: multipart/alternative; boundary=Apple-Mail-3-499777066 --Apple-Mail-3-499777066 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Glen, In response to your concerns: 1. PWG Process 3.0 (http://www.pwg.org/chair/membership_docs/pwg-process30.= pdf) does not specify that a PWG standard must be an original creation of t= he PWG or that it cannot be based on an existing vendor, industry, or group= standard. In fact, most PWG standards are necessarily based on existing st= andards from different sources. That said, if you have an alternative exist= ing format you would like to propose as an alternative to CUPS Raster, ple= ase do so now. 2. The reference implementation of CUPS Raster is provided under version 2 = of the GNU LGPL and nothing would prevent a vendor from doing an independen= t implementation under alternative terms. Also, since CUPS Raster has not b= een formally included in any PWG standard to date, Apple naturally has not = provided a LOA for that IP (yet). Hope this clears things up! On Feb 1, 2011, at 6:24 AM, Petrie, Glen wrote: > I have reviewed the new proposed standard and have two concerns with resp= ect to the "IPP Subset of CUPS Raster" >=20=20 > 1. It was my understand that a IEEE ISTO PWG Standard must not be the = standardization of product or a specific company's implementation > a. Thus, there is a great need for a PWG IPP Image format or PWG IPP R= aster format; however, I believe that specifying it as a subset of the spec= ific open-source or vendor product is not in line with PWG standards practi= ces. This is not to say that is could not have a normative or informative = reference to a specific open-source or vendor product but it should stand o= n its own with ties to a specific open-source or vendor product. Also, it = should not use attribute names or variables that are identified with a spec= ific open-source or vendor product. > b. I am aware of other entities that wish to use an established format= (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be = PWG entity. > 2. The specific open-source or vendor product that is being discussed = is CUPS. So, the other concern with a standard that directly references CU= PS is that CUPS is licensed by/under Apple and GPL.=20 > a. I have not heard or know that Apple has provided a Letter of Assura= nce on the use by others for the use a subset of CUPS definition. While, I= believe that Apple would provide LOA upon request. > b. On the other, if any or part of the content PWG is proposing to use= from CUPS was/is part of CUPS that was/is under GPL before Apple=92s owner= ship; then there is the question if GPL license applies. Major print vendo= rs may be at risk of either having to release their source code that is ass= ociated with CUPS content or even being sued by GPL proponents.=20=20=20 >=20=20 > Glen >=20=20 >=20=20 >=20=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Wednesday, January 26, 2011 11:10 PM > To: ipp@pwg.org > Cc: cloud@pwg.org > Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifi= cation posted >=20=20 > All, >=20=20 > I have posted a new version of the IPP Raster specification at: >=20=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf >=20=20 > This version incorporates all of the feedback from the IPP telecon includ= ing the rename from PWG to IPP... >=20=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20=20 > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20=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. --Apple-Mail-3-499777066 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 http://www.pwg.org/chair/membership_= docs/pwg-process30.pdf) does not specify that a PWG standard must be an= original creation of the PWG or that it cannot be based on an existing ven= dor, industry, or group standard. In fact, most PWG standards are necessari= ly based on existing standards from different sources. That said, if you ha= ve an alternative existing format you would like to propose as an alternati= ve to CUPS  Raster, please do so now.

2. The = reference implementation of CUPS Raster is provided under version 2 of the = GNU LGPL and nothing would prevent a vendor from doing an independent imple= mentation under alternative terms. Also, since CUPS Raster has not been for= mally included in any PWG standard to date, Apple naturally has not provide= d a LOA for that IP (yet).

Hope this clears things= up!


On Feb 1, 2011, at 6:24 AM, Pe= trie, Glen wrote:
I have reviewed the new prop= osed standard and have two concerns with respect to the "IPP Subset of CUPS= Raster"
 
1.    It was my understand that a IEEE ISTO PWG Standard must not be the stan= dardization of product or a specific company's implementation
a.  =   Thus, there is a great need for a PWG IPP Image format or = PWG IPP Raster format; however, I believe that specifying it as a subset of= the specific open-source or vendor product is not in line with PWG standar= ds practices.  This is not to say that is could not have a normative o= r informative reference to a specific open-source or vendor product but it = should stand on its own with ties to a specific open-source or vendor produ= ct.  Also, it should not use attribute names or variables that are ide= ntified with a specific open-source or vendor product.
b.    I am aware of other entities that wish to use an established format= (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be = PWG entity.
2.    = The specific open-source or vendo= r product that is being discussed is CUPS.  So, the other concern with= a standard that directly references CUPS is that CUPS is licensed by/under= Apple and GPL. 
a.    I have not heard or know = that Apple has provided a Letter of Assurance on the use by others for the = use a subset of CUPS definition.  While, I believe that Apple would pr= ovide LOA upon request.
b.    On the other, if any = or part of the content PWG is proposing to use from CUPS was/is part of CUP= S that was/is under GPL before Apple=92s ownership; then there is the quest= ion if GPL license applies.  Major print vendors may be at risk of eit= her having to release their source code that is associated with CUPS conten= t or even being sued by GPL proponents.   
 
Glen
 
 
 
-----Original Message-----
From: ipp-bounces@pwg.org=  [mailto:ipp-bounces@pwg.= org] On Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 = PM
To: ipp@pwg= .org
Cc:  
All,=
 
I have posted a new version of the IPP= Raster specification at:
 <= /div>
 
This version incorporates all of the feedbac= k from the IPP telecon including the rename from PWG to IPP...
 
______________________________________________= __________________________
Michael Sweet, Senior Printing = System Engineer, PWG Chair
 =
&n= bsp;
--
This message has been scanned for viru= ses and
dangerous content by MailScanner, and is
believed to be clean.
 
<= font size=3D"2" face=3D"Courier New">____= ___________________________________________
<= div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; m= argin-left: 0in; font-size: 10pt; font-family: 'Courier New'; ">ipp mailing l= ist

_______________________________________________= _________________________
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. --Apple-Mail-3-499777066-- --===============1444762629== 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 --===============1444762629==-- From ipp-bounces@pwg.org Wed Feb 2 06:43:56 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDA5F3A6D1F for ; Wed, 2 Feb 2011 06:43:56 -0800 (PST) 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=[AWL=-0.000, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYOReE3Akt8D for ; Wed, 2 Feb 2011 06:43:47 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 7D3BD3A6B20 for ; Wed, 2 Feb 2011 06:43:47 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id F01FC79533; Wed, 2 Feb 2011 09:46:35 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 0E2B479526; Wed, 2 Feb 2011 09:46:19 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Feb 2011 06:46:17 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Date: Wed, 2 Feb 2011 06:46:17 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted Thread-Index: AcvCsXjEeHJ4o2QuQLu67bSDwK+x2gAMeeuw References: From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 02 Feb 2011 14:46:17.0772 (UTC) FILETIME=[F2D8CEC0:01CBC2E7] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@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="===============0631393693==" 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: F01FC79533.AB1AE X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0631393693== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC2E7.F2658E5F" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC2E7.F2658E5F Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable It does not really clear things up for me, sorry. I guess I still see a PWG standard being based on an element (headers and code) of vendor product that has origins as GPL code. =20 Alternatives: While I do not know of "vendor, industry or group standard" with an acceptable job/"raster" (really, job/image (really, job/content)) format that is similar to CUPS raster, I would suggest something like the following. =20 Format: Job Ticket, =20 Job Ticket content =3D=3D JTAPI from OpenPrinting (CPL License and completely available to all to use without GPL "hooks" or concerns).=20=20= =20 =20 Note JTAPI was derived to be consistent with IPP!!! =20 Page overrides =3D=3D only those JTAPI elements that need individual page override Page content =3D=3D Byte-wise Run-Length compressed "sRGB" or other image/color-space data format(s). In future, this is extensible to other data formats that could include vector, jpeg, etc =20 This has the same objective as CUPS raster but is based on public standards and code elements that have free licenses. There already exist CPL based header file for JTAPI job elements and an approved public standard. The standard provides compliance for mobile, SOHO, office and production printing domains/applications. This approach could reduce the 1800 bytes / page overhead of CUPS Raster 2 to a few bytes if no page override needed (the most likely use case) along with alignment of other small details in CUPS raster. =20 Glen =20 =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Wednesday, February 02, 2011 12:16 AM To: Petrie, Glen Cc: ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted =20 Glen, =20 In response to your concerns: =20 1. PWG Process 3.0 (http://www.pwg.org/chair/membership_docs/pwg-process30.pdf) does not specify that a PWG standard must be an original creation of the PWG or that it cannot be based on an existing vendor, industry, or group standard. In fact, most PWG standards are necessarily based on existing standards from different sources. That said, if you have an alternative existing format you would like to propose as an alternative to CUPS Raster, please do so now. =20 2. The reference implementation of CUPS Raster is provided under version 2 of the GNU LGPL and nothing would prevent a vendor from doing an independent implementation under alternative terms. Also, since CUPS Raster has not been formally included in any PWG standard to date, Apple naturally has not provided a LOA for that IP (yet). =20 Hope this clears things up! =20 =20 On Feb 1, 2011, at 6:24 AM, Petrie, Glen wrote: =09 I have reviewed the new proposed standard and have two concerns with respect to the "IPP Subset of CUPS Raster" =09=20 1. It was my understand that a IEEE ISTO PWG Standard must not be the standardization of product or a specific company's implementation a. Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-source or vendor product is not in line with PWG standards practices. This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with ties to a specific open-source or vendor product. Also, it should not use attribute names or variables that are identified with a specific open-source or vendor product. b. I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity. 2. The specific open-source or vendor product that is being discussed is CUPS. So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL.=20 a. I have not heard or know that Apple has provided a Letter of Assurance on the use by others for the use a subset of CUPS definition. While, I believe that Apple would provide LOA upon request. b. On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/is under GPL before Apple's ownership; then there is the question if GPL license applies. Major print vendors may be at risk of either having to release their source code that is associated with CUPS content or even being sued by GPL proponents.=20=20=20 =09=20 Glen =09=20 =09=20 =09=20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Wednesday, January 26, 2011 11:10 PM To: ipp@pwg.org Cc: cloud@pwg.org Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specification posted =09=20 All, =09=20 I have posted a new version of the IPP Raster specification at: =09=20 =09 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126.pdf =09 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110126-rev.pdf =09=20 This version incorporates all of the feedback from the IPP telecon including the rename from PWG to IPP... =09=20 =09 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =09=20 =09=20 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. =09=20 _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp =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_01CBC2E7.F2658E5F Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

It does not really clear things up for= me, sorry.  I guess I still see a PWG standard being based on an element (= headers and code) of vendor product that has origins as GPL code.=

 

Alternatives: While I do not know of &= #8220;vendor, industry or group standard” with an acceptable job/”raster̶= 1; (really, job/image (really, job/content)) format that is similar to CUPS ra= ster, I would suggest something like the following.

 

Format: Job Ticket, <Page Overrides= , Page content (image or maybe something else) …….. n-number of pages&= gt;

 

Job Ticket content =3D=3D JTAPI from O= penPrinting  (CPL License and completely available to all to use without GPL “hook= s” or concerns).  

 

      &n= bsp;            = ;            &n= bsp;    Note JTAPI was derived to be consistent with IPP!!!

 

Page overrides      =3D=3D only those JTAPI elements th= at need individual page override

Page content        =3D=3D Byte-wise Run-Leng= th compressed “sRGB” or other image/color-space data format(s).&nb= sp; In future, this is extensible to other data formats that could include vect= or, jpeg, etc

 

This has the same objective as CUPS ra= ster but is based on public standards and code elements that have free licenses.=   There already exist CPL based header file for JTAPI job elements and an app= roved public standard.  The standard provides compliance for mobile, SOHO, office and production printing domains/applic= ations. This approach could reduce the 1800 bytes / page overhead of CUPS Raster 2 = to a few bytes if no page override needed (the most likely use case) along with alignment of other small details in CUPS raster.

 

Glen

 

 


From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Wednesday, February 02= , 2011 12:16 AM
To: Petrie, Glen
Cc: ipp@pwg.org; cloud@pwg.o= rg
Subject: Re: [IPP] New draft= of IPP Subset of CUPS Raster (IPP Raster)specification posted

 

Glen,

 

In response to your concerns:

 

1. PWG Process 3.0 (http://= www.pwg.org/chair/membership_docs/pwg-process30.pdf) does not specify that a PWG standard must be an original creation of the PW= G or that it cannot be based on an existing vendor, industry, or group standard.= In fact, most PWG standards are necessarily based on existing standards from different sources. That said, if you have an alternative existing format you would like to propose as an alternative to CUPS  Raster, please do so = now.

 

2. The reference implementation of CUPS Raster is provided under version 2 of the GNU LGPL and nothing would prevent a vendor from doing an independent implementation under alternative terms. Also, since CUPS Raster= has not been formally included in any PWG standard to date, Apple naturally has= not provided a LOA for that IP (yet).

 

Hope this clears things up!

 

 

On Feb 1, 2011, at 6:24 AM, Petrie, Glen wrote:

I have reviewed the new proposed standard and ha= ve two concerns with respect to the "IPP Subset of CUPS Raster"

 

1.    It was my understand that a IEEE ISTO PWG Standard must not be the standardiza= tion of product or a specific company's implementation<= /p>

a.    Thus, there is a great need for a PWG IPP Image format or PWG IPP Raster format; however, I believe that specifying it as a subset of the specific open-sour= ce or vendor product is not in line with PWG standards practices.  This is not to say that is could not have a normative or informative reference to a specific open-source or vendor product but it should stand on its own with = ties to a specific open-source or vendor product.  Also, it should not use attribute names or variables that are identified with a specific open-sourc= e or vendor product.

b.    I am aware of other entities that wish to use an established format (i.e. CUPS Raster 2); but if PWG is going to standardize it, it should be PWG entity.<= o:p>

2.    The specific open-source or vendor product that is being discussed is CUPS.&nbs= p; So, the other concern with a standard that directly references CUPS is that CUPS is licensed by/under Apple and GPL. 

a.    I have not heard or know that Apple has provided a Letter of Assurance on the= use by others for the use a subset of CUPS definition.  While, I believe t= hat Apple would provide LOA upon request.

b.    On the other, if any or part of the content PWG is proposing to use from CUPS was/is part of CUPS that was/is under GPL before Apple’s ownership; t= hen there is the question if GPL license applies.  Major print vendors may= be at risk of either having to release their source code that is associated wi= th CUPS content or even being sued by GPL proponents.   <= /span>

 

Glen

 

 

 

-----Original Message-----
From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On = Behalf Of Michael Sweet
Sent: Wednesday, January 26, 2011 11:10 PM
To: ipp@pwg.org
Cc: cloud@pwg.org
Subject: [IPP] New draft of IPP Subset of CUPS Raster (IPP Raster)specifica= tion posted

 

All,

 

I have posted a new version of the IPP Raster specification at:

 

 

This version incorporates all of the feedback fr= om the IPP telecon including the rename from PWG to 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.

 

_______________________________________________<= u1:p>

ipp mailing list<= /font>

 

______________= __________________________________________________________
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_01CBC2E7.F2658E5F-- --===============0631393693== 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 --===============0631393693==-- From pwg-announce-bounces@pwg.org Wed Feb 2 14:49:32 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F5263A6C72 for ; Wed, 2 Feb 2011 14:49:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.932 X-Spam-Level: X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wVbOKhkTDtg for ; Wed, 2 Feb 2011 14:49:31 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id B86383A688A for ; Wed, 2 Feb 2011 14:49:31 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id ED17A79525; Wed, 2 Feb 2011 17:52:36 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id DBE5979522 for ; Wed, 2 Feb 2011 17:52:22 -0500 (EST) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 9D6A2CC380CE for ; Wed, 2 Feb 2011 14:52:14 -0800 (PST) X-AuditID: 11807130-b7b3cae00000405d-99-4d49e01a2ece Received: from [17.153.95.81] (Unknown_Domain [17.153.95.81]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id A1.92.16477.D10E94D4; Wed, 2 Feb 2011 14:52:14 -0800 (PST) From: Michael R Sweet Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (8C148) Message-Id: <7CE3C2F6-D1A0-4FB5-83B1-76561E3E2694@apple.com> Date: Wed, 2 Feb 2011 12:47:56 -1000 To: pwg-announce@pwg.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8C148) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] Delaying start of plenary to 1:30pm X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: ED17A79525.ACF71 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org All, Due to our offsite lunch we are going to delay the start of the plenary to = 1:30pm Hawaii time. Sent from my iPhone --=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 From ipp-bounces@pwg.org Wed Feb 2 19:09:56 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C11F3A67C3 for ; Wed, 2 Feb 2011 19:09:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.884 X-Spam-Level: X-Spam-Status: No, score=-102.884 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvgXNXKFV6Ns for ; Wed, 2 Feb 2011 19:09:53 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 60B0C3A67C1 for ; Wed, 2 Feb 2011 19:09:53 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BE06079540; Wed, 2 Feb 2011 22:13:00 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id 9AD3A7951E for ; Wed, 2 Feb 2011 22:12:48 -0500 (EST) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id AB335CFC31FA for ; Wed, 2 Feb 2011 19:12:47 -0800 (PST) X-AuditID: 11807134-b7c40ae000006cb9-5e-4d4a1d2e0f75 Received: from [17.153.56.178] (Unknown_Domain [17.153.56.178]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 18.A1.27833.F2D1A4D4; Wed, 2 Feb 2011 19:12:47 -0800 (PST) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 2 Feb 2011 17:12:46 -1000 To: ipp@pwg.org Message-Id: <0D279E6E-768B-4DA0-BA00-213E14DB2D07@apple.com> Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] F2F meeting minutes posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: BE06079540.A95FD X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted the minutes from today's F2F meeting at: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20110202.pdf Please let me know if I missed anything or anyone... ________________________________________________________________________ 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 Feb 3 08:29:13 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BCC53A69FD for ; Thu, 3 Feb 2011 08:29:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.597 X-Spam-Level: X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id omjau0v7aZlE for ; Thu, 3 Feb 2011 08:29:01 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 931033A69D1 for ; Thu, 3 Feb 2011 08:29:00 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0990479556; Thu, 3 Feb 2011 11:31:23 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 1DACF7954F; Thu, 3 Feb 2011 11:31:06 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Feb 2011 08:31:01 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 3 Feb 2011 08:31:01 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: The Proposed PWG Raster Thread-Index: AcvDv15pUYeRLXi1Q32DBKDFMGTlXA== From: "Petrie, Glen" To: , , X-OriginalArrivalTime: 03 Feb 2011 16:31:01.0957 (UTC) FILETIME=[BEED1750:01CBC3BF] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] The Proposed PWG Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0241597407==" 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: 0990479556.AB71D X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0241597407== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC3BF.BED0E1BD" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC3BF.BED0E1BD Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hello All, =20 I have been thinking more on the details of the proposed raster format. =20 1. I would propose the name: PWG HCD Raster (PHR) =20 ------------------------------------------------------------------------ ------------------------------=20 Assumptions: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. A PHR is a separate entity from the Job Ticket; that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket =3D> A PHR must have sufficient header data to describe "What is this?" But does not contain HCD Job Ticket attributes. =20 2. A PHR is usable-by or generated-by one or more HCD Services (Print, Scan, Fax, Copy). =3D> A PHR must have sufficient header data to describe "What is this?" =20 3. A PHR is usable-by or generated-by one or more external Services (Print-Preview, Post-Processing, Transforms). =3D> A PHR must have sufficient header data to describe "What is this?" =20 4. A PHR may contain 1-to-many rasters. =3D> For more than one raster, the individual raster may be on one or separate page. Example: Scan multiple regions of the same page. (Smart form processing) Example: N-up the next four raster. =3D> The bounding region of the raster must be recorded. =20 5. A PHR is usable-in or generated-in a mobile, cloud, soho, business or production environment. =3D> There may be limitation or requirement based on system resources. =20 ------------------------------------------------------------------------ ------------------------------=20 Discussion Items =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. Full page raster =3D> Each raster is the same size as the media size. a. To support assumption 5 for the mobile environment; this need is impractical. Device in the mobile environment typical have insufficient system resources to generate a full page raster at a print dpi. One could argue that the mobile device/application could "stream-out" the full page raster. This is often referred to as banded output of the raster content. However, I still contend that encoding useless top/bottom/left/right white space is wasteful.=20 =20 =3D> A requirement to make PHR input/output streamable. =20 b. To support assumption 2, this need is not required. Example of scanning a region. The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put these in a PHR of 8.5 in x 11.0 has not value and consume resources. =20 =3D> The bounding region should be recorded and raster should be the size of the bounding region. =20 Practical examples: Print: I would like to place the next 10 raster in the PHR on a single page. Yes, the client could have done this but would be required to. Scan: I would like scan 3 areas of the 8.5 in x 11.0 in document and record in a PHR. By recording the bounding region of each raster; then each raster could be associated with a field on the original scanned document such as date, name, amount, etc. This would be extremely usefully to external Services. =20 2. Term "HW Resolution" a. The reference to 'HW' within the PHR is not important to HCD services. The reference to "resolution" is not technically correct. What is important to HCD/External services is the Raster DPI. In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply different DPI's in each direction. Any scaling (integer or otherwise) between the "preferred (actual) DPI" of the raster and the Job Ticket DPI is determinable by the HCD service. =20 =3D> The PHRHDR should record the raster horizontal and vertical DPI's.=20 =20 ------------------------------------------------------------------------ ------------------------------=20 Requirements =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. All internal PHR rasters shall have the same set of header content =3D> There is no separate pre-header within a PHR =20 PHRHDR =3D=3D=3D PWG HCD Raster Header =20 2. A PHR shall be identifiable. =3D> There is an explicit identifier in the PHRHDR =3D> A PHRHDR contains the PHR format version =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the largest DPI and shall be scaled by the HCD. =20 4. A PHRHDR shall record the width (horizontal) and height (vertical) number of pixels of the raster. =20 5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line. =20 6. A PHRHDR shall record the top and left position, relative to the media's top-left physical corner, of the raster. =20 7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster. =20 8. A PHRHDR shall record the raster number for this raster and total number raster in the PHR =20 9. A PHR shall be input and output streamable. =20 10. A PHRHDR shall record a new page indicator. =20 11. Byte order of PHR shall follow network convention of "big endian". =20 12. A PHRHDR shall record the duplex parameter for the raster. This does mean that the duplex parameters are to be performed by the HCD; it means what duplex parameter were applied by the creator of the raster in the PHR. =20 13. A PHRHDR shall record the type of compression used for the raster data. =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Terms and Definitions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 Later....=20 =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Structure and Format of PHRHDR =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 =20 (I was not picky on order) =20 Bytes Value Description=20 --------- ------------------ ------------------------------ [01] --- [10] PHR xxxxxx PHR identifier/Version [11] --- [11] RasterNumber Number, of total, for this raster [12] --- [12] TotalRaster Total number of raster in PHR [13] --- [16] RasterWidth Raster width in pixels [17] --- [20] RasterHeight Raster height in pixels [21] --- [24] RasterBPL Raster bytes-per-line [25] --- [28] HorizDPI Raster DPI in horizontal direction [29] --- [32] VertDPI Raster DPI in vertical direction [33] --- [36] TopOffset Raster Top offset at raster vertical DPI [37] --- [40] LeftOffset Raster left offset at raster horizontal DPI [41] --- [41] NewPage Raster is on a new page flag [42] --- [42] ColorSpaceID Identification number for color space [43] --- [43] BitsPerPixel Number of bits per pixel [44] --- [44] BitsPerColor Number of bits per color=20 [45] --- [45] ColorOrderID Identification number for color ordering in a pixel [46] --- [46] DuplexID Id number for duplex operation performed [47] --- [47] CompressionID Id number for raster compression method [48] --- [64] 0XFF Reserve byte for future by PWG [65] --- [95] 0xEE Reserve byte for Vendor/Service/App =20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 [100] ----- > compressed raster data. =20 See CUPS Raster for possible values of ID variables. =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC3BF.BED0E1BD Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hello All,

 

I have been thinking more on the details of the proposed raster format.

 

1. I would propose the name: PWG HCD Raster  (PHR)<= o:p>

 

--------------------------------------------------------= ---------------------------------------------- 

Assumptions:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /p>

1. A PHR is a separate entity from the Job Ticket; = that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket

=3D> A PHR must have sufficient header data to describe "What is this?"  But does= not contain HCD Job Ticket attributes.

 

2. A PHR is usable-by or generated-by one or more H= CD Services (Print, Scan, Fax, Copy).

=3D> A PHR must have sufficient header data to describe "What is this?"

 

3. A PHR is usable-by or generated-by one or more e= xternal Services (Print-Preview, Post-Processing, Transforms).

=3D> A PHR must have sufficient header data to describe "What is this?"

 

4. A PHR may contain 1-to-many rasters.<= /span>

=3D> For more than one rast= er, the individual raster may be on one or separate page.<= /p>

Example: Scan multiple regions= of the same page. (Smart form processing)

Example: N-up the next four ra= ster.

=3D> The bounding region of= the raster must be recorded.

 

5. A PHR is usable-in or generated-in a mobile, cloud, s= oho, business or production environment.

=3D> There may be limitatio= n or requirement based on system resources.

 

--------------------------------------------------------= ---------------------------------------------- 

Discussion Items

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

  1. Full page raster =3D> = Each raster is the same size as the media size.
    1. To support assumption 5 = for the mobile environment; this need is impractical.  Device in the mobile environment typical have insufficient system resources to gene= rate a full page raster at a print dpi.   One could argue that t= he mobile device/application could “stream-out” the full page raster.  This is often referred to as banded output of the raster content.  However, I still contend that encoding useless top/bottom/left/right white space is wasteful.

 

=3D> A requirement to make = PHR input/output streamable.

 

    1. To support assumption 2,= this need is not required.  Example of scanning a region.  The r= egion may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put these in a PHR of 8.5 in x 11.0 has not value and consume resources.<= /span>

 

=3D> The bounding region sh= ould be recorded and raster should be the size of the bounding region.

 

Practical examples:=

Print: I would like to place t= he next 10 raster in the PHR on a single page.  Yes, the client could have done this but would be required to.

Scan: I would like scan 3 area= s of the 8.5 in x 11.0 in document and record in a PHR.   By recording= the bounding region of each raster; then each raster could be associated with a field on the original scanned document such as date, name, amount, etc.&nbs= p; This would be extremely usefully to external Services.

 

  1. Term “HW Resolution= ”
    1. The reference to ‘= HW’ within the PHR is not important to HCD services.  The reference = to “resolution” is not technically correct.  What is important to HCD/External s= ervices is the Raster DPI.  In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply differen= t DPI’s in each direction.  Any scaling (integer or otherwise) between t= he “preferred (actual) DPI” of the raster and the Job Ticket DPI is determina= ble by the HCD service.

 

=3D> The PHRHDR should reco= rd the raster horizontal and vertical DPI’s.

 

--------------------------------------------------------= ---------------------------------------------- 

Requirements

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1. All internal PHR rasters shall have the same set of header content

=3D> There is no separate p= re-header within a PHR

 

PHRHDR =3D=3D=3D PWG HCD Raster Header=

 

2. A PHR shall be identifiable.=

=3D> There is an explicit i= dentifier in the PHRHDR

=3D> A PHRHDR contains the = PHR format version

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the largest DPI and shall be scaled by the HCD.

 

4. A PHRHDR shall record the width (horizontal) and heig= ht (vertical) number of pixels of the raster.

 

5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line.

 

6. A PHRHDR shall record the top and left position, rela= tive to the media’s top-left physical corner, of the raster.

 

7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster.<= /p>

 

8. A PHRHDR shall record the raster number for this rast= er and total number raster in the PHR

 

9. A PHR shall be input and output streamable.

 

10. A PHRHDR shall record a new page indicator.

 

11. Byte order of PHR shall follow network convention of= “big endian”.

 

12. A PHRHDR shall record the duplex parameter for the raster.  This does mean that the duplex parameters are to be performed= by the HCD; it means what duplex parameter were applied by the creator of the = raster in the PHR.

 

13. A PHRHDR shall record the type of compression used f= or the raster data.

 

 

--------------------------------------------------------= ---------------------------------------------- 

Terms and Definitions

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

 

Later….

 

 

--------------------------------------------------------= ---------------------------------------------- 

Structure and Format of PHRHDR<= /p>

=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

 

(I was not picky on order)

 

Bytes        &nb= sp;             = ;      Value      &n= bsp;            = ;         Description

---------        = ;            &n= bsp;      ------------------         &nb= sp;        ------------------------------

[01] --- [10]        =             PHR xxxxxx            &n= bsp;     PHR identifier/Version

[11] --- [11]       &= nbsp;            Ras= terNumber           =     Number, of total, for this raster

[12] --- [12]       &= nbsp;            Tot= alRaster           &= nbsp;        Total number of raster in PHR

[13] --- [16]       &= nbsp;            Ras= terWidth           &= nbsp;      Raster width in pixels

[17] --- [20]       &= nbsp;            Ras= terHeight            = ;     Raster height in pixels

[21] --- [24]        =             RasterBP= L            &n= bsp;       Raster bytes-per-line

[25] --- [28]       &= nbsp;            Hor= izDPI           &nbs= p;           Raster DPI in horizontal direction

[29] --- [32]       &= nbsp;            Ver= tDPI            = ;             R= aster DPI in vertical direction

[33] --- [36]       &= nbsp;            Top= Offset           &nb= sp;          Raster Top offset at raster vertical DPI

[37] --- [40]       &= nbsp;            Lef= tOffset           &n= bsp;          Raster left offset at raster horizontal DPI

[41] --- [41]       &= nbsp;            New= Page            = ;          Raster is on a new page flag

[42] --- [42]       &= nbsp;            Col= orSpaceID           =      Identification number for color space

[43] --- [43]        =             BitsPerP= ixel            = ;      Number of bits per pixel

[44] --- [44]       &= nbsp;            Bit= sPerColor           =        Number of bits per color

[45] --- [45]       &= nbsp;            Col= orOrderID            = ;      Identification number for color ordering in a pixel

[46] --- [46]       &= nbsp;            Dup= lexID           &nbs= p;           Id number for duplex operation performed

[47] --- [47]       &= nbsp;            Com= pressionID           = ;   Id number for raster compression method

[48] --- [64]       &= nbsp;            0XF= F            &n= bsp;            = ;    Reserve byte for future by PWG

[65] --- [95]       &= nbsp;            0xE= E            &n= bsp;            = ;   Reserve byte for Vendor/Service/App

 

[96] --- [99]        =             CmpRaste= rLen            = ;   Length in bytes of compressed raster to follow

 

[100] ----- >       &nb= sp;            compr= essed raster data.

 

See CUPS Raster for possible values of ID variables.

 

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC3BF.BED0E1BD-- --===============0241597407== 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 --===============0241597407==-- From ipp-bounces@pwg.org Thu Feb 3 13:37:55 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51A543A69F7 for ; Thu, 3 Feb 2011 13:37:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.848 X-Spam-Level: X-Spam-Status: No, score=-102.848 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hC84+QBrSWwL for ; Thu, 3 Feb 2011 13:37:53 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 15DB63A69EE for ; Thu, 3 Feb 2011 13:37:53 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 18AAA7955A; Thu, 3 Feb 2011 16:40:46 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 3622A79520; Thu, 3 Feb 2011 16:40:33 -0500 (EST) Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out3.apple.com (Postfix) with ESMTP id 7FEFDCC704F1; Thu, 3 Feb 2011 13:40:33 -0800 (PST) X-AuditID: 11807135-b7cf8ae0000007ed-66-4d4b20ce1206 Received: from [17.153.60.29] (Unknown_Domain [17.153.60.29]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay12.apple.com (Apple SCV relay) with SMTP id AA.5B.02029.FC02B4D4; Thu, 3 Feb 2011 13:40:33 -0800 (PST) Subject: Re: [IPP] The Proposed PWG Raster Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Thu, 3 Feb 2011 11:40:29 -1000 Message-Id: References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1443394271==" 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: 18AAA7955A.AB15B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1443394271== Content-Type: multipart/alternative; boundary=Apple-Mail-11-634450136 --Apple-Mail-11-634450136 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Glen, Let me preface my response with this: I don't want to define an entirely ne= w and complex raster format. I believe the consensus at the F2F was the sam= e. That said, my comments are inline below... On Feb 3, 2011, at 6:31 AM, Petrie, Glen wrote: > Hello All, >=20=20 > I have been thinking more on the details of the proposed raster format. >=20=20 > 1. I would propose the name: PWG HCD Raster (PHR) We only use "HCD" in the IDS group, and as several people pointed out in th= e F2F we don't want the name or format to be too closely tied to any one as= pect of a HCD/MFD/printer/whatever. =20 > -------------------------------------------------------------------------= -----------------------------=20 > Assumptions: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 1. A PHR is a separate entity from the Job Ticket; that is, the PHR is no= t contained in the Job Ticket but is referenced by the Job Ticket > =3D> A PHR must have sufficient header data to describe "What is this?" = But does not contain HCD Job Ticket attributes. I don't believe that the job ticket referenced the document; rather, the jo= b associates the job ticket with the document(s) in the job. >=20=20 > 2. A PHR is usable-by or generated-by one or more HCD Services (Print, Sc= an, Fax, Copy). > =3D> A PHR must have sufficient header data to describe "What is this?" Why? What problem are you trying to solve? =20 > 3. A PHR is usable-by or generated-by one or more external Services (Prin= t-Preview, Post-Processing, Transforms). > =3D> A PHR must have sufficient header data to describe "What is this?" Again, why? What problem are you trying to solve? =20 > 4. A PHR may contain 1-to-many rasters. > =3D> For more than one raster, the individual raster may be on one or sep= arate page. > Example: Scan multiple regions of the same page. (Smart form processing) > Example: N-up the next four raster. > =3D> The bounding region of the raster must be recorded. Let me reiterate a point I made in the F2F - we really don't want to design= yet another raster format. IIRC PDF/is does allow for more than one image = stream per page and is far better suited to this particular use case. PWG R= aster/CUPS Raster is a simple page-based raster format. =20 > 5. A PHR is usable-in or generated-in a mobile, cloud, soho, business or = production environment. > =3D> There may be limitation or requirement based on system resources. This is already discussed in the draft spec and it the motivation behind us= ing PackBits/RLE as the basic compression algorithm over higher-performing = (but higher-resource) algorithms. =20 > -------------------------------------------------------------------------= -----------------------------=20 > Discussion Items > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Full page raster =3D> Each raster is the same size as the media size. > To support assumption 5 for the mobile environment; this need is impracti= cal. Device in the mobile environment typical have insufficient system res= ources to generate a full page raster at a print dpi. One could argue tha= t the mobile device/application could =93stream-out=94 the full page raster= . This is often referred to as banded output of the raster content. Howev= er, I still contend that encoding useless top/bottom/left/right white space= is wasteful. >=20=20 > =3D> A requirement to make PHR input/output streamable. Yes, and if you'll notice this is in the current draft already and a specif= ic feature of CUPS Raster. (and sending whitespace for the margins is trivial, very space efficient, a= nd generally simpler for the client) > To support assumption 2, this need is not required. Example of scanning = a region. The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but = to put these in a PHR of 8.5 in x 11.0 has not value and consume resources. >=20=20 > =3D> The bounding region should be recorded and raster should be the size= of the bounding region. >=20=20 > Practical examples: > Print: I would like to place the next 10 raster in the PHR on a single pa= ge. Yes, the client could have done this but would be required to. > Scan: I would like scan 3 areas of the 8.5 in x 11.0 in document and reco= rd in a PHR. By recording the bounding region of each raster; then each r= aster could be associated with a field on the original scanned document suc= h as date, name, amount, etc. This would be extremely usefully to external= Services. PDF/is can address the multi-image per page case. For the simple 1-image case the PWG Raster can just provide the area scanne= d (and not be a full page - again this isn't a print-only format), and coul= d even provide multiple "pages", one per area scanned. =20 > Term =93HW Resolution=94 > The reference to =91HW=92 within the PHR is not important to HCD services= . The reference to =93resolution=94 is not technically correct. What is i= mportant to HCD/External services is the Raster DPI. In addition, there is= concept of fast-scan / slow-scan and fast-print / slow-print directions wh= ich imply different DPI=92s in each direction. Any scaling (integer or oth= erwise) between the =93preferred (actual) DPI=94 of the raster and the Job = Ticket DPI is determinable by the HCD service. >=20=20 > =3D> The PHRHDR should record the raster horizontal and vertical DPI=92s. Actually we want Pixels Per Inch (PPI). WRT the format, PPI =3D=3D DPI =3D= =3D HWResolution, the difference is in the name and not the actual semantic= s. > ... > Structure and Format of PHRHDR > =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 > ...=20 > [96] --- [99] CmpRasterLen Length in byt= es of compressed raster to follow This kills streaming... ________________________________________________________________________ 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. --Apple-Mail-11-634450136 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Hello All,
 
I have been thinking more on the details of the propo= sed raster format.
=  
1. I would propose the name: PWG HCD Raster  (PHR= )

We only= use "HCD" in the IDS group, and as several people pointed out in the F2F w= e don't want the name or format to be too closely tied to any one aspect of= a HCD/MFD/printer/whatever.
 
---------------------------------------= --------------------------------------------------------------- <= /o:p>
Assumptions:
1.&nb= sp;A PHR is a separate entity from the Job Ticket; that is, the PHR is not = contained in the Job Ticket but is referenced by the Job Ticket<= /span>
=3D> A PHR must have sufficient header da= ta to describe "What is this?"  But does not contain HCD Job Ticket at= tributes.

I don't believe that the job ticket referenced the document; rather, the j= ob associates the job ticket with the document(s) in the job.
 
2. A PHR is usable-by or generated-by one or more HCD Services (= Print, Scan, Fax, Copy).
=3D> = A PHR must have sufficient header data to describe "What is this?"

Why? What problem= are you trying to solve?
 
3. A PHR is usable-by or generated-b= y one or more external Services (Print-Preview, Post-Processing, Transforms= ).
=3D> A PHR must have suffic= ient header data to describe "What is this?"

Again, why? What problem are you trying= to solve?
 
4. A PHR may contain 1-to-many rasters.
=3D> For more than one raster, the individual r= aster may be on one or separate page.
Ex= ample: Scan multiple regions of the same page. (Smart form processing)=
Example: N-up the next four raster.
=3D> The bounding region of the raster must b= e recorded.

Let me reiterate a point I made in the F2F - we really don't want to des= ign yet another raster format. IIRC PDF/is does allow for more than one ima= ge stream per page and is far better suited to this particular use case. PW= G Raster/CUPS Raster is a simple page-based raster format.
=  
5. A = PHR is usable-in or generated-in a mobile, cloud, soho, business or product= ion environment.
= =3D> There may be = limitation or requirement based on system resources.

This is already discussed in th= e draft spec and it the motivation behind using PackBits/RLE as the basic c= ompression algorithm over higher-performing (but higher-resource) algorithm= s.
 
<= font size=3D"2" face=3D"Arial">-----------------------------------------------------------------= ------------------------------------- 
<= div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; m= argin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; ">Discussion Items
=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
  1. Full page raster =3D> Each raster is the same size as the media size.
    1. To support assumption 5= for the mobile environment; this need is impractical.  Device in the = mobile environment typical have insufficient system resources to generate a= full page raster at a print dpi.   One could argue that the mobi= le device/application could =93stream-out=94 the full page raster.  Th= is is often referred to as banded output of the raster content.  Howev= er, I still contend that encoding useless top/bottom/left/right white space= is wasteful.
 
=3D> A requirement to make PHR input/output= streamable.

Yes, and if you'll notice this is in the current draft already and= a specific feature of CUPS Raster.

(and sending w= hitespace for the margins is trivial, very space efficient, and generally s= impler for the client)

=
    1. To suppo= rt assumption 2, this need is not required.  Example of scanning a reg= ion.  The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but = to put these in a PHR of 8.5 in x 11.0 has not value and consume resources.=
 
=3D> The bounding region should be recorded and raster sho= uld be the size of the bounding region.
 
Practical examples:=
Print: I would like to place the next 10 raster = in the PHR on a single page.  Yes, the client could have done this but= would be required to.
Scan: I would l= ike scan 3 areas of the 8.5 in x 11.0 in document and record in a PHR. = ;  By recording the bounding region of each raster; then each raster c= ould be associated with a field on the original scanned document such as da= te, name, amount, etc.  This would be extremely usefully to external S= ervices.

= PDF/is can address the multi-image per page case.

= For the simple 1-image case the PWG Raster can just provide the area scanne= d (and not be a full page - again this isn't a print-only format), and coul= d even provide multiple "pages", one per area scanned.
&nbs= p;
  1. Term =93HW Resolution=94
    1. The reference to =91HW=92 within the PHR is not important to HCD s= ervices.  The reference to =93resolution=94 is not technically correct= .  What is important to HCD/External services is the Raster DPI. = In addition, there is concept of fast-scan / slow-scan and fast-print / sl= ow-print directions which imply different DPI=92s in each direction.  = Any scaling (integer or otherwise) between the =93preferred (actual) DPI=94= of the raster and the Job Ticket DPI is determinable by the HCD service.
 
=3D> The PHRHDR should record the raster horizontal and ve= rtical DPI=92s.
Actually we want Pixels Per Inch (PPI). WRT the format, PPI =3D=3D D= PI =3D=3D HWResolution, the difference is in the name and not the actual se= mantics.

<= /font>
...
Structure = and Format of PHRHDR
=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
..= . 
[96] --- [99]      &= nbsp;             Cm= pRasterLen           = ;    Length in bytes of compressed raster to follow

This kills stream= ing...

_______________________________________________= _________________________
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. --Apple-Mail-11-634450136-- --===============1443394271== 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 --===============1443394271==-- From ipp-bounces@pwg.org Thu Feb 3 14:42:44 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD6E03A6B30 for ; Thu, 3 Feb 2011 14:42:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.348 X-Spam-Level: X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NH7HJsgm764k for ; Thu, 3 Feb 2011 14:42:43 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 8B7C83A6B22 for ; Thu, 3 Feb 2011 14:42:43 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6372879566; Thu, 3 Feb 2011 17:45:49 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 5DCA87953C; Thu, 3 Feb 2011 17:45:36 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Feb 2011 14:45:35 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] The Proposed PWG Raster Date: Thu, 3 Feb 2011 14:45:34 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] The Proposed PWG Raster Thread-Index: AcvD6wCiKVZQTCb9S6umnMeKgKsyfwACH5JA References: From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 03 Feb 2011 22:45:35.0713 (UTC) FILETIME=[12541D10:01CBC3F4] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2125231031==" 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: 6372879566.A9753 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============2125231031== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC3F4.11760046" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC3F4.11760046 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable ... Structure and Format of PHRHDR =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 ...=20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 This kills streaming... =20 [gwp] Oops, this should do after the raster content to entire the entire raster was received. --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC3F4.11760046 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

...<= /o:p>

Structure and Format of PHRHDR=

=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

... =

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

This kills streaming...

 

[gwp] Oops, this should do after the r= aster content to entire the entire raster was received.<= /p>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC3F4.11760046-- --===============2125231031== 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 --===============2125231031==-- From ipp-bounces@pwg.org Thu Feb 3 17:08:44 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 192763A6947 for ; Thu, 3 Feb 2011 17:08:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.82 X-Spam-Level: X-Spam-Status: No, score=-102.82 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+eGjfXymrZS for ; Thu, 3 Feb 2011 17:08:43 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id DDB8F3A68F3 for ; Thu, 3 Feb 2011 17:08:42 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B6D7B79561; Thu, 3 Feb 2011 20:11:48 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id D57687955F; Thu, 3 Feb 2011 20:11:36 -0500 (EST) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id C6C6FCFF99A7; Thu, 3 Feb 2011 17:11:35 -0800 (PST) X-AuditID: 11807137-b7baaae000007a67-e7-4d4b52461a3a Received: from [17.153.18.189] (Unknown_Domain [17.153.18.189]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 3C.A3.31335.7425B4D4; Thu, 3 Feb 2011 17:11:35 -0800 (PST) Subject: Re: [IPP] The Proposed PWG Raster Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Thu, 3 Feb 2011 15:11:34 -1000 Message-Id: <7937710D-B694-4D44-9001-DC52E4EEDEA6@apple.com> References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0529862765==" 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: B6D7B79561.A9D89 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0529862765== Content-Type: multipart/alternative; boundary=Apple-Mail-3-647114332 --Apple-Mail-3-647114332 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Feb 3, 2011, at 12:45 PM, Petrie, Glen wrote: > ... >> Structure and Format of PHRHDR >> =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 >> ...=20 >> [96] --- [99] CmpRasterLen Length in by= tes of compressed raster to follow >=20=20 > This kills streaming... >=20=20 > [gwp] Oops, this should do after the raster content to entire the entire = raster was received. How would that help? And what about raster data larger than 4GiB? ________________________________________________________________________ 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. --Apple-Mail-3-647114332 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
...
Structure and Format of PHRHDR
=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
... 
[96] --- [= 99]             = ;       CmpRasterLen    &= nbsp;          Length in bytes= of compressed raster to follow
<= /blockquote>
 
This kills streaming...
[g= wp] Oops, this should do after the raster content to entire the entire rast= er was received.

How would that help? And what about raster data larger t= han 4GiB?

_______________________________________________= _________________________
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. --Apple-Mail-3-647114332-- --===============0529862765== 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 --===============0529862765==-- From ipp-bounces@pwg.org Thu Feb 3 17:11:53 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA2A03A6947 for ; Thu, 3 Feb 2011 17:11:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.198 X-Spam-Level: X-Spam-Status: No, score=-3.198 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5AGa+061Y5n for ; Thu, 3 Feb 2011 17:11:49 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 9D70D3A68E7 for ; Thu, 3 Feb 2011 17:11:49 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 072FC7956D; Thu, 3 Feb 2011 20:14:44 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 62C047955F; Thu, 3 Feb 2011 20:14:28 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 3 Feb 2011 17:14:27 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] The Proposed PWG Raster Date: Thu, 3 Feb 2011 17:14:26 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] The Proposed PWG Raster Thread-Index: AcvECHpP94r6M3vjRGWOWaZw6dWG1AAAFKSw References: <7937710D-B694-4D44-9001-DC52E4EEDEA6@apple.com> From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 04 Feb 2011 01:14:27.0182 (UTC) FILETIME=[DDE620E0:01CBC408] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0225801674==" 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: 072FC7956D.AA9E4 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0225801674== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC408.DD39FC8E" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC408.DD39FC8E Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable It was proposed only as a check value - it could be dropped (or use something like a check sum) =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Thursday, February 03, 2011 5:12 PM To: Petrie, Glen Cc: ipp@pwg.org; cloud@pwg.org; mfd@pwg.org Subject: Re: [IPP] The Proposed PWG Raster =20 On Feb 3, 2011, at 12:45 PM, Petrie, Glen wrote: =09 ... Structure and Format of PHRHDR =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 ...=20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =09=20 This kills streaming... =09=20 [gwp] Oops, this should do after the raster content to entire the entire raster was received. =20 How would that help? And what about raster data larger than 4GiB? =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_01CBC408.DD39FC8E Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

It was proposed only as a check value = – it could be dropped  (or use something like a check sum)

 


From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Thursday, February 03,= 2011 5:12 PM
To: Petrie, Glen
Cc: ipp@pwg.org; cloud@pwg.o= rg; mfd@pwg.org
Subject: Re: [IPP] The Propo= sed PWG Raster

 

On Feb 3, 2011, at 12:45 PM, Petrie, Gl= en wrote:

...<= /o:p>

Structure and Format of PHRHDR=

=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

... =

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

This kills streaming...

 

[gwp] Oops, this should do after the raster content to entire the entire raster was received.

 

How would that help? And what about raster data larger than 4GiB?

 

______________= __________________________________________________________
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_01CBC408.DD39FC8E-- --===============0225801674== 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 --===============0225801674==-- From ipp-bounces@pwg.org Fri Feb 4 05:54:47 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 573103A6BB6 for ; Fri, 4 Feb 2011 05:54:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.097 X-Spam-Level: X-Spam-Status: No, score=-3.097 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjdiNP2+flUf for ; Fri, 4 Feb 2011 05:54:37 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 861103A6B73 for ; Fri, 4 Feb 2011 05:54:37 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 938877957B; Fri, 4 Feb 2011 08:57:05 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id CB3CF7956A; Fri, 4 Feb 2011 08:56:48 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 4 Feb 2011 05:56:47 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 4 Feb 2011 05:56:46 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MFD] The Proposed PWG Raster Thread-Index: AcvDv15pUYeRLXi1Q32DBKDFMGTlXAAstqrg References: From: "Petrie, Glen" To: , , X-OriginalArrivalTime: 04 Feb 2011 13:56:47.0154 (UTC) FILETIME=[5D0BF920:01CBC473] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] RE: [MFD] The Proposed PWG Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1769013797==" 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: 938877957B.AB3B3 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1769013797== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC473.5C887075" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC473.5C887075 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable After more consideration, I was not happy with requirement 3 and propose the following change=20 =20 Was =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the largest DPI and shall be scaled by the HCD. =20 =20 To =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the DPI of the first raster for the page in PHR and shall scale all other raster for the same page to the DPI of the first raster. =20 Based on emails with Mike, I modified my proposal of the byte data at the end to=20 =20 Was =20 [65] --- [95] 0xEE Reserve byte for Vendor/Service/App =20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 [100] ----- > compressed raster data. =20 To =20 [65] --- [99] 0xEE Reserve byte for Vendor/Service/App =20 [100] ----- > compressed raster data. =20 =20 ________________________________ From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Thursday, February 03, 2011 8:31 AM To: ipp@pwg.org; cloud@pwg.org; mfd@pwg.org Subject: [MFD] The Proposed PWG Raster =20 Hello All, =20 I have been thinking more on the details of the proposed raster format. =20 1. I would propose the name: PWG HCD Raster (PHR) =20 ------------------------------------------------------------------------ ------------------------------=20 Assumptions: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. A PHR is a separate entity from the Job Ticket; that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket =3D> A PHR must have sufficient header data to describe "What is this?" But does not contain HCD Job Ticket attributes. =20 2. A PHR is usable-by or generated-by one or more HCD Services (Print, Scan, Fax, Copy). =3D> A PHR must have sufficient header data to describe "What is this?" =20 3. A PHR is usable-by or generated-by one or more external Services (Print-Preview, Post-Processing, Transforms). =3D> A PHR must have sufficient header data to describe "What is this?" =20 4. A PHR may contain 1-to-many rasters. =3D> For more than one raster, the individual raster may be on one or separate page. Example: Scan multiple regions of the same page. (Smart form processing) Example: N-up the next four raster. =3D> The bounding region of the raster must be recorded. =20 5. A PHR is usable-in or generated-in a mobile, cloud, soho, business or production environment. =3D> There may be limitation or requirement based on system resources. =20 ------------------------------------------------------------------------ ------------------------------=20 Discussion Items =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. Full page raster =3D> Each raster is the same size as the media size. a. To support assumption 5 for the mobile environment; this need is impractical. Device in the mobile environment typical have insufficient system resources to generate a full page raster at a print dpi. One could argue that the mobile device/application could "stream-out" the full page raster. This is often referred to as banded output of the raster content. However, I still contend that encoding useless top/bottom/left/right white space is wasteful.=20 =20 =3D> A requirement to make PHR input/output streamable. =20 b. To support assumption 2, this need is not required. Example of scanning a region. The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put these in a PHR of 8.5 in x 11.0 has not value and consume resources. =20 =3D> The bounding region should be recorded and raster should be the size of the bounding region. =20 Practical examples: Print: I would like to place the next 10 raster in the PHR on a single page. Yes, the client could have done this but would be required to. Scan: I would like scan 3 areas of the 8.5 in x 11.0 in document and record in a PHR. By recording the bounding region of each raster; then each raster could be associated with a field on the original scanned document such as date, name, amount, etc. This would be extremely usefully to external Services. =20 2. Term "HW Resolution" a. The reference to 'HW' within the PHR is not important to HCD services. The reference to "resolution" is not technically correct. What is important to HCD/External services is the Raster DPI. In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply different DPI's in each direction. Any scaling (integer or otherwise) between the "preferred (actual) DPI" of the raster and the Job Ticket DPI is determinable by the HCD service. =20 =3D> The PHRHDR should record the raster horizontal and vertical DPI's.=20 =20 ------------------------------------------------------------------------ ------------------------------=20 Requirements =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. All internal PHR rasters shall have the same set of header content =3D> There is no separate pre-header within a PHR =20 PHRHDR =3D=3D=3D PWG HCD Raster Header =20 2. A PHR shall be identifiable. =3D> There is an explicit identifier in the PHRHDR =3D> A PHRHDR contains the PHR format version =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the largest DPI and shall be scaled by the HCD. =20 4. A PHRHDR shall record the width (horizontal) and height (vertical) number of pixels of the raster. =20 5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line. =20 6. A PHRHDR shall record the top and left position, relative to the media's top-left physical corner, of the raster. =20 7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster. =20 8. A PHRHDR shall record the raster number for this raster and total number raster in the PHR =20 9. A PHR shall be input and output streamable. =20 10. A PHRHDR shall record a new page indicator. =20 11. Byte order of PHR shall follow network convention of "big endian". =20 12. A PHRHDR shall record the duplex parameter for the raster. This does mean that the duplex parameters are to be performed by the HCD; it means what duplex parameter were applied by the creator of the raster in the PHR. =20 13. A PHRHDR shall record the type of compression used for the raster data. =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Terms and Definitions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 Later....=20 =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Structure and Format of PHRHDR =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 =20 (I was not picky on order) =20 Bytes Value Description=20 --------- ------------------ ------------------------------ [01] --- [10] PHR xxxxxx PHR identifier/Version [11] --- [11] RasterNumber Number, of total, for this raster [12] --- [12] TotalRaster Total number of raster in PHR [13] --- [16] RasterWidth Raster width in pixels [17] --- [20] RasterHeight Raster height in pixels [21] --- [24] RasterBPL Raster bytes-per-line [25] --- [28] HorizDPI Raster DPI in horizontal direction [29] --- [32] VertDPI Raster DPI in vertical direction [33] --- [36] TopOffset Raster Top offset at raster vertical DPI [37] --- [40] LeftOffset Raster left offset at raster horizontal DPI [41] --- [41] NewPage Raster is on a new page flag [42] --- [42] ColorSpaceID Identification number for color space [43] --- [43] BitsPerPixel Number of bits per pixel [44] --- [44] BitsPerColor Number of bits per color=20 [45] --- [45] ColorOrderID Identification number for color ordering in a pixel [46] --- [46] DuplexID Id number for duplex operation performed [47] --- [47] CompressionID Id number for raster compression method [48] --- [64] 0XFF Reserve byte for future by PWG [65] --- [95] 0xEE Reserve byte for Vendor/Service/App =20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 [100] ----- > compressed raster data. =20 See CUPS Raster for possible values of ID variables. =20 =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_01CBC473.5C887075 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

After more consideration, I was not ha= ppy with requirement 3  and propose the following change

 

Was

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the largest DPI and shall be scaled by the HCD.

 

 

To

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the DPI of the first raster for the page in PHR and shall scale all other raster for the same page to the DPI of the first raster.<= /font>

 

Based on emails with Mike, I modified = my proposal of the byte data at the end to

 

Was

 

[65] --- [95]            = ;        0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

[100] ----- >             &nb= sp;      compressed raster data.

 

To

 

[65] --- [99]       &= nbsp;            0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

 [100] ----- >             &nb= sp;      compressed raster data.

 

 


From: mfd-boun= ces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf = Of Petrie, Glen
Sent: Thursday, February 03,= 2011 8:31 AM
To: ipp@pwg.org; cloud@pwg.o= rg; mfd@pwg.org
Subject: [MFD] The Proposed = PWG Raster

 

Hello All,

 

I have been thinking more on the details of the proposed raster format.

 

1. I would propose the name: PWG HCD Raster  (PHR)<= o:p>

 

--------------------------------------------------------= ---------------------------------------------- 

Assumptions:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /p>

1. A PHR is a separate entity from the Job Ticket; = that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket

=3D> A PHR must have sufficient header data to describe "What is this?"  But does= not contain HCD Job Ticket attributes.

 

2. A PHR is usable-by or generated-by one or more H= CD Services (Print, Scan, Fax, Copy).

=3D> A PHR must have sufficient header data to describe "What is this?"

 

3. A PHR is usable-by or generated-by one or more external Services (Print-Preview, Post-Processing, Transforms).<= /span>

=3D> A PHR must have sufficient header data to describe "What is this?"

 

4. A PHR may contain 1-to-many rasters.<= /span>

=3D> For more than one rast= er, the individual raster may be on one or separate page.<= /p>

Example: Scan multiple regions= of the same page. (Smart form processing)

Example: N-up the next four ra= ster.

=3D> The bounding region of= the raster must be recorded.

 

5. A PHR is usable-in or generated-in a mobile, cloud, s= oho, business or production environment.

=3D> There may be limitatio= n or requirement based on system resources.

 

--------------------------------------------------------= ---------------------------------------------- 

Discussion Items

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

  1. Full page raster =3D> = Each raster is the same size as the media size.
    1. To support assumption 5 = for the mobile environment; this need is impractical.  Device in the mobile environment typical have insufficient system resources to gene= rate a full page raster at a print dpi.   One could argue that t= he mobile device/application could “stream-out” the full page raster.  This is often referred to as banded output of the raster content.  However, I still contend that encoding useless top/bot= tom/left/right white space is wasteful.

 

=3D> A requirement to make = PHR input/output streamable.

 

    1. To support assumption 2,= this need is not required.  Example of scanning a region.  The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put th= ese in a PHR of 8.5 in x 11.0 has not value and consume resources.

 

=3D> The bounding region sh= ould be recorded and raster should be the size of the bounding region.

 

Practical examples:=

Print: I would like to place t= he next 10 raster in the PHR on a single page.  Yes, the client could have done this but would be required to.

Scan: I would like scan 3 area= s of the 8.5 in x 11.0 in document and record in a PHR.   By recording= the bounding region of each raster; then each raster could be associated with a= field on the original scanned document such as date, name, amount, etc.  This would be extremely usefully to external Services.<= /p>

 

  1. Term “HW Resolution”
    1. The reference to ‘HW’ within the PHR is not important to HCD services.&nbs= p; The reference to “resolution” is not technically correct.  What is important to HCD/External services is the Rast= er DPI.  In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply different DPI’s = in each direction.  Any scaling (integer or otherwise) between the “preferred (actual) DPI” of the raster and the Job Ticket= DPI is determinable by the HCD service.

 

=3D> The PHRHDR should reco= rd the raster horizontal and vertical DPI’s.

 

--------------------------------------------------------= ---------------------------------------------- 

Requirements

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1. All internal PHR rasters shall have the same set of header content

=3D> There is no separate pre-header within a PHR

 

PHRHDR =3D=3D=3D PWG HCD Raster Header=

 

2. A PHR shall be identifiable.=

=3D> There is an explicit identifier in the PHRHDR

=3D> A PHRHDR contains the = PHR format version

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the largest DPI and shall be scaled by the HCD.

 

4. A PHRHDR shall record the width (horizontal) and heig= ht (vertical) number of pixels of the raster.

 

5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line.

 

6. A PHRHDR shall record the top and left position, rela= tive to the media’s top-left physical corner, of the raster.

 

7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster.<= /p>

 

8. A PHRHDR shall record the raster number for this rast= er and total number raster in the PHR

 

9. A PHR shall be input and output streamable.

 

10. A PHRHDR shall record a new page indicator.

 

11. Byte order of PHR shall follow network convention of “big endian”.

 

12. A PHRHDR shall record the duplex parameter for the raster.  This does mean that the duplex parameters are to be performed= by the HCD; it means what duplex parameter were applied by the creator of the raster in the PHR.

 

13. A PHRHDR shall record the type of compression used f= or the raster data.

 

 

--------------------------------------------------------= ---------------------------------------------- 

Terms and Definitions

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

 

Later….

 

 

--------------------------------------------------------= ---------------------------------------------- 

Structure and Format of PHRHDR<= /p>

=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

 

(I was not picky on order)

 

Bytes        &nb= sp;                   Value           &nbs= p;            &= nbsp;   Description

---------        = ;            &n= bsp;      ------------------         &nb= sp;        ------------------------------

[01] --- [10]             &nb= sp;      PHR xxxxxx                  PHR identifier/Version

[11] --- [11]            = ;        RasterNumber          &nb= sp;    Number, of total, for this raster

[12] --- [12]       &= nbsp;            TotalRaster          &nbs= p;         Total number of raster in PHR

[13] --- [16]            = ;        RasterWidth          &nbs= p;       Raster width in pixels

[17] --- [20]            = ;        RasterHeight                 Raster height in pixels

[21] --- [24]             &nb= sp;      RasterBPL           =          Raster bytes-per-line

[25] --- [28]            = ;        HorizDPI           &= nbsp;           Raster DPI in horizontal direction

[29] --- [32]            = ;        VertDPI           &n= bsp;             Raster DPI in vertical direction

[33] --- [36]            = ;        TopOffset           =            Raster Top offset at raster vertical DPI

[37] --- [40]            = ;        LeftOffset           = ;           Raster left offset at raster horizontal DPI

[41] --- [41]            = ;        NewPage           &n= bsp;          Raster is on a new page flag

[42] --- [42]            = ;        ColorSpaceID          &nb= sp;     Identification number for color space

[43] --- [43]             &nb= sp;      BitsPerPixel          &nb= sp;       Number of bits per pixel

[44] --- [44]            = ;        BitsPerColor          &nb= sp;       Number of bits per color

[45] --- [45]            = ;        ColorOrderID                  Identification number for color ordering in a pixel

[46] --- [46]            = ;        DuplexID           &= nbsp;           Id number for duplex operation performed

[47] --- [47]            = ;        CompressionID          &n= bsp;   Id number for raster compression method

[48] --- [64]            = ;        0XFF            = ;            &n= bsp;    Reserve byte for future by PWG

[65] --- [95]            = ;        0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

[100] ----- >             &nb= sp;      compressed raster data.

 

See CUPS Raster for possible values of ID variables.

 

 


--
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_01CBC473.5C887075-- --===============1769013797== 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 --===============1769013797==-- From ipp-bounces@pwg.org Fri Feb 4 16:01:32 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9104D3A69F4 for ; Fri, 4 Feb 2011 16:01:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.026 X-Spam-Level: X-Spam-Status: No, score=-3.026 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMq3qzGcUqk7 for ; Fri, 4 Feb 2011 16:01:19 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 643A53A69DC for ; Fri, 4 Feb 2011 16:01:19 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 82EF779585; Fri, 4 Feb 2011 19:03:31 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 21E6F7957C; Fri, 4 Feb 2011 19:03:11 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 4 Feb 2011 16:03:08 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 4 Feb 2011 16:03:06 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MFD] The Proposed PWG Raster Thread-Index: AcvDv15pUYeRLXi1Q32DBKDFMGTlXAAstqrgABU0CKA= References: From: "Petrie, Glen" To: "Petrie, Glen" , , , X-OriginalArrivalTime: 05 Feb 2011 00:03:08.0886 (UTC) FILETIME=[123FB760:01CBC4C8] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] RE: [MFD] The Proposed PWG Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0133778251==" 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: 82EF779585.AAB89 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0133778251== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC4C8.11159D44" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC4C8.11159D44 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Played with writing some sample code and changed the length of a few of the values =20 [01][04] PHR identifier=20 [05][10] PHR Version=20 [11][14] Number, of total, for this raster=20 [15][18] Total number of raster in PHR=20 [19][22] Raster width in pixels=20 [23][26] Raster height in pixels=20 [27][30] Raster bytes-per-line=20 [31][34] Raster PPI in horizontal direction=20 [35][38] Raster DPI in vertical direction=20 [39][42] Raster Top offset at raster vertical PPI=20 [43][46] Raster left offset at raster horizontal PPI=20 [47][47] Raster is on a new page flag=20 [48][48] Identification number for color space=20 [49][49] Number of bits per pixel=20 [50][50] Number of bits per color=20=20 [51][52] Identification number for color ordering in a pixel=20 [53][53] Id number for duplex operation performed=20 [54][54] Id number for raster compression method=20 [55][69] Reserve byte for future by PWG=20 [70][79] Reserve byte for future by vendor=20 [80][89] Reserve byte for future by services [90][99] Reserve byte for future by apps=20 =20 ________________________________ From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, February 04, 2011 5:57 AM To: ipp@pwg.org; cloud@pwg.org; mfd@pwg.org Subject: RE: [MFD] The Proposed PWG Raster =20 After more consideration, I was not happy with requirement 3 and propose the following change=20 =20 Was =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the largest DPI and shall be scaled by the HCD. =20 =20 To =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the DPI of the first raster for the page in PHR and shall scale all other raster for the same page to the DPI of the first raster. =20 Based on emails with Mike, I modified my proposal of the byte data at the end to=20 =20 Was =20 [65] --- [95] 0xEE Reserve byte for Vendor/Service/App =20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 [100] ----- > compressed raster data. =20 To =20 [65] --- [99] 0xEE Reserve byte for Vendor/Service/App =20 [100] ----- > compressed raster data. =20 =20 ________________________________ From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Thursday, February 03, 2011 8:31 AM To: ipp@pwg.org; cloud@pwg.org; mfd@pwg.org Subject: [MFD] The Proposed PWG Raster =20 Hello All, =20 I have been thinking more on the details of the proposed raster format. =20 1. I would propose the name: PWG HCD Raster (PHR) =20 ------------------------------------------------------------------------ ------------------------------=20 Assumptions: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. A PHR is a separate entity from the Job Ticket; that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket =3D> A PHR must have sufficient header data to describe "What is this?" But does not contain HCD Job Ticket attributes. =20 2. A PHR is usable-by or generated-by one or more HCD Services (Print, Scan, Fax, Copy). =3D> A PHR must have sufficient header data to describe "What is this?" =20 3. A PHR is usable-by or generated-by one or more external Services (Print-Preview, Post-Processing, Transforms). =3D> A PHR must have sufficient header data to describe "What is this?" =20 4. A PHR may contain 1-to-many rasters. =3D> For more than one raster, the individual raster may be on one or separate page. Example: Scan multiple regions of the same page. (Smart form processing) Example: N-up the next four raster. =3D> The bounding region of the raster must be recorded. =20 5. A PHR is usable-in or generated-in a mobile, cloud, soho, business or production environment. =3D> There may be limitation or requirement based on system resources. =20 ------------------------------------------------------------------------ ------------------------------=20 Discussion Items =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. Full page raster =3D> Each raster is the same size as the media size. a. To support assumption 5 for the mobile environment; this need is impractical. Device in the mobile environment typical have insufficient system resources to generate a full page raster at a print dpi. One could argue that the mobile device/application could "stream-out" the full page raster. This is often referred to as banded output of the raster content. However, I still contend that encoding useless top/bottom/left/right white space is wasteful.=20 =20 =3D> A requirement to make PHR input/output streamable. =20 b. To support assumption 2, this need is not required. Example of scanning a region. The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put these in a PHR of 8.5 in x 11.0 has not value and consume resources. =20 =3D> The bounding region should be recorded and raster should be the size of the bounding region. =20 Practical examples: Print: I would like to place the next 10 raster in the PHR on a single page. Yes, the client could have done this but would be required to. Scan: I would like scan 3 areas of the 8.5 in x 11.0 in document and record in a PHR. By recording the bounding region of each raster; then each raster could be associated with a field on the original scanned document such as date, name, amount, etc. This would be extremely usefully to external Services. =20 2. Term "HW Resolution" a. The reference to 'HW' within the PHR is not important to HCD services. The reference to "resolution" is not technically correct. What is important to HCD/External services is the Raster DPI. In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply different DPI's in each direction. Any scaling (integer or otherwise) between the "preferred (actual) DPI" of the raster and the Job Ticket DPI is determinable by the HCD service. =20 =3D> The PHRHDR should record the raster horizontal and vertical DPI's.=20 =20 ------------------------------------------------------------------------ ------------------------------=20 Requirements =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. All internal PHR rasters shall have the same set of header content =3D> There is no separate pre-header within a PHR =20 PHRHDR =3D=3D=3D PWG HCD Raster Header =20 2. A PHR shall be identifiable. =3D> There is an explicit identifier in the PHRHDR =3D> A PHRHDR contains the PHR format version =20 3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster. a. If a PHR contains raster for the same page of different DPI, all raster will be rendered by the HCD service at the largest DPI and shall be scaled by the HCD. =20 4. A PHRHDR shall record the width (horizontal) and height (vertical) number of pixels of the raster. =20 5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line. =20 6. A PHRHDR shall record the top and left position, relative to the media's top-left physical corner, of the raster. =20 7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster. =20 8. A PHRHDR shall record the raster number for this raster and total number raster in the PHR =20 9. A PHR shall be input and output streamable. =20 10. A PHRHDR shall record a new page indicator. =20 11. Byte order of PHR shall follow network convention of "big endian". =20 12. A PHRHDR shall record the duplex parameter for the raster. This does mean that the duplex parameters are to be performed by the HCD; it means what duplex parameter were applied by the creator of the raster in the PHR. =20 13. A PHRHDR shall record the type of compression used for the raster data. =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Terms and Definitions =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 Later....=20 =20 =20 ------------------------------------------------------------------------ ------------------------------=20 Structure and Format of PHRHDR =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 =20 (I was not picky on order) =20 Bytes Value Description=20 --------- ------------------ ------------------------------ [01] --- [10] PHR xxxxxx PHR identifier/Version [11] --- [11] RasterNumber Number, of total, for this raster [12] --- [12] TotalRaster Total number of raster in PHR [13] --- [16] RasterWidth Raster width in pixels [17] --- [20] RasterHeight Raster height in pixels [21] --- [24] RasterBPL Raster bytes-per-line [25] --- [28] HorizDPI Raster DPI in horizontal direction [29] --- [32] VertDPI Raster DPI in vertical direction [33] --- [36] TopOffset Raster Top offset at raster vertical DPI [37] --- [40] LeftOffset Raster left offset at raster horizontal DPI [41] --- [41] NewPage Raster is on a new page flag [42] --- [42] ColorSpaceID Identification number for color space [43] --- [43] BitsPerPixel Number of bits per pixel [44] --- [44] BitsPerColor Number of bits per color=20 [45] --- [45] ColorOrderID Identification number for color ordering in a pixel [46] --- [46] DuplexID Id number for duplex operation performed [47] --- [47] CompressionID Id number for raster compression method [48] --- [64] 0XFF Reserve byte for future by PWG [65] --- [95] 0xEE Reserve byte for Vendor/Service/App =20 [96] --- [99] CmpRasterLen Length in bytes of compressed raster to follow =20 [100] ----- > compressed raster data. =20 See CUPS Raster for possible values of ID variables. =20 =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC4C8.11159D44 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Played with writing some sample code a= nd changed the length of a few of the values

 

[01][04]  PHR identifier

[05][10]  PHR Version =

[11][14]  Number, of total, for t= his raster

[15][18]  Total number of raster = in PHR

[19][22]  Raster width in pixels =

[23][26]  Raster height in pixels=

[27][30]  Raster bytes-per-line <= o:p>

[31][34]  Raster PPI in horizontal direction

[35][38]  Raster DPI in vertical = direction

[39][42]  Raster Top offset at ra= ster vertical PPI

[43][46]  Raster left offset at r= aster horizontal PPI

[47][47]  Raster is on a new page= flag

[48][48]  Identification number f= or color space

[49][49]  Number of bits per pixe= l

[50][50]  Number of bits per colo= r 

[51][52]  Identification number f= or color ordering in a pixel

[53][53]  Id number for duplex op= eration performed

[54][54]  Id number for raster co= mpression method

[55][69]  Reserve byte for future= by PWG

[70][79]  Reserve byte for future= by vendor

[80][89]  Reserve byte for future= by services

[90][99]  Reserve byte for future= by apps

 


From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Friday, February 04, 2= 011 5:57 AM
To: ipp@pwg.org; cloud@pwg.o= rg; mfd@pwg.org
Subject: RE: [MFD] The Propo= sed PWG Raster

 

After more consideration, I was not ha= ppy with requirement 3  and propose the following change

 

Was

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the largest DPI and shall be scaled by the HCD.

 

 

To

 

3. A PHRHDR shall record the horizontal (witdth) and vertical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service at the DPI of the first raster for the page in PHR and shall scale all other raster for the same page to the DPI of the first raster.<= /p>

 

Based on emails with Mike, I modified = my proposal of the byte data at the end to

 

Was

 

[65] --- [95]            = ;        0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

[100] ----- >             &nb= sp;      compressed raster data.

 

To

 

[65] --- [99]            = ;        0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

 [100] ----- >             &nb= sp;      compressed raster data.

 

 


From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Thursday, February 03,= 2011 8:31 AM
To: ipp@pwg.org; cloud@pwg.o= rg; mfd@pwg.org
Subject: [MFD] The Proposed = PWG Raster

 

Hello All,

 

I have been thinking more on the details of the proposed raster format.

 

1. I would propose the name: PWG HCD Raster  (PHR)<= o:p>

 

--------------------------------------------------------= ---------------------------------------------- 

Assumptions:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /p>

1. A PHR is a separate entity from the Job Ticket; = that is, the PHR is not contained in the Job Ticket but is referenced by the Job Ticket

=3D> A PHR must have sufficient header data to describe "What is this?"  But does= not contain HCD Job Ticket attributes.

 

2. A PHR is usable-by or generated-by one or more H= CD Services (Print, Scan, Fax, Copy).

=3D> A PHR must have sufficient header data to describe "What is this?"

 

3. A PHR is usable-by or generated-by one or more external Services (Print-Preview, Post-Processing, Transforms).<= /span>

=3D> A PHR must have sufficient header data to describe "What is this?"

 

4. A PHR may contain 1-to-many rasters.<= /span>

=3D> For more than one rast= er, the individual raster may be on one or separate page.<= /p>

Example: Scan multiple regions= of the same page. (Smart form processing)

Example: N-up the next four ra= ster.

=3D> The bounding region of= the raster must be recorded.

 

5. A PHR is usable-in or generated-in a mobile, cloud, s= oho, business or production environment.

=3D> There may be limitatio= n or requirement based on system resources.

 

--------------------------------------------------------= ---------------------------------------------- 

Discussion Items

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

  1. Full page raster =3D> = Each raster is the same size as the media size.
    1. To support assumption 5 = for the mobile environment; this need is impractical.  Device in the mobile environment typical have insufficient system resources to gene= rate a full page raster at a print dpi.   One could argue that t= he mobile device/application could “stream-out” the full page raster.  This is often referred to as banded output of the raster content.  However, I still contend that encoding useless top/bottom/left/right white space is wasteful.

 

=3D> A requirement to make = PHR input/output streamable.

 

    1. To support assumption 2,= this need is not required.  Example of scanning a region.  The region may be 1in x 1in or 3in x 10in or 8.5in x 11.0in but to put th= ese in a PHR of 8.5 in x 11.0 has not value and consume resources.

 

=3D> The bounding region sh= ould be recorded and raster should be the size of the bounding region.

 

Practical examples:=

Print: I would like to place t= he next 10 raster in the PHR on a single page.  Yes, the client could have done this but would be required to.

Scan: I would like scan 3 area= s of the 8.5 in x 11.0 in document and record in a PHR.   By recording= the bounding region of each raster; then each raster could be associated with a field on the original scanned document such as date, name, amount, etc.&nbs= p; This would be extremely usefully to external Services.

 

  1. Term “HW Resolution”
    1. The reference to ‘HW’ within the PHR is not important to HCD services.&nbs= p; The reference to “resolution” is not technically correct.  What is important to HCD/External services is the Rast= er DPI.  In addition, there is concept of fast-scan / slow-scan and fast-print / slow-print directions which imply different DPI’s = in each direction.  Any scaling (integer or otherwise) between the “preferred (actual) DPI” of the raster and the Job Ticket= DPI is determinable by the HCD service.

 

=3D> The PHRHDR should reco= rd the raster horizontal and vertical DPI’s.

 

--------------------------------------------------------= ---------------------------------------------- 

Requirements

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1. All internal PHR rasters shall have the same set of header content

=3D> There is no separate pre-header within a PHR

 

PHRHDR =3D=3D=3D PWG HCD Raster Header=

 

2. A PHR shall be identifiable.=

=3D> There is an explicit identifier in the PHRHDR

=3D> A PHRHDR contains the = PHR format version

 

3. A PHRHDR shall record the horizontal (witdth) and ver= tical (height) DPI of the raster.

a. If a PHR contains raster fo= r the same page of different DPI, all raster will be rendered by the HCD service = at the largest DPI and shall be scaled by the HCD.

 

4. A PHRHDR shall record the width (horizontal) and heig= ht (vertical) number of pixels of the raster.

 

5. A PHRHDR shall record the number of (8-bit) bytes in single horizontal raster line.

 

6. A PHRHDR shall record the top and left position, rela= tive to the media’s top-left physical corner, of the raster.

 

7. A PHRDR shall record the Color Space, Color Order, Bits-per-pixel and Bits-per-color for the raster.<= /p>

 

8. A PHRHDR shall record the raster number for this rast= er and total number raster in the PHR

 

9. A PHR shall be input and output streamable.

 

10. A PHRHDR shall record a new page indicator.

 

11. Byte order of PHR shall follow network convention of “big endian”.

 

12. A PHRHDR shall record the duplex parameter for the raster.  This does mean that the duplex parameters are to be performed= by the HCD; it means what duplex parameter were applied by the creator of the raster in the PHR.

 

13. A PHRHDR shall record the type of compression used f= or the raster data.

 

 

--------------------------------------------------------= ---------------------------------------------- 

Terms and Definitions

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

 

Later….

 

 

--------------------------------------------------------= ---------------------------------------------- 

Structure and Format of PHRHDR<= /p>

=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

 

(I was not picky on order)

 

Bytes        &nb= sp;                   Value           &nbs= p;            &= nbsp;   Description

---------        = ;            &n= bsp;      ------------------         &nb= sp;        ------------------------------

[01] --- [10]             &nb= sp;      PHR xxxxxx                  PHR identifier/Version

[11] --- [11]            = ;        RasterNumber          &nb= sp;    Number, of total, for this raster

[12] --- [12]            = ;        TotalRaster          &nbs= p;         Total number of raster in PHR

[13] --- [16]            = ;        RasterWidth          &nbs= p;       Raster width in pixels

[17] --- [20]            = ;        RasterHeight                 Raster height in pixels

[21] --- [24]             &nb= sp;      RasterBPL           =          Raster bytes-per-line

[25] --- [28]            = ;        HorizDPI           &= nbsp;           Raster DPI in horizontal direction

[29] --- [32]            = ;        VertDPI           &n= bsp;             Raster DPI in vertical direction

[33] --- [36]            = ;        TopOffset           =            Raster Top offset at raster vertical DPI

[37] --- [40]            = ;        LeftOffset           = ;           Raster left offset at raster horizontal DPI

[41] --- [41]            = ;        NewPage           &n= bsp;          Raster is on a new page flag

[42] --- [42]            = ;        ColorSpaceID          &nb= sp;     Identification number for color space

[43] --- [43]             &nb= sp;      BitsPerPixel          &nb= sp;       Number of bits per pixel

[44] --- [44]            = ;        BitsPerColor          &nb= sp;       Number of bits per color

[45] --- [45]            = ;        ColorOrderID                  Identification number for color ordering in a pixel

[46] --- [46]            = ;        DuplexID           &= nbsp;           Id number for duplex operation performed

[47] --- [47]            = ;        CompressionID          &n= bsp;   Id number for raster compression method

[48] --- [64]            = ;        0XFF            = ;            &n= bsp;    Reserve byte for future by PWG

[65] --- [95]            = ;        0xEE            = ;            &n= bsp;   Reserve byte for Vendor/Service/App

 

[96] --- [99]                    CmpRasterLen          &nb= sp;    Length in bytes of compressed raster to follow

 

[100] ----- >             &nb= sp;      compressed raster data.

 

See CUPS Raster for possible values of ID variables.

 

 


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


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC4C8.11159D44-- --===============0133778251== 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 --===============0133778251==-- From ipp-bounces@pwg.org Mon Feb 7 06:59:22 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FB823A6D7D for ; Mon, 7 Feb 2011 06:59:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZv4OlbgPqGF for ; Mon, 7 Feb 2011 06:59:21 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 807923A6D6C for ; Mon, 7 Feb 2011 06:59:21 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 10F0779554; Mon, 7 Feb 2011 09:59:02 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id D4E5B79195; Mon, 7 Feb 2011 09:58:49 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Feb 2011 06:58:47 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 7 Feb 2011 06:58:45 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Test - Do Not Respond Thread-Index: AcvDv15pUYeRLXi1Q32DBKDFMGTlXAAstqrgAJkykdA= References: From: "Petrie, Glen" To: , , X-OriginalArrivalTime: 07 Feb 2011 14:58:47.0632 (UTC) FILETIME=[85DD1D00:01CBC6D7] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Test - Do Not Respond 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="===============0812242161==" 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: 10F0779554.A9727 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0812242161== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC6D7.84D8EAAF" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC6D7.84D8EAAF Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC6D7.84D8EAAF 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. ------_=_NextPart_001_01CBC6D7.84D8EAAF-- --===============0812242161== 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 --===============0812242161==-- From ipp-bounces@pwg.org Mon Feb 7 11:47:53 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A20A43A6E80 for ; Mon, 7 Feb 2011 11:47:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.298 X-Spam-Level: X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v92qL9Qr3SKS for ; Mon, 7 Feb 2011 11:47:52 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 877423A6BDE for ; Mon, 7 Feb 2011 11:47:52 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 246247955E; Mon, 7 Feb 2011 14:47:36 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id A3B1E7953D; Mon, 7 Feb 2011 14:47:22 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Feb 2011 11:47:20 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 7 Feb 2011 11:47:19 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MFD] The Proposed PWG Raster Thread-Index: AcvDv15pUYeRLXi1Q32DBKDFMGTlXAAstqrgAKMyUdA= References: From: "Petrie, Glen" To: , , X-OriginalArrivalTime: 07 Feb 2011 19:47:20.0650 (UTC) FILETIME=[D53A02A0:01CBC6FF] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] RE: [MFD] The Proposed PWG Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2123299036==" 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: 246247955E.A93C8 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============2123299036== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC6FF.D43FA41F" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC6FF.D43FA41F Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable After discussion with my Japanese colleague, I had decided to withdraw my proposal/suggestion for the PWG raster format. =20 Glen =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC6FF.D43FA41F Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

After discussion with my Japanese coll= eague, I had decided to withdraw my proposal/suggestion for the PWG raster format.=

 

Glen

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC6FF.D43FA41F-- --===============2123299036== 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 --===============2123299036==-- From g-osmun@sbcglobal.net Mon Feb 7 11:58:36 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D4D13A6EA2 for ; Mon, 7 Feb 2011 11:58:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Td46zWFyuDfH for ; Mon, 7 Feb 2011 11:58:35 -0800 (PST) Received: from nm2.bullet.mail.sp2.yahoo.com (nm2.bullet.mail.sp2.yahoo.com [98.139.91.72]) by core3.amsl.com (Postfix) with SMTP id 3F3973A6E98 for ; Mon, 7 Feb 2011 11:58:34 -0800 (PST) Received: from [98.139.91.69] by nm2.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:58:37 -0000 Received: from [98.139.91.51] by tm9.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:58:37 -0000 Received: from [127.0.0.1] by omp1051.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:58:37 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 56736.89923.bm@omp1051.mail.sp2.yahoo.com Received: (qmail 73227 invoked by uid 60001); 7 Feb 2011 19:58:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1297108716; bh=FZ9z2iNzgtC4CewdjINLlVpqwsMBfKLtd5cpFIc39As=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=Lr4j1MORmP4VeU0W3ldAtRsxlFoiM4NZ0TG814dpdzpUQMzhLwvNgu+DNN3O8DZOr6HQdlOSYpGp+9ba/b+c+mqm2BUxZBA89RnP15ZRSy2hZkt5qivqdkbYAJToAZaBAtLQweeingYbj61omgT5MPY0lH9Um6JWy1M+rdrtomI= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=X9KgHax1ilmEE126QQKtvAdBVZXvkTzf03SvGXXPRlKKRObstA5H9ph2vRtDAqxnZ+3e4zRZsqGBX6sfH4L87V+U58s+BPmWUyA8eteTPDJYvHh/JE1enZd4HN56C1jDRsh07/5qIfow7zn0ntC4RJXgaeoBSmxmA/VxuavzSVQ=; Message-ID: <559766.70622.qm@web180012.mail.gq1.yahoo.com> X-YMail-OSG: eH3V1dEVM1lYbBqTnpn3U3uuL4XtEPq9oWOcc8NyQ5hR_G4 HwUuHoPifNPHt5A7V7N1eXRTVLq4BNsnp12X7lNEbl_z1ahst0UIvUd5Pw6b AANAH1DCmm.RFc6L1wvC1NLs137tIclcHQWdzuc.Qp3.NS2w5mMeAoe8EUuo m_7VJw2O0.wHrXzaEltAQg63nxTBjIATUDS.K8SDUkFzsetpCqu5OEcir_oa G0bV5HteN8sQpRudbH7eff7X1vePLlZSz.ktWO1zjM31NWIJzTAVKewEMg6a fqHifsnSQzOQTDXil7XByhoJ4WYFnjq3kTADnHJjjautqmMRGlD5.uiTYTbr 3xGs4mO7hkKdS5e4JmJUtq0H2IM1OJ6VwIPxe3bPLXNrL1GmcRT4MzVLb3s5 1wTabihYCrGUkiyZai4pOX5kIbajidXyyHOczWfPpaZFy343PSpRYHqizeTm xX4wwk0l40SJK09r9TQlNNP1ZVOGXo10iO_vX_z4A76NgfxO_lM2nDfnmR6. bLRZIArp8yYG3shwvrCtdF.JKBzSRFEvHSJezCUeZHwo9VKqDOPbJx4BsRYR Mz8sTqsHxI5DAJ6nWBHeiwd8rD.gzRnl0VP6IDBJduGkpY0v5GIB9LDohGzS dmevc6XwucyHsTAkuuRyXFghwt1CoySNeF87K6PSOV03ljdw2Vo8dO7NdLfk gLy62yD0SiYVHyy9BxnMCs.HcUKfTI86wFRwIJhZw9NfQr7HZujryhGM._SA TtCLmJNbexG1B4tmiNocwnWIaBDEnae_CWz8Ko0u1uLCh8UjfWIZP2K04Mgd z9kRRwfbiJVhj.4llzO7HJMX4ZLdll2.CO3zgnUK5yRKzHhmWI2HYHHgZ3dO lOqGPgD9dRni.c9lksnTCcelv00k2VUOOh07qSi_Y1IQSiu1K0foIR_4Gf6L jYJmp88k_Gk7TU8E2HIJAuLKXcMT7oY_Opm0ejRxvdOiTMBh9TuzezKnB4lh BLwxKHHhJWIVSZoIdxW7F3jOHMmtTScRdNvWjqmeO8x2D Received: from [65.120.57.66] by web180012.mail.gq1.yahoo.com via HTTP; Mon, 07 Feb 2011 11:58:36 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.108.291010 Date: Mon, 7 Feb 2011 11:58:36 -0800 (PST) From: Webmail Technical Support Team Subject: Dear Subscriber To: undisclosed recipients: ; MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-234980894-1297108716=:70622" --0-234980894-1297108716=:70622 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Dear Subscriber. =0A =0AWe are contacting you to remind you that our Account Review Team is curr= ently updating all Webmail Account. As a result, access to your account has= been limited in accordance with the Webmail Online User Agreement. To re-v= alidate your mailbox please click this link and fill the form to update you= r account: =0A =0Awww.WebmailTechnicalSupportTeam.Web.officelive.com =0A =0AThanks =0A =0AWebmail Technical Support Team =0A=A9 2011 All Right Reserved. --0-234980894-1297108716=:70622 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable


Dear Subscriber.
=0A
=0AWe are = contacting you to remind you that our Account Review Team is currently upda= ting all Webmail Account. As a result, access to your account has been limi= ted in accordance with the Webmail Online User Agreement. To re-validate yo= ur mailbox please click this link and fill the form to update your account:=
=0A
=0Awww.WebmailTechnicalSupportTeam.Web.officelive.com
=0A
= =0AThanks
=0A
=0AWebmail Technical Support Team
=0A=A9 2011 All Ri= ght Reserved.
--0-234980894-1297108716=:70622-- From g-osmun@sbcglobal.net Mon Feb 7 11:59:20 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 512933A6EA2 for ; Mon, 7 Feb 2011 11:59:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UK2I1K0G8Jja for ; Mon, 7 Feb 2011 11:59:19 -0800 (PST) Received: from nm24-vm0.bullet.mail.sp2.yahoo.com (nm24-vm0.bullet.mail.sp2.yahoo.com [98.139.91.226]) by core3.amsl.com (Postfix) with SMTP id 96C233A6BDE for ; Mon, 7 Feb 2011 11:59:19 -0800 (PST) Received: from [98.139.91.64] by nm24.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:59:19 -0000 Received: from [98.139.91.8] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:59:19 -0000 Received: from [127.0.0.1] by omp1008.mail.sp2.yahoo.com with NNFMP; 07 Feb 2011 19:59:19 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 464526.8247.bm@omp1008.mail.sp2.yahoo.com Received: (qmail 21167 invoked by uid 60001); 7 Feb 2011 19:59:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1297108758; bh=UUt3CCm7DnuaO1TOXKSmIzBcPNiWeJm0omgNoGvBa0I=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=3XGuGaRbQvVQzNo85jspqtiD9hfPdptuqMkB8eCj+ESWSWjdJsTG73xLSWkbQN6nwVGFoXGriUI8ehJMCO3PKzKTJFfgdVfnai1UFE0xXsmqXEHv2GyuQoXHN76tyDzeqS5zOjYlIWcZ3k3VmccRXkTWeeMGY29AWlzQ4S/cPU0= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=KlXRP5Rld3F+ImNehuyypyDT8Q7mj/fYG/waR2rtSvTxvxrlpy9xUeLNSaaxIRi2+he7pQ0PXoyvDzGhxNVcI24EE+cB6qd89Yml8QR1VVIv5y+k6O3VD5RQuhsCiO6mx2d7DHLSm7+uiXz8uJZHFCSmexC6oSSPSO0e/VatlZU=; Message-ID: <989667.8404.qm@web180011.mail.gq1.yahoo.com> X-YMail-OSG: 4b6LMWQVM1kiHv.PLIY_DnaMpQeIYVYZP4egDpCcbHSfq64 3Fj7bhZcfTCtPDmLmd_7jZDgYjzMfUxaYUSwSIkzltspF5HrKXltMEvlCcWP zwyI_2GKHmrCyjqAXpKsSq_joqbMhDBR13jQbnp5RNp3NB_Ld6L_t8G73Rvp R4_YiwUOfhlPDETO1LeKdREIKJ7Ggjyi3UG1uWyJaJjFZDyaCGcsY1LKfWGd Mi7_7GoeGc4Q280FtygL7iVFWurTh.5b5y1WVrg0dukQsFEYPXOIk3Ou73tZ UzTHqm5MjUEAsV2h1BE4nnF6RO0.yV_m9_lk8hWLUND0q2raUNChGh0Yn6tH z.eREPcUFVe0K2pns5KSH_8M_UBOzfvbfGRzFAV0c724YFGg5zTS4myTAsXF JdzQfMHDrQnAlJ0ZtXc4VSV0j32IP6feJMLod.PxOZl6MSvtOoRikY1EJnBN olGzziJZe607FhDfa3oiuibcOU47xR8nJu_HpdpAh1F7T5e4TnXUghMxUXty dc8.EAJykUfpBDsJalDY4XcwDEDtMixhV2Fy.M2AncOxylHMs6QxPLxi9.eO Mejjnfjyc6zpBBnHNf7krHA8cIySMFEdfJ1o7ldO13FhSuT3TDgZDH3rOCjR 7_uQ18mXoC304FdebWtrw1IvSYJbChHajhYn2qE_Spxj1YGTKh9rRIu9PkWl AePDwpFt6HnbctAWEaMBNi7rU5nOQrmfHKjT7KgFZ1fTV8K9dpCuiEYhxX8n aq5MDP4zZTjSm_U0GvqBvR9nroK9qsFF1NxA.0lPLsXTz8n_PeHYMNBfzwxp jTYt7CorLmT7lERhMbbkKb7Y9sAQkmdp6YP8ioZesJYC_9iCMJJ2WR3L7CsK jZTi55OVr9aYkcRAKbpboaWNJJn2imdnPbM.SxMNNYvIEjhSU4Ib7cNyUNJ. Ol_uIdB2LgksldrWFMXA__0Ey7u.xI8u5Sc4P41VKkMUjWPGVyPq.9.DFJGA NtZFGSoE4VkFGPO9I.SOibPLE9JtzU6GPGAFo75ZgoYXmcZQoHns42ZqA.eI ivGm65ZHj1C1h9oSbHaTXmHuHdpdPbw_ikfxPegCGiFg2A35f0saSsJg- Received: from [65.120.57.66] by web180011.mail.gq1.yahoo.com via HTTP; Mon, 07 Feb 2011 11:59:18 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.108.291010 Date: Mon, 7 Feb 2011 11:59:18 -0800 (PST) From: Webmail Technical Support Team Subject: Dear Subscriber To: undisclosed recipients: ; MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1559397812-1297108758=:8404" --0-1559397812-1297108758=:8404 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Dear Subscriber. =0A =0AWe are contacting you to remind you that our Account Review Team is curr= ently updating all Webmail Account. As a result, access to your account has= been limited in accordance with the Webmail Online User Agreement. To re-v= alidate your mailbox please click this link and fill the form to update you= r account: =0A =0Awww.WebmailTechnicalSupportTeam.Web.officelive.com =0A =0AThanks =0A =0AWebmail Technical Support Team =0A=A9 2011 All Right Reserved. --0-1559397812-1297108758=:8404 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable


Dear Subscriber.
=0A
=0AWe are = contacting you to remind you that our Account Review Team is currently upda= ting all Webmail Account. As a result, access to your account has been limi= ted in accordance with the Webmail Online User Agreement. To re-validate yo= ur mailbox please click this link and fill the form to update your account:=
=0A
=0Awww.WebmailTechnicalSupportTeam.Web.officelive.com
=0A
= =0AThanks
=0A
=0AWebmail Technical Support Team
=0A=A9 2011 All Ri= ght Reserved.
--0-1559397812-1297108758=:8404-- From g-osmun@sbcglobal.net Mon Feb 7 12:00:57 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FF9E3A6EC2 for ; Mon, 7 Feb 2011 12:00:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8GMUx0+CEqx for ; Mon, 7 Feb 2011 12:00:56 -0800 (PST) Received: from nm12-vm0.bullet.mail.ne1.yahoo.com (nm12-vm0.bullet.mail.ne1.yahoo.com [98.138.91.51]) by core3.amsl.com (Postfix) with SMTP id 967FA3A6EC5 for ; Mon, 7 Feb 2011 12:00:45 -0800 (PST) Received: from [98.138.90.54] by nm12.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2011 20:00:44 -0000 Received: from [98.138.88.235] by tm7.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2011 20:00:44 -0000 Received: from [127.0.0.1] by omp1035.mail.ne1.yahoo.com with NNFMP; 07 Feb 2011 20:00:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 452600.92839.bm@omp1035.mail.ne1.yahoo.com Received: (qmail 65507 invoked by uid 60001); 7 Feb 2011 20:00:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1297108843; bh=HIV8UW0ydl0gg9bSh+kZPG9X1sFQPwctyCuAGNn0ziU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=zy2gbrfogBPyKNakB/ufzY3BbaZ+uA6D50KvHGuaObzYSxDgu5/MilOHmuwvXn6CKrhno8UTQyVzws1GbzAblfaKlc8h6y/FJi50fSwG3JnRvJa/cUIzTF0U0VWJuUIv5+K1zfZKXKl2lX6vQxriLVkbsZmjZ5iXoDi4vNrH5OA= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=FjYJWAfxfgv/dIhHLzvqet9BZ+LWghaf7bxfUyqbi4+IoauzcRin3273kBdxtAWm31TLQdXg5Celx019Oe8xfQx//XSOFtvPj/4fnFIgB/GyX1EHAbzb3bp5aIOO55kvWwmyHeaonkptHw3guaZQV6AMDmkaTo7qTMCZc0NYAO0=; Message-ID: <613442.62907.qm@web180005.mail.gq1.yahoo.com> X-YMail-OSG: Vdqv.zQVM1k4_LxSrirK3eqoy09iu0.f6QrnZX.FQfxeqm5 Rz_stV.hEwV5zragqV5qbnN6BNzJszlmIRTifUIWOpEQbZHDuHc9EXy2T04A gjcMjHMX7q1hpOW70j.jCiIo9PdiHp2xJYcGKE2KYk0be1zAs2WGQGAWD4sm A1OwDt5yI5T5sknrMNhgPjnC_gAJn0raSO9Eq5XYZrjmF5KRBjbxx28hCFPT nbp9ITI_jQAxhLoMx4A6phwwY0MtWbb2_9d0HPKvN3bXjh6VCGz20HQ4ZKq8 PiwALNrL0sDE7FWFuu2pGgKztMDNE9kTRkcsBcGkB2d1f2R6EVbbxEeCpoWW m66vmxkUQosT1QHpDpH0PHP9LGeDQQx5tGtD0Vv9ojThEONu1Z_PgXhCrtaF MeLz3Hy5QKEKHV_XGy0lgf3YiLBHkBa9I0OJJTf68j2ymMPilqJy6d6.gKKv _VmCW8keqMjF9FdGHmdNSIOZTDEDhfbGnDen1KUAgRlwTN89fXLHu8IW2wId vSeCpu07hRebImIy_vBvF7OfdIiNSh1m.c2.Z9cckNV7O3sDZRWKTon53.2c qeuTVn29W4RbSu1puRtawwKrdrARIPk0okfI1QJgOmpY3VZFU3U_Ls64qwjG A9owQb9T3UGcBPlI8hFSrxvWQa8vTq8HXJ2L5qI4_NhirKsuYXLsVON_faRi KE5Xqg4CK5dJOQb8pTcw_yCYZ40IsExfQOOINAR6xdqBe6l9ncFbWwh6V1xx F6vG.4JfgB5CUnyObogRszBKvNpk2kMPnQ2EeJMtyPS6U7s9oBQGMVdlKO0q wyT.yzQ7tNeDkPz.UJ55O8OotN2rKPNP7j6nH3sVeI7P9h3qe9xoT35qHuGq ulGNRRBHk4G50TcFNzvmzJnQ- Received: from [65.120.57.66] by web180005.mail.gq1.yahoo.com via HTTP; Mon, 07 Feb 2011 12:00:43 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.108.291010 Date: Mon, 7 Feb 2011 12:00:43 -0800 (PST) From: Webmail Technical Support Team Subject: Dear Subscriber To: undisclosed recipients: ; MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1983375484-1297108843=:62907" --0-1983375484-1297108843=:62907 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Dear Subscriber. =0A =0AWe are contacting you to remind you that our Account Review Team is curr= ently updating all Webmail Account. As a result, access to your account has= been limited in accordance with the Webmail Online User Agreement. To re-v= alidate your mailbox please click this link and fill the form to update you= r account: =0A =0Awww.WebmailTechnicalSupportTeam.Web.officelive.com =0A =0AThanks =0A =0AWebmail Technical Support Team =0A=A9 2011 All Right Reserved. --0-1983375484-1297108843=:62907 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable


Dear Subscriber.
=0A
=0AWe are = contacting you to remind you that our Account Review Team is currently upda= ting all Webmail Account. As a result, access to your account has been limi= ted in accordance with the Webmail Online User Agreement. To re-validate yo= ur mailbox please click this link and fill the form to update your account:=
=0A
=0Awww.WebmailTechnicalSupportTeam.Web.officelive.com
=0A
= =0AThanks
=0A
=0AWebmail Technical Support Team
=0A=A9 2011 All Ri= ght Reserved.
--0-1983375484-1297108843=:62907-- From ipp-bounces@pwg.org Tue Feb 8 07:24:00 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DE063A67AD for ; Tue, 8 Feb 2011 07:24:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.948 X-Spam-Level: X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ge9JKvD+zwQS for ; Tue, 8 Feb 2011 07:23:56 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id D73843A67A8 for ; Tue, 8 Feb 2011 07:23:48 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 7F68479526; Tue, 8 Feb 2011 10:23:35 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 602FD7945D for ; Tue, 8 Feb 2011 10:23:22 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Feb 2011 07:23:21 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 8 Feb 2011 07:23:15 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Epson Request for PWG/IPP Raster Thread-Index: AcvHo64K5ptxotg3RtCWu5iz+Qi1jg== From: "Petrie, Glen" To: X-OriginalArrivalTime: 08 Feb 2011 15:23:21.0345 (UTC) FILETIME=[1EAD9F10:01CBC7A4] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Epson Request for PWG/IPP Raster X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1461956682==" 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: 7F68479526.A97C2 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1461956682== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC7A4.1B33F9F0" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC7A4.1B33F9F0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Epson would like in endorse the IPP working group's fast tracking of the PWG/IPP raster specification / standard. Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking of the of PWG/IPP Raster specification / standard.=20 =20 Epson supports the currently proposed format of the raster format provided that the format is "streamable" in order to eliminate the need for printers to provide buffering of full pages. =20 If the format has a REQUIRED color space, and Epson is not proposing that there should be a REQUIRED color space; then Epson would like to propose and support 24-bit sRGB=20 =20 Glen =20 =20 =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC7A4.1B33F9F0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Epson would like in endorse the IPP working group’s fast tracking of the PWG/IPP raster specification / standard.  Epson w= ould like to further encourage and endorse the PWG Steering committee in approvi= ng a (very) fast tracking of the of PWG/IPP Raster specification / standard.

 

Epson supports the currently proposed format of the rast= er format provided that the format is “streamable” in order to eliminate the need for printers to provide buffering of full pages.

 

If the format has a REQUIRED color space, and Epson is n= ot proposing that there should be a REQUIRED color space; then Epson would lik= e to propose and support 24-bit sRGB

 

Glen

 

 

 

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBC7A4.1B33F9F0-- --===============1461956682== 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 --===============1461956682==-- From ipp-bounces@pwg.org Tue Feb 8 08:48:58 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F7983A67AD for ; Tue, 8 Feb 2011 08:48:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PeD2oiSz2+MW for ; Tue, 8 Feb 2011 08:48:57 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 418623A67A5 for ; Tue, 8 Feb 2011 08:48:57 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 254B97953E; Tue, 8 Feb 2011 11:48:48 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 3160D79533 for ; Tue, 8 Feb 2011 11:48:35 -0500 (EST) Received: by fxm20 with SMTP id 20so7428347fxm.5 for ; Tue, 08 Feb 2011 08:48:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XyeBlk5U7A9y/x2b+cVsZIAscBZZYiweUPCu+H5hYs4=; b=AuFKXi/R6PARXRj6FpI6KMW5af9FcDjjiP/04HlawIeuh+RgyXHKc9L5F+BujCBDFI 2J00TnCTBI+Vh/myxtvWqO+8L8ePc3aF2pVzMHXYUfYmOR8ZRR6PBeB/vgCQkqxl4q9q /oij/OyphjZJRjI4H52rUd+OWSDSeLT0esWaE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Lzj6M6nCA7SO4ZEGYPiHbbY2353fXgROJ21fQ0+55vI9Zx25eImQ+6UdnBiyma2msX r9QIx7PlCEyWo2BeRTNYRqwcm/gKkJKMorrPGmfysQMfmUnzROi/BRArlPLjktyWFyU2 ce7fz1HPx2ladoHR7BD9WQqXCiZmF+5Xl45xo= MIME-Version: 1.0 Received: by 10.223.83.144 with SMTP id f16mr6455416fal.4.1297183714389; Tue, 08 Feb 2011 08:48:34 -0800 (PST) Received: by 10.223.103.142 with HTTP; Tue, 8 Feb 2011 08:48:34 -0800 (PST) In-Reply-To: References: Date: Tue, 8 Feb 2011 11:48:34 -0500 Message-ID: Subject: Re: [IPP] Epson Request for PWG/IPP Raster 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="===============1493623012==" 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: 254B97953E.AAB7F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1493623012== Content-Type: multipart/alternative; boundary=20cf3054a737813006049bc81e4f --20cf3054a737813006049bc81e4f Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen, With respect to 'fast tracking' of PWG Raster spec, note that the status phases Initial/Interim/Protoype/Stable must occur, per PWG Process/3.0. Except for waiving the PWG Process/3.0 requirement for a PWG Last Call to span a PWG face-to-face, there is little the PWG Steering Committee can do to 'fast track' this spec. And during the Prototype phase an actual prototype of substantial amounts of the base spec must be performed, reported on, and reviewed by the IPP WG. For comparison, PDF/is had *every* required and optional field prototyped. Wire formats need to be very stable before adopting them. I can't speak to Mike Sweet's editing priorities, but the main IPP Everywhere (profiles) and IPP JPS3 specs are high priority for their Cloud Imaging WG and MFD WG impacts. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen w= rote: > Epson would like in endorse the IPP working group=92s fast tracking of t= he > PWG/IPP raster specification / standard. Epson would like to further > encourage and endorse the PWG Steering committee in approving a (very) fa= st > tracking of the of PWG/IPP Raster specification / standard. > > > > Epson supports the currently proposed format of the raster format provided > that the format is =93streamable=94 in order to eliminate the need for pr= inters > to provide buffering of full pages. > > > > If the format has a REQUIRED color space, and Epson is not proposing that > there should be a REQUIRED color space; then Epson would like to propose = and > support 24-bit sRGB > > > > Glen > > > > > > > > > > -- > 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. --20cf3054a737813006049bc81e4f Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen,

With respect to 'fast tracking' of PWG Raster spec,= note
that the status phases Initial/Interim/Protoype/Stable must
o= ccur, per PWG Process/3.0.

Except for waiving the PWG Process/3.0 re= quirement
for a PWG Last Call to span a PWG face-to-face, there
is little the PWG = Steering Committee can do to 'fast
track' this spec.

And = during the Prototype phase an actual prototype of
substantial amounts o= f the base spec must be performed,
reported on, and reviewed by the IPP WG.

For comparison, PDF/is had = *every* required and
optional field prototyped.=A0 Wire formats need to= be
very stable before adopting them.

I can't speak to Mike S= weet's editing priorities, but the
main IPP Everywhere (profiles) and IPP JPS3 specs
are high priority for = their Cloud Imaging WG and MFD
WG impacts.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair -= Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=A0 PO Box 221=A0 Grand Marais, MI= 49839
=A0 906-494-2434



On Tue, Feb 8, 2011 at 10:23 AM, Petrie,= Glen <g= len.petrie@eitc.epson.com> wrote:

Epson would like in endorse the IPP workin= g group=92s fast tracking of the PWG/IPP raster specification / standard.=A0 Epson would like to further encourage and endorse the PWG Steering committee in approvi= ng a (very) fast tracking of the of PWG/IPP Raster specification / standard.

=A0

Epson supports the currently proposed form= at of the raster format provided that the format is =93streamable=94 in order to eliminate the need for printers to provide buffering of full pages.<= /font>

=A0

If the format has a REQUIRED color space, = and Epson is not proposing that there should be a REQUIRED color space; then Epson would lik= e to propose and support 24-bit sRGB

=A0

Glen

=A0

=A0

=A0

=A0


--=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. --20cf3054a737813006049bc81e4f-- --===============1493623012== 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 --===============1493623012==-- From ipp-bounces@pwg.org Tue Feb 8 10:42:44 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3215C3A681E for ; Tue, 8 Feb 2011 10:42:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.164 X-Spam-Level: X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SjW3pDprAtuA for ; Tue, 8 Feb 2011 10:42:37 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 2DE113A6810 for ; Tue, 8 Feb 2011 10:42:37 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 546D079542; Tue, 8 Feb 2011 13:42:22 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 96EB8794D7 for ; Tue, 8 Feb 2011 13:42:08 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Feb 2011 10:42:07 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Epson Request for PWG/IPP Raster Date: Tue, 8 Feb 2011 10:42:07 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Epson Request for PWG/IPP Raster Thread-Index: AcvHsA6Hll9un8MkTOely7soW8Qh7wAAA3Tw References: From: "Petrie, Glen" To: "Ira McDonald" X-OriginalArrivalTime: 08 Feb 2011 18:42:07.0795 (UTC) FILETIME=[E3657830:01CBC7BF] 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="===============1543925405==" 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: 546D079542.AA3EB X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1543925405== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC7BF.E2FEF420" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC7BF.E2FEF420 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable While I understand your comments on fast tracking, is there a "specific" duration to each phase / process? So, I did not mean to change the process but to encourage shortening it. =20 Can you help me understand the "scope of a prototype"? In this case, the scope of the technical content is very small but I still assume that the process steps can not be dropped. =20 Having just a source provider of the PWG raster is not interoperability. I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subset. So is emulation of a printer ok? I also assume for interoperability, there must be two independent developments. =20 Glen =20 =20 =20 =20 ________________________________ From: Ira McDonald [mailto:blueroofmusic@gmail.com]=20 Sent: Tuesday, February 08, 2011 8:49 AM To: Petrie, Glen; Ira McDonald Cc: ipp@pwg.org Subject: Re: [IPP] Epson Request for PWG/IPP Raster =20 Hi Glen, With respect to 'fast tracking' of PWG Raster spec, note=20 that the status phases Initial/Interim/Protoype/Stable must=20 occur, per PWG Process/3.0. Except for waiving the PWG Process/3.0 requirement for a PWG Last Call to span a PWG face-to-face, there is little the PWG Steering Committee can do to 'fast track' this spec. And during the Prototype phase an actual prototype of=20 substantial amounts of the base spec must be performed,=20 reported on, and reviewed by the IPP WG. For comparison, PDF/is had *every* required and=20 optional field prototyped. Wire formats need to be very stable before adopting them. I can't speak to Mike Sweet's editing priorities, but the main IPP Everywhere (profiles) and IPP JPS3 specs are high priority for their Cloud Imaging WG and MFD WG impacts. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc =20 mailto:blueroofmusic@gmail.com Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen wrote: Epson would like in endorse the IPP working group's fast tracking of the PWG/IPP raster specification / standard. Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking of the of PWG/IPP Raster specification / standard.=20 =20 Epson supports the currently proposed format of the raster format provided that the format is "streamable" in order to eliminate the need for printers to provide buffering of full pages. =20 If the format has a REQUIRED color space, and Epson is not proposing that there should be a REQUIRED color space; then Epson would like to propose and support 24-bit sRGB=20 =20 Glen =20 =20 =20 =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC7BF.E2FEF420 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. ------_=_NextPart_001_01CBC7BF.E2FEF420-- --===============1543925405== 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 --===============1543925405==-- From ipp-bounces@pwg.org Tue Feb 8 10:56:18 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B53B3A67D6 for ; Tue, 8 Feb 2011 10:56:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6FT9vzWbeGM for ; Tue, 8 Feb 2011 10:56:16 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 7DB603A6844 for ; Tue, 8 Feb 2011 10:56:16 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2B99079550; Tue, 8 Feb 2011 13:56:09 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id EB3EA79545 for ; Tue, 8 Feb 2011 13:55:52 -0500 (EST) Received: by fxm20 with SMTP id 20so7559032fxm.5 for ; Tue, 08 Feb 2011 10:55:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=63PJ4jTzkjLiMwiKDjlyGKj0SepwZqwqlSb42g8Mbo8=; b=AOcdi7E917jXn7InhMFTlj0t44y1aYoxyrb3xox9GSfm82enO7GLj7Tr/3fFXZmSKs 5dL2iVCjowFhoD/i3bR4zZVjA3csEy24erdXtf30DuqR5+DEvMBTzhg3xHP8kfGCWGh1 nA1PTaHEzeL6Unkqs2i5wBMWGiIGpfROY40MA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dGxEu8ZIap44ICLucsvSvi19MJdo4JUsSxuBDQWczrjK9431RisUQS7L2XXeakL16o TZq8J+e1H28hmfU3UMlvOZSppaRJc/sIU1oo8I9lO57L+a9OU2n6gXuFMyOf21Cl0/gW AyfEY+jOPMzbzVt/EAKv+ZBr1HXDwFPwrjGYc= MIME-Version: 1.0 Received: by 10.223.96.66 with SMTP id g2mr1464785fan.61.1297191351768; Tue, 08 Feb 2011 10:55:51 -0800 (PST) Received: by 10.223.103.142 with HTTP; Tue, 8 Feb 2011 10:55:51 -0800 (PST) In-Reply-To: References: Date: Tue, 8 Feb 2011 13:55:51 -0500 Message-ID: Subject: Re: [IPP] Epson Request for PWG/IPP Raster 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="===============0144494747==" 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: 2B99079550.AA3F5 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0144494747== Content-Type: multipart/alternative; boundary=20cf3054a69fba58aa049bc9e53a --20cf3054a69fba58aa049bc9e53a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen, There is no specific duration for the document status phases. Both the WG last call and PWG Last Call can't reasonably be shortened. The time consumed is often *after* one or the other last call, while the editors update the document and the WG reviews those changes. The scope of a SINGLE prototype (not an interoperability test) is the choice of the implementation. But the PWG SC took a conservative view with PDF/is (prototype every field) and the IPP Fax WG followed through on that. In that case, Rick Seeler (Adobe) tested that the sample PDF/is documents could be correctly displayed by Adobe Reader as well. A PWG Raster prototype could be fairly easily based on the existing open source code for CUPS, I suspect. The interoperability tests (between vendors) normally are only *after* the PWG Candidate Standard is approved and required for advancement to full PWG Standard document status. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 8, 2011 at 1:42 PM, Petrie, Glen wr= ote: > While I understand your comments on fast tracking, is there a =93specifi= c=94 > duration to each phase / process? So, I did not mean to change the proce= ss > but to encourage shortening it. > > > > Can you help me understand the =93scope of a prototype=94? In this case,= the > scope of the technical content is very small but I still assume that the > process steps can not be dropped. > > > > Having just a source provider of the PWG raster is not interoperability. = I > personally do not know of a printer that can read CUPS raster xxx or one > that could be modified to read a subset. So is emulation of a printer ok? > I also assume for interoperability, there must be two independent > developments. > > > > Glen > > > > > > > > > ------------------------------ > > *From:* Ira McDonald [mailto:blueroofmusic@gmail.com] > *Sent:* Tuesday, February 08, 2011 8:49 AM > *To:* Petrie, Glen; Ira McDonald > *Cc:* ipp@pwg.org > *Subject:* Re: [IPP] Epson Request for PWG/IPP Raster > > > > Hi Glen, > > With respect to 'fast tracking' of PWG Raster spec, note > that the status phases Initial/Interim/Protoype/Stable must > occur, per PWG Process/3.0. > > Except for waiving the PWG Process/3.0 requirement > for a PWG Last Call to span a PWG face-to-face, there > is little the PWG Steering Committee can do to 'fast > track' this spec. > > And during the Prototype phase an actual prototype of > substantial amounts of the base spec must be performed, > reported on, and reviewed by the IPP WG. > > For comparison, PDF/is had *every* required and > optional field prototyped. Wire formats need to be > very stable before adopting them. > > I can't speak to Mike Sweet's editing priorities, but the > main IPP Everywhere (profiles) and IPP JPS3 specs > are high priority for their Cloud Imaging WG and MFD > WG impacts. > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Hardcopy WG > 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 > Christmas through April: > 579 Park Place Saline, MI 48176 > 734-944-0094 > May to Christmas: > PO Box 221 Grand Marais, MI 49839 > 906-494-2434 > > > > On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen > wrote: > > Epson would like in endorse the IPP working group=92s fast tracking of the > PWG/IPP raster specification / standard. Epson would like to further > encourage and endorse the PWG Steering committee in approving a (very) fa= st > tracking of the of PWG/IPP Raster specification / standard. > > > > Epson supports the currently proposed format of the raster format provided > that the format is =93streamable=94 in order to eliminate the need for pr= inters > to provide buffering of full pages. > > > > If the format has a REQUIRED color space, and Epson is not proposing that > there should be a REQUIRED color space; then Epson would like to propose = and > support 24-bit sRGB > > > > Glen > > > > > > > > > > > -- > 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. --20cf3054a69fba58aa049bc9e53a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Glen,

There is no specific duration for the document status phase= s.

Both the WG last call and PWG Last Call can't reasonably beshortened.=A0 The time consumed is often *after* one or the other
last= call, while the editors update the document and the WG
reviews those changes.

The scope of a SINGLE prototype (not an inter= operability test)
is the choice of the implementation.=A0 But the PWG SC= took a
conservative view with PDF/is (prototype every field) and the
IPP Fax WG followed through on that.=A0 In that case, Rick Seeler
(Adobe= ) tested that the sample PDF/is documents could be
correctly displayed b= y Adobe Reader as well.

A PWG Raster prototype could be fairly easil= y based on the
existing open source code for CUPS, I suspect.

The interoperability = tests (between vendors) normally are only
*after* the PWG Candidate Stan= dard is approved and required
for advancement to full PWG Standard docum= ent status.

Cheers,
- Ira

Ira McDonald (Musician / Software= Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE= -ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - = IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic<= /a>
http://sites.google.com/site/highnor= thinc
mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 S= aline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 2= 21=A0 Grand Marais, MI 49839
=A0 906-494-2434



On Tue, Feb 8, 2011 at 1:42 PM, Petrie, = Glen <gl= en.petrie@eitc.epson.com> wrote:

While I unders= tand your comments on fast tracking, is there a =93specific=94 duration to each phase / process?=A0 So, I did not mean to change the process but to encourage shortening it.

=A0

Can you help m= e understand the =93scope of a prototype=94?=A0 In this case, the scope of the technical content is very small but I still assume that the process steps can not be dropped.=

=A0

Having just a = source provider of the PWG raster is not interoperability.=A0 I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subse= t.=A0 So is emulation of a printer ok?=A0 I also assume for interoperability, there must be two independent developments.

=A0

Glen

=A0

=A0

=A0

=A0


From: Ira McDonald [mailto:bluero= ofmusic@gmail.com]
Sent: Tuesday, February 08= , 2011 8:49 AM
To: Petrie, Glen; Ira McDo= nald
Cc: ipp@pwg.org
Subject: Re: [IPP] Epson R= equest for PWG/IPP Raster

=A0

Hi Glen,

With respect to 'fast tracking' of PWG Raster spec, note
that the status phases Initial/Interim/Protoype/Stable must
occur, per PWG Process/3.0.

Except for waiving the PWG Process/3.0 requirement
for a PWG Last Call to span a PWG face-to-face, there
is little the PWG Steering Committee can do to 'fast
track' this spec.

And during the Prototype phase an actual prototype of
substantial amounts of the base spec must be performed,
reported on, and reviewed by the IPP WG.

For comparison, PDF/is had *every* required and
optional field prototyped.=A0 Wire formats need to be
very stable before adopting them.

I can't speak to Mike Sweet's editing priorities, but the
main IPP Everywhere (profiles) and IPP JPS3 specs
are high priority for their Cloud Imaging WG and MFD
WG impacts.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.= google.com/site/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 221=A0 Grand Marais, MI 49839
=A0 906-494-2434



On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen <glen.petrie@e= itc.epson.com> wrote:

Epson would like in endorse the IPP working group=92s fast tracking of the PWG/IPP raster specification / standard.=A0 Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking = of the of PWG/IPP Raster specification / standard.

=A0

Epson supports the currently proposed format of the raster format provided that t= he format is =93streamable=94 in order to eliminate the need for printers to provide buffering of full pages.

=A0

If the format has a REQUIRED color space, and Epson is not proposing that there sh= ould be a REQUIRED color space; then Epson would like to propose and support 24-= bit sRGB

=A0

Glen

=A0

=A0

=A0

=A0


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

=A0



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --20cf3054a69fba58aa049bc9e53a-- --===============0144494747== 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 --===============0144494747==-- From ipp-bounces@pwg.org Tue Feb 8 10:58:38 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 186FB3A67DB for ; Tue, 8 Feb 2011 10:58:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.272 X-Spam-Level: X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KluIv+jRGYr0 for ; Tue, 8 Feb 2011 10:58:30 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 445883A67D6 for ; Tue, 8 Feb 2011 10:58:30 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id F0CE27956D; Tue, 8 Feb 2011 13:58:10 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 53DB87956D for ; Tue, 8 Feb 2011 13:57:26 -0500 (EST) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Feb 2011 10:57:25 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Epson Request for PWG/IPP Raster Date: Tue, 8 Feb 2011 10:57:25 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Epson Request for PWG/IPP Raster Thread-Index: AcvHwd8pBxBcx2r7S+qFzKqO7YDcbwAAE6/g References: From: "Petrie, Glen" To: "Ira McDonald" X-OriginalArrivalTime: 08 Feb 2011 18:57:25.0755 (UTC) FILETIME=[068B0CB0:01CBC7C2] 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="===============0332578583==" 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: F0CE27956D.AA609 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0332578583== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC7C2.061F0572" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBC7C2.061F0572 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Thanks for the clarifications=20 =20 ________________________________ From: Ira McDonald [mailto:blueroofmusic@gmail.com]=20 Sent: Tuesday, February 08, 2011 10:56 AM To: Petrie, Glen; Ira McDonald Cc: ipp@pwg.org Subject: Re: [IPP] Epson Request for PWG/IPP Raster =20 Hi Glen, There is no specific duration for the document status phases. Both the WG last call and PWG Last Call can't reasonably be shortened. The time consumed is often *after* one or the other last call, while the editors update the document and the WG=20 reviews those changes. The scope of a SINGLE prototype (not an interoperability test) is the choice of the implementation. But the PWG SC took a conservative view with PDF/is (prototype every field) and the IPP Fax WG followed through on that. In that case, Rick Seeler (Adobe) tested that the sample PDF/is documents could be correctly displayed by Adobe Reader as well. A PWG Raster prototype could be fairly easily based on the existing open source code for CUPS, I suspect. The interoperability tests (between vendors) normally are only *after* the PWG Candidate Standard is approved and required for advancement to full PWG Standard document status. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc =20 mailto:blueroofmusic@gmail.com Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Tue, Feb 8, 2011 at 1:42 PM, Petrie, Glen wrote: While I understand your comments on fast tracking, is there a "specific" duration to each phase / process? So, I did not mean to change the process but to encourage shortening it. =20 Can you help me understand the "scope of a prototype"? In this case, the scope of the technical content is very small but I still assume that the process steps can not be dropped. =20 Having just a source provider of the PWG raster is not interoperability. I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subset. So is emulation of a printer ok? I also assume for interoperability, there must be two independent developments. =20 Glen =20 =20 =20 =20 ________________________________ From: Ira McDonald [mailto:blueroofmusic@gmail.com]=20 Sent: Tuesday, February 08, 2011 8:49 AM To: Petrie, Glen; Ira McDonald Cc: ipp@pwg.org Subject: Re: [IPP] Epson Request for PWG/IPP Raster =20 Hi Glen, With respect to 'fast tracking' of PWG Raster spec, note=20 that the status phases Initial/Interim/Protoype/Stable must=20 occur, per PWG Process/3.0. Except for waiving the PWG Process/3.0 requirement for a PWG Last Call to span a PWG face-to-face, there is little the PWG Steering Committee can do to 'fast track' this spec. And during the Prototype phase an actual prototype of=20 substantial amounts of the base spec must be performed,=20 reported on, and reviewed by the IPP WG. For comparison, PDF/is had *every* required and=20 optional field prototyped. Wire formats need to be very stable before adopting them. I can't speak to Mike Sweet's editing priorities, but the main IPP Everywhere (profiles) and IPP JPS3 specs are high priority for their Cloud Imaging WG and MFD WG impacts. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc =20 mailto:blueroofmusic@gmail.com Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 =20 On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen wrote: Epson would like in endorse the IPP working group's fast tracking of the PWG/IPP raster specification / standard. Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking of the of PWG/IPP Raster specification / standard.=20 =20 Epson supports the currently proposed format of the raster format provided that the format is "streamable" in order to eliminate the need for printers to provide buffering of full pages. =20 If the format has a REQUIRED color space, and Epson is not proposing that there should be a REQUIRED color space; then Epson would like to propose and support 24-bit sRGB=20 =20 Glen =20 =20 =20 =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBC7C2.061F0572 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Thanks for the clarifications

 


From: Ira McDo= nald [mailto:blueroofmusic@gmail.com]
Sent: Tuesday, February 08, = 2011 10:56 AM
To: Petrie, Glen; Ira McDona= ld
Cc: ipp@pwg.org
Subject: Re: [IPP] Epson Req= uest for PWG/IPP Raster

 

Hi Glen,

There is no specific duration for the document status phases.

Both the WG last call and PWG Last Call can't reasonably be
shortened.  The time consumed is often *after* one or the other
last call, while the editors update the document and the WG
reviews those changes.

The scope of a SINGLE prototype (not an interoperability test)
is the choice of the implementation.  But the PWG SC took a
conservative view with PDF/is (prototype every field) and the
IPP Fax WG followed through on that.  In that case, Rick Seeler
(Adobe) tested that the sample PDF/is documents could be
correctly displayed by Adobe Reader as well.

A PWG Raster prototype could be fairly easily based on the
existing open source code for CUPS, I suspect.

The interoperability tests (between vendors) normally are only
*after* the PWG Candidate Standard is approved and required
for advancement to full PWG Standard document status.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.google.com/sit= e/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box= 221  Grand Marais, MI 49839
  906-494-2434



On Tue, Feb 8, 2011 at 1:42 PM, Petrie, Glen <glen.petrie@eitc.epson.com&g= t; wrote:

While I understand your comments on fast tracking, is there a “specific” duration to each phase / process?  So, I did no= t mean to change the process but to encourage shortening it.

 

Can you help me understand the “scope of a prototype̶= 1;?  In this case, the scope of the technical content is very small but I still ass= ume that the process steps can not be dropped.

 

Having just a source provider of the PWG raster is not interoperability.  I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subset.  So is emulation of a printer ok?  I also assume for interoperability, there = must be two independent developments.

 

Glen

 

 

 

 


From: Ira McDonald [mailto:blueroofmusic@gma= il.com]
Sent: Tuesday, February 08, = 2011 8:49 AM
To: Petrie, Glen; Ira McDona= ld
Cc: ipp@pwg.org
Subject: Re: [IPP] Epson Req= uest for PWG/IPP Raster

 

Hi Glen,=

With respect to 'fast tracking' of PWG Raster spec, note
that the status phases Initial/Interim/Protoype/Stable must
occur, per PWG Process/3.0.

Except for waiving the PWG Process/3.0 requirement
for a PWG Last Call to span a PWG face-to-face, there
is little the PWG Steering Committee can do to 'fast
track' this spec.

And during the Prototype phase an actual prototype of
substantial amounts of the base spec must be performed,
reported on, and reviewed by the IPP WG.

For comparison, PDF/is had *every* required and
optional field prototyped.  Wire formats need to be
very stable before adopting them.

I can't speak to Mike Sweet's editing priorities, but the
main IPP Everywhere (profiles) and IPP JPS3 specs
are high priority for their Cloud Imaging WG and MFD
WG impacts.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.google.com/sit= e/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box= 221  Grand Marais, MI 49839
  906-494-2434

&nb= sp;

On Tue, = Feb 8, 2011 at 10:23 AM, Petrie, Glen <glen.petrie@eitc.epson.com> wrote:

Ep= son would like in endorse the IPP working group’s fast tracking of the PWG/IPP = raster specification / standard.  Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking of t= he of PWG/IPP Raster specification / standard.

&n= bsp;

Ep= son supports the currently proposed format of the raster format provided that t= he format is “streamable” in order to eliminate the need for printers to = provide buffering of full pages.

&n= bsp;

If= the format has a REQUIRED color space, and Epson is not proposing that there sh= ould be a REQUIRED color space; then Epson would like to propose and support 24-= bit sRGB

&n= bsp;

Gl= en

&n= bsp;

&n= bsp;

&n= bsp;

&n= bsp;


--
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. ------_=_NextPart_001_01CBC7C2.061F0572-- --===============0332578583== 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 --===============0332578583==-- From ipp-bounces@pwg.org Tue Feb 8 14:06:13 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF7473A68AC for ; Tue, 8 Feb 2011 14:06:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfTgq9ayWt9p for ; Tue, 8 Feb 2011 14:06:12 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 9E6EB3A68B7 for ; Tue, 8 Feb 2011 14:06:12 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0805F7955D; Tue, 8 Feb 2011 17:06:01 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id C7DE579528 for ; Tue, 8 Feb 2011 17:05:48 -0500 (EST) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 04F39D0D5F40; Tue, 8 Feb 2011 14:05:47 -0800 (PST) X-AuditID: 1180711d-b7c12ae00000228a-02-4d51be37735e Received: from [17.151.96.71] (Unknown_Domain [17.151.96.71]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 37.ED.08842.A3EB15D4; Tue, 8 Feb 2011 14:05:46 -0800 (PST) Subject: Re: [IPP] Epson Request for PWG/IPP Raster Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Tue, 8 Feb 2011 14:05:43 -0800 Message-Id: <930A7C7A-ACE7-43D4-B654-5AF57CDC4B3D@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== 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="===============0337328750==" 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: 0805F7955D.A9617 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0337328750== Content-Type: multipart/alternative; boundary=Apple-Mail-1-1067963429 --Apple-Mail-1-1067963429 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Feb 8, 2011, at 8:48 AM, Ira McDonald wrote: > ... > I can't speak to Mike Sweet's editing priorities, but the > main IPP Everywhere (profiles) and IPP JPS3 specs > are high priority for their Cloud Imaging WG and MFD > WG impacts. WRT to the PWG Raster specification, given that I have most of the necessar= y text available to publish another working draft I suspect it will get fin= ished rather quickly. That said, given that sample code and documentation i= s already available there is no reason vendors have to delay their prototyp= e implementations... My editing priorities for the next few months (at least) are: PWG Raster, I= PP JPS3 (first draft/outline), IPP Everywhere (first draft/outline), and PW= G Common Log Format. ________________________________________________________________________ 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. --Apple-Mail-1-1067963429 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On Feb 8, 2011, = at 8:48 AM, Ira McDonald wrote:
...
I can't speak to Mike Sweet's editing priorities, but the
main IPP Everywhere (profiles) and IPP JPS3 specs
are high priority for = their Cloud Imaging WG and MFD
WG impacts.

WRT to the PWG Raster specification, given that I have most of the necess= ary text available to publish another working draft I suspect it will get f= inished rather quickly. That said, given that sample code and documentation= is already available there is no reason vendors have to delay their protot= ype implementations...

My editing priorities for t= he next few months (at least) are: PWG Raster, IPP JPS3 (first draft/outlin= e), IPP Everywhere (first draft/outline), and PWG Common Log Format.
<= div>
___________________= _____________________________________________________
Michael Swe= et, 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. --Apple-Mail-1-1067963429-- --===============0337328750== 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 --===============0337328750==-- From ipp-bounces@pwg.org Tue Feb 8 14:11:03 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A20743A68C8 for ; Tue, 8 Feb 2011 14:11:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSfiA-qVz5Ra for ; Tue, 8 Feb 2011 14:10:58 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id DCCF53A68BD for ; Tue, 8 Feb 2011 14:10:57 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E045779596; Tue, 8 Feb 2011 17:10:52 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id DC13479591 for ; Tue, 8 Feb 2011 17:10:39 -0500 (EST) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 3607ECD87EB3; Tue, 8 Feb 2011 14:10:39 -0800 (PST) X-AuditID: 11807130-b7b3cae00000405d-bb-4d51bf5e4de8 Received: from [17.151.96.71] (Unknown_Domain [17.151.96.71]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 38.91.16477.E5FB15D4; Tue, 8 Feb 2011 14:10:39 -0800 (PST) Subject: Re: [IPP] Epson Request for PWG/IPP Raster Mime-Version: 1.0 (Apple Message framework v1082) From: Michael Sweet In-Reply-To: Date: Tue, 8 Feb 2011 14:10:37 -0800 Message-Id: <65295034-DFC7-4497-B74B-2C4DF143089D@apple.com> References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1082) X-Brightmail-Tracker: AAAAAA== 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="===============0263283958==" 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: E045779596.A8B28 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0263283958== Content-Type: multipart/alternative; boundary=Apple-Mail-2-1068257698 --Apple-Mail-2-1068257698 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Feb 8, 2011, at 10:42 AM, Petrie, Glen wrote: > ... >=20 > Having just a source provider of the PWG raster is not interoperability. = I personally do not know of a printer that can read CUPS raster xxx or one= that could be modified to read a subset. So is emulation of a printer ok?= I also assume for interoperability, there must be two independent develop= ments. >=20 WRT implementations, there is no differentiation between hardware, firmware= , and software - anything that generates or consumes PWG Raster will be con= sidered. As Ira points out, the multiple implementation argument doesn't co= me up until we advance from "PWG Candidate Standard" status to just "PWG St= andard". Interoperability testing will be something that is included in the= updated charter (just as we already have interop/bake-off milestones for I= PP/2.0...) ________________________________________________________________________ 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. --Apple-Mail-2-1068257698 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On Feb 8, 2011, = at 10:42 AM, Petrie, Glen wrote:

...

<= /o:smarttagtype>

Having just a source provider of the PWG raster is not interoperability.  I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subse= t.  So is emulation of a printer ok?  I also assume for interoperability, there must be two independent developments.


WRT implementation= s, there is no differentiation between hardware, firmware, and software - a= nything that generates or consumes PWG Raster will be considered. As Ira po= ints out, the multiple implementation argument doesn't come up until we adv= ance from "PWG Candidate Standard" status to just "PWG Standard". Interoper= ability testing will be something that is included in the updated charter (= just as we already have interop/bake-off milestones for IPP/2.0...)

___________________= _____________________________________________________
Michael Swe= et, 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. --Apple-Mail-2-1068257698-- --===============0263283958== 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 --===============0263283958==-- From ipp-bounces@pwg.org Mon Feb 14 05:55:48 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 845993A6D30 for ; Mon, 14 Feb 2011 05:55:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kX1IBJISy7yj for ; Mon, 14 Feb 2011 05:55:47 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 1159A3A6D2F for ; Mon, 14 Feb 2011 05:55:46 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1AD557951F; Mon, 14 Feb 2011 08:55:55 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 4B4BD7950E for ; Mon, 14 Feb 2011 08:55:40 -0500 (EST) Received: by fxm20 with SMTP id 20so6024660fxm.5 for ; Mon, 14 Feb 2011 05:55:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=zrRdtioJO3dAzB9w9SNjIsqy/M8x012zBalTZYL2+K8=; b=Znyl9qGWTthcrofKfJeR3f1l522KcDza+/Tq6cM4k0Vw2puF+NM6ThqMgLszCnwNEY V0VSbWhmH0SKidMndkyu3xUdOYsDU6icEo1lx8G71LwNJR5Ypz3PuGjTg4Ai/GqCRKsu o5KGEaRGacM+b//8hyGLQ5MCxMSm8KmoFjy4M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=F96TRNrqTeY/OpgAvXtF21IKv/oPXfeK6j0YRgMaO1LZkfXUMcCy5G/O8e8cfMb6oc gdfbJduSVVCXVyBpTCPaCv1P0wf6DJx3CQqquYczyl+o3zHpf58D2Hm8gtheBbUqX8XR MCf9FS9rTFFUGAkQZatLrCmCqOvaC788ocmH4= MIME-Version: 1.0 Received: by 10.223.100.12 with SMTP id w12mr972109fan.42.1297635326620; Sun, 13 Feb 2011 14:15:26 -0800 (PST) Received: by 10.223.103.142 with HTTP; Sun, 13 Feb 2011 14:15:26 -0800 (PST) Date: Sun, 13 Feb 2011 17:15:26 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald , Paul Tykodi , Michael R Sweet X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - NEW TIME - 1pm EDT Monday 14 February 2011 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="===============0001148848==" 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: 1AD557951F.A9E49 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0001148848== Content-Type: multipart/alternative; boundary=20cf3054a729b0f5e7049c31449d --20cf3054a729b0f5e7049c31449d Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be tomorrow. Monday 14 February 10-11am US PST / 1-2pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. *** Main Objective - Work on IPP Everywhere *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from PWG face-to-face - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20110202.pdf (3) Status of IPP/2.0 Second Edition - PWG Formal Vote (Ira) - *ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20110110.pdf* (PWG Formal Vote ends Monday 14 February) - ALL - please cast your votes (4) Discussion of IPP Everywhere (Mike/Ira)* * - *http://pwg-wiki.wikispaces.com/IPP+Everywhere* - Mike/Ira to revise charter for PWG Raster spec - Ira to revise IPPS URI scheme - Andrew/Ira to publish first draft of IPP Scan - other new requirements/features? (5) Next Steps - IPP WG teleconference Monday 28 February Cheers, - Ira (IPP WG Co-Chair) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --20cf3054a729b0f5e7049c31449d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our next IPP WG call will be tomorrow.

=A0Monday 14 February 10-11am US PST / 1-2pm US EST

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

=A0Attendee Access Code: *******#
=A0Attendee ID Code: # (empty)

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


*** Main Objective - Work on IPP Everywhere ***

Agenda:

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

(2) Approve IPP minutes from PWG face-to-face
=A0=A0 - ftp://ftp.pwg.org/pu= b/pwg/ipp/minutes/ippv2-f2f-minutes-20110202.pdf

(3) Status of IPP/2.0 Second Edition - PWG Formal Vote (Ir= a)
=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-2= 0110110.pdf
=A0 =A0=A0 (PWG Formal Vote ends Monday 14 February)
=A0=A0 - ALL - ple= ase cast your votes

(4) Discussion of IPP Everywhere (M= ike/Ira)
=A0=A0 - http://pwg-wiki.wikispaces.com/IPP+Everywhere
=A0=A0 - Mike/Ira to revise charter for PWG Raster spec
=A0=A0 - Ira to = revise IPPS URI scheme
=A0=A0 - Andrew/Ira to publish first draft of IPP= Scan
=A0=A0 - other new requirements/features?

(5) Next Steps
=A0=A0 - IPP WG teleconference Monday 28 Feb= ruary

Cheers,
- Ira (IPP WG Co-Chair)


Ira McDonald = (Musician / Software Architect)
Chair - Linux Foundation Open Printing W= G
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF = Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic<= /a>
http://sites.google.com/site/highnor= thinc
mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 S= aline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 2= 21=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. --20cf3054a729b0f5e7049c31449d-- --===============0001148848== 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 --===============0001148848==-- From ipp-bounces@pwg.org Mon Feb 14 11:14:26 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6E783A6DA4 for ; Mon, 14 Feb 2011 11:14:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwXV6TVWsxLu for ; Mon, 14 Feb 2011 11:14:26 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 437313A6C6C for ; Mon, 14 Feb 2011 11:14:25 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CF7D97952A; Mon, 14 Feb 2011 14:14:35 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id ADDDA79495 for ; Mon, 14 Feb 2011 14:14:23 -0500 (EST) Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out3.apple.com (Postfix) with ESMTP id 8DE7ECEEB0D9 for ; Mon, 14 Feb 2011 11:14:22 -0800 (PST) X-AuditID: 11807136-b7b89ae000000345-4d-4d597f0e3f3a Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id B0.7F.00837.E0F795D4; Mon, 14 Feb 2011 11:14:22 -0800 (PST) From: Michael Sweet Date: Mon, 14 Feb 2011 11:14:22 -0800 To: ipp@pwg.org Message-Id: <082DF403-2863-484B-944E-9156CDA53A7D@apple.com> Mime-Version: 1.0 (Apple Message framework v1198) X-Mailer: Apple Mail (2.1198) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted for 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: , Content-Type: multipart/mixed; boundary="===============0207785782==" 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: CF7D97952A.A8E44 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0207785782== Content-Type: multipart/alternative; boundary="Apple-Mail=_980CE641-517A-49FF-BC09-D89DC088D2AF" --Apple-Mail=_980CE641-517A-49FF-BC09-D89DC088D2AF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 All, I have posted the minutes from today's IPP conference call at: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20110214.pdf Please let me know if you see any errors. Pending action items: =95 Action: Mike to put out (updated) drafts of PWG Raster, JPS3, and IPP = Everywhere =95 Action: Ira to amend IPP Everywhere Charter for new documents and sche= dule (open) =95 Action: Ira to update IPPS URI scheme and transport binding RFC ________________________________________________________________________ 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. --Apple-Mail=_980CE641-517A-49FF-BC09-D89DC088D2AF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 All,

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

=

Please let me= know if you see any errors.

Pending action items:=

While I understand your comments on fa= st tracking, is there a “specific” duration to each phase / proces= s?  So, I did not mean to change the process but to encourage shortening it.

 

Can you help me understand the “= scope of a prototype”?  In this case, the scope of the technical conte= nt is very small but I still assume that the process steps can not be dropped.=

 

Having just a source provider of the P= WG raster is not interoperability.  I personally do not know of a printer that can read CUPS raster xxx or one that could be modified to read a subse= t.  So is emulation of a printer ok?  I also assume for interoperability, there must be two independent developments.

 

Glen

 

 

 

 


From: Ira McDo= nald [mailto:blueroofmusic@gmail.com]
Sent: Tuesday, February 08, = 2011 8:49 AM
To: Petrie, Glen; Ira McDona= ld
Cc: ipp@pwg.org
Subject: Re: [IPP] Epson Req= uest for PWG/IPP Raster

 

Hi Glen,

With respect to 'fast tracking' of PWG Raster spec, note
that the status phases Initial/Interim/Protoype/Stable must
occur, per PWG Process/3.0.

Except for waiving the PWG Process/3.0 requirement
for a PWG Last Call to span a PWG face-to-face, there
is little the PWG Steering Committee can do to 'fast
track' this spec.

And during the Prototype phase an actual prototype of
substantial amounts of the base spec must be performed,
reported on, and reviewed by the IPP WG.

For comparison, PDF/is had *every* required and
optional field prototyped.  Wire formats need to be
very stable before adopting them.

I can't speak to Mike Sweet's editing priorities, but the
main IPP Everywhere (profiles) and IPP JPS3 specs
are high priority for their Cloud Imaging WG and MFD
WG impacts.

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
ht= tp://sites.google.com/site/blueroofmusic
http://sites.google.com/sit= e/highnorthinc

mailto:blueroo= fmusic@gmail.com
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box= 221  Grand Marais, MI 49839
  906-494-2434



On Tue, Feb 8, 2011 at 10:23 AM, Petrie, Glen <glen.petrie@eitc.epson.com&g= t; wrote:

Ep= son would like in endorse the IPP working group’s fast tracking of the PWG/IPP raster specification / standard.  Epson would like to further encourage and endorse the PWG Steering committee in approving a (very) fast tracking = of the of PWG/IPP Raster specification / standard.

&n= bsp;

Ep= son supports the currently proposed format of the raster format provided that t= he format is “streamable” in order to eliminate the need for print= ers to provide buffering of full pages.

&n= bsp;

If= the format has a REQUIRED color space, and Epson is not proposing that there sh= ould be a REQUIRED color space; then Epson would like to propose and support 24-= bit sRGB

&n= bsp;

Gl= en

&n= bsp;

&n= bsp;

&n= bsp;

&n= bsp;


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

 

=95 Action: Mike to put out (updated) drafts of PWG Ra= ster, JPS3, and IPP Everywhere
=95 Action: Ira to amend IPP Everywhere Charter for= new documents and schedule (open)
=95 Action: Ira to update IPPS URI schem= e and transport binding RFC

__________= ______________________________________________________________
Mi= chael 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. --Apple-Mail=_980CE641-517A-49FF-BC09-D89DC088D2AF-- --===============0207785782== 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 --===============0207785782==-- From pwg-announce-bounces@pwg.org Tue Feb 15 09:30:06 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 151943A6C64 for ; Tue, 15 Feb 2011 09:30:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.998 X-Spam-Level: X-Spam-Status: No, score=-101.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_66=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWHoIj+dvQZh for ; Tue, 15 Feb 2011 09:29:55 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 0B9A13A6CD9 for ; Tue, 15 Feb 2011 09:29:54 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A72B679544; Tue, 15 Feb 2011 12:29:49 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by pwg.org (Postfix) with ESMTP id 47CA779542 for ; Tue, 15 Feb 2011 12:29:32 -0500 (EST) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta01.westchester.pa.mail.comcast.net with comcast id 8HV11g00227AodY51HVZ3N; Tue, 15 Feb 2011 17:29:33 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta19.westchester.pa.mail.comcast.net with comcast id 8HVY1g008548CT43fHVYQQ; Tue, 15 Feb 2011 17:29:33 +0000 From: "William Wagner" To: References: In-Reply-To: Date: Tue, 15 Feb 2011 12:29:27 -0500 Message-ID: <001801cbcd35$e5e5bb30$b1b13190$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acu/GTfMi3wqoSjeST+HOXvun1JuPQOF81ZQ Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] RE: Comments on MFD Model and Common Semantics 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="===============1685859085==" 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: A72B679544.AE329 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============1685859085== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01CBCD0B.FD0FB330" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0019_01CBCD0B.FD0FB330 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit All, To remind you, the PWG Process/3.0 requires that a 30% of all PWG members (NOT as previously indicated, 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. Agreed that the MFD Model and Common Semantics is a large and somewhat unwieldy document, it has been in process and has been reviewed and re-reviewed for over three years (and there are lots of pictures.) It is likely that anyone who has participated in the MFD telephone or face-to-face meetings has been exposed to this specification. The document represents the collection of MFD characterization information accumulated since the MFD group started in 2007, and has reflected the changes and improvements to the MFD model as that model as addressed the various services. It acts as a guide to and elaboration upon what is in the MFD Schema. One of the intentions of the specification was to ensure a consistent and cohesive view of the MFD regardless of what specific imaging service was being considered. An effect of this was to make the agreement upon this specification a necessary condition to the approval of any further MFD Service specification. As we embark upon expanding access to MFD services, it is critical that what constitutes these services be consistently specified. To allow these specifications to proceed, the MFD Model and Common Semantics specification must be approved. And to allow the MFD Model and Common Semantics to be presented for ballot, sufficient last call comments from the PWG members must be received. So that sufficient review may be documented, please respond as indicated below that you or someone in your member company has reviewed the document (or is prepared the accept the document for vote without further review). If you have comments, questions or objections to what is in the document, all the better.please make them known so that they may be addressed. But we believe it is in the best interests of all of our companies to allow these MFD Service specifications to proceed, so please respond. Thanks, Bill Wagner, Co-editor of MFD Model From: Zehler, Peter Sent: Monday, January 24, 2011 8:07 AM To: pwg-announce@pwg.org Subject: PWG Last Call of MFD Model and Common Semantics (1/24/11 - 2/25/11) All, [This PWG Last Call will start today on Monday January 24, 2011. This PWG Last Call will end Friday February 25, 2011 at 10pm US PDT.] This is the formal announcement of the PWG Last Call for the MFD Model and Common Semantics, which is located at: All required operations and attributes defined in this document have been prototyped by Xerox and/or other vendors through their deployment of existing protocols such as ISO 10175, IETF/PWG IPP and Microsoft WSD. The MFD WG has completed a working group last call and subsequent revisions of this document. The PWG Process/3.0 requires that a quorum (30%) of PWG voting members must acknowledge a PWG Last Call (with or without comments), before any document can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote but it DOES require your review acknowledgment. Please send your review acknowledgment *exactly* as follows: To: mfd at pwg.org Subject: has reviewed the MFD Model and Common Semantics and has [no] comments Please do NOT simply reply to this note on the PWG-Announce list. Note: The PWG Definition of the Standards Development Process Version 3.0 is located at: Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -- 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_0019_01CBCD0B.FD0FB330 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 <= /p>

To remind you, the=
 PWG Process/3.0 requires that a 30% of all PWG members (NOT as previously =
indicated, voting members) must acknowledge a PWG Last Call (with or withou=
t comments), before any document can progress to PWG Formal Vote.  Thi=
s PWG Last Call is NOT a Formal Vote but it DOES require your review acknow=
ledgment.
 
Agreed that the MFD Model and Common Semantics <ftp://=
ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110124.pdf>
is a large =
and somewhat unwieldy document, it has been in process and has been reviewe=
d and re-reviewed for over three years (and there are lots of pictures.) It=
 is likely that anyone who has participated in the MFD telephone or face-to=
-face meetings has been exposed to this specification. The document represe=
nts the collection of MFD characterization information accumulated since th=
e MFD group started in 2007, and has reflected the changes and improvements=
 to the MFD model as that model as addressed the various services. It acts =
as a guide to and elaboration upon  what is in the MFD Schema.
=
 
One of the  intentions of the specification was to ensure a consis=
tent and cohesive view of the MFD regardless of what specific imaging servi=
ce was being considered. An effect of this was to make the agreement upon t=
his specification a necessary condition to the approval of any further MFD =
Service specification. As we embark upon expanding access to MFD services, =
it is critical that what constitutes these services be consistently specifi=
ed. To allow these specifications to proceed, the MFD Model and Common Sema=
ntics specification must be approved. And to allow the MFD Model and Common=
 Semantics to be presented for ballot, sufficient last call comments from t=
he PWG members must be received. 
 
So that sufficient review ma=
y be documented, please  respond as indicated below that you or someon=
e in your member company has reviewed the document (or is prepared the acce=
pt the document for vote without further review). If you have comments, que=
stions or objections to what is in the document, all the better…pleas=
e make them known so that they may be addressed. But we believe it is in th=
e best interests of all of our companies to allow these MFD Service specifi=
cations to proceed, so please respond.

 

Thanks,

 

Bill Wagner, Co-editor of MFD M= odel

 

From: Zehler, Peter
Sent: Monday, January 24, 2011 8:07 AM=
To: pwg-announce@pwg.org
Subject: PWG Last Call of MFD= Model and Common Semantics (1/24/11 - 2/25/11)

=

 

All,
 
[This PWG Last Call will start t=
oday on Monday January 24, 2011.
This PWG Last Call will end Friday Febru=
ary 25, 2011 at 10pm US PDT.]
 
This is the formal announcement of=
 the PWG Last Call for the MFD Model and Common Semantics, which is located=
 at:
<ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110124.pdf>=
 
All required operations and attributes defined in this document=
 have been prototyped by Xerox and/or other vendors through their deploymen=
t of existing protocols such as ISO 10175, IETF/PWG IPP and Microsoft WSD.&=
nbsp; The MFD WG has completed a working group last call and subsequent rev=
isions of this document.
 
The PWG Process/3.0 requires that a q=
uorum (30%) of PWG voting members must acknowledge a PWG Last Call (with or=
 without comments), before any document can progress to PWG Formal Vote.&nb=
sp; This PWG Last Call is NOT a Formal Vote but it DOES require your review=
 acknowledgment.
 
Please send your review acknowledgment *exactly=
* as follows:
 
To:  mfd at pw=
g.org
Subject:  <Company Name> has reviewed the MFD Model =
and Common Semantics and has [no] comments
 
=
 
Please do NO=
T simply reply to this note on the PWG-Announce list.
 
Note: =
; The PWG Definition of the Standards Development Process Version 3.0 is lo=
cated at:
  <http://www.pwg.org/chair/membership_docs/pwg-process30.p=
df>
 

 

 

<= o:p> 

Peter Zehler<= br>
Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com

V= oice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.

800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701

 


--
Th= is message has been scanned for viruses and
dangerous content by MailScanner, and is
belie= ved to be clean.


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0019_01CBCD0B.FD0FB330-- --===============1685859085== 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 --===============1685859085==-- From pwg-announce-bounces@pwg.org Mon Feb 21 14:21:58 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B91E3A7191 for ; Mon, 21 Feb 2011 14:21:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.497 X-Spam-Level: X-Spam-Status: No, score=-100.497 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_50=0.001, HTML_MESSAGE=0.001, J_BACKHAIR_43=1, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhvkyJtWLana for ; Mon, 21 Feb 2011 14:21:51 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 0F97E3A716D for ; Mon, 21 Feb 2011 14:21:50 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5CC247946C; Mon, 21 Feb 2011 17:22:08 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by pwg.org (Postfix) with ESMTP id 14B537945D for ; Mon, 21 Feb 2011 17:21:51 -0500 (EST) Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta04.westchester.pa.mail.comcast.net with comcast id AmLY1g0080EZKEL54mMsLL; Mon, 21 Feb 2011 22:21:52 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta01.westchester.pa.mail.comcast.net with comcast id AmMp1g016548CT43MmMrQ5; Mon, 21 Feb 2011 22:21:52 +0000 From: "William Wagner" To: References: In-Reply-To: Date: Mon, 21 Feb 2011 17:21:38 -0500 Message-ID: <000001cbd215$b735be90$25a13bb0$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcvR8ebOoN4M9AVCRdiFyWyNcOkL7gAIZhAw Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "'Zehler, Peter'" Subject: [Pwg-Announce] MFD Model and Common Semantics Last Call 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="===============1379152412==" 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: 5CC247946C.AE0D6 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============1379152412== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01CBD1EB.CE5FB690" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0001_01CBD1EB.CE5FB690 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In considering the Xerox comments to the MFD Model and Common Semantics , it appears that the PDF version does not agree with the MS Word file. (The Word file shows 204 pages while the pdf shows 217.) This likely is partially a result of the duplication of figures (as indicated in the comments) which does not appear in the MS Word version. I apologize for this, but I had mistakenly expected the PDF to agree with the MS Word versions, at least in terms of content if not format. The last call period for this document is intended to end on 25 February. I will post a version addressing the comments received to date (with a list of changes) in the next day or two, provided that I can figure out how to avoid the MS Word to PDF translation problem. If reviewing the currently posted document, consider the figures to appear the first time. The duplicates occurring on later pages are ghosts. Thanks, Bill Wagner From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Zehler, Peter Sent: Monday, February 21, 2011 1:05 PM To: mfd@pwg.org Subject: [MFD] Xerox has reviewed the MFD Model and Common Semantics and has comments Here are the comments from Xerox: SECTION 2.2.1 page 22 figure 6 Primary interfaces is missing a line from scanner subunit to Email Out Section 2.2.2 page 24 duplicate graphic of figure 7 on page 26. Section 2.4.2 page 30 line 825 job produces 1 ton should be job produces 1 to N Section 3.2 page 48 line 1149 missing reference source Section 3.6 page 60 line 1212 missing reference source Section 3.10 page 70 line 1280 missing reference source line 1282 figure 45 should be figure 44 Section 4.3 page 95 duplicate graphic of figure 62 Section 4.3.1 page 102 10th attribute from the top, is annotation a instance of imposition, if not it should be added to the graphic Section 4.3.3 page 112 duplicate graphic of figure 73 Line 1644 References figure 73 but no graphic below the reference. page 113 duplicate graphic of figure 74 page 114 duplicate graphic of figure 75 Section 4.7.1 page 129 line 1759 reference source not found Section 5.1 page 132 line 1829 reference source not found page 133 graphic missing caption Image Job Status Element Page 135 Figure 84 caption not bolded Section 5.2.1 page 141 does imposition fulfill requirement for annotation programming Section 5.2.3 page 150 duplicate graphic of figure 94 Section 7.1 page 165 Figure 102 graphic shows up on this page but is referenced in the document as being on page 167 Section 7.1.4 page 167 line 2126 Scheduling of Jobs should be scheduling of the service's Jobs. Section 7.2.1. page 168 duplicate graphic of figure 103 page 171 duplicate graphic of figure 103 Section 7.3.1.3 page 183 line 2423 reference source not found line 2424 aceljob should be CancelJob Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -- 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_0001_01CBD1EB.CE5FB690 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

In considering the Xerox comments to the MFD= Model and Common Semantics , it appears that the PDF version does not agre= e with the MS Word file. (The Word file shows 204 pages while the pdf shows= 217.) This likely is partially  a result of the duplication of figure= s (as indicated in the comments) which does not appear in the MS Word versi= on. I apologize for this, but I had mistakenly expected  the PDF to ag= ree with the MS Word versions, at least in terms of content if not format. = The last call period for this document is intended to end on 25 February. I= will post a version addressing the comments received to date (with a list = of changes) in the next day or two, provided that I can figure out how to a= void  the MS Word to PDF translation problem. If reviewing the current= ly posted document, consider the figures to appear the first time. The dupl= icates occurring on later pages are ghosts.

 

Thanks,

 

Bill Wagner

=  

From:<= span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mfd-boun= ces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Zehler, Peter<= br>Sent: Monday, February 21, 2011 1:05 PM
To: mfd@pwg.org=
Subject: [MFD] Xerox has reviewed the MFD Model and Common Seman= tics and has comments

 

He= re are the comments from Xerox:

<= span style=3D'color:#1F497D'> 

 

SECTION 2.2.1    page 2= 2             &= nbsp; figure 6           =        Primary interfaces is missing a line f= rom scanner subunit to Email Out

= Section 2.2.2      page 2= 4             &= nbsp;           &nbs= p;            &= nbsp;         duplicate graphic of = figure 7 on page 26.

Section 2.4.2      page 30 = ;              = line 825           &= nbsp;     job produces 1 ton should be job produces = 1 to N

Section 3.2          p= age 48           &nb= sp;    line 1149       &n= bsp;      missing reference source

Section 3.6 &= nbsp;        page 60   &n= bsp;            line= 1212           &nbs= p;  missing reference source

Section 3.10     &n= bsp;  page 70         &nb= sp;      line 1280     &n= bsp;        missing reference source
=             &nb= sp;            =             &nb= sp;            =             &nb= sp; line 1282          &n= bsp;   figure 45 should be figure 44

=

Section 4.3  &= nbsp;       page 95    &n= bsp;            = ;            &n= bsp;            = ;      duplicate graphic of  figure 62

Section 4= .3.1      page 102     &n= bsp;            = ;            &n= bsp;            = ;   10th attribute from the top, is annotation a insta= nce of imposition, if not it should be added to the graphic

Section 4.3.3 = ;     page 112       = ;            &n= bsp;            = ;            &n= bsp; duplicate graphic of figure 73

       =             &nb= sp;            =             &nb= sp;            =        Line 1644     = ;        References figure 73 but no gra= phic below the reference.

        &nbs= p;            &= nbsp;          page 113 &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;       duplicate graphic of figure 74
&n= bsp;            = ;            &n= bsp;      page 114     &n= bsp;            = ;            &n= bsp;            = ;   duplicate graphic of figure 75

Section 4.7.1   &= nbsp;  page 129         &= nbsp;    line 1759       =        reference source not found<= /span>

Section 5.1&nb= sp;         page 132  &nb= sp;           line 1829&n= bsp;            = ; reference source not found
       &= nbsp;           &nbs= p;            page 1= 33            &= nbsp;            &nb= sp;            =         graphic missing caption Image Jo= b Status Element

          &= nbsp;           &nbs= p;         Page 135  &nbs= p;           Figure 84&nb= sp;            = caption not bolded

Section 5.2.1      page 141&nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;       does imposition fulfill requireme= nt for annotation programming

Section 5.2.3      page= 150            = ;            &n= bsp;            = ;         duplicate graphic of figu= re 94

Section 7.1          page 1= 65            &= nbsp; Figure 102          = ; graphic shows up on this page but is referenced in the document as being = on page 167

Section 7.1.4      page 167  &n= bsp;           line 2126&= nbsp;           &nbs= p; Scheduling of Jobs should be scheduling of the service’s Jobs.<= /b>

Section 7.2.1.     page 168   &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;     duplicate graphic of figure 103
  &= nbsp;           &nbs= p;            &= nbsp;    page 171       &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p; duplicate graphic of figure 103
Section 7.3.1.3   page 183&= nbsp;           &nbs= p; line 2423          &nb= sp;   reference source not found
     = ;            &n= bsp;            = ;            &n= bsp;            = ;         line 2424  &nbs= p;           acel<serv= ice>job should be Cancel<service>Job

<= p class=3DMsoNormal> 

 

 

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

 


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0001_01CBD1EB.CE5FB690-- --===============1379152412== 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 --===============1379152412==-- From pwg-announce-bounces@pwg.org Mon Feb 21 14:44:48 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 592283A7195 for ; Mon, 21 Feb 2011 14:44:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.747 X-Spam-Level: X-Spam-Status: No, score=-99.747 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_50=0.001, HTML_MESSAGE=0.001, J_BACKHAIR_43=1, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+gqB5I4P8vV for ; Mon, 21 Feb 2011 14:44:41 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 0879F3A70F9 for ; Mon, 21 Feb 2011 14:44:41 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 184C579495; Mon, 21 Feb 2011 17:44:46 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by pwg.org (Postfix) with ESMTP id 86CCC793BE for ; Mon, 21 Feb 2011 17:44:30 -0500 (EST) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta06.westchester.pa.mail.comcast.net with comcast id Amj91g0041wpRvQ56mkXcH; Mon, 21 Feb 2011 22:44:31 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta18.westchester.pa.mail.comcast.net with comcast id AmkV1g00X548CT43emkVGf; Mon, 21 Feb 2011 22:44:30 +0000 From: "William Wagner" To: References: <000001cbd215$b735be90$25a13bb0$@net> In-Reply-To: <000001cbd215$b735be90$25a13bb0$@net> Subject: RE: [Pwg-Announce] MFD Model and Common Semantics Last Call Date: Mon, 21 Feb 2011 17:44:19 -0500 Message-ID: <001401cbd218$e0959aa0$a1c0cfe0$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcvR8ebOoN4M9AVCRdiFyWyNcOkL7gAIZhAwAAFAkQA= Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean 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="===============1964917763==" 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: 184C579495.ADA75 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============1964917763== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01CBD1EE.F7BF92A0" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0015_01CBD1EE.F7BF92A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Correction - the unintentional figure duplications apparently occurred in an MS Word version conversion, not PDF. From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of William Wagner Sent: Monday, February 21, 2011 5:22 PM To: pwg-announce@pwg.org Cc: 'Zehler, Peter' Subject: [Pwg-Announce] MFD Model and Common Semantics Last Call In considering the Xerox comments to the MFD Model and Common Semantics , it appears that the PDF version does not agree with the MS Word file. (The Word file shows 204 pages while the pdf shows 217.) This likely is partially a result of the duplication of figures (as indicated in the comments) which does not appear in the MS Word version. I apologize for this, but I had mistakenly expected the PDF to agree with the MS Word versions, at least in terms of content if not format. The last call period for this document is intended to end on 25 February. I will post a version addressing the comments received to date (with a list of changes) in the next day or two, provided that I can figure out how to avoid the MS Word to PDF translation problem. If reviewing the currently posted document, consider the figures to appear the first time. The duplicates occurring on later pages are ghosts. Thanks, Bill Wagner From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] On Behalf Of Zehler, Peter Sent: Monday, February 21, 2011 1:05 PM To: mfd@pwg.org Subject: [MFD] Xerox has reviewed the MFD Model and Common Semantics and has comments Here are the comments from Xerox: SECTION 2.2.1 page 22 figure 6 Primary interfaces is missing a line from scanner subunit to Email Out Section 2.2.2 page 24 duplicate graphic of figure 7 on page 26. Section 2.4.2 page 30 line 825 job produces 1 ton should be job produces 1 to N Section 3.2 page 48 line 1149 missing reference source Section 3.6 page 60 line 1212 missing reference source Section 3.10 page 70 line 1280 missing reference source line 1282 figure 45 should be figure 44 Section 4.3 page 95 duplicate graphic of figure 62 Section 4.3.1 page 102 10th attribute from the top, is annotation a instance of imposition, if not it should be added to the graphic Section 4.3.3 page 112 duplicate graphic of figure 73 Line 1644 References figure 73 but no graphic below the reference. page 113 duplicate graphic of figure 74 page 114 duplicate graphic of figure 75 Section 4.7.1 page 129 line 1759 reference source not found Section 5.1 page 132 line 1829 reference source not found page 133 graphic missing caption Image Job Status Element Page 135 Figure 84 caption not bolded Section 5.2.1 page 141 does imposition fulfill requirement for annotation programming Section 5.2.3 page 150 duplicate graphic of figure 94 Section 7.1 page 165 Figure 102 graphic shows up on this page but is referenced in the document as being on page 167 Section 7.1.4 page 167 line 2126 Scheduling of Jobs should be scheduling of the service's Jobs. Section 7.2.1. page 168 duplicate graphic of figure 103 page 171 duplicate graphic of figure 103 Section 7.3.1.3 page 183 line 2423 reference source not found line 2424 aceljob should be CancelJob Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -- 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_0015_01CBD1EE.F7BF92A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Correction – the unintentional figure = duplications apparently occurred in an MS Word version conversion, not PDF.=

 

Fr= om: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] <= b>On Behalf Of William Wagner
Sent: Monday, February 21, 2011= 5:22 PM
To: pwg-announce@pwg.org
Cc: 'Zehler, Peter'Subject: [Pwg-Announce] MFD Model and Common Semantics Last Call

 

<= p class=3DMsoNormal>In consi= dering the Xerox comments to the MFD Model and Common Semantics , it appear= s that the PDF version does not agree with the MS Word file. (The Word file= shows 204 pages while the pdf shows 217.) This likely is partially  a= result of the duplication of figures (as indicated in the comments) which = does not appear in the MS Word version. I apologize for this, but I had mis= takenly expected  the PDF to agree with the MS Word versions, at least= in terms of content if not format. The last call period for this document = is intended to end on 25 February. I will post a version addressing the com= ments received to date (with a list of changes) in the next day or two, pro= vided that I can figure out how to avoid  the MS Word to PDF translati= on problem. If reviewing the currently posted document, consider the figure= s to appear the first time. The duplicates occurring on later pages are gho= sts.

 

Thanks,

 

Bill Wagner

 

From: mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org= ] On Behalf Of Zehler, Peter
Sent: Monday, February 21, 20= 11 1:05 PM
To: mfd@pwg.org
Subject: [MFD] Xerox has rev= iewed the MFD Model and Common Semantics and has comments
=

 

Here are the comments from Xerox:

 = ;

&= nbsp;

SE= CTION 2.2.1    page 22       &= nbsp;       figure 6     =              Pr= imary interfaces is missing a line from scanner subunit to Email Out

Section 2= .2.2      page 24       &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;   duplicate graphic of figure 7 on page 26.<= /p>

Section 2.4.2 &n= bsp;    page 30        &n= bsp;      line 825     &n= bsp;           job produc= es 1 ton should be job produces 1 to N

Section 3.2   &nb= sp;      page 48     &nbs= p;          line 1149 &nb= sp;            missi= ng reference source

Section 3.6       &nb= sp;  page 60         &nbs= p;      line 1212     &nb= sp;        missing reference source=

Section= 3.10        page 70   &n= bsp;            line= 1280           &nbs= p;  missing reference source
      &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;       line 1282    &= nbsp;         figure 45 should be <= b>figure 44

Section 4.3        &nb= sp; page 95          &nbs= p;            &= nbsp;           &nbs= p;            duplic= ate graphic of  figure 62

Section 4.3.1      pag= e 102           &nbs= p;            &= nbsp;           &nbs= p;         10th attribut= e from the top, is annotation a instance of imposition, if not it should be= added to the graphic

Section 4.3.3      page 112&nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;       duplicate graphic of figure 73

 = ;            &n= bsp;            = ;            &n= bsp;            = ;             L= ine 1644           &= nbsp; References figure 73 but no graphic below the reference.

  &nb= sp;            =             &nb= sp;    page 113       &nb= sp;            =             &nb= sp;            = duplicate graphic of figure 74
      &nbs= p;            &= nbsp;            pag= e 114           &nbs= p;            &= nbsp;           &nbs= p;         duplicate graphic of fig= ure 75

Section 4.7.1      page 129   &= nbsp;          line 1759 =              re= ference source not found

Section 5.1       =    page 132         =      line 1829       = ;       reference source not found
 &= nbsp;           &nbs= p;            &= nbsp;     page 133      &= nbsp;            &nb= sp;            =             &nb= sp; graphic missing caption Image Job Status Element

<= p class=3DMsoNormal>    &= nbsp;           &nbs= p;            &= nbsp;  Page 135         &= nbsp;    Figure 84       =        caption not bolded

Section 5.2.1 &nb= sp;    page 141       &nb= sp;            =             &nb= sp;            = does imposition fulfill requirement for annotation programming<= /span>

Section 5.2.3&= nbsp;     page 150      &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;  duplicate graphic of figure 94

Section 7.1    &nb= sp;     page 165      &nb= sp;       Figure 102    &= nbsp;      graphic shows up on this page but is re= ferenced in the document as being on page 167

Section 7.1.4   &= nbsp;  page 167         &= nbsp;    line 2126       =        Scheduling of Jobs should be schedu= ling of the service’s Jobs.

Section 7.2.1.   =   page 168          =             &nb= sp;            =            duplicate grap= hic of figure 103
         =             &nb= sp;          page 171 &nb= sp;            =             &nb= sp;            =        duplicate graphic of figure 103
Sec= tion 7.3.1.3   page 183       =        line 2423     = ;         reference source not foun= d
           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;  line 2424         &nb= sp;    acel<service>job should be Cancel<service= >Job

 

=

 

 

Peter Zehler

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

 <= /p>


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


--
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. ------=_NextPart_000_0015_01CBD1EE.F7BF92A0-- --===============1964917763== 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 --===============1964917763==-- From ipp-bounces@pwg.org Mon Feb 21 21:36:34 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D9693A6823 for ; Mon, 21 Feb 2011 21:36:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D+zJarN4B5Kd for ; Mon, 21 Feb 2011 21:36:31 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 7D16A3A6820 for ; Mon, 21 Feb 2011 21:36:31 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5E3FB79508; Tue, 22 Feb 2011 00:36:53 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 7491179501 for ; Tue, 22 Feb 2011 00:36:31 -0500 (EST) Received: by fxm17 with SMTP id 17so2566172fxm.5 for ; Mon, 21 Feb 2011 21:36:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=pPzMeROo24NGuU5NL1ibSZCh2l3JxVZWPPqc0uGZ8gE=; b=AxBd0qd9iyXgbAjowIsQzDOsOzwxTSR/YL+1OB8/TBY98COg6eFVI95tNIAxETf0Q+ q+/NZVnildV4odJ/3V/d8q2cbUHmSXuvN4WDokeOXsvXV2P/4pdV3l3VmCQ4Cnv6JZhH RqaZvJQrxY4mBqZMWR/A2xMQaC2NqXzuIbiHw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=nTIFqemkt9iIrAOhNr1OFsNHlbAyLjkt5c5ITRcls8GnIT+LOIQhPI7omjJIzJOFO4 HEvHsgquh/UY+0pK/MLvFbl9pvVxulRwE+77fxuKG2VOUGDLhEMeKUwnPDG5ZUL8XCWd 08sM67niE71ToNjBh/9XOAYawCKyPxnzfx368= MIME-Version: 1.0 Received: by 10.223.103.12 with SMTP id i12mr2531022fao.43.1298327763176; Mon, 21 Feb 2011 14:36:03 -0800 (PST) Received: by 10.223.78.132 with HTTP; Mon, 21 Feb 2011 14:36:03 -0800 (PST) Date: Mon, 21 Feb 2011 17:36:03 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Revised IPP Everywhere Charter (21 February 2011) 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="===============2106325925==" 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: 5E3FB79508.A8784 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2106325925== Content-Type: multipart/alternative; boundary=20cf3054a547205215049cd27d21 --20cf3054a547205215049cd27d21 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just posted a new IPP Everywhere Project charter at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110221.pdf / doc - line numbers and redlines Major revision that adds all of the following specs: - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-track) - LDAP Printer Schema (IETF informational) - PWG Raster (w/ IANA MIME type registration) - IPP Everywhere First Edition (printing) - clarified scope as printing only - IPP Scan Service - IPP System Control Service - IPP Fax Service (leveraging previous IPP Fax project) - IPP Everywhere Second Edition (multifunction) Added initial draft and prototype draft milestones for all these specs (but not PWG Last Call except for Requirements because prototyping may change them). Revised many milestone dates - Bill - please check them for plausibility. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --20cf3054a547205215049cd27d21 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've just posted a new IPP Everywhere Project charter at:
ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-2011= 0221.pdf / doc
- line numbers and redlines

Major revision that adds all of the foll= owing specs:

- IPP over HTTPS Transport Binding and 'ipps' U= RI Scheme (IETF standards-track)
- LDAP Printer Schema (IETF information= al)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edi= tion (printing) - clarified scope as printing only
- IPP Scan Service - IPP System Control Service
- IPP Fax Service (leveraging previous IP= P Fax project)
- IPP Everywhere Second Edition (multifunction)

Added initial draft = and prototype draft milestones for all these specs (but not
PWG Last Cal= l except for Requirements because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.
Comments?

Cheers,
- Ira


Ira McDona= ld (Musician / Software Architect)
Chair - Linux Foundation Open Printin= g WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=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. --20cf3054a547205215049cd27d21-- --===============2106325925== 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 --===============2106325925==-- From ipp-bounces@pwg.org Mon Feb 21 22:40:20 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E6993A67EC for ; Mon, 21 Feb 2011 22:40:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlA+lk1gg6qz for ; Mon, 21 Feb 2011 22:40:10 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 16BD93A677C for ; Mon, 21 Feb 2011 22:40:10 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 12B6979513; Tue, 22 Feb 2011 01:40:41 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 44A5C794D4 for ; Tue, 22 Feb 2011 01:40:28 -0500 (EST) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id B1F77D10609E; Mon, 21 Feb 2011 22:40:28 -0800 (PST) X-AuditID: 11807134-b7c40ae000006cb9-84-4d635a5b921c Received: from [17.151.68.241] (Unknown_Domain [17.151.68.241]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 89.AE.27833.C5A536D4; Mon, 21 Feb 2011 22:40:28 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1203) From: Michael Sweet In-Reply-To: Date: Mon, 21 Feb 2011 22:40:28 -0800 Message-Id: <17E0D491-DFEC-4615-A471-9D36EF59DE07@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1203) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Revised IPP Everywhere Charter (21 February 2011) 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="===============1202777050==" 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: 12B6979513.A9B90 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1202777050== Content-Type: multipart/alternative; boundary="Apple-Mail=_88898233-1E06-4FCD-B0E4-C8861E0C2ACF" --Apple-Mail=_88898233-1E06-4FCD-B0E4-C8861E0C2ACF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Feb 21, 2011, at 2:36 PM, Ira McDonald wrote: > Hi, >=20 > I've just posted a new IPP Everywhere Project charter at: >=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110221.pdf / = doc > - line numbers and redlines >=20 > Major revision that adds all of the following specs: >=20 > - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-= track) > - LDAP Printer Schema (IETF informational) > - PWG Raster (w/ IANA MIME type registration) > - IPP Everywhere First Edition (printing) - clarified scope as printing o= nly > - IPP Scan Service=20 > - IPP System Control Service > - IPP Fax Service (leveraging previous IPP Fax project) > - IPP Everywhere Second Edition (multifunction) >=20 > Added initial draft and prototype draft milestones for all these specs (b= ut not > PWG Last Call except for Requirements because prototyping may change them= ). >=20 > Revised many milestone dates - Bill - please check them for plausibility. >=20 > Comments? Lines 27-30: Change to read: Multifunction devices supporting network scan, fax, and other imaging servi= ces are now common and have similar discovery, driver, and document format = issues. Extending the IPP printing model to support these multifunction ima= ging services and leverage the existing widespread IPP support in multifunc= tion devices is an important long term goal for this project as well. Lines 34-36: Remove (no longer have a separate requirements document) Lines 39-40: Replace the reference to IPP Everywhere Requirements with "def= ine a small set of new IPP Job and Printer operations and attributes to sup= port driverless and mobile printing." Lines 43-44: "to always starts TLS first (before HTTP session layer)" shoul= d be "to always start TLS first before the HTTP session layer" Line 51: The filename I've been using is wd-ippraster10-yyyymmdd Lines 120, 127: Drop REQ __________________________________________________ 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. --Apple-Mail=_88898233-1E06-4FCD-B0E4-C8861E0C2ACF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On Feb 21, 2011,= at 2:36 PM, Ira McDonald wrote:
Hi,

= I've just posted a new IPP Everywhere Project charter at:

ft= p://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110221.pdf / = doc
- line numbers and redlines

Major revision that adds all of the foll= owing specs:

- IPP over HTTPS Transport Binding and 'ipps' URI Schem= e (IETF standards-track)
- LDAP Printer Schema (IETF informational)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edi= tion (printing) - clarified scope as printing only
- IPP Scan Service - IPP System Control Service
- IPP Fax Service (leveraging previous IP= P Fax project)
- IPP Everywhere Second Edition (multifunction)

Added initial draft = and prototype draft milestones for all these specs (but not
PWG Last Cal= l except for Requirements because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.
Comments?

Lines 27-30: Chan= ge to read:

Multifun= ction devices supporting network scan, fax, and other imaging services are = now common and have similar discovery, driver, and document format issues.&= nbsp;Extending the IPP printing model to support these multifunction imagin= g services and leverage the existing widespread IPP support in mu= ltifunction devices is an important long term goal for this project as= well.

Lines 34-36: Remove (no longer= have a separate requirements document)

Lines 39-4= 0: Replace the reference to IPP Everywhere Requirements with "define a smal= l set of new IPP Job and Printer operations and attributes to support drive= rless and mobile printing."

Lines 43-44: "to alway= s starts TLS first (before HTTP session layer)" should be "to always sta= rt TLS first before the HTTP session layer"

=
Line 51: The filename I've been using is wd-ippraster10-yyyymmdd
=

Lines 120, 127: Drop REQ


<= /div>
__________________________________________________
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. --Apple-Mail=_88898233-1E06-4FCD-B0E4-C8861E0C2ACF-- --===============1202777050== 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 --===============1202777050==-- From ipp-bounces@pwg.org Tue Feb 22 08:39:29 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 025E33A6946 for ; Tue, 22 Feb 2011 08:39:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HqvFYx3X88M8 for ; Tue, 22 Feb 2011 08:39:27 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A207F3A6942 for ; Tue, 22 Feb 2011 08:39:27 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A093B79519; Tue, 22 Feb 2011 11:39:56 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 7722A794D5 for ; Tue, 22 Feb 2011 11:39:44 -0500 (EST) Received: by fxm17 with SMTP id 17so3167252fxm.5 for ; Tue, 22 Feb 2011 08:39:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=Dw2TYO0z9xNfIQrVj18DpmYzaQvdZhNM1xlqmSSpnH4=; b=vhRVDaYG+adui/95ww14coc3eVbUmHHjA+cPtDYYTfv/XPDuedktoW9DqYWdSrGe/+ 4sCup23VPLFwfGrrejmAMH+yE5TrIYR59OUOTrGWJ4dQFc81DYFwYvh5CwlhWYj3m9EV OQLxAu9Of9yLWsm+lxP/+jzVZrtfO63OkuPtQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Qz53kqtNsr3U32R4kr2LnVXRad6TZ5RTU3FHa44bu3MfEh/mJNBa4WkM1P2ZDvYyEC 2n3GUmRs/na518N4QEXHNW/5/P7LFdNkLfDLtcroag+d7MeK4lMNlnR2Ws+dKaNZMviG XGAwXbg/Zc5nQ+37Puw6ejTYDycp3u/sec5/M= MIME-Version: 1.0 Received: by 10.223.103.12 with SMTP id i12mr3723277fao.43.1298392722718; Tue, 22 Feb 2011 08:38:42 -0800 (PST) Received: by 10.223.78.132 with HTTP; Tue, 22 Feb 2011 08:38:41 -0800 (PST) Date: Tue, 22 Feb 2011 11:38:41 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Second revised IPP Everywhere Charter (22 February 2011) 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="===============0746075253==" 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: A093B79519.AA7C7 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0746075253== Content-Type: multipart/alternative; boundary=20cf3054a547044caf049ce19df1 --20cf3054a547044caf049ce19df1 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just posted a *second* draft of our new IPP Everywhere Project charter at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110222.pdf / doc - line numbers and redlines All of Mike Sweet's suggested changes last night have been made. Major revision that *deletes* the following spec: - IPP Everywhere Requirements - to be included in each spec Major revision that *adds* all of the following specs: - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-track) - LDAP Printer Schema (IETF informational) - PWG Raster (w/ IANA MIME type registration) - IPP Everywhere First Edition (printing) - clarified scope as printing only - IPP Scan Service - IPP System Control Service - IPP Fax Service (leveraging previous IPP Fax project) - IPP Everywhere Second Edition (multifunction) Added initial draft and prototype draft milestones for all these specs (but not PWG Last Call because prototyping may change them). Revised many milestone dates - Bill - please check them for plausibility. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --20cf3054a547044caf049ce19df1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've just posted a second draft of our new IPP Everyw= here Project charter at:

ftp://ftp.pwg.org= /pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110222.pdf / doc
- line numbers and redlines

All of Mike Sweet's suggested change= s last night have been made.

Major revision that deletes the = following spec:

- IPP Everywhere Requirements - to be included in ea= ch spec

Major revision that adds all of the following specs:

- IP= P over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standard= s-track)
- LDAP Printer Schema (IETF informational)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edi= tion (printing) - clarified scope as printing only
- IPP Scan Service - IPP System Control Service
- IPP Fax Service (leveraging previous IP= P Fax project)
- IPP Everywhere Second Edition (multifunction)


Added initial dr= aft and prototype draft milestones for all these specs (but not
PWG Last= Call because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.
Comments?

Cheers,
- Ira


Ira McDona= ld (Musician / Software Architect)
Chair - Linux Foundation Open Printin= g WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=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. --20cf3054a547044caf049ce19df1-- --===============0746075253== 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 --===============0746075253==-- From pwg-announce-bounces@pwg.org Tue Feb 22 23:39:49 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A9B23A67A2 for ; Tue, 22 Feb 2011 23:39:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.298 X-Spam-Level: X-Spam-Status: No, score=-101.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSmRrnLSRnDf for ; Tue, 22 Feb 2011 23:39:48 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 6E4F63A677C for ; Tue, 22 Feb 2011 23:39:48 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BC0887951E; Wed, 23 Feb 2011 02:40:15 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by pwg.org (Postfix) with ESMTP id 1A14B79510 for ; Wed, 23 Feb 2011 02:40:03 -0500 (EST) Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta13.emeryville.ca.mail.comcast.net with comcast id BKeV1g0011bwxycADKg3YQ; Wed, 23 Feb 2011 07:40:03 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta18.emeryville.ca.mail.comcast.net with comcast id BKg01g00F548CT48eKg2a1; Wed, 23 Feb 2011 07:40:03 +0000 From: "William Wagner" To: References: <000001cbd215$b735be90$25a13bb0$@net> In-Reply-To: Date: Wed, 23 Feb 2011 02:39:49 -0500 Message-ID: <001001cbd32c$db5c9290$9215b7b0$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcvR8ebOoN4M9AVCRdiFyWyNcOkL7gAIZhAwAAFAkQAARGo3IA== Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document 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="===============1567177069==" 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: BC0887951E.ACB6A X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============1567177069== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CBD302.F2868A90" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0011_01CBD302.F2868A90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Recognizing that the documents posted for PWG last call of the MFD Model and Common Semantics specification suffered from some formatting difficulties, we have corrected these problems and reposted the documents at ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.pdf and ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.docx We would appreciate your review of the specification. Thank you. Bill Wagner -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_0011_01CBD302.F2868A90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Recognizing that the documents posted for PW= G last call of the MFD Model and Common Semantics specification suffered fr= om some formatting difficulties, we have corrected these problems and repos= ted the documents at

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmod= el10-20110222.pdf  and

<= span style=3D'font-size:14.0pt;color:#1F497D'>ftp://ftp.pwg.org/pub/pwg/mfd/w= d/wd-mfdmodel10-20110222.docx

 

We wo= uld appreciate your review of the specification.

 =

Thank you.

 

Bill Wagner


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0011_01CBD302.F2868A90-- --===============1567177069== 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 --===============1567177069==-- From pwg-announce-bounces@pwg.org Wed Feb 23 07:14:26 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56C3A3A6A14 for ; Wed, 23 Feb 2011 07:14:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJ0FVCqn1lEB for ; Wed, 23 Feb 2011 07:14:25 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 077573A68F3 for ; Wed, 23 Feb 2011 07:14:24 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 7C5C779529; Wed, 23 Feb 2011 10:14:56 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-gw.okidata.com (mail-gw.okidata.com [207.77.135.74]) by pwg.org (Postfix) with ESMTP id 9239C7952B; Wed, 23 Feb 2011 10:14:44 -0500 (EST) In-Reply-To: <001001cbd32c$db5c9290$9215b7b0$@net> To: "William Wagner" Subject: Re: [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document MIME-Version: 1.0 X-KeepSent: B37DC85B:495E8264-85257840:00538099; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 6.5.6 CCH4 June 18, 2008 Message-ID: From: Nancy.Chen@okidata.com Date: Wed, 23 Feb 2011 10:14:43 -0500 X-MIMETrack: Serialize by Router on ODA-SMTP-MTA/OKIDATA/OKI_DATA_CORP/OKI_ELECTRIC/US(Release 8.5.1FP5|September 29, 2010) at 02/23/2011 10:14:44 AM Content-Type: multipart/mixed; boundary="=_mixed 0053BF4B85257840_=" X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org, pwg-announce-bounces@pwg.org X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 7C5C779529.AD5AD X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --=_mixed 0053BF4B85257840_= Content-Type: multipart/alternative; boundary="=_alternative 0053BF5685257840_=" --=_alternative 0053BF5685257840_= Content-Type: text/plain; charset="US-ASCII" Bill, Would you please provide the version with change marks so that we don't have to review every from scratch? Thanks, -Nancy "William Wagner" Sent by: pwg-announce-bounces@pwg.org 02/23/2011 02:39 AM To cc Subject [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document Recognizing that the documents posted for PWG last call of the MFD Model and Common Semantics specification suffered from some formatting difficulties, we have corrected these problems and reposted the documents at ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.pdf and ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.docx We would appreciate your review of the specification. Thank you. Bill Wagner -- 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. --=_alternative 0053BF5685257840_= Content-Type: text/html; charset="US-ASCII"
Bill,

Would you please provide the  version with change marks so that we don't have to review every from scratch?

Thanks,
-Nancy



"William Wagner" <wamwagner@comcast.net>
Sent by: pwg-announce-bounces@pwg.org

02/23/2011 02:39 AM

To
<pwg-announce@pwg.org>
cc
Subject
[Pwg-Announce] MFD Model and Common Semantics Last Call -Updated        Document




Recognizing that the documents posted for PWG last call of the MFD Model and
Common Semantics specification suffered from some formatting difficulties,
we have corrected these problems and reposted the documents at

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.pdf  and

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.docx



We would appreciate your review of the specification.



Thank you.



Bill Wagner


--
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. --=_alternative 0053BF5685257840_=-- --=_mixed 0053BF4B85257840_= Content-Type: text/html; name="C.htm" Content-Disposition: attachment; filename="C.htm" Content-Transfer-Encoding: quoted-printable

Recognizing that the documents posted for PW= G last call of the MFD Model and Common Semantics specification suffered fr= om some formatting difficulties, we have corrected these problems and repos= ted the documents at

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmod= el10-20110222.pdf  and

<= span style=3D'font-size:14.0pt;color:#1F497D'>ftp://ftp.pwg.org/pub/pwg/mfd/w= d/wd-mfdmodel10-20110222.docx

 

We wo= uld appreciate your review of the specification.

 =

Thank you.

 

Bill Wagner


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. = --=_mixed 0053BF4B85257840_= 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 --=_mixed 0053BF4B85257840_=-- From pwg-announce-bounces@pwg.org Wed Feb 23 08:42:17 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C68CA3A68C5 for ; Wed, 23 Feb 2011 08:42:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+OgsoqJq5go for ; Wed, 23 Feb 2011 08:42:16 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id BE1273A6892 for ; Wed, 23 Feb 2011 08:42:16 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C1D3E79535; Wed, 23 Feb 2011 11:42:49 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id BCBF77952B for ; Wed, 23 Feb 2011 11:42:36 -0500 (EST) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id CA8FCD3FDD58 for ; Wed, 23 Feb 2011 08:42:35 -0800 (PST) X-AuditID: 11807130-b7b3cae00000405d-30-4d6538f949a8 Received: from [17.153.106.178] (Unknown_Domain [17.153.106.178]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 38.05.16477.AF8356D4; Wed, 23 Feb 2011 08:42:35 -0800 (PST) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Feb 2011 08:42:32 -0800 To: pwg-announce@pwg.org Message-Id: <752276DB-B4A4-4D41-8416-03FD7C559562@apple.com> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] Updated standard template posted X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: C1D3E79535.ACEDF X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org All, I have posted an update to the Word templates for PWG standards at: ftp://ftp.pwg.org/pub/pwg/general/templates/wd-template.dot ftp://ftp.pwg.org/pub/pwg/general/templates/wd-template.dotx The update corrects a bunch of font/formatting issues, adds example figure = and table entries along with a list of figures and tables, and adds some su= bsections that were missing in the boilerplate text. Please let me know if you notice any other issues... ________________________________________________________________________ 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. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From pwg-announce-bounces@pwg.org Wed Feb 23 08:59:12 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B07E3A68F2 for ; Wed, 23 Feb 2011 08:59:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.623 X-Spam-Level: X-Spam-Status: No, score=-101.623 tagged_above=-999 required=5 tests=[AWL=0.975, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPLzmTHOYsx5 for ; Wed, 23 Feb 2011 08:59:11 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id CC3F73A67A1 for ; Wed, 23 Feb 2011 08:59:10 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 804E679539; Wed, 23 Feb 2011 11:59:43 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by pwg.org (Postfix) with ESMTP id 6995B79539 for ; Wed, 23 Feb 2011 11:59:25 -0500 (EST) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta13.emeryville.ca.mail.comcast.net with comcast id BUxi1g0041GXsucADUzQUA; Wed, 23 Feb 2011 16:59:24 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta07.emeryville.ca.mail.comcast.net with comcast id BUzM1g00y548CT48UUzNY2; Wed, 23 Feb 2011 16:59:24 +0000 From: "William Wagner" To: References: <001001cbd32c$db5c9290$9215b7b0$@net> In-Reply-To: Subject: RE: [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document Date: Wed, 23 Feb 2011 11:59:10 -0500 Message-ID: <005701cbd37a$ff93d3a0$febb7ae0$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcvTbGcbOlvhoZ8cSfqfzLSDVHyYEwACu70A Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org, pwg-announce-bounces@pwg.org 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="===============0386265319==" 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: 804E679539.AD66B X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============0386265319== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01CBD351.16BDCBA0" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0058_01CBD351.16BDCBA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sorry Nancy. This document already stresses MS Word to the point of instability. Allowing change tracking not only results in a basically unreadable text, the results are unpredictable. I appreciate that this is a complicated draft to review. This reason and the MS Word problems were why some sections have been reviewed separately over the past few years (subunits and operations chapters). I did provide a list of the last changes made, pointing to the comments prompting those changes. This was distributed on the MFD list and I have posted it on the FTP site at ftp://ftp.pwg.org/pub/pwg/mfd/white/MFD_Model_Last_Call_changes_2-22-11.docx . Thanks, Bill Wagner From: Nancy.Chen@okidata.com [mailto:Nancy.Chen@okidata.com] Sent: Wednesday, February 23, 2011 10:15 AM To: William Wagner Cc: pwg-announce@pwg.org; pwg-announce-bounces@pwg.org Subject: Re: [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document Bill, Would you please provide the version with change marks so that we don't have to review every from scratch? Thanks, -Nancy "William Wagner" Sent by: pwg-announce-bounces@pwg.org 02/23/2011 02:39 AM To cc Subject [Pwg-Announce] MFD Model and Common Semantics Last Call -Updated Document Recognizing that the documents posted for PWG last call of the MFD Model and Common Semantics specification suffered from some formatting difficulties, we have corrected these problems and reposted the documents at ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.pdf and ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.docx We would appreciate your review of the specification. Thank you. Bill Wagner -- 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. ------=_NextPart_000_0058_01CBD351.16BDCBA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Sorry Nan= cy. This document already stresses MS Word to the point of instability. &nb= sp;Allowing change tracking not only results in a basically unreadable text= , the results are unpredictable.

=  

I appreciate= that this is a complicated draft to review. This reason and the MS Word pr= oblems were why some sections have been reviewed separately over the past f= ew years (subunits and operations chapters).  I did provide a list of = the last changes made, pointing to the comments prompting those changes. Th= is was distributed on the MFD list and I have posted it on the FTP site at =

ftp://ftp.p= wg.org/pub/pwg/mfd/white/MFD_Model_Last_Call_changes_2-22-11.docx.

 

Thanks, Bill Wagner

 

=

 =

 

From: Nancy.Chen@okidata.com [mailto:Nancy.Chen@okidata.com] <= br>Sent: Wednesday, February 23, 2011 10:15 AM
To: William= Wagner
Cc: pwg-announce@pwg.org; pwg-announce-bounces@pwg.orgSubject: Re: [Pwg-Announce] MFD Model and Common Semantics Last Cal= l -Updated Document

&n= bsp;


Bill, <= br>
Wo= uld you please provide the  version with change marks so that we don't= have to review every from scratch?

Thanks,
-Nancy

<= br>

=

"Wil= liam Wagner" <wamwagner@comcast.net>
Sent by: pwg-announce-bou= nces@pwg.org

02/23/2011 02:39 AM

= <= td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>

Subject

To

<pwg-announce@pwg.org>

cc

[Pwg-Announce= ] MFD Model and Common Semantics Last Call -Updated       &n= bsp;Document

 



<= tt>Recognizing that the documents posted f= or PWG last call of the MFD Model and
Common Semantics specification suf= fered from some formatting difficulties,
we have corrected thes= e problems and reposted the documents at

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-201102= 22.pdf  and

ftp://ftp.p= wg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110222.docx



We would appreciate your review of the specif= ication.



Thank you.<= /span>
<= /span>


Bill Wagner

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


_______________________________________________
pwg-ann= ounce 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. ------=_NextPart_000_0058_01CBD351.16BDCBA0-- --===============0386265319== 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 --===============0386265319==-- From ipp-bounces@pwg.org Wed Feb 23 13:48:57 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FF9D3A692B for ; Wed, 23 Feb 2011 13:48:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LcC3UF1jx0gr for ; Wed, 23 Feb 2011 13:48:56 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id EEDD33A67F1 for ; Wed, 23 Feb 2011 13:48:55 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 51A6C79553; Wed, 23 Feb 2011 16:49:31 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id BF9597954F for ; Wed, 23 Feb 2011 16:49:16 -0500 (EST) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 0A8C0D17AEB2 for ; Wed, 23 Feb 2011 13:49:16 -0800 (PST) X-AuditID: 11807130-b7b3cae00000405d-de-4d6580db39d3 Received: from da0704a-dhcp214.apple.com (da0704a-dhcp214.apple.com [17.197.43.214]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id 55.1A.16477.BD0856D4; Wed, 23 Feb 2011 13:49:16 -0800 (PST) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 23 Feb 2011 13:49:15 -0800 To: ipp@pwg.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Updated PWG Raster draft posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: 51A6C79553.AA167 X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted an updated PWG Raster draft at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110223.doc ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110223.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110223-rev.pdf The latter is the redlined version of the 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. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From pwg-announce-bounces@pwg.org Thu Feb 24 11:28:16 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8C5A3A6807 for ; Thu, 24 Feb 2011 11:28:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYWe8nTf3rUg for ; Thu, 24 Feb 2011 11:28:14 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 754083A6802 for ; Thu, 24 Feb 2011 11:28:14 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2618E79576; Thu, 24 Feb 2011 14:28:42 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from bware2.sdsamerica.net (bware2.sdsamerica.net [206.67.236.192]) by pwg.org (Postfix) with ESMTP id 25A7279575 for ; Thu, 24 Feb 2011 14:28:28 -0500 (EST) From: Ron Nevo To: "pwg-announce@pwg.org" Date: Thu, 24 Feb 2011 14:30:22 -0500 Thread-Topic: Samsung has reviewed the MFD Model and Common Semantics and has no comments Thread-Index: AcvUK1yui7kCKhjvTUqE2D2vazTHtQALefIA Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Received-SPF: none X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] FW: Samsung has reviewed the MFD Model and Common Semantics and has no comments 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="===============1577256170==" 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: 2618E79576.ADF78 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1577256170== Content-Language: en-US Content-Type: multipart/related; boundary="_004_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_"; type="multipart/alternative" --_004_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_ Content-Type: multipart/alternative; boundary="_000_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_" --_000_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thank You, [cid:image001.jpg@01CBD401.73D5FA50] Ron Nevo | Senior Manager | Product Marketing Solutions, Information Security, Standards and Certifications Co-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.5945 samsung.com/business P Save trees! Print this e-mail only if necessary. For more information about Samsung's sustainability initiatives, please vis= it samsung.com/green ---------------------------------------------------------------------------= --------------------------------- This email may contain information that is confidential or privileged. If y= ou have received this is error, please delete it without copying or forwarding and = notify the sender of the error by reply email or call Samsung at (201) 229-4000. Than= k you. From: Ron Nevo Sent: Thursday, February 24, 2011 9:02 AM To: 'mfd@pwg.org' Subject: Samsung has reviewed the MFD Model and Common Semantics and has no= comments Thank You, [cid:image001.jpg@01CBD401.73D5FA50] Ron Nevo | Senior Manager | Product Marketing Solutions, Information Security, Standards and Certifications Co-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.5945 samsung.com/business P Save trees! Print this e-mail only if necessary. For more information about Samsung's sustainability initiatives, please vis= it samsung.com/green ---------------------------------------------------------------------------= --------------------------------- This email may contain information that is confidential or privileged. If y= ou have received this is error, please delete it without copying or forwarding and = notify the sender of the error by reply email or call Samsung at (201) 229-4000. Than= k you. --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --_000_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

Thank You,

 

3Dsamsung

Ron Nevo | Senior Manager | Product Mar= keting

Solutions, Information Security, Standards and Certifi= cations

Co-Chair IEEE/ISTO Printer Working Group-Cloud Imaging=

Samsung Electronics America, Inc.

Enterprise B= usiness Division

=

 = ;

85 Challenger Road | Ridgefield Park, NJ 07660

P 201.329.6231<= /span>

C 201.220.5945
samsung.com/business

 

P  <= span lang=3DEN-GB style=3D'font-size:9.0pt;color:#006600'>Save trees! Print= this e-mail only if necessary.

For more information about= Samsung's sustainability initiatives, please visit samsung.com/green<= b>

 

-------------------------------------------------------------------------= -----------------------------------

 

<= span style=3D'font-size:8.0pt;color:gray'>This email may contain informatio= n that is confidential or privileged. If you have
received this is erro= r, please delete it without copying or forwarding and notify the
sender= of the error by reply email or call Samsung at (201) 229-4000.  Thank= you.

 

&nbs= p;

From: Ron Nevo
S= ent: Thursday, February 24, 2011 9:02 AM
To: 'mfd@pwg.org'Subject: Samsung has reviewed the MFD Model and Common Semantics an= d has no comments

 

 

 

Thank You,

 

3Dsamsung

Ron Nevo | Senior Manager | Product Marketing=

Solutions, Information Security, Standards and Certifications

Co-Chair IEEE/ISTO Printer Working Group-Cloud Imaging=

Samsung Electronics America, Inc.

Enterprise Business Div= ision

 

85 = Challenger Road | Ridgefield Park, NJ 07660

P 201.329.6231

C 201.220.5945
<= a href=3D"http://www.samsung.com/business">samsung.com/business

 

P<= /b>  Save trees! Print this e-mail only if n= ecessary.

For more information about Samsung's sustainabilit= y initiatives, please visit samsung.com/green

 

--------------------------------------------------------------= ----------------------------------------------

 

This email may contain= information that is confidential or privileged. If you have
received t= his is error, please delete it without copying or forwarding and notify the=
sender of the error by reply email or call Samsung at (201) 229-4000.&= nbsp; Thank you.
<= /o:p>

 

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --_000_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_-- --_004_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_ Content-Type: image/jpeg; name="image001.jpg" Content-Description: image001.jpg Content-Disposition: inline; filename="image001.jpg"; size=2235; creation-date="Thu, 24 Feb 2011 14:28:27 GMT"; modification-date="Thu, 24 Feb 2011 14:28:27 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 --_004_EC44E463C7BF714DBE6A6B235A5AED840169C48DEESEAEXseasamsu_-- --===============1577256170== 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 --===============1577256170==-- From pwg-announce-bounces@pwg.org Fri Feb 25 06:30:30 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A361E3A69CF for ; Fri, 25 Feb 2011 06:30:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waiXPL7oYAO7 for ; Fri, 25 Feb 2011 06:30:29 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 61E2F3A67EC for ; Fri, 25 Feb 2011 06:30:29 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D713B79581; Fri, 25 Feb 2011 09:31:05 -0500 (EST) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 20D2079580 for ; Fri, 25 Feb 2011 09:30:50 -0500 (EST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArEFAAJMZ00Nl9IPgWdsb2JhbACCTJVcjhIVAQEWIiW9JIMYgkgEhRCKUQ X-IronPort-AV: E=Sophos;i="4.62,225,1297058400"; d="scan'208,217";a="13331268" Received: from usa7061gw002.na.xerox.net ([13.151.210.15]) by USA7109MR001.ACS-INC.COM with ESMTP; 25 Feb 2011 08:30:49 -0600 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 25 Feb 2011 06:30:31 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 25 Feb 2011 06:30:30 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Last Call for the MFD Model and Overall Semantics specification has succeeded Thread-Index: AcvU+I3mxyw0IJQQTd+SasNXoes2gg== From: "Zehler, Peter" To: X-OriginalArrivalTime: 25 Feb 2011 14:30:31.0118 (UTC) FILETIME=[8E191EE0:01CBD4F8] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] Last Call for the MFD Model and Overall Semantics specification has succeeded 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="===============0250224896==" 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: D713B79581.AD41A X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============0250224896== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBD4F8.8DCEB449" This is a multi-part message in MIME format. ------_=_NextPart_001_01CBD4F8.8DCEB449 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, The process required 9 responses to conclude the Last Call. We received 10 responses, 4 without comments and 6 with comments. Two more companies have said they will respond. Thank you to all those that took on the onerous task of reviewing such a large and complex specification. There is still time to submit comments. So if you have some please send them in. Thanks, Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CBD4F8.8DCEB449 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,<= /p>

The process required 9 responses to conclude the La= st Call.  We received 10 responses, 4 without comments and 6 with comm= ents.  Two more companies have said they will respond.  Thank you= to all those that took on the onerous task of reviewing such a large and c= omplex specification.  There is still time to submit comments.  S= o if you have some please send them in.

= Thanks,

Pete

 

 

Peter Zehler

Xerox Research Center Webster
E= mail: = Peter.Zehler@Xerox.com
<= /span>Voice: (585) 265-8755
FAX: (585) 265-7441
US= Mail: Peter Zehler

Xerox = Corp.
800 Phillips Rd.

M/S 128-25E
Webster NY, 14580-9701

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CBD4F8.8DCEB449-- --===============0250224896== 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 --===============0250224896==-- From ipp-bounces@pwg.org Fri Feb 25 15:41:31 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C1EE3A6A7F for ; Fri, 25 Feb 2011 15:41:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jI7tGOirdPIT for ; Fri, 25 Feb 2011 15:41:30 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 62E323A6A7E for ; Fri, 25 Feb 2011 15:41:30 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E41C57958A; Fri, 25 Feb 2011 18:42:09 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 50BF079586 for ; Fri, 25 Feb 2011 18:41:55 -0500 (EST) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out3.apple.com (Postfix) with ESMTP id 48C03D21031C for ; Fri, 25 Feb 2011 15:41:54 -0800 (PST) X-AuditID: 11807130-b7b3cae00000405d-c8-4d683e415944 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id E0.27.16477.24E386D4; Fri, 25 Feb 2011 15:41:54 -0800 (PST) From: Michael Sweet Date: Fri, 25 Feb 2011 15:41:53 -0800 To: ipp@pwg.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1203) X-Mailer: Apple Mail (2.1203) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] (Very) Draft IPP Job and Printer Extensions - Set 3 posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1373579617==" 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: E41C57958A.AA0AB X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1373579617== Content-Type: multipart/alternative; boundary="Apple-Mail=_E2669337-1681-4A4D-9277-8E43D2A57AFC" --Apple-Mail=_E2669337-1681-4A4D-9277-8E43D2A57AFC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii All, I have just uploaded an initial draft of the IPP Job and Printer Extensions= - Set 3 (JPS3) specification containing most of the combined additions we = have discussed for IPP Everywhere: ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.docx ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf There is still a bunch of stuff I need to fill in, and I noticed (just afte= r uploading) that I forgot to include the job-uuid, printer-uuid, and subsc= ription-uuid attributes, but otherwise it should be relatively complete fro= m the "this is what we need to work on" point of view. Comments, etc. welcome. For possible discussion at Monday's IPP telecon... ________________________________________________________________________ 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. --Apple-Mail=_E2669337-1681-4A4D-9277-8E43D2A57AFC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii All,

I = have just uploaded an initial draft of the IPP Job and Printer Extensions -= Set 3 (JPS3) specification containing most of the combined additions we ha= ve discussed for IPP Everywhere:


There is = still a bunch of stuff I need to fill in, and I noticed (just after uploadi= ng) that I forgot to include the job-uuid, printer-uuid, and subscription-u= uid attributes, but otherwise it should be relatively complete from the "th= is is what we need to work on" point of view.

Comm= ents, etc. welcome. For possible discussion at Monday's IPP telecon...

_______________________________________________________________= _________
Michael Sweet, Senior Printing System Engineer, PWG Cha= ir






--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Apple-Mail=_E2669337-1681-4A4D-9277-8E43D2A57AFC-- --===============1373579617== 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 --===============1373579617==-- From ipp-bounces@pwg.org Fri Feb 25 16:24:33 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9D513A6A8C for ; Fri, 25 Feb 2011 16:24:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3CnyrAcbXgUj for ; Fri, 25 Feb 2011 16:24:32 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 14AA13A6A8B for ; Fri, 25 Feb 2011 16:24:32 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 96F9A79590; Fri, 25 Feb 2011 19:25:11 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 303857958F for ; Fri, 25 Feb 2011 19:25:00 -0500 (EST) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id BBFECD211DA7 for ; Fri, 25 Feb 2011 16:24:59 -0800 (PST) X-AuditID: 1180711d-b7c12ae00000228a-98-4d68484bdb6f Received: from [17.153.40.72] (Unknown_Domain [17.153.40.72]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 71.15.08842.058486D4; Fri, 25 Feb 2011 16:24:59 -0800 (PST) Subject: Re: [IPP] (Very) Draft IPP Job and Printer Extensions - Set 3 posted Mime-Version: 1.0 (Apple Message framework v1203) From: Michael Sweet In-Reply-To: Date: Fri, 25 Feb 2011 16:24:41 -0800 Message-Id: <41D839ED-0935-40E6-B530-9FF015D364CB@apple.com> References: To: Michael Sweet X-Mailer: Apple Mail (2.1203) X-Brightmail-Tracker: AAAAAA== 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="===============2115211664==" 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: 96F9A79590.AA978 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2115211664== Content-Type: multipart/alternative; boundary="Apple-Mail=_505E4B41-ED47-411F-9905-2CAC9D35D56A" --Apple-Mail=_505E4B41-ED47-411F-9905-2CAC9D35D56A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii All, Sorry, the correct URLs are: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf On Feb 25, 2011, at 3:41 PM, Michael Sweet wrote: > All, >=20 > I have just uploaded an initial draft of the IPP Job and Printer Extensio= ns - Set 3 (JPS3) specification containing most of the combined additions w= e have discussed for IPP Everywhere: >=20 > ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.docx > ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf >=20 > There is still a bunch of stuff I need to fill in, and I noticed (just af= ter uploading) that I forgot to include the job-uuid, printer-uuid, and sub= scription-uuid attributes, but otherwise it should be relatively complete f= rom the "this is what we need to work on" point of view. >=20 > Comments, etc. welcome. For possible discussion at Monday's IPP telecon... >=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=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. > _______________________________________________ > 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. --Apple-Mail=_505E4B41-ED47-411F-9905-2CAC9D35D56A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
All,

Sorry, the correct URLs are:

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.docx<= /a>
    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinter= ext3v10-20110225.pdf

On Feb 25, 2011, at 3:41 PM, Michael = Sweet wrote:
Al= l,

I have just uploaded an initial draft of the IPP Job = and Printer Extensions - Set 3 (JPS3) specification containing most of the = combined additions we have discussed for IPP Everywhere:

=
There is still a bunch of stuff I need to fill in, and I not= iced (just after uploading) that I forgot to include the job-uuid, printer-= uuid, and subscription-uuid attributes, but otherwise it should be relative= ly complete from the "this is what we need to work on" point of view.
=

Comments, etc. welcome. For possible discussion at Mond= ay's IPP telecon...

=
_________________________________________= _______________________________
Michael Sweet, Senior Printing Sy= stem 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
<= br>
_______________________________________= ___________
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. --Apple-Mail=_505E4B41-ED47-411F-9905-2CAC9D35D56A-- --===============2115211664== 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 --===============2115211664==-- From ipp-bounces@pwg.org Fri Feb 25 18:24:08 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 431303A6ACA for ; Fri, 25 Feb 2011 18:24:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vCfJjT3YP2Ot for ; Fri, 25 Feb 2011 18:24:07 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id CAAFB3A6ABA for ; Fri, 25 Feb 2011 18:24:06 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A84C479590; Fri, 25 Feb 2011 21:24:47 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 13F567958A for ; Fri, 25 Feb 2011 21:24:35 -0500 (EST) Received: by fxm17 with SMTP id 17so2760322fxm.5 for ; Fri, 25 Feb 2011 18:24:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=VGrWFGtXbtnAUbkQLwERodc5bAsemg+hpyMw2Q2LIsQ=; b=fehwPScTmi+Lpx5XD7q/qGfZh6hA+s91WX8xvVC46jGQukQD1+40vzrp93JGObprnx Zq7EquzvdjxHa2RwyY/Qa5PdMbWA6n8L2tIV33TBAUrcbJvLnDsloJzYn5XrXgqzu1oD M/n6uWYlo5CVeuLTKNjRyRuXUZhAayk3T+NBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fX5Fk9HUXHXL/F6CpWN8WmTeOu7JcsLjNcPJKa+q09cKe8WJq3/WJCaRu2sOt4vfS/ ZLtH2a7JSyRQFEXIiPmtrNlPcrMG1hRMoCb0KwmIXK3vB4DheXgMJsXHVgtcH3rlA/eK 3pV68MnV2YbiWKZsjYQ3YBnzdUOrFu7xPLdnM= MIME-Version: 1.0 Received: by 10.223.101.129 with SMTP id c1mr3473240fao.25.1298683509302; Fri, 25 Feb 2011 17:25:09 -0800 (PST) Received: by 10.223.78.132 with HTTP; Fri, 25 Feb 2011 17:25:09 -0800 (PST) Date: Fri, 25 Feb 2011 20:25:09 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - NEW TIME - 1pm EDT Monday 28 February 2011 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="===============0346058263==" 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: A84C479590.AA220 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0346058263== Content-Type: multipart/alternative; boundary=20cf30433ef83f657b049d2551aa --20cf30433ef83f657b049d2551aa Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be next Monday. Monday 28 February 10-11am US PST / 1-2pm US EST Call-in toll-free number (US/Canada): 1-866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 (Primary) Call-in toll number (US/Canada): 1-408-856-9570 (Backup) Attendee Access Code: *******# Attendee ID Code: # (empty) If you need the Attendee Access code, please email me a request. *** Main Objective - Review IPP Everywhere Charter and JPS3 *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20110214.pdf (3) Status of IPP/2.0 Second Edition - PWG Approved (Ira) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20110110.pdf (PWG Candidate Standard 5100.12-2011- minor edits needed) (4) Review of draft IPP Everywhere Charter (Mike/Ira) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110222.pdf (added many specs and IPP Everywhere Second Edition for multifunction) (5) Review of IPP JPS3 draft (Mike) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf (6) Discussion of IPP Everywhere (Mike/Ira)* * - *http://pwg-wiki.wikispaces.com/IPP+Everywhere* - Ira to revise IPPS URI scheme - Andrew/Ira to publish first draft of IPP Scan - other new requirements/features? (7) Next Steps - IPP WG teleconference Monday 14 March Cheers, - Ira (IPP WG Co-Chair) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --20cf30433ef83f657b049d2551aa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Our next IPP WG call will be next Monday.

=A0Monday 28 February 10-11am US PST / 1-2pm US EST

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

=A0Attendee Access Code: *******#
=A0Attendee ID Code: # (empty)

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


*** Main Objective - Review IPP Everywhere Charter and JPS3 ***

Agenda:

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

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

(3) Status of IPP/2.0 Second Edition - PWG Approved (Ira)<= br>=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-= ipp20-20110110.pdf
=A0 =A0=A0 (PWG Candidate Standard 5100.12-2011- minor edits needed)
(4) Review of draft IPP Everywhere Charter (Mike/Ira)
=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp= everywhere-charter-20110222.pdf
=A0=A0=A0=A0 (added many specs and IPP Everywhere Second Edition for multif= unction)

(5) Review of IPP JPS3 draft (Mike)
=A0=A0 - ftp://ftp.pwg.org/pub/pw= g/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf

(6) Discussi= on of IPP Everywhere (Mike/Ira)http://pwg-wiki.wikispaces.com/IPP+Everywhere
=A0=A0 - Ira to revise IPPS URI scheme
=A0=A0 - Andrew/Ira to publish fi= rst draft of IPP Scan
=A0=A0 - other new requirements/features?

(7) Next Steps
=A0=A0 - IPP WG teleconference Monday 14 Mar= ch

Cheers,
- Ira (IPP WG Co-Chair)

Ira McDonald (Mus= ician / Software Architect)
Chair - Linux Foundation Open Printing WGCo-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desi= gnated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic<= /a>
http://sites.google.com/site/highnor= thinc
mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 S= aline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 2= 21=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. --20cf30433ef83f657b049d2551aa-- --===============0346058263== 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 --===============0346058263==-- From ipp-bounces@pwg.org Sat Feb 26 13:40:52 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C0C13A6816 for ; Sat, 26 Feb 2011 13:40:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1b5vDzDYVLwu for ; Sat, 26 Feb 2011 13:40:50 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 5021D3A6832 for ; Sat, 26 Feb 2011 13:40:50 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1EFA67958F; Sat, 26 Feb 2011 16:41:28 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 4F43779581 for ; Sat, 26 Feb 2011 16:41:14 -0500 (EST) Received: by fxm17 with SMTP id 17so3290687fxm.5 for ; Sat, 26 Feb 2011 13:41:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ALNeAfGcT8mi1cpRgMjt05mfhnf7INdQRb2Tlht9Ads=; b=IM6UYWA7kea2jZ89YlbYlJNfKJlNFGOxlC8o9RsupTSwugok/dPIXx5jfpiq6IeR5N 2FYmnKymClz+xeFthVx0LBGxNvq/n3udEC19IjpNHgRTL/mG8r5r7q8hHnTCycHi+zfS gdr3W1+gEh2v5/wVuXx6YEEphhjm8/uuLCtNE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wHHw/aJTc32+ZuDXjT9kK9uVznKw4JBLD0sPay5pR4UwGcNwy+JuKDZzomvbxZKr2y j9xtxjnFIYXgIoikp+V0tIrEQ9Tz09N72RNiHJ2eZL7sWlIkhHONB7DCqizJgW7hUccx NR/WCb5bA8tnvqjBYZCP+pFrFkTTH3YdMuICY= MIME-Version: 1.0 Received: by 10.223.104.71 with SMTP id n7mr4426422fao.120.1298756474245; Sat, 26 Feb 2011 13:41:14 -0800 (PST) Received: by 10.223.78.132 with HTTP; Sat, 26 Feb 2011 13:41:14 -0800 (PST) In-Reply-To: <41D839ED-0935-40E6-B530-9FF015D364CB@apple.com> References: <41D839ED-0935-40E6-B530-9FF015D364CB@apple.com> Date: Sat, 26 Feb 2011 16:41:14 -0500 Message-ID: Subject: Re: [IPP] (Very) Draft IPP Job and Printer Extensions - Set 3 posted 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="===============1384855960==" 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: 1EFA67958F.AB78B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1384855960== Content-Type: multipart/alternative; boundary=001636c5a8484c143b049d364e78 --001636c5a8484c143b049d364e78 Content-Type: text/plain; charset=ISO-8859-1 Hi Mike, Editorial - You didn't regenerate the Table of Contents from the template, so the TOC is useless for browsing the document. Editorial - I dislike this new references format - it's very different from IETF and W3C references and leaves out the important month and year of publication (which warns the reader to check for a newer version when it's an old RFC, etc.). Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Feb 25, 2011 at 7:24 PM, Michael Sweet wrote: > All, > > Sorry, the correct URLs are: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.docx > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf > > On Feb 25, 2011, at 3:41 PM, Michael Sweet wrote: > > All, > > I have just uploaded an initial draft of the IPP Job and Printer Extensions > - Set 3 (JPS3) specification containing most of the combined additions we > have discussed for IPP Everywhere: > > ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.docx > ftp://ftp.pwg.org/pub/ipp/wd/wd-ippjobprinterext3v10-20110225.pdf > > There is still a bunch of stuff I need to fill in, and I noticed (just > after uploading) that I forgot to include the job-uuid, printer-uuid, and > subscription-uuid attributes, but otherwise it should be relatively complete > from the "this is what we need to work on" point of view. > > Comments, etc. welcome. For possible discussion at Monday's IPP telecon... > > ________________________________________________________________________ > 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 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --001636c5a8484c143b049d364e78 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Mike,

Editorial - You didn't regenerate the Table of Contents=
from the template, so the TOC is useless for browsing
the document.<= br>
Editorial - I dislike this new references format - it's very
different from IETF and W3C references and leaves out
the important mont= h and year of publication (which warns
the reader to check for a newer v= ersion when it's an old
RFC, etc.).

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - L= inux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-C= hair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic<= /a>
http://sites.google.com/site/highnor= thinc
mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 S= aline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 2= 21=A0 Grand Marais, MI 49839
=A0 906-494-2434



On Fri, Feb 25, 2011 at 7:24 PM, Michael= Sweet <msweet@app= le.com> wrote:
All,

Sorry, = the correct URLs are:

=A0 =A0=A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20110225.docx
=A0 =A0=A0
ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippj= obprinterext3v10-20110225.pdf

On Feb= 25, 2011, at 3:41 PM, Michael Sweet wrote:
All,

I have just uploaded a= n initial draft of the IPP Job and Printer Extensions - Set 3 (JPS3) specif= ication containing most of the combined additions we have discussed for IPP= Everywhere:


There is still a bunch of stuff I need to fill in= , and I noticed (just after uploading) that I forgot to include the job-uui= d, printer-uuid, and subscription-uuid attributes, but otherwise it should = be relatively complete from the "this is what we need to work on"= point of view.

Comments, etc. welcome. For possible discussion at Mond= ay's IPP telecon...

=
______________________________________________________________________= __
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

__________________________________________________
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. --001636c5a8484c143b049d364e78-- --===============1384855960== 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 --===============1384855960==-- From ipp-bounces@pwg.org Sat Feb 26 20:22:06 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 498E83A68CD for ; Sat, 26 Feb 2011 20:22:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxM+6fcOTr6X for ; Sat, 26 Feb 2011 20:22:05 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id D05F03A6859 for ; Sat, 26 Feb 2011 20:22:03 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 3C3137956D; Sat, 26 Feb 2011 23:22:44 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id B67847956B for ; Sat, 26 Feb 2011 23:22:30 -0500 (EST) Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id EF776D4E759B; Sat, 26 Feb 2011 20:22:29 -0800 (PST) X-AuditID: 11807136-b7b89ae000000345-c6-4d69d185a0ad Received: from [17.153.51.238] (Unknown_Domain [17.153.51.238]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id 4F.57.00837.581D96D4; Sat, 26 Feb 2011 20:22:29 -0800 (PST) Subject: Re: [IPP] (Very) Draft IPP Job and Printer Extensions - Set 3 posted Mime-Version: 1.0 (Apple Message framework v1203) From: Michael Sweet In-Reply-To: Date: Sat, 26 Feb 2011 20:22:30 -0800 Message-Id: <0A89A30A-B8E3-4DD1-8F39-497F3349A8DF@apple.com> References: <41D839ED-0935-40E6-B530-9FF015D364CB@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.1203) X-Brightmail-Tracker: AAAAAA== 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="===============0211977669==" 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: 3C3137956D.A9449 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0211977669== Content-Type: multipart/alternative; boundary="Apple-Mail=_025C48EC-2256-409F-A4E9-168237886B08" --Apple-Mail=_025C48EC-2256-409F-A4E9-168237886B08 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Feb 26, 2011, at 1:41 PM, Ira McDonald wrote: > Hi Mike, >=20 > Editorial - You didn't regenerate the Table of Contents > from the template, so the TOC is useless for browsing > the document. Oops! I wish Word would auto-regenerate on save... :( > Editorial - I dislike this new references format - it's very > different from IETF and W3C references and leaves out > the important month and year of publication (which warns > the reader to check for a newer version when it's an old > RFC, etc.). I'll see what other formats are in use by our published specs; if there is = a common format, I'll just change to that and update the template to includ= e examples. __________________________________________________ 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. --Apple-Mail=_025C48EC-2256-409F-A4E9-168237886B08 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii
On Feb 26, 2011, at 1:41 PM, Ira McDonald wrote:
Hi Mike,

Editorial - You didn't regenerate the Table of Contents
from the template, so the TOC is useless for browsing
the document.

Oops!  I wish Word would auto-regenerate on save... :(

Editorial - I dislike this new references format - it's very
different from IETF and W3C references and leaves out
the important month and year of publication (which warns
the reader to check for a newer version when it's an old
RFC, etc.).

I'll see what other formats are in use by our published specs; if there is a common format, I'll just change to that and update the template to include examples.

__________________________________________________
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. --Apple-Mail=_025C48EC-2256-409F-A4E9-168237886B08-- --===============0211977669== 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 --===============0211977669==-- From ipp-bounces@pwg.org Mon Feb 28 09:04:41 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5C823A6C3C for ; Mon, 28 Feb 2011 09:04:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iq009u4tF6eK for ; Mon, 28 Feb 2011 09:04:40 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 5F18C3A6C3B for ; Mon, 28 Feb 2011 09:04:40 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C97D0794D7; Mon, 28 Feb 2011 12:05:25 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id F1C8A7943C for ; Mon, 28 Feb 2011 12:05:13 -0500 (EST) Received: by fxm17 with SMTP id 17so4739715fxm.5 for ; Mon, 28 Feb 2011 09:05:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=bKeFkqy/X2S2j1DfhRxHgJnW/hIdzWyLmY3mJX1MorA=; b=CfS/EXsItWSG8rYjtn2SrQITf5k3POxZKhGrZ/ingen2/PnFPMAHvDwfMBW3noTDVq fV6aZlZPsPfVbdS3OHfiDulLbUPtGNGRCtS65HUy2yxhopN3/0ztn2EXn/pYrqFJmDd1 +AR2si+nALYPi8czIvZLtK8pfKjNJALjLCFRw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=nxv3cXce9MoxprVKoazDoftbnTz343fU0Z9uTgPSHbkMK+EslieYGmfOCR4wzoXhg3 JRwQOzl6E5cFsQutIYgRgZZ0DiYFqOI9840iPORNtzdkAP1oefrwG01MWT4EzMgov5xs NsTbX7qD4z0PaVouGxii8orl91HapSGZDl13g= MIME-Version: 1.0 Received: by 10.223.104.71 with SMTP id n7mr6747805fao.120.1298912676174; Mon, 28 Feb 2011 09:04:36 -0800 (PST) Received: by 10.223.78.132 with HTTP; Mon, 28 Feb 2011 09:04:36 -0800 (PST) Date: Mon, 28 Feb 2011 12:04:36 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP over HTTP Transport Binding and 'ipps' URI Scheme (28 February 2011) 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="===============0290055652==" 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: C97D0794D7.A9ADD X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0290055652== Content-Type: multipart/alternative; boundary=001636c5a848a85bfa049d5aac31 --001636c5a848a85bfa049d5aac31 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just posted a third Internet-Draft of IPP over HTTP Transport Binding and 'ipps' URI Scheme to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-02-20110228.txt - plaintext Internet-Draft format (warning - contains explicit formfeed characters) ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-02-20110228.htm - HTML format w/ live table of contents This document has already been accepted and posted to the IETF I-D repository. This document was created by a complete rewrite IPP URI Scheme [RFC3510]. This version has many editorial changes per comments received from Mykyta Yevstifeyev on the second draft - see Change History at end. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --001636c5a848a85bfa049d5aac31 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've just posted a third Internet-Draft of IPP over HTTP Tra= nsport Binding and
'ipps' URI Scheme t= o:

=A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/dra= ft-mcdonald-ipps-uri-scheme-02-20110228.txt
=A0- plaintext Internet-Draft format (warning - contains explicit formfeed= characters)

=A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/dra= ft-mcdonald-ipps-uri-scheme-02-20110228.htm
=A0- HTML format w/ live table of contents

This document has alread= y been accepted and posted to the IETF I-D repository.

This document was created by a complete rewrite IPP URI Scheme= =A0 [RFC3510].

This version has many editorial changes per comments rece= ived from Mykyta
Yevstifeyev on the second draft - see Change History at end.

Comments?

Cheers,
- Ira


Ira McDonald (Mu= sician / Software Architect)
Chair - Linux Foundation Open Printing WGCo-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Des= ignated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic<= /a>
http://sites.google.com/site/highnor= thinc
mailto:blueroo= fmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 S= aline, MI=A0 48176
=A0 734-944-0094
May to Christmas:
=A0 PO Box 2= 21=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. --001636c5a848a85bfa049d5aac31-- --===============0290055652== 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 --===============0290055652==-- From ipp-bounces@pwg.org Mon Feb 28 11:10:37 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C1073A6C61 for ; Mon, 28 Feb 2011 11:10:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtrhWpaYpR9m for ; Mon, 28 Feb 2011 11:10:36 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 336013A6C49 for ; Mon, 28 Feb 2011 11:10:36 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 403F17951F; Mon, 28 Feb 2011 14:11:23 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id AF4DA7951E for ; Mon, 28 Feb 2011 14:11:08 -0500 (EST) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 0B2ECD2D399F for ; Mon, 28 Feb 2011 11:11:08 -0800 (PST) X-AuditID: 11807134-b7c40ae000006cb9-cd-4d6bf34b41f2 Received: from da0704a-dhcp214.apple.com (da0704a-dhcp214.apple.com [17.197.43.214]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id A0.91.27833.B43FB6D4; Mon, 28 Feb 2011 11:11:07 -0800 (PST) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Feb 2011 11:11:07 -0800 To: ipp@pwg.org Message-Id: <7970C49B-3232-4295-9CAE-0433538B2067@apple.com> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's IPP telecon 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: 403F17951F.A949F X-pwg-MailScanner-From: ipp-bounces@pwg.org All, I have posted today's minutes at: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20110228.pdf Primary discussion was on the updated charter, with lots of discussion (Ira= , please review minutes - several questions for you...) We didn't get to the new JPS3 draft, however I will be posting an update so= on with the missing xxx-uuid attributes along with fixed table-of-contents = and list-of-tables to make the document easier to read. New action items: - Mike and Paul to reach out to label/portable printer vendors to join IPP = WG discussions ________________________________________________________________________ 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 Mon Feb 28 15:58:29 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 900023A6CA5 for ; Mon, 28 Feb 2011 15:58:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.654 X-Spam-Level: X-Spam-Status: No, score=-2.654 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0BQvNQLNMzK for ; Mon, 28 Feb 2011 15:58:28 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 582A23A6828 for ; Mon, 28 Feb 2011 15:58:28 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 759BF79522; Mon, 28 Feb 2011 18:59:16 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id F0E6779514 for ; Mon, 28 Feb 2011 18:59:04 -0500 (EST) Received: by fxm17 with SMTP id 17so5193923fxm.5 for ; Mon, 28 Feb 2011 15:59:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=+xulHJWptK/nxMlY6zbhTQztLK7c1TIiZ0J0HM8hIv4=; b=s3QJ5SuC2iKZ6kVZF8Xf7w0pLPz3tH1ksp8LHKSapj1gTw17MZ2TsUdvzv+2NxibOP 7FCIvJDfe62AbVyxICXh+jMACVgG6u1Wxe2yiSL377bMwnPTF8vHuf3/E4eY5jitF8KZ h+KlFmMdY0yBjmVuBheyJy3hEsF86qRHPckwc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=huleKIM0hCgKo9wcMuWmO1Mp57rblKk1S28k2jCHTsKErKHug9T6qx7V9UdfqmH75j YRih70sxNER5hmMySyg8kgl3J23q8xOCE54e4eQFmFaJhypKrSg6HhApKesDoPKI2lFR s/QnzHxo+E446t6MsSrsWh76CuhWeHlTFsJ3E= MIME-Version: 1.0 Received: by 10.223.53.68 with SMTP id l4mr7371183fag.44.1298937513006; Mon, 28 Feb 2011 15:58:33 -0800 (PST) Received: by 10.223.78.132 with HTTP; Mon, 28 Feb 2011 15:58:32 -0800 (PST) Date: Mon, 28 Feb 2011 18:58:32 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Third revised IPP Everywhere Charter (28 February 2011) 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="===============0949447195==" 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: 759BF79522.AA52D X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0949447195== Content-Type: multipart/alternative; boundary=0015174796480c5567049d6075ca --0015174796480c5567049d6075ca Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just posted a *third* draft of our new IPP Everywhere Project charterat: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.pdf / doc - line numbers and redlines After talking with Mike Sweet just now and reviewing his minutes from today's IPP WG teleconference, I've tweaked it accordingly. Major revision that *deletes* the following spec: - IPP Everywhere Requirements - to be included in each spec Major revision that *adds* all of the following specs: - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-track) - LDAP Printer Schema (IETF informational) - PWG Raster (w/ IANA MIME type registration) - IPP Everywhere First Edition (printing) - clarified scope as printing only - IPP Scan Service - IPP System Control Service - IPP FaxIn Service (leveraging previous IPP Fax project and MFD FaxIn) - IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut) - IPP Everywhere Second Edition (multifunction) Note: The IPP over HTTPS Transport Binding and 'ipps' URI Scheme spec MUST be IETF standards-track (i.e., the PWG may not consider it a new transport binding, but the IETF will so consider it). Added initial draft and prototype draft milestones for all these specs (but not PWG Last Call because prototyping may change them). Revised many milestone dates - Bill - please check them for plausibility. Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: 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. --0015174796480c5567049d6075ca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've just posted a third draft of our new IPP Everywh= ere Project charter at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.= pdf / doc
- line numbers and redlines

After talking with Mike Sweet just now a= nd reviewing his minutes from today's
IPP WG teleconference, I'v= e tweaked it accordingly.

Major revision that deletes the fol= lowing spec:

- IPP Everywhere Requirements - to be included in each spec

Major revision that adds all of the following specs:

- IP= P over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standard= s-track)
- LDAP Printer Schema (IETF informational)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edi= tion (printing) - clarified scope as printing only
- IPP Scan Service - IPP System Control Service
- IPP FaxIn Service (leveraging previous = IPP Fax project and MFD FaxIn)
- IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut)- IPP Everywhere Second Edition (multifunction)


Note:=A0 The I= PP over HTTPS Transport Binding and 'ipps' URI Scheme spec
MUST= be IETF standards-track (i.e., the PWG may not consider it a new
transport binding, but the IETF will so consider it).

Added initial = draft and prototype draft milestones for all these specs (but not
PWG La= st Call because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.
Comments?

Cheers,
- Ira


Ira McDona= ld (Musician / Software Architect)
Chair - Linux Foundation Open Printin= g WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=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. --0015174796480c5567049d6075ca-- --===============0949447195== 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 --===============0949447195==-- From ipp-bounces@pwg.org Mon Feb 28 16:27:18 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78BE93A6CBA for ; Mon, 28 Feb 2011 16:27:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZMpz9n3-+utH for ; Mon, 28 Feb 2011 16:27:17 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id EEA873A6CB3 for ; Mon, 28 Feb 2011 16:27:16 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6B40B79522; Mon, 28 Feb 2011 19:28:04 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by pwg.org (Postfix) with ESMTP id DF0C679515 for ; Mon, 28 Feb 2011 19:27:51 -0500 (EST) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id EFFE9D55FA87; Mon, 28 Feb 2011 16:27:50 -0800 (PST) X-AuditID: 11807137-b7c3cae0000010f5-46-4d6c3d676ebd Received: from [17.153.39.191] (Unknown_Domain [17.153.39.191]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 27.D2.04341.87D3C6D4; Mon, 28 Feb 2011 16:27:50 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1203) From: Michael Sweet In-Reply-To: Date: Mon, 28 Feb 2011 16:27:17 -0800 Message-Id: References: To: Ira McDonald X-Mailer: Apple Mail (2.1203) X-Brightmail-Tracker: AAAAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Third revised IPP Everywhere Charter (28 February 2011) 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="===============1087501567==" 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: 6B40B79522.AAA0B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1087501567== Content-Type: multipart/alternative; boundary="Apple-Mail=_8D5BA5ED-62DE-4DFF-B274-891FEA3F62B1" --Apple-Mail=_8D5BA5ED-62DE-4DFF-B274-891FEA3F62B1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Minor correction: Line 107: remove "see OBJ-4 above" from OBJ-7... Also, in order to mitigate risk for the first edition of IPP Everywhere, we= can make the reference to the "ipps" RFC informational (pointing to the cu= rrent draft) with the corresponding background text (in wide use for many y= ears, IPP over HTTPS, etc.) On Feb 28, 2011, at 3:58 PM, Ira McDonald wrote: > Hi, >=20 > I've just posted a third draft of our new IPP Everywhere Project charter = at: >=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.pdf / = doc > - line numbers and redlines >=20 > After talking with Mike Sweet just now and reviewing his minutes from tod= ay's > IPP WG teleconference, I've tweaked it accordingly. >=20 > Major revision that deletes the following spec: >=20 > - IPP Everywhere Requirements - to be included in each spec >=20 > Major revision that adds all of the following specs: >=20 > - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-= track) > - LDAP Printer Schema (IETF informational) > - PWG Raster (w/ IANA MIME type registration) > - IPP Everywhere First Edition (printing) - clarified scope as printing o= nly > - IPP Scan Service=20 > - IPP System Control Service > - IPP FaxIn Service (leveraging previous IPP Fax project and MFD FaxIn) > - IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut) > - IPP Everywhere Second Edition (multifunction) >=20 >=20 > Note: The IPP over HTTPS Transport Binding and 'ipps' URI Scheme spec=20 > MUST be IETF standards-track (i.e., the PWG may not consider it a new=20 > transport binding, but the IETF will so consider it). >=20 > Added initial draft and prototype draft milestones for all these specs (b= ut not > PWG Last Call because prototyping may change them). >=20 > Revised many milestone dates - Bill - please check them for plausibility. >=20 > Comments? >=20 > Cheers, > - Ira >=20 >=20 > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Hardcopy WG > 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 > Christmas through April: > 579 Park Place Saline, MI 48176 > 734-944-0094 > May to Christmas: > PO Box 221 Grand Marais, MI 49839 > 906-494-2434=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. --Apple-Mail=_8D5BA5ED-62DE-4DFF-B274-891FEA3F62B1 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Minor correction:

    Line 107: remove "see OBJ-4 above" from OBJ-7...

Also, in order to mitigate risk for the first edition of IPP Everywhere, we can make the reference to the "ipps" RFC informational (pointing to the current draft) with the corresponding background text (in wide use for many years, IPP over HTTPS, etc.)

On Feb 28, 2011, at 3:58 PM, Ira McDonald wrote:

Hi,

I've just posted a third draft of our new IPP Everywhere Project charter at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.pdf / doc
- line numbers and redlines

After talking with Mike Sweet just now and reviewing his minutes from today's
IPP WG teleconference, I've tweaked it accordingly.

Major revision that deletes the following spec:

- IPP Everywhere Requirements - to be included in each spec

Major revision that adds all of the following specs:

- IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standards-track)
- LDAP Printer Schema (IETF informational)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edition (printing) - clarified scope as printing only
- IPP Scan Service
- IPP System Control Service
- IPP FaxIn Service (leveraging previous IPP Fax project and MFD FaxIn)
- IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut)
- IPP Everywhere Second Edition (multifunction)


Note:  The IPP over HTTPS Transport Binding and 'ipps' URI Scheme spec
MUST be IETF standards-track (i.e., the PWG may not consider it a new
transport binding, but the IETF will so consider it).

Added initial draft and prototype draft milestones for all these specs (but not
PWG Last Call because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.

Comments?

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
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
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


__________________________________________________
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. --Apple-Mail=_8D5BA5ED-62DE-4DFF-B274-891FEA3F62B1-- --===============1087501567== 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 --===============1087501567==-- From ipp-bounces@pwg.org Mon Feb 28 17:51:00 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F6A53A6A56 for ; Mon, 28 Feb 2011 17:51:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.648 X-Spam-Level: X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOeeiGJ8GD97 for ; Mon, 28 Feb 2011 17:50:59 -0800 (PST) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 090953A695E for ; Mon, 28 Feb 2011 17:50:59 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 74D197953A; Mon, 28 Feb 2011 20:51:43 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 2856A79539 for ; Mon, 28 Feb 2011 20:51:30 -0500 (EST) Received: by fxm17 with SMTP id 17so5271519fxm.5 for ; Mon, 28 Feb 2011 17:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WUFGYilhVDXCUyRJmOh3fxZHnP3eS36N/RB3vVeeyAs=; b=xwtIlrlUDNqMuY2eDWZ/U8uv3l0qsWavC+Ai6QybpmaMcJGwh6YnUhd86V7b8QvklQ EGeZ8R8B/zT5yw259xELUnoRZrgbVNlTy6RjJ9HHaZwD+48zFjdDeB687jZ5c0bvAqcS +tmuYoPDwc+LLxUMfAISVBsBRZva+15ffmXvM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=K7x6Ji30XaoK1h7xDNaUtLP9KgJJZtgfDJN2n0akBvSbuX+1rRh0p+RyJKBNIjom2S Yklczy0VdWKUoHjRgWvSINDzUqPvJNA+p6uVf/csoPYwpPzkyRBPqtpJi6Vh2BScnnTH ZaMLABamNCOoeKl89iepuugTpgJDTr6Cn5Xx8= MIME-Version: 1.0 Received: by 10.223.53.68 with SMTP id l4mr7468219fag.44.1298944289740; Mon, 28 Feb 2011 17:51:29 -0800 (PST) Received: by 10.223.78.132 with HTTP; Mon, 28 Feb 2011 17:51:29 -0800 (PST) In-Reply-To: References: Date: Mon, 28 Feb 2011 20:51:29 -0500 Message-ID: From: Ira McDonald To: Michael Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Third revised IPP Everywhere Charter (28 February 2011) 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="===============0735711372==" 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: 74D197953A.AA258 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0735711372== Content-Type: multipart/alternative; boundary=001517479648f9171f049d6208cf --001517479648f9171f049d6208cf Content-Type: text/plain; charset=ISO-8859-1 Hi, Thanks for that catch Mike - I slightly revised the charter and posted it over the earlier copy at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.pdf / doc - line numbers and redlines Additional changes: - Added Andrew Mitchell as an editor (for IPP Scan) - Removed the assumptions about IETF document status from specs (b) 'ipps' and (c) LDAP, since this is at the discretion of the IESG and current IETF best practice - Removed reference to (deleted) OBJ-4 from OBJ-7 Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Hardcopy WG 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 Christmas through April: 579 Park Place Saline, MI 48176 734-944-0094 May to Christmas: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Feb 28, 2011 at 7:27 PM, Michael Sweet wrote: > Minor correction: > > Line 107: remove "see OBJ-4 above" from OBJ-7... > > Also, in order to mitigate risk for the first edition of IPP Everywhere, we > can make the reference to the "ipps" RFC informational (pointing to the > current draft) with the corresponding background text (in wide use for many > years, IPP over HTTPS, etc.) > > On Feb 28, 2011, at 3:58 PM, Ira McDonald wrote: > > Hi, > > I've just posted a *third* draft of our new IPP Everywhere Project charterat: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20110228.pdf / > doc > - line numbers and redlines > > After talking with Mike Sweet just now and reviewing his minutes from > today's > IPP WG teleconference, I've tweaked it accordingly. > > Major revision that *deletes* the following spec: > > - IPP Everywhere Requirements - to be included in each spec > > Major revision that *adds* all of the following specs: > > - IPP over HTTPS Transport Binding and 'ipps' URI Scheme (IETF > standards-track) > - LDAP Printer Schema (IETF informational) > - PWG Raster (w/ IANA MIME type registration) > - IPP Everywhere First Edition (printing) - clarified scope as printing > only > - IPP Scan Service > - IPP System Control Service > - IPP FaxIn Service (leveraging previous IPP Fax project and MFD FaxIn) > - IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut) > - IPP Everywhere Second Edition (multifunction) > > > Note: The IPP over HTTPS Transport Binding and 'ipps' URI Scheme spec > MUST be IETF standards-track (i.e., the PWG may not consider it a new > transport binding, but the IETF will so consider it). > > Added initial draft and prototype draft milestones for all these specs (but > not > PWG Last Call because prototyping may change them). > > Revised many milestone dates - Bill - please check them for plausibility. > > Comments? > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Hardcopy WG > 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 > Christmas through April: > 579 Park Place Saline, MI 48176 > 734-944-0094 > May to Christmas: > PO Box 221 Grand Marais, MI 49839 > 906-494-2434 > > > __________________________________________________ > 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. --001517479648f9171f049d6208cf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Thanks for that catch Mike - I slightly revised the charter
a= nd posted it over the earlier copy at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere= -charter-20110228.pdf / doc
- line numbers and redlines

Additional changes:

- Added Andre= w Mitchell as an editor (for IPP Scan)

- Removed the assumptions abo= ut IETF document status
=A0 from specs (b) 'ipps' and (c) LDAP,= since this is at the
=A0 discretion of the IESG and current IETF best practice

- Removed = reference to (deleted) OBJ-4 from OBJ-7

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Fou= ndation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=A0 PO Box 221=A0 Grand Marais, MI= 49839
=A0 906-494-2434



On Mon, Feb 28, 2011 at 7:27 PM, Michael= Sweet <msweet@app= le.com> wrote:
Minor correction:

= =A0 =A0 Line 107: remove "see OBJ-4 above" from OBJ-7...

Also, in order to mitigate risk for the first edition of I= PP Everywhere, we can make the reference to the "ipps" RFC inform= ational (pointing to the current draft) with the corresponding background t= ext (in wide use for many years, IPP over HTTPS, etc.)

On Feb 28, 2011, at 3:= 58 PM, Ira McDonald wrote:

Hi,

I&= #39;ve just posted a third draft of our new IPP Everywhere Project <= span>charter at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeveryw= here-charter-20110228.pdf / doc
- line numbers and redlines

After talking with Mike Sweet just now a= nd reviewing his minutes from today's
IPP WG teleconference, I'v= e tweaked it accordingly.

Major revision that deletes the fol= lowing spec:

- IPP Everywhere Requirements - to be included in each spec

Major revision that adds all of the following specs:

- IP= P over HTTPS Transport Binding and 'ipps' URI Scheme (IETF standard= s-track)
- LDAP Printer Schema (IETF informational)
- PWG Raster (w/ IANA MIME type registration)
- IPP Everywhere First Edi= tion (printing) - clarified scope as printing only
- IPP Scan Service - IPP System Control Service
- IPP FaxIn Service (leveraging previous = IPP Fax project and MFD FaxIn)
- IPP FaxOut Service (leveraging previous IPP Fax project and MFD FaxOut)- IPP Everywhere Second Edition (multifunction)


Note:=A0 The I= PP over HTTPS Transport Binding and 'ipps' URI Scheme spec
MUST= be IETF standards-track (i.e., the PWG may not consider it a new
transport binding, but the IETF will so consider it).

Added initial = draft and prototype draft milestones for all these specs (but not
PWG La= st Call because prototyping may change them).

Revised many milestone dates - Bill - please check them for plausibility.
Comments?

Cheers,
- Ira


Ira McDona= ld (Musician / Software Architect)
Chair - Linux Foundation Open Printin= g WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Desig= nated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
<= a href=3D"http://sites.google.com/site/blueroofmusic" target=3D"_blank">htt= p://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:
b= lueroofmusic@gmail.com
Christmas through April:
=A0 579 Park Place=A0 Saline, MI=A0 48176
= =A0 734-944-0094
May to Christmas:
=A0 PO Box 221=A0 Grand Marais, MI= 49839
=A0 906-494-2434


__________________________________________________
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. --001517479648f9171f049d6208cf-- --===============0735711372== 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 --===============0735711372==-- From ipp-bounces@pwg.org Mon Feb 28 18:30:47 2011 Return-Path: X-Original-To: ietfarch-ipp-archive@core3.amsl.com Delivered-To: ietfarch-ipp-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 949E03A6C4C for ; Mon, 28 Feb 2011 18:30:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.643 X-Spam-Level: X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dt55QiAy0grf for ; Mon, 28 Feb 2011 18:30:41 -0800 (PST) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A9F393A6B17 for ; Mon, 28 Feb 2011 18:30:41 -0800 (PST) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1C67679542; Mon, 28 Feb 2011 21:31:28 -0500 (EST) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46]) by pwg.org (Postfix) with ESMTP id 1A8A579541 for ; Mon, 28 Feb 2011 21:31:15 -0500 (EST) Received: by fxm17 with SMTP id 17so5296349fxm.5 for ; Mon, 28 Feb 2011 18:31:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=s6SNAHiHr2Uo6tqLw9KwwNNLa4jH2Vqosi+pPSkbG64=; b=Q4UTnLI1KRYdT6dCPB1iEQ880U1fKL6nxGclqrLMirS9C64XwvvzqL+hZBDhXadWJs reSKUm7S2whbcnRIW5ufc0U8ks2xKKdn483/FTLvapm5WtaC45piaYudPPlBBU8TgWpQ xM+P8oQbouOc8V8mmNQ/1zQVavm3bL/oDarAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=v4O5frDGZNwGhTHapiD5s5WqjB4L7foHXbfNBpay8lAz2CbU7CJCq2gKTbKvwTFRqr WkD0Lm9upmDKGziGCIE+uebqEVAhw+LsftW+vDee7MJd+Ha7fOsbdst5X2+paSCTyL0b iMk1n0PK3/t32hWth+SKfRUDaAhve/fZ5Ut5Y= MIME-Version: 1.0 Received: by 10.223.104.147 with SMTP id p19mr7149896fao.6.1298946674569; Mon, 28 Feb 2011 18:31:14 -0800 (PST) Received: by 10.223.78.132 with HTTP; Mon, 28 Feb 2011 18:31:14 -0800 (PST) Date: Mon, 28 Feb 2011 21:31:14 -0500 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP/2.0 SE (28 February 2011) 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="===============0265724816==" 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: 1C67679542.AA2EF X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0265724816== Content-Type: multipart/alternative; boundary=0016e6da98be1eb358049d6297d9 --0016e6da98be1eb358049d6297d9 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, I've just posted a final Stable draft of PWG IPP Version 2.0 Second Edition, ready with one minor edit from a PWG Formal Vote comment at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20110228.pdf / doc - clean copy with line numbers and hot links in TOC ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20110228-rev.pdf / doc - redlined copy with line numbers and hot links in TOC This draft is in preparation for publication as PWG 5100.12-2011. Cheers, - Ira -------------------- ***Changes made to create 28 February 2011 version (Stable Draft)* Editorial =96 Kept status at Stable Draft =96 minor edit after PWG Formal V= ote Editorial =96 Revised section 4.3 to correct alignment, per PWG Formal Vote comment --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --0016e6da98be1eb358049d6297d9 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi,

I've just posted a final Stable draft of PWG IPP Version 2.0= Second Edition, ready
with one minor edit from a PWG Formal Vote comme= nt at:

=A0 ftp://ftp.pwg.org/pub/pwg/= ipp/wd/wd-ipp20-20110228.pdf <= /span>/ doc
=A0 - clean copy with line numbers and hot links in TOC

=A0 ftp://ftp.pwg.org/pub/= pwg/ipp/wd/wd-ipp20-20110228-rev.pdf / doc
=A0 - redlined copy with line numbers and hot links in TOC

This draft is in preparation for publication as PWG 5100.12-2011.
Cheers,
- Ira
--------------------

Changes made to create 28 February 2011 version (Stable Draft)

Editorial =96 Kept status a= t Stable Draft =96 minor edit after PWG Formal Vote

Editorial =96 Revised section 4.3 to correct alignment, per PWG Formal Vote comment




--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --0016e6da98be1eb358049d6297d9-- --===============0265724816== 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 --===============0265724816==--