From pwg-announce-bounces@pwg.org Sun Aug 1 08:08:43 2010 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 4D5553A697B for ; Sun, 1 Aug 2010 08:08:43 -0700 (PDT) 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 w7AR5JpuziMD for ; Sun, 1 Aug 2010 08:08:37 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 60D6D3A6969 for ; Sun, 1 Aug 2010 08:08:37 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D903E79310; Sun, 1 Aug 2010 11:08:43 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by pwg.org (Postfix) with ESMTP id 24D6F79305 for ; Sun, 1 Aug 2010 11:08:37 -0400 (EDT) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta09.westchester.pa.mail.comcast.net with comcast id p2tT1e00C1swQuc5938ev3; Sun, 01 Aug 2010 15:08:38 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta15.westchester.pa.mail.comcast.net with comcast id p38d1e007548CT43b38eea; Sun, 01 Aug 2010 15:08:38 +0000 From: "William Wagner" To: References: In-Reply-To: Date: Sun, 1 Aug 2010 11:08:23 -0400 Message-ID: <001d01cb318b$62ddcf70$28996e50$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcswuIArqiABfmcHS22rxJtClGDtlQAz6aqw Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "'Zehler, Peter'" Subject: [Pwg-Announce] First Session - MFD 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="===============0234958872==" 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: D903E79310.AD756 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org This is a multi-part message in MIME format. --===============0234958872== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01CB3169.DBCC2F70" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_001E_01CB3169.DBCC2F70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings: The first session of the MFD Face-to-face meeting on 3 August is concerned with the Requirements Document Last Call Comments Review and Overall Specification Review. I have posted what we believe to be the final Requirements Document LCRC at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722.pdf ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722.doc ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722-rev.pdf ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722-rev.doc and the Last Call Resolution Comments at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-resolution-20100 722.txt I have posted an update to the "Overall" document at ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730.pdf ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730.doc ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730-rev.pdf ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730-rev.doc This document does not yet reflect the recent changes to the Schema, but does include some major changes. Also, I would like the WG sense on how to proceed with some other issues with that document. Thanks, Bill Wagner From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Zehler, Peter Sent: Saturday, July 31, 2010 9:59 AM To: pwg-announce@pwg.org Subject: [Pwg-Announce] Updated Plenary slides for MFD & v 1.104 of SM schema available All, I have updated the MFD plenary slides with corrected links for the MFD Requirements and FaxIn specifications. The MFD page has all the correct document links. Also note that I have published the latest WSDL and schema (v1.104). The updated slides are available at: The MFD page 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_001E_01CB3169.DBCC2F70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetin= gs:

The fir= st session of the MFD Face-to-face meeting on 3 August is concerned with the R= equirements Document Last Call Comments Review and Overall Specification Review. I have posted what we believe to be the final Requirements Document LCRC at:<= /o:p>

ftp://= ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722.pdf=

ftp://= ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722.doc=

ft= p://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722-rev.pdf

ft= p://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722-rev.doc

&n= bsp;

and the= Last Call Resolution Comments at:

ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comme= nt-resolution-20100722.txt

&n= bsp;

I have = posted an update to the “Overall” document at

f= tp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730.pdf

f= tp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730.doc

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730-rev.pdf

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdoverallmod10-20100730-rev.doc

&n= bsp;

This do= cument does not yet reflect the recent changes to the Schema, but does include som= e major changes. Also, I would like the WG sense on how to proceed with some other issues with that document.

Thanks,=

Bill Wa= gner

&n= bsp;

From: pwg-announce-= bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Zehler, Peter
Sent: Saturday, July 31, 2010 9:59 AM
To: pwg-announce@pwg.org
Subject: [Pwg-Announce] Updated Plenary slides for MFD & v 1.104= of SM schema available

 

All,

I have updated the MFD plenary slides with corrected l= inks for the MFD Requirements and FaxIn specifications.  The MFD page has a= ll the correct document links.  Also note that I have published the latest WSDL and schema (v1.104). 

 

The updated slides are available at:

<ft= p://ftp.pwg.org/pub/pwg/mfd/minutes/MFD_WG_Plenary_Aug_10.pdf><= /o:p>

 

The MFD page is located at:

<http= ://www.pwg.org/mfd/index.html>

 

 

 =

Peter Zehler

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

 


--
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_001E_01CB3169.DBCC2F70-- --===============0234958872== 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 --===============0234958872==-- From pwg-announce-bounces@pwg.org Wed Aug 4 15:47:30 2010 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 7C2773A683F for ; Wed, 4 Aug 2010 15:47:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.751 X-Spam-Level: X-Spam-Status: No, score=-0.751 tagged_above=-999 required=5 tests=[AWL=-0.752, BAYES_50=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 Y2dlQ6B4O7-t for ; Wed, 4 Aug 2010 15:47:29 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 5F6D03A6407 for ; Wed, 4 Aug 2010 15:47:26 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5F31B79252; Wed, 4 Aug 2010 18:47:47 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id A85DD7922D for ; Wed, 4 Aug 2010 18:47:40 -0400 (EDT) Received: by vws3 with SMTP id 3so4828201vws.5 for ; Wed, 04 Aug 2010 15:47:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=WsKDeaKTEKYzQQ/2m32MorzyU4cnFPfsr8Ot4WwRhGQ=; b=Aw7WRoJz2m2QpnMI1T/4IDpLevKI69Ba8ayLNzQf5wshmpEj1NY87NkSKhWHFdKAwP XNymDjofalWTe+OEUdC7P4Zl52Kw/93pI45lLMBls5Mm5Fw7Y5U5qz1eE0FyDe7Es/NJ m7IkGHhoZp/SAyQ7nXlSfXlxYpqX+LJ0+wAxA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=bBZhKFyGCicJ+rRqMBX7rT+uQ80zCP0CoANuWTKUgQ2I4cB5oN7RnDiTZF55idxquG KjIxrbXUgQnlyMl/ytJfrucs5lS3ayJlgBkUTEiRau2t+MvYaNuHjiJ5e3gz9ThEkTXt fc/VoEbiEBSa/MOi4I2gbzncfxUHZuBdbsR4Q= MIME-Version: 1.0 Received: by 10.220.71.136 with SMTP id h8mr6663386vcj.135.1280962059849; Wed, 04 Aug 2010 15:47:39 -0700 (PDT) Received: by 10.220.175.195 with HTTP; Wed, 4 Aug 2010 15:47:39 -0700 (PDT) Date: Wed, 4 Aug 2010 18:47:39 -0400 Message-ID: From: Ira McDonald To: pwg-announce@pwg.org, Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [Pwg-Announce] Minutes for today's PWG Plenary (4 August 2010) 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: 5F31B79252.AC71A X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Hi, Minutes for today's PWG Plenary are posted at: =A0 ftp://ftp.pwg.org/pub/pwg/general/minutes/pwg-plenary-minutes-20100804.= htm Please send any corrections or additions to me. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: =A0 579 Park Place=A0 Saline, MI=A0 48176 =A0 734-944-0094 summer: =A0 PO Box 221=A0 Grand Marais, MI 49839 =A0 906-494-2434 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From diophantineir7@foreverwed.com Fri Aug 6 15:50:59 2010 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 139F03A6A6F; Fri, 6 Aug 2010 15:50:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.204 X-Spam-Level: X-Spam-Status: No, score=-2.204 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FB_QUALITY_REPLICA=10.357, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, SARE_SPEC_REPLICA_OBFU=1.812, SARE_SPEC_ROLEX_NOV5A=1.062, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, 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 iX+jJKcw1egd; Fri, 6 Aug 2010 15:50:57 -0700 (PDT) Received: from chello084112139132.12.11.vie.surfer.at (chello084112139132.12.11.vie.surfer.at [84.112.139.132]) by core3.amsl.com (Postfix) with ESMTP id 4088D3A68E1; Fri, 6 Aug 2010 15:50:53 -0700 (PDT) Received: from 84.112.139.132 by foreverwed.com; Sat, 7 Aug 2010 00:51:21 +0100 Message-ID: <000d01cb35b9$e3677060$6400a8c0@diophantineir7> From: To: Subject: The lastest run way fashion for all watches and bags Date: Sat, 7 Aug 2010 00:51:21 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CB35B9.E3677060" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01CB35B9.E3677060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 Now, with just a few simple clicks, you can have that watch you've alw= ays wanted!=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 We specializes in the sales of brand name quality replica timepiec= es, at some of the lowest=20 prices possible. =20 =20 =20 With our large selection of watches you can be sure to find that p= erfect timepiece that will suit=20 you best=2E =20 =20 Now, with just a few simple clicks, you can have that watch you've= always wanted!=20 =20 =20 Don't spend all your savings on that timepiece you've always longed for. B= uy a replica=20 B r a n d at only a=20 fraction of the price! =20 =20 Just one move to visit =09 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 ------=_NextPart_000_0007_01CB35B9.E3677060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 =20
=20
=20 =20

=20 Now, with just a few simple clicks, you can have that watch you've alw= ays wanted!=20

=20
=20
=20 =20 =20 =20 =20
=20 3D"Visit

We specializes in the sales of brand name quality replica timep= ieces, at some of the lowest=20 prices possible. =20

=20

With our large selection of watches you can be sure to find that p= erfect timepiece that will suit=20 you best=2E

Now, with just a few simple clicks, you can have that watch you've= always wanted!=20

=20 Don't spend all your savings on that timepiece you've always longed for= Buy a replica=20 B r a n d at only a=20 fraction of the price!

=20

Just one move to visit

=20
=20
=20 =20
------=_NextPart_000_0007_01CB35B9.E3677060-- From ipp-bounces@pwg.org Mon Aug 9 02:36:21 2010 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 651DE3A68F5 for ; Mon, 9 Aug 2010 02:36:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.46 X-Spam-Level: ** X-Spam-Status: No, score=2.46 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_FONT_SIZE_HUGE=0.057, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, J_CHICKENPOX_33=0.6, J_CHICKENPOX_36=0.6, J_CHICKENPOX_37=0.6, 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 Z1X8s495++ov for ; Mon, 9 Aug 2010 02:36:04 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 184A63A68AB for ; Mon, 9 Aug 2010 02:36:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9797A79380; Mon, 9 Aug 2010 05:36:01 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail.printassociates.com (gw.tib27.printassociates.com [80.62.106.102]) by pwg.org (Postfix) with ESMTP id 545297937F; Mon, 9 Aug 2010 05:35:48 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Attributes needed for Cloud Printing and definitioninconsistencies Date: Mon, 9 Aug 2010 11:37:24 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Attributes needed for Cloud Printing and definitioninconsistencies Thread-Index: AcspxRRVo4ExmexOQvqGozc+7BuVQQN3fqnw References: From: "Christoph Lindemann" To: , X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2011592030==" 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: 9797A79380.A9EE7 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============2011592030== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB37A6.3F74FFEF" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB37A6.3F74FFEF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 Would it also be possible to add some sort of parent job UUID list/hierarchy? So it will be possible to track source/parent jobs after splitting a job into several jobs. =20 For example (maybe not the best, but..): Imagine I have a company internal print cloud, to which I submit the jobs. This cloud could forward jobs to other external clouds, based on location (one provider for US, another for EU,...), cost or other parameters. =20 So if I need to print a marketing document in both US and EU, I could submit the job to a special queue in the company cloud, which again would submit 1 copy to my local DeskJet printer, submit a new job with 10000 copies to the external EU print/cloud partner and another 10000 to the US partner. In this example, the jobs at the two external clouds, better not have the same UUID if I need to track them. But I would still need the "root job" UUID for doing accounting. =20 Hope this makes sense, Christoph Lindemann =20 =20 ________________________________ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Zehler, Peter Sent: Thursday, July 22, 2010 8:48 PM To: ipp@pwg.org; mfd@pwg.org Subject: [IPP] Attributes needed for Cloud Printing and definitioninconsistencies =20 Job Identifiers: *existing* job-id (SM: JobId): The identifier for a job with a local scope. That is the ID is unique within the service. The ID may be reused in other instance of a Printer (i.e. Print Service) or for jobs in other types of services (e.g. Copy Service). Datatype: abstract:int32, IPP:integer, SM:xs:int =20 *new* job-uuid (SM:JobUuid): The identifier for a job with a global scope. The identifier is unique for a Job across all service instances of any service type. The UUID URN namespace is specified in rfc4122. The format used for "job-uuid" is the string representation of a UUID as a URN. An example is "urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3". The version (aka subtype) used is implementation specific. Version 1 (i.e. time based) is recommended. Datatype: abstract:char[64], IPP:uri MaxLength=3D64, SM:xs:anyURI maxLen=3D64 =20 Note: I do not believe the IPP attribute "job-uri" is applicable as a globally unique identifier. 1) RFC2911 states "Since every URL is a specialized form of a URI, even though the more generic term URI is used throughout the rest of this document, its usage is intended to cover the more specific notion of URL as well.". All uses of the uri syntax is really a URL syntax. 2) URL implies not only a specific protocol binding but also a location. 3) Locations can be specified using an IP address that need not be locally unique (e.g. 192.168.1.1, localhost)=20 4) Regarding the "job-uri" RFC2911 further states that "This URI is then used by clients as the target for subsequent Job operations.". The globally unique identifier for a job should not specify a transport endpoint for a specific protocol.=20=20=20 5) The globally unique identifier for a Job, Printer or Service should be a URN. It should be protocol independent so that a product that supports multiple protocols should have the same identifiers regardless of the protocol mapping. 6) The globally unique identifier for a Job, Printer or Service should require no central authority to administrate them. Generation of a unique identifier should be simple from an administrative point of view and preferably automated. =20 Note: Both the local and global identifiers should be mandated. For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the local identifier MUST still be maintained. It is possible to use the time_low portion of the Timestamp in the version 1 UUID as the local identifier. The implementation may then keep only the 128 bit local representation of the UUID and use it to create the appropriate protocol values. =20 Printer Identifiers: *existing (Service Monitoring MIB)* applIndex (SM: Id i.e. PrinterId): The service identifier with a local scope. That is the ID is unique across the service instances collocated on a host. Datatype: abstract:int32, MIB:integer, SM:xs:int =20 *new* printer-uuid (SM:ServiceUuid): The identifier for a Printer with a global scope. The identifier is unique across all service instances of any service type. The UUID URN namespace is specified in rfc4122. The format used for "job-uuid" is the string representation of a UUID as a URN. An example is "urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3". The version (aka subtype) used is implementation specific. Version 1 (i.e. time based) is recommended. Datatype: abstract:char[64], IPP:uri, SM:xs:anyURI maxLen=3D64 =20 Note: I do not believe the IPP attribute "printer-uri" is applicable as a globally unique identifier.=20=20 1) RFC2911 states "Since every URL is a specialized form of a URI, even though the more generic term URI is used throughout the rest of this document, its usage is intended to cover the more specific notion of URL as well.". All uses of the uri syntax is really a URL syntax. 2) URL implies not only a specific protocol binding but also a location. 3) Locations can be specified using an IP address that need not be locally unique (e.g. 192.168.1.1, localhost)=20 4) The printer may have multiple "printer-uri" values as enumerated in the "printer-uris-supported" attribute. There should be only a single identifier for a printer. 5) The globally unique identifier for a Job, Printer or Service should be a URN. It should be protocol independent so that a product that supports multiple protocols should have the same identifiers regardless of the protocol mapping. 6) The globally unique identifier for a Job, Printer or Service should require no central authority to administrate them. Generation of a unique identifier should be simple from an administrative point of view and preferably automated. =20 =20 Note: The local instance id in the MIB and SM are artifacts of the model's data binding and are insufficient for use as an identifier. IPP's printer-uri, the URL for Web Service bindings (e.g. WS-Print) and the IP address for legacy protocols such as LPR and Port 9100 are also insufficient. They need not be globally unique. Nonroutable IP addresses may be used.=20=20 =20 Printer Location: *existing* printer-location (SM: ServiceLocation): Identifies the location of the device that this Printer represents. (Example: Pete's Office) This is helpful for a human but is pretty much useless for geolocation since the content is implementation specific. Datatype: abstract:char[127], IPP:string MaxLength=3D127, SM:xs:int =20 *new* printer-geo-location (SM:ServiceGeoLocation): This identifies the location of the associated device using the World Geodetic System 1984(WGS84). The means for expressing the location information is the same as used in DNS (rfc1876) Datatype: abstract:class, IPP:collection, SM:sequence =20 *new* size (SM:Size): Diameter of the bounding sphere containing the device expressed in centimeters. Datatype: abstract: int32, IPP:integer, SM:xs:int =20 *new* horizontal-precision (SM: HorizontalPrecision): The horizontal precision expressed as the diameter of the "circle of error" (i.e. twice the +- error value) The units are centimeters. Datatype: abstract: int32, IPP:integer, SM:xs:int =20 *new* vertical-precision (SM: VerticalPrecision): The vertical precision expressed as the diameter of the "circle of error" (i.e. twice the +- error value) The units are centimeters. Datatype: abstract:integer, IPP: int32, SM:xs:int =20 *new* latitude (SM:Latitude): The latitude of the center of the sphere described by the size attribute. Expressed in thousandths of a second of arc. The value 2147483648 (231) represents the equator. Values above that are north and below are south. Datatype: abstract: int32, IPP:integer, SM:xs:int =20 *new* longitude (SM:Latitude): The longitude of the center of the sphere described by the size attribute. Expressed in thousandths of a second of arc. The value 2147483648 (231) represents the prime meridian. Values above that are east and below are south. The value is rounded away from the prime meridian Datatype: abstract: int32, IPP:integer, SM:xs:int =20 *new* altitude (SM:Altitude): The altitude of the center of the sphere described by the size attribute. Expressed in centimeters from a base of 100,000m below the reference spheroid used by GPS [WGS 84]. Altitude above (or below) sea level may be used as an approximation of altitude relative to the [WGS 84] spheroid, though due to the Earth's surface not being a perfect spheroid, there will be differences. Datatype: abstract: int32, IPP:integer, SM:xs:int =20 Note: There is disagreement on the semantics for all the attributes between what is posted on and what I have in the definition above. I took the definition directly from rfc1876 (I think). See included text from rfc1876 and the location example below.=20=20 =20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 =20 =46rom rfc1876 section 2 =20 =20 SIZE The diameter of a sphere enclosing the described entity, in centimeters, expressed as a pair of four-bit unsigned integers, each ranging from zero to nine, with the most significant four bits representing the base and the second number representing the power of ten by which to multiply the base. This allows sizes from 0e0 (<1cm) to 9e9 (90,000km) to be expressed. This representation was chosen such that the hexadecimal representation can be read by eye; 0x15 =3D 1e5. Four-bit values greater than 9 are undefined, as are values with a base of zero and a non-zero exponent. =20 Since 20000000m (represented by the value 0x29) is greater than the equatorial diameter of the WGS 84 ellipsoid (12756274m), it is therefore suitable for use as a "worldwide" size. =20 HORIZ PRE The horizontal precision of the data, in centimeters, expressed using the same representation as SIZE. This is the diameter of the horizontal "circle of error", rather than a "plus or minus" value. (This was chosen to match the interpretation of SIZE; to get a "plus or minus" value, divide by 2.) =20 VERT PRE The vertical precision of the data, in centimeters, expressed using the sane representation as for SIZE. This is the total potential vertical error, rather than a "plus or minus" value. (This was chosen to match the interpretation of SIZE; to get a "plus or minus" value, divide by 2.) Note that if altitude above or below sea level is used as an approximation for altitude relative to the [WGS 84] ellipsoid, the precision value should be adjusted. =20 LATITUDE The latitude of the center of the sphere described by the SIZE field, expressed as a 32-bit integer, most significant octet first (network standard byte order), in thousandths of a second of arc. 2^31 represents the equator; numbers above that are north latitude. =20 LONGITUDE The longitude of the center of the sphere described by the SIZE field, expressed as a 32-bit integer, most significant octet first (network standard byte order), in thousandths of a second of arc, rounded away from the prime meridian. 2^31 represents the prime meridian; numbers above that are east longitude. =20 ALTITUDE The altitude of the center of the sphere described by the SIZE field, expressed as a 32-bit integer, most significant octet first (network standard byte order), in centimeters, from a base of 100,000m below the [WGS 84] reference spheroid used by GPS (semimajor axis a=3D6378137.0, reciprocal flattening rf=3D298.257223563). Altitude above (or below) sea level may be used as an approximation of altitude relative to the the [WGS 84] spheroid, though due to the Earth's surface not being a perfect spheroid, there will be differences. (For example, the geoid (which sea level approximates) for the continental US ranges from 10 meters to 50 meters below the [WGS 84] spheroid. Adjustments to ALTITUDE and/or VERT PRE will be necessary in most cases. The Defense Mapping Agency publishes geoid height values relative to the [WGS 84] ellipsoid. =20 =20 =20 =20 =20 =20 =20 2-Dimmensional Location of my office printer Google Map URL: http://maps.google.com/maps?f=3Dq&source=3Ds_q&hl=3Den&geocode=3D&q=3D800+p= hillips +rd+webster+ny+14580&sll=3D37.0625,-95.677068&sspn=3D62.226996,106.962891&ie =3DUTF8&hq=3D&hnear=3D800+Phillips+Rd,+Webster,+Monroe,+New+York+14580&ll= =3D43.2 20973,-77.417162&spn=3D0.001781,0.003264&t=3Dh&z=3D19=20 Location representations: Decimal Degrees (WGS84) Latitude Longitude=20 43.220973 -77.417162=20 Degrees, Minutes & Seconds Latitude Longitude=20 N43 13 15 W77 25 01=20 GPS Latitude Longitude=20 N 43 13.258 W 77 25.030=20 UTM X Y=20 18N 303685 4788191=20 =20 My office elevation: 12800 centimeters (419 feet) above sea level Size of Printer: 91 centimeter (3 feet) Margin of error 183 centimeter (6 feet) =20 PrinterGeoLocation (RFC1876) Size =3D 258 (0x0102) (encoded centimeter) HorizontalPrecision =3D 514 (0x0202) (encoded centimeter) VerticalPrecision =3D 514 (0x0202) (encoded centimeter) Latitude =3D 2303079151 (thousandths of a second of arc, 231 represent equater) ( (DecimalDegreeLatitude*60*60*1000)+2147483648 ) Longitude =3D 1868781865 (thousandths of a second of arc, 231 represent prime meridian) ( 2147483648-(DecimalDegreeLongitude*60*60*1000) ) Altitude =3D 10012800 (centimeter) (OfficeElevation+10000000) =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_01CB37A6.3F74FFEF Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

Would it also be po= ssible to add some sort of parent job UUID list/hierarchy? So it will be possible = to track source/parent jobs after splitting a job into several jobs.

 

For example (maybe = not the best, but..):

Imagine I have a company internal print cloud, to which I submi= t the jobs. This cloud could forward jobs to other external clouds, based on loca= tion (one provider for US, another for EU,…), cost or other parameters.

 

So if I need to print a marketing document in both US and EU, I= could submit the job to a special queue in the company cloud, which again would submit 1 copy to my local DeskJet printer, submit a new job with 10000 copi= es to the external EU print/cloud partner and another 10000 to the US partner.

In this example, the jobs at the two external clouds, better not have the same UUID if I need to track them. But I would still need the R= 20;root job” UUID for doing accounting.

 

Hope this makes sen= se,

Christoph Lindemann

 

 


From:= ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Zehler, Peter
Sent: Thursday, July 22, 201= 0 8:48 PM
To: ipp@pwg.org; mfd@pwg.org=
Subject: [IPP] Attributes ne= eded for Cloud Printing and definitioninconsistencies

 

Job Identifiers:

*existing*

job-id (SM: JobId): The identifier for a job with a local scope.&nb= sp; That is the ID is unique within the service.  The ID may be reused in other instance of a Printer (i.e. Print Service)  or for jobs in other types of services (e.g. Copy Service).  Datatype: abstract:int32, IPP:integer, SM:xs:int

 

*new*

job-uuid (SM:JobUuid):  The identifier for a job with a global scope.  The identifier is unique for a Job across all service instance= s of any service type.    The UUID URN namespace is specified in rfc4122.  The format used for “job-uuid” is the string representation of a UUID as a URN.  An example is “urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3”.  The version (aka subtype) use= d is implementation specific.  Version 1 (i.e. time based) is recommended.   Datatype: abstract:char[64], IPP:uri MaxLength=3D6= 4, SM:xs:anyURI maxLen=3D64

 

Note:  I do not believe the IPP attribute “job-uri”= ; is applicable as a globally unique identifier.

1)   RFC2911 states “Since every URL is a spe= cialized form of a URI, even though the more generic term URI is used throughout the rest of this document, its usage is intended to cover the more specific not= ion of URL as well.”.   All uses of the uri syntax is really a = URL syntax.

2)   URL implies not only a specific protocol bindi= ng but also a location.

3)   Locations can be specified using an IP address= that need not be locally unique (e.g. 192.168.1.1, localhost) =

4)   Regarding the “job-uri” RFC2911&nb= sp; further states that “This URI is then used by clients as the target f= or subsequent Job operations.”.  The globally unique identifier for= a job should not specify a transport endpoint for a specific protocol.  

5)   The globally unique identifier for a Job, Prin= ter or Service should be a URN.  It should be protocol independent so that a product that supports multiple protocols should have the same identifiers regardless of the protocol mapping.

6)   The  globally unique identifier for a Job, Printer or Service should require no central authority to administrate them.  Generation of a unique identifier should be simple from an administrative point of view and preferably automated.

 

Note: Both the local and global identifiers should be mandated.&nbs= p; For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the local identi= fier MUST still be maintained.  It is possible to use the time_low portion = of the Timestamp in the version 1 UUID as the local identifier.  The implementation may then keep only the 128 bit local representation of the U= UID and use it to create the appropriate protocol values.

 

Printer Identifiers:=

*existing (Service Monitoring M= IB)*

applIndex (SM: <service>Id i.e. PrinterId): The service identifier with a local scope.  That is the ID is unique across the service instances collocated on a host.  Datatype: abstract:int32, MIB:integer, SM:xs:int

 

*new*

printer-uuid (SM:ServiceUuid):  The identifier for a Printer w= ith a global scope.  The identifier is unique across all service instances= of any service type.    The UUID URN namespace is specified in rfc4122.  The format used for “job-uuid” is the string representation of a UUID as a URN.  An example is “urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3”.  The version (aka subtype) use= d is implementation specific.  Version 1 (i.e. time based) is recommended.   Datatype: abstract:char[64], IPP:uri, SM:xs:anyURI maxLen=3D64

 

Note:  I do not believe the IPP attribute “printer-uri” is applicable as a globally unique identifier.&nb= sp;

1)   RFC2911 states “Since every URL is a spe= cialized form of a URI, even though the more generic term URI is used throughout the rest of this document, its usage is intended to cover the more specific not= ion of URL as well.”.   All uses of the uri syntax is really a = URL syntax.

2)   URL implies not only a specific protocol bindi= ng but also a location.

3)   Locations can be specified using an IP address= that need not be locally unique (e.g. 192.168.1.1, localhost) =

4)   The printer may have multiple “printer-uri” values as enumerated in the “printer-uris-supported” attribute.  There should be only a single  identifier for a printer.

5)   The globally unique identifier for a Job, Prin= ter or Service should be a URN.  It should be protocol independent so that a product that supports multiple protocols should have the same identifiers regardless of the protocol mapping.

6)   The  globally unique identifier for a Job, Printer or Service should require no central authority to administrate them.  Generation of a unique identifier should be simple from an administrative point of view and preferably automated.

 

 

Note: The local instance id in the MIB and SM are artifacts of the model’s data binding and are insufficient for use as an identifier.&n= bsp; IPP’s printer-uri, the URL for Web Service bindings (e.g. WS-Print) a= nd the IP address for legacy protocols such as LPR and Port 9100 are also insu= fficient.  They need not be globally unique.  Nonroutable IP addresses may be used. 

 

Printer Location:

*existing*

printer-location (SM: ServiceLocation): Identifies the location of = the device that this Printer represents.  (Example: Pete’s Office)&n= bsp; This is helpful for a human but is pretty much useless for geolocation since the content is implementation specific.   Datatype: abstract:char[127], IPP:string MaxLength=3D127, SM:xs:int=

 

*new*

printer-geo-location (SM:ServiceGeoLocation):  This identifies= the location of the associated device using the World Geodetic System 1984(WGS84).  The means for expressing the location information is the same as used in DNS (rfc1876)  Datatype: abstract:class, IPP:collectio= n, SM:sequence

 

*new*

size (SM:Size):  Diameter of t= he bounding sphere containing the device expressed in centimeters.    Datatype: abstract: int32, IPP:integer, SM:xs:int

 

*new*

horizontal-precision (SM: HorizontalPrecision):  The horizontal precision expressed as the diame= ter of the “circle of error” (i.e. twice the +- error value)  = The units are centimeters.    Datatype: abstract: int32, IPP:integer, SM:xs:int

 

*new*

vertical-precision (SM: VerticalPrecision):  The vertical precision expressed as the diameter = of the “circle of error” (i.e. twice the +- error value)  The units are centimeters.    Datatype: abstract:integer, IPP: int32, SM:xs:int

 

*new*

latitude (SM:Latitude):  The l= atitude of the center of the sphere described by the size attribute.  Expresse= d in thousandths of a second of arc.  The value 2147483648  (231<= /sup>) represents the equator.  Values above that are north and below are sou= th.   Datatype: abstract: int32, IPP:integer, SM:xs:int

 

*new*

longitude (SM:Latitude):  The longitude of the center of the sphere described by the size attribute. = ; Expressed in thousandths of a second of arc.  The value 2147483648  (2= 31) represents the prime meridian.  Values above that are east and below a= re south.  The value is rounded away from the prime meridian   Datatype: abstract: int32, IPP:integer, SM:xs:int

 

*new*

altitude (SM:Altitude):  The a= ltitude of the center of the sphere described by the size attribute.  Expresse= d in centimeters from a base of 100,000m below the reference spheroid used by GPS [WGS 84].  Altitude above (or below) sea level may be used as an approximation of altitude relative to the [WGS 84] spheroid, though due to = the Earth's surface not being a perfect spheroid, there will be differences.    Datatype: abstract: int32, IPP:integer, SM:xs:int

 

Note:  There is disagreement on the semantics for all the attributes between what is posted on <http://pwg-wiki.wikispa= ces.com/Geolocation>  and what I have in the definition above.  I took the definition directly from rfc1876 (I think).  See included text from rfc1876 and t= he location example below. 

 

 

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com<= /font>
Voice: (585) 265-87= 55
FAX: (585) 265-7441=
US Mail: Peter Zehl= er
Xerox Corp.<= /font>
800 Phillips Rd.
M/S 128-25E<= /font>
Webster NY, 14580-9= 701

 

 

From rfc1876 section 2 <http://www.rfc-editor.or= g/rfc/rfc1876.txt>

 

SIZE   =       The diameter of a sphere enclosing the described entity, in

   &nbs= p;         centimeters, expressed as a pair of four-bit unsigned

   &nbs= p;         integers, each ranging from zero to nine, with the most

   &nbs= p;         significant four bits representing the base and the second

   &nbs= p;         number representing the power of ten by which to multiply=

             the base.  This allows sizes from 0e0 (<1cm) to 9e9

   &nbs= p;         (90,000km) to be expressed.  This representation was chosen=

   &nbs= p;         such that the hexadecimal representation can be read by

   &nbs= p;         eye; 0x15 =3D 1e5.  Four-bit values greater than 9 are

   &nbs= p;         undefined, as are values with a base of zero and a non-zero

   &nbs= p;         exponent.

 

   &nbs= p;         Since 20000000m (represented by the value 0x29) is greater

   &nbs= p;         than the equatorial diameter of the WGS 84 ellipsoid

   &nbs= p;         (12756274m), it is therefore suitable for use= as a

   &nbs= p;         "worldwide" size.

 

HORIZ PRE  &= nbsp; The horizontal precision of the data, in centimeters,

   &nbs= p;         expressed using the same representation as SIZE.  This is

   &nbs= p;         the diameter of the horizontal "circle of error", rather

          &nb=
sp;  than a "plus or minus" value.  (This was chosen to=
 match
             t=
he interpretation of SIZE; to get a "plus or minus" value,
             d=
ivide by 2.)
 
VERT PRE     The vertical precision of the data, in ce=
ntimeters,
             e=
xpressed using the sane representation as for SIZE.  This
             i=
s the total potential vertical error, rather than a "plus
             o=
r minus" value.  (This was chosen to match the<=
/font>
             i=
nterpretation of SIZE; to get a "plus or minus" value,=
             d=
ivide by 2.)  Note that if altitude above or below sea
             l=
evel is used as an approximation for altitude relative to=
             t=
he [WGS 84] ellipsoid, the precision value should be
             a=
djusted.
 
LATITUDE     The latitude of the center of the sphere =
described by the
             S=
IZE field, expressed as a 32-bit integer, most significant
             o=
ctet first (network standard byte order), in thousandths<=
/font>
             o=
f a second of arc.  2^31 represents the equator; numbers
             a=
bove that are north latitude.
 
LONGITUDE    The longitude of the center of the sphere desc=
ribed by the
             S=
IZE field, expressed as a 32-bit integer, most significant
             o=
ctet first (network standard byte order), in thousandths<=
/font>
             o=
f a second of arc, rounded away from the prime meridian.<=
/font>
             2=
^31 represents the prime meridian; numbers above that are=
             e=
ast longitude.
 
ALTITUDE     The altitude of the center of the sphere =
described by the
             S=
IZE field, expressed as a 32-bit integer, most significant
             o=
ctet first (network standard byte order), in centimeters,=
             f=
rom a base of 100,000m below the [WGS 84] reference
             s=
pheroid used by GPS (semimajor axis a=3D6378137.0,=
             r=
eciprocal flattening rf=3D298.257223563).  Altitude above
             (=
or below) sea level may be used as an approximation of
             a=
ltitude relative to the the [WGS 84] spheroid, though due=
             t=
o the Earth's surface not being a perfect spheroid, there=
             w=
ill be differences.  (For example, the geoid (which sea
             l=
evel approximates) for the continental US rang=
es from 10
             m=
eters to 50 meters below the [WGS 84] spheroid.
             A=
djustments to ALTITUDE and/or VERT PRE will be necessary<=
/font>
             i=
n most cases.  The Defense Mapping Agency publishes geoid
             h=
eight values relative to the [WGS 84] ellipsoid.
 

 

 

 

 

 

 

2-Dimmensional Location of my office printer

Google Map URL:

http://maps.google.com= /maps?f=3Dq&source=3Ds_q&hl=3Den&geocode=3D&q=3D800+phillip= s+rd+webster+ny+14580&sll=3D37.0625,-95.677068&sspn=3D62.226996,106= .962891&ie=3DUTF8&hq=3D&hnear=3D800+Phillips+Rd,+Webster,+Monro= e,+New+York+14580&ll=3D43.220973,-77.417162&spn=3D0.001781,0.003264= &t=3Dh&z=3D19

Location representations:<= /o:p>

Decimal Degrees (WGS84)

Latitude Longitude
43.220973 -77.417162

Degrees, Minutes & Seconds<= o:p>

Latitude Longitude
N43 13 15 W77 25 01

GPS

Latitude Longitude
N 43 13.258 W 77 25.030

UTM

 X Y =

18N 303685 4788191

 

My office elevation:

12800 centimeters (419 feet) above = sea level

Size of Printer:

91 centimeter (3 feet)

Margin of error

183 centimeter (6 feet)<= /span>

 

PrinterGeoLocation (RFC1876)

Size =3D 258 (0x0102) (encoded cent= imeter)
HorizontalPrecision =3D 514 (0x0202)  (encoded centimeter)
VerticalPrecision =3D 514 (0x0202)  (encoded centimeter)

Latitude =3D 2303079151 (thousandth= s of a second of arc, 231 represent equater)  ( (DecimalDegreeLatitude*60*60*1000)+2147483648 )

Longitude =3D 1868781865 (thousandt= hs of a second of arc, 231 represent prime meridian) ( 2147483648-(Decima= lDegreeLongitude*60*60*1000) )
Altitude =3D 10012800 (centimeter)  (OfficeElevation+10000000)

 

 


--
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_01CB37A6.3F74FFEF-- --===============2011592030== 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 --===============2011592030==-- From JorgeRickley@comcast.com Mon Aug 9 08:15:37 2010 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 CFF923A6986 for ; Mon, 9 Aug 2010 08:15:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -43.341 X-Spam-Level: X-Spam-Status: No, score=-43.341 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RATWARE_MS_HASH=1.398, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HEXOCTDWORD=2, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 kBoVVZsJEaYm for ; Mon, 9 Aug 2010 08:15:35 -0700 (PDT) Received: from 41-139-155-46.safaricombusiness.co.ke (41-139-155-46.safaricombusiness.co.ke [41.139.155.46]) by core3.amsl.com (Postfix) with ESMTP id 9C20D3A69DC for ; Mon, 9 Aug 2010 08:15:09 -0700 (PDT) Received: from 41-139-155-46.safaricombusiness.co.ke by mx2.comcast.com; Mon, 9 Aug 2010 18:15:43 +0300 From: To: Subject: Have more hard excitement with girls Date: Mon, 9 Aug 2010 18:15:43 +0300 Message-ID: <01cb37ee$e16025f0$2e9b8b29@comcast.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01CB37EE.E16B4980" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQK4skLrmM11wbiCsEHRfxAF6TMfH8== Content-Language: en X-OlkEid: 34F0C7053486EDA86729991C70C7053BB48DA8D3 ------=_NextPart_000_000C_01CB37EE.E16B4980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit If you are unable to see the message below, click here to view. Give her more sensations Paraguayan President Fernando Lugo has been diagnosed with lymphoma, a cancer affecting the immune system, Health Minister Esperanza Martinez said Friday in a news conference.But that was all. He was mostly out of sight, if not forgotten.With Slide, Google is scooping up a developer with an already well-established presence on Facebook, MySpace and other networks. Slide makes a number of popular social games like SuperPoke! Pets, Rock Riot, Top Friends and FunSpace.Brown, a Democrat who is running to replace Schwarzenegger, also weighed in on the controversial case.Stocks closed moderately lower Thursday as investors avoided big moves ahead of Friday's payrolls report.The dour jobs data added to concerns about the economic recovery, which is turning out to be less robust than many analysts had anticipated. In particular, investors are worried that consumer spe nding, the main engine powering the U.S. economy, will suffer as unemployment remains high.The Danish top seed will next play Russian qualifier Anna Chakvetadze, who beat Slovenian sixth seed Polona Hercog 6-4 6-3."The case was about the brain injury," said Kilpatrick. "Mark gets lost going to places he's gone all his life."Friday marked the 109th day since blowout preventer failed, after the explosion on the Deepwater Horizon that sank the rig and killed 11 workers.Jobs: The Labor Department reported that the economy lost 131,000 jobs last month, as the government shed 143,000 temporary workers hired for the decennial census. Economists polled by Briefing.com were expecting 87,000 job losses during the month.The two-year note's yield dropped below 0.5% for the first time ever Friday, but then pared back some of those losses to trade at 0.52% later in the dayObama has made public an unsigned "certification of live birth," which birthers claim is not the same as a birth certi ficate. However, two Honolulu, Hawaii, newspapers have presented birth announcements for Obama, and the state's Republican governor has confirmed that the president was born in the Aloha State."It's clear they want to hold hostage tax cuts for the middle class for their desire for more tax cuts for the wealthy," countered Jim Manley, spokesman for Democratic Senate Leader Harry Reid. Copy © 2010 VficneOWyUrM . All rights reserved. Unsubscribe ------=_NextPart_000_000C_01CB37EE.E16B4980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

If you are unable to see the message below, click here to view.

Give her more sensation= s
Paraguayan President Fernando Lugo has been diagnosed with lymphoma, a ca= ncer affecting the immune system, Health Minister Esperanza Martinez said= Friday in a news conference.
But that was all. He was mostly out of sight, if not forgotten.
With Slide, Google is scooping up a developer with an already well-establ= ished presence on Facebook, MySpace and other networks. Slide makes a num= ber of popular social games like SuperPoke! Pets, Rock Riot, Top Friends = and FunSpace.
Brown, a Democrat who is running to replace Schwarzenegger, also weighed = in on the controversial case.
Stocks closed moderately lower Thursday as investors avoided big moves ah= ead of Friday's payrolls report.
The dour jobs data added to concerns about the economic recovery, which i= s turning out to be less robust than many analysts had anticipated. In pa= rticular, investors are worried that consumer spending, the main engine p= owering the U.S. economy, will suffer as unemployment remains high.
The Danish top seed will next play Russian qualifier Anna Chakvetadze, wh= o beat Slovenian sixth seed Polona Hercog 6-4 6-3.
"The case was about the brain injury," said Kilpatrick. "Mark gets lost g= oing to places he's gone all his life."
Friday marked the 109th day since blowout preventer failed, after the exp= losion on the Deepwater Horizon that sank the rig and killed 11 workers.<= br /> Jobs: The Labor Department reported that the economy lost 131,000 jobs la= st month, as the government shed 143,000 temporary workers hired for the = decennial census. Economists polled by Briefing.com were expecting 87,000= job losses during the month.
The two-year note's yield dropped below 0.5% for the first time ever Frid= ay, but then pared back some of those losses to trade at 0.52% later in t= he day
Obama has made public an unsigned "certification of live birth," which bi= rthers claim is not the same as a birth certificate. However, two Honolul= u, Hawaii, newspapers have presented birth announcements for Obama, and t= he state's Republican governor has confirmed that the president was born = in the Aloha State.
"It's clear they want to hold hostage tax cuts for the middle class for t= heir desire for more tax cuts for the wealthy," countered Jim Manley, spo= kesman for Democratic Senate Leader Harry Reid.

Copy © 2010 VficneOWyUrM . All rights reserved.

Unsubscribe

------=_NextPart_000_000C_01CB37EE.E16B4980-- From pwg-announce-bounces@pwg.org Mon Aug 9 13:59:44 2010 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 A72B83A69B8 for ; Mon, 9 Aug 2010 13:59:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.799 X-Spam-Level: X-Spam-Status: No, score=-100.799 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_50=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 zFzXQ8IR1Zih for ; Mon, 9 Aug 2010 13:59:43 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 7558A3A69B9 for ; Mon, 9 Aug 2010 13:59:43 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 4290D79384; Mon, 9 Aug 2010 17:00:04 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by pwg.org (Postfix) with ESMTP id 274CD79383 for ; Mon, 9 Aug 2010 16:59:59 -0400 (EDT) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 4180DA259D45 for ; Mon, 9 Aug 2010 13:59:59 -0700 (PDT) X-AuditID: 11807134-b7b5eae00000345f-ea-4c606c4f4f32 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id C0.2C.13407.F4C606C4; Mon, 9 Aug 2010 13:59:59 -0700 (PDT) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 9 Aug 2010 13:59:58 -0700 To: pwg-announce@pwg.org Message-Id: <6B909B31-862B-4B63-8D14-32A7134157C1@apple.com> Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August 2010) 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: 4290D79384.AC2A9 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Greetings: This email initiates the Formal Approval vote by the PWG membership on the = PWG MFD Requirements, which is located at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.pdf The complete list of PWG Last Call issues and resolutions is located at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-resolution-= 20100722.txt The voting period will open today on Monday 9 August 2010 and will close at= 10pm (US Pacific Time) on Tuesday 31 August 2010. Valid votes are: Yes, No, No (with Strong Objection), Abstain. Representatives from PWG member companies are strongly encouraged to exerci= se their right to vote. PWG Privacy Policy: Your vote is confidential and will not be disclosed by= PWG officers or document editors. To vote, send an email with *exactly* the following subject line format: MFD Requirements Formal Vote--- Example: MFD Requirements Formal Vote-Acme-McGee-Yes Any "No" vote MUST state the reason for the "No" vote and MUST contain a de= scription of the *technical* changes required to turn the "No" vote into a = "Yes" vote - otherwise such a "No" vote will NOT be counted. Any "No" vote= MUST NOT contain *editorial* comments, per the PWG Process/3.0. Any "Yes" vote MAY contain "editorial" comments but MUST NOT contain any *t= echnical* comments, per the PWG Process/3.0. Please send your vote to all of the following email addresses (replacing "d= ot" with '.' and "at" with '@'): msweet"at"apple"dot"com (PWG Chair) ptykodi"at"tykodi"dot"com (PWG Secretary)=20 Peter"dot"Zehler"at"xerox"dot"com (MFD WG Chair) wamwagner"at"comcast"dot"net (MFD Requirements Editor) Please do NOT simply reply to this note on PWG-Announce (to preserve the co= nfidentiality of your vote). Note: (1) This Formal Vote is being conducted under the rules of the PWG Process/= 3.0 and the current PWG Policy on Intellectual Property and Confidentiality= agreement. The 2010 PWG Membership Agreement calls out both of these docum= ents and the links are provided below. (2) To be eligible to vote the member MUST have submitted a signed copy of = the 2010 PWG Membership Agreement and paid their dues. The PWG Definition of the Standards Development Process Version 3.0 is loca= ted at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf The PWG Policy on Intellectual Property and Confidentiality is located at: http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf Regards, Michael Sweet (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 abundances6170@rayan.com Wed Aug 11 12:20:17 2010 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 C67453A68DB; Wed, 11 Aug 2010 12:20:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.484 X-Spam-Level: X-Spam-Status: No, score=-0.484 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DOS_OE_TO_MX=2.75, FUZZY_VPILL=0.687, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, STOX_REPLY_TYPE=0.001, TVD_FINGER_02=2.134, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 cFTDuGwMDani; Wed, 11 Aug 2010 12:20:16 -0700 (PDT) Received: from chello080108242064.3.14.vie.surfer.at (chello080108242064.3.14.vie.surfer.at [80.108.242.64]) by core3.amsl.com (Postfix) with ESMTP id 73EC03A688C; Wed, 11 Aug 2010 12:20:16 -0700 (PDT) Message-ID: <000d01cb398a$4eb6bd20$6400a8c0@abundances6170> From: To: Subject: The pill form gives you a unique sophistication that makes you ever ready for STEAMY, HOT SEX anytime, anywhere... Date: Wed, 11 Aug 2010 21:20:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam: Not detected ViaGrow is the only 100% herbal formula that works even with alcohol http://lightseel.ru From ipp-bounces@pwg.org Fri Aug 13 11:51:37 2010 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 B41723A6943 for ; Fri, 13 Aug 2010 11:51:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.758 X-Spam-Level: X-Spam-Status: No, score=-100.758 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_40=-0.185, 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 MSTZMQmu3nHX for ; Fri, 13 Aug 2010 11:51:36 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 83F5A3A6359 for ; Fri, 13 Aug 2010 11:51:33 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2DB13792FD; Fri, 13 Aug 2010 14:52:05 -0400 (EDT) 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 AC61A7924D for ; Fri, 13 Aug 2010 14:52:00 -0400 (EDT) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id 0877AA90A330 for ; Fri, 13 Aug 2010 11:52:00 -0700 (PDT) X-AuditID: 11807134-b7b5eae00000345f-94-4c65944fdf33 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 25.EF.13407.F44956C4; Fri, 13 Aug 2010 11:51:59 -0700 (PDT) From: Michael Sweet Date: Fri, 13 Aug 2010 11:51:59 -0700 To: ipp@pwg.org Message-Id: <164D2861-0C68-4826-9E86-43FE21C343ED@apple.com> Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] IPP Face-to-face Minutes Posted for August F2F 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="===============0099274899==" 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: 2DB13792FD.A89A7 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0099274899== Content-Type: multipart/alternative; boundary=Apple-Mail-4-623125590 --Apple-Mail-4-623125590 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii All, I've posted the minutes for the IPP face-to-face meeting at: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20100805.pdf Apologies for the delay; for some reason I thought I had posted them alread= y... ________________________________________________________________________ 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-4-623125590 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii All,

I'= ve posted the minutes for the IPP face-to-face meeting at:


Apologies for the = delay; for some reason I thought I had posted them already...
___________________= _____________________________________________________
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-4-623125590-- --===============0099274899== 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 --===============0099274899==-- From ipp-archive@lists.ietf.org Fri Aug 20 04:54:35 2010 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 4548D3A6924 for ; Fri, 20 Aug 2010 04:54:35 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): From: USA VIAGRA \256 Official ; Fri, 20 Aug 2010 04:54:28 -0700 (PDT) Received: from HS2-22-128.xG.SPb.SkyLink.RU (HS2-22-128.xG.SPb.SkyLink.RU [89.253.22.128]) by core3.amsl.com (Postfix) with ESMTP id 949833A687C for ; Fri, 20 Aug 2010 04:54:27 -0700 (PDT) Received: (qmail 2564 by uid 191); Fri, 20 Aug 2010 15:51:36 +0400 Message-Id: <20100820155136.2566.qmail@HS2-22-128.xG.SPb.SkyLink.RU> From: USA VIAGRA Official To: ipp-archive@lists.ietf.org Subject: ipp-archive@lists.ietf.org VIAGRA Official Seller -34% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Date: Fri, 20 Aug 2010 04:54:27 -0700 (PDT)
Click here to view as a web page.

View image in browser now
To ipp-archive@lists.ietf.org | Privacy Policy | Contact Us

Copyright 2010 All rights reserved.
From ipp-archive@megatron.ietf.org Fri Aug 20 04:54:35 2010 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 511A63A687C for ; Fri, 20 Aug 2010 04:54:35 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): From: USA VIAGRA \256 Official ; Fri, 20 Aug 2010 04:54:28 -0700 (PDT) Received: from HS2-22-128.xG.SPb.SkyLink.RU (HS2-22-128.xG.SPb.SkyLink.RU [89.253.22.128]) by core3.amsl.com (Postfix) with ESMTP id 8E3A93A68AE for ; Fri, 20 Aug 2010 04:54:27 -0700 (PDT) Received: (qmail 2564 by uid 191); Fri, 20 Aug 2010 15:51:36 +0400 Message-Id: <20100820155136.2566.qmail@HS2-22-128.xG.SPb.SkyLink.RU> From: USA VIAGRA Official To: ipp-archive@megatron.ietf.org Subject: ipp-archive@megatron.ietf.org VIAGRA Official Seller -34% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Date: Fri, 20 Aug 2010 04:54:27 -0700 (PDT)
Click here to view as a web page.

View image in browser now
To ipp-archive@megatron.ietf.org | Privacy Policy | Contact Us

Copyright 2010 All rights reserved.
From pwg-announce-bounces@pwg.org Fri Aug 20 13:52:40 2010 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 931D33A693A for ; Fri, 20 Aug 2010 13:52:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.688 X-Spam-Level: X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[AWL=0.311, BAYES_00=-2.599, J_CHICKENPOX_93=0.6] 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+2TwHEu9NQr for ; Fri, 20 Aug 2010 13:52:39 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 62EBD3A6881 for ; Fri, 20 Aug 2010 13:52:39 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E36A07931F; Fri, 20 Aug 2010 16:53:07 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 160407919E for ; Fri, 20 Aug 2010 16:53:03 -0400 (EDT) Received: by vws3 with SMTP id 3so3536576vws.5 for ; Fri, 20 Aug 2010 13:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=F/XX2n0BOnc93jGFTChTrTjtjBJqfo+OqZR/uPGEMvg=; b=dzya+I74eDd8KmDUp4W2rQ0iXCrfJEXW6sVX3lI/v2PtIGDLba2ZxibtoQmYB2zNGb ogg7LVbvT+iA7hw5FbS2IHxG5GMS5zQA8dY5RiUhcQXQY/GP06lFe7X6h1GnUcEeGWI+ cVhnlyuHWuEEvRwfhJKq5NAW2McelrDITQ9Ps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=wYLXydNeUbFfv8NE2IuppRRmcAMHwVn5ldd9g1SoPiCfV0mkZk6LccGkdVujp50wub yQKd1OshktsDHEzVy8ub8E/PK4daRSaqk8XjfJdDvZIAacewikMiHTHTt6Y4NgRmZj+G hijHb0o8wWpA5IssQiLtmzwOI7DGmNaxlVlEQ= MIME-Version: 1.0 Received: by 10.220.62.136 with SMTP id x8mr1152653vch.177.1282337583194; Fri, 20 Aug 2010 13:53:03 -0700 (PDT) Received: by 10.220.199.204 with HTTP; Fri, 20 Aug 2010 13:53:03 -0700 (PDT) Date: Fri, 20 Aug 2010 16:53:03 -0400 Message-ID: From: Ira McDonald To: pwg-announce@pwg.org, Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Transport Model for SNMP 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: E36A07931F.ACAC5 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Hi, The long-awaited enterprise network-friendly way to deploy SNMP authentication and security using TLS and DTLS. Recommended reading. Cheers, - Ira ---------- Forwarded message ---------- From: Date: Fri, Aug 20, 2010 at 2:14 PM Subject: [Isms] RFC 5953 on Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Cc: isms@ietf.org, rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. =A0 =A0 =A0 =A0RFC 5953 =A0 =A0 =A0 =A0Title: =A0 =A0 =A0Transport Layer Security (TLS) Transport =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Model for the Simple Network Managem= ent =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Protocol (SNMP) =A0 =A0 =A0 =A0Author: =A0 =A0 W. Hardaker =A0 =A0 =A0 =A0Status: =A0 =A0 Standards Track =A0 =A0 =A0 =A0Stream: =A0 =A0 IETF =A0 =A0 =A0 =A0Date: =A0 =A0 =A0 August 2010 =A0 =A0 =A0 =A0Mailbox: =A0 =A0ietf@hardakers.net =A0 =A0 =A0 =A0Pages: =A0 =A0 =A065 =A0 =A0 =A0 =A0Characters: 147393 =A0 =A0 =A0 =A0Updates/Obsoletes/SeeAlso: =A0 None =A0 =A0 =A0 =A0I-D Tag: =A0 =A0draft-ietf-isms-dtls-tm-14.txt =A0 =A0 =A0 =A0URL: =A0 =A0 =A0 =A0http://www.rfc-editor.org/rfc/rfc5953.txt This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. =A0The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. =A0This document describes how the TLS Transport Model (TLSTM) implements the needed features of a SNMP Transport Subsystem to make this protection possible in an interoperable way. This Transport Model is designed to meet the security and operational needs of network administrators. =A0It supports the sending of SNMP messages over TLS/TCP and DTLS/UDP. =A0The TLS mode can make use of TCP's improved support for larger packet sizes and the DTLS mode provides potentially superior operation in environments where a connectionless (e.g., UDP) transport is preferred. =A0Both TLS and DTLS integrate well into existing public keying infrastructures. This document also defines a portion of the Management Information Base (MIB) for use with network management protocols. =A0In particular, it defines objects for managing the TLS Transport Model for SNMP. [STANDARDS TRACK] This document is a product of the Integrated Security Model for SNMP Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. =A0Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. =A0Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see =A0http://www.ietf.org/mailman/listinfo/ietf-announce =A0http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. =A0Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ Isms mailing list Isms@ietf.org https://www.ietf.org/mailman/listinfo/isms --=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 Sat Aug 21 10:43:05 2010 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 2D93F3A67F9 for ; Sat, 21 Aug 2010 10:43:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.712 X-Spam-Level: X-Spam-Status: No, score=-0.712 tagged_above=-999 required=5 tests=[AWL=-0.713, BAYES_50=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 WF597ABP20qz for ; Sat, 21 Aug 2010 10:43:03 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A81BA3A68BC for ; Sat, 21 Aug 2010 10:43:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 685A579336; Sat, 21 Aug 2010 13:43:32 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id C24A379334 for ; Sat, 21 Aug 2010 13:43:28 -0400 (EDT) Received: by vws3 with SMTP id 3so4184453vws.5 for ; Sat, 21 Aug 2010 10:43:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=HgjjtCArSUoUrNjKH+2fcLgNBGpLxQaHdFyDv5/orJI=; b=CC/Ppdp+pjTsspT6rNArC+4+rdJb7NULN/IJm/7oHfENDiv1sx7b5QPAqiR80I4xPE xH1wOwbxl9VrXrn0vJF3T+0t3/7DsCVQP+fAEc5ug9jgL7dEKOiObAFPLSaTWKsEOG4x cgdJyy25RZVaxR2OGyH2u97mBPZ67EWbFXtPU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=skN1Zgm4wEVB9dYblO+ulmZPm4oFmRTRcni3XAKtJRob3Edeu0OM2mtQxVM4CTN71x nncqrl9O9ChGAP4dDkd+6+3msZwFD1aUOcsSYhNVzQ4ziPP2LaDaO1sy6b1MkOFz7isP 7Lb1hLklU+X7CMr3KuULfQnLbhn8aZF4Lwv7g= MIME-Version: 1.0 Received: by 10.220.95.10 with SMTP id b10mr1794350vcn.204.1282412608217; Sat, 21 Aug 2010 10:43:28 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 10:43:28 -0700 (PDT) Date: Sat, 21 Aug 2010 13:43:28 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , "Zehler, Peter" , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Proposal for mapping Printer MIB into IPP 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: 685A579336.A7A93 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, Saturday (21 August 2010) Per my action item from our August 2010 PWG Meeting, here is my proposal for a new IPP spec called "IPP Printer Device Extensions". Since the complete ABNF and mapping rules for all 170+ objects defined in the Printer MIB will be fairly long, I suggest that this should be in a separate IPP spec and not simply included in "IPP Everywhere" spec. Comments? Cheers, - Ira ------------------------------------------------------------------------ Approach: - Avoid use of new Object (e.g., Device) or Collection to reduce cost for lightweight mobile implementations of IPP Clients - Follow style of IPP PSX mapping of prtAlertTable, i.e., array of text parameters in "printer-alert" representing most columns and separate attributes like "printer-alert-description" for string MIB objects - Convert all enumerated values from Printer MIB into IANA registered string names, e.g., "prtChannelType" of "38" maps to "chBidirPortTCP" - Map bit masks, e.g., "prtChannelStatus (PrtSubUnitStatusTC), directly as integers (because string encoding in IPP is too verbose) Pros: - Simple human-readable text encoding - Lightweight (no new attribute groups, objects, etc.) - High fidelity mapping from Printer MIB objects to IPP attributes Cons: - Like "printer-alert", maps a *single* physical output device onto an IPP Printer object - Note that this precedent was already established with "printer-alert" which has shipped in CUPS and various printers for several years Examples: printer-channel[1] = "index=1;type=chBidirPortTCP;jclIndex=0;pdlIndex=1; state=printDataAccepted;ifIndex=3;status=0;" printer-channel-version[1] = "Bi-Directional Raw TCP/IP Printing" printer-channel-info[1] = "Port=9100" printer-marker[1] = "index=1;markTech=inkjetAqueous;counterUnit=impressions; lifeCount=23412;powerOnCount=479;processColorants=4; spotColorants=0;addressUnit=tenThousandthsOfInches; addressFeedDir=600;addressXFeedDir=600; northMargin=1066;southMargin=1066;eastMargin=1066;westMargin=1066; status=0;" ------------------------------------------------------------------------ -- 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 Sat Aug 21 10:58:56 2010 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 C52143A67F9 for ; Sat, 21 Aug 2010 10:58:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.961 X-Spam-Level: X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599] 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 hppZ+4Wk0veK for ; Sat, 21 Aug 2010 10:58:55 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 68D603A6915 for ; Sat, 21 Aug 2010 10:58:55 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6520479336; Sat, 21 Aug 2010 13:59:16 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id D85B879335; Sat, 21 Aug 2010 13:59:10 -0400 (EDT) Received: by vws3 with SMTP id 3so4191538vws.5 for ; Sat, 21 Aug 2010 10:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oEauAJCmDakU70Q11jbKBt2Zr0eMTJp9IASeyWWRwug=; b=mGSk8ddkq7h/n2ky6YMF0u8VTb/G5hNy77fYlajltkDh3xUYjlBcistISsA3SZdojx 9+FLlyXIdTvyGxov1PdlqhwV5rDcv+E3sqvEQPV6g/WvgPAnp6Dkt8Qfvig1F7TOvF+l FJrUQHpAeQoF7acifvuzTZbPpYKJG/vgc6TG4= 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:content-transfer-encoding; b=EcQLAp3L0gRBZJxsOEBmrc0U6go9Nc5jACudt3+85tc4KRnI4LzmEZLvkv/bblLD93 OnXywutrtm89aqjZFL5okTluB65wvbi6JLofpxWG2p0FrmwIiXLR+7we2eNl4Rp2VeJN Sjc3PKJ3MENriN8tjuAEWslgZxWvM5UzLSRxw= MIME-Version: 1.0 Received: by 10.220.124.198 with SMTP id v6mr1880148vcr.27.1282413550016; Sat, 21 Aug 2010 10:59:10 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 10:59:09 -0700 (PDT) In-Reply-To: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> References: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> Date: Sat, 21 Aug 2010 13:59:09 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org Subject: [IPP] Re: PWG Last Call of IPP JPS2 (26 July to 27 August 2010) 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: 6520479336.A7F69 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, Reminder that this PWG Last Call for IPP JPS2 will end this coming Friday (27 August 2010). Please take the time to review this document and send your acknowledgment as described below, so that we can achieve the quorum required by the PWG Process/3.0 in order to exit from PWG Last Call. Thanks, - Ira McDonald (IPP editor) On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > =A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-cl= ean.pdf > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. =A0The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: =A0ipp@pwg.org > Subject: =A0 has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: =A0The PWG Definition of the Standards Development Process Version = 3.0 > is located at: > > =A0http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > --=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 pwg-announce-bounces@pwg.org Sat Aug 21 10:58:59 2010 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 2138A3A6915 for ; Sat, 21 Aug 2010 10:58:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.004 X-Spam-Level: X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[AWL=0.595, BAYES_00=-2.599] 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 X30VHAcaf+Km for ; Sat, 21 Aug 2010 10:58:58 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 32D293A67F9 for ; Sat, 21 Aug 2010 10:58:58 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id F1CA579342; Sat, 21 Aug 2010 13:59:16 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id D85B879335; Sat, 21 Aug 2010 13:59:10 -0400 (EDT) Received: by vws3 with SMTP id 3so4191538vws.5 for ; Sat, 21 Aug 2010 10:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oEauAJCmDakU70Q11jbKBt2Zr0eMTJp9IASeyWWRwug=; b=mGSk8ddkq7h/n2ky6YMF0u8VTb/G5hNy77fYlajltkDh3xUYjlBcistISsA3SZdojx 9+FLlyXIdTvyGxov1PdlqhwV5rDcv+E3sqvEQPV6g/WvgPAnp6Dkt8Qfvig1F7TOvF+l FJrUQHpAeQoF7acifvuzTZbPpYKJG/vgc6TG4= 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:content-transfer-encoding; b=EcQLAp3L0gRBZJxsOEBmrc0U6go9Nc5jACudt3+85tc4KRnI4LzmEZLvkv/bblLD93 OnXywutrtm89aqjZFL5okTluB65wvbi6JLofpxWG2p0FrmwIiXLR+7we2eNl4Rp2VeJN Sjc3PKJ3MENriN8tjuAEWslgZxWvM5UzLSRxw= MIME-Version: 1.0 Received: by 10.220.124.198 with SMTP id v6mr1880148vcr.27.1282413550016; Sat, 21 Aug 2010 10:59:10 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 10:59:09 -0700 (PDT) In-Reply-To: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> References: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> Date: Sat, 21 Aug 2010 13:59:09 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org Subject: [Pwg-Announce] Re: PWG Last Call of IPP JPS2 (26 July to 27 August 2010) 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: F1CA579342.ABD91 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Hi, Reminder that this PWG Last Call for IPP JPS2 will end this coming Friday (27 August 2010). Please take the time to review this document and send your acknowledgment as described below, so that we can achieve the quorum required by the PWG Process/3.0 in order to exit from PWG Last Call. Thanks, - Ira McDonald (IPP editor) On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > =A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-cl= ean.pdf > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. =A0The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: =A0ipp@pwg.org > Subject: =A0 has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: =A0The PWG Definition of the Standards Development Process Version = 3.0 > is located at: > > =A0http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > --=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 Sat Aug 21 14:05:21 2010 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 4EA0C3A68CC for ; Sat, 21 Aug 2010 14:05:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.041 X-Spam-Level: X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558, BAYES_00=-2.599] 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 OY98Y4LL5h6B for ; Sat, 21 Aug 2010 14:05:20 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id E52883A67FE for ; Sat, 21 Aug 2010 14:05:19 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BA79A79341; Sat, 21 Aug 2010 17:05:44 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 01A1279341 for ; Sat, 21 Aug 2010 17:05:13 -0400 (EDT) Received: by vws3 with SMTP id 3so4275425vws.5 for ; Sat, 21 Aug 2010 14:05:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=7Y3bzuDBw/QGdRkqehK5HWvFW1D/9o+puVw9r4jtRy4=; b=jwyZVuelT32G+uhtFyOBfxT4vSjekS+IPaKLXc+E1CCRVTW0SJTT/qS4P6dSBlvQ1W A0FjV/aelsXKYT/VS08n44NrHf9aSBhFUWtaRuMM0p1PVsireA/urxsfkVEEjlhRI15+ hFHnTlaRUu/H2zwmuNMrjMPI47UQiioiGr8NY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Pe9jG+yeofUujKyWIrs37V1j+WhhPkh0D/QBx8lYy056YiR7z65wB1MlHyWRpH6ZNP uNIRQF24vabdAiKeAKtoPNdbRR1bEgqJfhgJLI6NhvF50Mjb3+GPXMbpPs8m7KwH3jTh AMOjGSxiHezC7gx7Ug29bg5+ZeWoy1YzyYVgg= MIME-Version: 1.0 Received: by 10.220.49.202 with SMTP id w10mr1975854vcf.70.1282424713163; Sat, 21 Aug 2010 14:05:13 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 14:05:13 -0700 (PDT) Date: Sat, 21 Aug 2010 17:05:13 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Stable Draft of IPP/2.0 Second Edition (21 August 2010) 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: BA79A79341.A86CF X-pwg-MailScanner-From: ipp-bounces@pwg.org [Based on IPP WG complete review on 5 August - for review at IPP WG meeting on 21 August and IPP WG Last Call] I've just posted a Stable draft of IPP/2.0 Second Edition at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821.pdf / doc - clean copy with line numbers ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821-rev.pdf / doc - redlines from 18 July draft Prototype reports for IPP/2.2 new content already exist. So this spec is ready for final review, IPP WG last call, and PWG Last Call. Comments? Cheers, - Ira ---------------------------------------------------------------------------= --- Changes made to create 21 August 2010 version (Stable Draft) Editorial =96 Changed status to Stable Draft =96 all changes below per IPP WG review at August F2F Editorial =96 Revised Table 1 in section 4, to move 3 TLS versions together at end, add note that empty cells mean OPTIONAL, and extend non-OPTIONAL levels to the right Editorial =96 Revised Tables 4 and 5 in section 5 to remove gray background on IPP/1.1 rows Editorial =96 Revised all Tables to make heading rows repeat (across pages) Editorial =96 Revised Table 6 in section 6.1 to add operation-id, request-id, status-code, and version-number as REQUIRED parameters in all operation requests and/or responses Editorial =96 Revised Table 6 in section 6.1 to make requested-attributes and requesting-user-name apply to All objects Editorial =96 Revised Table 7 in section 6.2 to change =93CONDITIONAL=94 to =93REQUIRED for color=94 Editorial =96 Global =96 Changed =93STRONGLY RECOMMENDED=94 to =93RECOMMENDED=94 Editorial =96 Revised Acknowledgments table, adding and correcting several rows --=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 Sat Aug 21 14:10:34 2010 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 4ECEB3A6942 for ; Sat, 21 Aug 2010 14:10:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.074 X-Spam-Level: X-Spam-Status: No, score=-2.074 tagged_above=-999 required=5 tests=[AWL=0.525, BAYES_00=-2.599] 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 Iw6NqsZLggj9 for ; Sat, 21 Aug 2010 14:10:29 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id AB1EA3A68CC for ; Sat, 21 Aug 2010 14:10:26 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 81C9A79355; Sat, 21 Aug 2010 17:10:52 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 1E13579351 for ; Sat, 21 Aug 2010 17:10:48 -0400 (EDT) Received: by vws3 with SMTP id 3so4277847vws.5 for ; Sat, 21 Aug 2010 14:10:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=Hs44VR/ZlhZi0U+ohkvSR8pgv6phpif4q+v0e2QebjM=; b=NtwOEAtJl+om8eqxrQRdFr2MHHDqBUVhPIlwy/lt65EvX6maI4XuVlQRUt4BWwyOWp uaTgWCfZs62IO4RzdXAak+NNr6LZDd4xplHTaf2s6O/mnrbSGer1ZW9djOhw74+lIbqh cWX/96vqp/8vW8gn5iozDCOkjpNDO9pNfIAV0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=M35gq3CXHhxS24uA/NcGJQem2ZO/Pl1vK9Wl19FoRFigY7nW2DYqb3pnMY9WcZCkDy 2b5a5Lq/97xvuv/h0Drv0bhsZOzKMoUIXy/+P/7mIc8IjSfyklCjGcQpg/OVCG0CHxTH PGEKtThr9wgsf5eMoJUKCFeSDGxtnLHR7Ko5Y= MIME-Version: 1.0 Received: by 10.220.71.136 with SMTP id h8mr1903411vcj.275.1282425048589; Sat, 21 Aug 2010 14:10:48 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 14:10:48 -0700 (PDT) Date: Sat, 21 Aug 2010 17:10:48 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Tom Hastings , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - 4pm EDT Monday 21 August 2010 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: 81C9A79355.A839B X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, [as planned at our August F2F] Reminder of our next IPP WG call: Monday 21 August - 1-2pm PDT / 4-5pm EDT 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 - move IPP/2.0 SE into IPP WG Last Call *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from last meeting (August F2F) - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20100805.pdf (3) Status of IPP Version 2.0 Second Edition (Ira) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821-rev.pdf (new Stable draft for IPP WG last call - no open issues) (4) Status of PWG Last Call on IPP JPS2 (Tom) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-cle= an.pdf (ends Friday 27 August) (5) Review of IPP Printer Device Extensions proposal (Ira) - email proposal sent on 21 August (6) Status of IPP Everywhere Project (Mike/Ira) - ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-august-10.pdf (other pending action items?) (7) Next Steps - IPP WG - Monday 13 September (Monday 6th is Labor Day) - IPP/2.0 SE into IPP WG Last Call? - IPP JPS2 into PWG Formal Vote? Cheers, - Ira (IPP co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: =A0 579 Park Place=A0 Saline, MI=A0 48176 =A0 734-944-0094 summer: =A0 PO Box 221=A0 Grand Marais, MI 49839 =A0 906-494-2434 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Sat Aug 21 16:06:57 2010 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 945AB3A6955 for ; Sat, 21 Aug 2010 16:06:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.088 X-Spam-Level: X-Spam-Status: No, score=-102.088 tagged_above=-999 required=5 tests=[AWL=0.511, 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 a3oR8IU9xamX for ; Sat, 21 Aug 2010 16:06:56 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 99B613A6961 for ; Sat, 21 Aug 2010 16:06:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1B46679366; Sat, 21 Aug 2010 19:07:25 -0400 (EDT) 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 E680A79363 for ; Sat, 21 Aug 2010 19:07:21 -0400 (EDT) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 056D2AA89E9F for ; Sat, 21 Aug 2010 16:07:21 -0700 (PDT) X-AuditID: 11807137-b7c08ae00000377a-91-4c705c28ba89 Received: from [17.151.98.197] (Unknown_Domain [17.151.98.197]) (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 E6.E0.14202.82C507C4; Sat, 21 Aug 2010 16:07:20 -0700 (PDT) From: Michael Sweet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 21 Aug 2010 16:07:20 -0700 To: ipp@pwg.org Message-Id: Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Apple has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 1B46679366.A80BA X-pwg-MailScanner-From: ipp-bounces@pwg.org ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Sat Aug 21 17:16:18 2010 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 7E2A83A6818 for ; Sat, 21 Aug 2010 17:16:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599] 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 b7Oz8N4fwpWN for ; Sat, 21 Aug 2010 17:16:17 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 0AFB93A6403 for ; Sat, 21 Aug 2010 17:16:17 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id EE27279352; Sat, 21 Aug 2010 20:16:44 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 52BA77932B for ; Sat, 21 Aug 2010 20:16:41 -0400 (EDT) Received: by vws3 with SMTP id 3so4348602vws.5 for ; Sat, 21 Aug 2010 17:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=bqYNCej8VqkD1kysoBwgjhv+NecB0WCvUGjZZ3nh844=; b=OFltN22s+imKrAqXmDCao/XKonGVMP/F5K6wqmIsBJVy3HWK0nU0NJEELE1iFR5NeK FWfOBXNUFv3junQpA1uUJVsh3Yksxe6Cz1GXOZBqPZA/dXx9FV7SKdhJNvjWy7D4Meso +l/IWhkDFydpTpRkaxw0TbJ3NUyYjvVmXut7s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ngiQqETC6PXvsLe2eB3jtmil6/2gkTPyPzoYwRtAP29VpstFKJodb3zpj8Os8sokgJ rYxBEmHoNkF4k4XRPmT1nSAxv5vQdDiI2wwR7hNA+oomXrLNCXcyNjatENIbx7Uk7LXO RYuturhQfEA5DEqoH1pF2ZaX+RLZAGngEztp0= MIME-Version: 1.0 Received: by 10.220.59.5 with SMTP id j5mr1988898vch.230.1282436200440; Sat, 21 Aug 2010 17:16:40 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sat, 21 Aug 2010 17:16:40 -0700 (PDT) Date: Sat, 21 Aug 2010 20:16:40 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] High North has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: EE27279352.A7EB1 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, Good job Tom! Cheers, - Ira McDonald (President, High North) -- 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 Sun Aug 22 09:58:48 2010 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 073553A691A for ; Sun, 22 Aug 2010 09:58:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.129 X-Spam-Level: X-Spam-Status: No, score=-2.129 tagged_above=-999 required=5 tests=[AWL=0.470, BAYES_00=-2.599] 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 RBTrWreM7xWm for ; Sun, 22 Aug 2010 09:58:47 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id E220D3A6888 for ; Sun, 22 Aug 2010 09:58:46 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 426697936D; Sun, 22 Aug 2010 12:59:14 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id E8F5A7936B for ; Sun, 22 Aug 2010 12:59:09 -0400 (EDT) Received: by vws3 with SMTP id 3so4714467vws.5 for ; Sun, 22 Aug 2010 09:59:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=YMlH7g4SvcbifvVOJ9pY1Omr+ScTYlAXO7VN3LGHdO0=; b=C1JhjjQ10hH8yifkkmNiX6nj0bUmzHrCwfTLvL60+rTX+lQ/k623CcCvCZISOdOWCm tAl7owpaezPHjSLqRnXi3/Y9JhhWoYaAOmiDH2BO3Px4M/Rrspww+fPFws8VUKzRR+uF 9NV2rgXMsX5PFlrbhc8nsUnzkr7CYO2LB2EaM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jNMTuwNaBULOdWqGyEM3JNK8QHpg0e7pUNIe5OwML3CZ/JPw6ZmfKEMt11tHf94fA2 D9tyAisM1g09n83dZ9A8V0y07I7DXvnNqAZAOS8pgBZsHLxBIPgiYYl2wfFJfo1BtYsk Bx3m+ArWm3R93r1cI0dzQlVo7i1x4q+pK94y4= MIME-Version: 1.0 Received: by 10.220.60.204 with SMTP id q12mr2559821vch.181.1282496349511; Sun, 22 Aug 2010 09:59:09 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Sun, 22 Aug 2010 09:59:09 -0700 (PDT) Date: Sun, 22 Aug 2010 12:59:09 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Proposal for IPP organizational attributes 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: 426697936D.A8853 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, Sunday (22 August 2010) Per my action item from our August 2010 PWG Meeting, here is my proposal for two IPP organizational location attributes that are REQUIRED (same as "printer-location" in IPP/2.0 conformance level) for inclusion in the "IPP Everywhere" spec. The proposed approach is to use LDAP User Schema [RFC4519] / ITU-T X.520 directory attributes. Comments? Cheers, - Ira McDonald (IPP co-editor) ------------------------------------------------------------------------ IPP Organizational Location Attributes printer-organization (text(127)) This REQUIRED Printer attribute specifies the name of the organization (e.g., company, university, social club, etc.) that is administratively associated with this Printer. See: Section 5.4.1 'OrganizationName' in ITU-T [X.520] and the derived section 2.19 'o' in IETF LDAP User Schema [RFC4519]. printer-organizational-unit (text(127)) This REQUIRED Printer attribute specifies the name of the organizational unit (e.g., 'Human Resources', 'Finance', etc.) that is functionally associated with this Printer. See: Section 5.4.2 'OrganizationalUnitName' in ITU-T [X.520] and the derived section 2.20 'ou' in LDAP User Schema [RFC4519]. ------------------------------------------------------------------------ -- 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 Sun Aug 22 10:20:21 2010 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 BE9CE3A6839 for ; Sun, 22 Aug 2010 10:20:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6] 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 Le3Ul+egBcdM for ; Sun, 22 Aug 2010 10:20:20 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 6328F3A67B5 for ; Sun, 22 Aug 2010 10:20:20 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 22E9879374; Sun, 22 Aug 2010 13:20:50 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from omr14.networksolutionsemail.com (omr14.networksolutionsemail.com [205.178.146.64]) by pwg.org (Postfix) with ESMTP id A1EEA79372 for ; Sun, 22 Aug 2010 13:20:45 -0400 (EDT) Received: from cm-omr2 (mail.networksolutionsemail.com [205.178.146.50]) by omr14.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id o7MHKj12019632 for ; Sun, 22 Aug 2010 13:20:45 -0400 Authentication-Results: cm-omr2 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [75.16.40.111] ([75.16.40.111:49604] helo=[192.168.0.101]) by cm-omr2 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 75/45-18253-C6C517C4; Sun, 22 Aug 2010 13:20:45 -0400 Subject: Re: [Pwg-Announce] Fwd: [Isms] RFC 5953 - TLS Transport Model for SNMP Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Randy Turner In-Reply-To: Date: Sun, 22 Aug 2010 10:20:43 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <026CD5B5-74F5-4D4A-8D1C-37FAB2849589@amalfisystems.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@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: 22E9879374.ACE19 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Good catch Ira,...yes, this is a long-awaited publication. Looking forward to the "next" long-awaited doc (at least I'm waiting for it= :) that enables using NAC mechanisms to provision SNMP VACM agents... Pretty soon....SNMPv3 will become easy to deploy :) Hopefully, that will c= reate a catalyst for more folks using it. R. On Aug 20, 2010, at 1:53 PM, Ira McDonald wrote: > Hi, >=20 > The long-awaited enterprise network-friendly way to deploy SNMP > authentication and security using TLS and DTLS. >=20 > Recommended reading. >=20 > Cheers, > - Ira >=20 >=20 > ---------- Forwarded message ---------- > From: > Date: Fri, Aug 20, 2010 at 2:14 PM > Subject: [Isms] RFC 5953 on Transport Layer Security (TLS) Transport > Model for the Simple Network Management Protocol (SNMP) > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: isms@ietf.org, rfc-editor@rfc-editor.org >=20 >=20 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 5953 >=20 > Title: Transport Layer Security (TLS) Transport > Model for the Simple Network Management > Protocol (SNMP) > Author: W. Hardaker > Status: Standards Track > Stream: IETF > Date: August 2010 > Mailbox: ietf@hardakers.net > Pages: 65 > Characters: 147393 > Updates/Obsoletes/SeeAlso: None >=20 > I-D Tag: draft-ietf-isms-dtls-tm-14.txt >=20 > URL: http://www.rfc-editor.org/rfc/rfc5953.txt >=20 > This document describes a Transport Model for the Simple Network > Management Protocol (SNMP), that uses either the Transport Layer > Security protocol or the Datagram Transport Layer Security (DTLS) > protocol. The TLS and DTLS protocols provide authentication and > privacy services for SNMP applications. This document describes how > the TLS Transport Model (TLSTM) implements the needed features of a > SNMP Transport Subsystem to make this protection possible in an > interoperable way. >=20 > This Transport Model is designed to meet the security and operational > needs of network administrators. It supports the sending of SNMP > messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of > TCP's improved support for larger packet sizes and the DTLS mode > provides potentially superior operation in environments where a > connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS > integrate well into existing public keying infrastructures. >=20 > This document also defines a portion of the Management Information > Base (MIB) for use with network management protocols. In particular, > it defines objects for managing the TLS Transport Model for SNMP. > [STANDARDS TRACK] >=20 > This document is a product of the Integrated Security Model for SNMP > Working Group of the IETF. >=20 > This is now a Proposed Standard Protocol. >=20 > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and suggestio= ns > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. >=20 > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >=20 > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.htm= l. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. >=20 > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. >=20 >=20 > The RFC Editor Team > Association Management Solutions, LLC >=20 >=20 > _______________________________________________ > Isms mailing list > Isms@ietf.org > https://www.ietf.org/mailman/listinfo/isms >=20 > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce >=20 --=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 Mon Aug 23 08:28:29 2010 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 488903A689E for ; Mon, 23 Aug 2010 08:28:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.318 X-Spam-Level: X-Spam-Status: No, score=0.318 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_50=0.001, 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 c+KWLeue6Vnl for ; Mon, 23 Aug 2010 08:28:28 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id D82CC3A6879 for ; Mon, 23 Aug 2010 08:28:27 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 580487936E; Mon, 23 Aug 2010 11:28:53 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from wvmler5.mail.xerox.com (wvmler5.mail.xerox.com [13.8.138.230]) by pwg.org (Postfix) with ESMTP id E29F879358 for ; Mon, 23 Aug 2010 11:28:47 -0400 (EDT) Received: from wvmlir2.mail.xerox.com (wvmlir2.mail.xerox.com [13.147.8.222]) by wvmler5.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7NFSkcf010385 for ; Mon, 23 Aug 2010 08:28:46 -0700 Received: from wvmlir2.mail.xerox.com (localhost [127.0.0.1]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7NFSdxH012464 for ; Mon, 23 Aug 2010 08:28:39 -0700 Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7NFSZh1012362 for ; Mon, 23 Aug 2010 08:28:39 -0700 X-XeroxINT-Source-Ip: 13.135.210.15 X-XeroxINT-Source-Name: usa0300gw002.na.xerox.net X-XeroxINT-Reported-Name: USA0300GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 23 Aug 2010 11:28:37 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 23 Aug 2010 08:28:35 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LiveMeeting information for 8.23 IPP teleconference Thread-Index: Acss212FxyrhmYnkQNaUduBOqcPM8wV/Fz5A From: "Zehler, Peter" To: X-OriginalArrivalTime: 23 Aug 2010 15:28:37.0793 (UTC) FILETIME=[DB7C0110:01CB42D7] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] LiveMeeting information for 8.23 IPP teleconference 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="===============1215610021==" 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: 580487936E.A9A40 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1215610021== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB42D7.DAC06D1C" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB42D7.DAC06D1C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Attendee: Join the meeting. =20=20 =20 First Time Users:=20 To save time before the meeting, check your system to make sure it is ready to use Microsoft Office Live Meeting.=20 Troubleshooting Unable to join the meeting? Follow these steps:=20 =20 1. Copy this address and paste it into your web browser:=20 https://www.livemeeting.com/cc/xerox/join=20 2. Copy and paste the required information:=20 Meeting ID: Ipp823=20 Entry Code: LetMeIn=20 Location: https://www.livemeeting.com/cc/xerox=20 =20 =20 =20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CB42D7.DAC06D1C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Attendee:

= Join the meeting. <https://www.livemeeting.com/cc/xerox/join?id=3DIpp82= 3&role=3Dattend&pw=3DLetMeIn>

First Time Users:
T= o save time before the meeting, check your system to make sure it is ready to use Microsoft Office Live Meeti= ng.
Troubleshooting
U= nable to join the meeting? Follow these steps:

 

1.      Copy this addr= ess and paste it into your web browser:
https://www.livemeeting.= com/cc/xerox/join

2.      Copy and paste= the required information:
M= eeting ID: Ipp823
E= ntry Code: LetMeIn
L= ocation: https://www.livemeeting.co= m/cc/xerox

 <= /span>

 

 =

 =

 =

Peter Zehler

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CB42D7.DAC06D1C-- --===============1215610021== 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 --===============1215610021==-- From ipp-bounces@pwg.org Mon Aug 23 09:29:05 2010 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 155513A689C for ; Mon, 23 Aug 2010 09:29:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.883 X-Spam-Level: X-Spam-Status: No, score=-101.883 tagged_above=-999 required=5 tests=[AWL=0.716, 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 N83geRk0iJob for ; Mon, 23 Aug 2010 09:29:04 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id D6AB13A6358 for ; Mon, 23 Aug 2010 09:29:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B1CB679383; Mon, 23 Aug 2010 12:29:30 -0400 (EDT) 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 5579D79369 for ; Mon, 23 Aug 2010 12:29:25 -0400 (EDT) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 8F08AAAC3C95; Mon, 23 Aug 2010 09:29:24 -0700 (PDT) X-AuditID: 11807137-b7c08ae00000377a-4c-4c72a1e49160 Received: from da0704a-dhcp158.apple.com (da0704a-dhcp158.apple.com [17.197.43.158]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id F0.E2.14202.4E1A27C4; Mon, 23 Aug 2010 09:29:24 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Michael Sweet In-Reply-To: Date: Mon, 23 Aug 2010 09:29:24 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <08DF0841-935D-4083-BA72-76ACF330FE80@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Proposal for IPP organizational attributes 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: B1CB679383.A9058 X-pwg-MailScanner-From: ipp-bounces@pwg.org Comments inline... On Aug 22, 2010, at 9:59 AM, Ira McDonald wrote: > ------------------------------------------------------------------------ >=20 > IPP Organizational Location Attributes >=20 > printer-organization (text(127)) Is 127 octets sufficient? I checked both the X.520 and LDAP definitions an= d did not see a specific limit defined. I would actually think that text(MAX) would be more appropriate. >=20 > This REQUIRED Printer attribute specifies the name of the organization > (e.g., company, university, social club, etc.) that is administratively > associated with this Printer. >=20 > See: Section 5.4.1 'OrganizationName' in ITU-T [X.520] and the derived > section 2.19 'o' in IETF LDAP User Schema [RFC4519]. >=20 >=20 > printer-organizational-unit (text(127)) Ditto for this one. >=20 > This REQUIRED Printer attribute specifies the name of the organizational > unit (e.g., 'Human Resources', 'Finance', etc.) that is functionally > associated with this Printer. >=20 > See: Section 5.4.2 'OrganizationalUnitName' in ITU-T [X.520] and the > derived section 2.20 'ou' in LDAP User Schema [RFC4519]. >=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. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Aug 23 09:36:53 2010 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 265A33A689C for ; Mon, 23 Aug 2010 09:36:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.153 X-Spam-Level: X-Spam-Status: No, score=-2.153 tagged_above=-999 required=5 tests=[AWL=0.446, BAYES_00=-2.599] 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 t9ZJnnBukysj for ; Mon, 23 Aug 2010 09:36:51 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id BAC673A67B4 for ; Mon, 23 Aug 2010 09:36:49 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 64F5E79383; Mon, 23 Aug 2010 12:37:18 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 94CAF7936C for ; Mon, 23 Aug 2010 12:37:14 -0400 (EDT) Received: by vws3 with SMTP id 3so5459275vws.5 for ; Mon, 23 Aug 2010 09:37:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=VSwBdkJXXXHaH+/d88/hIVxsMsRJ7xMXfi1gCMfXos8=; b=Ov0vRtLT7VuXT3VPlKJULvwf0L6ewX0uD+uw1yIW1JYML12REQ61ayHKoS0JMV2XgL 69+sAvfRtbOFr6KQXgsfjnAKkBB7mzawwL0XCbarDzd5gk7QiFjFRyOgL8OzYRK4d9Vi zpsahD97Fi49ticACuWgW9Yusn46s2+p5jce0= 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 :content-type:content-transfer-encoding; b=h+FjKoGHdOWIhD0MAFSQL8azeUI3hjd8FojMrS77e7Ygm4/sNur6t7/BYtCb32KZRV KsUpiFddeK8g3zBqYiYqAgHrIHONZz8qvuooWmHKk11AjoipbWM1vBTQYKm6ki8N1p3j kOUAjUf+mhFHM03/vwIK5HUe+yEEWUXLV6BA8= MIME-Version: 1.0 Received: by 10.220.128.68 with SMTP id j4mr3444634vcs.68.1282581433577; Mon, 23 Aug 2010 09:37:13 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 23 Aug 2010 09:37:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 Aug 2010 12:37:13 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Tom Hastings , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Re: IPP Agenda - 4pm EDT Monday 21 August 2010 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: 64F5E79383.A8318 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, Reminder of our IPP WG teleconference today in 3+ hours. See Pete Zehler's separate note for Live Meeting link. Cheers, - Ira On Sat, Aug 21, 2010 at 5:10 PM, Ira McDonald wro= te: > Hi, > > [as planned at our August F2F] > > Reminder of our next IPP WG call: > > =A0Monday 21 August - 1-2pm PDT / 4-5pm EDT > > =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 - move IPP/2.0 SE into IPP WG Last Call *** > > Agenda: > > (1) PWG IP Policy and Minute Taker > =A0- Mike? > > (2) Approve IPP minutes from last meeting (August F2F) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20100805.pdf > > (3) Status of IPP Version 2.0 Second Edition (Ira) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821-rev.pdf > =A0 =A0(new Stable draft for IPP WG last call - no open issues) > > (4) Status of PWG Last Call on IPP JPS2 (Tom) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-= clean.pdf > =A0 =A0(ends Friday 27 August) > > (5) Review of IPP Printer Device Extensions proposal (Ira) > =A0- email proposal sent on 21 August > > (6) Status of IPP Everywhere Project (Mike/Ira) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-august-10.pdf > =A0 =A0(other pending action items?) > > (7) Next Steps > =A0- IPP WG - Monday 13 September (Monday 6th is Labor Day) > =A0- IPP/2.0 SE into IPP WG Last Call? > =A0- IPP JPS2 into PWG Formal Vote? > > Cheers, > - Ira (IPP co-editor) > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing 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 > winter: > =A0 579 Park Place=A0 Saline, MI=A0 48176 > =A0 734-944-0094 > summer: > =A0 PO Box 221=A0 Grand Marais, MI 49839 > =A0 906-494-2434 > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Aug 23 09:40:28 2010 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 2AAAC3A68D8 for ; Mon, 23 Aug 2010 09:40:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.973 X-Spam-Level: X-Spam-Status: No, score=-101.973 tagged_above=-999 required=5 tests=[AWL=0.626, 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 r0BXfWvMejTS for ; Mon, 23 Aug 2010 09:40:26 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 5FBC93A68BF for ; Mon, 23 Aug 2010 09:40:26 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 12E187939C; Mon, 23 Aug 2010 12:40:50 -0400 (EDT) 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 2BB7A79399 for ; Mon, 23 Aug 2010 12:40:45 -0400 (EDT) Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id ACB66AAC4445; Mon, 23 Aug 2010 09:40:44 -0700 (PDT) X-AuditID: 11807136-b7cc9ae000004162-0d-4c72a48c087a Received: from da0704a-dhcp158.apple.com (da0704a-dhcp158.apple.com [17.197.43.158]) (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 6F.E0.16738.C84A27C4; Mon, 23 Aug 2010 09:40:44 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Michael Sweet In-Reply-To: Date: Mon, 23 Aug 2010 09:40:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <54FC3EC3-CCF2-42EE-AAD1-8CD5C69FBB13@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Proposal for mapping Printer MIB into IPP 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: 12E187939C.A8D78 X-pwg-MailScanner-From: ipp-bounces@pwg.org Comments inline... On Aug 21, 2010, at 10:43 AM, Ira McDonald wrote: > Hi, Saturday (21 August 2010) >=20 > Per my action item from our August 2010 PWG Meeting, here is my proposal > for a new IPP spec called "IPP Printer Device Extensions". >=20 > Since the complete ABNF and mapping rules for all 170+ objects defined > in the Printer MIB will be fairly long, I suggest that this should be in > a separate IPP spec and not simply included in "IPP Everywhere" spec. >=20 > Comments? Of course we'll need to update the IPP charter to cover this, right? :) > Cheers, > - Ira >=20 > ------------------------------------------------------------------------ >=20 > Approach: >=20 > - Avoid use of new Object (e.g., Device) or Collection to reduce cost > for lightweight mobile implementations of IPP Clients >=20 > - Follow style of IPP PSX mapping of prtAlertTable, i.e., array of text > parameters in "printer-alert" representing most columns and separate > attributes like "printer-alert-description" for string MIB objects >=20 > - Convert all enumerated values from Printer MIB into IANA registered > string names, e.g., "prtChannelType" of "38" maps to "chBidirPortTCP" >=20 > - Map bit masks, e.g., "prtChannelStatus (PrtSubUnitStatusTC), directly > as integers (because string encoding in IPP is too verbose) I presume we would also require mapping of OID (indirect) values to the act= ual/real values? >=20 >=20 > Pros: >=20 > - Simple human-readable text encoding >=20 > - Lightweight (no new attribute groups, objects, etc.) >=20 > - High fidelity mapping from Printer MIB objects to IPP attributes >=20 >=20 > Cons: >=20 > - Like "printer-alert", maps a *single* physical output device onto an > IPP Printer object >=20 > - Note that this precedent was already established with "printer-alert" > which has shipped in CUPS and various printers for several years - Puts a greater burden on the client to decode the "simple" human-readable= text encoding. - Does not expose "simple" attributes/values like we do for printer-state-r= easons (e.g. printer-state-reasons gives the high-level issue, looking at p= rinter-alert gives you details) > Examples: In the examples below you are including bracketed numbers after the name - = what does that represent? Also, the first 3 examples show how you would map a port 9100 print channel= into an IPP attribute, which seems strange (something to think about for t= he "final" spec...) > printer-channel[1] =3D > "index=3D1;type=3DchBidirPortTCP;jclIndex=3D0;pdlIndex=3D1; > state=3DprintDataAccepted;ifIndex=3D3;status=3D0;" >=20 > printer-channel-version[1] =3D > "Bi-Directional Raw TCP/IP Printing" >=20 > printer-channel-info[1] =3D > "Port=3D9100" >=20 >=20 > printer-marker[1] =3D > "index=3D1;markTech=3DinkjetAqueous;counterUnit=3Dimpressions; > lifeCount=3D23412;powerOnCount=3D479;processColorants=3D4; > spotColorants=3D0;addressUnit=3DtenThousandthsOfInches; > addressFeedDir=3D600;addressXFeedDir=3D600; > northMargin=3D1066;southMargin=3D1066;eastMargin=3D1066;westMargin=3D1= 066; > status=3D0;" ________________________________________________________________________ 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 Aug 23 09:43:03 2010 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 171863A68BF for ; Mon, 23 Aug 2010 09:43:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vj6XayxqLLv6 for ; Mon, 23 Aug 2010 09:43:01 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 980FF3A689C for ; Mon, 23 Aug 2010 09:43:01 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A71F27939D; Mon, 23 Aug 2010 12:43:28 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by pwg.org (Postfix) with ESMTP id 654B47939B for ; Mon, 23 Aug 2010 12:43:24 -0400 (EDT) Received: by pvg2 with SMTP id 2so2239438pvg.5 for ; Mon, 23 Aug 2010 09:43:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LjAoklriC3Euj2g2RsGCq9+6XKa0qGNvBtEBvpv8roQ=; b=CCaAvoFt77l+MFM59J5yLuuRccUc0gZzDbv/w3FS+FyWgx8YVmm8xyIS1tRaD4LQiC Uj7W0oFBvxyyTExWropr31Tp/Eex0LXiv/aI3qF/ba7VJ4ASwybUXNw9MVuXJSO+NAEC 6/PFb5tsg2Fnz0lFNfn3KZcylLgCfzrpI/BZk= 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:content-transfer-encoding; b=ATf3+ypjfbS/TLUeQ+hGt7+JMIbPPb+8Vu4c8cesLpjiEIltgQhSpf9hQZdcze00Hy TaqTOhu6LwFS5260yGN66nLZUyterzyRkW6wJxbPKvraqJ/u3Kimu79QHvRLZMeI+t5T hmJ8UJS5n0yE9mie0W4Y4LpThh5kgCroGYrl8= MIME-Version: 1.0 Received: by 10.142.144.16 with SMTP id r16mr4538616wfd.312.1282581802414; Mon, 23 Aug 2010 09:43:22 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 23 Aug 2010 09:43:22 -0700 (PDT) In-Reply-To: <08DF0841-935D-4083-BA72-76ACF330FE80@apple.com> References: <08DF0841-935D-4083-BA72-76ACF330FE80@apple.com> Date: Mon, 23 Aug 2010 12:43:22 -0400 Message-ID: From: Ira McDonald To: Michael Sweet , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Proposal for IPP organizational attributes 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: A71F27939D.A8A70 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi Mike, Agreed - I made them '127' to align with printer-info and printer-location (both of which SHOULD have been longer for internationalization). Also, they both SHOULD be '1setOf (text)', because they're multi-valued in both LDAP and X.520 specs. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: =A0 579 Park Place=A0 Saline, MI=A0 48176 =A0 734-944-0094 summer: =A0 PO Box 221=A0 Grand Marais, MI 49839 =A0 906-494-2434 On Mon, Aug 23, 2010 at 12:29 PM, Michael Sweet wrote: > Comments inline... > > On Aug 22, 2010, at 9:59 AM, Ira McDonald wrote: >> ------------------------------------------------------------------------ >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IPP Organizational Location Attributes >> >> printer-organization (text(127)) > > Is 127 octets sufficient? =A0I checked both the X.520 and LDAP definition= s and did not see a specific limit defined. > > I would actually think that text(MAX) would be more appropriate. > >> >> This REQUIRED Printer attribute specifies the name of the organization >> (e.g., company, university, social club, etc.) that is administratively >> associated with this Printer. >> >> See: =A0Section 5.4.1 'OrganizationName' in ITU-T [X.520] and the derived >> section 2.19 'o' in IETF LDAP User Schema [RFC4519]. >> >> >> printer-organizational-unit (text(127)) > > Ditto for this one. > >> >> This REQUIRED Printer attribute specifies the name of the organizational >> unit (e.g., 'Human Resources', 'Finance', etc.) that is functionally >> associated with this Printer. >> >> See: =A0Section 5.4.2 'OrganizationalUnitName' in ITU-T [X.520] and the >> derived section 2.20 'ou' in LDAP User Schema [RFC4519]. >> >> ------------------------------------------------------------------------ > > ________________________________________________________________________ > 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 Aug 23 09:48:43 2010 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 6F3123A68BF for ; Mon, 23 Aug 2010 09:48:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gSPO5W1BlxLQ for ; Mon, 23 Aug 2010 09:48:42 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id F3DE73A689C for ; Mon, 23 Aug 2010 09:48:41 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5E3BD793A1; Mon, 23 Aug 2010 12:49:09 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr12.networksolutionsemail.com (omr12.networksolutionsemail.com [205.178.146.62]) by pwg.org (Postfix) with ESMTP id 51BCB79399 for ; Mon, 23 Aug 2010 12:49:03 -0400 (EDT) Received: from cm-omr9 (mail.networksolutionsemail.com [205.178.146.50]) by omr12.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id o7NGn2C7023535 for ; Mon, 23 Aug 2010 12:49:02 -0400 Authentication-Results: cm-omr9 smtp.user=ptykodi@tykodi.com; auth=pass (LOGIN) X-Authenticated-UID: ptykodi@tykodi.com Received: from [76.179.177.123] ([76.179.177.123:4089] helo=TCSLAPTOP01) by cm-omr9 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id DF/6E-29653-A76A27C4; Mon, 23 Aug 2010 12:49:02 -0400 From: "Paul Tykodi" To: References: Date: Mon, 23 Aug 2010 12:48:54 -0400 Organization: Tykodi Consulting Services LLC Message-ID: <865DE24FAF314A84B1FCB54FE2EAE688@TCSLAPTOP01> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 In-Reply-To: thread-index: ActBdVhi8QjtNk4EQViuUEvkgn3ckwBa2kzA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] RE: IPP Agenda - 4pm EDT Monday 21 August 2010 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ptykodi@tykodi.com List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: 5E3BD793A1.A8E6B X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, I have a scheduling conflict so that I will not be able to call into today's meeting. 1. I confirm that the changes listed by Ira in the latest stable draft of IPP/2.0 SE (see URL in his e-mail shown below) fulfill all the change requests I believe were made during the review of the previous version of the document during the August 2010 F2F in Copenhagen, Denmark. As IPP WG Chair, I am therefore comfortable with promoting IPP/2.0 SE to IPP WG last call at this time unless someone voices significant concerns at today's meeting. 2. I will make sure to review IPP JPS2 before the deadline expires. 3. Review of IPP Printer Device Extensions proposal (Ira) - I think the proposal as written mirrors what has been done for many years on servers that handle primarily recurring transactional based printing. I therefore do not believe that the cons as outlined by Ira should be considered as significant reasons to not proceed with investigating the idea. 4. IPP Everywhere - I will read the notes from today's meeting to see how we are progressing. Thanks. Best Regards, /Paul -- Paul Tykodi Principal Consultant TCS - Tykodi Consulting Services LLC Tel/Fax: 603-343-1820 Mobile: 603-866-0712 E-mail: ptykodi@tykodi.com WWW: http://www.tykodi.com > -----Original Message----- > From: Ira McDonald [mailto:blueroofmusic@gmail.com] > Sent: Saturday, August 21, 2010 5:11 PM > To: ipp@pwg.org; Michael R Sweet; Paul Tykodi; Tom Hastings; Ira McDonald > Subject: IPP Agenda - 4pm EDT Monday 21 August 2010 >=20 > Hi, >=20 > [as planned at our August F2F] >=20 > Reminder of our next IPP WG call: >=20 > Monday 21 August - 1-2pm PDT / 4-5pm EDT >=20 > 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) >=20 > Attendee Access Code: *******# > Attendee ID Code: # (empty) >=20 > If you need the Attendee Access code, please email me a request. >=20 >=20 > *** Main Objective - move IPP/2.0 SE into IPP WG Last Call *** >=20 > Agenda: >=20 > (1) PWG IP Policy and Minute Taker > - Mike? >=20 > (2) Approve IPP minutes from last meeting (August F2F) > - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20100805.pdf >=20 > (3) Status of IPP Version 2.0 Second Edition (Ira) > - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821-rev.pdf > (new Stable draft for IPP WG last call - no open issues) >=20 > (4) Status of PWG Last Call on IPP JPS2 (Tom) > - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725- > clean.pdf > (ends Friday 27 August) >=20 > (5) Review of IPP Printer Device Extensions proposal (Ira) > - email proposal sent on 21 August >=20 > (6) Status of IPP Everywhere Project (Mike/Ira) > - ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-august-10.pdf > (other pending action items?) >=20 > (7) Next Steps > - IPP WG - Monday 13 September (Monday 6th is Labor Day) > - IPP/2.0 SE into IPP WG Last Call? > - IPP JPS2 into PWG Formal Vote? >=20 > Cheers, > - Ira (IPP co-editor) >=20 > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing 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 > winter: > =A0 579 Park Place=A0 Saline, MI=A0 48176 > =A0 734-944-0094 > summer: > =A0 PO Box 221=A0 Grand Marais, MI 49839 > =A0 906-494-2434 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Aug 23 12:33:35 2010 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 5801B3A6ABF for ; Mon, 23 Aug 2010 12:33:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.174 X-Spam-Level: X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599] 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 0ku-itMT0tpr for ; Mon, 23 Aug 2010 12:33:32 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 422223A6ACA for ; Mon, 23 Aug 2010 12:33:32 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E70F1793AF; Mon, 23 Aug 2010 15:34:01 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 9BE81793A7 for ; Mon, 23 Aug 2010 15:33:58 -0400 (EDT) Received: by vws3 with SMTP id 3so5624221vws.5 for ; Mon, 23 Aug 2010 12:33:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+KYeeAnWkaO7kkMVdLfWK0XaBgc9oqwxDzWzJb16bV4=; b=XL3jELphDccAaB2w9jNJMbiBM5eb81WTovNh2ads/RQd5u9uBkejHC97iTrIHSpKfH n9zf5E8QHaHbcLvDSGMXkzaJJCKZANay0tGWucGtA7Cxzi528+zlA1E17wHc4+SgOlYo FYsxpNpVGsxOsgRHypMspkb3GL0RQNHS5fwA4= 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:content-transfer-encoding; b=A8swk1qHd1xHnKhzDGghP295VZY5OQEXJj9SZ0QXvNz0f7IGLZGGBbtyfIZxYfH7PM fgQBWXxXkP52JNWSxuGpruy1UVT7EpBwx5LQrGwLiNCKp2bIx80Qp5oF+u2t5f3LpFVx RNjxoe+lStew8Uur4Uyi/Nkl/JQOrvay0iKkQ= MIME-Version: 1.0 Received: by 10.220.168.12 with SMTP id s12mr3520997vcy.100.1282592037853; Mon, 23 Aug 2010 12:33:57 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 23 Aug 2010 12:33:57 -0700 (PDT) In-Reply-To: <54FC3EC3-CCF2-42EE-AAD1-8CD5C69FBB13@apple.com> References: <54FC3EC3-CCF2-42EE-AAD1-8CD5C69FBB13@apple.com> Date: Mon, 23 Aug 2010 15:33:57 -0400 Message-ID: From: Ira McDonald To: Michael Sweet , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: Proposal for mapping Printer MIB into IPP 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: E70F1793AF.A8E46 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi Mike, Square brackets in examples mean a row instance in 1setOf tables, just like in IPP PSX examples. On reflection, I agree that changing all the enums (dozens) to labels is undesirable. So I propose a high-fidelity direct mapping (i.e., an integer object stays a decimal string integer and a string object gets a separate IPP attribute, to disambiguate line delimiters). Hmm? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: =A0 579 Park Place=A0 Saline, MI=A0 48176 =A0 734-944-0094 summer: =A0 PO Box 221=A0 Grand Marais, MI 49839 =A0 906-494-2434 On Mon, Aug 23, 2010 at 12:40 PM, Michael Sweet wrote: > Comments inline... > > On Aug 21, 2010, at 10:43 AM, Ira McDonald wrote: >> Hi, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0Saturday (21 August 2010) >> >> Per my action item from our August 2010 PWG Meeting, here is my proposal >> for a new IPP spec called "IPP Printer Device Extensions". >> >> Since the complete ABNF and mapping rules for all 170+ objects defined >> in the Printer MIB will be fairly long, I suggest that this should be in >> a separate IPP spec and not simply included in "IPP Everywhere" spec. >> >> Comments? > > Of course we'll need to update the IPP charter to cover this, right? :) > >> Cheers, >> - Ira >> >> ------------------------------------------------------------------------ >> >> Approach: >> >> - Avoid use of new Object (e.g., Device) or Collection to reduce cost >> =A0for lightweight mobile implementations of IPP Clients >> >> - Follow style of IPP PSX mapping of prtAlertTable, i.e., array of text >> =A0parameters in "printer-alert" representing most columns and separate >> =A0attributes like "printer-alert-description" for string MIB objects >> >> - Convert all enumerated values from Printer MIB into IANA registered >> =A0string names, e.g., "prtChannelType" of "38" maps to "chBidirPortTCP" >> >> - Map bit masks, e.g., "prtChannelStatus (PrtSubUnitStatusTC), directly >> =A0as integers (because string encoding in IPP is too verbose) > > I presume we would also require mapping of OID (indirect) values to the a= ctual/real values? > >> >> >> Pros: >> >> - Simple human-readable text encoding >> >> - Lightweight (no new attribute groups, objects, etc.) >> >> - High fidelity mapping from Printer MIB objects to IPP attributes >> >> >> Cons: >> >> - Like "printer-alert", maps a *single* physical output device onto an >> =A0IPP Printer object >> >> - Note that this precedent was already established with "printer-alert" >> =A0which has shipped in CUPS and various printers for several years > > - Puts a greater burden on the client to decode the "simple" human-readab= le text encoding. > - Does not expose "simple" attributes/values like we do for printer-state= -reasons (e.g. printer-state-reasons gives the high-level issue, looking at= printer-alert gives you details) > >> Examples: > > In the examples below you are including bracketed numbers after the name = - what does that represent? > > Also, the first 3 examples show how you would map a port 9100 print chann= el into an IPP attribute, which seems strange (something to think about for= the "final" spec...) > >> printer-channel[1] =3D >> =A0 =A0"index=3D1;type=3DchBidirPortTCP;jclIndex=3D0;pdlIndex=3D1; >> =A0 =A0state=3DprintDataAccepted;ifIndex=3D3;status=3D0;" >> >> printer-channel-version[1] =3D >> =A0 =A0"Bi-Directional Raw TCP/IP Printing" >> >> printer-channel-info[1] =3D >> =A0 =A0"Port=3D9100" >> >> >> printer-marker[1] =3D >> =A0 =A0"index=3D1;markTech=3DinkjetAqueous;counterUnit=3Dimpressions; >> =A0 =A0lifeCount=3D23412;powerOnCount=3D479;processColorants=3D4; >> =A0 =A0spotColorants=3D0;addressUnit=3DtenThousandthsOfInches; >> =A0 =A0addressFeedDir=3D600;addressXFeedDir=3D600; >> =A0 =A0northMargin=3D1066;southMargin=3D1066;eastMargin=3D1066;westMargi= n=3D1066; >> =A0 =A0status=3D0;" > > > > ________________________________________________________________________ > 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 Aug 23 12:41:18 2010 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 7ACEB3A6AC0 for ; Mon, 23 Aug 2010 12:41:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.193 X-Spam-Level: X-Spam-Status: No, score=-2.193 tagged_above=-999 required=5 tests=[AWL=0.406, BAYES_00=-2.599] 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 eWMFu4HfgaBd for ; Mon, 23 Aug 2010 12:41:16 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 87AD13A6A7D for ; Mon, 23 Aug 2010 12:41:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 91613793B0; Mon, 23 Aug 2010 15:41:48 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 9F74E793AF for ; Mon, 23 Aug 2010 15:41:45 -0400 (EDT) Received: by vws3 with SMTP id 3so5632970vws.5 for ; Mon, 23 Aug 2010 12:41:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=R7ozwxFPN801z8VwPBUWzDqYQUYETrfN1f0KK2KVLNI=; b=eHK80b+4oTHBRwHBhVw51cc6Eu45SqMubhsM8kwOpUd2zrjbkIdJCwoS5CfM8H1zul iuVrUbtjMgStSEaEPVsNDkm9XU5QvHmvWUesf+3rVT+IPVwnI5VycMjdcdlQ8AU3LsZk 3+TWDkwS+y3gbRK1XKg9xtnT4SmEzY5e44DwI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=AZklcI6cw9OYPM9PWGkWDMf2df7zzoosF1swzcOl6uQ4mLgCC9eU8a4jhFAnVfd8QV LNLHCOvFUA3IqDlU3vcFTCgL4Yp2ev2rm+TKqyR+/gtUIdOHkGGGqJE0G+lVPOhWFDNT TP6uvV27/0nCqERKkDaxt2DmiHiUtjsFkR8us= MIME-Version: 1.0 Received: by 10.220.59.5 with SMTP id j5mr3458314vch.230.1282592505176; Mon, 23 Aug 2010 12:41:45 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 23 Aug 2010 12:41:45 -0700 (PDT) Date: Mon, 23 Aug 2010 15:41:45 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Tom Hastings , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Re: IPP Agenda - 4pm EDT Monday 23 August 2010 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: 91613793B0.A8F4E X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, As Glen pointed out - wrong date - oops. Fixed in subject line and copied note below. Cheers, - Ira Chair - Linux Foundation Open Printing WG On Sat, Aug 21, 2010 at 5:10 PM, Ira McDonald wro= te: > Hi, > > [as planned at our August F2F] > > Reminder of our next IPP WG call: > > =A0Monday 23 August - 1-2pm PDT / 4-5pm EDT > > =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 - move IPP/2.0 SE into IPP WG Last Call *** > > Agenda: > > (1) PWG IP Policy and Minute Taker > =A0- Mike? > > (2) Approve IPP minutes from last meeting (August F2F) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-f2f-minutes-20100805.pdf > > (3) Status of IPP Version 2.0 Second Edition (Ira) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821-rev.pdf > =A0 =A0(new Stable draft for IPP WG last call - no open issues) > > (4) Status of PWG Last Call on IPP JPS2 (Tom) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-= clean.pdf > =A0 =A0(ends Friday 27 August) > > (5) Review of IPP Printer Device Extensions proposal (Ira) > =A0- email proposal sent on 21 August > > (6) Status of IPP Everywhere Project (Mike/Ira) > =A0- ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-august-10.pdf > =A0 =A0(other pending action items?) > > (7) Next Steps > =A0- IPP WG - Monday 13 September (Monday 6th is Labor Day) > =A0- IPP/2.0 SE into IPP WG Last Call? > =A0- IPP JPS2 into PWG Formal Vote? > > Cheers, > - Ira (IPP co-editor) > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing 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 > winter: > =A0 579 Park Place=A0 Saline, MI=A0 48176 > =A0 734-944-0094 > summer: > =A0 PO Box 221=A0 Grand Marais, MI 49839 > =A0 906-494-2434 > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Aug 23 13:02:48 2010 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 788663A6ADF for ; Mon, 23 Aug 2010 13:02:48 -0700 (PDT) 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 ic6OU9kv102M for ; Mon, 23 Aug 2010 13:02:47 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 6EC513A67D0 for ; Mon, 23 Aug 2010 13:02:47 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5E82E793BA; Mon, 23 Aug 2010 16:03:19 -0400 (EDT) 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 A6868793B7 for ; Mon, 23 Aug 2010 16:03:14 -0400 (EDT) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 9BE04A43E392 for ; Mon, 23 Aug 2010 13:03:13 -0700 (PDT) X-AuditID: 11807134-b7b5eae00000345f-9c-4c72d401043a Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay14.apple.com (Apple SCV relay) with SMTP id 3A.4D.13407.104D27C4; Mon, 23 Aug 2010 13:03:13 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [10.60.122.112] (166-205-138-240.mobile.mymmode.com [166.205.138.240]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0L7M00GC3FPA2A60@gertie.apple.com> for ipp@pwg.org; Mon, 23 Aug 2010 13:03:13 -0700 (PDT) From: Michael R Sweet X-Mailer: iPhone Mail (8A400) Message-id: <13501831-F866-4042-93A0-98CC9F9D709E@apple.com> Date: Mon, 23 Aug 2010 13:03:12 -0700 To: "ipp@pwg.org" X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Running late 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: 5E82E793BA.A99AD X-pwg-MailScanner-From: ipp-bounces@pwg.org Calling in 5 Sent from my iPhone -- 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 Aug 23 14:12:46 2010 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 A1D2B3A6B08 for ; Mon, 23 Aug 2010 14:12:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.21 X-Spam-Level: X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=0.388, 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 3JiMe-4+Dnzr for ; Mon, 23 Aug 2010 14:12:39 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 3975A3A6B1F for ; Mon, 23 Aug 2010 14:11:49 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id DEAA4793C0; Mon, 23 Aug 2010 17:12:07 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 68580793AD for ; Mon, 23 Aug 2010 17:12:03 -0400 (EDT) Received: by vws3 with SMTP id 3so5735233vws.5 for ; Mon, 23 Aug 2010 14:12:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=xSczpd4kziSuy7xdMnpO1LUtI/wb43tuoCouOwWf+Pk=; b=DwCUGZ/20Tw6zudNfQONtBVVNH54whyTXDxcHpeG3TDZUAFxy5fVIKZTQMt9lSXjd7 eVCq/v0jBoh/v5saT7O6/tb18M1qNwdLhei9421VWRqrP/Wqt+zGdU8rmHlkkQSp0sJ7 PaYl1wbmya+Id3OQHii1nAYdoY5c4dgAL60FY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KUbt2CYQtwk4ZqwaOMkI4aJekEQ6IXJQINcXXy7GkTrXVB61HS+5xVGKckBEphhc3R 0xyDfr3QzVHkBBYbAF2z+7/pzuOVCq2kche6VPZcgnCROhBzXDWjKJ1iJsO7DdDvzphk B2tv/uJlXo5foYk1d9BoBVqxLvXdNmgQNpOHw= MIME-Version: 1.0 Received: by 10.220.126.229 with SMTP id d37mr3650718vcs.107.1282597922684; Mon, 23 Aug 2010 14:12:02 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 23 Aug 2010 14:12:02 -0700 (PDT) Date: Mon, 23 Aug 2010 17:12:02 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald , Michael R Sweet X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Conference bridge appears broken 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="===============0073130370==" 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: DEAA4793C0.AA1F5 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0073130370== Content-Type: multipart/alternative; boundary=00163691fc44923f7e048e841951 --00163691fc44923f7e048e841951 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've restarted the call three times and gotten squealing line. I suggest we quit for today - meet in 3 weeks (due to Labor Day) - continue discussions today on the email reflector. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --00163691fc44923f7e048e841951 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've restarted the call three times and gotten squealing lin= e.

I suggest we quit for today - meet in 3 weeks (due to Labor
Da= y) - continue discussions today on the email reflector.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
= Chair - Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
= IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High Nort= h Inc
http://sites.google.= com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:blueroofmusic@gmail.com
winter:
=A0 579 Park Place=A0 Saline, MI=A0 48176
=A0 734-944-0094summer:
=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. --00163691fc44923f7e048e841951-- --===============0073130370== 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 --===============0073130370==-- From ipp-bounces@pwg.org Mon Aug 23 14:39:32 2010 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 DC2CD3A68B1 for ; Mon, 23 Aug 2010 14:39:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.042 X-Spam-Level: X-Spam-Status: No, score=-102.042 tagged_above=-999 required=5 tests=[AWL=0.556, 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 IJbw1EB6lS+I for ; Mon, 23 Aug 2010 14:39:31 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 8AC753A686D for ; Mon, 23 Aug 2010 14:39:31 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C450D793C9; Mon, 23 Aug 2010 17:39:58 -0400 (EDT) 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 53E29793C7 for ; Mon, 23 Aug 2010 17:39:54 -0400 (EDT) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id AAB79AAD0D99 for ; Mon, 23 Aug 2010 14:39:53 -0700 (PDT) X-AuditID: 11807134-b7b5eae00000345f-47-4c72eaa9aab2 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 70.1A.13407.9AAE27C4; Mon, 23 Aug 2010 14:39:53 -0700 (PDT) From: Michael Sweet Date: Mon, 23 Aug 2010 14:39:53 -0700 To: ipp@pwg.org Message-Id: <89963006-3B93-46C9-AD7D-A342902C01E4@apple.com> Mime-Version: 1.0 (Apple Message framework v1162) X-Mailer: Apple Mail (2.1162) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Concall minutes 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="===============1016471913==" 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: C450D793C9.AA556 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1016471913== Content-Type: multipart/alternative; boundary=Apple-Mail-1--650284572 --Apple-Mail-1--650284572 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii All, Tried calling back in a couple times and just got the tone; I've posted the= minutes from today at: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20100823.pdf Looking at the calendar, two weeks puts us on Labor Day, so I propose our n= ext concall for September 13, 2010 at the usual time. We can resume discus= sion of IPP Everywhere and the possible new Job and Printer Extensions spec= ification at the next concall... ________________________________________________________________________ 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--650284572 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii All,

Tr= ied calling back in a couple times and just got the tone; I've posted the m= inutes from today at:


Looking at the calendar, two weeks puts us on= Labor Day, so I propose our next concall for September 13, 2010 at the usu= al time.  We can resume discussion of IPP Everywhere and the possible = new Job and Printer Extensions specification at the next concall...

_______________________________________________________________= _________
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-1--650284572-- --===============1016471913== 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 --===============1016471913==-- From ipp-bounces@pwg.org Tue Aug 24 17:31:07 2010 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 CA5583A688E for ; Tue, 24 Aug 2010 17:31:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.02 X-Spam-Level: X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[AWL=-0.835, BAYES_40=-0.185] 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 TBIKSk3iawvP for ; Tue, 24 Aug 2010 17:31:04 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 2D4DC3A6A72 for ; Tue, 24 Aug 2010 17:31:04 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B55EB793D0; Tue, 24 Aug 2010 20:31:31 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by pwg.org (Postfix) with ESMTP id 514BA793C9 for ; Tue, 24 Aug 2010 20:31:28 -0400 (EDT) Received: by vws3 with SMTP id 3so75985vws.5 for ; Tue, 24 Aug 2010 17:31:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=l435sXK5waWsT3excGoGOUWnTi5ciN0ldwq2KbyqOhE=; b=Xvp8AVTx1WbgZyXyEfvxu69S5CDzjZt5rZjDfxVUUzO5jNcuasWmrcyW0fF+z093Vx VWCgXQ5FdKmObd/d1/ubLyOWomC18oSTogRqqHogEoKrGtuLX/VawEQmyZw9JfkCX0+n HhmoNrOn1i0Hj9gEtsdG57mUqE/n9siafOedg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=E2c2jEahIwAsRF+yTU4+cBVbwMd5ReK76aif2WnARiJbbHgiC8cM1JOHwq2u7bhK6+ 03SjHjWUsiQpwRB/1VCXhXymVkSESmSCP3by9MNuUaM4eyTFAfUrPWwiw4CaITkIjj5h dsmiA+ylboBjRhoNkq1688F0f/EVPsEdEfXXQ= MIME-Version: 1.0 Received: by 10.220.127.81 with SMTP id f17mr4340813vcs.47.1282696287461; Tue, 24 Aug 2010 17:31:27 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Tue, 24 Aug 2010 17:31:27 -0700 (PDT) Date: Tue, 24 Aug 2010 20:31:27 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Paul Tykodi , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Working Group Last Call on IPP/2.0 SE (ends Friday 17 Sept 2010) 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: B55EB793D0.A8D90 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, This is the formal announcement of the IPP Working Group Last Call of the IPP Version 2.0 Second Edition spec, which is located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp20-20100821.pdf - clean version with line numbers This IPP WG Last Call will start today Tuesday 24 August 2010 and will end on Friday 17 September 2010 at 10pm US PDT. All newly required operations and attributes defined in this document have been prototyped by Apple and/or Xerox. To send your comments, simply hit "Reply All" to this message. After a lively discussion at yesterday's IPP WG teleconference, we concluded that we probably don't want to delay the completion of IPP/2.0 SE (and therefore the availability of new IPP/2.2 conformance level) for 6 or 8 months - the probable delay in order to include the proposed IPP Job and Printer Extensions Set3 spec (new attributes and any new operations needed for IPP Everywhere conformance profile). Please take the time to review this specification. Cheers, - Ira (IPP/2.0 SE co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: =A0 579 Park Place=A0 Saline, MI=A0 48176 =A0 734-944-0094 summer: =A0 PO Box 221=A0 Grand Marais, MI 49839 =A0 906-494-2434 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Wed Aug 25 05:01:14 2010 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 16D043A6AF3 for ; Wed, 25 Aug 2010 05:01:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[AWL=0.831, BAYES_05=-1.11, 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 yfDc4tVQoPsa for ; Wed, 25 Aug 2010 05:01:07 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 9BF2E3A6AF4 for ; Wed, 25 Aug 2010 05:01:07 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 7DFDE793CA; Wed, 25 Aug 2010 08:01:26 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from wvmler5.mail.xerox.com (wvmler5.mail.xerox.com [13.8.138.230]) by pwg.org (Postfix) with ESMTP id 9EA23793C7 for ; Wed, 25 Aug 2010 08:01:18 -0400 (EDT) Received: from wvmlir2.mail.xerox.com (wvmlir2.mail.xerox.com [13.147.8.222]) by wvmler5.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7PC1DaR009569; Wed, 25 Aug 2010 05:01:15 -0700 Received: from wvmlir2.mail.xerox.com (localhost [127.0.0.1]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7PC13bw000513; Wed, 25 Aug 2010 05:01:03 -0700 Received: from USA7061GW002.na.xerox.net (usa7061gw002.na.xerox.net [13.151.210.15]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7PC10EU032303; Wed, 25 Aug 2010 05:01:03 -0700 X-XeroxINT-Source-Ip: 13.151.210.15 X-XeroxINT-Source-Name: usa7061gw002.na.xerox.net X-XeroxINT-Reported-Name: USA7061GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 Aug 2010 05:00:56 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Attributes needed for Cloud Printing anddefinitioninconsistencies Date: Wed, 25 Aug 2010 05:00:51 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Attributes needed for Cloud Printing anddefinitioninconsistencies Thread-Index: AcspxRRVo4ExmexOQvqGozc+7BuVQQN3fqnwAypdXSA= References: From: "Zehler, Peter" To: "Christoph Lindemann" , X-OriginalArrivalTime: 25 Aug 2010 12:00:56.0661 (UTC) FILETIME=[2CE5A850:01CB444D] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1991955877==" 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: 7DFDE793CA.AB487 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1991955877== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB444D.2CE5ABA2" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB444D.2CE5ABA2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Christoph, At next week's MFD meeting we will be discussing some cloud related semantics. I am hoping that you, and other interested parties, will be able to attend. I've included the MFD meeting agenda, phone number and Livemeeting information below. Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Christoph Lindemann Sent: Monday, August 09, 2010 5:37 AM To: ipp@pwg.org; mfd@pwg.org Subject: RE: [IPP] Attributes needed for Cloud Printing anddefinitioninconsistencies =20 Hi, =20 Would it also be possible to add some sort of parent job UUID list/hierarchy? So it will be possible to track source/parent jobs after splitting a job into several jobs. =20 For example (maybe not the best, but..): Imagine I have a company internal print cloud, to which I submit the jobs. This cloud could forward jobs to other external clouds, based on location (one provider for US, another for EU,...), cost or other parameters. =20 So if I need to print a marketing document in both US and EU, I could submit the job to a special queue in the company cloud, which again would submit 1 copy to my local DeskJet printer, submit a new job with 10000 copies to the external EU print/cloud partner and another 10000 to the US partner. In this example, the jobs at the two external clouds, better not have the same UUID if I need to track them. But I would still need the "root job" UUID for doing accounting. =20 Hope this makes sense, Christoph Lindemann =20 There will be an MFD conference call at 3:00 PM EST (12:00 PM PST) Thursday May 20. Below is the proposed agenda =20 The meeting is held in accord with the PWG Intellectual Property Policy. =20 teleconference: Call-in toll-free number (US/Canada): 1-866-469-3239=20 Call-in toll number (US/Canada): 1-650-429-3300=20 Call-in toll number (US/Canada): 1-408-856-9570=20 Attendee access code: (by request only, please contact me if you do not have it) Live Meeting: =20 =20 =20 =20 Agenda: =20 1. Identify Minute Taker =20 2. Approval of minutes from last meeting =20 =20 =20 3. Agenda bashing=20 =20 4. Discuss parent job UUID (See below) =20 5. Discuss Cloud specific element definitions (Will be released under separate cover) =20 6. Discuss Power elements in schema (See below) =20 7. Discuss JobOriginatingUserAuthenticationInfo element in schema=20=20 =20 =20 =20 8. Next steps=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_01CB444D.2CE5ABA2 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Christoph,

At next week’s MFD= meeting we will be discussing some cloud related semantics.  I am hoping that = you, and other interested parties, will be able to attend.  I’ve incl= uded the MFD meeting agenda, phone number and Livemeeting information below.

Pete

 =

 =

Peter Zehler

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

 =

From: ipp-bounces@p= wg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Christoph Lindemann
Sent: Monday, August 09, 2010 5:37 AM
To: ipp@pwg.org; mfd@pwg.org
Subject: RE: [IPP] Attributes needed for Cloud Printing anddefinitioninconsistencies

 

Hi,

 

Would it also be possible to add some sort of parent job UUID list/hierarchy? So it will be possible to track source/parent jobs after splitting a job into several jobs.

 

For example (maybe not the best, but..):

Imagine I have a company internal print cloud, to which I submit the jobs. This cloud could forward = jobs to other external clouds, based on location (one provider for US, another f= or EU,…), cost or other parameters.

 

So if I need to print a marketing document in both US and EU, I could submit the job to a special q= ueue in the company cloud, which again would submit 1 copy to my local DeskJet printer, submit a new job with 10000 copies to the external EU print/cloud = partner and another 10000 to the US partner.

In this example, the jo= bs at the two external clouds, better not have the same UUID if I need to track them. But I would still need the “root job” UUID for doing accounting.

 

Hope this makes sense,

Christoph Lindemann

 

&= lt;snip/>

There will be an MFD conference call at 3= :00 PM EST (12:00 PM PST) Thursday May 20.  Below is the proposed agenda

 

The meeting is held in accord with the PWG Intellectual Property Policy.

 

teleconference:

Call-in toll-free number (US/Canada): 1-866-469-3239

Call-in toll number (US/Canada): 1-650-429-3300

Call-in toll number (US/Canada): 1-408-85= 6-9570

Att= endee access code: (by request only, please contact me if you do not have it)=

Live Meeting:

<https://www.livemeeting.com/cc/xerox/join?id=3DPWG-= MFD&role=3Dattend&pw=3DLetMeIn>

 

 

 

 

Agenda:

 

1. Identify Minute Taker

 

2. Approval of minutes from last meeting<= o:p>

 

       = ; <ftp://ftp.pwg.org/pub/pwg/mfd/minutes/pwg-ftf-mfd-minutes-20100803.pdf= >  

 

3. Agenda bashing

 

4. Discuss parent job UUID (See below)

 

5. Discuss Cloud specific element definit= ions (Will be released under separate cover)

 

6. Discuss Power elements in schema  (See below)

 

7. Discuss JobOriginatingUserAuthenticationInfo element in schema  

       = ;     <http://www.pwg.org/mfd/navigate/PwgSmRev1-107_ImagingJobStatu= sType.html#LinkC20>

 

8. Next steps

 

  <= /span>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CB444D.2CE5ABA2-- --===============1991955877== 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 --===============1991955877==-- From ipp-bounces@pwg.org Wed Aug 25 07:36:39 2010 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 3943C3A6B17 for ; Wed, 25 Aug 2010 07:36:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.086 X-Spam-Level: * X-Spam-Status: No, score=1.086 tagged_above=-999 required=5 tests=[AWL=-0.717, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, J_CHICKENPOX_33=0.6, J_CHICKENPOX_37=0.6, 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 AHRdt0Euq+GW for ; Wed, 25 Aug 2010 07:36:20 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 4D6893A6A41 for ; Wed, 25 Aug 2010 07:36:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6D606793E0; Wed, 25 Aug 2010 10:36:12 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from wvmler6.mail.xerox.com (wvmler6.mail.xerox.com [13.8.138.231]) by pwg.org (Postfix) with ESMTP id 6C119793DD; Wed, 25 Aug 2010 10:36:02 -0400 (EDT) Received: from wvmlir2.mail.xerox.com (wvmlir2.mail.xerox.com [13.147.8.222]) by wvmler6.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7PEa0Eq020536; Wed, 25 Aug 2010 07:36:01 -0700 Received: from wvmlir2.mail.xerox.com (localhost [127.0.0.1]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7PEZraj000889; Wed, 25 Aug 2010 07:35:53 -0700 Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7PEZgoW000316; Wed, 25 Aug 2010 07:35:53 -0700 X-XeroxINT-Source-Ip: 13.135.210.15 X-XeroxINT-Source-Name: usa0300gw002.na.xerox.net X-XeroxINT-Reported-Name: USA0300GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 Aug 2010 10:35:52 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 25 Aug 2010 07:35:46 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Cloud specific element definitions Thread-Index: ActEYs5VzLiPO1H0SCWARNfNKH5adw== From: "Zehler, Peter" To: , X-OriginalArrivalTime: 25 Aug 2010 14:35:52.0993 (UTC) FILETIME=[D1F15910:01CB4462] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Cloud specific element definitions 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="===============0693527185==" 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: 6D606793E0.AAB87 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0693527185== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4462.D12CD798" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4462.D12CD798 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, Here is the semantics and syntax as I understand it for the Cloud Specific model extensions for global identifiers and geolocation.=20=20 Comments? =20 =20 Job Identifiers: *new* job-uuid (SM:JobUuid): The identifier for a job with a global scope. The identifier is unique for a Job across all service instances of any service type. The UUID URN namespace is specified in rfc4122. The format used for "job-uuid" is the string representation of a UUID as a URN. An example is "urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3". The version (aka subtype) used is implementation specific. Version 1 (i.e. time based) is recommended. Datatype: abstract:char[64], IPP:uri MaxLength=3D64, SM:xs:anyURI maxLen=3D64 (Note: Both the local and global identifiers should be mandated. For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the local identifier MUST still be maintained.) =20 ISSUE: Do we recommend/suggest: It is possible to use the time_low portion of the Timestamp in the version 1 UUID as the local identifier. The implementation may then keep only the 128 bit local representation of the UUID and use it to create the appropriate protocol values. =20 Printer Identifiers: *new* printer-uuid (SM:ServiceUuid): The identifier for a Printer with a global scope. The identifier is unique across all service instances of any service type. The UUID URN namespace is specified in rfc4122. The format used for "job-uuid" is the string representation of a UUID as a URN. An example is "urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3". The version (aka subtype) used is implementation specific. Version 1 (i.e. time based) is recommended. Datatype: abstract:char[64], IPP:uri, SM:xs:anyURI maxLen=3D64=20 =20 Printer Location: *new* printer-geo-location (SM:ServiceGeoLocation): This identifies the location of the associated device using the World Geodetic System 1984(WGS84). The means for expressing the location information is aligned with those used in DNS [RFC1876] Datatype: abstract:class, IPP:collection, SM:sequence =20 *new* size (SM:Size): Diameter of the bounding sphere containing the device expressed in centimeters. Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for size as a pair of 4 bit integers with value between 0 and 9. The first integer is the base and the second the exponent.) =20 *new* horizontal-precision (SM: HorizontalPrecision): The horizontal precision expressed as the diameter of the "circle of error" (i.e. twice the +- error value) The units are centimeters. Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for horizontal-precision as a pair of 4 bit integers with value between 0 and 9. The first integer is the base and the second the exponent.) =20 *new* vertical-precision (SM: VerticalPrecision): The vertical precision expressed as the diameter of the "circle of error" (i.e. twice the +- error value) The units are centimeters. Datatype: abstract:integer, IPP: int32, SM:xs:int (Note: rfc1876 encodes the value for vertical-precision as a pair of 4 bit integers with value between 0 and 9. The first integer is the base and the second the exponent.) =20 *new* latitude (SM:Latitude): The latitude of the center of the sphere described by the size attribute. Expressed in thousandths of a second of arc. The 0 represents the equator. Positive values above that are north and Negative values are south. Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for the equator as 2147483648 (231) to keep the latitude value positive.) =20 *new* longitude (SM:Latitude): The longitude of the center of the sphere described by the size attribute. Expressed in thousandths of a second of arc. The value 0 represents the prime meridian. Positive values above that are east and negative values are west. The value is rounded away from the prime meridian Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for the prime meridian as 2147483648 (231) to keep the longitude value positive.) =20 *new* altitude (SM:Altitude): The altitude of the center of the sphere described by the size attribute. Expressed in centimeters from a base of the reference spheroid used by GPS [WGS 84]. Altitude above (or below) sea level may be used as an approximation of altitude relative to the [WGS 84] spheroid, though due to the Earth's surface not being a perfect spheroid, there will be differences. Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for the base as 100,000m below the reference spheroid used by GPS [WGS 84]to keep the altitude value positive.) =20 =20 references: [WGS84]=20 World Geodetic System 1984, Last revised 2004, National Geospatial-Intelligence Agency, =20 [RFC1876]=20 RFC1876: A Means for Expressing Location Information in the Domain Name System, January 1996, C. Davis, P. Vixie, T. Goodwin, I. Dickinson, =20 =20 =20 Geolocation examples: 2-Dimmensional Location of my office printer Google Map URL: http://maps.google.com/maps?f=3Dq&source=3Ds_q&hl=3Den&geocode=3D&q=3D800+p= hillips +rd+webster+ny+14580&sll=3D37.0625,-95.677068&sspn=3D62.226996,106.962891&ie =3DUTF8&hq=3D&hnear=3D800+Phillips+Rd,+Webster,+Monroe,+New+York+14580&ll= =3D43.2 20973,-77.417162&spn=3D0.001781,0.003264&t=3Dh&z=3D19=20 Location representations: Decimal Degrees (WGS84) Latitude Longitude=20 43.220973 -77.417162=20 Degrees, Minutes & Seconds Latitude Longitude=20 N43 13 15 W77 25 01=20 GPS Latitude Longitude=20 N 43 13.258 W 77 25.030=20 UTM X Y=20 18N 303685 4788191=20 =20 My office elevation: 128 meters (419 feet) above sea level Size of Printer: 91 centimeter (3 feet) Margin of error 183 centimeter (6 feet) =20 DNS LOC record (RFC1876) Version =3D 0 Size =3D 18 (0x12) (encoded centimeter) HorizontalPrecision =3D 34 (0x22) (encoded centimeter) VerticalPrecision =3D 34 (0x22) (encoded centimeter) Latitude =3D 2303079151 (0x8946, 0x32EF) (thousandths of a second of arc) ) (2147483648 +(DecimalDegreeLatitude*60*60*1000) ) (North is positive) Longitude =3D 1868781865 (0x6F63, 0x5929)(thousandths of a second of arc) ( 2147483648-(DecimalDegreeLongitude*60*60*1000) ) (West is negative) Altitude =3D 10012800 (0x0098, 0xC880)(centimeter) (OfficeElevation+10000000) PrinterGeoLocation (PWG) Size =3D 91 (centimeter) HorizontalPrecision =3D 183 (centimeter) VerticalPrecision =3D 183 (centimeter) Latitude =3D 155595503 (thousandths of a second of arc) ) ( DecimalDegreeLatitude*60*60*1000 ) (North is positive) Longitude =3D -278701783 (thousandths of a second of arc) (DecimalDegreeLongitude*60*60*1000) (West is negative) Altitude =3D 12800 (centimeter) (above sea level (i.e. reference spheroid used by GPS) is positive) =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_01CB4462.D12CD798 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

Here is the semantics and syntax as I understand it for the Cloud Specific model extensions for global identifiers and geolocation. 

Comments?

 

 

Job Identifiers:

*new*

job-uuid (SM:JobUuid):  The identifier for a job = with a global scope.  The identifier is unique for a Job across all service instances of any service type.    The UUID URN namespace is specified in rfc4122.  The format used for “job-uuid” is t= he string representation of a UUID as a URN.  An example is “urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3”.  The version (aka subtype) used is implementation specific.  Version 1 (i.e. time based) is recommended.   Datatype: abstract:char[64], IPP:uri MaxLength=3D64, SM:xs:anyURI maxLen=3D64 (Note: Both the local and = global identifiers should be mandated.  For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the local identifier MUST still be maintained.)

 

ISSUE: Do we recommend/suggest:  It is possible t= o use the time_low portion of the Timestamp in the version 1 UUID as the local identifier.  The implementation may then keep only the 128 bit local representation of the UUID and use it to create the appropriate protocol values.

 

Printer Identifier= s:

*new*

printer-uuid (SM:ServiceUuid):  The identifier fo= r a Printer with a global scope.  The identifier is unique across all serv= ice instances of any service type.    The UUID URN namespace is specified in rfc4122.  The format used for “job-uuid” is t= he string representation of a UUID as a URN.  An example is “urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3”.  The version (aka subtype) used is implementation specific.  Version 1 (i.e. time based) is recommended.   Datatype: abstract:char[64], IPP:uri, SM:xs:anyURI maxLen=3D64

 

Printer Location:<= o:p>

*new*

printer-geo-location (SM:ServiceGeoLocation):  Th= is identifies the location of the associated device using the World Geodetic System 1984(WGS84).  The means for expressing the location information= is aligned with those used in DNS [RFC1876]  Datatype: abstract:class, IPP:collection, SM:sequence

 

*new*

size (SM:Size):  Diame= ter of the bounding sphere containing the device expressed in centimeters.    Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc187= 6 encodes the value for size as a pair of 4 bit integers with value between 0 and 9.  The first integer is the base and the second the exponent.)

 

*new*

horizontal-precision (SM: HorizontalPrecision):  The horizontal precision expressed as the diame= ter of the “circle of error” (i.e. twice the +- error value)  = The units are centimeters.    Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for horizontal-precision  as a pair of 4 bit integers with value between 0= and 9.  The first integer is the base and the second the exponent.)

 

*new*

vertical-precision (SM: VerticalPrecision):  The vertical precision expressed as the diameter = of the “circle of error” (i.e. twice the +- error value)  The units are centimeters.    Datatype: abstract:integer, IPP: int32, SM:xs:int (Note: rfc1876 encodes the value for vertical-precision as= a pair of 4 bit integers with value between 0 and 9.  The first integer = is the base and the second the exponent.)

 

*new*

latitude (SM:Latitude):&nbs= p; The latitude of the center of the sphere described by the size attribute.  Expressed in thousandths of a second of arc.  The 0 represents the equator.  Positive values above that are north and Negative values are south.   Datatype: abstract: int32, IPP:integer, SM:xs:int  (Note: rfc1876 encodes the value for the equator as 2147483648  (231) to keep the latitude value positive.)

 

*new*

longitude (SM:Latitude):&nb= sp; The longitude of the center of the sphere described by the size attribute.  Expressed in thousandths of a second of arc.  The value 0 represents t= he prime meridian.  Positive values above that are east and negative valu= es are west.  The value is rounded away from the prime meridian   Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for the prime meridian as 2147483648  (231) to keep the longitude value positive.)

 

*new*

altitude (SM:Altitude):&nbs= p; The altitude of the center of the sphere described by the size attribute. = Expressed in centimeters from a base of the reference spheroid used by GPS [WGS 84].  Altitude above (or below) sea level may be used as an approximat= ion of altitude relative to the [WGS 84] spheroid, though due to the Earth's surface not being a perfect spheroid, there will be differences.    Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc1876 encodes the value for the base as 100,000m below the reference sphe= roid used by GPS  [WGS 84]to keep the altitude value positive.)<= /p>

 

 

references:

[WGS84]

     &nbs= p;      World Geodetic System 1984, Last revised 2004, National Geospatial-Intelligence Agency,  <https://www1.nga.mil/ProductsServices/GeodesyG= eophysics/WorldGeodeticSystem/Pages/default.aspx>

[RFC1876]

     &nbs= p;      RFC1876: A Means for Expressing Location Information in the Domain Name System, Janu= ary 1996, C. Davis, P. Vixie, T. Goodwin, I. Dickinson,&nb= sp; <http://tools.ietf.org/rfc/rf= c1876.txt>

 

 

Geolocation examples:

2-Dimmen= sional Location of my office printer

Google Map = URL:

http://maps.google.com= /maps?f=3Dq&source=3Ds_q&hl=3Den&geocode=3D&q=3D800+phillip= s+rd+webster+ny+14580&sll=3D37.0625,-95.677068&sspn=3D62.226996,106= .962891&ie=3DUTF8&hq=3D&hnear=3D800+Phillips+Rd,+Webster,+Monro= e,+New+York+14580&ll=3D43.220973,-77.417162&spn=3D0.001781,0.003264= &t=3Dh&z=3D19

Location representations:

Decimal Deg= rees (WGS84)

Latitude Longitude =
43.220973 -77.417162

Degrees, Mi= nutes & Seconds

Latitude Longitude =
N43 13 15 W77 25 01

GPS

Latitude Longitude =
N 43 13.258 W 77 25.030

UTM

 X Y

18N 303685 4788191 =

 

My office elevation:

128 meters (419 fee= t) above sea level

Size of = Printer:

91 centimeter (3 fe= et)

Margin o= f error

183 centimeter (6 f= eet)

 

DNS LOC record (RFC1876)

Version =3D 0
Size =3D 18 (0x12) (encoded centimeter)
HorizontalPrecision =3D 34 (0x22)  (encoded centimeter)
VerticalPrecision =3D 34 (0x22)  (encoded centimeter)

Latitude =3D 2303079151 (0x8946, 0x32EF) (thous= andths of a second of arc) )  (2147483648 +(= DecimalDegreeLatitude*60*60*1000) ) (North is positive)

Longitude =3D 1868781865 (0x6F63, 0x5929)(thous= andths of a second of arc) ( 2147483648-(DecimalDegreeLongitude*60*60*1000) ) (West is negative)<= br> Altitude =3D 10012800 (0x0098, 0xC880)(centimeter) (OfficeElevation+1000000= 0)

PrinterGeoLocation (PWG)

Size =3D 91 (centimeter)
HorizontalPrecision =3D 183 (centimeter)
VerticalPrecision =3D 183 (centimeter)

Latitude =3D 155595503 (thousandths of a second= of arc) )  ( DecimalDegreeLatitude*60*60*1000= ) (North is positive)

Longitude =3D -278701783 (thousandths of a seco= nd of arc) (DecimalDegreeLongitude*60*60*1000) &= nbsp;(West is negative)
Altitude =3D 12800 (centimeter) (above sea level (i.e. reference spheroid u= sed by GPS) is positive)

 

 =

Peter Zehler

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

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CB4462.D12CD798-- --===============0693527185== 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 --===============0693527185==-- From ipp-bounces@pwg.org Wed Aug 25 11:52:59 2010 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 941F83A6888 for ; Wed, 25 Aug 2010 11:52:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cm73P+3YMQ9w for ; Wed, 25 Aug 2010 11:52:58 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 284273A687F for ; Wed, 25 Aug 2010 11:52:58 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id EE0D8793ED; Wed, 25 Aug 2010 14:53:27 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by pwg.org (Postfix) with ESMTP id 59020793E1 for ; Wed, 25 Aug 2010 14:53:23 -0400 (EDT) Received: by pvg2 with SMTP id 2so335419pvg.5 for ; Wed, 25 Aug 2010 11:53:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=TY7VWSWUfVQMHxaqmAQZ4nM5wYsStrkrEjYhF1BTGCM=; b=Y3xgtE3inShLxFu9zjeXHE/GE/JR3LoBwwrftcfEUTe3PwE0ZBi8gSMVS+XTnGM+z7 t3Oj5k5L+Vn/ZprSNFYlhULKsi6yc8g/HE89JWp1TwaaX5P9TM6Cd1XDIS5ac9MGpQp9 Zihq9/wZrh/rqz7WbeBedgWOBNA/3FplEbNVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pBdSC6AHFF+GMq6GPWQLOabtjMtSdgl/tfWVcUyrOw0ex3j1YaHfbcT8kcvtHdboA3 2P336qonT7PCWM0xmMoT/O6xJeuZUwZjfqNcQBjh2vAjTc3WfabGdJvdq8h9GLuLH4O/ KQoXJs0Tfe4akeluFuwk/FVR+rBR9ibIv3eoA= MIME-Version: 1.0 Received: by 10.114.133.14 with SMTP id g14mr9950674wad.192.1282762403142; Wed, 25 Aug 2010 11:53:23 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Wed, 25 Aug 2010 11:53:23 -0700 (PDT) Date: Wed, 25 Aug 2010 14:53:23 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Michael R Sweet , Ira McDonald Content-Type: text/plain; charset=ISO-8859-1 X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) 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: EE0D8793ED.A92D7 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi, I've just posted an Initial draft of IPPS URI Scheme: ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100825.txt - plaintext Internet-Draft format (w/ explicit formfeeds) ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100825.htm - HTML w/ live table of contents Hint: You can view and print the plaintext file easily with MS WordPad. We agreed to do an IPP WG review first before submitting this document to the IETF Internet-Drafts Editor. This document was created by rewriting IPP URI Scheme [RFC3510]. Comments? Cheers, - Ira (IPPS URI Scheme co-editor) ----------------------------------------------------- Change Log 25 August 2010 - draft-mcdonald-ipps-uri-scheme-00.txt - Editorial - complete rewrite of RFC 3510 for new transport binding - Technical - added section 3.2 IPP over HTTP Transport Binding - Technical - added section 3.3 IPP over HTTPS Transport Binding - Editorial - updated Appendix A w/ registration template from RFC 4395 -- 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 Wed Aug 25 14:46:10 2010 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 49B333A6B66 for ; Wed, 25 Aug 2010 14:46:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.19 X-Spam-Level: X-Spam-Status: No, score=-102.19 tagged_above=-999 required=5 tests=[AWL=0.409, 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 7by7k2WgQ-9S for ; Wed, 25 Aug 2010 14:46:09 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A388B3A6837 for ; Wed, 25 Aug 2010 14:46:08 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 61D42793C5; Wed, 25 Aug 2010 17:46:31 -0400 (EDT) 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 2A7E8793C0 for ; Wed, 25 Aug 2010 17:46:26 -0400 (EDT) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 58A74AB44ECE; Wed, 25 Aug 2010 14:46:26 -0700 (PDT) X-AuditID: 11807130-b7c6fae0000063ca-e7-4c758f31dc76 Received: from [17.151.86.175] (Unknown_Domain [17.151.86.175]) (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 DE.16.25546.23F857C4; Wed, 25 Aug 2010 14:46:26 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Michael Sweet In-Reply-To: Date: Wed, 25 Aug 2010 14:46:24 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <76E148C0-E243-4D0A-88B7-1C41F52BDE00@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Apple has reviewed IPP/2.0 SE and has comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 61D42793C5.A9421 X-pwg-MailScanner-From: ipp-bounces@pwg.org Comments: 1. The intro paragraph for Section 3 is a bit repetitious. I recommend com= bining the last two sentences to read "This section also describes ... and = defines ...". 2. Missing bullet on line 236 3. Bad justification on line 338 4. Suggest the removal of "and because REQUIRED Create-Job/Print-Job in IPP= /2.1 make Validate-Job trivial to implement" from lines 382-383 since we ar= e not in the position to make that assessment. 5. Suggest the removal of "and because REQUIRED Create-Job/Print-Job in IPP= /2.1 make Validate-Job trivial to implement" from lines 408-409 since we ar= e not in the position to make that assessment. 6. Suggest change of wording on line 448: "because it OFTEN cannot be suppo= rted" 7. Suggest change of wording on line 470: "because it OFTEN cannot be suppo= rted" 8. Suggest change of wording on line 498: "because it OFTEN cannot be suppo= rted" 9. Missing 2.2 version after line 581 for IANA registration. ________________________________________________________________________ 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 Wed Aug 25 15:23:03 2010 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 4FDCC3A6926 for ; Wed, 25 Aug 2010 15:23:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.057 X-Spam-Level: X-Spam-Status: No, score=-100.057 tagged_above=-999 required=5 tests=[AWL=-1.860, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, J_CHICKENPOX_33=0.6, J_CHICKENPOX_37=0.6, 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 wScPNIRJsYGM for ; Wed, 25 Aug 2010 15:23:01 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id BE0E23A6801 for ; Wed, 25 Aug 2010 15:23:00 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 422B879330; Wed, 25 Aug 2010 18:23:23 -0400 (EDT) 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 6E24A7919C; Wed, 25 Aug 2010 18:23:14 -0400 (EDT) Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id CCCA7AB46C5C; Wed, 25 Aug 2010 15:23:13 -0700 (PDT) X-AuditID: 11807137-b7c08ae00000377a-19-4c7597cfe763 Received: from [17.151.86.175] (Unknown_Domain [17.151.86.175]) (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 9A.D8.14202.0D7957C4; Wed, 25 Aug 2010 15:23:13 -0700 (PDT) Subject: Re: [IPP] Cloud specific element definitions Mime-Version: 1.0 (Apple Message framework v1081) From: Michael Sweet In-Reply-To: Date: Wed, 25 Aug 2010 15:23:11 -0700 Message-Id: <4712CA24-9469-4F12-A845-D3D47717A4DC@apple.com> References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1081) X-Brightmail-Tracker: AAAAAQAAAZE= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, mfd@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0000262161==" 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: 422B879330.A98A6 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0000262161== Content-Type: multipart/alternative; boundary=Apple-Mail-5--474886235 --Apple-Mail-5--474886235 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Aug 25, 2010, at 7:35 AM, Zehler, Peter wrote: > All, > Here is the semantics and syntax as I understand it for the Cloud Specifi= c model extensions for global identifiers and geolocation.=20 > Comments? >=20=20 >=20=20 > Job Identifiers: > *new* > job-uuid (SM:JobUuid): The identifier for a job with a global scope. Th= e identifier is unique for a Job across all service instances of any servic= e type. The UUID URN namespace is specified in rfc4122. The format used= for =93job-uuid=94 is the string representation of a UUID as a URN. An ex= ample is =93urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3=94. The version = (aka subtype) used is implementation specific. Version 1 (i.e. time based)= is recommended. Datatype: abstract:char[64], IPP:uri MaxLength=3D64, SM:= xs:anyURI maxLen=3D64 (Note: Both the local and global identifiers should b= e mandated. For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the= local identifier MUST still be maintained.) >=20=20 > ISSUE: Do we recommend/suggest: It is possible to use the time_low porti= on of the Timestamp in the version 1 UUID as the local identifier. The imp= lementation may then keep only the 128 bit local representation of the UUID= and use it to create the appropriate protocol values. While that could certainly be an appropriate implementation choice, I don't= think we should make a recommendation beyond the requirement for an RFC 41= 22 UUID. =20 > Printer Identifiers: > *new* > printer-uuid (SM:ServiceUuid): The identifier for a Printer with a globa= l scope. The identifier is unique across all service instances of any serv= ice type. The UUID URN namespace is specified in rfc4122. The format us= ed for =93job-uuid=94 is the string representation of a UUID as a URN. An = example is =93urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3=94. The versio= n (aka subtype) used is implementation specific. Version 1 (i.e. time base= d) is recommended. Datatype: abstract:char[64], IPP:uri, SM:xs:anyURI max= Len=3D64 >=20=20 > Printer Location: > *new* > printer-geo-location (SM:ServiceGeoLocation): This identifies the locati= on of the associated device using the World Geodetic System 1984(WGS84). T= he means for expressing the location information is aligned with those used= in DNS [RFC1876] Datatype: abstract:class, IPP:collection, SM:sequence >=20=20 > *new* > size (SM:Size): Diameter of the bounding sphere containing the device ex= pressed in centimeters. Datatype: abstract: int32, IPP:integer, SM:xs:in= t (Note: rfc1876 encodes the value for size as a pair of 4 bit integers wit= h value between 0 and 9. The first integer is the base and the second the = exponent.) >=20=20 > *new* > horizontal-precision (SM: HorizontalPrecision): The horizontal precision= expressed as the diameter of the =93circle of error=94 (i.e. twice the +- = error value) The units are centimeters. Datatype: abstract: int32, IPP:= integer, SM:xs:int (Note: rfc1876 encodes the value for horizontal-precisio= n as a pair of 4 bit integers with value between 0 and 9. The first integ= er is the base and the second the exponent.) >=20=20 > *new* > vertical-precision (SM: VerticalPrecision): The vertical precision expre= ssed as the diameter of the =93circle of error=94 (i.e. twice the +- error = value) The units are centimeters. Datatype: abstract:integer, IPP: int3= 2, SM:xs:int (Note: rfc1876 encodes the value for vertical-precision as a p= air of 4 bit integers with value between 0 and 9. The first integer is the= base and the second the exponent.) >=20=20 > *new* > latitude (SM:Latitude): The latitude of the center of the sphere describ= ed by the size attribute. Expressed in thousandths of a second of arc. Th= e 0 represents the equator. Positive values above that are north and Negat= ive values are south. Datatype: abstract: int32, IPP:integer, SM:xs:int = (Note: rfc1876 encodes the value for the equator as 2147483648 (231) to ke= ep the latitude value positive.) >=20=20 > *new* > longitude (SM:Latitude): The longitude of the center of the sphere descr= ibed by the size attribute. Expressed in thousandths of a second of arc. = The value 0 represents the prime meridian. Positive values above that are = east and negative values are west. The value is rounded away from the prim= e meridian Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rfc18= 76 encodes the value for the prime meridian as 2147483648 (231) to keep th= e longitude value positive.) >=20=20 > *new* > altitude (SM:Altitude): The altitude of the center of the sphere describ= ed by the size attribute. Expressed in centimeters from a base of the refe= rence spheroid used by GPS [WGS 84]. Altitude above (or below) sea level m= ay be used as an approximation of altitude relative to the [WGS 84] spheroi= d, though due to the Earth's surface not being a perfect spheroid, there wi= ll be differences. Datatype: abstract: int32, IPP:integer, SM:xs:int (No= te: rfc1876 encodes the value for the base as 100,000m below the reference = spheroid used by GPS [WGS 84]to keep the altitude value positive.) >=20=20 >=20=20 > references: > [WGS84] > World Geodetic System 1984, Last revised 2004, National Geosp= atial-Intelligence Agency, >=20 > [RFC1876] > RFC1876: A Means for Expressing Location Information in the D= omain Name System, January 1996, C. Davis, P. Vixie, T. Goodwin, I. Dickins= on, >=20 >=20=20 >=20=20 > Geolocation examples: > 2-Dimmensional Location of my office printer > Google Map URL: > http://maps.google.com/maps?f=3Dq&source=3Ds_q&hl=3Den&geocode=3D&q=3D800= +phillips+rd+webster+ny+14580&sll=3D37.0625,-95.677068&sspn=3D62.226996,106= .962891&ie=3DUTF8&hq=3D&hnear=3D800+Phillips+Rd,+Webster,+Monroe,+New+York+= 14580&ll=3D43.220973,-77.417162&spn=3D0.001781,0.003264&t=3Dh&z=3D19 > Location representations: > Decimal Degrees (WGS84) > Latitude Longitude=20 > 43.220973 -77.417162 > Degrees, Minutes & Seconds > Latitude Longitude=20 > N43 13 15 W77 25 01 > GPS > Latitude Longitude=20 > N 43 13.258 W 77 25.030 > UTM > X Y > 18N 303685 4788191 >=20=20 > My office elevation: > 128 meters (419 feet) above sea level > Size of Printer: > 91 centimeter (3 feet) > Margin of error > 183 centimeter (6 feet) >=20=20 > DNS LOC record (RFC1876) > Version =3D 0 > Size =3D 18 (0x12) (encoded centimeter) > HorizontalPrecision =3D 34 (0x22) (encoded centimeter) > VerticalPrecision =3D 34 (0x22) (encoded centimeter) > Latitude =3D 2303079151 (0x8946, 0x32EF) (thousandths of a second of arc)= ) (2147483648 +(DecimalDegreeLatitude*60*60*1000) ) (North is positive) > Longitude =3D 1868781865 (0x6F63, 0x5929)(thousandths of a second of arc)= ( 2147483648-(DecimalDegreeLongitude*60*60*1000) ) (West is negative) > Altitude =3D 10012800 (0x0098, 0xC880)(centimeter) (OfficeElevation+10000= 000) > PrinterGeoLocation (PWG) > Size =3D 91 (centimeter) > HorizontalPrecision =3D 183 (centimeter) > VerticalPrecision =3D 183 (centimeter) > Latitude =3D 155595503 (thousandths of a second of arc) ) ( DecimalDegre= eLatitude*60*60*1000 ) (North is positive) > Longitude =3D -278701783 (thousandths of a second of arc) (DecimalDegreeL= ongitude*60*60*1000) (West is negative) > Altitude =3D 12800 (centimeter) (above sea level (i.e. reference spheroid= used by GPS) is positive) >=20=20 >=20=20 > Peter Zehler >=20 > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Apple-Mail-5--474886235 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
All,
Here is the se= mantics and syntax as I understand it for the Cloud Specific model extensio= ns for global identifiers and geolocation. 
Comments?
 =
 
Job Identifiers:
*new*
job-uuid (SM:JobUuid):  The identifier for a job with a global sc= ope.  The identifier is unique for a Job across all service instances = of any service type.    The UUID URN namespace is specified = in rfc4122.  The format used for =93job-uuid=94 is the string represen= tation of a UUID as a URN.  An example is =93urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3=94.&nb= sp; The version (aka subtype) used is implementation specific.  Versio= n 1 (i.e. time based) is recommended.   Datatype: abstract:char[6= 4], IPP:uri MaxLength=3D64, SM:xs:anyURI maxLen=3D64 (Note: Both the local = and global identifiers should be mandated.  For legacy protocol mappin= gs (e.g. IPP 1.1, WS-Print, LPR) the local identifier MUST still be maintai= ned.)
 
ISSUE: Do we recommend/suggest:  = It is possible to use the time_low portion of the Timestamp in the version = 1 UUID as the local identifier.  The implementation may then keep only= the 128 bit local representation of the UUID and use it to create the appr= opriate protocol values.

While that could certainly be an appropriate implementation choice, I don= 't think we should make a recommendation beyond the requirement for an RFC = 4122 UUID.
 
Printer Id= entifiers:
*new*
printer-uuid (= SM:ServiceUuid):  The identifier for a Printer with a global scope.&nb= sp; The identifier is unique across all service instances of any service ty= pe.    The UUID URN namespace is specified in rfc4122. = The format used for =93job-uuid=94 is the string representation of a UUID = as a URN.  An example is =93u= rn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3=94.  The version (= aka subtype) used is implementation specific.  Version 1 (i.e. time ba= sed) is recommended.   Datatype: abstract:char[64], IPP:uri, SM:x= s:anyURI maxLen=3D64
 
Printer Location:
*new*
printer-geo-location (SM:ServiceGeoLocation):  This identifies th= e location of the associated device using the World Geodetic System 1984(WG= S84).  The means for expressing the location information is aligned wi= th those used in DNS [RFC1876]  Datatype: abstract:class, IPP:collecti= on, SM:sequence
 
*new*<= /div>
 
<= div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; m= argin-left: 0.5in; font-size: 11pt; font-family: Calibri, sans-serif; ">*new
*
horizontal-precision (SM: HorizontalPrecision):&nbs= p; The horizontal precision expressed as the diameter of the =93circle of e= rror=94 (i.e. twice the +- error value)  The units are centimeters.&nb= sp;   Datatype: abstract: int32, IPP:integer, SM:xs:int (Note: rf= c1876 encodes the value for horizontal-precision  as a pair of 4 bit i= ntegers with value between 0 and 9.  The first integer is the base and= the second the exponent.)
 
*new*=
vertical-precision (SM: VerticalPrecision):  The vertic= al precision expressed as the diameter of the =93circle of error=94 (i.e. t= wice the +- error value)  The units are centimeters.    = ;Datatype: abstract:integer, IPP: int32, SM:xs:int (Note: rfc1876 encodes t= he value for vertical-precision as a pair of 4 bit integers with value betw= een 0 and 9.  The first integer is the base and the second the exponen= t.)
 
*new*
latitude = (SM:Latitude):  The latitude of the center of the sphere described by = the size attribute.  Expressed in thousandths of a second of arc. = ; The 0 represents the equator.  Positive values above that are north = and Negative values are south.   Datatype: abstract: int32, IPP:i= nteger, SM:xs:int  (Note: rfc1876 encodes the value for the equator as= 2147483648  (231) to keep the latitude value positive.)
 
*new*
longitude (SM:L= atitude):  The longitude of the center of the sphere described by the = size attribute.  Expressed in thousandths of a second of arc.  Th= e value 0 represents the prime meridian.  Positive values above that a= re east and negative values are west.  The value is rounded away from = the prime meridian   Datatype: abstract: int32, IPP:integer, SM:x= s:int (Note: rfc1876 encodes the value for the prime meridian as 2147483648=  (231) to keep the longitude value positive.)
*new*
altitude (SM:Altitude):&n= bsp; The altitude of the center of the sphere described by the size attribu= te.  Expressed in centimeters from a base of the reference spheroid us= ed by GPS [WGS 84].  Altitude above (or below) sea level may be used a= s an approximation of altitude relative to the [WGS 84] spheroid, though du= e to the Earth's surface not being a perfect spheroid, there will be differ= ences.    Datatype: abstract: int32, IPP:integer, SM:xs:int = (Note: rfc1876 encodes the value for the base as 100,000m below the referen= ce spheroid used by GPS  [WGS 84]to keep the altitude value positive.)=
 
 
references:

[WGS84]

          &n= bsp; World Geodetic System 1984, Last revised 2004, National Geospatial-Int= elligence Agency,  <https://www1.nga.mil/ProductsSe= rvices/GeodesyGeophysics/WorldGeodeticSystem/Pages/default.aspx>

[RFC1876]

         &n= bsp;  RFC1876: A Means for Expressing Location Information in the Doma= in Name System, January 1996, C. Davis, P. Vixie, T. Goodwin, I. Dickinson,  <http://tools.ietf.org/rfc/rfc1876.txt>
 
 
Geolocation examples:
<= u>2-Dimmensional Location of my office pr= inter
Goo= gle Map URL:
Location representations:
Decimal Degrees (WGS84)
 43.220973 -77.417162
De= grees, Minutes & Seconds
Latitude Longitude 
N43 13 15 W77 25 01<= /o:p>
GPS
La= titude Longitude 
N 43= 13.258 W 77 25.030
UTM<= o:p>
 X Y
18N 303685 4788191<= /div>
 
My office ele= vation:
128 meters (419 feet) above sea level
Size of Printer:
91 centimeter (3 feet)
Margin of error
183 centi= meter (6 feet)
 
DNS LOC record (RFC1876)
Version = =3D 0
Size =3D 18 (0x12) (encoded centimeter)
HorizontalPrecision =3D= 34 (0x22)  (encoded centimeter)
VerticalPrecision =3D 34 (0x22)&nb= sp; (encoded centimeter)
Latitude =3D 2303079151 (0x8946, 0x3= 2EF) (thousandths of a second of arc) )  (2147483648 +(Decima= lDegreeLatitude*60*60*1000) ) (North is positive)
Long= itude =3D 1868781865 (0x6F63, 0x5929)(thousandths of a second of arc) ( 2147483648-(DecimalDegreeLongitude*60*60*1000) ) (West is negative)
Altitude =3D 10012800 (0x0098, 0xC880)(centimeter) (OfficeElevatio= n+10000000)
PrinterGeoL= ocation (PWG)
Size =3D 91 (centimeter)
Hori= zontalPrecision =3D 183 (centimeter)
VerticalPrecision =3D 183 (centimet= er)
Latitude =3D 155595503 (thousandths of a second of arc) )=   ( DecimalDegreeLatitude*60*60*1000 ) (North is positive)
Longitude =3D -278701783 (thousandths of a second of arc= ) (DecimalDegreeLongitude*60*60*1000)  (West is negative)
Altitude =3D 12800 (centimeter) (above sea level (i.e. reference sph= eroid used by GPS) is positive)
 
 
Peter Zehler

Xerox Research Center We= bster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755=
FAX: (585) 265-744= 1
US Mail: P= eter Zehler
= Xerox Corp.

= 800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
 
<= /div>
-- 
This mess= age has been scanned for viruses and&= nbsp;
dangerous content by&= nbsp;MailScanner, and is 
believed to be clean. ______________________________________= _________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp

___________________= _____________________________________________________
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-5--474886235-- --===============0000262161== 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 --===============0000262161==-- From ipp-bounces@pwg.org Thu Aug 26 03:27:37 2010 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 836023A681D for ; Thu, 26 Aug 2010 03:27:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 85XWlOnFbXZj for ; Thu, 26 Aug 2010 03:27:35 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 43F5D3A67F3 for ; Thu, 26 Aug 2010 03:27:35 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1D626793F9; Thu, 26 Aug 2010 06:27:53 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by pwg.org (Postfix) with ESMTP id A17DD793F5; Thu, 26 Aug 2010 06:27:45 -0400 (EDT) Received: from FamilyRoom ([unknown] [71.189.7.213]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0L7R00G9P91X78T1@vms173019.mailsrvcs.net>; Thu, 26 Aug 2010 05:27:34 -0500 (CDT) From: "Tom Hastings" To: References: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> Date: Thu, 26 Aug 2010 03:27:31 -0700 Message-id: <01DE79BD39BE4A2A9444F4A61B7510F2@FamilyRoom> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 Thread-index: ActBXBSu7ikPHcGRSUmFIk0WXqImLgDq++jw X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 In-reply-to: X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org, Michael Sweet Subject: [IPP] RE: [Pwg-Announce] Re: PWG Last Call of IPP JPS2 (26 July to 27 August 2010) [Abstract & Summary of changes] X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tom.hastings@alum.mit.edu 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: 1D626793F9.AA2E8 X-pwg-MailScanner-From: ipp-bounces@pwg.org The Draft IPP Job and Printer Extensions - Set 2 (JPS2) specification is up for PWG Last Call with comments due this Friday, August 27. See Ira's reminder at the end of this email for how to do this.=20=20 The intent of this email is to encourage member companies to submit their comments, if any. This email has the current abstract and the list of the technical changes since the August 3, 2009 version whose technical content was the same as the version submitted by Xerox seven years ago on 21 August 2002. Here is the current Abstract: Abstract: This Job and Printer Extensions - Set 2 Specification (JPS2) defines an extension to the Internet Printing Protocol/1.0 (IPP) ([RFC2565], [RFC2566]), IPP/1.1 ([RFC2910], [RFC2911]), and [RFC3380]. This JPS2 consists of a REQUIRED Job Template attribute to print a proof print(s) of the job prior to printing the full run of the job and OPTIONAL Job Template attributes for submitting print jobs that permit a user to save jobs for later reprinting (i.e., retain the jobs indefinitely), provide a recipient name and a job phone number, provide the feed orientation, provide the font name and font size, hold a job until a specific date and time, delay the output of a job (but allow processing) until a specified time period, delay the output of a job (but allow processing) until a specific date and time, and specify an interpreter initialization file. =20=20 This JPS2 also defines four new REQUIRED operations - Cancel-Jobs, Cancel-My-Jobs, Close-Job, and Resubmit-Job - and a new REQUIRED "job-ids" operation attribute to be used with the existing Get-Jobs and Purge-Jobs operations. Cancel-Jobs allows an operator/administrator to cancel a list of Not Completed jobs or all Not Completed jobs on the Printer. Cancel-My-Jobs allows a user to cancel a list of their Not Completed jobs or all their Not Completed jobs. Close-Job allows a client to close a multi-document job without supplying any additional documents (to support streaming clients and servers). Resubmit-Job allows a user to re-process a modified copy of a Retained Job. Get-Jobs with the "job-ids" attribute allows a user to get a list of jobs. Purge-Jobs with the "job-ids" attribute allows an operator/administrator to purge a list of jobs. There are also Printer Description attributes to list the Job Creation attributes supported, indicate whether jobs are spooled, and list the set of media collections supported. In addition, conformance to JPS2 also REQUIRES support of the Reprocess-Job operation defined in [RFC3998]. Some of the Job Template attributes defined in this specification are also defined to be supplied as Operation attributes in the Hold-Job ([RFC2911]) and Set-Job-Attributes ([RFC3380]) operations. In addition, OPTIONAL semantics for Attribute Precedence, a Queue Override Feature, and a feature to guarantee protocol precedence over the PDL attribute are defined. Here is the summary of the technical changes to the Draft IPP Job and Printer Extensions - Set 2 (JPS2) since August 3, 2009 (in order to keep this list short, the non-technical changes, such as new diagrams, reformatting tables, editorial improvement, adding terminology, etc. is not included): 1. Added the following REQUIRED operations (the original 2002 draft had no new operations defined): a. Cancel-Jobs - allows an operator/administrator to cancel a list of Not Completed jobs or all Not Completed jobs on the Printer. b. Cancel-My-Jobs - allows a user to cancel a list of their Not Completed jobs or all their Not Completed jobs. c. Close-Job - allows a client to close a multi-document job without supplying any additional documents (to support streaming clients and servers). d. Resubmit-Job - prints a Retained Job using the same job template attributes as the saved job, creating a new job (and job ID). 2. Made a Saved Job a special case of a Retained Job (when the client supplies the "job-save-disposition" (collection) Job Template attribute). Use the job's =93job-id=94 integer(1:MAX) as the handle to uniquely identify jobs saved using the Reprocess-Job (defined in RFC 3998) and Resubmit-Job (new) in a Printer context, instead of =93document-uri=94 (uri). Therefore, multiple Saved Jobs can have the same "job-name", since they are uniquely distinguished by their "job-id". Do NOT use the existing Print-URI operation to reprint Saved Jobs. Removed the discussion about Virtual File Name to identify Saved Jobs, since the "job-id" is now used. 3. Made a Proof Print Job a special case of a Retained Job (when the client supplies the "proof-print" (collection) Job Template attribute), so the Proof Print Job winds up in the 'completed' state, rather than the 'pending-held' state while being proof read by a human. The Printer MUST retain the job for an implementation-defined time period that is sufficiently long for the user to be able to proof read the output of the Proof Print job and SHOULD be longer than the aging of normal completed jobs. When the user reprints the Proof Print Job (using either the Resubmit-Job or Reprocess-Job operation), the =93proof-print=94 (collection) attribute is not copied to the new job. 4. Added the "job-delay-output-until" (type3 keyword | name(MAX) and "job-delay-output-until-time" (dateTime) Job Template attributes which delay any output until the specified time period or time, respectively, but allow the Printer to start processing the job. 5. Added a REQUIRED "job-ids" Operation attribute to the existing Get-Jobs and Purge-Jobs operations defined in [RFC2911]. 6. Added 'saved' and 'proof-print' keywords to the "which-jobs" operation attribute used in (1) the Get-Jobs operation and (2) "which-jobs-supported" Printer Description attribute. 7. Added the following "job-state-reasons" values: a. 'job-delay-output-until-specified' b. 'job-printed-successfully' c. 'job-printed-with-errors' d. 'job-printed-with-warnings' 8. Removed the following "job-state-reasons" values: a. 'job-proof-wait' b. 'job-scheduling' 9. Changed the data type of the "job-phone-number" Job Template attribute from text(127) to tel: URI (REQUIRED, if supporting "job-phone-number") with fax: scheme as OPTIONAL. 10. Extended the length of the data type of "job-password-supported" Printer Description attribute from integer(0:127) to integer(0:255), since the password that the client can supply with the "job-password" Operation attribute can be 255 octets.=20 11. To the "media-type" member attribute of the "media-col" Job Template attribute: Added a large number of keywords from [JDF1.4] MediaType and MediaTypeDetails, including the five keywords from =93media-material=94 ('aluminum', 'dry-film', 'paper', 'polyester', 'wet-film') and removed the =93media-material=94 attribute altogether. 12. Added the following Printer Description attributes: a. "job-ids-supported" (boolean) b. "save-name-subdirectory-supported' (boolean) c. "pdl-init-file-name-subdirectory-supported" (boolean) -----Original Message----- From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Ira McDonald Sent: Saturday, August 21, 2010 10:59 To: ipp@pwg.org; Ira McDonald Cc: pwg-announce@pwg.org Subject: [Pwg-Announce] Re: PWG Last Call of IPP JPS2 (26 July to 27 August2010) Hi, Reminder that this PWG Last Call for IPP JPS2 will end this coming Friday (27 August 2010). Please take the time to review this document and send your acknowledgment as described below, so that we can achieve the quorum required by the PWG Process/3.0 in order to exit from PWG Last Call. Thanks, - Ira McDonald (IPP editor) On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > =A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-clea= n.p df > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. =A0The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: =A0ipp@pwg.org > Subject: =A0 has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: =A0The PWG Definition of the Standards Development Process Version = 3.0 > is located at: > > =A0http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From pwg-announce-bounces@pwg.org Thu Aug 26 03:27:44 2010 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 3C5AB3A6359 for ; Thu, 26 Aug 2010 03:27:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599] 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 DB-bT1N+g0qN for ; Thu, 26 Aug 2010 03:27:42 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id ADDDF3A67F3 for ; Thu, 26 Aug 2010 03:27:42 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BDBE5793FD; Thu, 26 Aug 2010 06:27:53 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by pwg.org (Postfix) with ESMTP id A17DD793F5; Thu, 26 Aug 2010 06:27:45 -0400 (EDT) Received: from FamilyRoom ([unknown] [71.189.7.213]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0L7R00G9P91X78T1@vms173019.mailsrvcs.net>; Thu, 26 Aug 2010 05:27:34 -0500 (CDT) From: "Tom Hastings" To: References: <0C3EBE88-178C-4858-9297-BA38C652D9FC@apple.com> Subject: RE: [Pwg-Announce] Re: PWG Last Call of IPP JPS2 (26 July to 27 August 2010) [Abstract & Summary of changes] Date: Thu, 26 Aug 2010 03:27:31 -0700 Message-id: <01DE79BD39BE4A2A9444F4A61B7510F2@FamilyRoom> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 Thread-index: ActBXBSu7ikPHcGRSUmFIk0WXqImLgDq++jw X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 In-reply-to: X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org, Michael Sweet X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tom.hastings@alum.mit.edu 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: BDBE5793FD.ACF2C X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org The Draft IPP Job and Printer Extensions - Set 2 (JPS2) specification is up for PWG Last Call with comments due this Friday, August 27. See Ira's reminder at the end of this email for how to do this.=20=20 The intent of this email is to encourage member companies to submit their comments, if any. This email has the current abstract and the list of the technical changes since the August 3, 2009 version whose technical content was the same as the version submitted by Xerox seven years ago on 21 August 2002. Here is the current Abstract: Abstract: This Job and Printer Extensions - Set 2 Specification (JPS2) defines an extension to the Internet Printing Protocol/1.0 (IPP) ([RFC2565], [RFC2566]), IPP/1.1 ([RFC2910], [RFC2911]), and [RFC3380]. This JPS2 consists of a REQUIRED Job Template attribute to print a proof print(s) of the job prior to printing the full run of the job and OPTIONAL Job Template attributes for submitting print jobs that permit a user to save jobs for later reprinting (i.e., retain the jobs indefinitely), provide a recipient name and a job phone number, provide the feed orientation, provide the font name and font size, hold a job until a specific date and time, delay the output of a job (but allow processing) until a specified time period, delay the output of a job (but allow processing) until a specific date and time, and specify an interpreter initialization file. =20=20 This JPS2 also defines four new REQUIRED operations - Cancel-Jobs, Cancel-My-Jobs, Close-Job, and Resubmit-Job - and a new REQUIRED "job-ids" operation attribute to be used with the existing Get-Jobs and Purge-Jobs operations. Cancel-Jobs allows an operator/administrator to cancel a list of Not Completed jobs or all Not Completed jobs on the Printer. Cancel-My-Jobs allows a user to cancel a list of their Not Completed jobs or all their Not Completed jobs. Close-Job allows a client to close a multi-document job without supplying any additional documents (to support streaming clients and servers). Resubmit-Job allows a user to re-process a modified copy of a Retained Job. Get-Jobs with the "job-ids" attribute allows a user to get a list of jobs. Purge-Jobs with the "job-ids" attribute allows an operator/administrator to purge a list of jobs. There are also Printer Description attributes to list the Job Creation attributes supported, indicate whether jobs are spooled, and list the set of media collections supported. In addition, conformance to JPS2 also REQUIRES support of the Reprocess-Job operation defined in [RFC3998]. Some of the Job Template attributes defined in this specification are also defined to be supplied as Operation attributes in the Hold-Job ([RFC2911]) and Set-Job-Attributes ([RFC3380]) operations. In addition, OPTIONAL semantics for Attribute Precedence, a Queue Override Feature, and a feature to guarantee protocol precedence over the PDL attribute are defined. Here is the summary of the technical changes to the Draft IPP Job and Printer Extensions - Set 2 (JPS2) since August 3, 2009 (in order to keep this list short, the non-technical changes, such as new diagrams, reformatting tables, editorial improvement, adding terminology, etc. is not included): 1. Added the following REQUIRED operations (the original 2002 draft had no new operations defined): a. Cancel-Jobs - allows an operator/administrator to cancel a list of Not Completed jobs or all Not Completed jobs on the Printer. b. Cancel-My-Jobs - allows a user to cancel a list of their Not Completed jobs or all their Not Completed jobs. c. Close-Job - allows a client to close a multi-document job without supplying any additional documents (to support streaming clients and servers). d. Resubmit-Job - prints a Retained Job using the same job template attributes as the saved job, creating a new job (and job ID). 2. Made a Saved Job a special case of a Retained Job (when the client supplies the "job-save-disposition" (collection) Job Template attribute). Use the job's =93job-id=94 integer(1:MAX) as the handle to uniquely identify jobs saved using the Reprocess-Job (defined in RFC 3998) and Resubmit-Job (new) in a Printer context, instead of =93document-uri=94 (uri). Therefore, multiple Saved Jobs can have the same "job-name", since they are uniquely distinguished by their "job-id". Do NOT use the existing Print-URI operation to reprint Saved Jobs. Removed the discussion about Virtual File Name to identify Saved Jobs, since the "job-id" is now used. 3. Made a Proof Print Job a special case of a Retained Job (when the client supplies the "proof-print" (collection) Job Template attribute), so the Proof Print Job winds up in the 'completed' state, rather than the 'pending-held' state while being proof read by a human. The Printer MUST retain the job for an implementation-defined time period that is sufficiently long for the user to be able to proof read the output of the Proof Print job and SHOULD be longer than the aging of normal completed jobs. When the user reprints the Proof Print Job (using either the Resubmit-Job or Reprocess-Job operation), the =93proof-print=94 (collection) attribute is not copied to the new job. 4. Added the "job-delay-output-until" (type3 keyword | name(MAX) and "job-delay-output-until-time" (dateTime) Job Template attributes which delay any output until the specified time period or time, respectively, but allow the Printer to start processing the job. 5. Added a REQUIRED "job-ids" Operation attribute to the existing Get-Jobs and Purge-Jobs operations defined in [RFC2911]. 6. Added 'saved' and 'proof-print' keywords to the "which-jobs" operation attribute used in (1) the Get-Jobs operation and (2) "which-jobs-supported" Printer Description attribute. 7. Added the following "job-state-reasons" values: a. 'job-delay-output-until-specified' b. 'job-printed-successfully' c. 'job-printed-with-errors' d. 'job-printed-with-warnings' 8. Removed the following "job-state-reasons" values: a. 'job-proof-wait' b. 'job-scheduling' 9. Changed the data type of the "job-phone-number" Job Template attribute from text(127) to tel: URI (REQUIRED, if supporting "job-phone-number") with fax: scheme as OPTIONAL. 10. Extended the length of the data type of "job-password-supported" Printer Description attribute from integer(0:127) to integer(0:255), since the password that the client can supply with the "job-password" Operation attribute can be 255 octets.=20 11. To the "media-type" member attribute of the "media-col" Job Template attribute: Added a large number of keywords from [JDF1.4] MediaType and MediaTypeDetails, including the five keywords from =93media-material=94 ('aluminum', 'dry-film', 'paper', 'polyester', 'wet-film') and removed the =93media-material=94 attribute altogether. 12. Added the following Printer Description attributes: a. "job-ids-supported" (boolean) b. "save-name-subdirectory-supported' (boolean) c. "pdl-init-file-name-subdirectory-supported" (boolean) -----Original Message----- From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Ira McDonald Sent: Saturday, August 21, 2010 10:59 To: ipp@pwg.org; Ira McDonald Cc: pwg-announce@pwg.org Subject: [Pwg-Announce] Re: PWG Last Call of IPP JPS2 (26 July to 27 August2010) Hi, Reminder that this PWG Last Call for IPP JPS2 will end this coming Friday (27 August 2010). Please take the time to review this document and send your acknowledgment as described below, so that we can achieve the quorum required by the PWG Process/3.0 in order to exit from PWG Last Call. Thanks, - Ira McDonald (IPP editor) On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > =A0ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-clea= n.p df > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. =A0The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: =A0ipp@pwg.org > Subject: =A0 has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: =A0The PWG Definition of the Standards Development Process Version = 3.0 > is located at: > > =A0http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From ipp-archive@lists.ietf.org Thu Aug 26 21:53:26 2010 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 536903A688E for ; Thu, 26 Aug 2010 21:53:26 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): Subject: ...ve@lists.ietf.org V|AGRA \256 Official Selle[...] X-Spam-Flag: NO X-Spam-Score: -24.242 X-Spam-Level: X-Spam-Status: No, score=-24.242 tagged_above=-999 required=5 tests=[BAYES_80=2, DRUGS_ERECTILE=1, DRUGS_ERECTILE_OBFU=1.5, FUZZY_VPILL=0.687, HELO_DYNAMIC_DIALIN=3.384, HELO_EQ_DIP_DIALIN=1.573, HOST_EQ_DIP_TDIAL=2.144, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, J_CHICKENPOX_14=0.6, MANGLED_VIAGRA=2.5, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_OBFU_VIAGRA=1.666, SUBJECT_NEEDS_ENCODING=0.001, TT_OBSCURED_VIAGRA=1.652, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_WS_SURBL=10, 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 mQQD9nr3JY+T for ; Thu, 26 Aug 2010 21:53:25 -0700 (PDT) Received: from p4FE2AD6D.dip.t-dialin.net (p4FE2AD6D.dip.t-dialin.net [79.226.173.109]) by core3.amsl.com (Postfix) with ESMTP id 02D583A6B49 for ; Thu, 26 Aug 2010 21:53:24 -0700 (PDT) From: ipp-archive@lists.ietf.org To: ipp-archive@lists.ietf.org Subject: ipp-archive@lists.ietf.org V|AGRA Official Seller -91% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20100827045325.02D583A6B49@core3.amsl.com> Date: Thu, 26 Aug 2010 21:53:24 -0700 (PDT)
Click here!

From ipp-archive@megatron.ietf.org Thu Aug 26 21:53:26 2010 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 5D4C23A6B18 for ; Thu, 26 Aug 2010 21:53:26 -0700 (PDT) X-Quarantine-ID: <3JiruLtylSom> X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): Subject: ...megatron.ietf.org V|AGRA \256 Official Selle[...] X-Spam-Flag: NO X-Spam-Score: -24.242 X-Spam-Level: X-Spam-Status: No, score=-24.242 tagged_above=-999 required=5 tests=[BAYES_80=2, DRUGS_ERECTILE=1, DRUGS_ERECTILE_OBFU=1.5, FUZZY_VPILL=0.687, HELO_DYNAMIC_DIALIN=3.384, HELO_EQ_DIP_DIALIN=1.573, HOST_EQ_DIP_TDIAL=2.144, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, J_CHICKENPOX_14=0.6, MANGLED_VIAGRA=2.5, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_OBFU_VIAGRA=1.666, SUBJECT_NEEDS_ENCODING=0.001, TT_OBSCURED_VIAGRA=1.652, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_WS_SURBL=10, 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 3JiruLtylSom for ; Thu, 26 Aug 2010 21:53:25 -0700 (PDT) Received: from p4FE2AD6D.dip.t-dialin.net (p4FE2AD6D.dip.t-dialin.net [79.226.173.109]) by core3.amsl.com (Postfix) with ESMTP id 028F93A6B1A for ; Thu, 26 Aug 2010 21:53:24 -0700 (PDT) From: ipp-archive@megatron.ietf.org To: ipp-archive@megatron.ietf.org Subject: ipp-archive@megatron.ietf.org V|AGRA Official Seller -91% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20100827045325.028F93A6B1A@core3.amsl.com> Date: Thu, 26 Aug 2010 21:53:24 -0700 (PDT)
Click here!

From ipp-bounces@pwg.org Fri Aug 27 13:51:48 2010 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 438303A67B5 for ; Fri, 27 Aug 2010 13:51:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.648 X-Spam-Level: X-Spam-Status: No, score=-0.648 tagged_above=-999 required=5 tests=[AWL=-0.651, BAYES_50=0.001, 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 oyP9h15h9q1h for ; Fri, 27 Aug 2010 13:51:38 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 8BA733A6828 for ; Fri, 27 Aug 2010 13:51:38 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0677979375; Fri, 27 Aug 2010 16:52:00 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by pwg.org (Postfix) with ESMTP id F37B17936B for ; Fri, 27 Aug 2010 16:51:52 -0400 (EDT) Received: from FamilyRoom ([unknown] [71.189.7.213]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0L7T0050RWLR0NI2@vms173007.mailsrvcs.net> for ipp@pwg.org; Fri, 27 Aug 2010 15:51:29 -0500 (CDT) From: "Tom Hastings" To: Date: Fri, 27 Aug 2010 13:51:26 -0700 Message-id: MIME-version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-index: ActGKSVhK863HosJRCSJ4mASefdlhQ== X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Your JPS2 editor has reviewed IPP JPS2 and has comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tom.hastings@alum.mit.edu List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1700842700==" 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: 0677979375.A945C X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1700842700== Content-type: multipart/alternative; boundary="----=_NextPart_000_0240_01CB45EE.F2688460" This is a multi-part message in MIME format. ------=_NextPart_000_0240_01CB45EE.F2688460 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Here are some PWG Last Call Comments from your JPS2 Editor that I found while writing up the changes that we had made over the last year to the draft. Here they are (in HTML with red underlined inserts and blue cross-outs): 6.1 job-password (octetString(255)) for Job Creation operations This Operation attribute may OPTIONALLY be included in the request of the following Job Creation operations: Print-Job, Print-URI, and Create-Job. The OPTIONAL "job-password" operation attribute allows a user to perform Secure Print. The user enters a password in the job submitting application which is encrypted by the client using one of the methods specified by the "job-password-encryption-supported" attribute. The encrypted password is sent to the Printer as the value of the "job-password" attribute. If a "job-password" value is provided, other than a zero-length string, the printer MUST hold the job in the 'pending-held' state, and the 'job-password-wait' value is added to the "job-state-reason" attribute. The user enters the same password at the device to release the job for printing. The Printer uses the same encryption method specified in the "job-password-encryption" attribute on this password. The printer MUST resume the print job when the locally-supplied encrypted password matches the value of the "job-password" attribute. The method in which the password is entered and validated at the Printer is implementation dependent. The "job-password" attribute value MUST NOT be returned in a Get-Job-Attributes response. If a "job-password" attribute value other than a zero-length string is provided in a Job Creation operation, the job is placed into the 'pending-held' state, and the 'job-password-wait' value is added to the "job-state-reason" attribute. Other jobs may be printed before the release of the Secure Print Job from the 'pending-held' state. If the Secure Print Job is released by the user while another job is printing, the Secure Job MUST NOT resume printing until the current job is done printing. The Secure Job SHOULD be the next job printed after the current job, unless there is another job in the Printer which has a higher priority than the Secure Job as determined by the "job-priority" attribute. 7.4 job-delay-output-until (type3 keyword | name(MAX)) . A Flow Diagram for Job Creation with the "job-delay-output-until" attribute is shown in Figure 1 below. The semantics of the "job-delay-output-until" attribute are similar to the "job-hold-until" Job Template attribute [RFC2911] (see Table 5 below), except that for the "job-delay-output-until" attribute the job is not put into the 'pending-held' state while waiting for the time period to arrive. Instead, the Printer MAY process the job normally, i.e., by putting the job into the 'pending' and 'processing' states. However, the Printer MUST NOT produce any output until the specified time period arrives. If the Printer completes the processing and the specified time period has not yet arrived, the Printer MUST suspend the processing of the job by putting the job in the 'processing-stopped' state, MUST add the 'job-delay-output-until-suspended' value to the job's "job-state-reasons" attribute, and MUST NOT delay processing or output of any other jobs while waiting for the specified time period to arrive. When the time period does arrive, the Printer MUST remove the 'job-delay-output-until-specified' and 'job-delay-output-until-suspended' values from the "job-state-reasons" attribute and MAY add the 'job-queued' [RFC2911] value to the job's "job-state-reasons" attribute. Then the job can be scheduled and processed, i.e., the job enters the 'processing' state and produces the output. 7.8.1.2.3.2 save-name (name(MAX)) The "save-name" member attribute specifies the name of the saved job in the directory specified by the "save-location" member attribute. The client can supply a "save-name" attribute value that is either a simple file name or a relative path where each component of the path is separated by a FORWARD SLASH ("/") character. The "save-name-subdirectory-supported" Printer Description attribute indicates whether or not the Printer supports a FORWARD-SLASH ("/") in the "save-name" value. Whether the FORWARD SLASH when supported is actually implemented as a sub-directory is IMPLEMENTATION DEPENDENT. 7.10.1.2 pdl-init-file-name (name(MAX)) This member attribute specifies the name of the initialization file within the directory specified by the "save-namepdl-init-file-location" member attribute that the Printer MUST send to its PDL interpreter prior to processing the document. The "pdl-init-file-subdirectory-supported" Printer Description attribute indicates whether or not the Printer supports a FORWARD-SLASH ("/") in the "save-name" value. Whether the FORWARD SLASH when supported is actually implemented as a sub-directory is IMPLEMENTATION DEPENDENT. 13.2 Attribute Value Registration . job-state-reasons (type2 keyword): [pwg5100.11] job-delay-output-until-specified [pwg5100.11] job-password-wait [pwg5100.11] job-printed-successfully [pwg5100.11] job-printed-with-errors [pwg5100.11] job-printed-with-warnings [pwg5100.11] job-printed-with-errors [pwg5100.11] job-resuming [pwg5100.11] job-saved-successfully [pwg5100.11] job-saved-with-errors [pwg5100.11] job-saved-with-warnings [pwg5100.11] job-saving [pwg5100.11] job-scheduling [pwg5100.11] job-spooling [pwg5100.11] job-streaming [pwg5100.11] job-suspended-by-operator [pwg5100.11] job-suspended-by-system [pwg5100.11] job-suspended-by-user [pwg5100.11] job-suspending [pwg5100.11] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_0240_01CB45EE.F2688460 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

He= re are some PWG Last Call Comments from your JPS2 Editor that I found while writin= g up the changes that we had made over the last year to the draft.  Here th= ey are (in HTML with red underl= ined inserts and blue cross-outs):

&n= bsp;6.1  job-password  (octetString(255)) for Job Creation operations

This Operation attribute may OPTIONALLY be included in the request of the follow= ing Job Creation operations: Print-Job, Print-URI, and Create-Job.

The OPTIONAL "job-password" operation attribute allows a user to perf= orm Secure Print.  The user enters a password in the job submitting application which is encrypted by the client using one of the methods speci= fied by the "job-password-encryption-supported" attribute.  The encrypted password is sent to the Printer as the value of the "job-password" attribute.  If a "job-password" val= ue is provided, other than a zero-length string, the printer MUST hold the job in the 'pending-held' state, and the 'job-password-wait' value is added to the "job-state-reason" attribute.

The user enters the same password at the device to release the job for printing.  The Printer uses the same encryption method specified in the "job-password-encryption" attribute on this password. The printer MUST resume the print job when the locally-supplied encrypted password matc= hes the value of the "job-password" attribute.  The method in wh= ich the password is entered and validated at the Printer is implementation dependent.

The "job-password" attribute value MUST NOT be returned in a Get-Job-Attributes response.

If a "job-password" attribute value other than a zero-length string is provided in a Job Creation operation, the job is placed into the 'pending-held' state, and the 'job-password-wait' va= lue is added to the "job-state-reason" attribute.

Other jobs may be printed before the release of the Secure Print Job from the 'pending-held' state. If the Secure Print Job is released by the user while another job is printing, the Secure Job MUST NOT resume printing until the current job is done printing.  The Secure Job SHOULD be the next job printed after the current job, unless there is another job in the Printer w= hich has a higher priority than the Secure Job as determined by the "job-priority" attribute.

&n= bsp;

&n= bsp;

7.4  job-delay-output-until (type3 k= eyword | name(MAX))

&n= bsp;

&#= 8230;

&n= bsp;

A Flow Diagram for Job Creation with the "job-delay-output-until" attrib= ute is shown in Figure 1 below.  The semantics of the "job-delay-output-until" attribute are similar to the "job-hold-until" Job Template attribute [RFC2911] (see Table 5 below), except that for the "job-delay-output-until" attribute the job is not put into the 'pending-held' state while waiting for the time per= iod to arrive.  Instead, the Printer MAY process the job normally, i.e., by putting the job into the 'pending' and 'processing' states.  However, = the Printer MUST NOT produce any output until the specified time period arrives.  If the Printer completes the processing and the specified ti= me period has not yet arrived, the Printer MUST suspend the processing of the job by = putting the job in the 'processing-stopped' state, MUST add the 'job-delay-output-until-suspended' value to the job's "job-state-reasons" attribute, and MUST NOT del= ay processing or output of any other jobs while waiting for the specified time period to arrive.  When the time period does arrive, the Printer MUST remove the 'job-delay-output-until-specified' and 'job-delay-output-until-suspended' <= /s>values from the “job-state-reasons” attribute and MAY add the 'job-queued' [RFC2911] value to the jo= b's "job-state-reasons" attribute.  Then the j= ob can be scheduled and processed, i.e., the job enters the 'processing' state= and produces the output.

&n= bsp;

&n= bsp;

7.8.1.2.3.2  save= -name (name(MAX))

The “save-name” member attribute specifies the name of the saved jo= b in the directory specified by the “save-location” member attribute.  The client can supply a “save-name” attribute value that is either a simple file name or a relative path where each compo= nent of the path is separated by a FORWARD SLASH (“/”) character.   The “save-name-subdirectory-supported” <= u>Printer Description attribute indicates whether or not the Printer supports a FORWARD-SLASH (“/R= 21;) in the “save-name” value.  Whether the FORWARD SLASH when supported is actually implemented as a sub-directory is IMPLEMENTATION DEPENDENT.

&n= bsp;

&n= bsp;

7.= 10.1.2  pdl-init-file-name (name(MAX))<= o:p>

This member attribute specifies the name of the initialization file within the directory specified by the "save-namepdl-init-file-location<= /u>" member attribute that the Printer MUST send to its PDL interpreter prior to processing the document.   The “pdl-init-file-subdirectory-supported” Printer Description attribute indicat= es whether or not the Printer supports a FORWARD-SLASH (“/”) in the “save-name” value.  Whether the FORWARD SLASH when support= ed is actually implemented as a sub-directory is IMPLEMENTATION DEPENDENT.

&n= bsp;

13.2 Att= ribute Value Registration

…<= o:p>

job-state-reasons (typ= e2 keyword):                        &nb= sp;   [pwg5100.11]

  job-delay-outpu= t-until-specified         &nbs= p;            &= nbsp;     [pwg5100.11]

  job-password-wait         &nbs= p;            &= nbsp;           &nbs= p;        [pwg5100.11]

  job-printed-successfully        &nb= sp;            =             &nb= sp;  [pwg5100.11]

  job-printed-with-errors     &nbs= p;            &= nbsp;           &nbs= p;      [pwg5100.11]

  job-printed-with-warnings        &n= bsp;            = ;            &n= bsp; [pwg5100.11]

  job-printed-with-errors        &nbs= p;            &= nbsp;           &nbs= p;   [pwg5100.11]

  job-resuming          &nb= sp;                    &nb= sp;            =     [pwg5100.11]

  job-saved-successfully         = ;            &n= bsp;            = ;    [pwg5100.11]

  job-saved-with-errors         =             &nb= sp;            =      [pwg5100.11]

  job-saved-with-warnings        &nbs= p;            &= nbsp;           &nbs= p;   [pwg5100.11]

  job-saving             &nb= sp;            =             &nb= sp;           [pwg51= 00.11]

  job-scheduling       &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p; [pwg5100.11]

  job-spooling          &nb= sp;            =             &nb= sp;            [pwg5100.11]

  job-streaming           &= nbsp;           &nbs= p;            &= nbsp;          [pwg5100.1= 1]

  job-suspended-by-operator        &n= bsp;            = ;            &n= bsp; [pwg5100.11]

  job-suspended-by-system        &nbs= p;            &= nbsp;           &nbs= p;   [pwg5100.11]

  job-suspended-by-user         =             &nb= sp;                 [pwg5100.= 11]

  job-suspending          &= nbsp;           &nbs= p;            &= nbsp;          [pwg5100.11]

&n= bsp;

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0240_01CB45EE.F2688460-- --===============1700842700== 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 --===============1700842700==-- From ipp-bounces@pwg.org Sat Aug 28 15:48:58 2010 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 772103A683E for ; Sat, 28 Aug 2010 15:48:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.257 X-Spam-Level: X-Spam-Status: No, score=0.257 tagged_above=-999 required=5 tests=[AWL=0.255, 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 C+78uTGnP-Qm for ; Sat, 28 Aug 2010 15:48:57 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 207373A681F for ; Sat, 28 Aug 2010 15:48:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D727F7933F; Sat, 28 Aug 2010 18:49:23 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from wbmler1.mail.xerox.com (wbmler1.mail.xerox.com [13.13.138.216]) by pwg.org (Postfix) with ESMTP id 1344D7933A for ; Sat, 28 Aug 2010 18:49:15 -0400 (EDT) Received: from wbmlir1.mail.xerox.com (wbmlir1.mail.xerox.com [13.131.8.221]) by wbmler1.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7SMnFSb019718 for ; Sat, 28 Aug 2010 18:49:15 -0400 Received: from wbmlir1.mail.xerox.com (localhost [127.0.0.1]) by wbmlir1.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7SMnEp0024502 for ; Sat, 28 Aug 2010 18:49:14 -0400 Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15]) by wbmlir1.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7SMnEvU024497 for ; Sat, 28 Aug 2010 18:49:14 -0400 X-XeroxINT-Source-Ip: 13.135.210.15 X-XeroxINT-Source-Name: usa0300gw002.na.xerox.net X-XeroxINT-Reported-Name: USA0300GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Sat, 28 Aug 2010 18:49:14 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sat, 28 Aug 2010 15:49:09 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Xerox has reviewed IPP JPS2 and has no comments Thread-Index: ActEQ7mTCzdOcX/vQBa38rPQuYzyHA== From: "Zehler, Peter" To: X-OriginalArrivalTime: 28 Aug 2010 22:49:14.0700 (UTC) FILETIME=[3D2CA0C0:01CB4703] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Xerox has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0146265309==" 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: D727F7933F.A9026 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0146265309== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4703.3C73D0F4" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4703.3C73D0F4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CB4703.3C73D0F4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

 =

Peter Zehler

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

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CB4703.3C73D0F4-- --===============0146265309== 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 --===============0146265309==-- From ipp-bounces@pwg.org Mon Aug 30 05:34:54 2010 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 56F2A3A6818 for ; Mon, 30 Aug 2010 05:34:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.066 X-Spam-Level: X-Spam-Status: No, score=-1.066 tagged_above=-999 required=5 tests=[AWL=1.533, BAYES_00=-2.599] 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 uuQDqWcithKA for ; Mon, 30 Aug 2010 05:34:47 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 19F893A680A for ; Mon, 30 Aug 2010 05:34:46 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id B3C3B79363; Mon, 30 Aug 2010 08:35:13 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from wbmler2.mail.xerox.com (wbmler2.mail.xerox.com [13.13.138.217]) by pwg.org (Postfix) with ESMTP id 3243779362 for ; Mon, 30 Aug 2010 08:35:10 -0400 (EDT) Received: from wbmlir1.mail.xerox.com (wbmlir1.mail.xerox.com [13.131.8.221]) by wbmler2.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7UCZ6hw030687; Mon, 30 Aug 2010 08:35:06 -0400 Received: from wbmlir1.mail.xerox.com (localhost [127.0.0.1]) by wbmlir1.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7UCZ27W006712; Mon, 30 Aug 2010 08:35:02 -0400 Received: from USA7061GW002.na.xerox.net (usa7061gw002.na.xerox.net [13.151.210.15]) by wbmlir1.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7UCYth3006372; Mon, 30 Aug 2010 08:35:02 -0400 X-XeroxINT-Source-Ip: 13.151.210.15 X-XeroxINT-Source-Name: usa7061gw002.na.xerox.net X-XeroxINT-Reported-Name: USA7061GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Aug 2010 05:35:00 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) Date: Mon, 30 Aug 2010 05:35:27 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) Thread-Index: ActEhuZzDVyvPrrKS2qdiixQAmrESQDt+znw References: From: "Zehler, Peter" To: "Ira McDonald" , , "Michael R Sweet" X-OriginalArrivalTime: 30 Aug 2010 12:35:00.0419 (UTC) FILETIME=[C3232130:01CB483F] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: B3C3B79363.A7F14 X-pwg-MailScanner-From: ipp-bounces@pwg.org Is it legal for two or more printer-uri-supported to differ only in the URI scheme? Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Ira McDonald Sent: Wednesday, August 25, 2010 2:53 PM To: ipp@pwg.org; Michael R Sweet; Ira McDonald Subject: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) Hi, I've just posted an Initial draft of IPPS URI Scheme: =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100 825.txt - plaintext Internet-Draft format (w/ explicit formfeeds) =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100 825.htm - HTML w/ live table of contents Hint: You can view and print the plaintext file easily with MS WordPad. We agreed to do an IPP WG review first before submitting this document to the IETF Internet-Drafts Editor. This document was created by rewriting IPP URI Scheme [RFC3510]. Comments? Cheers, - Ira (IPPS URI Scheme co-editor) ----------------------------------------------------- Change Log 25 August 2010 - draft-mcdonald-ipps-uri-scheme-00.txt - Editorial - complete rewrite of RFC 3510 for new transport binding - Technical - added section 3.2 IPP over HTTP Transport Binding - Technical - added section 3.3 IPP over HTTPS Transport Binding - Editorial - updated Appendix A w/ registration template from RFC 4395 --=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 --=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 Aug 30 08:20:46 2010 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 E10BE3A6842 for ; Mon, 30 Aug 2010 08:20:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.193 X-Spam-Level: X-Spam-Status: No, score=-2.193 tagged_above=-999 required=5 tests=[AWL=0.405, 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 K9pvAacyRa5k for ; Mon, 30 Aug 2010 08:20:45 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 4E8D93A689F for ; Mon, 30 Aug 2010 08:20:44 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 000C67937A; Mon, 30 Aug 2010 11:21:06 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-ew0-f46.google.com (mail-ew0-f46.google.com [209.85.215.46]) by pwg.org (Postfix) with ESMTP id C15C57936D for ; Mon, 30 Aug 2010 11:20:58 -0400 (EDT) Received: by ewy23 with SMTP id 23so3409242ewy.5 for ; Mon, 30 Aug 2010 08:20:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=qKrU3p+8nrZyhOua4g88slHZfz3g4CVM1TpOKhHL9ck=; b=lKyO4gIZ1Zv4kxNccnkkfkoZ+fEbPmx4wH69NisVfoGX3Z4l5L7TPY/AX9IZmfrfO2 KOXGQKs1ebjabFufMnjWV3ct3fkUe5za6pnyWAvjhs2nF2KjtWUQDAh4Xpa13cE73t0b rOiivDpdnLmnlVOB5BqkFvLRND+6hIInkhLIQ= 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=E/D0weoGNHZioeHzJ+lYe9GuYDx/81wtYr2+yL2nbZtplxxHqK9lBW4pm2SREPY4aP Xwd4rqDu30IceIZa+6p5yT552bURa4y4vDvNqMNZQLWOiX8w6EJCZ4wVDrxaMNRfu7MY +OJr7bdKm18X4J4cLmmAT5Ph0SCqgaXkqZxm8= MIME-Version: 1.0 Received: by 10.239.191.129 with SMTP id b1mr266224hbi.75.1283181657545; Mon, 30 Aug 2010 08:20:57 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 30 Aug 2010 08:20:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Aug 2010 11:20:56 -0400 Message-ID: Subject: Re: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) From: Ira McDonald To: "Zehler, Peter" , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0582275563==" 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: 000C67937A.AA703 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0582275563== Content-Type: multipart/alternative; boundary=00163649a1a3e17049048f0c0276 --00163649a1a3e17049048f0c0276 Content-Type: text/plain; charset=ISO-8859-1 Hi Pete, Given RFC 2911 and RFC 3510 examples, I'd say that 2 or more printer-uri-supported values can legally differ only by the URI scheme - I've seen printers that list both "http:" (for IPP/1.0 compatibility) and "ipp:" (for IPP/1.1) to the same target. I think it's *unwise*. But I don't think we can actually prohibit using both "ipp:" (unsecured) and "ipps:" (TLS always) for the same IPP Printer. I do think we should RECOMMEND against the practice, because it supplies ambiguous security to the IPP Printer object. I've urged all of my printer vendor clients to NOT allow both unauthenticated (guest) and authenticated (with at least HTTP Basic/Digest) access to the same instance of IPP Printer object, because denial-of-service attacks become much easier in this case. All - your opinions? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Aug 30, 2010 at 8:35 AM, Zehler, Peter wrote: > Is it legal for two or more printer-uri-supported to differ only in the > URI scheme? > > > 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 > > > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Ira > McDonald > Sent: Wednesday, August 25, 2010 2:53 PM > To: ipp@pwg.org; Michael R Sweet; Ira McDonald > Subject: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) > > Hi, > > I've just posted an Initial draft of IPPS URI Scheme: > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100 > 825.txt > - plaintext Internet-Draft format (w/ explicit formfeeds) > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ipps-uri-scheme-00-20100 > 825.htm > - HTML w/ live table of contents > > Hint: You can view and print the plaintext file easily with > MS WordPad. > > We agreed to do an IPP WG review first before submitting > this document to the IETF Internet-Drafts Editor. > > This document was created by rewriting IPP URI Scheme > [RFC3510]. > > Comments? > > Cheers, > - Ira (IPPS URI Scheme co-editor) > > ----------------------------------------------------- > Change Log > > 25 August 2010 - draft-mcdonald-ipps-uri-scheme-00.txt > - Editorial - complete rewrite of RFC 3510 for new transport binding > - Technical - added section 3.2 IPP over HTTP Transport Binding > - Technical - added section 3.3 IPP over HTTPS Transport Binding > - Editorial - updated Appendix A w/ registration template from RFC 4395 > > -- > 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. --00163649a1a3e17049048f0c0276 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pete,

Given RFC 2911 and RFC 3510 examples, I'd say that
2= or more printer-uri-supported values can legally differ
only by the UR= I scheme - I've seen printers that list both
"http:" (for = IPP/1.0 compatibility) and "ipp:" (for IPP/1.1)
to the same target.

I think it's *unwise*.

But I don'= t think we can actually prohibit using both "ipp:"
(unsecured)= and "ipps:" (TLS always) for the same IPP
Printer.

I do think we should RECOMMEND against the practice,
because it supplies= ambiguous security to the IPP Printer
object.

I've urged all= of my printer vendor clients to NOT allow
both unauthenticated (guest) = and authenticated (with at
least HTTP Basic/Digest) access to the same instance
of IPP Printer obj= ect, because denial-of-service attacks
become much easier in this case.<= br>
All - your opinions?

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Op= en Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IP= P & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofm= usic
http://sites.google.c= om/site/highnorthinc
mailto:blueroofmusic@gmail.com
winter:
=A0 579 Park Place=A0 Saline, = MI=A0 48176
=A0 734-944-0094
summer:
=A0 PO Box 221=A0 Grand Marais, MI 49839
= =A0 906-494-2434


On Mon, Aug 30, 2010 at 8:35 AM, Zehler,= Peter <Pete= r.Zehler@xerox.com> wrote:
Is it legal for two or more printer-uri-supported to differ only in the
URI scheme?


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


-----Original Message-----
From: ipp-bounces@pwg.org [mailt= o:ipp-bounces@pwg.org] On Behalf= Of Ira
McDonald
Sent: Wednesday, August 25, 2010 2:53 PM
To: ipp@pwg.org; Michael R Sweet; Ira Mc= Donald
Subject: [IPP] Initial draft of IPPS URI Scheme (25 August 2010)

Hi,

I've just posted an Initial draft of IPPS URI Scheme:


ftp://ftp.pwg.org/pub/pwg/ipp/wd/draf= t-mcdonald-ipps-uri-scheme-00-20100
825.txt

=A0- plaintext Internet-Draft format (w/ explicit formfeeds)


ftp://ftp.pwg.org/pub/pwg/ipp/wd/draf= t-mcdonald-ipps-uri-scheme-00-20100
825.htm

=A0- HTML w/ live table of contents

Hint: =A0You can view and print the plaintext file easily with
MS WordPad.

We agreed to do an IPP WG review first before submitting
this document to the IETF Internet-Drafts Editor.

This document was created by rewriting IPP URI Scheme
[RFC3510].

Comments?

Cheers,
- Ira (IPPS URI Scheme co-editor)

-----------------------------------------------------
Change Log

25 August 2010 - draft-mcdonald-ipps-uri-scheme-00.txt
- Editorial - complete rewrite of RFC 3510 for new transport binding
- Technical - added section 3.2 IPP over HTTP Transport Binding
- Technical - added section 3.3 IPP over HTTPS Transport Binding
- Editorial - updated Appendix A w/ registration template from RFC 4395

--
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. --00163649a1a3e17049048f0c0276-- --===============0582275563== 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 --===============0582275563==-- From pwg-announce-bounces@pwg.org Mon Aug 30 08:50:27 2010 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 703F73A687A for ; Mon, 30 Aug 2010 08:50:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.013 X-Spam-Level: X-Spam-Status: No, score=0.013 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_40=-0.185] 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 Pl15UJrZI--1 for ; Mon, 30 Aug 2010 08:49:57 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 8EE903A67F2 for ; Mon, 30 Aug 2010 08:49:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D611579399; Mon, 30 Aug 2010 11:50:17 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from wvmler5.mail.xerox.com (wvmler5.mail.xerox.com [13.8.138.230]) by pwg.org (Postfix) with ESMTP id 0358479395 for ; Mon, 30 Aug 2010 11:50:08 -0400 (EDT) Received: from wvmlir2.mail.xerox.com (wvmlir2.mail.xerox.com [13.147.8.222]) by wvmler5.mail.xerox.com (8.14.4/8.13.8) with ESMTP id o7UFo7CF008911 for ; Mon, 30 Aug 2010 08:50:08 -0700 Received: from wvmlir2.mail.xerox.com (localhost [127.0.0.1]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7UFnvZp004990 for ; Mon, 30 Aug 2010 08:49:57 -0700 Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15]) by wvmlir2.mail.xerox.com (8.14.4/8.13.6) with ESMTP id o7UFng1s004570 for ; Mon, 30 Aug 2010 08:49:57 -0700 X-XeroxINT-Source-Ip: 13.135.210.15 X-XeroxINT-Source-Name: usa0300gw002.na.xerox.net X-XeroxINT-Reported-Name: USA0300GW002.na.xerox.net Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Aug 2010 11:49:54 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Aug 2010 08:50:20 -0700 Message-ID: In-Reply-To: <6B909B31-862B-4B63-8D14-32A7134157C1@apple.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PWG MFD Requirements Formal Vote Ends tomorrow (8/31/10), Please register your vote TODAY Thread-Index: Acs4Bf+lWLNetWVCSvea+1r9sZl3XgQVD6YQ References: <6B909B31-862B-4B63-8D14-32A7134157C1@apple.com> From: "Zehler, Peter" To: X-OriginalArrivalTime: 30 Aug 2010 15:49:54.0179 (UTC) FILETIME=[FD294D30:01CB485A] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote Ends tomorrow (8/31/10), Please register your vote TODAY 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: D611579399.ACC87 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org All, We need to reach a quorum AND the necessary ratio of "YES" votes. Pete Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 -----Original Message----- From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, August 09, 2010 5:00 PM To: pwg-announce@pwg.org Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August 2010) Greetings: This email initiates the Formal Approval vote by the PWG membership on the PWG MFD Requirements, which is located at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.pdf=20 The complete list of PWG Last Call issues and resolutions is located at: =20 ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-resolution-2 0100722.txt=20 The voting period will open today on Monday 9 August 2010 and will close at 10pm (US Pacific Time) on Tuesday 31 August 2010. Valid votes are: Yes, No, No (with Strong Objection), Abstain. Representatives from PWG member companies are strongly encouraged to exercise their right to vote. PWG Privacy Policy: Your vote is confidential and will not be disclosed by PWG officers or document editors. To vote, send an email with *exactly* the following subject line format: MFD Requirements Formal Vote--- Example: MFD Requirements Formal Vote-Acme-McGee-Yes Any "No" vote MUST state the reason for the "No" vote and MUST contain a description of the *technical* changes required to turn the "No" vote into a "Yes" vote - otherwise such a "No" vote will NOT be counted. Any "No" vote MUST NOT contain *editorial* comments, per the PWG Process/3.0. Any "Yes" vote MAY contain "editorial" comments but MUST NOT contain any *technical* comments, per the PWG Process/3.0. Please send your vote to all of the following email addresses (replacing "dot" with '.' and "at" with '@'): msweet"at"apple"dot"com (PWG Chair) ptykodi"at"tykodi"dot"com (PWG Secretary)=20 Peter"dot"Zehler"at"xerox"dot"com (MFD WG Chair) wamwagner"at"comcast"dot"net (MFD Requirements Editor) Please do NOT simply reply to this note on PWG-Announce (to preserve the confidentiality of your vote). Note: (1) This Formal Vote is being conducted under the rules of the PWG Process/3.0 and the current PWG Policy on Intellectual Property and Confidentiality agreement. The 2010 PWG Membership Agreement calls out both of these documents and the links are provided below. (2) To be eligible to vote the member MUST have submitted a signed copy of the 2010 PWG Membership Agreement and paid their dues. The PWG Definition of the Standards Development Process Version 3.0 is located at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf The PWG Policy on Intellectual Property and Confidentiality is located at: http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf Regards, Michael Sweet (PWG Chair) --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From pwg-announce-bounces@pwg.org Mon Aug 30 09:25:05 2010 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 8A1AB3A67F7 for ; Mon, 30 Aug 2010 09:25:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.299 X-Spam-Level: X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 QIrU6VsMFRya for ; Mon, 30 Aug 2010 09:24:56 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 3A6893A67F6 for ; Mon, 30 Aug 2010 09:24:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2BE25793A1; Mon, 30 Aug 2010 12:24:56 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by pwg.org (Postfix) with ESMTP id 34F9A793A1 for ; Mon, 30 Aug 2010 12:20:30 -0400 (EDT) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta02.westchester.pa.mail.comcast.net with comcast id 0bR71f0031HzFnQ52gLX2k; Mon, 30 Aug 2010 16:20:31 +0000 Received: from VistaBusiness ([24.61.240.234]) by omta14.westchester.pa.mail.comcast.net with comcast id 0gLX1f002548CT43agLXsH; Mon, 30 Aug 2010 16:20:31 +0000 From: "William Wagner" To: "'Zehler, Peter'" , References: <6B909B31-862B-4B63-8D14-32A7134157C1@apple.com> In-Reply-To: Subject: RE: [Pwg-Announce] PWG MFD Requirements Formal Vote Ends tomorrow (8/31/10), Please register your vote TODAY Date: Mon, 30 Aug 2010 12:20:24 -0400 Message-ID: <000801cb485f$40441dd0$c0cc5970$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acs4Bf+lWLNetWVCSvea+1r9sZl3XgQVD6YQAAEv+2A= Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: 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: 2BE25793A1.ACD66 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org Please respond, even if to abstain if you do not have company approval. Thanks, Bill Wagner -----Original Message----- From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Zehler, Peter Sent: Monday, August 30, 2010 11:50 AM To: pwg-announce@pwg.org Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote Ends tomorrow (8/31/10), Please register your vote TODAY All, We need to reach a quorum AND the necessary ratio of "YES" votes. Pete Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -----Original Message----- From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, August 09, 2010 5:00 PM To: pwg-announce@pwg.org Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August 2010) Greetings: This email initiates the Formal Approval vote by the PWG membership on the PWG MFD Requirements, which is located at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.pdf The complete list of PWG Last Call issues and resolutions is located at: ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-resolution-2 0100722.txt The voting period will open today on Monday 9 August 2010 and will close at 10pm (US Pacific Time) on Tuesday 31 August 2010. Valid votes are: Yes, No, No (with Strong Objection), Abstain. Representatives from PWG member companies are strongly encouraged to exercise their right to vote. PWG Privacy Policy: Your vote is confidential and will not be disclosed by PWG officers or document editors. To vote, send an email with *exactly* the following subject line format: MFD Requirements Formal Vote--- Example: MFD Requirements Formal Vote-Acme-McGee-Yes Any "No" vote MUST state the reason for the "No" vote and MUST contain a description of the *technical* changes required to turn the "No" vote into a "Yes" vote - otherwise such a "No" vote will NOT be counted. Any "No" vote MUST NOT contain *editorial* comments, per the PWG Process/3.0. Any "Yes" vote MAY contain "editorial" comments but MUST NOT contain any *technical* comments, per the PWG Process/3.0. Please send your vote to all of the following email addresses (replacing "dot" with '.' and "at" with '@'): msweet"at"apple"dot"com (PWG Chair) ptykodi"at"tykodi"dot"com (PWG Secretary) Peter"dot"Zehler"at"xerox"dot"com (MFD WG Chair) wamwagner"at"comcast"dot"net (MFD Requirements Editor) Please do NOT simply reply to this note on PWG-Announce (to preserve the confidentiality of your vote). Note: (1) This Formal Vote is being conducted under the rules of the PWG Process/3.0 and the current PWG Policy on Intellectual Property and Confidentiality agreement. The 2010 PWG Membership Agreement calls out both of these documents and the links are provided below. (2) To be eligible to vote the member MUST have submitted a signed copy of the 2010 PWG Membership Agreement and paid their dues. The PWG Definition of the Standards Development Process Version 3.0 is located at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf The PWG Policy on Intellectual Property and Confidentiality is located at: http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf Regards, Michael Sweet (PWG Chair) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ 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. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From pwg-announce-bounces@pwg.org Mon Aug 30 14:18:38 2010 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 D98E63A6855 for ; Mon, 30 Aug 2010 14:18:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.209 X-Spam-Level: X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=0.389, 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 CJHcIxj9tsvS for ; Mon, 30 Aug 2010 14:18:36 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 307043A687D for ; Mon, 30 Aug 2010 14:18:36 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 365A5793A7; Mon, 30 Aug 2010 17:19:00 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com [209.85.213.174]) by pwg.org (Postfix) with ESMTP id AC292793A0 for ; Mon, 30 Aug 2010 17:18:55 -0400 (EDT) Received: by yxp4 with SMTP id 4so499242yxp.5 for ; Mon, 30 Aug 2010 14:18:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=wuYs/AX5/mLDYaU6SYYrFq7d1zfTGCGg9P7DXiB09Pw=; b=B3SIpRZnFsnVmxUX0Tdi/heZd6uo5x3lvMRVW3wMXtyJf8lqFGNB0MeMYKkVYsb+lN ohq1vZWiE4fMCPzR+Ayx6MOYNqIVJlcWqmG6xrT9Q6hLZxyrn/MhF38z0/P1OKK3Sh9X VkEhYTTxFKfVe8Qpbz45BzoCJzAKcFZeoNpBQ= 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=PYM+GCdhzn77/ftStS2PfgcErMCaJX8qc4DL85+KiDKdNKnby1YYKex6szXTpkpRoW U6G1UyWc1MhFHMgRtDfNYkHx4DDeKJSvbud2WMayXL/UjF1JN7mXjJTHS3u+7oE0XBoz dfKtp2ExTG3fp/xMdsRI8SKuUnS/dqa3+ES0w= MIME-Version: 1.0 Received: by 10.220.60.204 with SMTP id q12mr3054297vch.185.1283203134789; Mon, 30 Aug 2010 14:18:54 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 30 Aug 2010 14:18:54 -0700 (PDT) In-Reply-To: <000801cb485f$40441dd0$c0cc5970$@net> References: <6B909B31-862B-4B63-8D14-32A7134157C1@apple.com> <000801cb485f$40441dd0$c0cc5970$@net> Date: Mon, 30 Aug 2010 17:18:54 -0400 Message-ID: Subject: Re: [Pwg-Announce] PWG MFD Requirements Formal Vote Ends tomorrow (8/31/10), Please register your vote TODAY From: Ira McDonald To: William Wagner , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org, "Zehler, Peter" 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="===============1979485374==" 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: 365A5793A7.AC76A X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1979485374== Content-Type: multipart/alternative; boundary=e0cb4e887865061a13048f110336 --e0cb4e887865061a13048f110336 Content-Type: text/plain; charset=ISO-8859-1 Hi, Note that an Abstain *counts* towards quorum. Cheers, - Ira On Mon, Aug 30, 2010 at 12:20 PM, William Wagner wrote: > Please respond, even if to abstain if you do not have company approval. > > Thanks, Bill Wagner > > -----Original Message----- > From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] > On > Behalf Of Zehler, Peter > Sent: Monday, August 30, 2010 11:50 AM > To: pwg-announce@pwg.org > Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote Ends tomorrow > (8/31/10), Please register your vote TODAY > > All, > We need to reach a quorum AND the necessary ratio of "YES" votes. > Pete > > Peter Zehler > > Xerox Research Center Webster > Email: Peter.Zehler@Xerox.com > Voice: (585) 265-8755 > FAX: (585) 265-7441 > US Mail: Peter Zehler > Xerox Corp. > 800 Phillips Rd. > M/S 128-25E > Webster NY, 14580-9701 > > > -----Original Message----- > From: pwg-announce-bounces@pwg.org [mailto:pwg-announce-bounces@pwg.org] > On Behalf Of Michael Sweet > Sent: Monday, August 09, 2010 5:00 PM > To: pwg-announce@pwg.org > Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August > 2010) > > Greetings: > > This email initiates the Formal Approval vote by the PWG membership on > the PWG MFD Requirements, which is located at: > > ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.pdf > > The complete list of PWG Last Call issues and resolutions is located at: > > > ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-resolution-2 > 0100722.txt > > The voting period will open today on Monday 9 August 2010 and will close > at 10pm (US Pacific Time) on Tuesday 31 August 2010. > > Valid votes are: Yes, No, No (with Strong Objection), Abstain. > > Representatives from PWG member companies are strongly encouraged to > exercise their right to vote. > > PWG Privacy Policy: Your vote is confidential and will not be disclosed > by PWG officers or document editors. > > To vote, send an email with *exactly* the following subject line format: > > MFD Requirements Formal Vote-- name>- > > Example: MFD Requirements Formal Vote-Acme-McGee-Yes > > Any "No" vote MUST state the reason for the "No" vote and MUST contain a > description of the *technical* changes required to turn the "No" vote > into a "Yes" vote - otherwise such a "No" vote will NOT be counted. Any > "No" vote MUST NOT contain *editorial* comments, per the PWG > Process/3.0. > > Any "Yes" vote MAY contain "editorial" comments but MUST NOT contain any > *technical* comments, per the PWG Process/3.0. > > Please send your vote to all of the following email addresses (replacing > "dot" with '.' and "at" with '@'): > > msweet"at"apple"dot"com (PWG Chair) > > ptykodi"at"tykodi"dot"com (PWG Secretary) > > Peter"dot"Zehler"at"xerox"dot"com (MFD WG Chair) > > wamwagner"at"comcast"dot"net (MFD Requirements Editor) > > Please do NOT simply reply to this note on PWG-Announce (to preserve the > confidentiality of your vote). > > Note: > (1) This Formal Vote is being conducted under the rules of the PWG > Process/3.0 and the current PWG Policy on Intellectual Property and > Confidentiality agreement. The 2010 PWG Membership Agreement calls out > both of these documents and the links are provided below. > > (2) To be eligible to vote the member MUST have submitted a signed copy > of the 2010 PWG Membership Agreement and paid their dues. > > The PWG Definition of the Standards Development Process Version 3.0 is > located at: > > http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > The PWG Policy on Intellectual Property and Confidentiality is located > at: > > http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf > > Regards, > Michael Sweet (PWG Chair) > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > 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. > > _______________________________________________ > 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. --e0cb4e887865061a13048f110336 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Note that an Abstain *counts* towards quorum.

Cheers,
= - Ira


On Mon, Aug 30, 2010 at 12:20 P= M, William Wagner <wamwagner@comcast.net> wrote:
Please respond, e= ven if to abstain if you do not have company approval.

Thanks, Bill Wagner

-----Original Message-----
From: pwg-announce-bounces@= pwg.org [mailto:pwg-ann= ounce-bounces@pwg.org] On
Behalf Of Zehler, Peter
Sent: Monday, August 30, 2010 11:50 AM
To: pwg-announce@pwg.org
Subject: [Pwg-Announce] PWG MFD Req= uirements Formal Vote Ends tomorrow
(8/31/10), Please register your vote TODAY

All,
We need to reach a quorum AND the necessary ratio of "YES" votes.=
Pete

Peter Zehler

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


-----Original Message-----
From: pwg-announce-bounces@= pwg.org [mailto:pwg-ann= ounce-bounces@pwg.org]
On Behalf Of Michael Sweet
Sent: Monday, August 09, 2010 5:00 PM
To: pwg-announce@pwg.org
Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August
2010)

Greetings:

This email initiates the Formal Approval vote by the PWG membership on
the PWG MFD Requirements, which is located at:

=A0 =A0ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.= pdf

The complete list of PWG Last Call issues and resolutions is located at:


ftp://ftp.pwg.org/pub/pwg/mfd/wd/= mfdreq10-last-call-comment-resolution-2
0100722.txt


The voting period will open today on Monday 9 August 2010 and will close
at 10pm (US Pacific Time) on Tuesday 31 August 2010.

Valid votes are: Yes, No, No (with Strong Objection), Abstain.

Representatives from PWG member companies are strongly encouraged to
exercise their right to vote.

PWG Privacy Policy: =A0Your vote is confidential and will not be disclosed<= br> by PWG officers or document editors.

To vote, send an email with *exactly* the following subject line format:

=A0 =A0MFD Requirements Formal Vote-<company name>-<voter's l= ast
name>-<Yes/No/Abstain>

Example: MFD Requirements Formal Vote-Acme-McGee-Yes

Any "No" vote MUST state the reason for the "No" vote a= nd MUST contain a
description of the *technical* changes required to turn the "No" = vote
into a "Yes" vote - otherwise such a "No" vote will NOT= be counted. =A0Any
"No" vote MUST NOT contain *editorial* comments, per the PWG
Process/3.0.

Any "Yes" vote MAY contain "editorial" comments but MUS= T NOT contain any
*technical* comments, per the PWG Process/3.0.

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

=A0 =A0msweet"at"apple"dot"com (PWG Chair)

=A0 =A0ptykodi"at"tykodi"dot"com (PWG Secretary)

=A0 =A0Peter"dot"Zehler"at"xerox"dot"com (MF= D WG Chair)

=A0 =A0wamwagner"at"comcast"dot"net (MFD Requirements = Editor)

Please do NOT simply reply to this note on PWG-Announce (to preserve the
confidentiality of your vote).

Note:
(1) This Formal Vote is being conducted under the rules of the PWG
Process/3.0 and the current PWG Policy on Intellectual Property and
Confidentiality agreement. The 2010 PWG Membership Agreement calls out
both of these documents and the links are provided below.

(2) To be eligible to vote the member MUST have submitted a signed copy
of the 2010 PWG Membership Agreement and paid their dues.

The PWG Definition of the Standards Development Process Version 3.0 is
located at:

=A0 =A0http://www.pwg.org/chair/membership_docs/pwg-process3= 0.pdf

The PWG Policy on Intellectual Property and Confidentiality is located
at:

=A0 =A0http://www.pwg.org/chair/membership_docs/pwg-ip-polic= y.pdf

Regards,
Michael Sweet (PWG Chair)
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

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

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

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e0cb4e887865061a13048f110336-- --===============1979485374== 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 --===============1979485374==-- From ipp-bounces@pwg.org Mon Aug 30 14:33:50 2010 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 D22803A6884 for ; Mon, 30 Aug 2010 14:33:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.992 X-Spam-Level: X-Spam-Status: No, score=-101.992 tagged_above=-999 required=5 tests=[AWL=0.606, 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 fIqakd+nHSaO for ; Mon, 30 Aug 2010 14:33:49 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id EEC143A6866 for ; Mon, 30 Aug 2010 14:33:48 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 65C8E793A9; Mon, 30 Aug 2010 17:34:15 -0400 (EDT) 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 EA561793A7 for ; Mon, 30 Aug 2010 17:34:10 -0400 (EDT) Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id E6430A541506; Mon, 30 Aug 2010 14:34:09 -0700 (PDT) X-AuditID: 11807134-b7cacae0000058e0-ad-4c7c23d0d6f9 Received: from [17.151.80.96] (Unknown_Domain [17.151.80.96]) (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 2C.F9.22752.1D32C7C4; Mon, 30 Aug 2010 14:34:09 -0700 (PDT) Subject: Re: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) Mime-Version: 1.0 (Apple Message framework v1081) From: Michael Sweet In-Reply-To: Date: Mon, 30 Aug 2010 14:34:08 -0700 Message-Id: References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) 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="===============1281202040==" 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: 65C8E793A9.A859B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1281202040== Content-Type: multipart/alternative; boundary=Apple-Mail-2--45829767 --Apple-Mail-2--45829767 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Aug 30, 2010, at 8:20 AM, Ira McDonald wrote: > ... > I do think we should RECOMMEND against the practice, > because it supplies ambiguous security to the IPP Printer > object. FWIW, while it is certainly possible I think it would be better to simply r= equire that printers supporting both ipp and ipps report the appropriate ke= ywords for uri-security-supported (ssl3 and/or tls) along with mandatory su= pport for HTTP Upgrade. That would be consistent with our "message" since = IPP/1.1 and gives us what we want on the standards side of things. Whether a Printer allows clear-text connections when configured with SSL/TL= S support is, IMHO, a site-specific policy outside the scope of IPP, and in= particular HTTP Upgrade allows both the Client and Printer to enforce a pa= rticular policy dynamically. Moreover, some communications channels may al= ready be secured, making any transport-level encryption optional over those= channels. ________________________________________________________________________ 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--45829767 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On Aug 30, 2010,= at 8:20 AM, Ira McDonald wrote:
...
I do think we should RECOMMEND against the practice,
because it supplies= ambiguous security to the IPP Printer
object.

=
FWIW, while it is certainly possible I think it would be better = to simply require that printers supporting both ipp and ipps report the app= ropriate keywords for uri-security-supported (ssl3 and/or tls) along with m= andatory support for HTTP Upgrade.  That would be consistent with our = "message" since IPP/1.1 and gives us what we want on the standards side of = things.

Whether a Printer allows clear-text connec= tions when configured with SSL/TLS support is, IMHO, a site-specific policy= outside the scope of IPP, and in particular HTTP Upgrade allows both the C= lient and Printer to enforce a particular policy dynamically.  Moreove= r, some communications channels may already be secured, making any transpor= t-level encryption optional over those channels.

___________________= _____________________________________________________
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--45829767-- --===============1281202040== 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 --===============1281202040==-- From ipp-bounces@pwg.org Mon Aug 30 14:41:37 2010 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 4B3B43A6895 for ; Mon, 30 Aug 2010 14:41:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.223 X-Spam-Level: X-Spam-Status: No, score=-2.223 tagged_above=-999 required=5 tests=[AWL=0.375, 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 QjQoxxqaStma for ; Mon, 30 Aug 2010 14:41:35 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id A49C73A687B for ; Mon, 30 Aug 2010 14:41:35 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 216FA793B5; Mon, 30 Aug 2010 17:41:59 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by pwg.org (Postfix) with ESMTP id 575E17933A for ; Mon, 30 Aug 2010 17:41:55 -0400 (EDT) Received: by qyk33 with SMTP id 33so5512000qyk.5 for ; Mon, 30 Aug 2010 14:41:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Qi9YhG/P0DCZyZ6Pv8YaabSMZHRHpTFxLC2yqTSBMv4=; b=EANa+wCagHeJd0iTR8xb7hLKsBAtkFzpg9IvdT4XNhmu9OO6PxHM2MnnpKp4BROR1n pYe+RSeDclIqZ3H9lvtd0qMsWcKLPMj55EFyH1VjpJjuU+hGo2MysEzQLx/0SOf6++LA F9M2oBABPNPmRiXPkixwQiR3jEaaCqLE/25vI= 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=WHxMb/GyBANext3GR/Bn3YFht/dK50azBxNpVb6SdEW5d0d6HcUuotDHi+MtyTV+qO RmK96fGJvdjU5BTUjAA1rvlkuEi/C9UIh8+Y8da7R5gpyxhEWeKJ9JUklO57okMUi2JF Gh9Fve/zkwrGfZqfSVDfG/NunQDDzjZN24eUI= MIME-Version: 1.0 Received: by 10.220.62.5 with SMTP id v5mr3222073vch.244.1283204514351; Mon, 30 Aug 2010 14:41:54 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 30 Aug 2010 14:41:54 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Aug 2010 17:41:54 -0400 Message-ID: Subject: Re: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) 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="===============1307556543==" 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: 216FA793B5.A8FFC X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1307556543== Content-Type: multipart/alternative; boundary=e0cb4e887ee9408b13048f1155bd --e0cb4e887ee9408b13048f1155bd Content-Type: text/plain; charset=ISO-8859-1 Hi, I agree with Mike. If you support "ipps:" on an IPP Printer object and also support "ipp:", then you MUST support HTTP Upgrade. About encryption: For many printing situations (emails, service messages, etc.) it's fine to send the data in cleartext over the enterprise network, VPN, or even public Internet - but you still want Data Integrity (i.e., secure hashes of application PDUs in the TLS Record layer) - "print what you sent" - right? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Aug 30, 2010 at 5:34 PM, Michael Sweet wrote: > On Aug 30, 2010, at 8:20 AM, Ira McDonald wrote: > > ... > I do think we should RECOMMEND against the practice, > because it supplies ambiguous security to the IPP Printer > object. > > > FWIW, while it is certainly possible I think it would be better to simply > require that printers supporting both ipp and ipps report the appropriate > keywords for uri-security-supported (ssl3 and/or tls) along with mandatory > support for HTTP Upgrade. That would be consistent with our "message" since > IPP/1.1 and gives us what we want on the standards side of things. > > Whether a Printer allows clear-text connections when configured with > SSL/TLS support is, IMHO, a site-specific policy outside the scope of IPP, > and in particular HTTP Upgrade allows both the Client and Printer to enforce > a particular policy dynamically. Moreover, some communications channels may > already be secured, making any transport-level encryption optional over > those channels. > > ________________________________________________________________________ > 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. --e0cb4e887ee9408b13048f1155bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I agree with Mike.=A0 If you support "ipps:" on an IPP= Printer object
and also support "ipp:", then you MUST support= HTTP Upgrade.

About encryption:

For many printing situations= (emails, service messages, etc.) it's
fine to send the data in cleartext over the enterprise network, VPN,
or = even public Internet - but you still want Data Integrity (i.e., secure
= hashes of application PDUs in the TLS Record layer) - "print what
you sent" - right?

Cheers,
- Ira

Ira Mc= Donald (Musician / Software Architect)
Chair - Linux Foundation Open Pri= nting 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/hig= hnorthinc
mailto:blueroofmusic@gmail.com
winter:
=A0 579 Park Place=A0 Saline, MI=A0 48176
=A0 734-944-0= 094
summer:
=A0 PO Box 221=A0 Grand Marais, MI 49839
=A0 906-494-2= 434


On Mon, Aug 30, 2010 at 5:34 PM, Michael= Sweet <msweet@app= le.com> wrote:
On Aug 30, 2010, at 8:20 AM= , Ira McDonald wrote:
...
I do think we should RECOMMEND against the practice,
because it supplies= ambiguous security to the IPP Printer
object.

FWIW, while it is certainly possible I think it would be b= etter to simply require that printers supporting both ipp and ipps report t= he appropriate keywords for uri-security-supported (ssl3 and/or tls) along = with mandatory support for HTTP Upgrade. =A0That would be consistent with o= ur "message" since IPP/1.1 and gives us what we want on the stand= ards side of things.

Whether a Printer allows clear-text connections when co= nfigured with SSL/TLS support is, IMHO, a site-specific policy outside the = scope of IPP, and in particular HTTP Upgrade allows both the Client and Pri= nter to enforce a particular policy dynamically. =A0Moreover, some communic= ations channels may already be secured, making any transport-level encrypti= on optional over those channels.

______________________________________________________________________= __
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. --e0cb4e887ee9408b13048f1155bd-- --===============1307556543== 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 --===============1307556543==-- From ipp-bounces@pwg.org Mon Aug 30 16:43:34 2010 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 D84DF3A6859 for ; Mon, 30 Aug 2010 16:43:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.068 X-Spam-Level: X-Spam-Status: No, score=-102.068 tagged_above=-999 required=5 tests=[AWL=0.530, 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 XULwNxVIhD07 for ; Mon, 30 Aug 2010 16:43:33 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 12C353A6882 for ; Mon, 30 Aug 2010 16:43:33 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id ED294793B6; Mon, 30 Aug 2010 19:43:57 -0400 (EDT) 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 3EB5279382 for ; Mon, 30 Aug 2010 19:43:53 -0400 (EDT) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 7500EAC2CB93; Mon, 30 Aug 2010 16:43:52 -0700 (PDT) X-AuditID: 1180711d-b7b8eae0000035ac-94-4c7c42375597 Received: from [17.151.80.96] (Unknown_Domain [17.151.80.96]) (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 1F.45.13740.7324C7C4; Mon, 30 Aug 2010 16:43:52 -0700 (PDT) Subject: Re: [IPP] Initial draft of IPPS URI Scheme (25 August 2010) Mime-Version: 1.0 (Apple Message framework v1081) From: Michael Sweet In-Reply-To: Date: Mon, 30 Aug 2010 16:43:51 -0700 Message-Id: <4D0A6EF1-822C-4C62-A2FF-E527703A174D@apple.com> References: To: Ira McDonald X-Mailer: Apple Mail (2.1081) 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="===============1653471135==" 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: ED294793B6.A9B17 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1653471135== Content-Type: multipart/alternative; boundary=Apple-Mail-3--38046734 --Apple-Mail-3--38046734 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Aug 30, 2010, at 2:41 PM, Ira McDonald wrote: > Hi, >=20 > I agree with Mike. If you support "ipps:" on an IPP Printer object > and also support "ipp:", then you MUST support HTTP Upgrade. >=20 > About encryption: >=20 > For many printing situations (emails, service messages, etc.) it's > fine to send the data in cleartext over the enterprise network, VPN, > or even public Internet - but you still want Data Integrity (i.e., secure= =20 > hashes of application PDUs in the TLS Record layer) - "print what > you sent" - right? In general, data injection/replacement isn't a real problem - aside from pr= anks, there is little to be gained at great cost, especially when most jobs= are one-offs. The real issues for secure printing environments are privacy/disclosure of = print data and authentication and authorization of clients, servers, and se= rvices. For example, when you print something on the MFD down the hall, ar= e you actually talking to the MFD down the hall when you send the print job= ? TLS provides a way to provide both privacy and authentication/authorizat= ion, but for environments where the network is already secured something as= simple as Digest authentication with the MD5-session stuff may be sufficie= nt to prevent man-in-the-middle attacks. >=20 > Cheers, > - Ira >=20 > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing 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 > winter: > 579 Park Place Saline, MI 48176 > 734-944-0094 > summer: > PO Box 221 Grand Marais, MI 49839 > 906-494-2434 >=20 >=20 > On Mon, Aug 30, 2010 at 5:34 PM, Michael Sweet wrote: > On Aug 30, 2010, at 8:20 AM, Ira McDonald wrote: >> ... >> I do think we should RECOMMEND against the practice, >> because it supplies ambiguous security to the IPP Printer >> object. >=20 > FWIW, while it is certainly possible I think it would be better to simply= require that printers supporting both ipp and ipps report the appropriate = keywords for uri-security-supported (ssl3 and/or tls) along with mandatory = support for HTTP Upgrade. That would be consistent with our "message" sinc= e IPP/1.1 and gives us what we want on the standards side of things. >=20 > Whether a Printer allows clear-text connections when configured with SSL/= TLS support is, IMHO, a site-specific policy outside the scope of IPP, and = in particular HTTP Upgrade allows both the Client and Printer to enforce a = particular policy dynamically. Moreover, some communications channels may = already be secured, making any transport-level encryption optional over tho= se channels. >=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 >=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-3--38046734 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On Aug 30, 2010,= at 2:41 PM, Ira McDonald wrote:
Hi,

= I agree with Mike.  If you support "ipps:" on an IPP Printer objectand also support "ipp:", then you MUST support HTTP Upgrade.

About = encryption:

For many printing situations (emails, service messages, = etc.) it's
fine to send the data in cleartext over the enterprise network, VPN,
or = even public Internet - but you still want Data Integrity (i.e., secure
= hashes of application PDUs in the TLS Record layer) - "print what
you sent" - right?

In general, data inj= ection/replacement isn't a real problem - aside from pranks, there is littl= e to be gained at great cost, especially when most jobs are one-offs.
=

The real issues for secure printing environments = are privacy/disclosure of print data and authentication and authorization o= f clients, servers, and services.  For example, when you print somethi= ng on the MFD down the hall, are you actually talking to the MFD down the h= all when you send the print job?  TLS provides a way to provide both p= rivacy and authentication/authorization, but for environments where the net= work is already secured something as simple as Digest authentication with t= he MD5-session stuff may be sufficient to prevent man-in-the-middle attacks= .


Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair -= Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
IETF De= signated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/hig= hnorthinc
mailto:blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
&nbs= p; 734-944-0094
summer:
  PO Box 221  Grand Marais, MI 4983= 9
  906-494-2434


On Mon, Aug 30, 2010 at 5:34 PM, Michael= Sweet <msweet@app= le.com> wrote:
On Aug 30, 2010, at 8:20 AM= , Ira McDonald wrote:
...
I do think we should RECOMMEND against the practice,
because it supplies= ambiguous security to the IPP Printer
object.

FWIW, while it is certainly possible I think it would be b= etter to simply require that printers supporting both ipp and ipps report t= he appropriate keywords for uri-security-supported (ssl3 and/or tls) along = with mandatory support for HTTP Upgrade.  That would be consistent wit= h our "message" since IPP/1.1 and gives us what we want on the standards si= de of things.

Whether a Printer allows clear-text connections when co= nfigured with SSL/TLS support is, IMHO, a site-specific policy outside the = scope of IPP, and in particular HTTP Upgrade allows both the Client and Pri= nter to enforce a particular policy dynamically.  Moreover, some commu= nications channels may already be secured, making any transport-level encry= ption optional over those channels.

______________________________________________________________________= __
Michael Sweet, Senior Printing System Engineer, PWG Chair






___________________= _____________________________________________________
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-3--38046734-- --===============1653471135== 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 --===============1653471135==-- From ipp-bounces@pwg.org Mon Aug 30 20:35:23 2010 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 7D2B33A6860 for ; Mon, 30 Aug 2010 20:35:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.236 X-Spam-Level: X-Spam-Status: No, score=-2.236 tagged_above=-999 required=5 tests=[AWL=0.362, 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 74dIjrNX-Vgc for ; Mon, 30 Aug 2010 20:35:00 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 1366E3A659B for ; Mon, 30 Aug 2010 20:35:00 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id F1F8C793BF; Mon, 30 Aug 2010 23:35:26 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com [209.85.213.46]) by pwg.org (Postfix) with ESMTP id 39DFD793BB; Mon, 30 Aug 2010 23:35:20 -0400 (EDT) Received: by ywh1 with SMTP id 1so2119518ywh.5 for ; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=/8cktHpmq/UmsgjqCMpf/dxGQ/HQQY34FData2TQUfo=; b=cAQxbCRmGKWLZmXAe5603vccD+ebrf91mSBB/qKe+IiTpnLpUMzKlN5sDBTSuz13um hxxVFPhK9/M11F2cyAGTGquLcnd8pwFgPZtsHozUUYLQkUJdm5kAmMuG5Oeel56gnqUU UG/wHFgw5jjXS9X8EDY0XNewJZvCOH7zcl/AI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=jG/W38RBRXQCf0BQHcSzAHHqllcewO6ZGB9LSpZGK2e6GQ428WX+PpzW7uhDLKHkuK kbhKZn2DdwLZeclqMqVLK3uPZehT8h54K3/Io/fZLUdxSASr0LpldjXCVfA1aAeYpQyh nwI0nNTtjzelnEDkxkUCJFcgRv7OPblLpS8xU= MIME-Version: 1.0 Received: by 10.220.62.5 with SMTP id v5mr3321112vch.104.1283225720328; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) Date: Mon, 30 Aug 2010 23:35:20 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org Subject: [IPP] EXTENDED - PWG Last Call of IPP JPS2 (26 July to 17 September 2010) 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="===============1956242881==" 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: F1F8C793BF.A99BE X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1956242881== Content-Type: multipart/alternative; boundary=e0cb4e887ee93a1137048f16457a --e0cb4e887ee93a1137048f16457a Content-Type: text/plain; charset=ISO-8859-1 Hi, Per PWG Process/3.0, the PWG Last Call of IPP JPS2 is automatically extended until we achieve quorum (7 acknowledgements by PWG voting members - we now have 4). We discussed this at last week's IPP WG and decided to extend the PWG Last Call until Friday 17 September. See Mike's original note below for instructions on the subject and destination for your PWG Last Call note. Cheers, - Ira (IPP co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-clean.pdf > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: ipp@pwg.org > Subject: has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: The PWG Definition of the Standards Development Process Version 3.0 > is located at: > > http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e0cb4e887ee93a1137048f16457a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Per PWG Process/3.0, the PWG Last Call of IPP JPS2
is automat= ically extended until we achieve quorum (7
acknowledgements by PWG votin= g members - we now
have 4).

We discussed this at last week's = IPP WG and decided
to extend the PWG Last Call until Friday 17 September.

See Mike'= s original note below for instructions on the
subject and destination fo= r your PWG Last Call note.

Cheers,
- Ira (IPP co-editor)

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Op= en Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IP= P & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofm= usic
http://sites.google.c= om/site/highnorthinc
mailto:blueroofmusic@gmail.com
winter:
=A0 579 Park Place=A0 Saline, = MI=A0 48176
=A0 734-944-0094
summer:
=A0 PO Box 221=A0 Grand Marais, MI 49839
= =A0 906-494-2434


On Mon, Jul 26, 2010 at 11:19 PM, Michae= l Sweet <msweet@ap= ple.com> wrote:
Greetings:

[This PWG Last Call will start today on Monday 26 July 2010.
This PWG Last Call will end = at Friday 27 August 2010 at 10pm US PDT.]

= This is the formal announcement of = the PWG Last Call for the IPP Job and
Printer Operations Set-2 (JP= S2) specification, which is located at:

=A0
ftp://ftp.pwg.org/pub/pwg/ipp= /wd/wd-ippjobprinterext10-v31-20100725-clean.pdf

All required operations and attributes defined in th= is document have been
prototyped by Apple and/or Xero= x. =A0The IPP WG has completed a working
group last call and subseque= nt 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.

Please send your review acknowledgment *exactly* as = follows:

To: =A0= ipp@pwg.org
Subject: =A0<Company Name> has = reviewed IPP JPS2 and has [no] comments



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


N= ote: =A0The PWG Definition of the Standards Development Process Version 3.0=
is located at:

=A0http://www.pwg.org/chair/m= embership_docs/pwg-process30.pdf

Regards,
- Michael Sweet (PWG Chair)


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

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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e0cb4e887ee93a1137048f16457a-- --===============1956242881== 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 --===============1956242881==-- From pwg-announce-bounces@pwg.org Mon Aug 30 20:35:29 2010 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 0DE043A659B for ; Mon, 30 Aug 2010 20:35:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.349, 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 HDJAigLQDRX5 for ; Mon, 30 Aug 2010 20:35:23 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 2EC723A6894 for ; Mon, 30 Aug 2010 20:35:08 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id EBC38793C8; Mon, 30 Aug 2010 23:35:27 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com [209.85.213.46]) by pwg.org (Postfix) with ESMTP id 39DFD793BB; Mon, 30 Aug 2010 23:35:20 -0400 (EDT) Received: by ywh1 with SMTP id 1so2119518ywh.5 for ; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=/8cktHpmq/UmsgjqCMpf/dxGQ/HQQY34FData2TQUfo=; b=cAQxbCRmGKWLZmXAe5603vccD+ebrf91mSBB/qKe+IiTpnLpUMzKlN5sDBTSuz13um hxxVFPhK9/M11F2cyAGTGquLcnd8pwFgPZtsHozUUYLQkUJdm5kAmMuG5Oeel56gnqUU UG/wHFgw5jjXS9X8EDY0XNewJZvCOH7zcl/AI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=jG/W38RBRXQCf0BQHcSzAHHqllcewO6ZGB9LSpZGK2e6GQ428WX+PpzW7uhDLKHkuK kbhKZn2DdwLZeclqMqVLK3uPZehT8h54K3/Io/fZLUdxSASr0LpldjXCVfA1aAeYpQyh nwI0nNTtjzelnEDkxkUCJFcgRv7OPblLpS8xU= MIME-Version: 1.0 Received: by 10.220.62.5 with SMTP id v5mr3321112vch.104.1283225720328; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) Received: by 10.220.125.19 with HTTP; Mon, 30 Aug 2010 20:35:20 -0700 (PDT) Date: Mon, 30 Aug 2010 23:35:20 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: pwg-announce@pwg.org Subject: [Pwg-Announce] EXTENDED - PWG Last Call of IPP JPS2 (26 July to 17 September 2010) 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="===============0000069698==" 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: EBC38793C8.ACD60 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0000069698== Content-Type: multipart/alternative; boundary=e0cb4e887ee93a1137048f16457a --e0cb4e887ee93a1137048f16457a Content-Type: text/plain; charset=ISO-8859-1 Hi, Per PWG Process/3.0, the PWG Last Call of IPP JPS2 is automatically extended until we achieve quorum (7 acknowledgements by PWG voting members - we now have 4). We discussed this at last week's IPP WG and decided to extend the PWG Last Call until Friday 17 September. See Mike's original note below for instructions on the subject and destination for your PWG Last Call note. Cheers, - Ira (IPP co-editor) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing 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 winter: 579 Park Place Saline, MI 48176 734-944-0094 summer: PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Jul 26, 2010 at 11:19 PM, Michael Sweet wrote: > Greetings: > > [This PWG Last Call will start today on Monday 26 July 2010. > This PWG Last Call will end at Friday 27 August 2010 at 10pm US PDT.] > > This is the formal announcement of the PWG Last Call for the IPP Job and > Printer Operations Set-2 (JPS2) specification, which is located at: > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext10-v31-20100725-clean.pdf > > All required operations and attributes defined in this document have been > prototyped by Apple and/or Xerox. The IPP 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. > > Please send your review acknowledgment *exactly* as follows: > > To: ipp@pwg.org > Subject: has reviewed IPP JPS2 and has [no] comments > > > Please do NOT simply reply to this note on the PWG-Announce list. > > > Note: The PWG Definition of the Standards Development Process Version 3.0 > is located at: > > http://www.pwg.org/chair/membership_docs/pwg-process30.pdf > > Regards, > - Michael Sweet (PWG Chair) > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > pwg-announce mailing list > pwg-announce@pwg.org > https://www.pwg.org/mailman/listinfo/pwg-announce > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e0cb4e887ee93a1137048f16457a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Per PWG Process/3.0, the PWG Last Call of IPP JPS2
is automat= ically extended until we achieve quorum (7
acknowledgements by PWG votin= g members - we now
have 4).

We discussed this at last week's = IPP WG and decided
to extend the PWG Last Call until Friday 17 September.

See Mike'= s original note below for instructions on the
subject and destination fo= r your PWG Last Call note.

Cheers,
- Ira (IPP co-editor)

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Op= en Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IP= P & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofm= usic
http://sites.google.c= om/site/highnorthinc
mailto:blueroofmusic@gmail.com
winter:
=A0 579 Park Place=A0 Saline, = MI=A0 48176
=A0 734-944-0094
summer:
=A0 PO Box 221=A0 Grand Marais, MI 49839
= =A0 906-494-2434


On Mon, Jul 26, 2010 at 11:19 PM, Michae= l Sweet <msweet@ap= ple.com> wrote:
Greetings:

[This PWG Last Call will start today on Monday 26 July 2010.
This PWG Last Call will end = at Friday 27 August 2010 at 10pm US PDT.]

= This is the formal announcement of = the PWG Last Call for the IPP Job and
Printer Operations Set-2 (JP= S2) specification, which is located at:

=A0
ftp://ftp.pwg.org/pub/pwg/ipp= /wd/wd-ippjobprinterext10-v31-20100725-clean.pdf

All required operations and attributes defined in th= is document have been
prototyped by Apple and/or Xero= x. =A0The IPP WG has completed a working
group last call and subseque= nt 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.

Please send your review acknowledgment *exactly* as = follows:

To: =A0= ipp@pwg.org
Subject: =A0<Company Name> has = reviewed IPP JPS2 and has [no] comments



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


N= ote: =A0The PWG Definition of the Standards Development Process Version 3.0=
is located at:

=A0http://www.pwg.org/chair/m= embership_docs/pwg-process30.pdf

Regards,
- Michael Sweet (PWG Chair)


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

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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e0cb4e887ee93a1137048f16457a-- --===============0000069698== 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 --===============0000069698==-- From ipp-bounces@pwg.org Tue Aug 31 02:04:04 2010 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 690C23A68EF for ; Tue, 31 Aug 2010 02:04:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUruxGuodSDI for ; Tue, 31 Aug 2010 02:04:03 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 32E523A63D3 for ; Tue, 31 Aug 2010 02:04:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 2938D793D5; Tue, 31 Aug 2010 05:04:12 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mow.securemx.jp (mow300.securemx.jp [210.130.202.48]) by pwg.org (Postfix) with ESMTP id 57CC8793CF for ; Tue, 31 Aug 2010 05:04:05 -0400 (EDT) Received: by mow.securemx.jp (mow300) id o7V943jQ010158; Tue, 31 Aug 2010 18:04:03 +0900 Received: from mx20.fujixerox.co.jp (mx20.fujixerox.co.jp [192.26.96.20]) by relay.securemx.jp (mx-mr300) id o7V942IN018704; Tue, 31 Aug 2010 18:04:02 +0900 Received: from ms20.fujixerox.co.jp ([129.249.27.70]) by mx20.fujixerox.co.jp with ESMTP id o7V942nq025218 for ; Tue, 31 Aug 2010 18:04:02 +0900 (JST) Received: from ms2.dc.fxis.co.jp (ms2.dc.fxis.co.jp [143.94.15.17]) by ms20.fujixerox.co.jp with ESMTP id o7V942YR019473 for ; Tue, 31 Aug 2010 18:04:02 +0900 (JST) Received: from [172.27.142.231] ([172.27.142.231]) by ms2.dc.fxis.co.jp (8.13.8/8.13.8) with ESMTP id o7V941ZX012275 for ; Tue, 31 Aug 2010 18:04:01 +0900 (JST) Message-ID: <4C7CC581.5000507@fujixerox.co.jp> Date: Tue, 31 Aug 2010 18:04:01 +0900 From: Shin Ohtake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: ipp@pwg.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Fuji Xerox has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 2938D793D5.A8635 X-pwg-MailScanner-From: ipp-bounces@pwg.org -- // ------------------------------------------------------------ Shin Ohtake CTPF-4D, Fuji Xerox Co.,Ltd. phone: +81-45-755-5474 (direct) mail: shin.ohtake@fujixerox.co.jp ------------------------------------------------------------ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Tue Aug 31 07:01:37 2010 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 7F88C3A6A06 for ; Tue, 31 Aug 2010 07:01:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.368 X-Spam-Level: X-Spam-Status: No, score=-0.368 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, 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 nH0PMcxIjzlN for ; Tue, 31 Aug 2010 07:01:36 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 666E73A69D8 for ; Tue, 31 Aug 2010 07:01:36 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 35BBC793CA; Tue, 31 Aug 2010 10:01:59 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-gw.okidata.com (mail-gw.okidata.com [207.77.135.74]) by pwg.org (Postfix) with ESMTP id C058C79334 for ; Tue, 31 Aug 2010 10:01:54 -0400 (EDT) To: ipp@pwg.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.6 CCH4 June 18, 2008 Message-ID: From: Nancy.Chen@okidata.com Date: Tue, 31 Aug 2010 10:01:52 -0400 X-MIMETrack: Serialize by Router on ODA-SMTP-MTA/OKIDATA/OKI_DATA_CORP/OKI_ELECTRIC/US(Release 6.5.6FP3|March 27, 2008) at 08/31/2010 10:01:54 AM, Serialize complete at 08/31/2010 10:01:54 AM X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Oki Data has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1181971086==" 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: 35BBC793CA.A8D46 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============1181971086== Content-Type: multipart/alternative; boundary="=_alternative 004D132D85257790_=" This is a multipart message in MIME format. --=_alternative 004D132D85257790_= Content-Type: text/plain; charset="US-ASCII" -------------------------------------------------------------------------------------------------- Nancy Chen, PWG Vice-Chair Principal Engineer Solutions and Technology Oki Data 2000 Bishops Gate Blvd. Mt. Laurel, NJ 08054 Phone: (856)222-7006 Email: Nancy.Chen@okidata.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --=_alternative 004D132D85257790_= Content-Type: text/html; charset="US-ASCII"

--------------------------------------------------------------------------------------------------
Nancy Chen, PWG Vice-Chair
Principal Engineer
Solutions and Technology
Oki Data
2000 Bishops Gate Blvd.
Mt. Laurel, NJ 08054
Phone: (856)222-7006
Email: Nancy.Chen@okidata.com

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --=_alternative 004D132D85257790_=-- --===============1181971086== 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 --===============1181971086==-- From ipp-bounces@pwg.org Tue Aug 31 07:07:15 2010 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 411BF3A69D8 for ; Tue, 31 Aug 2010 07:07:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 DZBE3ysGoc-8 for ; Tue, 31 Aug 2010 07:07:07 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 38BB33A6A2B for ; Tue, 31 Aug 2010 07:07:07 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C1721793D6; Tue, 31 Aug 2010 10:07:33 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from EEAEX01.us.epson.net (eeaex01.eea.epson.com [12.9.144.164]) by pwg.org (Postfix) with ESMTP id 28FA4793D0 for ; Tue, 31 Aug 2010 10:07:27 -0400 (EDT) Received: from EEAEX03.us.epson.net ([148.130.32.21]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Aug 2010 07:07:27 -0700 x-mimeole: Produced By Microsoft Exchange V6.5 MIME-Version: 1.0 x-cr-puzzleid: {93958313-06A2-4A2B-9344-ADA1490B0F84} x-cr-hashedpuzzle: BTAb BpDN B9ge CkTs Cyrm DlbU D8Ps FVh5 Iovr JfjO Jro9 JzyM J1RK LK66 L6Fc L+wf; 1; aQBwAHAAQABwAHcAZwAuAG8AcgBnAA==; Sosha1_v1; 7; {93958313-06A2-4A2B-9344-ADA1490B0F84}; ZwBsAGUAbgAuAHAAZQB0AHIAaQBlAEAAZQBpAHQAYwAuAGUAcABzAG8AbgAuAGMAbwBtAA==; Tue, 31 Aug 2010 14:08:58 GMT; WwBJAFAAUABdACAARQBwAHMAbwBuACAAaABhAHMAIAByAGUAdgBpAGUAdwBlAGQAIABJAFAAUAAgAEoAUABTADIAIABhAG4AZAAgAGgAYQBzACAAbgBvACAAYwBvAG0AbQBlAG4AdABzAA== Content-class: urn:content-classes:message Subject: [IPP] Epson has reviewed IPP JPS2 and has no comments Date: Tue, 31 Aug 2010 07:08:58 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Epson has reviewed IPP JPS2 and has no comments Thread-Index: ActJFg5ahvWukCQqRH6p6REC5r0u3Q== From: "Petrie, Glen" To: X-OriginalArrivalTime: 31 Aug 2010 14:07:27.0097 (UTC) FILETIME=[D7A0C690:01CB4915] X-pwg-MailScanner: Found to be clean, Found to be clean X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1611795390==" 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: C1721793D6.AA21E X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1611795390== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4915.D727EF46" Content-class: urn:content-classes:message This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4915.D727EF46 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_01CB4915.D727EF46 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_01CB4915.D727EF46-- --===============1611795390== 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 --===============1611795390==-- From ipp-bounces@pwg.org Tue Aug 31 07:09:05 2010 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 145C83A6A3F for ; Tue, 31 Aug 2010 07:09:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqmmKyaCpDht for ; Tue, 31 Aug 2010 07:09:02 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 2639C3A6A0A for ; Tue, 31 Aug 2010 07:08:54 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6439F793E9; Tue, 31 Aug 2010 10:09:05 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail.mwaintel.com (67-148-10-188.dia.static.qwest.net [67.148.10.188]) by pwg.org (Postfix) with ESMTP id 22E36793E3 for ; Tue, 31 Aug 2010 10:09:01 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: [IPP] MWAi has reviewed IPP JPS2 and has no comments Date: Tue, 31 Aug 2010 07:09:01 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] MWAi has reviewed IPP JPS2 and has no comments Thread-Index: ActJFg5ahvWukCQqRH6p6REC5r0u3QAABgQw References: From: "Eric Chang" To: X-pwg-MailScanner: Found to be clean, Found to be clean X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1231977540==" 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: 6439F793E9.A8F8A X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1231977540== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4916.0FA50433" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4916.0FA50433 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_01CB4916.0FA50433 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_01CB4916.0FA50433-- --===============1231977540== 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 --===============1231977540==-- From ipp-bounces@pwg.org Tue Aug 31 09:25:50 2010 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 354F13A689B for ; Tue, 31 Aug 2010 09:25:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.109 X-Spam-Level: X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 w3sjbZMAjUSq for ; Tue, 31 Aug 2010 09:25:48 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by core3.amsl.com (Postfix) with ESMTP id 969873A690F for ; Tue, 31 Aug 2010 09:25:48 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 59368793EE; Tue, 31 Aug 2010 12:26:11 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail4.sharplabs.com (mail4.sharplabs.com [216.65.151.214]) by pwg.org (Postfix) with ESMTP id DF501793EC for ; Tue, 31 Aug 2010 12:26:03 -0400 (EDT) X-ASG-Debug-ID: 1283271960-0e2850ed0001-ml9GHW Received: from wabex1.enet.sharplabs.com (webmail.sharplabs.com [172.29.224.8]) by mail4.sharplabs.com with ESMTP id NaKetLF1pbzq5qYH for ; Tue, 31 Aug 2010 09:26:00 -0700 (PDT) X-Barracuda-Envelope-From: jmurdock@sharplabs.com Received: from wabex3.sharpamericas.com ([172.29.224.10]) by wabex1.enet.sharplabs.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Aug 2010 09:26:00 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 X-Barracuda-BBL-IP: 172.29.224.10 X-Barracuda-RBL-IP: 172.29.224.10 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 31 Aug 2010 09:25:59 -0700 X-ASG-Orig-Subj: Sharp has reviewed IPP JPS2 and has no comments Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Sharp has reviewed IPP JPS2 and has no comments Thread-Index: ActJKSfpZBPnPy1tTIqqwgSOx8kQVA== From: "Murdock, Joe" To: X-OriginalArrivalTime: 31 Aug 2010 16:26:00.0649 (UTC) FILETIME=[32E42390:01CB4929] X-Barracuda-Connect: webmail.sharplabs.com[172.29.224.8] X-Barracuda-Start-Time: 1283271960 X-Barracuda-URL: http://mail4.enet.sharplabs.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at sharplabs.com X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.00 X-Barracuda-Spam-Status: No, SCORE=-2.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=HTML_MESSAGE, THREAD_INDEX, THREAD_TOPIC X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.39528 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.01 THREAD_INDEX thread-index: AcO7Y8iR61tzADqsRmmc5wNiFHEOig== 0.01 THREAD_TOPIC Thread-Topic: ...(Japanese Subject)... 0.00 HTML_MESSAGE BODY: HTML included in message X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Sharp has reviewed IPP JPS2 and has no comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1845727627==" 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: 59368793EE.A9352 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1845727627== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB4929.329D18DC" This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4929.329D18DC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 =20 --------------------------------------- Joe Murdock Chair Printer Working Group Imaging Device Security Principal Engineer Sharp Labs of America 5750 NW Pacific Rim Blvd Camas, WA 98607 (360) 817-7542 jmurdock@sharplabs.com =20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CB4929.329D18DC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

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

Joe Murdock

Chair Printer Working Group Imaging Device Security

Pr= incipal Engineer

Sharp Labs of America

5750 NW Pacific Rim Blvd

Camas, WA 9860= 7

(360) 817-7542

jmurdock@sharplabs.com

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CB4929.329D18DC-- --===============1845727627== 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 --===============1845727627==-- From ipp-archive@lists.ietf.org Tue Aug 31 14:53:30 2010 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 CE5313A686C for ; Tue, 31 Aug 2010 14:53:30 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): Subject: ...ve@lists.ietf.org V|AGRA \256 Official Selle[...] X-Spam-Flag: NO X-Spam-Score: -6.465 X-Spam-Level: X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[BAYES_80=2, DRUGS_ERECTILE=1, DRUGS_ERECTILE_OBFU=1.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, FUZZY_VPILL=0.687, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, J_CHICKENPOX_14=0.6, MANGLED_VIAGRA=2.5, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_OBFU_VIAGRA=1.666, SUBJECT_NEEDS_ENCODING=0.001, TT_OBSCURED_VIAGRA=1.652, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 n5VikCqm-C04 for ; Tue, 31 Aug 2010 14:53:29 -0700 (PDT) Received: from 0139-86-27-72-DYNAMIC-dsl.cwjamaica.com (0139-86-27-72-DYNAMIC-dsl.cwjamaica.com [72.27.86.139]) by core3.amsl.com (Postfix) with ESMTP id 12B9D3A682B for ; Tue, 31 Aug 2010 14:53:28 -0700 (PDT) From: ipp-archive@lists.ietf.org To: ipp-archive@lists.ietf.org Subject: ipp-archive@lists.ietf.org V|AGRA Official Seller -96% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20100831215329.12B9D3A682B@core3.amsl.com> Date: Tue, 31 Aug 2010 14:53:28 -0700 (PDT)
Click here!

From ipp-archive@megatron.ietf.org Tue Aug 31 14:53:30 2010 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 D964E3A682B for ; Tue, 31 Aug 2010 14:53:30 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): Subject: ...megatron.ietf.org V|AGRA \256 Official Selle[...] X-Spam-Flag: NO X-Spam-Score: -6.465 X-Spam-Level: X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[BAYES_80=2, DRUGS_ERECTILE=1, DRUGS_ERECTILE_OBFU=1.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, FUZZY_VPILL=0.687, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_08=1.787, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, J_CHICKENPOX_14=0.6, MANGLED_VIAGRA=2.5, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_OBFU_VIAGRA=1.666, SUBJECT_NEEDS_ENCODING=0.001, TT_OBSCURED_VIAGRA=1.652, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 L3lsKQhDm1th for ; Tue, 31 Aug 2010 14:53:29 -0700 (PDT) Received: from 0139-86-27-72-DYNAMIC-dsl.cwjamaica.com (0139-86-27-72-DYNAMIC-dsl.cwjamaica.com [72.27.86.139]) by core3.amsl.com (Postfix) with ESMTP id 9E1E53A6839 for ; Tue, 31 Aug 2010 14:53:29 -0700 (PDT) From: ipp-archive@megatron.ietf.org To: ipp-archive@megatron.ietf.org Subject: ipp-archive@megatron.ietf.org V|AGRA Official Seller -96% MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20100831215329.9E1E53A6839@core3.amsl.com> Date: Tue, 31 Aug 2010 14:53:29 -0700 (PDT)
Click here!