From ipp-bounces@pwg.org Mon Apr 2 14:09:18 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1634E21F86E2 for ; Mon, 2 Apr 2012 14:09:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.998 X-Spam-Level: X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pkH0q71b8l17 for ; Mon, 2 Apr 2012 14:09:17 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id D6BD221F8523 for ; Mon, 2 Apr 2012 14:09:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BA2B679700; Mon, 2 Apr 2012 17:08:45 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 14DDC796FA; Mon, 2 Apr 2012 17:08:28 -0400 (EDT) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M1V001JLEPVK102@mail-out.apple.com>; Mon, 02 Apr 2012 14:08:28 -0700 (PDT) X-AuditID: 11807134-b7fee6d000000d31-36-4f7a154ba7ff 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 9F.B5.03377.C451A7F4; Mon, 02 Apr 2012 14:08:28 -0700 (PDT) From: Michael Sweet Date: Mon, 02 Apr 2012 14:08:27 -0700 To: cloud@pwg.org Message-id: X-Mailer: Apple Mail (2.1276) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOLMWRmVeSWpSXmKPExsUieFRTW9dHtMrfYEMLu8Xl7QdYLY7te8li ceRbrAOzx9aTP9g85i2ezhTAFMVlk5Kak1mWWqRvl8CV8enmafaCydIV8/+9Ym1g7JboYuTk kBAwkXj9cwobhC0mceHeeiCbi0NIYDqTROuVr4wgCTYBNYnfk/pYQWxeAUOJR2+uM4PYzAIJ Em/aljOB2CwCKhLf3ywCiwsLmEn82LaDEaJGUWLZ9D9gvSICghLnD9xggphjIzGv8ysLxGJZ iYtdfUwTGHlmIVkxC8kKCFtbYtnC10BxDiBbR2LyQkZUYQj74/kjTAsY2VYxChal5iRWGpro JRYU5KTqJefnbmIEBV9DockOxoM/+Q8xCnAwKvHwBp6o9BdiTSwrrsw9xCjBwawkwvvwBVCI NyWxsiq1KD++qDQntfgQozQHi5I470XhKn8hgfTEktTs1NSC1CKYLBMHp1QDY/RGjvtnJoSu 2H9H9iIfa5XE9ph/OaWzj6WId5t/35/SdmFz39Wroim/w01fe/Uk1LNLC4S1Kr5bkSBaOdtZ r0nD+3vzj7avsx8k35ga+2v3p8bQdUbrM0LXPZIQ3fiqUfyTQcKT9Uzmk9N8g2q9dt0uKLQr fvWqSuRp82+3+r9tLk+dAnUmKbEUZyQaajEXFScCAKPbJMI6AgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "" Subject: [IPP] Minutes posted from today's Cloud/IPP concall X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0931566727==" 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: BA2B679700.A7A00 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0931566727== Content-type: multipart/alternative; boundary="Boundary_(ID_U9xlXJ5BPBdkds1xhVxixw)" --Boundary_(ID_U9xlXJ5BPBdkds1xhVxixw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the minutes from today's combined Cloud Imaging and IPP working group conference call to: ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20120402.pdf Our next Cloud Imaging WG conference call will be April 16, 2012 at 3:00pm Eastern Time. New action items: - Mike to post prototype statement for IPP JPS3 - Mike to provide IPP slide on supply types and their printer-state-reasons - Ira to reduce RFC 4559 reference in LDAP schema to informative ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_U9xlXJ5BPBdkds1xhVxixw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the minutes from today's combined Cloud Imaging and IPP working= group conference call to:


Our next Cloud Imaging WG conference call will be April 16, 2012 at= 3:00pm Eastern Time.

New action items:
=
- Mike to post prototype statement for IPP JPS3
- M= ike to provide IPP slide on supply types and their printer-state-reasons
- Ira to reduce RFC 4559 reference in LDAP schema to informative
=

___________________________= _____________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_U9xlXJ5BPBdkds1xhVxixw)-- --===============0931566727== 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 --===============0931566727==-- From ipp-bounces@pwg.org Mon Apr 2 15:39:06 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C156821F86E3 for ; Mon, 2 Apr 2012 15:39:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAnqRlHusAJj for ; Mon, 2 Apr 2012 15:39:05 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id A773221F8648 for ; Mon, 2 Apr 2012 15:39:04 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A7EDB79704; Mon, 2 Apr 2012 18:38:39 -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 4E603796F8 for ; Mon, 2 Apr 2012 18:38:21 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Apr 2012 15:38:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CD1121.4E2A6B88" Date: Mon, 2 Apr 2012 15:38:18 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: A different function model for discuss Thread-Index: Ac0RIUtOdXZNDCuQQMmlzs03cwyVnA== From: "Petrie, Glen" To: X-OriginalArrivalTime: 02 Apr 2012 22:38:20.0958 (UTC) FILETIME=[4E57C3E0:01CD1121] X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] A different function model for discuss 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: A7EDB79704.A9D8D X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CD1121.4E2A6B88 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01CD1121.4E2A6B88" ------_=_NextPart_002_01CD1121.4E2A6B88 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 After today's meeting, I thought I would try to draw a slightly different representation of the functional model diagram than what is in the current model document. In the current model it is very unclear what and where the "Cloud Print Manager" is (is in its own cloud or is it proxy (so not really a cloud service) or in the printer (so not really a cloud service)). Why does the (Print) Client "register" with the Cloud Provider instead of just using the Cloud Print Provider.=20 =20 In the functional model attached, I propose the more cloud centric model which places service, security and other functionality in the Cloud. The model is not specifically concerned with interfaces such as using IPP; it is meant to be more a very top level view. In the attached model the Client uses or accesses the Cloud Provider for printing services. The User interacts with the Cloud Print Provider to select a Print Service associated with the User. The Cloud Print Provider then sends Capability information (which likely has no secure information) to the Client. The Print Client creates Print Job Ticket (with a Print Content reference) which is sent to the Print Service (or Print Service Manager) for printing. The Print Service accepts (or rejects the Print Job). The Print Service prints the Print Job and sends status info to the Print Status Service. Federated printing also work quit well with this model.=20 =20 Glen =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_002_01CD1121.4E2A6B88 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 

After today’s meeting, I thought I would try to draw a slightly different r= epresentation of the functional model diagram than what is in the current model document.=   In the current model it is very unclear what and where the “Cloud Pri= nt Manager” is (is in its own cloud or is it proxy (so not really a cloud service) or in the printer (so not really a cloud service)).   Wh= y does the (Print) Client “register” with the Cloud Provider instead of just using the Cloud Print Provider.

 

In the functional model attached, I propose the more cloud centric model which places service, security and other functionality in the Cloud. The model is= not specifically concerned with interfaces such as using IPP; it is meant to be more a very top level view.  In the attached model the Client uses or = accesses the Cloud Provider for printing services.  The User interacts with the= Cloud Print Provider to select a Print Service associated with the User.  Th= e Cloud Print Provider then sends Capability information (which likely has no secure information) to the Client.  The Print Client creates Print Job Ticket (with a Print Content reference) which is sent to the Print Service (or Pri= nt Service Manager) for printing.  The Print Service accepts (or rejects = the Print Job).  The Print Service prints the Print Job and sends status i= nfo to the Print Status Service.   Federated printing also work quit = well with this model.

 

Glen

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_002_01CD1121.4E2A6B88-- ------_=_NextPart_001_01CD1121.4E2A6B88 Content-Type: image/jpeg; name="A model-small.jpg" Content-Transfer-Encoding: base64 Content-Description: A model-small.jpg Content-Disposition: attachment; filename="A model-small.jpg" /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAMCAgICAgMCAgIDAwMDBAYEBAQE BAgGBgUGCQgKCgkICQkKDA8MCgsOCwkJDRENDg8QEBEQCgwSExIQEw8QEBD/ 2wBDAQMDAwQDBAgEBAgQCwkLEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQ EBAQEBAQEBAQEBAQEBAQEBAQEBAQEBD/wAARCAFgAfQDASIAAhEBAxEB/8QA HwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUF BAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1 dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEB AQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAEC AxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRom JygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU 1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD9U6KKKACi iigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKK KACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAoooo AKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAK8Xj+Ouqt8f T8OjolqfCBlbQV1kO3nf8JCtqL1rbH3fL+zHr18wFfavZm3FSFIBxxmvnlP2 OvCEWhR6rHfyD4jJqy+Iz4nM1yUbVftHntKbXzfL2EZi24z5ZxnPNAHqHxH+ LGg/DObRrLU9H17VL7xBLPBp1npFg11PNJDEZXG0EY+RSckgcckVzfg79p34 W+NPNuLKbV7CwGhSeJLfUNT02S1trvT4ionmhZ+WETOivkDBYYyDmur8TeBZ vEHjfwX4xGppAvhOe+meDyixuPtFq0AAbPy7S27oc9PevM9K/Zat4/C3hvwh rvif7XY6P8PtU8CXZhtjG9wt61qTOhLHZtFsRtOc7xzxyAbun/tP/DS50zU9 S1K28SaM2n2dvqMVpqejzQXOoWtxKIoJbWLBaYSSsiBR8wZ1DKuRWVoX7UWj Xmo+MjrfhrXNNg8O3el6dZ6ZLpki6tdXl3E8nkeRkhmwu5Sp27MsWwCRn337 NnjTxZJ/bPxA+J1le+IdJ0+zsPDl5p2iG2hszbXsF4txPE0z+fI81rb7wGRd qEKFLZqh4l/ZU8SeP4tf1b4h+MvDWta9qer6VrdpHL4bL6TDLZW8tv5MtrJO zSxPHO/WQMGO4HgAAHc6J8eNO8WeKfBuk+GrCZLbX59XtNTh1G3e3vdOubKK NzC8ZOFb5wT1BUqVJBBNDxP+0fY+DPjDr3w/8SeFtZttA0Dwxb+ILjXktC8C +Y84IOGyVPkiNNqlmlLLjgEs+G/7O6+A7/wlqkd54etptBu9Wvby10LQI9Ms ppL2GOICKJGJUIsS/M7SO3dgMATfFL4Dax8RfGGp65Z+L7bTNP13w3b6Dfwv p7TXEUlrdTXVpcwSeYqgrNKC6OjBlQAbc5oA674d/Fjw78R5tSsLHTdb0fVN I8lrzTNasGtLqKKYMYZdhyCjhWwwJ5VgcEEVwvi39p3RrDxZoXhXwroWq339 peL7bwrPqs+nSrpplMhS5jhuAQGlj2sORtyrAEkEV1Pw3+G/izQPFOufEH4h eK9O1zxFrdlZaWTpumtY2lvZ2rTNGqxvLKxdnuJWZi+OQAABXGyfs7+Mo9X0 jTNO+I2nxeCtF8ZjxnbaY+js16ZnupLmW3a587aYvNmkZCIwwyASwHIBNo/7 V3geRIbO+ttZ1O9Q3M2oy6Po0skGm2qX9zaxyzruZ1UtbSAld33GbCqRXU2v x98D33iy68K2tlr8iWtxc2P9rJpkh02S8gjaSa2W46GRVVs5AXcpUNuGK8l1 79jPUNZ0vStIHi/QF+xSXrDU5fD7f2pp5uNRuLvzbC7injeJwLgIRL5seYww UZIPpHhb4P8AjbwnrGoaTp/xDtV8CX+pajqz6YNIB1Bpr1pHlha6aQp5Imle UbYg+cLux1AL97+0T8M9M8O6N4r1PUL210zXPCs/jG2mktSdunRC2LF1XJEn +lwgIAckn0rNl/ad8C22jpqF94d8X2moz6hDptros+jsl/dzSxPLH5K7vLdT HFK24PgbGBweK5Xwx+zL480yLSdO1/4n6Pfaf4a8FX/gnR44fDagrbTG08ue 5WaWSOdwtoquu1UYHgLznM0z9kC+0/wXrvh0ar4Hxq+o2t7/AGIPC8knh1BD HIh22cty0kUkhk3NJDNHgxRgAANuAPa0+KnhiT4a3vxTcX1rpGnWV1e3Ud5a vb3MIt9/mxvE4BDho2XHQkcEgg1yN/8AtCaf4L0jSYviFoWqt4huNHXXtXst A06W9j0ayYn97cMOQi4KkjLMY3KrgHEdv8Brmy/Zs1n4FN4ia9uNR0nUrOO7 ZXSKF7kyukcau7usMZkCIrOzBEAJNZmofDr4h/ENIviJ4Y8Rx+CdV8W+F4PD vifTtY0RrqSFYmmO6DEseyaNri4Cs2+NgytggDIB3fhn4y+FPGPjrU/Afh20 1a9m0i2trq61KO0/4l6pcW8c8AE+cMzxyggAdjnHGc/Xvj54P8O+MYvCF/pH iXEuowaMdWj0mQ6cmoTBfJtjOcZdi6KCAV3OFLA8VN8Kfg/a/CnUPEJ0nUvP 0/Vl0qGzt3jIe2hsdOgslVnz85IgDZwOuPevN/GX7Kmu+L/ikPiBd+NtKmgt /E2l+JbH7bpMtxfWn2SSBjZRTG48uKBvJY5SIPmQ7mYZBAO/+AvxivfjL4Y1 LX7/AMF6v4dax1nUdMVL+ARiVLe7mhVkO5ssBEBIOAr7gMgZrlPDf7V3hs/D 7wp4p8W6Nqr6nrOgQeINVg0PT5buHSbSQsPPmOcpHlJMfeYhGIBAJrvvhL8P 9f8AhzYa3oWo69Y6npl1rmo6tpghsngngS8upbqSOZjIyyFZJmCsqp8oGQTz Xh15+w9bvYeGVh1TwdqV9pnhiy8LahceIvCSaoPJtnldLi0V5QIJf38gIfzE Py5Hy8gHr2o/tC+BdP8AFVh4akstfkttQvrTTI9ci0x20oXlyqNbwm46Ev5k YDKCuXALA8VyXif9rrwjZ+DfFfifwl4Y8T6s2h6VqV/psx0p1stVksw3mrFN nhVKktu2nYrsobFYniP9kTVNb8f2nihPGekNY6Vrmja1pa3ejPLeWaWBt8WU MgnWGG3YQMcRQq2ZCCSvBWX9kCe98TeKtYu/FmjWEXiLSNZ0mSXRdCNjdXy3 8LxB9Q2TeRcNEH3KVhjZmUEnqCAeqf8AC5dD0r4SWnxa8Y6Xq2h2ktvA8ljc 2h+1iWWRYo4xEpbJeRlCc8h1JI5xxniH9p+x06bwhLpngvxIw1rxBc6FqOl3 OkSrqkEiabPdxiKIHa5cxxfMGKbWYlhg47C/+HfinxB8G/8AhXfiTXdBuNYe ySzmuxogm0+YIw2h7OeR9yMiqrjzM8sVKnGOE+Gf7L114CvfDWoP4n05V0Px PdeIjpemWE0GnW6y6XLY/Z7SOWeV4VzJ5zZdgWLAKoIwAdLN+0z8Pf7B0bV9 K0zxPq1zraXsselado8kuoW6Wcvk3bTw8GMRS/I2Tktwu41B4B/aGs/iH8W9 S8BeH/DGrT6FF4e0vXrDxAtvi1uEu/tByWLZVSIVVPlyXEoIG0ZyLT9nvxt4 Vv7fxP8ADz4gaXp/iBLjxBHPLqWjvd2sllqeptf7BGs0bLLC5UK+4q2GyvIx sfC74D3vwk8VafeeGvFFvc6DF4U07w3e2t5YsbuV7J7l4p45lkCJua7kLoY2 6LgigDW8RfHzwh4Z8Yx+DtT0nxIBJqNtpD6tHpUjabFfXAQw27T8fM5kjUEA qGcAsDxXEeCP2m9e8VaJaeLdS+Huo6Lo0fjO48Kak1/AYnjRr2WztZ4iHYMR MkSTKQNrSnaSF5qeP/2Vdd8c/FCTx9ceNtKkgi8Q6V4hsBfaTNcXtkbN4GNn DKbgRRQP5LMSkIk3StlmGQZdW+E3jXR9DHwqhvYNY0jxP4+XxDHcwadJC2lW I1I6rdC5lMjI7GRVii2qhO8ZBwxAB9Egg9KWkAwKWgAooooAKKKKACiiigAo oooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACii igAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigBOvUUEgUtI QD1oA5Gf4o+Bba6uLOTWmMlrNJby+VaTyKsiMUddyoQSrKVODwQR2o/4Wz4D /wCgxP8A+C65/wDjdP8Ahj/yLd5/2MOvf+nW6rrKAOQ/4Wz4D/6DE/8A4Lrn /wCN0f8AC2fAf/QYn/8ABdc//G66+igDkP8AhbPgP/oMT/8Aguuf/jdH/C2f Af8A0GJ//Bdc/wDxuuvooA5D/hbPgP8A6DE//guuf/jdH/C2fAf/AEGJ/wDw XXP/AMbrr6KAOQ/4Wz4D/wCgxP8A+C65/wDjdH/C2fAf/QYn/wDBdc//ABuu vooA5D/hbPgP/oMT/wDguuf/AI3R/wALY8Bf9Bef/wAF1z/8brr6KAOQ/wCF s+A/+gxP/wCC65/+N0f8LZ8B/wDQYn/8F1z/APG66+igDkP+Fs+A/wDoMT/+ C65/+N0f8LZ8B/8AQYn/APBdc/8AxuuvooA5D/hbPgP/AKDE/wD4Lrn/AON0 f8LZ8B/9Bif/AMF1z/8AG66+igDkP+Fs+A/+gxP/AOC65/8AjdH/AAtnwH/0 GJ//AAXXP/xuuvooA5D/AIWz4D/6DE//AILrn/43R/wtnwH/ANBif/wXXP8A 8brr6KAOQ/4Wz4D/AOgxP/4Lrn/43R/wtnwH/wBBif8A8F1z/wDG66+igDkP +Fs+A/8AoMT/APguuf8A43R/wtnwH/0GJ/8AwXXP/wAbrr6KAOQ/4Wz4D/6D E/8A4Lrn/wCN0f8AC2fAf/QYn/8ABdc//G66+igDM0PXNK8Sacmr6JerdWkj yRrIoI+ZHKOpBAIIZWBBGQQa065P4agf2FqH/Ywa3/6cbiusoAKKKKACiiig AooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAC iiigAooooAKKKKACiiigDk/hj/yLd5/2MOvf+nW6rrK5P4Y/8i3ef9jDr3/p 1uq6ygDg/iX8WLL4a3GhadJ4U8R+ItR8R3E1vY2Oh28MszGKIyyM3myxqFCK TnP4VD4U+NXgnxLp1/dapLceFLrSb3+z7/T/ABJ5dlc205hWZVbLlG3RMHBR 2BXPPBxg/Gn4Za78RvHHw4l07U9c0rT9GvdSn1DUtHvltbi2WSyeOMBjkkM5 CkAHrzjrWD4i/Z40mx1/4eDSdIvfEdtb+M5fEHiS/wBbuxe3ExGkXdvFNK0p +ba5t0VVGF4IAAJoA9Uh+JHhD7HLearrun6Qkdzc2+NQvreIt5NwYGcYkI2l 9oGSD86hgrHbUFj8VvAd/wDEW++Fdv4jsn8SWGn2+pSWfnx7mhmMoUKN25mA hZmGOFZG6MK8I8H/AAC1i6+I0up+O/AFpe6Slr47EP21YJ41k1DXo57UhCTg yW29gccDIODxWj8A/ht4v8B+NvDGoeKvh1N5t38MvDui3msK1rJ9g1KxW6+0 RTt5nmlmWaJQ6Bw23BIAFAHfeI/2grDRPGGu+DNM+GXjzxFN4a+z/wBqXmja fbzW9uZoVmQfPOkjHy2BIVCewya7DQPiT4D8TWWl32j+LdLmGs2EWp2UTXKJ NLbSJ5iyCJiHA2gnkcYPoa8qX4C6v4p+MHxK8T694o8Z6BpGtT6WtlHout/Z IL+KOwjjlLqmXBDhkzlTgcetc94x/Z1v57z4n2Xg7wZYwW154N8OaD4aLyog mhtHvDc2KyEl4leN44mZsAiXqcGgD6F0zxb4V1tIJdF8T6VqEd1I8MDWt7HK JZEBLopVjuZQCSByADmom8Y6GNaj0VLuKQvb3k8lwlxCYoPszxpKknz7gwMo z8pAwdxU4B+aZfhV8Qb298TfFjwH8Ij4M1LSP7Ev/DXhqe4s4nv76y+0rdFx byNDEJ7a5NqCXyQis2MCo/G/7Ovj9tF8IaTpGlJrM9l4X1OTxEzzxxx6pqNx qul311asWPS6FveR5I2hThiBigD6D0L4ueAvEms69pGkeILW4i8OWNnqN7qK XETWPk3JnCFZgxU4NtLuzgDj8NmTxv4Mi02z1qXxfoqaffnFrdtqEQhuD6Rv u2v+BNfInin4J/Enxhe+PvEfhT4Sah4H07Vr/wAJ6gmjwS6ULvVIrA3gulEZ aW0WUGSB1STKN5aZIYnb0Pw3/Z/8QW2teA9U1zwXq50228Z6v4hvbTxBLpkk lksmkvbxSmCyjS3iLzBTsjEhDNvLZJwAfS3iXxjpPha50axvluZ7zX9QTTbC 3tow8kkhVnZiCQAiRo7sxPCr3JANnw94is/EejrrdvFJbwNLPERM0ZI8qV42 JMbMuCUJHzZwRkA5A8/8eA6Z8ePhrruotjTJ7LWtFhZvupqM628sP0LRW1yo 9S2O9cLa/DX4kXn7MPiP4O22i3uleIb2DW57e4M9uIZPtGrXUqW4fcwDSQsu SyFAswzkhlAB7/oviHQfEtob/wAPa3p+q2yyNEZrK5SeMOOqlkJGR3FZHj34 h+HvhzpVvqeu/bJ5L65SysLGxtmuLu+uXBKwwxLyzYVmOcBVUsxABNeMfs4+ AfE3w+1XxJ4q1Pwd40tRrjaVpotNUk0SOQ+W0ivc+RpyRwpGglALl2kdEGE+ VQfQfjD4c8Uy614L+IfhHQW1+88GajcXE2kJcRwy3dtcWzwSGFpSsfmpvVlD MoIDDIJFAFa0/aM8HPBcrrWg+JtA1Sy1DS9PuNI1XT1iu0OoXK21tMNrtG8T SPgujtt2sCMjFeiQ+J/Dc+q3GgweIdNk1OzjEtxZLdxmeFP7zxg7lHuQBXin jiP4u/FfQxu+GVxoGnWviPwxd2dlqFxbNqcq22rQz3k8hhmeJIkiQbUDFyVc 45UHifC/wa8eQ+IfDWgSfDAaZqfh3xRrOtar45a4tSmr2d0l2EjUo5uHeT7R AHSRFVPJ4JwtAH1NBrejXRtTa6tZT/brc3dr5dwjefANuZUwfmQb0ywyPmX1 Fc/ofxQ8GeJPF9x4L8PaxBqd5b6cNTkns5Y5rcRmZodnmIx/eB0OVxwMV8v2 fwp+OXirwf4a8ASfD698LzeFvhVrPgttUu9RtWhutQkGnJH5XkyO4hkW1kw7 KpAJyoxz6Z8GvB2r2/xs1bx1D8DpPh1o1x4QsdHEUklkGnuobqVmGy1kdQqo yhWJywAyBgCgDqfEP7Qun6H4r8ReFbH4ZePde/4RSSGLVtQ0jTree1t2kto7 kD5p1lciKVCQsZPOBk12ujfETwL4gttPutI8W6TP/adjHqdrH9rRZZLV4xIs vlkhguwhskcCvJbf4Bal4o+KPxQ8Q+JPE/jTQ9I8QarYtZ22j659kttQtk0m 0hkd1jy4PmRyRk5U4QY4wTzvjP8AZ61S4m+K0PhPwPYrBf6T4Z0/QI2kjjF7 ZWIJudOVyd0SSRqYDuwpEnOQDQB9E6b4s8Lazb215o/iXS76C9ma3tpba8jl SeVQWZEZSQzAKxIHICn0NV5PGmhR68+g/bYWeG1uLq5nFxD5VsIWiDpL8+9W xMjfdwB1IyoPzuvwo8a6xF45+IPhX4YN4Ivkm0XV/Cvh+eW0jkm1PTllMssg t5Hhi+0RyC1Pz5KIGbGeMbxL+z78Sbyz8PXqeGo9SvptBvNV8U2rXMSx6jqN xrmmajdacWZsESR29xCpPybY1DEA0AfRuhfF3wH4j1HxFZ6X4gtHtvDENpcX 2pfaIvsPl3CuyMkwYqQBGwYnGDWxL408HQWFnqc3izR0s9R/48rhr+IRXPIA 8ty2H5I6E9RXyD4l+CXxI8U3HjXxH4Z+E2qeDNM1HxN4b1ldDtZNJ+2aja2l rcRXG2KQy2YlWSSKUJJlW8peQxyOp+F3wC1/TvEPgDVte8GaqdNstf8AEOt3 Nvr02myy6e1xaRxwOYbONLeJnkR32RB9rOWLZJwAfSPgvxjpXjfSJdV0lZ4v s15cafdW9zGEmtrmCQxyRyKCQCCuRgkFSpBIINdDXk/wWD33i74reJbJs6Nq vi1Y7Bl+5I9rYWtrcuvqPtEEqE+sZr1igDlPht/yAtQ/7GDW/wD043FdXXKf Db/kBah/2MGt/wDpxuK6ugAooooAKKKKACiiigAooooAKKKKACiiigAooooA KKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAOT+GP8A yLd5/wBjDr3/AKdbquryK5P4ZjPhy8H/AFMOvf8Ap1uqwdH8GeFvFPinxte+ I9Ghv57fXI7eJ5yxMcQ06zYIvPA3OxwO7E96APSsijIrkP8AhUXw2/6E+w/J v8aP+FRfDb/oT7D8m/xoA6/IoyK8S0vxD+yVrmvr4T0fxX4CvNbedrVbCHVo XnadWKtGED5LhgRt65GK7K/+HXwk02ayt9Q8P6RbS6jcfZbRJX2mebYz+WgJ +ZtqO2BzhSe1AHd5FGRXDap8NvhRo1hc6tqvh3SLOys4nuLm4nby44Y1GWdm JwqgAkk8AClu/hr8KLDT5dVvfDuk21lBEZ5bmV9kUcYGS7MTgKBzk8YoA7jI oyK8o8G2n7OPxDe5j8CXfhLxC1lj7QumX8dyYsnALBHJAOOprqP+FRfDb/oT 7D8m/wAaAOvyKMiuPf4T/DSNC7eEdPCqMkkHAH51V0v4b/CfW9OtdY0jw7pN 5Y3sKT21xAxeOaNhlXVgcEEEEEUAddfabp2qxpFqen292kMqXEazRLIElRty OAQcMpAIPUEcVcGBwK5D/hUXw2/6E+w/Jv8AGj/hUXw2/wChPsPyb/GgDr8i jIrkP+FRfDb/AKE+w/Jv8aztM8NaD4V+JdhbeHdPjsIbvQr6SeOEkLIyXFoE YgnBIDsAf9o+tAHoNFFFABRRRQAUUUUAFFFFABSEZGKWigClpumado1nHp2l WNvZWsOfLgt4ljjTJJOFUADJJP1Jq7RRQBynw2/5AWof9jBrf/pxuK6uuU+G 3/IC1D/sYNb/APTjcV1dABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAU UUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAcn8Mf+Rb vP8AsYde/wDTrdU3wP8A8h/x5/2Maf8Apssad8Mf+RbvP+xh17/063VN8D/8 h/x5/wBjGn/pssaAOuorh/H/AMYPBHw11HS9I8TTau9/rEVxPZ2umaJealNJ FAYxK5S1ikZVUzRglgBlxWn4I8f+FfiLoj+IPCepG5tYbiS0nWWCS3mt50xv imilVZInGRlXUHBBxyKAPmz4N/CL4j/EX4U6Ro3iHxf4csvBy+JL3UhZW/h6 Uati31uadE+1vcFF3PGMusIO04HrVO0m8X6foGgeJ18VeKp9Q1z4p+JrO7E+ p3EkaWVsmuLbwpGW2xxjy4iAAMlU67Vx9gl0GCWAz0561Sh1ezk1W40hROJ7 eCK5ZmgcRFJGdV2ykbGbMbZUMWA2kgBlyAfDviHwt4pv/gpa6Vd+KvHOuy+O fgRqet6vBdavdzNNqtvDp7QGNQ2Y2P2iVGjTAkHDhjkn33xTF4C1X9lo2+jy +I/EnhK70+BGu9LupNRv1tzOvmXKtOXefyTudkO8ssZTaw+WvXJ/FGhW/iSy 8ITakiavqFncahbWvO6S3heJJXBxjAaeIdc/Nx0NawdCCQ64HB56UAfDuteP vG1zZeJdR+FPinR/iTqWl+FJlg8WaR4dksLzSITeWgmtZWh3xzSNB50qpHH5 iNb52fMBUXhLUPGviPw8uk2XxOvtQ8Maj478N6fHcaDrer3DRJI0ovYU1G7R JnRl8rcqMwjO7lSQB9ra/wCINI8MaLfeJNc1CKz03Tbd7q6uZD8kUSAlmP0A 6Dk1x3if49fDPwffx6ZrWrah9qa1ivZ4bTR7y6ayt5ASklyIYm+zKQCcy7fu n0NAHl3hlvHlv8VZPgpJqXiE6P4Hub3xT/a1xdTSNqGn3MRFhZyTsS0uyaa7 BDEnFlFn7wz538FvF02oyeEj8WviN4703xK2m+FW8KWNlcXJXU7eWyt2uZJI QrR3Ja4a4WdpQxijVWzHwx+zNM1XTNb0201jSr+3vLG/hS4tbiGQPHNG4DK6 sOCCCCCKt+YgO0uufTNAHxZ8AvFnxb1v436fH4p8ZRJrTXuqr4p0A3uq3EkN unmiENayQiztFVhAY5I2HmL3kLE19rUwui5y6jHXJqO4njt4nlkJIRS5Cgsx AGeAOSeOgoAnrlL3/kqej/8AYv6l/wClNlWr4a8R6N4u0Ky8SeHb9LzTtQiE 1vMgI3L0wQcFSCCCpAIIIIBBFZV7/wAlT0f/ALF/Uv8A0psqAOrooooAKKKK ACiiigAooooAKKKKACiiigDlPht/yAtQ/wCxg1v/ANONxXV1ynw2/wCQFqH/ AGMGt/8ApxuK6ugAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACi iigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAOT+GP/ACLd5/2M Ovf+nW6pvgf/AJD/AI8/7GNP/TZY074Y/wDIt3n/AGMOvf8Ap1uqb4H/AOQ/ 48/7GNP/AE2WNAHnfxh+Hnijx18afBMug+KPE3haGy8MeIopNb0RISYZ5JtN 8qKQzRSJhtjsFwGbyjg4BrwbxB8P/ia3wt0DRtd0DXXmsPFupH4iS3Gh3GvD XLz7OqW2pLaxywtc2rqsWEjJWI7F2Hysj7rooA+F7bwm2h6R4dsvjB4f8YeL tHtPCl6dAs00+SK80e+kvp3jlmto7iV7T/R/IjgnlkIiWFwzoxIrKHgHxR4o +GXhe8uNO8UHTF+G/gFnktNFfVra4li/tEzR3VmHRruJRNC0kUZMg3Rtg4r7 H8dfBz4ZfEu8tNQ8d+DNP1i6sY2hhlnDBhExy0TFSN8ZIyUbKn0rrra2gs7e K2tYUihhURxxooVUUDAAA6ADtQB8JaZ8LPEw/wCEO8Tj4Sy6d4qPhXxbo3h3 VIdIuylhqLXUL6TOyTNJLp8ZT7Q6JKwWEOUyuQtVfCvwo8YXPgTxrZ6fpHim ODUdL0iy1LTB4QudEW4vRqVu8km6S7mkubhIhOHuI1CsrZMj4GPv+igDxT49 6BpPhb4SaJo+j6bBYeGNK8TeHv7QtYE2wxaYmpQGUEdkAwW7bQc8Zri/itHf aR8S/EWs2mm/FTwrrF/DbJp+r+DLD+2LHXo0hARbu2khkihmjcvHlxGCmw+Y Rwv0jq+k6br2l3eiaxZQ3lhfwvbXVvMu5JonUqyMO4IJFS2lpBY2kNlbIVht 41ijUsWIVRgDJyTwOp5oA+Fvi18PPjDruoeHW8Z6BeWQbwVpdtpdr4d8Iy6r HpWtgy/axbmC7gj0+UFoCszfJtTbvAXa3p1t8ENX16++MXiC70u4XxqL/S5v DWtXcbRmSe00vTpo2j5KiNryAiTZkHaVJO0Y+pKTAoA+F/iH4J+JvjDStB+J fi3w1qlpp3jC/wBS1TX9Dm8MT69JYP5cMOlRS2MM0TnZBDJlgWCSzEkfxr6V 8E/hVq8HxC8Kaz8QdL1nVZ/DvgCzisNQ1m1MclvdG/vCEZRLKizpbvEnMjuF PLZZs/T2BUU8MdxC8EoJSRSjAEgkEYPI5FAHl37POG0HxZPZDGjz+Ndbk0nH 3fI+0ESFf9k3IuSMcYPHFdZe/wDJU9H/AOxf1L/0psq2tC0PSvDWj2egaFYQ 2WnWEKwW1vCuEijUYCisW9/5Kno//Yv6l/6U2VAHV0UUUAFFFFABRRRQAUUU UAFFFFABRRRQBynw2/5AWof9jBrf/pxuK6uuU+G3/IC1D/sYNb/9ONxXV0AF FFc18QNU1DR/Cl5f6XceRdh4IopSgfyzJMkZbaeCQGJGeM0AdLRXKf8ACK+M f+in6n/4LrL/AONUf8It4w/6Kdqf/gusv/jVAHV0Vyn/AAi3jD/op2p/+C6y /wDjVH/CLeMP+inan/4LrL/41QB1dFcp/wAIt4w/6Kdqf/gusv8A41R/wi3j D/op2p/+C6y/+NUAdXRXKf8ACLeMP+inan/4LrL/AONVk+Irfxn4XsrXWB4+ u75RqenWslvPY2qpJHPeQwuCUjDA7ZGwQeuKAPQaKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA5P4Y/8i3ef9jDr3/p 1uqb4H/5D/jz/sY0/wDTZY074Y/8i5ef9jBr3/p1uqb4H/5D/jz/ALGNP/TZ Y0AddRSHpXnT/FuMa++mR6Pby2iasNI85NSjNwZd4RnFvjdsDE5Oeik9KAPR qK5uP4heC5Y7uVPElkVsgGmbfwAW2gr/AHwW+Ubc5PHWqg+Jng9m86LXbN7O ONmmnEpyj71RUCbcsSzEccgjGPQA6+iuLt/iv4Mnv9QtW1aOOKwS3b7QQSkx mTeqx4GWO3BwOeenBq3e/EnwLYfZ/tXiazQ3cSTwAMWMiOWClQAc5KMPqMUA dTRXH638UPB2j6S2prrFtdF7Z7m2gjf5p9uQFHHyksNoz3468VrT695Gu6do BtmM1/bT3TNvGIUi2A545y0gFAG1RXI6P8SPDOqPDbzajDaXNw0xgglk+Z4k kkRZM4wAwjZgCegPXFTr8RPBUlnLep4ktDBDLHC75I+eQkJgYyQ2Dgjg4ODx QB09FYug+LvDnidJZNA1aC9EBAk8vPGc4PIHBweenB9K2qACuUvf+Sp6P/2L +pf+lNlXV1yl7/yVPR/+xf1L/wBKbKgDq6KKTI9aAFooooAKKKKACiiigAoo ooAKKKKAOU+G3/IC1D/sYNb/APTjcV1dcp8Nv+QFqH/Ywa3/AOnG4rq6ACuT +Kf/ACJN3/182X/pVFXWVyXxTYL4IvGYgAXFmST2/wBKioA8+/aD+K+vfDzx F4K0HS/H/gzwXaeIzqRu9Y8U25lt0NvHE0caD7RAAzGRurHpwKwfBH7T97Ja wadrmmf8Jteaj4pm8NaJqvg62VbLWPLsRePcIJ59qIgEsbESuu6I4JzXob+G Lf4j+NfD/wARblol0vw2NQg02GSESf2glzHGjTkk4RQYjswDuX5sgEVr+J/h 7B4i8V+CPEsd8LNfBd/dX0dskIKz+dZT2uzORsAE5bIB+7jvmgDzeD9qTS7U S6avg/xV4m1SMa3evHo2mQoI7Ow1OazkZhJcYypjH8WZMZVQW2ClD+1fZL40 8Sf2h4Q1ZfA+m+GdC1/TtcjW3IuzqJnEKhDP5n74rFHGvlg71k3lVKk9J4P/ AGebfwnruoa3H4oluTf6brmnGM2gUKNR1SW/L53HOwy+WB3Azx0rmL/9ka2v 9Cj8L3HjjfpMnhDQfDN5DLpEUrS3Gju0lldpvcoB5jsXhdJFcYGRzkA2E/aw 8Gy6WksXg3xTNrba9beHW0CGO0lvVurm3lngbck5gMTpC/ziUgEENja2Ol8f eN/F2lePfhh4X8P/AGGyh8W6jdpqovrZp5Ut7eze4aOPZIqpISm3ed4Hoa5n wt+zPHoY0a6vfEOk/btK8UW/iOQaN4ZtdJtJBDa3FulusMJyBi5Zy7vI2cgY BwNr4q6brj/Ff4Ra/p3h3UtSsNL1jUY9Qms41cWaXFhJCksuSMR73GSM4Hag BdJ+JPjvVvjl4g+GN34atNH0uy8NrqmlXs8gnnu5TcvAZWRGwkWVyqE7yOTt zisvwv4w8Q+PPgVovibxa9i+ry+I7S0unsYGhgdrfX0twyIzOVBEQOCzYJPN dzP4ISz+Jd18VxeTSyDw2NE/s+KAFmCXDz71bPLHdtC4/GvOPh3pOtaL+zxo Nn4h0W90i9k8Tw3b2V7GEnhSfxGJow6gkBtkikjJ60Ae9UUUUAFFFFABRRRQ AUUUUAFFFFABRRRQAUUUhoATOM8UHJFNyc5xx61h+MPGfhrwHocniHxXqiWF hCyo0zKzfMxwoAUEkknsKiUo04uUnZLqXTpzrSUKabk3ZJK7fob/ABjmk4I9 KrWF/aarZQajYzpNbXMazQyKcq6MMgj6g1a4xVJpq6JacXZ7i0UUUxBRRRQA nUUYFA6c1Bd3cFlbS3dw4SKBGkkbHRQMk/lSbSV2NJydkcz8Ms/8I5eH/qYN e/8ATrdUngc/8T/x5/2Maf8Apssa4j4NfGj4b+ILdvD2meJFe+v9Z1m6tY3g ljE8cmoXEqbGdQrExurbQcjnI4Ndt4HOdf8AHfOP+KjT/wBNljWdKtTrx5qc k15O5tiMLXwcuSvBxfZpp/idhXDWXws0awWxmhkAvoPtQurxYFWW7W4LGQMe o+ZgQcnG3HQmu5orUwPG2+CsvhbTIb7w7NNqWrWNxAbNv3cZiiQnjbIxRycj ILKOARgjBvaf8HtQk0cnUfErQ6rfRob5lto5o2cvLI/BxzvmLKw2lSikcDFe rUUAeX6t8GbfVAVl8UXLTJdR3cUksW9httkgYPtZS2RGGB4wSeuaiv8A4H+H bm3itrTWGhlie2e0bYG2pEkgIIVlLBmmlfIIwWHYVP4i1HVtP8VeJGt9I1Gb Ub7TLfT9FaG0keJjiQszSqNkYEknO4jhAawP7AsLXxRZWsPha9ubi1uLSyaO 50+U+RbwBVW6trxQFjXaodo8/McjAJOQDdt/hFpdjKljpniZ4LOVrRr2zMMb tdPBMZvvk7kDMzFgO/Prno9d8N3GuavFq2ieKW027S0eymaOGOfdCzBjtDH5 GyOG59wcV5p4SM0S6r4mk0e3l1ny9R1FI5PCl1HfCRi5jjF2/wApI3KoAHI4 HrW58Ofh5feF/FFomqW2mxvpulKtvc6bpv2YXZcBZftEm5i7qVBA4zu3fQA1 ZvhFYyTtbf8ACQ3cem/2c+nR2qRosixND5RBmHLIMlwpBw7E55xUGh/BrSdL S2uP7ceWWGdZzPHEFz5cUqRbdzNt2GVnB5G4DgU3X7KGDW/GWuavpusX9ium 2lgkMAldpy7O8iRBRkL80QbaMcHPQ1mWvhqG48I2tvpVvdRR6x4itZZrK1tJ 7S3tYg8ZkURuqt5YSJslgFZmJxyBQB3fgvwjL4ShvIp9Ye/e8n89j5Cwoh2g HbGvAJxuYjqxJwM11FIOlLQAVyl8cfFPR/8AsX9S/wDSmyrq65S+/wCSpaP/ ANi/qX/pTZUAdRkcEUmAOK8bur/4i/EHx14p0Lwz45Hhew8KzQWqCOxjnkup pIVlLyGTOEG8ABcE4PNep6BHrEWkWsOv3kF1qKRKLmeCMxxySY5ZVJOAfTNc tHEqvJqMXZXV9LOztprf8DtxWBeEhFzknJpNpXuk0mr6W1T6NmoKWiiuo4go oooAKKKKACiiigAooooA5T4bf8gLUP8AsYNb/wDTjcV1dcp8Nv8AkBah/wBj Brf/AKcbiuroAK85+JWmaj8R7O9+Heg3dvDGoim1S5niMkQAdXS1IBBzJt+f ByqHsWU10/inW7nTLeHT9IjSfWNRcw2UT/dU4+aV8dI0HzN68KOWFWfD2iQa BpiWELvLIWaW4nf79xMxy8jY7scn0HQcAUAYUdv8V4Y1ihm8HoiqFVVt7kBQ OgA3U7Z8W/8An68If9+Ln/4uuxrkdd8Q+KU8UReG/DGkaXcsLA300t/fSQAA ybFVQkT56EnOO3WgBmz4t/8AP14Q/wC/Fz/8XRs+Lf8Az9eEP+/Fz/8AF0/7 Z8Wf+he8Jf8Ag5uf/kWj7Z8Wf+he8Jf+Dm5/+RaAGbPi3/z9eEP+/Fz/APF0 uz4uH/l58If9+Ln/AOLp32z4s/8AQveEv/Bzc/8AyLR9s+LP/QveEv8Awc3P /wAi0AM2fFv/AJ+vCH/fi5/+Lqjq2gfEvxBDa6dq2oeGorSPULG8ma2t7jzC tvcxz7V3PjJ8rbk9M5rR+2fFn/oXvCX/AIObn/5Fo+2fFn/oXvCX/g5uf/kW gDrqK5H7Z8Wf+he8Jf8Ag5uf/kWpPC/iLxBqOtat4f8AEml6faXemRWsytY3 bzxyJN5mMl40IIMR7EcigDqqKKKACiiigAooooAKKKKACiiigAooooAYe+DX hvxu0Tx5478aaB4a8LaJZXGn6NG+rXb6p5iWU0x3RRRFkUlmUF3wPYntXuR4 4JpoXnpXLisOsVT9lJtJ2vbyOzL8dLL631imk5JO19ldWv6q+nmeYfs+2/in RPBkngrxfYSQXvhy6eyjlCuYZrf78TROwBdQrBM9fl5r1HI3fzpMcH5c5968 +sfDGneKfFni+bWbzWWNjqkFtbpb61eW0ccX2C1k2hIZVX78jtnGcsavD0fY U1TTvZW17dCMbiXjMRKu0k5O7S2u97fM9Forkf8AhVvhT/nt4h/8KbUv/j9H /CrfCn/PbxD/AOFNqX/x+tzmOuorkf8AhVvhT/nt4h/8KbUv/j9H/CrfCn/P bxD/AOFNqX/x+gDrCQKyvE8Mk/h3UoYUZ3e0mVVUZLEocACsf/hV3hT/AJ7+ If8AwptS/wDj9Hwuknn8EWIuLq4uGimu4Q88zSyFEuZUUM7ks2FUDJJPHWon Hmi49yqcvZyU10PkX4D6N4y8nwDp0Wn+KbmbQ9auZJtOvtLWLTbJfPuFllWf AcyruJKsThyy444+t/ApJ13xySMZ8RJkf9wyxp/wyVR4dvCAP+Rh17/063VJ 4HH/ABUHjz/sYo//AE2WNcWX4BYCDipN3tv5K3c9bOs4lnFVVJQUbX28230S 6s7CiiivQPHCiiigDjp/HDLp19qEGnCTytZGj2iebj7Q/mLGWJx8oDl+meEz WbZ/Eq+mutUe80O3gstMW6ecfbv9Lt1hDEPNAyjCvt+UqzfeX8L1t8O9Lt70 zTa3qE+nwXU95Dp8kkYgguJSxd9yqHJzI5AZjjdx0FUp/hXp9/b3FlqHi7V7 1xp8umW7ytAZLW3k27hkRguSEUZk3cZ9aAM21+MM7+Fb/wAT3J8LyR2sNuyQ 2etmZklmdURZyYgI1yxyecbTxxXQ+A/G9z4tm1GGS201ksPK23emXrXVrKX3 ZRZCifMu3kAEDcOaIPCME0EFvq3i651aOzvIL5VljtowpiztVvKjXK7iDzzl Rz1ra0HSLDSBerpdwXt7u6e6EQIKQu4BcJjoC2Wx6saAMX/hNNXvm1uLRvDD SS6VeRWSfarlYVYtGsjyOQG2IquvYt7Csr/haWom28P3S+HIca3dfZNv2w5d hN5ZaDCYkXaDJuYoCmMZPFauseALTUdPudJj8QX9i2oak2pzvF5TNOxGPLZX Qq0YAQYI52DOaYnguzuL+zudQ8X6lfxWMkN01pJJCIWnh+5KQqApg4O1Sq5A OOtAHajkUtMR1ZQyMGU9CDnNPoAK5O+/5Kno/H/Mv6l/6U2VdZXKX3/JU9H/ AOxf1L/0psqAMPxb8FvD3irW5vEcOsa5ot9expDfyaTftbC8RRhRIBkHAOMj BxxmtW71G3+H9roHhHw/4evtSa4V7e0gjuEykcKbmZ5JnGeMdySTXXjOM56V yPiX/koHg3/uI/8AogVjChTpTc4JJvc6KuLr1qap1JNpbJ9On4LbyJv+Eo8Y /wDRMtS/8GNn/wDHaP8AhKPGP/RMtS/8GNn/APHa6uitjnOU/wCEo8Y/9Ey1 L/wY2f8A8do/4Sjxj/0TLUv/AAY2f/x2ukubu1s4/Ou7mKBM43SOFGfTJpbe 6truPzbW4imTON0bhhn6igDmv+Eo8Y/9Ey1L/wAGNn/8do/4Sjxj/wBEy1L/ AMGNn/8AHa6ZJUkZlR1YodrAHO04zg+hwRS703iPeu4gkLnkj/JFAHMf8JR4 x/6JlqX/AIMbP/47R/wlHjH/AKJlqX/gxs//AI7XV0UAcp/wlHjH/omWpf8A gxs//jtaXhfxAnibRo9YWymsy8s8DwTFS8ckMrxOCVJU/NG2CDyMVs1ynwy/ 5FV/+wvq/wD6cbigA+G3/IC1D/sYNb/9ONxW5q+qWmi6fPqt/L5dvbIXc4yf YADkkngAckkCsL4bEDQtQyf+Zg1v/wBONxUdtnxpro1F1LaHo85FoP4b27Uk NN7xxnKp2L7m/hQ0AW/C+lXzzz+KNdh8vU9QQKkJOfsVsDlIBjjP8TkdWOMk KuOloooAK8j+KPxFt/hh4rHiKbQNT1uW5sdO0m1sNOMInnubvUVgiUGZ0jA3 yLkswAGa9TvLy1061kvb65it4IV3ySyuERFHUkngCvnn4y+H7j4463beHfDF pqjWsVz4evZ7yKd9PL2kGsxzXEttNuSTKRoxDpgk42EmgDvND+PehPqeoaJ8 RPDuqfDu/wBOsodRdPEdxZrFJayziBZEngnki/1pVCpYNl145rWi+NXw2IvL u68YaHaabbmDyNRm1a1FvdrLa/ag0ZEhIHlBn+cLlVLDK/NXn3xC/Zr0CPwL f6d4J0u/1fWdV1bQHvbnXNZuNQuJbG01W3uJYjLdyORGsaStsBAJ7EkVm6z8 EfFeq/HtPGVx4bs7jw6njTT9aDSSREC3g8O3Fn5nlk5yty8YAxn+IcDNAHol 7+0N8IbPxl4Q8Gf8Jxo89544tZ7vR5YdQgaG4SN0RQrb8sZHcqgUHcY3H8Nb 9n8V/hhqNvrN3YfETw5cweHN39ryRanC62GM5M5DYjxg/ex0NeA/8KR+JGk3 WjHTfC6CJtU8eWEktpd26SaXaazfiWzvVDMAyxom4xofMBYALnOOJ0T9mH4q S+AfE+h6p4Z1pdUh8CXHhOz/ALR8S2Nza38sjRErbxQwRlIP3OQZ2DDdjbyz EA+pPGfxg8N+Fvh4nxJ0eOXxXp1xeWdjZpok8ErXk1zdx2kaxu8ixf62QAku AMH0puu/Gfwd4f8AiR4X+FF493L4i8UmUwwQRb0tFS3ln3Tvnam5YJAoySxU kDAJHM/tOzaXofwktbi4mtdO0+y8V+FXkkkZYYYIl1yyJYk4VVA5JPAFbvxB 8I6z4j8f/C7xFo1vHNY+HdcvL/UpvNUbIJNKu4EYAnL5kmjGBng56A0AZ2l/ tA6bqHinT9Cm8A+LLDTtcv7rTNG1u7t4Es9Ru4EldokXzTNHuWCUo0kaKwTg 8jLfgp8QLT4n634k8X2ejahpAlhtrGaxv/KM9vPa3V9bSoxid0OJIXwVYgjF YHhe++LOv/Fc638UPgxqNnpem3dzHoN4NV017HSrfY6/bHVbgzSTyp8pIjHl q5UDBdmzf2PLyz1LTvFmoaddw3Vpc6xqU0E8MgeOWNtd1cqysOGUgggjgg0A fRlFFFABRRRQAV5/aaGvinxX4qbU9Z1yNNOv7e2torPV7m1jjjNlbyEbInUE l5HOSM8+wr0CvPLLxTofhXxL4nk129+zDU/E+n6Xany2bzLmextViT5QcZPG TwO5oA2P+FcaP/0G/FX/AIUt/wD/AB2j/hXGj/8AQb8Vf+FLf/8Ax2l134l+ CfDOpajpWv6/DYT6TpC67emZWVIbEyNGJS+NvLow2g7uOnIrlof2k/hI+ma1 qt1rWpadHoOmy6zdw6lol7ZXDWMWN88UM0SyTICQMxq3JA7igDqP+FcaP/0G /FX/AIUt/wD/AB2j/hXGj/8AQb8Vf+FLf/8Ax2uZsf2ivh3dw395NaeMNPtN L0+51S7utS8H6rZQRW8EZkkYyTW6rkIpIXOT0AJqx4R+Pnw58aa7ZeG9Om12 y1DU43ksYtY8PX+mC8CLvYQvdQxrIwT5iqknaCcYFAG9/wAK40f/AKDfir/w pb//AOO0f8K40f8A6Dfir/wpb/8A+O1Y8dePfCPw08MXnjPx1r1ro+j2C7p7 q4bAGeigdWYngKAST0Fc/wCNvjv8Mvh7qw0TxTrk9vcrbx3dyYdPubiKxt3Y qk11LFGyW0ZKthpSo+U+lAGx/wAK40f/AKDfir/wpb//AOO1D8NXnTTdXsp7 67u0sdbvbWB7q4eeQRJJ8ql3JZsZ7kmqF/8AHD4aaV4xi8DXmvyLqck8FqZF sZ3tIridQ0MEl0qGCOWQMpVGcM25cDkV5LP+1H4a+F/xTt/hFqPgrxhqF/4p 8S6kE1Cx0eaWyhUBnwJFUmaT5MFIwSM5OKAPpquT8H/8jR46/wCw3b/+myzr hvil+014X+GHgDWfHt14N8a30OjQC4ktx4dvbcyLvVSBJLEEU/NxuIBxjPNa XwJ8ead8TbHxN430nStZ0211XVbeaO11ewezuowdMs+HicZHseQRyCRQB6nR XlfiX4oeObnxpqngX4UeA9N1688Ow28usXmraw2n2kEk6l4raMpDM8kxjw5G 1VVXTJ+bjE1L9oi/0hJ08ReCH8OXFt4Mv/FN5Fq1yw+ySWt0lu0LmGNy0ZLl xKgJK4IXngA9vorgbf42fDi58aD4fxa9KdWa4ezRjZTi0kukUs9ul0U8h5lA YmIOXG05HBrlJP2s/hBdeG9T1/w3q1/q7Weg3HiC1gi0m8T+0LeFQXFuxixK VLIHCbjHu+YDBoA9prkfhV/yJFr/ANfd/wD+lk1O+GPjyy+JvgPQ/HlhYX1l DrNnHci3vLWa3kjYj5l2yojlQc4baAwwwyCDXh3gj9qnwtoPj7TfgTN4I8aS 6hJHqt++pRaHcPaFY7uU7Ydilp+vLINq9z2oA9x+GX/It3n/AGMOvf8Ap1uq b4H/AOQ/48/7GNP/AE2WNeOan+034X+EHwi17xzf+DvGWpQ6br2rSPbw6Bdx F1l1idcCSSMRhh5g+VmHI28GvQfgZ4ysviDYeJ/GOm6Zq2n22q63FPHbapZP aXUYOmWPEkTgMp/mMEZBoA9QooooAKKKKAPIo/7R1RLzwx/YupG+vfEMuoam HtXSIWkcu6MCZgEbekUKgKSfm5xg1gRwiwGtatofhrU5boabf3RuptLngvbW 6l4FvI+MXYzIdu0HaIweeDXvlFAHguneGvtPhCbw/wCH7HSjPqNxY6ZJcQ+F bixIhDh5TP5hzMhWM5wQOcE5YV3Hws8MT6Bc67NfWdnZXclyts9vp9j9ls9k YJjljXJ3F1cFmz1G3+GvQqKAPHNd0e/1z4u215Pp15/oV7boq/Y38sWkUbSf aFuiNqZlfY0anLBcHisjxN4NtJ1XX7fw9Lo+n6jqcltdf2ZpIecWUSuY98QQ 7/NnVWO5SMbAeM171RQBzngCyvdP8GaNaahYx2d0lsvnQRoEWNzyRtHC9eg4 B4HFdHRRQAnfkV4Z+0T8Y5PgZf2vj1fh94m8YG08P6n/AKDoNr50q/6RZnfJ z8kYxy+Dj0r19vEugR3v9mtrViLoNsMBuEEm7025zmse9wfilo/P/Mv6kf8A yZsqlSUtmOUJQtzK1znvDPxpm1/w5pWvN8LvG0P9pWUF35aaarqnmRh8Bt43 AZ64GfQV5x8Iv2ipvjt8RrG3f4V+LfCv/COajrFh9r1W0C2l95a7MwS8bm+X LLj5emTX0mqqgwowK5DxGoT4geDAvT/iY/8AogVQjsB0pao6tq+laBps+r65 qdrp1haoZJ7q6mWKKJR3Z2IAHuTWZ4S8eeCfH9lJqfgfxfoviC0ify5J9Lvo rpEb+6WjYgH2NAHkP7XukSa/pPw10eLwnovidrrx9ZoNI1mXy7K8/wBBvjsm bypcKMbv9W3KjjuOE1DwJ8SfhLY3GteGoPDfwu/4TXxR4V8PRaT4S23lrZxN etFc3IE9vHF50qTheIgAIkJ3Gvq6806w1B7Zr6xguWs5hc25liVzDKFKiRMj 5WAZhkc4Yjuag11dBj057/xKth9h0wjUHnvQnlWxh+cTln4Qpt3b+NuM5FAH zHaa38R9Q+Lmo/DPQPiDPoUN54u1OyvdTttKsmvLiO30DSpUclothlMkrkuy ng7cbVULT+Fmq+MPGvxu+GfijxV8T9RS7Pg/xLZT2kUVnFb6lJZazb2xJQxF g0qqkjhGBBjG3au4N9S2uieHHuxrlnpGm/aZna6W8jt4/Md3jVGk3gZJaNI1 LZyVVR0AqBvBng959OuX8K6O0ujzS3GnObGItZyyEmR4TtzGzFiWK4Jyc5zQ Bu0Vjw+K/DN14kufB1v4h02XXbK2S8udMS6RrqGBzhZXiB3KhPAYjBqmvxB8 CPoOo+LI/GWiNoukSzwahqIv4jbWkkLbZUlk3bUKNwwJGD1oA6SuU+GX/Iqv /wBhfV//AE43FdBYX1nqtjb6lp93FdWl3Ek8E8Lh45Y2AZXVhwykEEEcEGuG 8M662heCM2tuLnUbzWtWtrC1zjzpzqFyQCeygAszdlVjQBneGry51qyvfBuk zPE8mu61LqdzGSGtrU6lcjapHSSTBC+gDN1C59MsrO00+1hsrKBILe3jWKKN BhURRgKB2AFcT8GtKOk+F9QE8yXF7ceIdalvblYwhuJv7QnUuQOnCgAdgAOa 177xvC13JpPhixk1zUYmKSJbsFt7dvSac/KhHdRuf0U0AdMzqilmYAAZJPQC uTk8azaxI9p4F05dXdCUe/kcx2ETDg/vcEykf3Yw3PBK9aavgy719lufHmoL qS9Rpdupj09Dnjch+ac+8hK9wi11cUUUEaxRIqIihVVRgKB0AFAHM2vgpbu4 i1PxffHXL2J98SSpstLduxigyVyOzOWf/aHSqGu3Wp6H49j1mHwvq+qWc2kf ZN9gkb+XIs27DB3UjIPBGehruqrXd7Z2ELXF7dw28SjLPLIEUD1JPFAHNf8A Cf3n/ROfF3/gLB/8eo/4T+8/6Jz4u/8AAWD/AOPU6T4n+BgxitfEEOpTDrFp iPeuPqsAcj8a5zwB4Z1LxP4E8OeJdR+IHiz7Xq2kWd9Psuo418yWFXbC+X8o yx47UAdD/wAJ/ef9E58Xf+AsH/x6j/hP7z/onPi7/wABYP8A49Tf+Fezf9FB 8X/+B8f/AMbpf+FfTf8ARQfF3/gfH/8AG6AKuo+LY9XtXsNU+FviW7tpMb4b iwtpI2wcjKtKQcEA/hVhfHt0ihF+HHi0AcAC0gwP/I1O/wCFezf9FA8X/wDg fH/8bo/4V7N/0UDxf/4Hx/8AxugBr+PLqRSj/DjxaysMEG0gII/7/VR+H9lI niTX9StvCN14e0ya2sLe0t54IoctGZ2kKpGzADMq+mSTV/8A4V7N/wBFB8X/ APgfH/8AG6P+Fezf9FB8X/8AgfH/APG6AOworzXxp4R1HQ/B+u63p/xB8WC6 0/Tbq7gL3sbKJI4mZcgx8jIHFehWMjyWVvLIcs8SMx9SQKALFFFFABXg3xQ0 rWr5dd1nRNFvNXk8M+PdB16exslD3M9vb21m0oiUkB3CFmC5y23A5IFe81yf hH/ka/G//YXtv/Tda0AeEeKLbWPivrvjfx9Y/CHxFqnh2Xwlp3h3+ytXgl0a 91Qpfy3Fy1skuyVHjjcFGbYGkAAbHzVw/jXTPiH4r8C+PtE8H2nxQ8ReH5PA msWwHjPQFi1K01BxEIbbT5DClzcF1Em8ESISkWHJ4r7awKWgD5K1C5XXvh38 QfDWga18dvEGp6r4J1qztLDxT4ZubezeZrR9oRzZQjzSQFUb+dxABJFb3hn4 X+MfBPxr8D6p4o1vxn448NzaTImlyalMsg8M6usDLI8qQxxqY5oHeNZHB8tl K5/eCvpeigDyb9qLwYnjj4E+NLC38Mrrerx6FfnSIFtRPOt09u6KYRgkSEMV BXn5iO9cj8b/ABtbjXpvhRffDvxe2ga7paf8JNruj+F72+N5bMrp9hie2hf5 yuQ7uRsRyEyzZT6HpMCgD5r+Nb+IfEupaV4P8O+B/GNvqOh6vpepeH1gtDLo OqRo8D+ZqEhTEPkFXHluyuGjVkDkgD2D4eW8MsXiBpY0fy/EuoOm5Qdrb+o9 DXaYFch8Of8AU+Iv+xj1D/0YKAOquLeG5QxTxpIhwSrqGBwcjg+9cx4P48Ue Ov8AsN2//pss662uT8H/API0eOv+w3b/APpss6AOP1/wN8U/DXj3XPG/wjuf C11B4sjtTq+m+IJLiBY7qCIQpdQywI5OYVjRomUA+WpDryDyPjb9nn4ieMtN 1VdV8cadqWq6t4A1TwtNeXELQqb27u45w6xop2wIqFAMs+AucnJr6JwKMCgD 5j8Kfsoaj4d+K6eJJYvDt5oVt4kvPE9vfT3+pvqQlnlkmEItjKLRNkkrYmAJ KgDYCS1aunfs3+JLbwV8OPCdzrumLJ4P8Gax4ZvpoxIwkmvLSGFZYgVGVVo2 J3bTgivofAowKAOQ+FOi+KfDfw78P+G/GS6UNW0iwisJW0uaSW3kWFQiOpkR GyyKpII4JIBIGSz4WQQyeDLKZ4kZ47vUNjFQSubuYHB7V2dcj8Kv+RItf+vu /wD/AEsmoAZ8OYIbjw1eRzxK6f8ACRa6drqCMjVrog8+9O8Df8h/x2P+piT/ ANNljT/hj/yLd5/2MOvf+nW6pvgf/kP+PP8AsY0/9NljQBF8SPGdx4R0/T5L Oe1hn1C9Ft5tzbSzxxII3d3KREOcBMcdCwzWBp/xosNN0iO88XbWmuJZXtHs oGiW5s0C/wClCOZgypliAMkttyoOa9Bu9GsrzVLPV7hXaewWVIBu+UeYAGOP XC4H1PrXN3nwn8JXf2LzIrtBYI8MYjuCuYGcv5J/2AScAYIHANAFfUPjB4Xs wZo4dSntDvSK+htd1s8ixNK6BiQcqiknoMgjOQQKeqfFqPT7C7htND1K/wBU sWtbeVY7Xy4pJ5njTC7nyOZAQCRnBwTgkQx/CI3niG+udYvYzorvcva2FtJK qq87KXYqxKodoYHb97zG+7nFas3wz8JWTy6rc3l9EIZIrkSy3zBLVIZfOCqW 4VA+SQe3cUAV1+NvgdpL9BPclbCCacuERhMIjiRUAbO4E4+YAHsSOajsPjr4 FvLiWB5L218oTgNPEo3vFnegVWL7vlOAVGeg54pPD3gf4Yaml4nhzVYdRty6 F4rXUFnSBfMEnlgKTtUso4POMgcVbtvhd4FuBqMlp58sV68yMIrslLeQybpP Lx91w4J7lSCBjkUAWdD8ctrE2v3E+mXGn2OiQRGRbuLy5hKUaRwwyVwE8sjH 97n0HJeHvi/rTQW+r6/BbXOmPZie6+w6XdQyWcrlBHEWlJWVmZ9uFx0z0rt9 P8FaHHoWq6JFeXd1BrLS/bZ5LkyTSMyCNsv64UD2xitbVdD07VrW3s7tGENr cQ3KKjbRviYMmfUAgHHtQBx0fxf0WOH7Vdadqjq5nmCRWQDW8EU4gZpfnI/1 gbGOoHAyOaNj8efDglnh1yzu7GSK8liAIQhLdZDGszfPkhmVuFBIweMDJ6Gx +H3hM2jwWjSzRMkNtIwn3ZEE7y7SR3MrMW9elY958Pvhn4VuLPU9X1UWAR9q m91FYo5yrtIqtvI3bS7YAPTg5FAGhdfFnQbZ8JpOs3Ef26TTklhtAySTRlg4 QlhuxsPTk9ACcgdruDKGAIB554rz6+8LfDaez0i2ufESR28u77Mq6qqLqAeb zSDg4lzJ83HOT1ruL7UbDTLf7Tqd9b2sO4KZZ5VjXJOAMk4yTQB8leIV+D51 H4tt4z/sv/hJxq039kbiPt2/7LF5Xk7fn/1nTHfNe7+DzrP/AAkHg0+Ig39p f8Ihd/a89fN82x35992a7T/hHtCe8/tJtHsmui27zzAnmE+u7Gc1kXgx8UtH /wCxf1L/ANKbKvOweCeGnKba1vsrdW9e71PYzLNI46jCnFS0tu72skrJW0Tt dnXVyHiX/koPgz/uI/8AogV19ch4l/5KD4M/7iP/AKIFeieOcd+0/BoFz8Ob eLxRPrFjp661YTtq2nWSXi6TLFJ5sV1cwOrCW3WREV1KsMPk4ALL86a/8RfG KaR4t1rwHr3hPxOVOhWeqfEDw3Z3OkQf2c91KJ4J3h+0APEuGM8AZo45WyFI Br7mlkjiiaSZlWNQSzMcADuSfSuM0b4v/DPX9c0bwxpHii1l1LxBpba3pdoY 3je8sQxUzxhlGVyMj1GGGQQaAPmf4e3njnxlF4A8P6j8T9QvvD2pePdRggu/ D+v6jL5+nxaJcTfZ21CaKGa6iFzGSJBu7LvYqaueONf+KkFh8RPhxHr/AIgt x8MNA8S+Ijq4nlEuowXNlMdIiMvWQxmS43ZJO+zjJ6g19PeFPHvgzxtea5Y+ E9dttSm8Mak+kaosAP8Aol4qqzQkkAFgrrnGcZx1zXSFVOcqOeDx1oA+Wfhh 4sg1H4kCHxp8UfFtp46XWmtbHwzFNK9nPpAtVMDva7TH5TpiVro4YSkpvGNl cp+zd43+LXiT4vaSvibxxZvqVwmonxf4fOr6leTWrLuEatZyWq22n+XKEVCk oEiE4MpIevtHYu7dtGcYzikCKCWCgE9TjrQB80eLfF2p+B/HXx61zw3aC58R T2PhnTNDhA5l1G5hmhtlJ7L5siFj2VSe1cp8NPDvi74PQeL/AIZ+LfBVnoGl eKPBkl9py2ur/wBpR3OpWNmIL2V38mLZJNGbeTGDkpI2fT6Z034c6JpHxC1r 4k2d3qQ1HxBaWtnfWzXGbRhb5EUgixxIAzDdnoTTfiKfDOp6KPBHibWrvSk8 W+ZotvPayNFK8kkbExpKFKxuyK2M4z0GTxQBlfBW+tdN+AXgLUL6dIre38Ia VLLI5wERbKMkn8K5T4XeIrEWU2szwXera3c6hqq6dpFpFmaxtX1Cdv324hYX cgF2kZeFVRnbzu+O/g3fa98OdB+HPgvxzf8Ahay0AWkSPFEk73NvbRhI4ZGb BA+VGLLg5UVwnws8EyeHfCJtfEnhTxDrNoup6mHuNL1qSSJ2F7OrNJahomJO OcLIT3oA6PwkYZtC1C4+I/jCw0fTm17Wf+JVDfi3Qk6jcZEs5KvLzn5VCKRw Q1djYfEDwRZWkeneFLG+v7eFdkUWjaRNJAoHYSIgiH/fQrlfgrP8KrezvbPR LXRrDVTrmsYtpbZbW92f2hPtzHIqy4xgcj2r2EAdhQByK+KPGeoL/wASn4cX Nvn7r6vqMFsp98Qmdh+K59qaLL4p6jkXGueHtGQ/w2ljLeSAe0kjoo/GM/Su xooA5H/hBLq8H/E98d+JdQz1SO6SyQfT7KkbY+rH61LafDHwFaSLcf8ACL2V 1Op3Ce+U3c2fXzJizZ9811NFAEUEENtGIoIkjReiooAH4Cvn/wCIPjXWfh/+ yl4V8R6F4juNAuPs/hWyl1K3sku5ba3uLizgndIXjkDsIpHwNjc4wCa+ha8v 8O+B9L8ffBLwJomr3F1DBbWXh7VkNuwVjLZtbXManII2l4VDcZwTgg80AeQ6 R8ffFvg1PEniO11zxL8UvCWl6XaSC81TQE0OddUnv4baO0hk+zwJKGSZnP7v 5DGoLfOMdXqX7Qnirw540uPCl54Bu9R1y91HR9Ih0iHVbf7PaXN3YXt0Ss5h RmQfZMOzZ4OVHG1vXPiD4G0z4i+FbrwjrVxdwWd1Pazu9qyrIGguI50wWBGC 0Sg8dCenWue1L4HeFtS+IafEqfUNTXUk1Wx1YRJIgh821srq0jXG3O0x3khP OdwXBAyCAeYXP7SHxE1Dxl4Ct9P8C2em6Vc3/iDT/Flvd6ujPazaZlZvKdYW 8xECmVWGwyZCkJzVDQv28/BmvaV4h1Sy0Gzuhpvhe+8WabBYeILa8mura1VW aG5SMZs52DoQp3ryw3ZUivTr39nfwxPqFhqdr4g1uzuLHxDquvkxNAyz/wBo km7tZFeJgYXB28AOB0cHms2y/Zg8P23hXWvA958QvG2o6DqWhT+G7Kwur6Ix aVYyrtKwhYl8xlUKqvP5rKq4BwTkAn+L/jf4g6b8CJPFVlGPB3iO81DSLNfJ kh1BrJLvVLa2ZgZI/Ld/JmY4KEBjjnGThfF3xR8UPht4s8P62PHtzLouo61p 2mjTR4ejOnR2bSRR3U9/fbS0Ep3u0ZVkTdsTY2SR2X7QfhXxJ4r+El7oXg3S Rqmqw3+j31vZtcRweetpqVtcOnmOQikpC+CSBnFQ+IvgTpXjHWrrWdS8UeJr HTdbktbvW/DcN1C1hfTwhNvmbo2kUYjRWWKRFcLyDk5AOftvEPirUY/2gPDe v+IJdUs/D0rxaUJbeGJrW3uNGhuTDmNF3hXmYBny2MZJr2rTP+Qbaf8AXCP/ ANBFeLw+GvFWmRfH7xL4h0Maba+JJJJ9KBuY5muLa30eG184hCdm5oWIVsMA RkV7Rpn/ACDbT/rhH/6CKALVFFFABXG3HhDxPBrmq6t4e8YQ6fFq80dxNBNp i3G2RIY4sq29eCsSnGOua7KigDkP7A+JH/RRLH/wQr/8eo/sD4kf9FEsf/BC v/x6uvooA5D+wPiR/wBFEsf/AAQr/wDHqP7A+JH/AEUSx/8ABCv/AMerr6KA OQ/sD4kf9FEsf/BCv/x6j+wPiR/0USx/8EK//Hq6+igDkP7A+JH/AEUSx/8A BCv/AMeq/wCDvDdx4Y0+5trzVTqN1eXs99PP5AhBeVtxAQE4A4HU10FFABXn 2heKPDei+LvG9rrPiDTLCZtYt5FjubuOJip02zGQGIOMg8+xr0Gqs2nafcv5 lzYW8r4xueJWP5kUAZX/AAsDwH/0Oug/+DKH/wCKo/4WB4D/AOh10H/wZQ// ABVaX9j6P/0CrP8A78L/AIUf2Po//QKs/wDvwv8AhQBm/wDCwPAf/Q66D/4M of8A4qj/AIWB4D/6HXQf/BlD/wDFVpf2Po//AECrP/vwv+FH9j6P/wBAqz/7 8L/hQBmN8QPAmOPGug/+DKH/AOKr568CeA/2lNW8e6R428N/HDRofhs8OqrF on9kB2jme5k2SEq4+0A8kMXXbnhT1r6Y/sfR/wDoFWf/AH4X/CrMUccKLFEi oijCqowAPYUAeQfDnQPivJ4fuzb/ABI0aNf7e1wEHw4W+Yapchjn7QOpycds 45xmm+DNA+K76542EXxH0hWXX0EhPh0kO39nWRyP9I4GCBjnpnviu5+GP/It 3n/Yw69/6dbqm+B/+Q/48/7GNP8A02WNAFT/AIR34u/9FN0X/wAJo/8AyTR/ wjvxd/6Kbov/AITR/wDkmu4yB1NFAHD/APCO/F3/AKKbov8A4TR/+Sa53x54 P+M2reGLnRrb4h6VN/aTxWcoi8N4KQySKsj5NweFQsenavW657x5rtx4a8I6 prdkge6t4CLZShfdOxCRrtHLZdlGByelAHkerfCf4yWes2t7pfxaRpb3EV5c 2vhuOAxW0KSOIwI5VGXdgORn0IxWbaeC/wBpJobOWX4mTwyW/wDZ6eVHpB2u 8jtLcvJ+/wDmCK2znqQBjgGu80r4h+KNOvBHrlhfataXskVrYOmivpsz3LCR nQRzSZKKiZLnaB71asPi7btDavJo2pXa3At7h5Yo4kS3iubh4oA2ZPmPyg/L nIOcDoADxjwl4I/al02/0qxtvHstjYRGK4KXGhtIgDHfcCQ/aQCdxdQrAnG1 lwSa9M8LeDPjjH4XN3rvxSgmvtQgM9xbT6GzNAWBbyUxcDbjdt454HPFT+Hv j/pF5LZ6frmmTWt/dzpG6LNBiJZnxAdvmb3yrISVBwDk4Fdlo3iy58V+H7rW NE0ye0BEi2Mt4qlLhgWUOqq24rlQRnGQRj1oA474f+Bvi9oXg3StOf4gaNaS LB50sDeHCxjkkJkdSftHZmNU9d+H3xk8QeMbKSX4mabb22m2ErR3K+F43RpZ nUFNskzAkLHnPUbh613fw413WfEXh99R1sJ56XlxbqRAYHKxuUPmRbnCOGVg QGPQHvgZvxB8Wa1o+t6RoeiXEsDXcFxdXEsWkS6iyohjVR5cRBG5nPzE4G33 oA8kvPhd8WNGv5tJ0/VbXU2MK2cUk3hqKWyvYHkMrtOxuAYGWSWU4QDtgHgD X+JXw8+Pvi43Gm2Hjnw+9hpdpI0a3Hh2RftU8kbL+6C3B+ZFOAx4DP0OK6mT xp8Q4rWym1GTTdKUQ/vp57B5ImuDIwSK42SE2e6MxNlg4BkIzwM6XxZ+JT+B 7W3tNPv9Ot9UnhmvcXbZXyYlyVUZGWdtqL/wI9sUAS6doHxiksLWWf4j6PDK 8KM8beGjlGKjIP8ApPUHisC88P8AxW/4WVpKH4k6P5x0LUCr/wDCOHAX7RZ5 GPtHc45z2969ctpluLeK4QgiVFcEdwRmuavf+Sp6P/2L+pf+lNlQBR/4R34u /wDRTdF/8Jo//JNeQ/CHwJ+0N4O+Itk/xu+LWneLbS+1HWJtFtLfTvLewt2X KK05IZxtIGwg7cYDkCvpeuQ8S/8AJQfBn/cR/wDRAoAwv2kl1pvgF8QE8P8A mm+Ph69CeVneV8pt4XHOdm7GOc14x8aNI1vTPiTpXxj+HHhG/wBZt/BfhHS7 7So9NtmkW7gN3cRTW0O0EMxtbguEGT8qnHQ19XyKkiGN1DKwIIIyCO4rjodb 8B/DjQ5PDWiSWyReHLSJv7ItbpGntrd5NifJI4KJk4XcQMDA6AUAfKVh8P8A xb8Pfhp470TVvAuqa02qeLdButTK297JBOZdIs3vbqSG0xNdwC681WijyC3B 4VhT/hV8MvEvie38CeDfH3hbXj4dsfG3ifzrKWyvLC2TS5NOZrVGjeR2S2Z3 wsbyEZOw8gqPsa38WeFrrVP7DtfEulTaifMIs47yNpyI3KSHywd3yuCrccEE HmptY8Q6B4eiiuNf1zT9MinlWGJ7y5SBZJG6IpcgFj2A5oA+GPHXhXxtP8Ov D/gm7+HfiDUHsrbxNa6PdXun6pqX2Z49WuEsIYoYJYxFN9mWFo7qdwBGF2nk 5qfFZLqb4Y+LtX+KegeMtT8V/wDCv9J/4Rm/torsjSpP7LQ3sc7oQtrMbkyv KJtrSxvGo3Y2j7ZtviX4Sn1fxTpFzqAsD4Pkto9Uub10ht4/PgWdCJGbGNjj JOMHiue1n4W/A3x74q03xzqmh6Jqur3saXFpcJdkpqCW5BSRo0cR3Ij3KQzq +3K4xxQB84674M+KGoftFS6nfXWtW2pjxPp9xod9Z+Fby6C6KqQl4xqH2yO0 hgKiZJYnj3EszBZGKmukfwPF4V/Z78T6tJo1zZeMdf8AHdzNZy3XmfaJrweJ Zf7NKhzkIFaNlC4GxiehNfSup+OfB2jabDq2o+JtKhtbkstrI15EBcuucpES 2Hf5SNq5ORWN4d8RfDb4u2nhrxNZXFrf3EFraeItPtJ5QLmyW6tt0MskAY7W MUpwWBxk4PegDuh0rlfhl/yKr/8AYX1f/wBONxXV1ynwy/5FV/8AsL6v/wCn G4oAoeDNE0bX/DGoWOuaVZ6hbHxDrZMV1Asqf8hG47MCKtf8K+j09P8AilPE ms6GR92KO4+02308m4Dqo9k2fWpfht/yAtQ/7GDW/wD043FdXQBx4ufiVo5x e6bpfiGBf+WllI1nckf9cpC0bH/tqo9qcnxL8NwOtv4hF74dnY7dmrW5gQn0 WbmFj/uua66mPGkiGN1VlYYKkZBFADLe4guokntpo5Y5AGV0YMrD1BHWpq5O f4a+FjK13pFtPoV05LNPpE7WhZvVkQ+W/wDwNWpi6d8RtFBOn+INO8QQryId Ug+yzn63EAKf+QPxoA649K4HQfBHjrw7oeneH9M+IVr9j0y1is7fzdEVn8qN Ai7j5oycKMnA57VoL49nsPk8V+EtZ0nHW4ih+22318yDcyj3dErb0fxJoPiG Ez6FrNnqCLwxtp1k2n0bB4PsaAOHl1zUYZXhn+OfhWKSNijo1jArKwOCCDcc Gk/4SG8/6L14S/8AAO3/APkitD4W6foy/DfQ7i7sbMf6IGeSSJO7Hkkiupgs /DtyGa2stOmC9THGjY/IUAcN/wAJDef9F68Jf+Adv/8AJFH/AAkN5/0Xrwl/ 4B2//wAkV3n9l6IXMY0yyLKASvkpkA9OMe1ObSNFUhW0uzBbgfuE5/SgDgP+ Ehu/+i9eEv8AwDt//kil/wCEhvP+i9eEv/AO3/8AkivQP7H0f/oFWf8A34X/ AApkul6JDGZZdNsUVRlmaFAAPc4oA8z1q7fXtHvtDv8A49eFxbajbS2kxjtb dW2SIVbBM5wcE44ruIPHPgK3t4rceN9CIjQICdRh5wMf3q0WsfD6mMNYaePN +5mJPn+nHNZviTT9Cl8O60sdhYM8VjOGCxISh8tuvHFAHRI6SoJEYMrDIIPB FFYvgj/kS/D/AP2CrT/0UtFAG7RRRQAUUUUAFFFFABRRRQAUUUUAFcXL4m8b X+u6zpfhnw1olzbaPcx2kk1/rE1vJJI1vFMSES2kG0CZRndnIPArtK5Pwf8A 8jR46/7Ddv8A+myzoAb/AGh8Wv8AoUfCX/hRXP8A8hUf2h8Wv+hR8Jf+FFc/ /IVddRQByP8AaHxa/wChR8Jf+FFc/wDyFR/aHxa/6FHwl/4UVz/8hV11FAHI f2h8Wv8AoUvCP/hRXP8A8hVo+Ddfn8UeHLXWrqyjtJ5mljlhjmMqI8crRttc qpYZQkEqDg9BW6elfL/gz4j/ALSdj8Q9K8FaL8ENOuvAEkerTDxA2sYaedbq UqjYQ/Z+SflZW3Y4YUAe6/DH/kW7z/sYde/9Ot1TPA//ACH/AB5/2MSf+myx ri/hz4h+KqeH7oQ/DPS5FOva4S3/AAkQXDHVLksMfZ+xyM98Z4zim+DPEPxU XXfG7R/DLS3ZtfQyA+IwNjf2dZDAP2fngA54647UAU/2j/EfiHRrjwfYaLqf iG0i1LUZorpdCRHvJkW3kcKiuCDhgCfYGun+CLahP4cu7vUL/wAYTvJdFQvi eKKK4QBV+4sYA2HPU85zXP8AxB8KeNfiQmnr4g+GUcMmmTtNbTWPjF7eRHZS pIdIAehI/GrHgbRviL4Asrix0n4fNdx3MvnM2o+NZLp1OAMK0kBKjjoK8uGH rRxkqstYvbXbRLb1Pcq4vCzyynh4aVFvotdW9732a+49irK8QQaPNprT680a WVi6XzvJIUSMwsJA7HI4BUHnjjmub/4SX4tf9Eu0n/wph/8AI9c748vPjL4i 8L3Wg2nwy06I6i0VtJJH4lQtHC0i+Y3zW+PubvX6HpXqHhnZ2Gr+B/HVzHPp Wr2epzaZuZfs9xkxeYhQsQD3XcAfrim2Pg/wZNbFLCzSSGOaBTsmcgPagxxq ef4MHj156815Zqnh34xtf2VyPB9zfSvKPtt03i2OKVraNJCtupitowqtI4Jw MnHJHBrLt9K/aDMVkbrwLKZrRNOij2+MmRdyyNNcyMAnz5D+X82cY7jBoA9d 0T4feBbR7fUNFt5CtuBChjv5niJjygLLvKsyY2gkEjaBngVo6l4e8LWvhQaP qKLa6PpkCMG894zbpCMq4kBDKVxndnPvXzr4Y8N/tL6VqGmQw+A/sNlbtFch W8TmRYiCGmjb5sEyNvHMbgKw5BzXaWtl8Y4PAc2na38LP7ZvNRCzahEfGe2V svvMceYtqAZ24DAEDrQB6z4MuPCkmhpH4Oure402B3QPDIZAZCdzZYklmJbJ JJJJpmu6t4Q8Laimv+IdStNPuLqIWcctzNt3opL7VBOOpycDPTPQVwvgi++N OjaTNBefDS2aOa6kntYLvxb50trCwGImkMLFiCGP3jjdjPFU/Edv8a/EPiuw 1GHwTFpMOm2U0aTWfiSAtJJM6bhmS1bACxD+EfeGD1FAHTaufhDfajba5qWu 6eH1gxyxj+02SC9KEKjPEHCSYIAywP3cdq1vElz4C0J7mfxXqFlZvr0P2aR7 ucr50aKRtXJ4ADnpjliepryS70j4yaXdpp3h74NWg3xi2a7fxPDNbXVuXMki XiSQ7nJeSY7kUH5+O4p3xEHx413X4/7L+FcsVuulS2Ecth4ltRFumYbxL5sO 7ZhI/uAHGcGgD3ywht7eyt7e0IMEUSpFhtw2AALz34xzXPXv/JU9H/7F/Uv/ AEpsqxtN1z4uWWm2tmfhZowMECRER+JcKCqgfKDb9OOKwbvxD8VP+Fl6SzfD LSxKNC1AIg8RjBX7RZ5Ofs/GDjjHf2oA9irkPEv/ACUHwZ/3Ef8A0QKq/wDC S/Fr/ol2k/8AhTD/AOR68i+EXxB+P/jf4iWKfGn4Q2ng+00/UtYg0e8i1De+ oQKpVWMBG5BtAO8kBs5CgUAfQmv6NF4g0W90Oa8vbSO+geB57K4aCeMMMbo5 F+ZGHYjpXg/in4GeLPD/AMJ/GHgfwsdJ1uDU4rV7ExabHaanNMtyjP8AaplY R3B2KTvKo2Qc5zX0VRQB8waL8DdZ0zUPDPiaDwNbwa7B8X9b1/UL9FhFyNIu JdT8uRpM7jGyTW/yA5+YZXIOOp+OHg7Ub/4gaL4uvPhHJ8StDj0DUdG/siNr TdaXc8kLLOVuXRNjpG0bOpLoMYBya91wKMCgD5O8SfCDxsvifVPEUnwy/tjQ rPxL4d1aXw3DeQzDUbS20T7K8cRnZElMFwyOBKU3mEHqRR4V8A/EvwD4i8M/ Emw+FGoS6Ymt+J5ovCun3dmt1o1nqS2nkAhpVgC+ZayySLHIdhuMDdg19Y4F LQB8W+H/AIO+PdF8L6Q3jj4HP4xkv/B114fi0sXNm50K/kv7qZndppFURzJN BmWLc6/Z1+XmvR/BX7PviLXfAvw503xve2vh8+F/C2jWRXS7ZU1qO6htIlnj bUAxMaB1K7YhkgZ3819FYHoKWgBiLsUJknAAyTkn61y/wy/5FV/+wvq//pxu K6uuU+GX/Iqv/wBhfV//AE43FAB8Nv8AkBah/wBjBrf/AKcbiurrlPht/wAg LUP+xg1v/wBONxXV0AFFFFABRRRQAmBWDrXgjwr4gmF3qWiW7XS8JdxAw3Cf 7sqYdfwNb9FAHyJ8ZfCuvwfsezro3iGXUbeZNKi/sfWESa2n3anbqsTShfNV GJAYsZPlJ+U1V13wD8R/g/4P8ZfF7w74H8BfCq70bwbfW8Vp4TuDeQ318zxP HczRvbQx4h8twgKsx85gTivor4b6Zpus/CvQdP1bT7a8tXto2eC5hWWNmWTc pKsCCQyqw9CAe1dfqOmadrFjNperWFvfWdyhjnt7iJZIpUPVWVgQw9jQB8ue L/EHxL8KfFS68EaN4+3alcnwZp0+u3GkWbXUkd3d6qJiwSNVbCxqEU8LjI5Z t2Bqmp/ELWviJ4E0rxB8W9X83wd8UNa0BL2K0sIX1KJNBe6iM6mEx+YRK0Hy KoKuSFD7WX65n8N+HLy//ta60DT577dC/wBpktUaXdCXMJ3kZyhkkK8/KXbG Mmq2oeCPBmrRPBqnhHRr2OS/XVJEuNPikVrxQoW4IZTmUBVAf7w2jnigD428 J/tFfHvVvDupeM7vWIIodU8G+INaWyuLzR2Ol3VraySQm1ggY3JEcqiKRbkN ycnaRtPsPxbstck/Y911PGHiObxJe6jocM95dXNtDEJPOeJmjEcSKoQbioBB O3GSxyT7HB8PvAdrd6rqFt4K0GG516NotVmj02FZL9GGGWdguZQQSCGyDmqf xL+H1r8RfhzrHw7GoSaRBqloLVLm2hRjbAEFSqN8pxtHB4oA+UvjRpQg+Ivx G1vWtH8G3Wk/D6z0QaFpGovPFqH2AWyME0poZE+yStcGZFlUOXdFjwoUE+ve EdP07Tvi/wDHdtN0+K0F7omg3k6xoFMkz2t5ukfH3nIVQSeTgV63L4I8OapP o+q+KdD0rW9b0WNfs2qXenQtPFLgBpIiVJiLEE4QjGa5iP4dSeGdZ+JXj268 R3Goz+LrKFBbvbxxJZQ2sEyxxoV5f/WsSzc9KAOt8Ef8iX4f/wCwVaf+iloo 8Ef8iX4f/wCwVaf+ilooA3aKKKACiiigAooooAKKKKACiiigArk/B/8AyNHj r/sN2/8A6bLOusrk/B//ACNHjr/sN2//AKbLOgDwrxL8efiTpnxB1jRbvxf4 T8Jz2OrtY6R4b8R6HdwR61bB1EcqauZBAHmBJQKjbSQrAkGtzwj+0j42vY/G cviL4NeI5H0TxZc6DpsdjJY7JI44g5M0r3Iji2AEtJIyKfNjVctkDU179nXX 9bs9X8Gj4varF4C125nuLzQZdOgnuFSeUyTQQ3r/ADxxMzNgFWZQxCsuBjM8 V/spzeI7/U5rb4i+Vp914nPiu10290KC+tobqS3MEyypIwW4Qja8e4AxuoYF ulAFbTv2q9Q8SeMfB3/CK/DvV7vwnr3h3XNWv7ppbMTWk+n3cNvKp/0j5liY yBtgff5kRQsA2Ou179pfwT4c0HS/Eepabqy2mqeC5fG8eyKNmS0RrVfKb5wB ITeR99gCsSwAzWL4V/Zej8HweFrXSPH100Ph1NesroS6bD/p9hq12tzcQkIV WF1kRdsiDAAI2ekfhj9mPXNFltpNU+MWragdK8I3PgzSCml20DWVm8ls0chx uWWVRaorFl2uD91cHIB6D8KfinbfFPS7zUbfwzqmimzlRCt3JbTxTKy7leG4 tZZYJVxwdrkqRhgOM3fhSB/whFqf+nu//wDSyauc+CfwQtPg6fEF4NYtr/UP EtzDc3hstKh0y0UxIUUx20JKqxBJd8kscdAAB0nwq/5Ei1/6+7//ANLJqAHf DH/kW7z/ALGHXv8A063VM8D/APIf8ef9jEn/AKbLGn/DH/kW7z/sYde/9Ot1 TfA//If8ef8AYxp/6bLGgDrcCjApaKACud8ea9ceF/COqa3ZpvureAi2Uxl9 0zELGu0ctl2UYHJroqyPEkWitpUl34hIWx09kv5GJYBDCwkDHbyQCoOO+Oho A4LSviF4n0+8Ca5YX2r2t7JFa2Lx6K2nTPdMJGdBHPJkoETJc7QM96uWHxbt ZIbdn0fU7tbhbe4aWOKJEt4rm4eKANmT5j8oPy5yDnA6Dcs9Z8HeNr5BaTTT 3mmo0iRzQT28iLKpjLhZFUkEbhuAOOafYeDfB8lsEs9McRRTQLsYyr81qDHG MNgkLg47E/Nz1oA4vw98f9HvHs9O1vTZrS/urhInVZYMRLNJiA7fNLvlWQkq DjOTgVt3/wATbifwfJ4h0Dw7evJdXSWGlrcBALuV5TGrqA+dgxu5K5HQ96u6 B4B8BQrb6noMEjxW48lCl7M0TGLMYLKW2uy7doYgkBQB0FbFx4S8Oy+HovDU 1oU060SNYVWZ0aHy8FGWQEMrDAO7OfegCp8P9Z1XXvDy3usyq92lzPbygW3k FHjcoyMgdxkMrDIYgjBrI+IXi7WdF1nSdE0O4e3a7huLm4mj0ebUWVEKKoEc RBG5nPzE4+X3q9Z+Kvh54T0GxSz1e2g012mS3aPfNvKOfNckAkgNktIeMnJP NW9a1rwj4d1K31zU7iRbvUIPs1u0MM1w0kSHedqRq3HzAlsenPSgDi5PGnxF gtbC41E6ZpY8n99NcWMkkT3BkYJFPskJtMxmJskMAZCM8c6Xxa+JT+B7S3tL C/0231K4hmvMXjfJ5MS5KqMjLuxVFH1PbFR6rffB2/v4fEGo6llr8JcSBJbl YJAjbFkuYl+QbWTbmUDBTB6V0fiX/hC9DtL/AFjxLLFFDq6R2VxLIXfzF2sF RQMkDBc/L0yzHuaAOjtp1uLaK4QgrKgcY9CM1zV7/wAlT0f/ALF/Uv8A0psq 6Ozt4LS0htbZSIYI1jjGScKBgcnk8Vzl7/yVPR/+xf1L/wBKbKgDq6xfEPhL w54sW3j8RaRBei0cyQeYDmNiMEqQQRkHBrarnPEMOm3WuaHbXupXMErtdeRB FeSQi4/cMrhlQfPtViRkjacMOQKAKX/Cpfhz/wBCzb/9/ZP/AIqj/hUvw5/6 Fm3/AO/sn/xVa0fhfSo3vnD3+dQcyTZ1G4IBKFPkBf8AdjDHhMDOD1ANRN4N 0U2dnp5fUzDYvE8X/E1ut5Medu9/M3OPmOQxIbjdnAoAzv8AhUvw5/6Fm3/7 +yf/ABVH/Cpfhz/0LNv/AN/ZP/iq1z4W0o6gdT3X/nGH7Pj+0bjy9m/f/q9+ zdn+LGccZxxUI8G6Itjd6eH1Pyb1pXlP9q3W8GTG7Y/mbkHyjAUgLzjGTQBn f8Kl+HP/AELNv/39k/8AiqX/AIVL8Of+hYt/+/sn/wAVWrJ4X0p5LKQtqGdP cSQ41G4AJCBPnAfEg2qOHyM5PUk0tv4X0q2vZ7+I34luFhRw+oXDJiIYTahc qp9SAC38WaAMj/hUvw5/6Fm3/wC/sn/xVL/wqX4df9CzB/39k/8Aiquf8IJo P9jroPmar9lXGD/bF353Dl/9b5nmH5j/AHunHTirU/hjSri+i1KU3/nQpLGo XULhUxJndlA4VjzwSCV/hxQBk/8ACpfhz/0LFv8A9/ZP/iq39G0fTNA06HSN Hs4bS0g3eXDEuFXcxYn6kkknuSTVOPwppKG/bdqGdRdpJwdSuDgshQ7Pn/dj BPCYAOCOQDSeELW4sdBisbkofs008MRW4lnPkrM6xbpJSXZ9gXcST82ccYoA o/Db/kBah/2MGt/+nG4rq65T4bf8gLUP+xg1v/043FdXQAUUUUAFFFFABRRR QBxy/CT4cDO3wpaIGYttRnVQScnADYHJ7U7/AIVJ8Ov+hXg/7+yf/FV19FAH If8ACpPh1/0K8H/f2T/4qj/hUnw6/wChXg/7+yf/ABVdfRQByH/CpPh1/wBC vB/39k/+Ko/4VJ8Ov+hXg/7+yf8AxVdfRQByH/CpPh1/0K8H/f2T/wCKpknw h+G8yNFL4UtnRwVZWeQgg9QRursqKAILe2gs7eK0tYEjhhRY40T5VRQMAAdg BRU9FABRRRQAUUUUAFFFFABRRRQAUUUUAFcl4O/5Gjxz/wBhu3/9NlnXW1yF 34EvG1nUtX0jx3r+jf2rMlxc29pHYyRGRIY4Qw8+3kYZSJMjdjI6c0AdfRXJ f8IX4m/6K54q/wDAXSv/AJDo/wCEL8Tf9Fc8Vf8AgLpX/wAh0AdbRXJf8IX4 m/6K54q/8BdK/wDkOj/hC/E3/RXPFX/gLpX/AMh0AdbXIfCj/kR7X/r7v/8A 0smp3/CF+Jv+iueKv/AXSv8A5DrV8MeH7fwroVvodrd3N0lvvYz3OzzZXd2d mbYqrksxPyqB6CgDL+GP/It3n/Yw69/6dbqm+B/+Q/48/wCxjT/02WNO+GP/ ACLd5/2MOvf+nW6pvgf/AJD/AI8/7GNP/TZY0AddRRRQAVznj3Q73xJ4buNA syVF/LBDcOH2Fbcyr5xB9fLDAe5ro6KAPOtb+GFvcXthLbyX98on82/mvNQk eWWKOKTyoAxPCGSTJAwODmsK1+FviHyLL7aA9zZJpcULC7YLH5cjzXUgAOMs 7lB3x04r2KigDwHwz8G/HGl6ppkjSCxtrRra4AgulIgZMNMi8E5kcNnHBVgC eK9O8F+EX8O+Exa38AudVu4jLfmaQyCWdtzFcnI2hmIAHGK7CigDyyTwt4s0 /wAN6B4XtdAjubZbFo9Xmt7uOGZnkIaSJHblUZixYryeAMda3tY8ETa34o0+ 8a6vNO0/SdNe3tjY3ZhfzJHTcp287QsSj3z7V2tFAHluoeBvENhffZPC2kW1 tEnlw22orfN/x753Sx3cLhvtBLtKwPU+Z1U5JtfEPwH4j8b3V0trqqafa2en zW1jEIkkFzNNGVkZt33MDagI5GXPcV6RRQBU01blNPtkvVC3AhQSgHID7Ru5 +ua8W/aK+MN18Dr618eWnw68S+M3tPD2p/6BoVuJZF/0izO+TnKRjHLANj0r 3SuUvf8Akqej/wDYv6l/6U2VAHN+GPjLfa/4c0rXZPhT41ibUrKC7Ma2cLKh kjV8BjKCQM9cD6CuR+B/7RerfHHxDeWc3wW8XeGYtC1O/sH1LU4EWznERZA0 Mh+Z2O3DKowpP3mr3wAKMAcVkalDctrejyw3axRRNP5sPkK3nZj4wx5TB546 9DQBsUUUUAISB1oDKehrivixLdP4VXRNPthc3WtXlvp8cBl8vzFZt8qlsHAM SSZOK42bQvEHhrVdPvvDfhzSPCVxqc8WlJbWsv2lZ90iyySyqFVfkihkC98y HkcUAez5GcZo3L615Xcav4lTWrjTrDVIZb9tTs9Chv5bOMuypEbm5chQARtb aF6AjsSTUGl3nijxRrPhSC48TybbW91O9lMdvEgvba3m8mJnXHBbf/Dgd8ZA IAPWwQelLSL0oPSgAyCKxvCy2y6WwtNRlvY/tt5mWSfzmDfaZNybsDhGygX+ EKF5xmolfXNAsne6a718eeSDFFElwsbOMAqNqOEBPIwxAHBPV3hW7iutMcx2 Zs2W8u1MDKitxcyjfhQBh8FgcZIbJycmgCj8Nv8AkBah/wBjBrf/AKcbioH+ Im+/v7PTPBniPU00+5a0luLWGDyjKoBYLvlVjjIGcVP8Nf8AkA6h/wBjBrf/ AKcrio/h1/zM/wD2Md7/AOyUAH/Cean/ANEz8Xf9+rT/AOSKP+E81P8A6Jn4 u/79Wn/yRXX0UAch/wAJ5qf/AETPxd/36tP/AJIo/wCE81P/AKJn4u/79Wn/ AMkV12RRkUAcj/wnmp/9Ez8Xf9+rT/5Io/4TzU/+iZ+Lv+/Vp/8AJFdcCD0o yBQByP8Awnmp/wDRM/F3/fq0/wDkij/hPNT/AOiZ+Lv+/Vp/8kV19FAHIf8A Cean/wBEz8Xf9+rT/wCSK0vDHim38Tx35i02/sLjTLv7FdW16irJHJ5Uco+4 zKQUmjOQT19q3a5LwT/yMXj3/sYov/TVYUAdbRRRQAUUUUAFFFFABRRRQAUU UUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAHJ/DH/kW7z/sYde/9Ot1 TfA//If8ef8AYxp/6bLGnfDH/kW7z/sYde/9Ot1VfwhOttrHxAncMVi19XIR SxIGl2J4A5J9hQB2PmJv8veu/GdueceuKdkV4zpEHjLTvGX/AAnuteF5AdTs b8gWbtPcLHiJ4IXiKKEZVjPy7zl3buarW/if4itpljb/AG/xFJcvqBH2n+xA ouo/lXC5iHlKCS+JFXIBAk4DEA9vyKQsoIBYAnoM9a8W1PxV8S47t7mxGs+Z 9rmh1K2bRyYNPtPOCJNA2zdPLsw+FLgjdwMAU7xBrfji0j06XToNcvAtuxW+ utLRbmAzzbVdgkT7SI43Hypn96u5R2APaMjOMjmkLKAWJAA5JNfP/wDa3xTM Nt4mKasdVj0W3ieOSxYIEmupDJIQsLHzUjWLIVc5OdmBipZtW+KWr6XcaFrs urwfbYo4LA2+mNL9rinlMchuZDCgj8tOfuxnDA88igD3iSeCJQ0syIp6FmAB pfNj2h967Wxg54Oelec+M/CV/wCKfFek6XaWmmf2fo+myyE6nphu7ZpJHREV V3KN4WN+cnAbpzXODS/F/hm9h0DT5by60LRbhCIBpqNHOY4JLqR1ypKjzWij RVPBXAORQB7YSB1IoyK8Mv4fiXc3GlWOq6rrN0YZ9PupGjsUVPtS208rxZWP Aj3iBSWyAxPI6B/h/wAQ/GPVLWT7UbmF724s4NzWT7rWQy7ptqvbxDYIlcHc XGSvzc0Ae4ZFNWSNyQrqxU4IBzg1518OdT8U30mtNrl/rk9vCq/Z3vtOW2dC dxKKojXLoAA2N6E4KnnaOM8Jx+O/D0NvYw/2xFqF1JbX4T+ykZL97h/MuXup xGAvlhimMqw2DrkAAHvdcpe/8lT0f/sX9S/9KbKl8AjxFdaP/a/iW/uJLi/k eaO1kgWIWsRkcxpgKG3bCoO706DnKXv/ACVPR/8AsX9S/wDSmyoA6uuf1o6W PEugC8g33m66+xvtc7D5Xz8g7Rlf7wPtzXQVj6nPexa3pEMCwGCVp/PLzlHG I8rsQcPz1z0HNAGuOBTI5oZc+VKj4ODtYHBrnfH8+np4UvbXU9Ul02DUFFib yMf6hpTsV2PGFyRkkgY7ivMptZTwat/B4c8P6Ha60q2lobzR5kSyeO4lKiSV Gwscq7DjeT94fMQTQB7VPZ2lzLbz3FtHI9s5khZ1BMbFSpZfQ4YjPoTSS2dn PNBc3FtFJLbOXgdlBaNipUlT2JBI47GvItB8QfEDWdWtfDKeIPJWW8kka88y 1urgW8UP76MmJfLyJJYNpxkZOc4Ob8PjfXLe71PR59QeU+Fpry+1W5eNN7Wi KWtojgABn3dQAdsZ7mgD0iLSdIWUXUNhbCRZpJhIqDIkcYds/wB49CabFoGh wTWdxBpFnHLp6NFaOsKhoEb7yocfKDjkCvMtA1bW2aLTb7xjDot3p01naLYR WcTG+uZYo5pmdAu4qzSMAU2gbWYnrUPg/wAa+Odf8SaXdyzwpa6nNMZLB7y0 Kw2yhvuxqPOEiEIG3HGdwIHFAHsLyxIyo8iqznCgnBJ9qat1bPuC3ETbBlsO Dge9eaePbqxj8S6vr91Z29wfCnh4z2vnIG8u7nkYoy5+6w8leRz81cxoOj6d 4U1XTIdTsvDEkdpoF6bxtJXc9wiRIHa8yMMrYPXqxNAHusciSoHjdWU9CpyK 53Q/D8ao+qXaQf2q01zH9tgt/JkMH2l3jjPGWAG3OeGO4/xVH8NNIGh+A9E0 4wLC4tEmkjVdoWST944AHT5nPHarng8aSNHf+xW3W32++ycv/rftUvm/e5/1 m/29OMUAcr8NL/UdG8OPb6vHNqDy+I9Xt3urO1bG9tSusu8YJ8tOFywJALc4 HNafw1liuIvEc8EqSRSeIbx0dGBVlOwggjqKs/Db/kBah/2MGt/+nG4rF8A6 HFFc+M9T0h0tL+98Q3fmSkF45GRAqF0yM4yM4KkhVGcAUAei0VjxavNay2On axA63l2Cgkt4ZHt2kVAzfOAfLB5xvIJ2nGa1xyKAPBP2kviHqng7xZ4A0OL4 ka74N0nXDqpv7zRdETVLqR4IoWiQRtbXBC5dskJ6ZIrD8F/HL4maYml6FL4f 1LxsvifxZcaL4Z1bWIBoFxdWMWnfa5Lq4hMAwFeOeNSsSbwqkLzXuur+CtL1 nxh4e8aXM10t94bivYrVEYCNxdLGsm8EZOBGuMEd+tM8QeBtJ8S+JfC/ii+u LlLrwle3F9ZLEyhHkmtZbZhICCSNkzEYI5A7cUAeLad+0n4tmmuNC8M/Dm78 Uahbw+INUmku9Zt7MR22n6xPZmMMsIBJEY8sbckYDtndIdf4UfGTx98SfjDq tnD4fsYvAc/hDw94i0yd7/F5EL9Lp1Z4RDyz+WFZfMwnkggt5hC9T4Z+AfhL wtq95rGn6hqjzXtjq1hIssiFRHqGoSX0xGEHIllYL6KADk81L4H+B+h/DzX9 K1zw54j1tE03wvp3hWaykeF4L22sVdbWWX93vEqCWXlGVTvOVOBgA9KooooA K5LwT/yMXj3/ALGKL/01WFdbXJeCf+Ri8e/9jFF/6arCgDraKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA5P4Y/8i3e f9jDr3/p1uqZ4H/5D/jz/sYk/wDTZY0/4Y/8i3ef9jDr3/p1uqZ4H/5D/jz/ ALGJP/TZY0AQR+N7240q01C3s4Gk1LXW0uzUlsNAkzq0p56+XFI/HHArFg+J viGC01rUtY03TIF0uyuLp7DfKl3bMmfLV1YYlV+m+PjPTOa6Cz+GfhyzmId7 66tQk8cFlcXJe3tlmBEnlrwRkMwyScAkDGary/CnQprSe2u9X1y5kmgW1jnm vN8tvCHV9kZK4wWRMlgScDJoA59/ilrFr4XutcudS0C6mFxaWkIt7O6RIZJn wxkDnc4VdzfJz8prpfh/4v1TxTY395dx2t1DbShLa8sY5I4bsbMnYsvPB+XO cE/Q1dtPBUELWcl9rmrao1hefbYGvZ0crJ5bRgfKi8AOxx61LFL4X8FQvb3W t2mnxXlxLcxx3d2kahmOXEe4j5dxzjnBagDn5PHHiW68OXGu2Wn6VYpDqF1b tLfzsY4oYGZNx2cu7OpAC8DPfHKQeOvE7+IvDWm3eg29rDr1ss0kMpk86I+U Xk+cgR5UgDy+XIJPAFWr/wABeHrjSdHii8Q6hY22nStNazwXUY82WZs72ZlK sxZztI7tx1q9a+CdG0zWo9fm1DUJ5onZoI7q7LwwzSDa7op6O/I9PmOAMmgD qR0paQdKoalrejaKiSaxq1nYJIdqNczpEGPoCxGaANCimKyyKHVgVYZBByCK zn8SeH4tRGjya7pyX5YKLVrmMTEkZA2Z3ZP0oA1KKo2+saXeXc1haanaTXNv /roY5laSP/eUHK/jTf7c0b+0v7G/taz+343fZPPTzsYznZnd056UAaFcpe/8 lT0f/sX9S/8ASmyrq65S9/5Kno//AGL+pf8ApTZUAdXWJqm3+3tGzq01u264 22qzKq3X7voynltv3hjp1NbdYmqmL+3dGV9MmmkY3Gy6SBXW2/d8lnPKbugx 16GgDTuVtbiNrS7WKRJFIaKQAhl75B6iqdv4f8O2di+lWmi6fBZTZ320dsix PnrlAMH8q8/8ReANdawu9OTbqp1aa3t59Td2W+jtzcIZVbJ27PLDcpsxgfKe tY2qfDbVLjxvLHFYapDYx3du+mS2QtFtbS2UKz/O6mWOQyeYSEHz7hk9TQB6 RpOp+EkuL200m2gt18PoYZ5I7MxQ26kB2RH2hSOAWCnjAzWjbW2h6nbvfW9r ayxarGksrGFc3KbRtLgjLfLgc9uK4PTPAzaP8KNcsNP8L28Wr6zbXss1pFGi tI8rSGONudp2q4UAnAxisez8D6gmpRWVt4Nuba4j1K0nsdVLxrFp+nReWxhQ K+5XIWRGQLhi5JJFAHrTaXpf29NVfTrT7aqeWtyYl80J/dD4zj2zTYNJ0fT7 u41C102ytrm5+a4mjhVJJcd2YDLfjXlvxm8PeLfEepC20rQZ7qBLALaTxJG4 jnaTEjEySL5TKoUq6ozHJAIqceGdRn1XWZdS8G3N7qqyXsttq8lwixvAYylv Ag3bmBUgMjALncxzxQB1mkaDo+sX+qeKBqI1TSvEUMO6znt43gKxjarjK7iD gnB45zRrfgPQbrQ7rRtGFr4etrof6edPs4UM8ODuRvl4BB6jn0Ned2HhPxBY aY/hnTfBd/Ba6jZ6Pp5kzCkdvbK+66LgOTvLSSZAB65zVeHwv48l17VdZHh6 6trufTtVVnCRhJbiUqsKCTzWeVACWBbaBtwAOlAHtejalp+saZbajpcwltbi JZImAI+QgEcHkcEcGoPDs13PprPe2yQSC6ulCLOJRsWdwh3DuVCkj+EnHaue 0/wNd2mrWl3aS2+k22npDF/oRYzX6IiqBPnCbeMY2s2AMMOldB4aWZNNYT6m 98Td3Z85tmQDcSEJ8hIwgwg5zhfmAOQADM+G3/IC1D/sYNb/APTjcVH8Ov8A mZ/+xjvf/ZKk+G3/ACAtQ/7GDW//AE43FR/Dr/mZ/wDsY73/ANkoA5D9oJ/G l1a+HdE8D3948txfyXOqaRpOsRaZq+pafFCwdbOaTAUpLJbs+GQleN6558fX 9oPWfhnp8nhLR38Y6jr+o66LC20nxhpVzqV9oEa2X2h/Naw82a+jcLujYMSN zbnwtfSPj74Z+EfiZY2dl4rsJ5H064+1WN3Z3k1nd2c20qXhnhZZIyVYg4YZ Bwc1zT/s3fCaTw+fDzaPqR3X41U6n/bN5/an2wJ5Yn+3eb9o3+WSmd/3SR0o A4Xwp8dvi9491bwXoGj+C9J0K/1nStb1HVl1y1voSn9n3lvbK1vE4jlCTfaA 6+aqkAjOcc5+vftIa5r3ha1k0nRYIrmwsNOn8Uol1NDJp2ozazBYi0R42DD5 474sCeViQHhzn2jwv8JfAng270e98O6M1tPoWnXel2cjXMsjCC6mimuN5diZ HeWGNy75YkHnk5rH4J/DTyPEtsnhqONPF+rW+t6x5c0im5vIXieOTIPy4aFG 2rgE7iR8zZAOG8K/G34gal4W1T4wa74a0KP4exabqupWqWlzKdWiisy+0yow 8tzKsTnamDGSoO7kiv8AAH4+eOfin4jm0XxX4ImsLS50pdYsr+HRdUsoIfnR TayPewxrNJiRWWSI4YK52rgZ7vRvgP8ADPQPEV94l0/QZvPv1uka2mvriayh Fyc3Pk2ruYYTKclyijdk56mpfh78E/h98Lry4vvCGnX0U08CWiNeanc3v2a2 U5W3gE8j+TED0RMLwOOBgA8C+IviDxjb+EviVqWn+IvGF3dy/FrRPD0Fppmt PbzpYtNpyva2bNIiW5kFxKCQyAlhk8ZqpPr3jnSvBvxu8Maje/EXwodM8DN4 h8O22v6+LvVopoIrlprqG+gllPk+YtshjMrEENkBXwfX7T4EjXl+IHh34heR caB4l8WweKdKk0rUrq1voJY47fbveMIYnSW1RlMbnOTnGOY/Ff7PGmWPw28d 6B8OPNn8UeMtAuNB/tTxPrl9fssMqOm0zSmaRUQSu4RRgtjPqAD1XwvNNc+G tJuriVpJZrG3kd2OSzGNSSfcmsjwT/yMXj3/ALGKL/01WFbuhWL6Xomn6ZK6 u9paxQMy9GKIFJHtxWF4J/5GLx7/ANjFF/6arCgDraKKKACiiigAooooAKKK KACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA5P4Y/8AIt3n/Yw6 9/6dbqm+B/8AkP8Ajz/sY0/9NljTvhj/AMi3ef8AYw69/wCnW6pvgf8A5D/j z/sY0/8ATZY0AddRRRQAV534h8H6z4o8cS38d+NPs7HTY7WKSXT47kTPLIzS bPM4BASPkDvXoledeOfGut6V4ng8P6JcGALYG8nkTRLjUWLNJtjTbEy7M7ZD ljjigDCg8O+LtAaO30uXWJdN0u9aGysioZDa21p8rEY+ZpJ1GO3JxiqN/wCG /iE91pdleXuv6ittNYTtK7gJ9sjtp3Y5AGIjIYEJ6ZB7101j8ULyRLLS9V0W 6stTE9vbahMIVe2imaATyRjMgbIj3Z67cc54zBd/GhZI9P8A7P8AC2pxNdy2 cj/axEu2zmSWQygCTjCwScHB4zgigDn/AA4nxn1CHy9SvtUtPtt1ZwzyPEQ8 DCTfPIgYAKmxWTgFSWXGea3viPoN7e3Nlb6fY+IbvULWxaHS7uLypbbz3YZa 5Lg4xsQknhlJA54qzYfHfwbqkdw9jBezvG1uIYofKle4E0qxIVVHJU7mGVfa 2O1J4z+IWv6Tqdrp2kaU1skVrDfapcXFuLgWaSyFI0ZUkXur5ZS+AvANAHo0 SssSLIQWCgHA4z7V5ZYfDvV9U/tHxDqlxh7rVptUj0xrWKOV2ilzbo1wQXRW EUZOOxNerLnYN2M45xXlJ+IXi288R3sOkbJLK11f7CIG0W48trdHVZpmvd4i Xb+9PQ/cAoAl+HmjyW3iISQ+Fbyzsre2mdZdRtEhuLaeR1LQpKpzcIcsdxBx tX5jnjE0rRvEGp/EX+1bnR9SUHxDLeSLc6WIYooI42hikW6PzNlVQiMZBLHN dh4S8UeKdT8QvYa6+n252SyNp/2WSKaJFYBJI5SzJcIQRllC43D6VUl+KIn+ J9r4O06+0xrRLg2N1GXBuWn8h5SVG7hF2opODlmI4xQB6TXKXv8AyVPR/wDs X9S/9KbKurrlL3/kqej/APYv6l/6U2VAHV1j6lDfvrWkyWzw/Zo2n+0B4WZy DH8u1gMLz1z1HArYrnPFNrcxzWPiCx0a71S60lpTFa21ykTP5i7DxIVRsA55 YYxxk8UAdEOlGBWNPq+rRXtvbR+F72eKZZTJcLPAFhKjKgguGO48DAOO+KSL WtXe4von8J38aWzYgkM9uRdDYWygEmV5AX5gOWB6ZNAG3SYFc+df1wadaXn/ AAheomed4lltftNtvtwxYMzN5m0hAoJ2kk7hjODiwdX1VdS+yDwvem38hpft fnwbN4faI9u/duK/PnGMcZzxQBs0mBWCNd1v7Je3H/CHaj5tvJMsMH2i23XK pjYyHzMAPk4DEEYOccU6TWtXU2AXwpfuLp1E5E9v/oilAxZ8yfMASV+XJypI 4waAN2kwKx4NX1aW/ltJfC97DAiRMly08BSQt95QA5YFO+QAe2arHxDrw0c6 j/wgup/agcfYftNr5p+fbnd5uz7vzfe6cdeKAOirD8JG0bSXNjYSWcX269zG 8PlEv9ql3vtyeGbcwbPzBg2BnAdc6xq0N9DaxeF72eGRJme4WeAJEUGVUguG JfoMAgd8VPoMepQ2BTVkt0uDcXDgQMxXy2mcx/eOd2wru7bs44xQBj/Db/kB ah/2MGt/+nG4qP4df8zP/wBjHe/+yVJ8Nv8AkBah/wBjBrf/AKcbio/h1/zM /wD2Md7/AOyUAcf8X/GnxK8O6hHZ6XYzaN4XeAPd+KLTTX1i4tnydyfY0IaM AYPnFZEHdRXm/iP4i/EG3+Mdx4N8B69ptm+ueINC0h9UutPE7vby6FfXTSlM qC++3RlA2jseCa+psCsCfwL4PuNeHiebw1pz6sLmK9F61upmE8cLwRybuu5Y pZEB7K7DvQByfwT8X+KvE3gbU5PGF/bXusaFrus6FNe29t5CXX2K7lhSbysk IWVFJUEjOccV4L4c+Pfxt034Y+FviF4h8a+Hdfk8c+DdZ1aCystKWE6Td2Wm vdJLuDnzY90flyhgAJJEC4HB+sdP8PaRo9pd2Wjafb2MV7cXF5MsMYUPcTOX llYDqzOxYnuSa8++F37Ofwz+GXg608NReF9Dvb5tBh0DV9UGmRxTarAkIjcS 4ydrgZZcnPcnFAHivi34n/FzwdNol9/wkGjaj4m1Twno959uk0sRRRtfa/Y2 7ReWr8xrHcOM53EgHOai+IOv/GvU/EFv8Pbz4rQ2174Z+JegWK6tZ6LHF9rg vbMXCJLCXK/u3LDGcONuRkZr6f1D4c+BtUe3l1Hwnply9pbQWkDS2ysY4IJk nhjGeipLFG6jsyKe1Q+IPhd8O/FkGqWnibwXo+pxa3PBc6il1arILqaBQsMj 5HLIqqFPUAUAfO/gL9oD41+KPHdnfz+HbiPwpqetavonlXNvp1vDbLafaFSW KYXhuZpt9uC8RtwMOxAATJ1PCHxJ+M9x8OPAPjCTxe3ibxX4s0SDWf8AhHrT wsTaSxTRROFa4RlFrtLEebJJtO8/IcCvb7D4RfC/S/Fl149074faDa+I72No bjVIrGNbmRWADAuBn5gACep710Oi6Ppfh7SLLQNE0+Cx07ToI7W0tYECRwQo oVERRwFAAAHoKAGaBc6veaNZXev6XHpuozQI91Zx3AnW3lI+ZBIAA4B43YGa xfBP/IxePf8AsYov/TVYV1tcl4J/5GLx7/2MUX/pqsKAOtooooAKKKKACiii gAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigDk/hj/yLd5/ 2MOvf+nW6pvgf/kP+PP+xjT/ANNljTvhj/yLd5/2MOvf+nW6pvgf/kP+PP8A sY0/9NljQB11FFFABVCDSbC21O61eKIi6u444pXLE5WPdtAHQY3N09av0UAc 9deB/Dt55ouLJ2M01xcOfOcEyTR+XI2Qeuw7R6Dpiobn4feFLu7jvpdOYyxP GVxM4XakLQhCoOCnlu42ng7j6109FAHK6b8OvDGkiBbS0uGFtcR3EXnXk0ux owwQDexwq7jhemcHsKtat4L8Pa7qkGsalZySXMAQfLPIiShG3oJEUhZArEkB gcE10FFACAcYrNstB0vT9JfRLe0X7HL5vmROS4fzGZn3E8nJZs/WtOigDnNC 8DeHvDt19s06K6aZYTbxtc3s1x5MRIPlx+Yx2LlRwuOg9Klg8HaBBb2NtFYg Lp119sgbe2/zjuJdmzliS7E5Jzmt6igArlL3/kqej/8AYv6l/wClNlXV1yl7 /wAlT0f/ALF/Uv8A0psqAOrooooAKKKKACiiigBMCloooAKKKKACiiigDlPh t/yAtQ/7GDW//TjcVi6Lf+J/C9/r9qfh1r+pRXesXF7BdWVxp/lSRyBcYEty jgjBBBUcjv1ra+G3/IC1D/sYNb/9ONxXVYAoA5L/AITbxF/0STxb/wCBGlf/ ACbR/wAJt4i/6JJ4t/8AAjSv/k2uuooA5H/hNvEX/RJPFv8A4EaV/wDJtH/C beIv+iSeLf8AwI0r/wCTa66igDkf+E28Rf8ARJPFv/gRpX/ybQfG3iP/AKJJ 4t/8CNK/+Ta66kIzwaAPBvA0Nzr3hLTdZ1P4ffE69u7yIzTTx+LViSRixyQg 1NQo9goA7Ct7+woP+iXfFT/wsh/8ta5L4m+ItZ8KfshSa7oGq6pp17DBp0a3 Olg/a0STUIY5BCACS5R2UAAnJ4rkofiF4/8AhvY+K/H/AIVtPibrPhbw/wCF r2/u7f4ixPaGbU0kiNrHbNJGswUp5/mHaUH7vHORQB61/YcP/RLvip/4WI/+ WtO8C/CyxluPEmqazpni/SP7S1dbi1t7nxXeGbyVsraLc5gu3UkvFJjLE4A6 DAHF+IfjV8SvCPjq68M3HhnS7/xDcJ4Ys/siatKunRy6hc6ihZC0W5dq2yFm 2kt0x8ozj6j8a/jZrHjPwNo1lY+GtIn0/wAdat4Z8TwLeTy214LfSZLtWiby g+wxMHAYAiVEByuTQB7x/wAKt8K/8/fif/wqtU/+SKP+FW+Ff+fvxP8A+FVq n/yRXz74d/bT13xDpup+I4PhzM+jyeGtV8QaVOllqcYg+yWz3EUd5NNax2+J kThoZXAbCjdkNXffE3xf8QT+y7rfjTUprfw94jutJS7ibRbp3+xrK6bdkroC ZAj4J24znHFAHon/AAq3wr/z9+J//Cq1T/5IrO8QfDbw5Z6FqV3bX/idJoLS aSNv+Ep1T5WCEg/8fHqK8X+LE/xU8N+PNY8XXlx4sPw28B6Tpnn3Gn+LI7Oe cRq8t5cvbiJzdOFaIMrtDkI23cSBXb+HdU1iX4kfGnRLjxFqWoaXbaTpN/YW 13NvSzNzbXRkWEYGxD5aHbzyKAPVvB81xd+EtEurmdpZptOtpJJH5Z2MSksT 3JJopngj/kS/D/8A2CrT/wBFLRQBu0UUUAFFFFABRRRQAUUUUAFFFFABRRRQ AUUUUAFFFFABRRSHOOKAOU+GP/It3n/Yw69/6dbqkm8A276nqOr2HiXXtMfV bhbq5itLlBG0oiji3AMjY+SJBwccZ7mq8Pw9v7F7pdI+IvifTra5vLq++ywx 6e8cck8zzSBTLas+N8jEZY4zjNT/APCE+Iv+it+Lf/AfSv8A5CoAf/wgl1/0 P/iv/wACof8A41R/wgl1/wBD/wCK/wDwKh/+NUz/AIQnxF/0Vvxb/wCA+lf/ ACFR/wAIT4i/6K34t/8AAfSv/kKgB/8Awgl1/wBD/wCK/wDwKh/+NUf8IJdf 9D/4r/8AAqH/AONUz/hCfEX/AEVvxb/4D6V/8hUf8IT4i/6K34t/8B9K/wDk KgB//CCXX/Q/+K//AAKh/wDjVH/CCXX/AEP/AIr/APAqH/41TP8AhCfEX/RW /Fv/AID6V/8AIVH/AAhPiL/orfi3/wAB9K/+QqAH/wDCCXX/AEP/AIr/APAq H/41R/wgl1/0P/iv/wACof8A41TP+EJ8Rf8ARW/Fv/gPpX/yFR/whPiL/orf i3/wH0r/AOQqAH/8IJdf9D/4r/8AAqH/AONUf8IJdf8AQ/8Aiv8A8Cof/jVM /wCEJ8Rf9Fb8W/8AgPpX/wAhUf8ACE+Iv+it+Lf/AAH0r/5CoAf/AMIJdf8A Q/8Aiv8A8Cof/jVH/CCXX/Q/+K//AAKh/wDjVM/4QnxF/wBFb8W/+A+lf/IV H/CE+Iv+it+Lf/AfSv8A5CoAf/wgl1/0P/iv/wACof8A41U2keDINJ1ka7Lr mr6ldpbPaRtfTq4jjd0ZwoVVGSY05Oen1qt/whPiL/orfi3/AMB9K/8AkKj/ AIQnxF/0Vvxb/wCA+lf/ACFQB11Fcj/whPiL/orfi3/wH0r/AOQqP+EJ8Rf9 Fb8W/wDgPpX/AMhUAddRXI/8IT4i/wCit+Lf/AfSv/kKj/hCfEX/AEVvxb/4 D6V/8hUAddRXI/8ACE+Iv+it+Lf/AAH0r/5Co/4QnxF/0Vvxb/4D6V/8hUAd dRXI/wDCE+Iv+it+Lf8AwH0r/wCQqP8AhCfEX/RW/Fv/AID6V/8AIVAHXUVy P/CE+Iv+it+Lf/AfSv8A5Co/4QnxF/0Vvxb/AOA+lf8AyFQB11Fcj/whPiL/ AKK34t/8B9K/+QqP+EJ8Rf8ARW/Fv/gPpX/yFQA/4bf8gLUP+xg1v/043FdX WL4X8OxeF9J/sqLULy+P2m4u5Lm78vzZZZ5nlkZvLREHzSNgKoAGK2qACiii gAooooAKKKKAPMvDHg7Q/HvwV0bwt4igkm0+5itppEjkMbF4bhZo/mHIw8an 3Ax3rsPGXhHRfHvhXVPBniOCSbS9YtntLuOOQxs0bcEBhyD7isPTPhvqWjWU WmaR8TfFVnZQZWC3WHTXWJSSQoL2hYgZxySfUmrf/CE+Iv8Aorfi3/wH0r/5 CoArav8ACLwVrvi7/hNtSsJ31Yy6ZN5i3Lqu6wed7Y7QcfK11Nn+9kZ6Cs/U fgT4B1K9/tNodUtb4eJW8WLdWepTQSrqDWy2zkMhH7t4F2NH90gtxzWz/wAI T4i/6K34t/8AAfSv/kKj/hCfEX/RW/Fv/gPpX/yFQBydh+zN8K9Mh1Wyt7PW nsNT0290lNPm1q6ltLC2u1ZbhLSF3KW+4MRlACAcLgcVrfF74e6n4u+DGt/D nwe1pFeXGmpZ6f8AbpnSEGMoUEjqrMBhMEhSfY1rf8IT4i/6K34t/wDAfSv/ AJCo/wCEJ8Rf9Fb8W/8AgPpX/wAhUAYOs/A3wb401ceLPFWnXttqeowWo1uw 0/WLlNP1F4QCi3ESlEuVQ/KC6AsoAYY+UZ+neCvFOkeMfiz4511NLisPEenW NrpUdpcPLL5Npb3Cl5g0ahGYzcKpcYXrXXf8IT4i/wCit+Lf/AfSv/kKobvw Brl/aTWVz8WPFrRXEbRSL5GljKsMEZFn6GgDX8Ef8iX4f/7BVp/6KWitHS9O g0nTbTS7UHybOCO3j3cttRQoye5wKKALlFFFABRRRQAUUUUAFFFFABRRRQAU UUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAHNfEXxrp3w48Ca9491a GaWz0DT5r+aKHHmSCNC2xc8ZJAAzxzXmNz8dvGHw21W0tvj34W0XRbHV7C5v 7G60G/mv/IaDyzLbzq8SHftlBDplTtYccZ9e8S+H9I8W6BqPhjxBYpeabqtr LZ3du+QJYpFKsuRyMgnkcivG3/ZH8M38+qTeJPiT488QjUtJl0WNdU1GGb7D buI8NbkRDZKPKjzIcs+0by1AHQ+Lv2mvhN4JvL2w1vVtRNzp2oXGn3cNrpk9 w8JghgmnmYRqSIY0uoN0n3QXx1qze/tF/CbT4Zbu+8SNFaQ32oae90bdzEJb KzN5cHcByggBYMOG6DJrhfEH7EHws8VwrL4n1vX9X1VtSutSn1XUFsrq4na5 ito54yJbdo0VhaQkFEV0IOxlHFaWqfsffDDW9WvrjUtT8QzaRfNfSNoH2uMa fG95YGxuHVRH5mWhIxlyFZflwCwIBcn/AGufg3b6Lb6u93rpmutS/slNLXQr s6j9o8nzsG22eZtMRDhsYIPGTxXW+MvjP4L8ENocOrHWLi48RRPc2dtp2j3V 3Otsnl+ZPLFEheKNDNEGZgMFwOtecJ+xV8MLf4f3Hw9s9Y1i0tbzUBqF1cW1 tp0TzsIvKVGiW1FvgL0YRbw3zBt3Nd34m+B+ieIJPC91YeLPFGg3vhWxbSbe 90zUAlxc2D+T5lvNJIrlg5t4SXGJMrkMMnIBga/+1x8GPDHiHXPC+t6prFvq Hh+Hz7iM6LdfvkFzDbMYPkzNiW5hX5Ac7sjIqfxP+0b4esfhLc/Fjw3YX11a 2Gu2Wi31ne2U9tdW0kmow2lwrwMnmiSMSlgm3LEADrXP337F/wANL/xhqPjO XxB4mW51G9lvmgWe38tXlvLe8kXcYfMcGa0hI3uxVQUUqvFdrrPwG8Kaz4O8 QeCpNV1q2tfEfiIeKLi4trhEuIbwXcV0PKfZhVEkKYyCcZ5zzQBkal+1X8IN I0a11rUb/WYWuLi6t5rA6JdfbrI22w3DXNvs8yFIxLEzMwAxIhGdwrV+JPx2 8JfDC50O91/UozpGq6dd6gJLe2nuZ5Ujls4ozCsSsGBa8jyCdx3LtB5xxnif 9iz4VeMdPsovE2pa1qerW99eX9zrV8tndXd690IlmEglgaFcrbwKpjjRkWJQ hXnPb+PvgL4L+IZ8PDU5tQtE8MWrWVjFZyIiiI3FnPhgynOGsIQMY4LeoIAM fxT+0p4V0P4TTfFjRfD+v6tb2ut2ug3Gm/2ZPBfwXMl7HaujwMnmKyGTO3b8 3ygfeFYXgj9sD4fa3oOo33jGLUNAv9NbU5HhfTLoxXMNrqb2I+zOY8XEhc26 siZIeZVrtdc+BnhfW/B/iLwadX1izh8Sa9/wkct3byxi4tr4XMVwjRFkKgLL BGQGVhwQc5rmtY/ZH+F/iHw3B4X1ybVr6zt7TVrVPOkhY7r/AFKLUZJSDHtZ kuIIygKldoIZWzQBreIvj5oY+BHiv40+CYTfr4b03ULk2WoxyWbpc2qMWgnR 13xEEDOR0IIyCDXBaX+0/wCM7vQ/FpstB8HeK9R8OjSXTUPCerz6hpKR3s0k btPIkLSqbdYzLIkaO2xlIAzXcWv7OnhLQ/gfrvwP0CeWDTtft7uG7uTBbwvI 1wNsjbII44kO3CjZGAMDg95fFPwk1vxJoFtodprGm+H2sbyPULK90S2e0ntr pAVWVdrFGypYFXVlYMVII6puxcIKW7SMHSP2pvDWl6JoknxBkspNV167uoLB fCPn61b3cNv5fmXC+XH5saqZVV0kQOrA8EYNdz8RvjV4G+FZsY/FVxqTS38E 94sen6ZPePDaQ7POupViVjFDH5ibnbAG4V5P4h/ZEk8VeHxoOteNrqd7jUpd W1G/ZA1zfXMixI0r5G2NwkMao8KxsgT5GXcSPSviX8DtB+J5sJ7/AMQa/o9x aWFzo88+k3SxPeadc+X9otJfMR8xv5UZyuHBX5WGTQncJw5NmmaXhz4ueF/G cfig+EzeXg8Ku8F1cSWkkVrLOI/M2RTEbZflKklCcB19a8N+Gv7aceq6Zp+t fEJfCk9hqmgWWtBvBmoT6vPpstzcW1vFZXkIj3RztJdoqhckmKXj5c1754P+ F/hnwNoms+HtB+0x2OtXk95JGzg+SZY0jKR8cKFRcZyfUmsi1+BPgWx+HGh/ DGwt5bXTNDOjNFcQLElzcNps0M0DSuEw5ZrdN5wMgtjGeGQchb/tdfDSyvn0 nxHLqsV6LyeN/smiXskVnANRlsY2un8vELedF5bbuAx4JHNQ+Fv2yPhjq/h/ RNX8R2euaBc6zJNutbnSrhhZwJdNbrczuExFCzrgSNhcq4z8jEbE37Lnw/nm 8STtqWthvFJJvMTx4XOrS6n8n7vj9/O685+QAdfmrndR/Yi+Eer3ukX2q3er XsmjyTLD9qispy1o901yLTdJbsyRpLJIVeMrLiRgXIxgA3b39rT4R2M9vbvJ 4jllu9Uv9Jt44PD93M1xLZS+VdvGEQmSON/lLrkZ6Z5xbh+K/j+D40af8PdV 8HaOuj6yLuSzktdSebUre1hTK311CIxHFBK48tRv37mXI+8Fp+MP2VvAvjHw fZ+B7zX/ABDaabaapqWqn7NLAXkkvbqS5lGZImCFZJW2SRhZUH3XByT6Rpng vStJ8Ual4stnla81SwsdOl3hDiK1Mxj+fb5jEmd87mYcDAGWyAdHRRRQAUUU UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAf/2Q== ------_=_NextPart_001_01CD1121.4E2A6B88 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 ------_=_NextPart_001_01CD1121.4E2A6B88-- From ipp-bounces@pwg.org Mon Apr 2 17:39:32 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8445F21F8674 for ; Mon, 2 Apr 2012 17:39:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.597 X-Spam-Level: X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLLblE3UoTV5 for ; Mon, 2 Apr 2012 17:39:29 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 520A621F8683 for ; Mon, 2 Apr 2012 17:39:29 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id AB89979708; Mon, 2 Apr 2012 20:39:01 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by pwg.org (Postfix) with ESMTP id 7DC5B79703 for ; Mon, 2 Apr 2012 20:38:40 -0400 (EDT) Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta08.emeryville.ca.mail.comcast.net with comcast id tCb31i0081wfjNsA8CefyB; Tue, 03 Apr 2012 00:38:39 +0000 Received: from LarryHP6616 ([98.210.92.38]) by omta23.emeryville.ca.mail.comcast.net with comcast id tCee1i0040pficJ8jCeeQS; Tue, 03 Apr 2012 00:38:39 +0000 From: "larryupthegrove" To: "'Petrie, Glen'" , References: In-Reply-To: Subject: RE: [IPP] A different function model for discuss Date: Mon, 2 Apr 2012 17:38:38 -0700 Message-ID: <079401cd1132$1c90efb0$55b2cf10$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQG75lPLYvJY7pYJogdX57gRfX0zpZaqkGWw Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0675629441==" 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: AB89979708.A99E2 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============0675629441== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0795_01CD10F7.7037E410" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0795_01CD10F7.7037E410 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit All, The reason I see for having a "Print Manager" is for the purpose of having a standard for connecting a printer (logical or physical) to the cloud provider. So the simplest implementation would reflect just a user connecting to the cloud provider. The cloud provider "owns" the printers, so there isn't any outgoing connection to model. Examples would be Staples, Mimeo.com, Vistaprint.com Second implementation would be devices not owned by the cloud provider. Current implementations include mail protocols, FTP, IPP, route via Dropbox, Box, Google cloud print, etc. So a standard should address a common solution that works for a variety of implementations. So having a cloud print manager at , or as part of, each device makes sense to me. The third implementation would be a more robust print manager, which would control multiple devices off of a single connection. My example would be IBM InfoPrint manager or similar output manager. So I see two parts to this, one between the user and the cloud provider, and one between the cloud provider and some common point that works for multiple implementations. Since in a large number of cases the print data has to transverse into a private network, that common point should be capable of being hosted within a private network. Just my thoughts. Larry From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Monday, April 02, 2012 3:38 PM To: ipp@pwg.org Subject: [IPP] A different function model for discuss All, After today's meeting, I thought I would try to draw a slightly different representation of the functional model diagram than what is in the current model document. In the current model it is very unclear what and where the "Cloud Print Manager" is (is in its own cloud or is it proxy (so not really a cloud service) or in the printer (so not really a cloud service)). Why does the (Print) Client "register" with the Cloud Provider instead of just using the Cloud Print Provider. In the functional model attached, I propose the more cloud centric model which places service, security and other functionality in the Cloud. The model is not specifically concerned with interfaces such as using IPP; it is meant to be more a very top level view. In the attached model the Client uses or accesses the Cloud Provider for printing services. The User interacts with the Cloud Print Provider to select a Print Service associated with the User. The Cloud Print Provider then sends Capability information (which likely has no secure information) to the Client. The Print Client creates Print Job Ticket (with a Print Content reference) which is sent to the Print Service (or Print Service Manager) for printing. The Print Service accepts (or rejects the Print Job). The Print Service prints the Print Job and sends status info to the Print Status Service. Federated printing also work quit well with this model. Glen -- 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_0795_01CD10F7.7037E410 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,=

 

The reason I see for having a “Print Manage= r” is for the purpose of having a standard for connecting a printer (= logical or physical) to the cloud provider.

 

So the simplest implementation would reflect just a user connecting to the= cloud provider.  The cloud provider “owns” the printers, = so there isn’t any outgoing connection to model.

Examples would be Staples, Mimeo.com, Vistapri= nt.com

 

Second implementation would be devices= not owned by the cloud provider.  Current implementations include mai= l protocols, FTP, IPP, route via Dropbox, Box, Google cloud print, etc.&nbs= p; So a standard should address a common solution that works for a variety = of implementations.  So having a cloud print manager at , or as part o= f, each device makes sense to me.

 

The third i= mplementation would be a more robust print manager, which would control mul= tiple devices off of a single connection.  My example would be IBM Inf= oPrint manager or similar output manager.

 

So = I see two parts to this, one between the user and the cloud provider, and o= ne between the cloud provider and some common point that works for multiple= implementations.  Since in a large number of cases the print data has= to transverse into a private network, that common point should be capable = of being hosted within a private network.

 

Jus= t my thoughts…

 

Larry=

 

 

From= : ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of P= etrie, Glen
Sent: Monday, April 02, 2012 3:38 PM
To: ip= p@pwg.org
Subject: [IPP] A different function model for discuss

 

<= p class=3DMsoNormal>All,

 

After today’s meeting, I thought I would t= ry to draw a slightly different representation of the functional model diag= ram than what is in the current model document.  In the current model = it is very unclear what and where the “Cloud Print Manager” is = (is in its own cloud or is it proxy (so not really a cloud service) or in t= he printer (so not really a cloud service)).   Why does the (Prin= t) Client “register” with the Cloud Provider instead of just us= ing the Cloud Print Provider.

&nbs= p;

In the functional model attached, I propos= e the more cloud centric model which places service, security and other fun= ctionality in the Cloud. The model is not specifically concerned with inter= faces such as using IPP; it is meant to be more a very top level view. = ; In the attached model the Client uses or accesses the Cloud Provider for = printing services.  The User interacts with the Cloud Print Provider t= o select a Print Service associated with the User.  The Cloud Print Pr= ovider then sends Capability information (which likely has no secure inform= ation) to the Client.  The Print Client creates Print Job Ticket (with= a Print Content reference) which is sent to the Print Service (or Print Se= rvice Manager) for printing.  The Print Service accepts (or rejects th= e Print Job).  The Print Service prints the Print Job and sends status= info to the Print Status Service.   Federated printing also work= quit well with this model.

 =

Glen

 


--
This message has been scanned for viruses and <= br>dangerous content by MailSca= nner, 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_0795_01CD10F7.7037E410-- --===============0675629441== 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 --===============0675629441==-- From ipp-bounces@pwg.org Mon Apr 2 17:52:17 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C8821F8569 for ; Mon, 2 Apr 2012 17:52:17 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ErdQ+A+Ib0d for ; Mon, 2 Apr 2012 17:52:16 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 24C9F21F8565 for ; Mon, 2 Apr 2012 17:52:16 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id EF81B79637; Mon, 2 Apr 2012 20:51:56 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35]) by pwg.org (Postfix) with ESMTP id AE8DE795E6 for ; Mon, 2 Apr 2012 20:51:38 -0400 (EDT) Received: from G1W0401.americas.hpqcorp.net (g1w0401.americas.hpqcorp.net [16.236.31.6]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g1t0028.austin.hp.com (Postfix) with ESMTPS id 2692B1C0FC; Tue, 3 Apr 2012 00:51:38 +0000 (UTC) Received: from G9W0367G.americas.hpqcorp.net (16.216.193.231) by G1W0401.americas.hpqcorp.net (16.236.31.6) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 3 Apr 2012 00:50:54 +0000 Received: from G9W0723.americas.hpqcorp.net ([169.254.3.192]) by G9W0367G.americas.hpqcorp.net ([16.216.193.231]) with mapi id 14.01.0289.001; Tue, 3 Apr 2012 00:50:54 +0000 From: "Kennedy, Smith (Wireless Architect)" To: Michael Sweet Subject: Re: [IPP] IPP and HTTP/1.1 pipelining - thoughts or positions? Thread-Topic: [IPP] IPP and HTTP/1.1 pipelining - thoughts or positions? Thread-Index: AQHNDsFw0dQ0yW6WDUWHDShDVoPDVA== Date: Tue, 3 Apr 2012 00:50:54 +0000 Message-ID: <70967D45-A1EB-4677-A7DD-C37DF89411CD@hp.com> References: <24AA8057-818C-4377-9CAD-BF06D17C20C1@hp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [15.193.128.118] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: EF81B79637.A7D13 X-pwg-MailScanner-From: ipp-bounces@pwg.org Thanks as always for your quick replies and help, Mike! Smith On 2012-03-30, at 5:22 PM, Michael Sweet wrote: > Smith, >=20 > On Mar 30, 2012, at 3:07 PM, Kennedy, Smith (Wireless Architect) wrote: >> ... >> RFC 2616 section 9.1.2 says that the POST method is non-idempotent, for = understandable reasons. But in the context of IPP, it seems to me that the= idempotency of the IPP operation, not the HTTP request method, that should= be considered. For instance, the Get-Job-Status or Get-Job-Supported-Valu= es operations, and even the Set-Printer-Attributes operation as well, are a= ll idempotent as far as the Printer, Job and Subscription objects are conce= rned. >=20 > Because IPP is layered over HTTP and uses POST operations, all of the iss= ues with HTTP request processing apply whether the corresponding IPP operat= ion is idempotent or not. You just can't safely pipeline multiple IPP requ= est messages to an IPP printer since any one of those requests may fail and= close the HTTP connection (particularly for things like authentication) or= otherwise return an error that you cannot (reliably) link to a particular = request. And speaking of authentication, all IPP clients should be using t= he HTTP Expect header to elicit a 100 (continue), 401 (unauthorized), 403 (= forbidden), or 426 (upgrade) response before the IPP request message and do= cument data is sent - that also prevents pipelining from being used. >=20 > But back to your original question, we might be able to define (in IPP te= rms, not HTTP) certain IPP operations (like Get-Job-Attributes, Get-Printer= -Supported-Values) as idempotent, but others (like Set-Printer-Attributes) = specifically have side-effects that make them non-idempotent. This is one = of the reasons RFC 2616 talks about HTML forms and GET vs. POST - query for= ms using GET are OK, but forms that cause something to change/happen have t= o use POST because they are not idempotent. >=20 >> Is there an official position on pipelining for IPP that overrides the r= ecommendations for HTTP/1.1 laid out in RFC 2616 Section 8.1.2.2? >=20 >=20 > You'll find an errata to RFC 3196 (IPP Implementers Guide) on this; basic= ally, pipelining of and early responses to POST requests are not allowed, p= er RFC 2616. >=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Apr 2 22:13:28 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C7921F86FD for ; Mon, 2 Apr 2012 22:13:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.39 X-Spam-Level: X-Spam-Status: No, score=-101.39 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tt6kGEQLemHK for ; Mon, 2 Apr 2012 22:13:26 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5448F21F8546 for ; Mon, 2 Apr 2012 22:13:26 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 11E1A7971D; Tue, 3 Apr 2012 01:13:04 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by pwg.org (Postfix) with ESMTP id 9C95D7971A for ; Tue, 3 Apr 2012 01:12:43 -0400 (EDT) Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta13.emeryville.ca.mail.comcast.net with comcast id tGz41i0051eYJf8ADHCidw; Tue, 03 Apr 2012 05:12:42 +0000 Received: from LarryHP6616 ([98.210.92.38]) by omta19.emeryville.ca.mail.comcast.net with comcast id tHCh1i00l0pficJ01HCiz9; Tue, 03 Apr 2012 05:12:42 +0000 From: "larryupthegrove" To: =?iso-2022-jp?B?J05pc2hpbm8bJEIhJBsoQlRldHN1eWEoGyRCQD5MbkUwTGkbKEIpJw==?= , "'Petrie, Glen'" , References: <079401cd1132$1c90efb0$55b2cf10$@comcast.net> In-Reply-To: Subject: RE: [IPP] A different function model for discuss Date: Mon, 2 Apr 2012 22:12:41 -0700 Message-ID: <07a501cd1158$6593c630$30bb5290$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQG75lPLYvJY7pYJogdX57gRfX0zpQIq9v7zAP2U1+WWkZ8GsA== Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0265094302==" 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: 11E1A7971D.AB068 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============0265094302== Content-Type: multipart/alternative; boundary="----=_NextPart_000_07A6_01CD111D.B93C6840" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_07A6_01CD111D.B93C6840 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120330.docx Is the document we were discussing. Other discussion notes are in the meeting minutes and BOF presentations at http://www.pwg.org/cloud/index.html Larry Upthegrove From: Nishino,Tetsuya(西野徹也) [mailto:tetsuya.nishino@dc.kyocera.com] Sent: Monday, April 02, 2012 9:25 PM To: larryupthegrove; 'Petrie, Glen'; ipp@pwg.org Subject: RE: [IPP] A different function model for discuss Hi All, Can someone send me a link so that I can understand the diagram with the print manager, the cloud printer, printers and so on? Thanks, Tetsu ========================================================= KYOCERA Document Solutions Inc. R&D Department 63, Software 1 R&D Division, Corporate Software R&D Division Tetsuya Nishino 2-14-9, Tamagawadai, Setagaya-ward, Tokyo, 158-8610 Japan Tel:+81-03-3708-3846 / Fax:+81-03-3708-0423 (tetsuya.nishino@dc.kyocera.com ) http://www.kyoceradocumentsolutions.com ========================================================= New Document Solutions for your Business. "KYOCERA Document Solutions Inc." reborn on April 1. "KYOCERA MITA Corporation" is now called " KYOCERA Document Solutions Inc." ---------------------------------------------------------------------------- - _____ From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of larryupthegrove Sent: Tuesday, April 03, 2012 9:39 AM To: 'Petrie, Glen'; ipp@pwg.org Subject: RE: [IPP] A different function model for discuss All, The reason I see for having a “Print Manager” is for the purpose of having a standard for connecting a printer (logical or physical) to the cloud provider. So the simplest implementation would reflect just a user connecting to the cloud provider. The cloud provider “owns” the printers, so there isn’t any outgoing connection to model. Examples would be Staples, Mimeo.com, Vistaprint.com Second implementation would be devices not owned by the cloud provider. Current implementations include mail protocols, FTP, IPP, route via Dropbox, Box, Google cloud print, etc. So a standard should address a common solution that works for a variety of implementations. So having a cloud print manager at , or as part of, each device makes sense to me. The third implementation would be a more robust print manager, which would control multiple devices off of a single connection. My example would be IBM InfoPrint manager or similar output manager. So I see two parts to this, one between the user and the cloud provider, and one between the cloud provider and some common point that works for multiple implementations. Since in a large number of cases the print data has to transverse into a private network, that common point should be capable of being hosted within a private network. Just my thoughts… Larry From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Monday, April 02, 2012 3:38 PM To: ipp@pwg.org Subject: [IPP] A different function model for discuss All, After today’s meeting, I thought I would try to draw a slightly different representation of the functional model diagram than what is in the current model document. In the current model it is very unclear what and where the “Cloud Print Manager” is (is in its own cloud or is it proxy (so not really a cloud service) or in the printer (so not really a cloud service)). Why does the (Print) Client “register” with the Cloud Provider instead of just using the Cloud Print Provider. In the functional model attached, I propose the more cloud centric model which places service, security and other functionality in the Cloud. The model is not specifically concerned with interfaces such as using IPP; it is meant to be more a very top level view. In the attached model the Client uses or accesses the Cloud Provider for printing services. The User interacts with the Cloud Print Provider to select a Print Service associated with the User. The Cloud Print Provider then sends Capability information (which likely has no secure information) to the Client. The Print Client creates Print Job Ticket (with a Print Content reference) which is sent to the Print Service (or Print Service Manager) for printing. The Print Service accepts (or rejects the Print Job). The Print Service prints the Print Job and sends status info to the Print Status Service. Federated printing also work quit well with this model. Glen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_07A6_01CD111D.B93C6840 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable

ftp://ft= p.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120330.docx

 

Is the document we were discussing.  Other discussion = notes are in the meeting minutes and BOF presentations at http://www.pwg.org/cloud/index.html=

 

 

= Larry Upthegrove

 

From: Nishino=1B$B!$=1B(BTetsuya(=1B$B@>LnE0Li=1B(B) [mailto:tetsuy= a.nishino@dc.kyocera.com]
Sent: Monday, April 02, 2012 9:25 PMTo: larryupthegrove; 'Petrie, Glen'; ipp@pwg.org
Subject:
RE: [IPP] A different function model for discuss

 

Hi All,

 

Can someone send me a link so that I can un= derstand the diagram with the print manager, the cloud printer, printers an= d so on?

 

Thanks,

Tetsu

 

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
KYOCERA Document Sol= utions Inc.
R&D Department 63, Software 1 R&D Division, Corporat= e Software R&D  Division

Tetsuya Nishino

2= -14-9, Tamagawadai, Setagaya-ward, Tokyo, 158-8610 Japan
Tel:+81-03-3708-3846 / Fax:+81-03-3708-0423
(tetsuya.nishino@dc.kyocera.co= m)
http://www.ky= oceradocumentsolutions.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
New Document S= olutions for your Business.
"KYOCERA Document Solutions Inc." = reborn on April 1.

=

"KYO= CERA MITA Corporation" is now called " KYOCERA Document Solutions= Inc."
------------------------------------------------------------= -----------------

<= /div>

From:<= span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf = Of larryupthegrove
Sent: Tuesday, April 03, 2012 9:39 AM
<= b>To:
'Petrie, Glen'; ipp@pwg.orgSubject: RE: [IPP] A different function model for discuss

 

A= ll,

 

The reason I see for having a =1B$B!H=1B(= BPrint Manager=1B$B!I=1B(B is for the purpose of having a standard for conn= ecting a printer (logical or physical) to the cloud provider.

 

So the simplest implementation would reflect just a user c= onnecting to the cloud provider.  The cloud provider =1B$B!H=1B(Bowns= =1B$B!I=1B(B the printers, so there isn=1B$B!G=1B(Bt any outgoing connectio= n to model.

Examples would= be Staples, Mimeo.com, Vistaprint.com

 

Seco= nd implementation would be devices not owned by the cloud provider.  C= urrent implementations include mail protocols, FTP, IPP, route via Dropbox,= Box, Google cloud print, etc.  So a standard should address a common = solution that works for a variety of implementations.  So having a clo= ud print manager at , or as part of, each device makes sense to me.

 

The third implementation would be a more robust prin= t manager, which would control multiple devices off of a single connection.=   My example would be IBM InfoPrint manager or similar output manager.=

 <= /p>

So I see two parts to this, one between the = user and the cloud provider, and one between the cloud provider and some co= mmon point that works for multiple implementations.  Since in a large = number of cases the print data has to transverse into a private network, th= at common point should be capable of being hosted within a private network.=

 <= /p>

Just my thoughts=1B$B!D=1B(B

 

Larry

 

 

From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen
<= b>Sent: Monday, April 02, 2012 3:38 PM
To: ipp@pwg.org
Subject: [IPP] A different function = model for discuss

 

All,

 

After today=1B$B!G=1B(Bs meet= ing, I thought I would try to draw a slightly different representation of t= he functional model diagram than what is in the current model document.&nbs= p; In the current model it is very unclear what and where the =1B$B!H=1B(BC= loud Print Manager=1B$B!I=1B(B is (is in its own cloud or is it proxy (so n= ot really a cloud service) or in the printer (so not really a cloud service= )).   Why does the (Print) Client =1B$B!H=1B(Bregister=1B$B!I=1B(= B with the Cloud Provider instead of just using the Cloud Print Provider. <= o:p>

 

In the functional model attached, I propose the more cloud centric model = which places service, security and other functionality in the Cloud. The mo= del is not specifically concerned with interfaces such as using IPP; it is = meant to be more a very top level view.  In the attached model the Cli= ent uses or accesses the Cloud Provider for printing services.  The Us= er interacts with the Cloud Print Provider to select a Print Service associ= ated with the User.  The Cloud Print Provider then sends Capability in= formation (which likely has no secure information) to the Client.  The= Print Client creates Print Job Ticket (with a Print Content reference) whi= ch is sent to the Print Service (or Print Service Manager) for printing.&nb= sp; The Print Service accepts (or rejects the Print Job).  The Print S= ervice prints the Print Job and sends status info to the Print Status Servi= ce.   Federated printing also work quit well with this model.

 

= Glen

 


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


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_07A6_01CD111D.B93C6840-- --===============0265094302== 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 --===============0265094302==-- From ipp-bounces@pwg.org Tue Apr 3 17:23:38 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A981D21F8646 for ; Tue, 3 Apr 2012 17:23:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVsBGNubJ8Kz for ; Tue, 3 Apr 2012 17:23:36 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1672921F8643 for ; Tue, 3 Apr 2012 17:23:36 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 68DA779717; Tue, 3 Apr 2012 20:23:18 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by pwg.org (Postfix) with ESMTP id 2992379716 for ; Tue, 3 Apr 2012 20:23:01 -0400 (EDT) Received: by wibhr14 with SMTP id hr14so26177wib.11 for ; Tue, 03 Apr 2012 17:23:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qCR1VZA35AlGsHUllF7mbfWaDfYBgiWnMVsvD04bPSM=; b=XbBqCQ0MxQUaTBonoAuYEd8Y0ZmdCQtN5S8pbFPJAIids1XCZHKQzibUEkXNKvRbd9 KoDqogWaPptE/uYjtIImCQeF5RxXDYEkMKJiEP0e2Tb7JmPRuk4qOE4TVbhc8ikBKjgT kMdCFMEmM9UiZAJxz+wgpsUhJsHC8zrvTADfrKmNu43BBs+L7+yTbtQ1tSviRZHusAgb 3c3htxkXDtn38WTzQ6ozJp0xCrI43XYQdHWvnfqFxUp+9qQhPWEOFBIhkU1X+NvEesnI 4Sy1TsdOsUvY/GxUoCpm0RhPDu9R8/Y/TSwXPxdXiyEqMTkTq6mPDoibPk+ZaUoVYt2P id7w== MIME-Version: 1.0 Received: by 10.180.103.134 with SMTP id fw6mr518428wib.0.1333498980897; Tue, 03 Apr 2012 17:23:00 -0700 (PDT) Received: by 10.223.120.11 with HTTP; Tue, 3 Apr 2012 17:23:00 -0700 (PDT) Date: Tue, 3 Apr 2012 20:23:00 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Pat Fleming , Michael R Sweet , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] LDAP Printer Schema (3 April 2012) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0409517858==" 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: 68DA779717.AAFEA X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0409517858== Content-Type: multipart/alternative; boundary=f46d0443044210925904bccf6de4 --f46d0443044210925904bccf6de4 Content-Type: text/plain; charset=ISO-8859-1 Hi, Pat - we'll review this version briefly next week at the PWG IPP teleconference at 3-5pm EDT Monday 9 April 2012 and in more detail at the PWG/Open Printing Summit during the IPP WG session 1-5pm PDT 25 April 2012. We're still not assigning OIDs to the few new attributes, because we're waiting for the chosen set to stabilize (at April PWG/OPS meeting). I've just posted a second Internet-Draft of LDAP Schema for PrinterServices to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ldap-printer-schema-01-20120403.txt - plaintext Internet-Draft format (warning - contains explicit formfeed characters) ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ldap-printer-schema-01-20120403.pdf - line numbered PDF of plaintext - use this version for review, please This document has already been accepted and posted to the IETF I-D repository. This document was created by revising the original LDAP Schema for Printer Services [RFC3712]. This version adds new IPP directory attributes proposed in Table 1 of section 4.1 Printer Description Attributes Used in Discovery in the latest draft of PWG IPP Everywhere 1.0. Cheers, - Ira --------------------------------------- Change History: 3 April 2012 - draft-mcdonald-ldap-printer-schema-01.txt - Second draft - for IEEE-ISTO PWG IPP Everywhere project - Global - changed [IPPEVE1] to [PWG5100.EVE] and [IPPJPS3] to [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review. - Revised section 1.1, to add printer-charge-info-uri and printer-uuid to discussion of URI syntax, per IEEE-ISTO PWG IPP WG review. - Revised section 1.2 and section 1.3, to add printer-device-id to discussions of equality and substring matching, per IEEE-ISTO PWG IPP WG review. - Revised section 3.2, section 4, and section 7.2, to delete redundant printer-organization and printer-organizational-unit (already covered by 'O' and 'OU'), per IEEE-ISTO PWG IPP WG review. - Revised section 3.2, section 4, and section 7.2, to add missing printer-charge-info, per IEEE-ISTO PWG IPP WG review. - Revised section 3.5, section 4, and section 7.2, to rename printer-ipp-extensions-supported to printer-ipp-features-supported, per IEEE-ISTO PWG IPP WG review. - Revised numerous section 4 subsections, to add references to [IANAIPP] or [RFC3805] as appropriate for enumerations and keywords, per IEEE-ISTO PWG IPP WG review. - Revised section 4.2, to add 'negotiate' as value for 'auth' and references to [PWG5100.JPS3], [RFC4559], and [IANAIPP], per IEEE-ISTO PWG IPP WG review. - Revised section 4.2, to use 'example.com' for all DNS names, per IEEE-ISTO PWG IPP WG review. - Revised section 4.22 and section 4.23, to add normative reference to PWG Media Standardized Names [PWG5101.1], per IEEE-ISTO PWG IPP WG review. - Revised section 4.24, to divide notes into two separate paragraphs, per IEEE-ISTO PWG IPP WG review. - Revised section 4.31, section 4.32, and section 4.33, to change 'Values ... include' to 'Values ... are' (i.e., closed set), per IEEE-ISTO PWG IPP WG review. - Revised section 4.35 printer-device-id, to add warning about ordering of required key/value pairs (first) and truncation only at key/value pair boundaries for interoperability, per IEEE-ISTO PWG IPP WG review. - Revised section 4, to add printer-charge-info from [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review. - Revised section 4.38 printer-geo-location, to change 'should' to 'must' for conformance to [RFC5870], per IEEE-ISTO PWG IPP WG review. - Revised section 4.39, to change printer-ipp-extensions-supported to printer-ipp-features-supported per [PWG5100.JPS3] and add examples, per IEEE-ISTO PWG IPP WG review. - Revised section 4 subsection printer-uuid, to change 'should' to 'must' for conformance to [RFC4122], per IEEE-ISTO PWG IPP WG review. - Revised section 10 References, to update out-of-date references. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d0443044210925904bccf6de4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Pat - we'll review this version briefly next week at the PWG= IPP teleconference
at 3-5pm EDT Monday 9 April 2012 and in more detail = at the PWG/Open Printing
Summit during the IPP WG session 1-5pm PDT 25 = April 2012.=A0 We're still not
assigning OIDs to the few new attributes, because we're waiting for the= chosen
set to stabilize (at April PWG/OPS meeting).
=A0
I've = just posted a second Internet-Draft of LDAP Schem= a for Printer Services to:

=A0ftp://ftp.pwg.org/pub/pwg/ipp/wd= /draft-mcdonald-ldap-printer-schema-01-20120403.txt
=A0- plaintext Internet-Draft format (warning - contains explicit formfeed= characters)

=A0ftp://ftp.pwg.org/pub/pwg/ipp/wd= /draft-mcdonald-ldap-printer-schema-01-20120403.pdf
=A0- line numbered PDF of plaintext - use this version for review, please<= br>
This document has already been accepted and posted to the IETF I-D r= epository.

This document was created by revising the original LDAP<= /span> Schema for Printer
Services [RFC3712].=

This version adds new IPP directory attributes proposed in Table 1 = of section 4.1
Printer Description Attributes Used in Discovery = in the latest draft of PWG IPP
Everywhere 1.0.

Cheers,
- Ira

----------------------------= -----------
Change History:

=A0=A0 3 April 2012 - draft-mcdonald-= ldap-printer-schema-01.txt
=A0=A0 - Second draft - for IEEE-ISTO PWG IP= P Everywhere project

=A0=A0 - Global - changed [IPPEVE1] to [PWG5100.EVE] and [IPPJPS3] to=A0=A0 [PWG5100.JPS3], per IEEE-ISTO PWG IPP WG review.=A0

=A0=A0= - Revised section 1.1, to add printer-charge-info-uri and
=A0=A0 printe= r-uuid to discussion of URI syntax, per IEEE-ISTO PWG IPP WG
=A0=A0 review.=A0

=A0=A0 - Revised section 1.2 and section 1.3, to = add printer-device-id to
=A0=A0 discussions of equality and substring ma= tching, per IEEE-ISTO PWG IPP
=A0=A0 WG review.=A0

=A0=A0 - Revi= sed section 3.2, section 4, and section 7.2, to delete
=A0=A0 redundant printer-organization and printer-organizational-unit
= =A0=A0 (already covered by 'O' and 'OU'), per IEEE-ISTO PWG= IPP WG review.=A0

=A0=A0 - Revised section 3.2, section 4, and sec= tion 7.2, to add missing
=A0=A0 printer-charge-info, per IEEE-ISTO PWG IPP WG review.=A0

=A0= =A0 - Revised section 3.5, section 4, and section 7.2, to rename
=A0=A0 = printer-ipp-extensions-supported to printer-ipp-features-supported,
=A0= =A0 per IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised numerous section 4 subsections, to add references to=A0=A0 [IANAIPP] or [RFC3805] as appropriate for enumerations and keyword= s,
=A0=A0 per IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised = section 4.2, to add 'negotiate' as value for 'auth' and
=A0=A0 references to [PWG5100.JPS3], [RFC4559], and [IANAIPP], per IEEE-IST= O
=A0=A0 PWG IPP WG review.=A0

=A0=A0 - Revised section 4.2, to = use 'example.com' for all DNS na= mes, per
=A0=A0 IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised section 4.2= 2 and section 4.23, to add normative reference
=A0=A0 to PWG Media Stand= ardized Names [PWG5101.1], per IEEE-ISTO PWG IPP WG
=A0=A0 review.=A0
=A0=A0 - Revised section 4.24, to divide notes into two separate para= graphs,
=A0=A0 per IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised section= 4.31, section 4.32, and section 4.33, to change
=A0=A0 'Values ...= =A0 include' to 'Values ...=A0 are' (i.e., closed set), per
= =A0=A0 IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised section 4.35 printer-device-id, to add warning about=A0=A0 ordering of required key/value pairs (first) and truncation only a= t
=A0=A0 key/value pair boundaries for interoperability, per IEEE-ISTO P= WG IPP
=A0=A0 WG review.=A0

=A0=A0 - Revised section 4, to add printer-cha= rge-info from [PWG5100.JPS3],
=A0=A0 per IEEE-ISTO PWG IPP WG review.= =A0

=A0=A0 - Revised section 4.38 printer-geo-location, to change &= #39;should' to
=A0=A0 'must' for conformance to [RFC5870], per IEEE-ISTO PWG IPP W= G review.

=A0=A0 - Revised section 4.39, to change printer-ipp-exten= sions-supported to
=A0=A0 printer-ipp-features-supported per [PWG5100.JP= S3] and add examples,
=A0=A0 per IEEE-ISTO PWG IPP WG review.=A0

=A0=A0 - Revised section= 4 subsection printer-uuid, to change 'should' to
=A0=A0 'mu= st' for conformance to [RFC4122], per IEEE-ISTO PWG IPP WG review.
<= br>=A0=A0 - Revised section 10 References, to update out-of-date references= .=A0


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d0443044210925904bccf6de4-- --===============0409517858== 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 --===============0409517858==-- From ipp-bounces@pwg.org Fri Apr 6 08:18:22 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A614321F857A for ; Fri, 6 Apr 2012 08:18:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFEBjDDVQilv for ; Fri, 6 Apr 2012 08:18:21 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B3F3621F855F for ; Fri, 6 Apr 2012 08:18:21 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 71A0A795F4; Fri, 6 Apr 2012 11:18:03 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 9BC6E795E2 for ; Fri, 6 Apr 2012 11:17:46 -0400 (EDT) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2200ACMCSAFG01@mail-out.apple.com> for ipp@pwg.org; Fri, 06 Apr 2012 08:17:45 -0700 (PDT) X-AuditID: 11807136-b7f056d0000026ba-f3-4f7f090f17eb Received: from [17.151.78.103] (Unknown_Domain [17.151.78.103]) (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 DC.37.09914.8190F7F4; Fri, 06 Apr 2012 08:17:45 -0700 (PDT) From: Michael Sweet Date: Fri, 06 Apr 2012 08:17:46 -0700 To: "" Message-id: <4C450321-6259-419A-BCFD-BCDDBA81C821@apple.com> X-Mailer: Apple Mail (2.1447) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUiON0vXVeSs97f4MEKdYtj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZTxdOp2x4LR0xbON/5kaGP+LdzFyckgImEgs fD+HCcIWk7hwbz1bFyMXh5DAVCaJowtPsIAk2ATUJH5P6mMFsZkFEiT2nW0Cs1kEVCR2LlnM DmILA9VM+vWUGcQWEVCU+DltOyOIzStgI3G0fQ47hK0n8fjTH6CZHEDLZCUenKqawMg9C8nU WUiqIOLaEssWvmaeBdTBLKAjMXkhI6owhP3x/BGmBYxsqxgFi1JzEisNTfUSCwpyUvWS83M3 MYICq6HQbAfjjr9yhxgFOBiVeHhPbq31F2JNLCuuzD3EKMHBrCTC+/t1nb8Qb0piZVVqUX58 UWlOavEhRmkOFiVx3nDtKn8hgfTEktTs1NSC1CKYLBMHp1QDo5qSUbbaDqnrfwL4V1id9phl 79Kju/F05D2nxZGPRb58yVweVOmeuu/AqbM7U0KCzro9u3d/S4RYP2eCUuWxMuUSDxGLky2b vZ74Sh63lmu+f/Bgr0ntbIHNK3fJczx9vljTZ/7iPfuFtNuWmdz+X3DS86JcvMnbnqerZtlL zordF79YNUqHR4mlOCPRUIu5qDgRAFNFYkkoAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Prototype experience for JPS3 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1335632187==" 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: 71A0A795F4.A8A08 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1335632187== Content-type: multipart/alternative; boundary="Boundary_(ID_+A2shMgCO3ZiZJGHyZKTyQ)" --Boundary_(ID_+A2shMgCO3ZiZJGHyZKTyQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, This is Apple's notice of prototyping of the current draft of the IPP Job and Printer Extensions - Set 3 (JPS3) specification as posted here: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120327.pdf Apple has prototyped all of the proposed extensions and has shipped many of them since CUPS 1.4. The only implementation issue not directly addressed by the current JPS3 specification is how printers and clients interpret colorant values ("colorantname") in the printer-supply attribute. This issue was identified during the original discussions for printer-supply (vs. the CUPS marker-xxx implementation) and can be addressed by referencing PWG 5101.1 (MSN1) for colorantname values, including the proposed additions from the current MSN2 draft, and finishing the update of 5101.1 (MSN2) to support a full set of reference color names and vendor colors. __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_+A2shMgCO3ZiZJGHyZKTyQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

T= his is Apple's notice of prototyping of the current draft of the IPP Job an= d Printer Extensions - Set 3 (JPS3) specification as posted here:


Apple has prototyped all of the propos= ed extensions and has shipped many of them since CUPS 1.4. The only impleme= ntation issue not directly addressed by the current JPS3 specification is h= ow printers and clients interpret colorant values ("colorantname") in the p= rinter-supply attribute. This issue was identified during the original disc= ussions for printer-supply (vs. the CUPS marker-xxx implementation) and can= be addressed by referencing PWG 5101.1 (MSN1) for colorantname values, inc= luding the proposed additions from the current MSN2 draft, and finishing th= e update of 5101.1 (MSN2) to support a full set of reference color names an= d vendor colors.

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_+A2shMgCO3ZiZJGHyZKTyQ)-- --===============1335632187== 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 --===============1335632187==-- From ipp-bounces@pwg.org Fri Apr 6 08:26:31 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E08A21F84D5 for ; Fri, 6 Apr 2012 08:26:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.597 X-Spam-Level: X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GW5IibJBUqg7 for ; Fri, 6 Apr 2012 08:26:30 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id CB06E21F841C for ; Fri, 6 Apr 2012 08:26:29 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 45A1F795FF; Fri, 6 Apr 2012 11:26:12 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id A79A9795EF for ; Fri, 6 Apr 2012 11:25:53 -0400 (EDT) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M22008W8DIFM1O1@mail-out.apple.com> for ipp@pwg.org; Fri, 06 Apr 2012 08:25:53 -0700 (PDT) X-AuditID: 1180711d-b7f8b6d000002f13-2e-4f7f0ae36088 Received: from [17.151.78.103] (Unknown_Domain [17.151.78.103]) (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 E6.39.12051.9FA0F7F4; Fri, 06 Apr 2012 08:25:52 -0700 (PDT) Subject: Re: [IPP] WS-discovery binding for IPP Everywhere From: Michael Sweet In-reply-to: <15713B46EB868E4FB0CF6D8BFD33617E51865C69@TK5EX14MBXC110.redmond.corp.microsoft.com> Date: Fri, 06 Apr 2012 08:25:35 -0700 Message-id: <9CAE8BBE-60F7-42B8-A37A-AE12839D635A@apple.com> References: <15713B46EB868E4FB0CF6D8BFD33617E51865C69@TK5EX14MBXC110.redmond.corp.microsoft.com> To: Justin Hutchings X-Mailer: Apple Mail (2.1447) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUiON0vXZeBu97fYOJPDYtj+16yWFx7rG5x 5FusA7PH1pM/2Dxad/xl95i3eDpTAHMUl01Kak5mWWqRvl0CV8avv2dYC/60MFZ8nfqEqYHx V2kXIyeHhICJxP3pDYwQtpjEhXvr2boYuTiEBKYySaw7M5m9i5GDQ1jASmL9Jm2QGl4BPYnH n/6wgNjMAgkSb5fsYQKx2QTUJH5P6mMFsTkFEiWWXzoPZrMIqEhMf9PADlEvL9Fw5woLyEhe ARuJ05f4QcJCQGOmrr7PBmKLCGhLTHy6HWyrhICsxINTVRMY+WYhWTwLyWIIW1ti2cLXzBC2 gcTTzlesmOL6Em/ezWFawMi2ilGwKDUnsdLQWC+xoCAnVS85P3cTIyhkGwpldzDu/8l/iFGA g1GJh7doc62/EGtiWXFl7iFGCQ5mJRHe36/r/IV4UxIrq1KL8uOLSnNSiw8xSnOwKInzBmtX +QsJpCeWpGanphakFsFkmTg4pRoYl564mXiMU/32bFOZepNrVz1yp2seW23sOLed3Xbqkeea Ww4uXBvGcjl/6oKTO9ffe8Uik/nk7iqji88LBVUaVZ9P6SsP3iEdLcJ46TKTTyzj92lta7fm GM8NmfVsZtur5rfnlCvmNMocFBG6xalr637HwkpxjX9cl5Nd5MpN8sXr3bOXbpTKUGIpzkg0 1GIuKk4EAL/a7BpVAgAA 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="===============0648825866==" 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: 45A1F795FF.AA403 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0648825866== Content-type: multipart/alternative; boundary="Boundary_(ID_fQdCXMIxMZVEMqEw/tcGmg)" --Boundary_(ID_fQdCXMIxMZVEMqEw/tcGmg) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Justin, Can you provide a schema file that I can put up on the PWG web site? The n= amespace should be "http://www.pwg.org/schemas/2012/4/ipp-everywhere" to ma= tch the form we use for Semantic Model schema. Thanks! On Feb 10, 2012, at 10:20 AM, Justin Hutchings wrote: > All, > Per the discussion at this week=92s face to face, I mocked up an example = of how to do discovery of an IPP endpoint using ws-discovery. Since WS-disc= overy doesn=92t especially care what matching semantic model is used, I wou= ld propose that we just reuse the LDAP model to simplify the development ex= perience for people. The only unique descriptions we=92ll need are to estab= lish some keywords that describe the different IPP protocols, like IPP Ever= ywhere print, scan, fax, etc. That should be pretty trivial, as we just nee= d to name them and publish a schema. >=20=20 > How does this look? >=20=20 > Thanks! > Justin >=20=20 > Example probe message: > xmlns:a=3D"http://schemas.xmlsoap.org/ws/2004/08/addressing" > xmlns:d=3D"http://schemas.xmlsoap.org/ws/2005/04/discovery" > xmlns:ippe=3D"http://pwg.org/2012/08/ipp-everywhere" > xmlns:s=3D"http://www.w3.org/2003/05/soap-envelope" > > > > http://schemas.xmlsoap.org/ws/2005/04/discovery/Probe > > > uuid:0a6dc791-2be6-4991-9af1-454778a1917a > > urn:schemas-xmlsoap-org:ws:2005:04:discovery > > =20=20=20 > > ippe:Print > MatchBy=3D"http://schemas.xmlsoap.org/ws/2005/04/discovery/ldap" > > ldap:///ou=3Dengineering,o=3Dexamplecom,c=3Dus > > > > >=20=20 >=20=20 >=20=20 >=20=20 > Justin Hutchings | Program Manager | Windows\DNT\DeviceConnectivity::Prin= ting and Imaging >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_fQdCXMIxMZVEMqEw/tcGmg) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Justin,

Can you provide a schema file that I can = put up on the PWG web site?  The namespace should be "http://www.pwg.org/schemas/201= 2/4/ipp-everywhere" to match the form we use for Semantic Model schema.=

Thanks!

On Feb 10, 2012, = at 10:20 AM, Justin Hutchings <j= usthu@microsoft.com> wrote:

All,
Per the disc= ussion at this week=92s face to face, I mocked up an example of how to do d= iscovery of an IPP endpoint using ws-discovery. Since WS-discovery doesn=92= t especially care what matching semantic model is used, I would propose tha= t we just reuse the LDAP model to simplify the development experience for p= eople. The only unique descriptions we=92ll need are to establish some keyw= ords that describe the different IPP protocols, like IPP Everywhere print, = scan, fax, etc. That should be pretty trivial, as we just need to name them= and publish a schema.
 
How does this look?
 
Thanks!
Justin
 
Example probe messa= ge:
<s:Envelope
  &nb= sp;  xmlns:ippe=3D"http://pwg.o= rg/2012/08/ipp-everywhere"
   <s:Header>
     <a:Action>
      &= nbsp;</d:Scopes>
  &nb= sp;  </d:Probe>
 =   </s:Body>
 <= /s:Envelope>
 
 
 
 
Justin Hutchings | Program Manager | Windows\DNT\DeviceConn= ectivity::Printing and Imaging
 

-- 
This messa= ge has been scanned for viruses and&n= bsp;
dangerous content by&n= bsp;MailScanner, and is 
believed to be clean. ____________= ___________________________________
ipp mailing list
ipp@pw= g.org
https://www.pwg.org/mailman/li= stinfo/ipp

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_fQdCXMIxMZVEMqEw/tcGmg)-- --===============0648825866== 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 --===============0648825866==-- From ipp-bounces@pwg.org Fri Apr 6 08:35:23 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40DD821F85A0 for ; Fri, 6 Apr 2012 08:35:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PlzcidY1XVX for ; Fri, 6 Apr 2012 08:35:22 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE7E21F84B4 for ; Fri, 6 Apr 2012 08:35:19 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D5CFA79608; Fri, 6 Apr 2012 11:34:56 -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 50CEE7958D for ; Fri, 6 Apr 2012 11:34:38 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Apr 2012 08:34:37 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 6 Apr 2012 08:34:36 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Where is the Cloud Print Manager in the PWG: Cloud Model Thread-Index: Ac0UCsP3zn5IVHmfT6KR2X128w08ng== From: "Petrie, Glen" To: "Zehler, Peter" , "Ira McDonald" X-OriginalArrivalTime: 06 Apr 2012 15:34:37.0499 (UTC) FILETIME=[C66EC8B0:01CD140A] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model 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="===============0052414351==" 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: D5CFA79608.AA84F X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============0052414351== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD140A.C61F1EC8" This is a multi-part message in MIME format. ------_=_NextPart_001_01CD140A.C61F1EC8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ira, Pete, =20 I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram "is not in the cloud". Is this true? If so, where is it "located"?=20=20 =20 Glen =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CD140A.C61F1EC8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ira, Pete,

 

I believe it was stated in the last conference call that the Cloud Print Mana= ger in the cloud model diagram “is not in the cloud”.   I= s this true?  If so, where is it “located”? 

 

Glen

 


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CD140A.C61F1EC8-- --===============0052414351== 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 --===============0052414351==-- From ipp-bounces@pwg.org Fri Apr 6 09:01:16 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2101221F84E4 for ; Fri, 6 Apr 2012 09:01:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.298 X-Spam-Level: X-Spam-Status: No, score=-101.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWw5K0T4oa-3 for ; Fri, 6 Apr 2012 09:01:15 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4823521F84DC for ; Fri, 6 Apr 2012 09:01:15 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 731D179638; Fri, 6 Apr 2012 12:00:50 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 0DE827962C; Fri, 6 Apr 2012 12:00:31 -0400 (EDT) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2200AT3F3SFGC1@mail-out.apple.com>; Fri, 06 Apr 2012 09:00:15 -0700 (PDT) X-AuditID: 11807130-b7f5e6d000000682-d9-4f7f130fd871 Received: from da0704a-dhcp108.apple.com (da0704a-dhcp108.apple.com [17.197.43.108]) (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 F3.DA.01666.F031F7F4; Fri, 06 Apr 2012 09:00:15 -0700 (PDT) Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model From: Michael Sweet In-reply-to: Date: Fri, 06 Apr 2012 09:00:26 -0700 Message-id: References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1447) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUieFQ7R5dfuN7f4MwbEYvXr5ayW1zefoDV YvvZXywWx/a9ZLE48i3WouPJSlYHNo+tJ3+weRycP4vdY+esu+we8xZPZ/JYfmo9WwBrFJdN SmpOZllqkb5dAlfGrO+bGAv63SpuX21maWA8atPFyMkhIWAi8WJvMxuELSZx4d56IJuLQ0hg FZPEx6kHWEASwgLeEt/ffWMFsXkF9CQef/oDFmcWSJCYfHc1mM0moCbxe1IfWA2ngJfE1fe/ mEFsFgEVicWLp7KDDGUWaGWUeNX4iwlikI3Et77jYJuFBDwlln+aBdYsIqAv8enjZqAaDqCL ZCUenKqawMg3C8nqWUhWQ9jaEssWvmaGsA0knna+YsUU15d4824O0wJGtlWMgkWpOYmVhoZ6 iQUFOal6yfm5mxhBod5QaLCDce1P/kOMAhyMSjy8P7nr/YVYE8uKK3MPMUpwMCuJ8P5+Xecv xJuSWFmVWpQfX1Sak1p8iFGag0VJnDdEu8pfSCA9sSQ1OzW1ILUIJsvEwSnVwNjw0dzr1pI1 LYJiS84VPa693+Opuf1D84F69tuLqg/dY5j54PbefJ7N6a4HY36qtbbzfJ+fLrfk8DzDzggv n6TMgohr23s8DMxPlry1Pp7v8bL+pdnOTKc+w6plWxV284TMOXv30/J93zNj7k3YK/SMLXDZ dhV5R1n/7DefXz5la9hUxXMy55ASS3FGoqEWc1FxIgB9GBpgcQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, "cloud@pwg.org" X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0166032217==" 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: 731D179638.A917F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0166032217== Content-type: multipart/alternative; boundary="Boundary_(ID_ZbS583UhIYXOOTKRX/xaig)" --Boundary_(ID_ZbS583UhIYXOOTKRX/xaig) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable [Adding cloud@pwg.org since this is a cloud discussion] Glen, In the original BOF-generated functional model, the Cloud Print Manager is = either located in the Printer or attached to the Printer (e.g. in the local= print server). The Cloud Print Manager manages communications between the= lower-level printer interface and the Cloud Print Provider. Based on our last telecon, we have introduced a Cloud Print Service into th= e model which is the service in/under the Cloud Print Provider (which acts = as a System Control Service in the Semantic Model sense) that manages the j= obs/queue in the cloud for the Cloud Print Manager. The rough ASCII art di= agram in my mind looks like this: Cloud Print Provider Client <---> Cloud Print Service <---> Cloud Print Manager <---> Pr= inter(s) Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Pro= vider and corresponding Cloud Print Service, but never directly to each oth= er, and only the Cloud Print Manager actually talks directly with the Print= er(s) (physical or logical) it is registering/sharing with the Cloud Print = Provider/Service. There can potentially be multiple logical or physical printers behind the C= loud Print Manager (think traditional fan-out configurations and reprograph= ic services) and those printers *may* be addressable using the IPP/SM outpu= t device attributes/elements, but there is only a single Cloud Print Servic= e per Cloud Print Manager and to the Client it will appear to be a single "= queue" with one or more output devices associated with it. On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" wro= te: > Ira, Pete, >=20=20 > I believe it was stated in the last conference call that the Cloud Print = Manager in the cloud model diagram =93is not in the cloud=94. Is this tru= e? If so, where is it =93located=94?=20 >=20=20 > Glen >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_ZbS583UhIYXOOTKRX/xaig) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable
[Adding cloud@pwg.org sinc= e this is a cloud discussion]

Glen,

= In the original BOF-generated functional model, the Cloud Print Manager is = either located in the Printer or attached to the Printer (e.g. in the local= print server).  The Cloud Print Manager manages communications betwee= n the lower-level printer interface and the Cloud Print Provider.

Based on our last telecon, we have introduced a Cloud Print= Service into the model which is the service in/under the Cloud Print Provi= der (which acts as a System Control Service in the Semantic Model sense) th= at manages the jobs/queue in the cloud for the Cloud Print Manager.  T= he rough ASCII art diagram in my mind looks like this:

=

               =    Cloud Print Provider
    Client  <= ;--->  Cloud Print Service  <--->  Cloud Print Mana= ger <---> Printer(s)

Thus, Clients and Cloud= Print Managers talk directly to the Cloud Print Provider and corresponding= Cloud Print Service, but never directly to each other, and only the Cloud = Print Manager actually talks directly with the Printer(s) (physical or logi= cal) it is registering/sharing with the Cloud Print Provider/Service.
=

There can potentially be multiple logical or physical p= rinters behind the Cloud Print Manager (think traditional fan-out configura= tions and reprographic services) and those printers *may* be addressable us= ing the IPP/SM output device attributes/elements, but there is only a singl= e Cloud Print Service per Cloud Print Manager and to the Client it will app= ear to be a single "queue" with one or more output devices associated with = it.


On Apr 6, 2012, at 8:= 34 AM, "Petrie, Glen" <gle= n.petrie@eitc.epson.com> wrote:

Ira, Pete,
 
I believe it was = stated in the last conference call that the Cloud Print Manager in the clou= d model diagram =93is not in the cloud=94.   Is this true?  = If so, where is it =93located=94? 
 
Glen
 

-- 
This message has been scanned for viruses and 
dangerous content by Mail= Scanner, and is <= br>believed to be clean. _______________________________________________ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp
<= /div>
_______________________________________= ___________
Michael Sweet, Senior Printing System Engineer, = PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_ZbS583UhIYXOOTKRX/xaig)-- --===============0166032217== 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 --===============0166032217==-- From ipp-bounces@pwg.org Fri Apr 6 10:35:48 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1328421F85F8 for ; Fri, 6 Apr 2012 10:35:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.599 X-Spam-Level: X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[AWL=-0.998, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_HTML_MOSTLY=0.001, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEsXNXTvvNG3 for ; Fri, 6 Apr 2012 10:35:43 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id C6CAF21F8625 for ; Fri, 6 Apr 2012 10:35:42 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9878879657; Fri, 6 Apr 2012 13:35:02 -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 919A879635; Fri, 6 Apr 2012 13:34:42 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Apr 2012 10:34:41 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Date: Fri, 6 Apr 2012 10:34:40 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Thread-Index: Ac0UDmfroXd7RTGCRL2eJM2nnWgpeAAAF4dg References: From: "Petrie, Glen" To: "Michael Sweet" X-OriginalArrivalTime: 06 Apr 2012 17:34:41.0765 (UTC) FILETIME=[8C828950:01CD141B] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1093157991==" 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: 9878879657.A9DDC X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1093157991== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD141B.8C41D23C" This is a multi-part message in MIME format. ------_=_NextPart_001_01CD141B.8C41D23C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike, =20 Thanks for the update. I was reviewing the diagram again and I had noted there was no actual print entity "in the cloud"; that is, as an SAAS in cloud terminology; so adding the Cloud Print Service at least provides a cloud print SAAS. =20 =20 Some more discussion ---------- =20 I am still having a problem with the use of a Cloud Print Manager (in the printer) concept (an the name) in the general context of being a cloud citizen and with associating a User with an individual Print Service (Printers). That is, it is not modeled from User's, use-case or Cloud Provider developers' point of view. As currently defined, the current Cloud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to=20 =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Printer =20 With """"""maybe""""" the Printer =3D [ Cloud Print Manager <---> Printer(s) ] as seen from Cloud Print Provider =20 Actually, I see no reason to add the Print qualifier to the Provider; that is, =20 Cloud Provider Client <---> Cloud Print Service <---> Printer =20 This model states that a Client, as a proxy for the User, can access a Print Service, of the User's Cloud Provider, to print to a User's register print device.=20 =20 This model can be used to represent several different solutions or implementations: =20 1. The "Cloud Provider" is Print Cloud (like HP's or Epson's or) Print Cloud Provider Client <---> Cloud Print Service <---> Printer a. A good and bad model - requires other Cloud Solution to federate with Print Cloud Provider. This would be a big development effort for print vendors.=20 =20 =20 =20 2. Cloud Print Services are integrated into a Cloud Provider like Google Cloud Cloud Provider Client <---> Cloud Print Service <---> Printer a. Again, good and bad. Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason. =20 =20 =20 3. The Cloud Print Service is a "mini-cloud" or a "plug-in cloud" (but still in the Cloud) that is callable by a Cloud Provider.=20 =20 Cloud Provider Client <---> \ \=20=20=20=20=20=20=20=20=20=20=20 \ \ \ Cloud Print Service <---> Printer Where there is cloud around both Cloud Print and Cloud Print Service =20 a. Yes, this looks like model in the current specification but with some slight differences. i. The Cloud Print Services are in the cloud; thus, they are cloud SAAS=20 1. Yes, the Print Service could be in the physical printer but virtually linked ("registered") in the Cloud ii. A printer is associated with a single Cloud Print Service 1. From the User's and the Cloud Provider's point-of-view, one Print Service is associated with one Printer. The User and Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer.=20=20 a. Internally, an individual "Print Service" can support 2, 700,039 Printers; that is something the print vendor does as part of their implementation detail. It will not affect the API's the Cloud Provider developers uses to print to the printer. And has nothing to do with the PWG Cloud Print specification. 2. From the User's and the Cloud Provider's point-of-view, one Print Service (associated with one Printer) has its own queue.=20=20=20 a. If a print vendor wants to have individual queues (the "bucket" of Print Jobs) for each printer or have one giant queue (a big "bucket") that individual printers pull jobs from, this again, is a print vendor implementation detail. And has nothing to do with the PWG Cloud Print specification. iii. =46rom the Cloud Provider's point-of-view, the above definitions makes all Cloud Print Service interfaces look the same; that it, 1. An individual Printer is registered and has an associated a single Print Service 2. The Cloud Provider only talks to the Printer's Print Service for all APIs and actions.=20 3. Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented) iv. Thus, the goal of the PWG Cloud activity is to define the API's and data for the Cloud Provider to/from a Cloud Print Service 1. I know - use IPP a. I don't think IPP will be used by everyone. (Who is using it now for Cloud?) What "will be used" is the PWG:PJT, which does not require IPP to be useful. PWG:PJT make federation of the Print Jobs very simple. In general PWG:PJT is a perfect candidate for cloud print. =20 So the final model is something like =20 Cloud Provider |------- a Directory/Registry of Vendor Print Clouds Client <---> \ \ < -------------------- register Printers (and its Print Service) to a User=20 \ \ \ Vendor M Print Cloud \ Vendor N Print Cloud Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer =20 glen =20 =20 =20 =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com]=20 Sent: Friday, April 06, 2012 9:00 AM To: Petrie, Glen Cc: Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 [Adding cloud@pwg.org since this is a cloud discussion] =20 Glen, =20 In the original BOF-generated functional model, the Cloud Print Manager is either located in the Printer or attached to the Printer (e.g. in the local print server). The Cloud Print Manager manages communications between the lower-level printer interface and the Cloud Print Provider. =20 Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII art diagram in my mind looks like this: =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Cloud Print Manager <---> Printer(s) =20 Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud Print Provider/Service. =20 There can potentially be multiple logical or physical printers behind the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IPP/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a single "queue" with one or more output devices associated with it. =20 =20 On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" wrote: Ira, Pete, =20 I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram "is not in the cloud". Is this true? If so, where is it "located"?=20 =20 Glen =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CD141B.8C41D23C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Mike,

 

Thanks for the update.   I= was reviewing the diagram again and I had noted there was no actual print entit= y “in the cloud”; that is, as an SAAS in cloud terminology; so adding the C= loud Print Service at least provides a cloud print SAAS.

 

 

Some more discussion ----------=

 

I am still having a problem with the= use of a Cloud Print Manager (in the printer) concept (an the name) in the gene= ral context of being a cloud citizen and with associating a User with an indivi= dual Print Service (Printers).  That is, it is not modeled from User’= s, use-case or Cloud Provider developers’ point of view.  As curren= tly defined, the current Cloud Print Manager is an artifact of a particular implementati= on (like DocuPrint; maybe even CUPS) for a fan out with a single controller (P= rint Servcie?); from a reference model or architecture point of view it should n= ot matter if there is such an entity providing this function.  This means your simple diagram reduces to

 

 

                  &nbs= p;      Cloud Print Provider

    Client  <--->  Cloud Print Service &l= t;---> Printer

 

With “”””””maybe””&= #8221;”” the Printer =3D [ Cloud Print Manager <---> Printer(s) ]  as see= n from Cloud Print Provider

 

Actually, I see no reason to add the Print qualifier to the Provide= r; that is,

 

                  &nbs= p;          Cloud Provider

    Client  <--->  Cloud Print Service &l= t;---> Printer

 

This model states that a Client, as a proxy for the User, can access a Print Service, of the User’s Cloud Provider, to print to a User’s register print device.

 

This model can be used to represent several different solutions or implementations:

 

  1. The “Cloud Provider” is Print Cloud (like HP’s or Epson&= #8217;s or)

                  &nbs= p;       Print Cloud Provider

    Client  <--->  Cloud Print Service &l= t;---> Printer

    1. A good and bad model – requires other Cloud Solution to federate = with Print Cloud Provider.   This would be a big development eff= ort for print vendors.

 

 

 

  1. Cloud Print Services are integrated into a Cloud Provider like Google Cloud<= o:p>

                  &nbs= p;          Cloud Provider

    Client  <--->  Cloud Print Service &l= t;---> Printer

    1. Again, good and bad.   Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason.

 

 

 

  1. The Cloud Print Service is a “mini-cloud” or a “plug-in cloud” (but still in the Cloud) that is callable by a Cloud Provider.

 

                  &nbs= p;          Cloud Provider

    Client  <--->  &nb= sp; \           &nbs= p; \          

        =             &nb= sp;         \   &nbs= p;      =20  \

  \ Cloud Print Service <---> Printer=

Where there is cloud around both Cloud Print and= Cloud Print Service

 

    1. Yes, this looks like model in the current specification but with some slig= ht differences.

      =             &nb= sp;            =             &nb= sp;            =        i.      The Cloud Print Services are in the cloud; thus, they are cloud SAAS

1.      = Yes, the Print Service could be in the physical printer but virtually linked (“= ;registered”) in the Cloud

      =             &nb= sp;            =             &nb= sp;            =      ii.      A printer is associated with a sin= gle Cloud Print Service

1.      = >From the User’s and the Cloud Provider’s point-of-view, one Print Service is associat= ed with one Printer.   The User and Cloud Provider developers never = know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there= an associated Print Services for a specific Printer.  

a.      = = Internally, an individual “Print Service” can support 2, 700,039 Printers; = that is something the print vendor does as part of their implementation detail.   It will not affect the API’s the Cloud Provider developers uses to print to the printer.  And has nothing to do with t= he PWG Cloud Print specification.

2.      = >From the User’s and the Cloud Provider’s point-of-view, one Print Service (associated with one Printer) has its own queue.   <= /p>

a.      = = If a print vendor wants to have individual queues (the “bucket” of Print J= obs) for each printer or have one giant queue (a big “bucket”) that = individual printers pull jobs from, this again, is a print vendor implementation detai= l.   And has nothing to do with the PWG Cloud Print specification.=

      =             &nb= sp;            =             &nb= sp;            =    iii.      From the Cloud Provider’s point-of-view, the above definitions makes all Cloud Print Service interfac= es look the same; that it,

1.      = An individual Printer is registered and has an associated a single Print Service

2.      = The Cloud Provider only talks to the Printer’s Print Service for all APIs and actions.

3.      = Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented)

      =             &nb= sp;            =             &nb= sp;            =    iv.      Thus, the goal of the PWG Cloud ac= tivity is to define the API’s and data for the Cloud Provider to/from a Cloud Print Service

1.      = I know – use IPP

a.      = = I don’t think IPP will be used by everyone.   (Who is using it now for Cl= oud?)  What “will be used” is the PWG:PJT, which does not require IPP to be useful.   PWG:PJT make federation of the Print Jobs very simple.  In general PWG:PJT is a perfect candidate for cloud print.

 

So the final model is something like=

 

                  &nbs= p;          Cloud Provider      &= nbsp;           &nbs= p; |------- a Directory/Registry of Vendor Print Clouds

    Client  <--->  &nb= sp; \           &nbs= p; \ < -------------------- register Printers (and its Print Service) to a Us= er

        =             &nb= sp;         \   &nbs= p;      =20  \

            =             &nb= sp;             = ;\ Vendor M Print Cloud          =             &nb= sp;             = ;\ Vendor N Print Cloud

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

            =             &nb= sp;            =            Print Service <---> Printer         = ;            &n= bsp;            = ;          Print Service <---> Printer

 

glen

 

 

 

 


From: Michael = Sweet [mailto:msweet@apple.com]
Sent: Friday, April 06, 2012= 9:00 AM
To: Petrie, Glen
Cc: Peter Zehler; Ira Mcdona= ld; ipp@pwg.org; cloud@pwg.org
Subject: Re: [IPP] Where is = the Cloud Print Manager in the PWG: Cloud Model

 

[Adding cloud@pwg.org since th= is is a cloud discussion]

 

Glen,

 

In the original BOF-generated functional model, the Cloud Print Man= ager is either located in the Printer or attached to the Printer (e.g. in the lo= cal print server).  The Cloud Print Manager manages communications between= the lower-level printer interface and the Cloud Print Provider.

 

Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages = the jobs/queue in the cloud for the Cloud Print Manager.  The rough ASCII art diagram= in my mind looks like this:

 

 

                   Cloud Print Provider

    Client  <--->  Cloud Print Service  <--->  Cloud Print Manager <---> Printer(s)

 

Thus, Clients and Cloud Print Managers talk directly to the Cloud P= rint Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud P= rint Provider/Service.

 

There can potentially be multiple logical or physical printers behi= nd the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IP= P/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a si= ngle "queue" with one or more output devices associated with it.<= /o:p>

 

 

On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" <glen.petrie@eitc.epson.com&g= t; wrote:



Ira, Pete,

 

I believe it was stated in the last conference call th= at the Cloud Print Manager in the cloud model diagram “is not in the cloud”.   Is this true?  If so, where is it “located”? 

 

Glen

 


-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, = and is 
believed to be clean. _______________________________________________
ipp mailing list
ipp@pwg.org
<= span style=3D'color:purple'>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. ------_=_NextPart_001_01CD141B.8C41D23C-- --===============1093157991== 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 --===============1093157991==-- From ipp-bounces@pwg.org Fri Apr 6 10:51:28 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC5421F845A for ; Fri, 6 Apr 2012 10:51:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.948 X-Spam-Level: X-Spam-Status: No, score=-101.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DY8DB9TrUzSo for ; Fri, 6 Apr 2012 10:51:25 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBF621F860B for ; Fri, 6 Apr 2012 10:51:10 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BD28A79662; Fri, 6 Apr 2012 13:50:40 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 627647951B; Fri, 6 Apr 2012 13:50:25 -0400 (EDT) MIME-version: 1.0 Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M22003K8K7VPI90@mail-out.apple.com>; Fri, 06 Apr 2012 10:50:24 -0700 (PDT) X-AuditID: 11807137-b7f716d000005684-1d-4f7f2ce0e837 Received: from da0704a-dhcp108.apple.com (da0704a-dhcp108.apple.com [17.197.43.108]) (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 C7.21.22148.0EC2F7F4; Fri, 06 Apr 2012 10:50:24 -0700 (PDT) Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model From: Michael Sweet In-reply-to: Date: Fri, 06 Apr 2012 10:50:35 -0700 Message-id: <4042A850-05EE-439B-889E-8F62CFC208AD@apple.com> References: To: "Petrie, Glen" X-Mailer: Apple Mail (2.1447) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUieFQ7R/eBTr2/wbaLmhavXy1lt7i8/QCr xfazv1gsju17yWJx5FusRceTlawObB5bT/5g8zg4fxa7x85Zd9k95i2ezuSx/NR6tgDWKC6b lNSczLLUIn27BK6MF9PWsxcs06+Yu3YhSwPjFM0uRk4OCQETiddHJzJC2GISF+6tZ+ti5OIQ EljFJNGy+QsLSEJYwFvi+7tvrCA2r4CexONPf4DiHBzMAgkSG6/5gYTZBNQkfk/qAyvhFPCS aL5zHmwmi4CKxLprm5kgyoslOhZaQEyxkfjU/hVq1Q5GicPzu9lBEiIC+hKfPkLUSwjISjw4 VTWBkW8WksWzEBaDhJkFtCWWLXzNDBHWkZi8kBFVGML+eP4I0wJGtlWMgkWpOYmVhmZ6iQUF Oal6yfm5mxhBId5QaL6DcftfuUOMAhyMSjy8gXz1/kKsiWXFlbmHGCU4mJVEeH+/rvMX4k1J rKxKLcqPLyrNSS0+xCjNwaIkzhupXeUvJJCeWJKanZpakFoEk2Xi4JRqYJyXb1fu/drhYIR2 FMvsQ28KvyxfY9j3WcL26sV7Tjz18+tdgm18Ni2ZqnNaasIDRdtgxct/GB+79h57dawl41fj 4Ui+YwmmbiuZC8q7FqrHT5v0+Zn67cqn4Ztr1/FJq+3ZpnRrCXeelfjk7psfHBK4t/3/ENG/ c83OB81Nh9xDO1Sul4fsuazEUpyRaKjFXFScCAATjgu7bQIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1691598561==" 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: BD28A79662.A94B0 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1691598561== Content-type: multipart/alternative; boundary="Boundary_(ID_g1zGOouZgUZhDo9Lv6CfcA)" --Boundary_(ID_g1zGOouZgUZhDo9Lv6CfcA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Glen, On Apr 6, 2012, at 10:34 AM, "Petrie, Glen" wrote: > ... > single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to > > > Cloud Print Provider > Client <---> Cloud Print Service <---> Printer I would be OK with this as long as we clarify in the terminology/model discussion that Printer can be Physical or Logical printer (like IPP/SM) and then provide an explicit example/use case where a Logical Printer acts as the interface with the Cloud Print Provider for an existing Physical Printer. This addresses the canonical "printer proxy" configuration that is used for Google Cloud Print and other cloud printing solutions and preserves our ability to hand-wave the implementation details between the proxy/manager and physical printer. __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_g1zGOouZgUZhDo9Lv6CfcA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable glen.petrie@eitc.epson.com> wrote:
...
<= font size=3D"3">single controller (Print Servcie?); from a reference model or arc= hitecture point of view it should not matter if there is such an entity pro= viding this function.  This means your simple diagram reduces to<= /o:p>
 
 
                &= nbsp;        Cloud Print Provider<= /span>
    Client  <--->  Cloud Print Serv= ice <---> Printer
I would be OK with this as long as we clarify in the terminology/mo= del discussion that Printer can be Physical or Logical printer (like IPP/SM= ) and then provide an explicit example/use case where a Logical Printer act= s as the interface with the Cloud Print Provider for an existing Physical P= rinter.  This addresses the canonical "printer proxy" configuration th= at is used for Google Cloud Print and other cloud printing solutions and pr= eserves our ability to hand-wave the implementation details between the pro= xy/manager and physical printer.

__________________________________________________<= /span>
= Michael Sweet, Senior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_g1zGOouZgUZhDo9Lv6CfcA)-- --===============1691598561== 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 --===============1691598561==-- From ipp-bounces@pwg.org Fri Apr 6 13:20:47 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA48511E809F for ; Fri, 6 Apr 2012 13:20:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.995 X-Spam-Level: X-Spam-Status: No, score=-100.995 tagged_above=-999 required=5 tests=[AWL=-0.395, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7z26D4W0Zawr for ; Fri, 6 Apr 2012 13:20:42 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3F29711E8098 for ; Fri, 6 Apr 2012 13:20:42 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C9E287967F; Fri, 6 Apr 2012 16:19:47 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by pwg.org (Postfix) with ESMTP id 8FE1079677 for ; Fri, 6 Apr 2012 16:19:21 -0400 (EDT) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta08.emeryville.ca.mail.comcast.net with comcast id uk8J1i0051Y3wxoA8kKL7g; Fri, 06 Apr 2012 20:19:20 +0000 Received: from LarryHP6616 ([98.210.92.38]) by omta15.emeryville.ca.mail.comcast.net with comcast id ukKK1i00b0pficJ8bkKKM9; Fri, 06 Apr 2012 20:19:20 +0000 From: "larryupthegrove" To: "'Petrie, Glen'" , "'Michael Sweet'" References: In-Reply-To: Subject: RE: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Date: Fri, 6 Apr 2012 13:19:18 -0700 Message-ID: <0c2501cd1432$8c414320$a4c3c960$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHntflnqxSNbzlmOGFUFqnaPhyXKQHKsa6yAavZ1gGWPTr2YA== Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1800005897==" 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: C9E287967F.A9FE0 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============1800005897== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C26_01CD13F7.DFF04DD0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0C26_01CD13F7.DFF04DD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Glen, I'm struggling with a number of statements, I agree the connection between the user and the cloud is one part of the model, and the other part is the connection of the cloud to a logical print something or other (within my system). Since the model started as an imaging model, I believe the cloud to print connection should also be usable for a scan to cloud, with different elements. As a user and implementer I'm focusing on where the connection to the cloud originates, and where the connection from the cloud is terminates. So where you have in the last drawing - Vendor M and Vendor N, are those print services from different print vendors or? Larry From: cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, April 06, 2012 10:35 AM To: Michael Sweet Cc: ipp@pwg.org; cloud@pwg.org Subject: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Mike, Thanks for the update. I was reviewing the diagram again and I had noted there was no actual print entity "in the cloud"; that is, as an SAAS in cloud terminology; so adding the Cloud Print Service at least provides a cloud print SAAS. Some more discussion ---------- I am still having a problem with the use of a Cloud Print Manager (in the printer) concept (an the name) in the general context of being a cloud citizen and with associating a User with an individual Print Service (Printers). That is, it is not modeled from User's, use-case or Cloud Provider developers' point of view. As currently defined, the current Cloud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to Cloud Print Provider Client <---> Cloud Print Service <---> Printer With """"""maybe""""" the Printer = [ Cloud Print Manager <---> Printer(s) ] as seen from Cloud Print Provider Actually, I see no reason to add the Print qualifier to the Provider; that is, Cloud Provider Client <---> Cloud Print Service <---> Printer This model states that a Client, as a proxy for the User, can access a Print Service, of the User's Cloud Provider, to print to a User's register print device. This model can be used to represent several different solutions or implementations: 1. The "Cloud Provider" is Print Cloud (like HP's or Epson's or) Print Cloud Provider Client <---> Cloud Print Service <---> Printer a. A good and bad model - requires other Cloud Solution to federate with Print Cloud Provider. This would be a big development effort for print vendors. 2. Cloud Print Services are integrated into a Cloud Provider like Google Cloud Cloud Provider Client <---> Cloud Print Service <---> Printer a. Again, good and bad. Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason. 3. The Cloud Print Service is a "mini-cloud" or a "plug-in cloud" (but still in the Cloud) that is callable by a Cloud Provider. Cloud Provider Client <---> \ \ \ \ \ Cloud Print Service <---> Printer Where there is cloud around both Cloud Print and Cloud Print Service a. Yes, this looks like model in the current specification but with some slight differences. i. The Cloud Print Services are in the cloud; thus, they are cloud SAAS 1. Yes, the Print Service could be in the physical printer but virtually linked ("registered") in the Cloud ii. A printer is associated with a single Cloud Print Service 1. >From the User's and the Cloud Provider's point-of-view, one Print Service is associated with one Printer. The User and Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer. a. Internally, an individual "Print Service" can support 2, 700,039 Printers; that is something the print vendor does as part of their implementation detail. It will not affect the API's the Cloud Provider developers uses to print to the printer. And has nothing to do with the PWG Cloud Print specification. 2. >From the User's and the Cloud Provider's point-of-view, one Print Service (associated with one Printer) has its own queue. a. If a print vendor wants to have individual queues (the "bucket" of Print Jobs) for each printer or have one giant queue (a big "bucket") that individual printers pull jobs from, this again, is a print vendor implementation detail. And has nothing to do with the PWG Cloud Print specification. iii. From the Cloud Provider's point-of-view, the above definitions makes all Cloud Print Service interfaces look the same; that it, 1. An individual Printer is registered and has an associated a single Print Service 2. The Cloud Provider only talks to the Printer's Print Service for all APIs and actions. 3. Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented) iv. Thus, the goal of the PWG Cloud activity is to define the API's and data for the Cloud Provider to/from a Cloud Print Service 1. I know - use IPP a. I don't think IPP will be used by everyone. (Who is using it now for Cloud?) What "will be used" is the PWG:PJT, which does not require IPP to be useful. PWG:PJT make federation of the Print Jobs very simple. In general PWG:PJT is a perfect candidate for cloud print. So the final model is something like Cloud Provider |------- a Directory/Registry of Vendor Print Clouds Client <---> \ \ < -------------------- register Printers (and its Print Service) to a User \ \ \ Vendor M Print Cloud \ Vendor N Print Cloud Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer glen _____ From: Michael Sweet [mailto:msweet@apple.com] Sent: Friday, April 06, 2012 9:00 AM To: Petrie, Glen Cc: Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model [Adding cloud@pwg.org since this is a cloud discussion] Glen, In the original BOF-generated functional model, the Cloud Print Manager is either located in the Printer or attached to the Printer (e.g. in the local print server). The Cloud Print Manager manages communications between the lower-level printer interface and the Cloud Print Provider. Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII art diagram in my mind looks like this: Cloud Print Provider Client <---> Cloud Print Service <---> Cloud Print Manager <---> Printer(s) Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud Print Provider/Service. There can potentially be multiple logical or physical printers behind the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IPP/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a single "queue" with one or more output devices associated with it. On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" wrote: Ira, Pete, I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram "is not in the cloud". Is this true? If so, where is it "located"? Glen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_0C26_01CD13F7.DFF04DD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Glen,<= /o:p>

 

I’m struggling with a number of statements, = I agree the connection between the user and the cloud is one part of the mo= del, and the other part is the connection of the cloud to a logical print s= omething or other (within my system).   Since the model started a= s an imaging model, I believe the cloud to print connection should also be = usable for a scan to cloud, with different elements.

<= p class=3DMsoNormal> 

As a user and implementer I’m focusing on where the connectio= n to the cloud originates, and where the connection from the cloud is termi= nates.

 

So where you have in the last drawing = – Vendor M and Vendor N, are those print services from different prin= t vendors or?

 <= /o:p>

Larry

 

From: cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] On= Behalf Of Petrie, Glen
Sent: Friday, April 06, 2012 10:35 AM=
To: Michael Sweet
Cc: ipp@pwg.org; cloud@pwg.org
Subject: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG= : Cloud Model

&n= bsp;

Mike,

 

=

Thanks for the update.   I was reviewing the diagram again and= I had noted there was no actual print entity “in the cloud”; t= hat is, as an SAAS in cloud terminology; so adding the Cloud Print Service = at least provides a cloud print SAAS.

 

 

Some more discussion -----= -----

 

I am still hav= ing a problem with the use of a Cloud Print Manager (in the printer) concep= t (an the name) in the general context of being a cloud citizen and with as= sociating a User with an individual Print Service (Printers).  That is= , it is not modeled from User’s, use-case or Cloud Provider developer= s’ point of view.  As currently defined, the current Cloud Print= Manager is an artifact of a particular implementation (like DocuPrint; may= be even CUPS) for a fan out with a single controller (Print Servcie?); from= a reference model or architecture point of view it should not matter if th= ere is such an entity providing this function.  This means your simple= diagram reduces to

 

<= p class=3DMsoNormal> 

      &nb= sp;                 = Cloud Print Provider

    Clie= nt  <--->  Cloud Print Service <---> Printer

 

With &= #8220;”””””maybe””””&= #8221; the Printer =3D [ Cloud Print Manager <---> Printer(s) ] = as seen from Cloud Print Provider

=  

Actually, I see no reason to add the P= rint qualifier to the Provider; that is,

 

        &nbs= p;                 &= nbsp;  Cloud Provider

  &= nbsp; Client  <--->  Cloud Print Service <---> Printe= r

 

This model states that a = Client, as a proxy for the User, can access a Print Service, of the User= 217;s Cloud Provider, to print to a User’s register print device.

 

This model can be used= to represent several different solutions or implementations:

 

  1. The “Cloud Provid= er” is Print Cloud (like HP’s or Epson’s or)

          &nbs= p;               Print Cl= oud Provider

    Client  = <--->  Cloud Print Service <---> Printer

    1. <= span style=3D'font-family:"Cambria","serif"'>A good and bad model – r= equires other Cloud Solution to federate with Print Cloud Provider. &n= bsp; This would be a big development effort for print vendors. <= /span>

 

 

 

  1. Cloud Print Serv= ices are integrated into a Cloud Provider like Google Cloud

            =                 = ; Cloud Provider

    Clie= nt  <--->  Cloud Print Service <---> Printer

    1. Again, goo= d and bad.   Good for print vendor in that the Cloud Provider man= ages Print Service; bad for the same reason.

     

     

     

    1. The Cloud Print Service is a “= ;mini-cloud” or a “plug-in cloud” (but still in the Cloud= ) that is callable by a Cloud Provider.

     

    &n= bsp;                   &n= bsp;        Cloud Provider

        Client &nbs= p;<--->    \        = ;     \        =   

                &= nbsp;           &nbs= p;     \        = ;    \

      \ Cloud Print Service <---> Printer

    Where there is cloud around = both Cloud Print and Cloud Print Service

     

      1. Yes, this looks like model in the curren= t specification but with some slight differences.

         &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;         i.      The Cloud Print Services are in the cloud; thus, they are cloud SAAS

      1.      <= /span>Yes, the Print Service could be in the physical printer but vir= tually linked (“registered”) in the Cloud

      =

          &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;      ii.      A printer is ass= ociated with a single Cloud Print Service

      1.      <= span style=3D'font-family:"Cambria","serif";color:blue'>>From the User&#= 8217;s and the Cloud Provider’s point-of-view, one Print Service is a= ssociated with one Printer.   The User and Cloud Provider develop= ers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; = they know there an associated Print Services for a specific Printer.  =

      a= .     = ;  Internally, an individual “Print Service” = can support 2, 700,039 Printers; that is something the print vendor does as= part of their implementation detail.   It will not affect the AP= I’s the Cloud Provider developers uses to print to the printer.  = ;And has nothing to do with the PWG Cloud Print specification.

      2.      >From the User’s and the Cloud Provider’s point-of-view, = one Print Service (associated with one Printer) has its own queue. &nb= sp;

      a.    &= nbsp;  If a print vendor wants to have individual queues = (the “bucket” of Print Jobs) for each printer or have one giant= queue (a big “bucket”) that individual printers pull jobs from= , this again, is a print vendor implementation detail.   And has = nothing to do with the PWG Cloud Print specification.

      =

          &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;    iii.      From the Cloud ProviderR= 17;s point-of-view, the above definitions makes all Cloud Print Service int= erfaces look the same; that it,

      1.An individual Printer is regi= stered and has an associated a single Print Service

      2.      <= ![endif]>The Cloud= Provider only talks to the Printer’s Print Service for all APIs and = actions.

      3.   &n= bsp;  Print Jobs are submitted to the Print Service for t= he target printer (no matter how the queue is implemented)

         &nb= sp;            =             &nb= sp;            =             &nb= sp;     iv.      Thus, the goal of the P= WG Cloud activity is to define the API’s and data for the Cloud Provi= der to/from a Cloud Print Service

      = 1.      I know – use IPP=

      a.     &nbs= p; I don’t think IPP will be used by everyone. &nbs= p; (Who is using it now for Cloud?)  What “will be used” i= s the PWG:PJT, which does not require IPP to be useful.   PWG:PJT= make federation of the Print Jobs very simple.  In general PWG:PJT is= a perfect candidate for cloud print.

       <= /o:p>

      So the final model is something like

       

            =                  &nb= sp;     Cloud Provider     &nb= sp;            =   |------- a Directory/Registry of Vendor Print Clouds

      <= p class=3DMsoNormal style=3D'margin-left:.25in'>    Client  = <--->    \        &= nbsp;    \ < -------------------- register Printers (and = its Print Service) to a User

               &nb= sp;            =         \     &= nbsp;      \

      &n= bsp;            &nbs= p;            &= nbsp;           \ Vendor = M Print Cloud           &= nbsp;           &nbs= p;            \ Vend= or N Print Cloud

          = ;             &= nbsp;           &nbs= p;            &= nbsp;     Print Service <---> Printer  =              &n= bsp;            = ;            &n= bsp;   Print Service <---> Printer

                &n= bsp;            &nbs= p;            &= nbsp;           Print Ser= vice <---> Printer         &n= bsp;            = ;            &n= bsp;         Print Service <---&= gt; Printer

          &nbs= p;             =             &nb= sp;            =      Print Service <---> Printer   = ;             &= nbsp;           &nbs= p;            &= nbsp;  Print Service <---> Printer

                  &n= bsp;            = ;            &n= bsp;          Print Service &l= t;---> Printer          &nb= sp;            =             &nb= sp;        Print Service <---> Pri= nter

            = ;             &= nbsp;           &nbs= p;            &= nbsp;   Print Service <---> Printer    =              &n= bsp;            = ;            &n= bsp; Print Service <---> Printer

      &= nbsp;            &nb= sp;            =             &nb= sp;         Print Service <---&g= t; Printer           &nbs= p;            &= nbsp;           &nbs= p;       Print Service <---> Printer

       

      glen

       

       

       

       


      From: Michael Sweet [mailto:msweet@apple.com]
      = Sent: Friday, April 06, 2012 9:00 AM
      To: Petrie, Glen
      C= c: Peter Zehler; Ira Mcdonald; ipp@pwg.o= rg; cloud@pwg.org
      Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model

       

      [Adding cloud@pwg.org s= ince this is a cloud discussion]

       

      Glen,

       

In the original BOF-generated functional model, the Cloud Print Manager is= either located in the Printer or attached to the Printer (e.g. in the loca= l print server).  The Cloud Print Manager manages communications betwe= en the lower-level printer interface and the Cloud Print Provider.

 

Based on our last telecon, we have introduced a Cloud Print= Service into the model which is the service in/under the Cloud Print Provi= der (which acts as a System Control Service in the Semantic Model sense) th= at manages the jobs/queue in the cloud for the Cloud Print Manager.  T= he rough ASCII art diagram in my mind looks like this:

=

 

 

    &nbs= p;              Cloud Print Provider

    Client  <-= -->  Cloud Print Service  <--->  Cloud Print Manage= r <---> Printer(s)

 

Thus, Clients and Cloud Pr= int Managers talk directly to the Cloud Print Provider and corresponding Cl= oud Print Service, but never directly to each other, and only the Cloud Pri= nt Manager actually talks directly with the Printer(s) (physical or logical= ) it is registering/sharing with the Cloud Print Provider/Service.

 

There can potentially be multiple logical or physical print= ers behind the Cloud Print Manager (think traditional fan-out configuration= s and reprographic services) and those printers *may* be addressable using = the IPP/SM output device attributes/elements, but there is only a single Cl= oud Print Service per Cloud Print Manager and to the Client it will appear = to be a single "queue" with one or more output devices associated= with it.

 

 

On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" = <glen.petrie@eitc.epson.co= m> wrote:

 

Ira, Pete,

=

&nb= sp;

I believe it was stated in the last conference = call that the Cloud Print Manager in the cloud model diagram “is not = in the cloud”.   Is this true?  If so, where is it = 220;located”? 

 <= /p>

Glen

 


-- 
This mess= age has been scanned for viruses and&nb= sp;
dangerous content by = ;MailScanner, and is 
believed to be clean. ___________________________________= ____________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/m= ailman/listinfo/ipp

 

____= ______________________________________________

<= div>

Michael Sweet, Senior Printing System = Engineer, PWG Chair

<= o:p> 


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0C26_01CD13F7.DFF04DD0-- --===============1800005897== 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 --===============1800005897==-- From ipp-bounces@pwg.org Fri Apr 6 14:49:15 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4012611E80A4 for ; Fri, 6 Apr 2012 14:49:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.266 X-Spam-Level: X-Spam-Status: No, score=-1.266 tagged_above=-999 required=5 tests=[AWL=-0.665, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_HTML_MOSTLY=0.001, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFMEf1B4sokX for ; Fri, 6 Apr 2012 14:49:07 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 543AA11E8098 for ; Fri, 6 Apr 2012 14:49:07 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9EE7179691; Fri, 6 Apr 2012 17:47:56 -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 7F85579688; Fri, 6 Apr 2012 17:47:32 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 6 Apr 2012 14:47:31 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Date: Fri, 6 Apr 2012 14:47:32 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Thread-Index: AQHntflnqxSNbzlmOGFUFqnaPhyXKQHKsa6yAavZ1gGWPTr2YIAAEROg References: <0c2501cd1432$8c414320$a4c3c960$@comcast.net> From: "Petrie, Glen" To: "larryupthegrove" , "Michael Sweet" X-OriginalArrivalTime: 06 Apr 2012 21:47:31.0979 (UTC) FILETIME=[DEA97DB0:01CD143E] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1379371055==" 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: 9EE7179691.AB0DA X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1379371055== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD143E.DEAFB0DC" This is a multi-part message in MIME format. ------_=_NextPart_001_01CD143E.DEAFB0DC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Glen, =20 I'm struggling with a number of statements, I agree the connection between the user and the cloud is one part of the model, and the other part is the connection of the cloud to a logical print something or other (within my system). Since the model started as an imaging model, I believe the cloud to print connection should also be usable for a scan to cloud, with different elements. =20 [gwp] The User connects to either the Cloud Provider's Print Client (a Cloud Print Client) or an independent Print Client that connects to the Cloud Provider. The key is that connection is the User to a Print Client.=20 =20 [gwp] Other imaging service would following exactly the same model without loss of generality; namely,=20=20=20 =20 User <-----> Print Client <=3D> Print Service <------> Physical Printer User <-----> Scan Client <=3D> Scan Service <------> Physical Scanner=20 User <-----> Transform Client <=3D> Transform Service <------> "Physical" Transforms =20 Users register Service register Users <=3D> services are associated=20 =20 As a user and implementer I'm focusing on where the connection to the cloud originates, and where the connection from the cloud is terminates. =20 [gwp] As an user you are should have the following concerns Assumption: The User is a member (registered) with the Cloud Provider - i.e. has a User account.=20 =20 1. Does my (the User's) Cloud Provider support (have APIs/interfaces) to support an internal or external Print Client 2. How do I (the User) "install" (register) my (the User) Physical Printer with the Cloud Provider under my (the User) account 3. Can/How to set up default Print Settings 4. Can/How to allow others to use my Physical Printer. =20 Complete actions: 1. I (the User) have "installed" (registered) my Physical Printer in my account with my Cloud Provider. =20 Usage: 1. Using an internal/external Print Client, I (the User) can select an individual Physical Printer from my of installed Physical Printers 2. I (the User) can "create" a Print Job for my document using the capabilities of the selected Physical Printer.=20 =20 So the User does not know about or care Print Service; the User only understands the Physical Printer they want to use. The User certainly does not know how printing is "handled" within the Cloud and beyond.=20 =20 The User "just wants to print". =20 [gwp] As an implementer you are should have the following concerns First of all: What are you the implementer of? 1. An application developer invoking a print action from a print menu selection a. The application will actually invoke a Print Client=20 2. An internal/external Print Client developer capturing Print Intent and creating a Print Job. 3. A printer vendor developer wanting to provide Cloud Print support for my printers. 4. A Cloud Provider developer wanting to support Printing. =20 In all the implementer cases above you want the APIs for interfacing with the Print Service associated with a Physical Printer. And you don't know, want to know or care "where" the Print Service is; you only want to know how to access it and that it uses a common (defined, standardized) set of API for printing. You don't know, want to know or care how the Print Service communicates with the Physical Printer; only that the Print Service can communication with the Physical Printer. The Print Service will support the implementer (ultimately the User) by providing capability information, Print Job submission, reporting Printing Status, State & Error information and there is likely some security issues. Note that Print Service does not know, want to know or care if specific User has access to the Physical Printer or not; that is job of the Cloud Provider to support (secure) association. If a print vendor provides a fully implement Cloud; then that Cloud is classified as a Cloud Provider.=20 =20 So, does the implementer know if there is fan-out or fan-in; that there is "Print Manager"? No. Does implementer know about common or individual queues? No, the Print Service API provides Print Jobs info (queue info) for the specific Physical Printer. (Yes, there may be a system rollup; but that is an admin operation.) =20 ------------------- In summary: Users see Print Clients Implementers see Print Services=20 =20 So Print Client <=3D> Print Services !!!! =20 Also, how does all of this work with federation between Clouds?!?!?! (If allowed) A Print Service of any Cloud Provider could be "registered" with the Users' Cloud Provider. This is a complete transparent functionality (yes, there a security issues) but the User set their Print Intent and the Print Client sends the Print Job the User's Cloud Provider who federates (forwards) the Print Job to the other Cloud Provider and, so, forth.=20 =20 So where you have in the last drawing - Vendor M and Vendor N, are those print services from different print vendors or? =20 Yes =20 =20 Larry =20 From: cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, April 06, 2012 10:35 AM To: Michael Sweet Cc: ipp@pwg.org; cloud@pwg.org Subject: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 Mike, =20 Thanks for the update. I was reviewing the diagram again and I had noted there was no actual print entity "in the cloud"; that is, as an SAAS in cloud terminology; so adding the Cloud Print Service at least provides a cloud print SAAS. =20 =20 Some more discussion ---------- =20 I am still having a problem with the use of a Cloud Print Manager (in the printer) concept (an the name) in the general context of being a cloud citizen and with associating a User with an individual Print Service (Printers). That is, it is not modeled from User's, use-case or Cloud Provider developers' point of view. As currently defined, the current Cloud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to=20 =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Printer =20 With """"""maybe""""" the Printer =3D [ Cloud Print Manager <---> Printer(s) ] as seen from Cloud Print Provider =20 Actually, I see no reason to add the Print qualifier to the Provider; that is, =20 Cloud Provider Client <---> Cloud Print Service <---> Printer =20 This model states that a Client, as a proxy for the User, can access a Print Service, of the User's Cloud Provider, to print to a User's register print device.=20 =20 This model can be used to represent several different solutions or implementations: =20 1. The "Cloud Provider" is Print Cloud (like HP's or Epson's or) Print Cloud Provider Client <---> Cloud Print Service <---> Printer a. A good and bad model - requires other Cloud Solution to federate with Print Cloud Provider. This would be a big development effort for print vendors.=20 =20 =20 =20 2. Cloud Print Services are integrated into a Cloud Provider like Google Cloud Cloud Provider Client <---> Cloud Print Service <---> Printer a. Again, good and bad. Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason. =20 =20 =20 3. The Cloud Print Service is a "mini-cloud" or a "plug-in cloud" (but still in the Cloud) that is callable by a Cloud Provider.=20 =20 Cloud Provider Client <---> \ \=20=20=20=20=20=20=20=20=20=20=20 \ \ \ Cloud Print Service <---> Printer Where there is cloud around both Cloud Print and Cloud Print Service =20 a. Yes, this looks like model in the current specification but with some slight differences. i. The Cloud Print Services are in the cloud; thus, they are cloud SAAS=20 1. Yes, the Print Service could be in the physical printer but virtually linked ("registered") in the Cloud ii. A printer is associated with a single Cloud Print Service 1. >From the User's and the Cloud Provider's point-of-view, one Print Service is associated with one Printer. The User and Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer.=20=20 a. Internally, an individual "Print Service" can support 2, 700,039 Printers; that is something the print vendor does as part of their implementation detail. It will not affect the API's the Cloud Provider developers uses to print to the printer. And has nothing to do with the PWG Cloud Print specification. 2. >From the User's and the Cloud Provider's point-of-view, one Print Service (associated with one Printer) has its own queue.=20=20=20 a. If a print vendor wants to have individual queues (the "bucket" of Print Jobs) for each printer or have one giant queue (a big "bucket") that individual printers pull jobs from, this again, is a print vendor implementation detail. And has nothing to do with the PWG Cloud Print specification. iii. =46rom the Cloud Provider's point-of-view, the above definitions makes all Cloud Print Service interfaces look the same; that it, 1. An individual Printer is registered and has an associated a single Print Service 2. The Cloud Provider only talks to the Printer's Print Service for all APIs and actions.=20 3. Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented) iv. Thus, the goal of the PWG Cloud activity is to define the API's and data for the Cloud Provider to/from a Cloud Print Service 1. I know - use IPP a. I don't think IPP will be used by everyone. (Who is using it now for Cloud?) What "will be used" is the PWG:PJT, which does not require IPP to be useful. PWG:PJT make federation of the Print Jobs very simple. In general PWG:PJT is a perfect candidate for cloud print. =20 So the final model is something like =20 Cloud Provider |------- a Directory/Registry of Vendor Print Clouds Client <---> \ \ < -------------------- register Printers (and its Print Service) to a User=20 \ \ \ Vendor M Print Cloud \ Vendor N Print Cloud Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer =20 glen =20 =20 =20 =20 ________________________________ From: Michael Sweet [mailto:msweet@apple.com] =20=20 Sent: Friday, April 06, 2012 9:00 AM To: Petrie, Glen Cc: Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 [Adding cloud@pwg.org since this is a cloud discussion] =20 Glen, =20 In the original BOF-generated functional model, the Cloud Print Manager is either located in the Printer or attached to the Printer (e.g. in the local print server). The Cloud Print Manager manages communications between the lower-level printer interface and the Cloud Print Provider. =20 Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII art diagram in my mind looks like this: =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Cloud Print Manager <---> Printer(s) =20 Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud Print Provider/Service. =20 There can potentially be multiple logical or physical printers behind the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IPP/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a single "queue" with one or more output devices associated with it. =20 =20 On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" wrote: =20 Ira, Pete, =20 I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram "is not in the cloud". Is this true? If so, where is it "located"?=20 =20 Glen =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org =20 https://www.pwg.org/mailman/listinfo/ipp =20 =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CD143E.DEAFB0DC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Glen,

 

I’m stru= ggling with a number of statements, I agree the connection between the user and the cloud is one part of the model, and the other part is the connection of the cloud to a logical print something or other (within my system).   Since the model started as an imaging model, I believe the cloud to print connection should also be usable for a scan to cloud, with different elemen= ts.

 

[gwp] The User connects to either the Cloud Provider’s Print Client (a Cloud Print Client) or an independent Print Client that connects to the Cloud Provider.  The key is that con= nection is the User to a Print Client.

 

[gwp] Other imaging service would following exactly the same model without loss of generality; namely,  

 

      =       User <-----> Print Client         =  ó= Print Service            &= lt;------> Physical Printer

      =       User <-----> Scan Client         &= nbsp; ó= Scan Service            &= lt;------> Physical Scanner

User <-----> Transform Client ó= Transform Service <------> “Physical” Transforms<= /font>

 

Users    register

Service register

Users ó<= /span>= services are associated

 

As a user and implementer I’m focusing on where the connection to the cloud origina= tes, and where the connection from the cloud is terminates.

 

[gwp]  As an user you are should have the following concerns

Assumption: The User is a member (registered) with the Cloud Provider – i.e. has a User account. =

 

  1. Does my (the User’s) Cloud Provider support (have APIs/interfaces) to support an internal or external Print Client<= /li>
  2. How do I (the User) “install” (register) my (the User) Physical Printer with the Cloud Provider under my (the User) account=
  3. Can/How to set up default Print Settings
  4. Can/How to allow others to use my Physical Printer.

 

Complete actions:<= /font>

  1. I (the User) have “installed” (registered) my Physical Print= er in my account with my Cloud Provider.

 

Usage:

  1. Using an internal/external Print Client, I (the User) can select an individu= al Physical Printer from my of installed Physical Printers
  2. I (the User) can “create” a Print Job for my document using = the capabilities of the selected Physical Printer.

 

So the User does not know about or care Print Service; the User only understan= ds the Physical Printer they want to use.

The User certainly does not know how printing is “handled” within the Cl= oud and beyond.

 

The User “just wants to print”.

 

[gwp]  As an implementer you are should have the following concerns

First of all: What are you the implementer of?

  1. An application developer invoking a print action from a print menu select= ion
    1. The application will actually invoke a Print Client
  2. An internal/external Print Client developer capturing Print Intent and cr= eating a Print Job.
  3. A printer vendor developer wanting to provide Cloud Print support for my printers.
  4. A Cloud Provider developer wanting to support Printing.

 

In all the implementer cases above y= ou want the APIs for interfacing with the Print Service associated with a Phys= ical Printer.   And you don’t know, want to know or care “= where” the Print Service is; you only want to know how to access it and that it us= es a common (defined, standardized) set of API for printing.   You don= ’t know, want to know or care how the Print Service communicates with the Phys= ical Printer; only that the Print Service can communication with the Physical Printer.  The Print Service will support the implementer (ultimately t= he User) by providing capability information, Print Job submission, reporting = Printing Status, State & Error information and there is likely some security issues.   Note that Print Service does not know, want to know or = care if specific User has access to the Physical Printer or not; that is job of = the Cloud Provider to support (secure) association.   If a print vend= or provides a fully implement Cloud; then that Cloud is classified as a Cloud Provider.

 

So, does the implementer know if there is fan-out or fan-in; that there is R= 20;Print Manager”?  No.

Does implementer know about common or individual queues? No, the Print Service A= PI provides Print Jobs info (queue info) for the specific Physical Printer.&nb= sp; (Yes, there may be a system rollup; but that is an admin operation.)

 

-------------------

In summary: Users see Print Clients=

      =             &nb= sp;     Implementers see Print Services

 

So Print Client ó= Print Services !!!!

 

Also, how does all of this work with federation between Clouds?!?!?! (If allowed) A Print Service of any Cloud Provider could be “registered” with the Users’ Cloud Provider.  This is a complete transparent functionality (yes, there a security issues) but the User set their Print Intent and the Print Client s= ends the Print Job the User’s Cloud Provider who federates (forwards) the = Print Job to the other Cloud Provider and, so, forth.

 

So where you h= ave in the last drawing – Vendor M and Vendor N, are those print services fr= om different print vendors or?

 

Yes

 

 

Larry

 

From: cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Friday, April 06, 2012= 10:35 AM
To: Michael Sweet
Cc: ipp@pwg.org; cloud@pwg.o= rg
Subject: [Cloud] RE: [IPP] W= here is the Cloud Print Manager in the PWG: Cloud Model
=

 

Mike,

 

Thanks for the update.   I= was reviewing the diagram again and I had noted there was no actual print entity “in the cloud”; that is, as an SAAS in cloud terminology; so ad= ding the Cloud Print Service at least provides a cloud print SAAS.

 

 

Some more discussion ----------=

 

I am still having a problem with the= use of a Cloud Print Manager (in the printer) concept (an the name) in the gene= ral context of being a cloud citizen and with associating a User with an indivi= dual Print Service (Printers).  That is, it is not modeled from User’= s, use-case or Cloud Provider developers’ point of view.  As curren= tly defined, the current Cloud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function.  This means your simple diagram reduces to

 

 

                         Cloud Print Provider=

    Client  <--->  Cloud Print Service <---> Printer

 

With “”””””maybe””””= ” the Printer =3D [ Cloud Print Manager <---> Printer(s) ]  as see= n from Cloud Print Provider

 

Actually, I see no reason to add the Print qualifier to the Provide= r; that is,

 

                             Cloud Provider=

    Client  <--->  Cloud Print Service <---> Printer

 

This model states that a Client, as a proxy for the User, can access a Print Service, of the User’s Cloud Provider, to print to a User’s register print device.

 

This model can be used to represent several different solutions or implementations:

 

  1. The “Cloud Provider” is Print Cloud (like HP’s or Epson’s or)

                          Print Cloud Provider<= /span>

    Client  <--->  Cloud Print Service <---> Printer

    1. A good and bad model – requires other Cloud Solution to federate = with Print Cloud Provider.   This would be a big development eff= ort for print vendors.

 

 

 

  1. Cloud Print Services are integrated into a Cloud Provider like Google Cloud<= o:p>

                             Cloud Provider=

    Client  <--->  Cloud Print Service <---> Printer

    1. Again, good and bad.   Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason.

 

 

 

  1. The Cloud Print Service is a “mini-cloud” or a “plug-in cloud” (but still in the Cloud) that is callable by a Cloud Provider.

 

                             Cloud Provider=

    Client  <--->  &nb= sp; \             \          

        =             &nb= sp;         \            \<= /o:p>

  \ Cloud Print Service <---> Printer=

Where there is cloud around both Cloud Print and= Cloud Print Service

 

    1. Yes, this looks like model in the current specification but with some slig= ht differences.

      =             &nb= sp;            =             &nb= sp;            =        i.      The Cloud Print Services are in the cloud; thus, they are cloud SAAS

1.      = Yes, the Print Service could be in the physical printer but virtually linked (“registered”) in the Cloud

      =             &nb= sp;            =             &nb= sp;            =      ii.      A printer is associated with a sin= gle Cloud Print Service

1.      = >From the User’s and the Cloud Provider’s point-of-view, one Print Service is associated with one Printer.   The User and Cloud Prov= ider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer.  

a.      = = Internally, an individual “Print Service” can support 2, 700,039 Printers; = that is something the print vendor does as part of their implementation detail.   It will not affect the API’s the Cloud Provider developers uses to print to the printer.  And has nothing to do with t= he PWG Cloud Print specification.

2.      = >From the User’s and the Cloud Provider’s point-of-view, one Print Service (associated with one Printer) has its own queue.   <= /o:p>

a.      = = If a print vendor wants to have individual queues (the “bucket” of Print J= obs) for each printer or have one giant queue (a big “bucket”) that individual printers pull jobs from, this again, is a print vendor implementation detail.   And has nothing to do with the PWG Cloud Print specification.

      =             &nb= sp;            =             &nb= sp;            =    iii.      From the Cloud Provider’s point-of-view, the above definitions makes all Cloud Print Service interfac= es look the same; that it,

1.      = An individual Printer is registered and has an associated a single Print Servi= ce

2.      = The Cloud Provider only talks to the Printer’s Print Service for all APIs and actions.

3.      = Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented)

      =             &nb= sp;            =             &nb= sp;            =    iv.      Thus, the goal of the PWG Cloud ac= tivity is to define the API’s and data for the Cloud Provider to/from a Cloud Print Service

1.      = I know – use IPP

a.      = I don’t think IPP will be used by everyone.   (Who is using it now for Cloud?)  What “will be used” is the PWG:PJT, which does not require IPP to be useful.   PWG:PJT make federation of t= he Print Jobs very simple.  In general PWG:PJT is a perfect candidate for cloud print.

 

So the final model is something like=

 

                             Cloud Provider           &= nbsp;        |------- a Directory/Registry of Vendor Print Clouds

    Client  <--->  &nb= sp; \             \ < -------------------- register Printers (and its Print Service) to a Us= er

        =             &nb= sp;         \            \<= /o:p>

              &nb= sp;            =            \ Vendor M Print Cloud       &nbs= p;            &= nbsp;           &nbs= p;   \ Vendor N Print Cloud

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

                        &nb= sp;            =            Print Service <---> Printer                    &nb= sp;            =            Print Service <---> Printer

 

glen

 

 

 

 


From: Michael = Sweet [mailto:msweet@apple.com]=
Sent: Friday, April 06, 2012= 9:00 AM
To: Petrie, Glen
Cc: Peter Zehler; Ira Mcdona= ld; ipp@pwg.org; cloud@pwg.org
Subject: Re: [IPP] Where is = the Cloud Print Manager in the PWG: Cloud Model

 

[Adding cloud@pwg.org since th= is is a cloud discussion]

 

Glen,

 

In the original BOF-generated functional model, the Cloud Print Man= ager is either located in the Printer or attached to the Printer (e.g. in the lo= cal print server).  The Cloud Print Manager manages communications between= the lower-level printer interface and the Cloud Print Provider.

 

Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages = the jobs/queue in the cloud for the Cloud Print Manager.  The rough ASCII = art diagram in my mind looks like this:

 

 

                   Cloud Print Provider

    Client  <--->  Cloud Print Service  <--->  Cloud Print Manager <---> Printer(s)

 

Thus, Clients and Cloud Print Managers talk directly to the Cloud P= rint Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud P= rint Provider/Service.

 

There can potentially be multiple logical or physical printers behi= nd the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IP= P/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a si= ngle "queue" with one or more output devices associated with it.<= /o:p>

 

 

On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" <glen.petrie@eitc.epson.com&g= t; wrote:

 =

Ira, Pete,

 

I believe it was stated in the last conference call th= at the Cloud Print Manager in the cloud model diagram “is not in the cloud”.   Is this true?  If so, where is it “located”? 

 

Glen

 


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

 

______________= ____________________________________

Michael Sweet, Senior Printing System Engineer, PWG Chair

 


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------_=_NextPart_001_01CD143E.DEAFB0DC-- --===============1379371055== 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 --===============1379371055==-- From ipp-bounces@pwg.org Fri Apr 6 16:04:40 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5739A11E80AB for ; Fri, 6 Apr 2012 16:04:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.864 X-Spam-Level: X-Spam-Status: No, score=-100.864 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQnqZFRLrIAG for ; Fri, 6 Apr 2012 16:04:32 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id BF61F11E80A0 for ; Fri, 6 Apr 2012 16:04:31 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 00EF87968B; Fri, 6 Apr 2012 19:03:11 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by pwg.org (Postfix) with ESMTP id 03AE07968B for ; Fri, 6 Apr 2012 19:02:41 -0400 (EDT) Received: from omta10.emeryville.ca.mail.comcast.net ([76.96.30.28]) by qmta05.emeryville.ca.mail.comcast.net with comcast id umcc1i0040cQ2SLA5n2hHM; Fri, 06 Apr 2012 23:02:41 +0000 Received: from LarryHP6616 ([98.210.92.38]) by omta10.emeryville.ca.mail.comcast.net with comcast id un2f1i00i0pficJ8Wn2gAM; Fri, 06 Apr 2012 23:02:40 +0000 From: "larryupthegrove" To: "'Petrie, Glen'" , "'Michael Sweet'" References: <0c2501cd1432$8c414320$a4c3c960$@comcast.net> In-Reply-To: Subject: RE: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model Date: Fri, 6 Apr 2012 16:02:39 -0700 Message-ID: <0c5401cd1449$5da05850$18e108f0$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHntflnqxSNbzlmOGFUFqnaPhyXKQHKsa6yAavZ1gEDRhF1JwGe26AplhZFoRA= Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0273886279==" 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: 00EF87968B.A9B95 X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multipart message in MIME format. --===============0273886279== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C55_01CD140E.B1496F90" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0C55_01CD140E.B1496F90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I=92ll spend some time working through your notes and get a better understanding. =20 The implementation scenario I=92m trying to work with is the following: =20 Company has on-site ERP system, with output directed to 350 locations, 1700 printers (18 models, 7 different manufacturers). Current print Infrastructure is combination of UNIX and Windows print servers. Company has decided to move their ERP to the cloud, and eliminate if possible any print infrastructure. So a solution could be put everything in the cloud at XXXX, using the same system/print infrastructure and send print using 9100, LPR/LPD, and IPP to the individual devices.=20 =20 Since the ERP software is generating its own reports, I could assume a =93super user=94 status, that they own and can print to any device. Users = would have to send their local documents to the cloud, to be printed at a specified device. =20 Larry =20 =20 From: Petrie, Glen [mailto:glen.petrie@eitc.epson.com]=20 Sent: Friday, April 06, 2012 2:48 PM To: larryupthegrove; Michael Sweet Cc: ipp@pwg.org; cloud@pwg.org Subject: RE: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 =20 Glen, =20 I=92m struggling with a number of statements, I agree the connection between the user and the cloud is one part of the model, and the other part is the connection of the cloud to a logical print something or other (within my system). Since the model started as an imaging model, I believe the cloud to print connection should also be usable for a scan to cloud, with different elements. =20 [gwp] The User connects to either the Cloud Provider=92s Print Client (a Cl= oud Print Client) or an independent Print Client that connects to the Cloud Provider. The key is that connection is the User to a Print Client.=20 =20 [gwp] Other imaging service would following exactly the same model without loss of generality; namely,=20=20=20 =20 User <-----> Print Client =F3 Print Service <------> Physical Printer User <-----> Scan Client =F3 Scan Service <------> Physical Scanner=20 User <-----> Transform Client =F3 Transform Service <------> =93Physical=94 Transforms =20 Users register Service register Users =F3 services are associated=20 =20 As a user and implementer I=92m focusing on where the connection to the clo= ud originates, and where the connection from the cloud is terminates. =20 [gwp] As an user you are should have the following concerns Assumption: The User is a member (registered) with the Cloud Provider =96 i= .e. has a User account.=20 =20 1. Does my (the User=92s) Cloud Provider support (have APIs/interfaces) to support an internal or external Print Client 2. How do I (the User) =93install=94 (register) my (the User) Physical Printer with the Cloud Provider under my (the User) account 3. Can/How to set up default Print Settings 4. Can/How to allow others to use my Physical Printer. =20 Complete actions: 1. I (the User) have =93installed=94 (registered) my Physical Printer in my account with my Cloud Provider. =20 Usage: 1. Using an internal/external Print Client, I (the User) can select an individual Physical Printer from my of installed Physical Printers 2. I (the User) can =93create=94 a Print Job for my document using the capabilities of the selected Physical Printer.=20 =20 So the User does not know about or care Print Service; the User only understands the Physical Printer they want to use. The User certainly does not know how printing is =93handled=94 within the C= loud and beyond.=20 =20 The User =93just wants to print=94. =20 [gwp] As an implementer you are should have the following concerns First of all: What are you the implementer of? 1. An application developer invoking a print action from a print menu selection a. The application will actually invoke a Print Client=20 2. An internal/external Print Client developer capturing Print Intent and creating a Print Job. 3. A printer vendor developer wanting to provide Cloud Print support for my printers. 4. A Cloud Provider developer wanting to support Printing. =20 In all the implementer cases above you want the APIs for interfacing with the Print Service associated with a Physical Printer. And you don=92t kno= w, want to know or care =93where=94 the Print Service is; you only want to kno= w how to access it and that it uses a common (defined, standardized) set of API for printing. You don=92t know, want to know or care how the Print Service communicates with the Physical Printer; only that the Print Service can communication with the Physical Printer. The Print Service will support the implementer (ultimately the User) by providing capability information, Print Job submission, reporting Printing Status, State & Error information and there is likely some security issues. Note that Print Service does not know, want to know or care if specific User has access to the Physical Printer or not; that is job of the Cloud Provider to support (secure) association. If a print vendor provides a fully implement Cloud; then that Cloud is classified as a Cloud Provider.=20 =20 So, does the implementer know if there is fan-out or fan-in; that there is =93Print Manager=94? No. Does implementer know about common or individual queues? No, the Print Service API provides Print Jobs info (queue info) for the specific Physical Printer. (Yes, there may be a system rollup; but that is an admin operation.) =20 ------------------- In summary: Users see Print Clients Implementers see Print Services=20 =20 So Print Client =F3 Print Services !!!! =20 Also, how does all of this work with federation between Clouds?!?!?! (If allowed) A Print Service of any Cloud Provider could be =93registered=94 wi= th the Users=92 Cloud Provider. This is a complete transparent functionality (yes, there a security issues) but the User set their Print Intent and the Print Client sends the Print Job the User=92s Cloud Provider who federates (forwards) the Print Job to the other Cloud Provider and, so, forth.=20 =20 So where you have in the last drawing =96 Vendor M and Vendor N, are those print services from different print vendors or? =20 Yes =20 =20 Larry =20 From: cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, April 06, 2012 10:35 AM To: Michael Sweet Cc: ipp@pwg.org; cloud@pwg.org Subject: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 Mike, =20 Thanks for the update. I was reviewing the diagram again and I had noted there was no actual print entity =93in the cloud=94; that is, as an SAAS in cloud terminology; so adding the Cloud Print Service at least provides a cloud print SAAS. =20 =20 Some more discussion ---------- =20 I am still having a problem with the use of a Cloud Print Manager (in the printer) concept (an the name) in the general context of being a cloud citizen and with associating a User with an individual Print Service (Printers). That is, it is not modeled from User=92s, use-case or Cloud Provider developers=92 point of view. As currently defined, the current Cl= oud Print Manager is an artifact of a particular implementation (like DocuPrint; maybe even CUPS) for a fan out with a single controller (Print Servcie?); from a reference model or architecture point of view it should not matter if there is such an entity providing this function. This means your simple diagram reduces to=20 =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Printer =20 With =93=94=94=94=94=94maybe=94=94=94=94=94 the Printer =3D [ Cloud Print M= anager <---> Printer(s) ] as seen from Cloud Print Provider =20 Actually, I see no reason to add the Print qualifier to the Provider; that is, =20 Cloud Provider Client <---> Cloud Print Service <---> Printer =20 This model states that a Client, as a proxy for the User, can access a Print Service, of the User=92s Cloud Provider, to print to a User=92s register pr= int device.=20 =20 This model can be used to represent several different solutions or implementations: =20 1. The =93Cloud Provider=94 is Print Cloud (like HP=92s or Epson=92s or) Print Cloud Provider Client <---> Cloud Print Service <---> Printer a. A good and bad model =96 requires other Cloud Solution to federate with Print Cloud Provider. This would be a big development effort for print vendors.=20 =20 =20 =20 2. Cloud Print Services are integrated into a Cloud Provider like Google Cloud Cloud Provider Client <---> Cloud Print Service <---> Printer a. Again, good and bad. Good for print vendor in that the Cloud Provider manages Print Service; bad for the same reason. =20 =20 =20 3. The Cloud Print Service is a =93mini-cloud=94 or a =93plug-in cloud=94 (= but still in the Cloud) that is callable by a Cloud Provider.=20 =20 Cloud Provider Client <---> \ \=20=20=20=20=20=20=20=20=20=20=20 \ \ \ Cloud Print Service <---> Printer Where there is cloud around both Cloud Print and Cloud Print Service =20 a. Yes, this looks like model in the current specification but with some slight differences. i. The Cloud Print Services are in the cloud; thus, they are cloud SAAS=20 1. Yes, the Print Service could be in the physical printer but virtually linked (=93registered=94) in the Cloud ii. A printer is associated with a single Cloud Print Service 1. >From the User=92s and the Cloud Provider=92s point-of-view, one Pr= int Service is associated with one Printer. The User and Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-down or any kind of fan; they know there an associated Print Services for a specific Printer.= =20=20 a. Internally, an individual =93Print Service=94 can support 2, 700,0= 39 Printers; that is something the print vendor does as part of their implementation detail. It will not affect the API=92s the Cloud Provider developers uses to print to the printer. And has nothing to do with the PWG Cloud Print specification. 2. >From the User=92s and the Cloud Provider=92s point-of-view, one Pr= int Service (associated with one Printer) has its own queue.=20=20=20 a. If a print vendor wants to have individual queues (the =93bucket= =94 of Print Jobs) for each printer or have one giant queue (a big =93bucket=94) t= hat individual printers pull jobs from, this again, is a print vendor implementation detail. And has nothing to do with the PWG Cloud Print specification. iii. From the Cloud Provider=92s point-of-view, the above definitions makes all Cloud Print Service interfaces look the same; that it, 1. An individual Printer is registered and has an associated a single Print Service 2. The Cloud Provider only talks to the Printer=92s Print Service for = all APIs and actions.=20 3. Print Jobs are submitted to the Print Service for the target printer (no matter how the queue is implemented) iv. Thus, the goal of the PWG Cloud activity is to define the API=92s and data for the Cloud Provider to/from a Cloud Print Service 1. I know =96 use IPP a. I don=92t think IPP will be used by everyone. (Who is using it n= ow for Cloud?) What =93will be used=94 is the PWG:PJT, which does not require= IPP to be useful. PWG:PJT make federation of the Print Jobs very simple. In general PWG:PJT is a perfect candidate for cloud print.=20 =20 So the final model is something like =20 Cloud Provider |------- a Directory/Registry of Vendor Print Clouds Client <---> \ \ < -------------------- register Printers (and its Print Service) to a User=20 \ \ \ Vendor M Print Cloud \ Vendor N Print Cloud Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer Print Service <---> Printer =20 glen =20 =20 =20 =20 _____=20=20 From: Michael Sweet [mailto:msweet@apple.com] =20=20 Sent: Friday, April 06, 2012 9:00 AM To: Petrie, Glen Cc: Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model =20 [Adding cloud@pwg.org since this is a cloud discussion] =20 Glen, =20 In the original BOF-generated functional model, the Cloud Print Manager is either located in the Printer or attached to the Printer (e.g. in the local print server). The Cloud Print Manager manages communications between the lower-level printer interface and the Cloud Print Provider. =20 Based on our last telecon, we have introduced a Cloud Print Service into the model which is the service in/under the Cloud Print Provider (which acts as a System Control Service in the Semantic Model sense) that manages the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII art diagram in my mind looks like this: =20 =20 Cloud Print Provider Client <---> Cloud Print Service <---> Cloud Print Manager <---> Printer(s) =20 Thus, Clients and Cloud Print Managers talk directly to the Cloud Print Provider and corresponding Cloud Print Service, but never directly to each other, and only the Cloud Print Manager actually talks directly with the Printer(s) (physical or logical) it is registering/sharing with the Cloud Print Provider/Service. =20 There can potentially be multiple logical or physical printers behind the Cloud Print Manager (think traditional fan-out configurations and reprographic services) and those printers *may* be addressable using the IPP/SM output device attributes/elements, but there is only a single Cloud Print Service per Cloud Print Manager and to the Client it will appear to be a single "queue" with one or more output devices associated with it. =20 =20 On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" wrote: =20 Ira, Pete, =20 I believe it was stated in the last conference call that the Cloud Print Manager in the cloud model diagram =93is not in the cloud=94. Is this tru= e? If so, where is it =93located=94?=20 =20 Glen =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner, and is=20 believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp =20 __________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner, and is=20 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_000_0C55_01CD140E.B1496F90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I’ll = spend some time working through your notes and get a better understanding.<= o:p>

 

The implementation scenario I’m trying = to work with is the following:

 

Company has on= -site ERP system, with output directed to 350 locations, 1700 printers (18 = models, 7 different manufacturers).=A0 Current print Infrastructure is comb= ination of UNIX and Windows print servers.=A0 Company has decided to move t= heir ERP to the cloud, and eliminate if possible any print infrastructure.= =A0 So a solution could be put everything in the cloud at XXXX, using the s= ame system/print infrastructure and send print using 9100, LPR/LPD, and IPP= to the individual devices.

 

Since the ERP so= ftware is generating its own reports, I could assume a “super user= 221; status, that they own and can print to any device.=A0 Users would have= to send their local documents to the cloud, to be printed at a specified d= evice.

 

Larry

 

 

From: Petrie, Gl= en [mailto:glen.petrie@eitc.epson.com]
Sent: Friday, April 06, 2= 012 2:48 PM
To: larryupthegrove; Michael Sweet
Cc: ipp@= pwg.org; cloud@pwg.org
Subject: RE: [Cloud] RE: [IPP] Where is th= e Cloud Print Manager in the PWG: Cloud Model

 

&nb= sp;

Glen,

 

I’m struggling with a number of statements, I agree the connection = between the user and the cloud is one part of the model, and the other part= is the connection of the cloud to a logical print something or other (with= in my system).   Since the model started as an imaging model, I b= elieve the cloud to print connection should also be usable for a scan to cl= oud, with different elements.

 

[gwp] The User connects to either the Cloud Provider’s Prin= t Client (a Cloud Print Client) or an independent Print Client that connect= s to the Cloud Provider.  The key is that connection is the User to a = Print Client.

 

[gwp]= Other imaging service would following exactly the same model without loss = of generality; namely,  

 

          = ;  User <-----> Print Client       = ;   = =F3 Print S= ervice            &l= t;------> Physical Printer

   &nb= sp;        User <-----> Scan Clien= t           =F3 Scan Service     &n= bsp;      <------> Physical Scanner

User <-----> Transfo= rm Client =F3 Transform Servic= e <------> “Physical” Transforms

=  

Users    register<= /span>

Service register

Users =F3 services are associated

 

As a user a= nd implementer I’m focusing on where the connection to the cloud orig= inates, and where the connection from the cloud is terminates.

 

[gwp] = ; As an user you are should have the following concerns

Assumption: The User is a member (registered) with the Cloud Provider = – i.e. has a User account.

 =

  1. Does my (the User’s) Cloud Provider support (ha= ve APIs/interfaces) to support an internal or external Print Client
  2. How do I (the User) &#= 8220;install” (register) my (the User) Physical Printer with the Clou= d Provider under my (the User) account
  3. Can/How to set up default Print Settings=
  4. Can/How to allow others t= o use my Physical Printer.

=  <= /span>

Complete actions:

  1. I (the User)= have “installed” (registered) my Physical Printer in my accoun= t with my Cloud Provider.

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

Usage:

  1. Using an internal/exter= nal Print Client, I (the User) can select an individual Physical Printer fr= om my of installed Physical Printers
  2. I (the User) can “create” a Print Job for= my document using the capabilities of the selected Physical Printer. =

 

So the User does not know about or care Print Service; the User on= ly understands the Physical Printer they want to use.

=

The User certainly does not know how printing= is “handled” within the Cloud and beyond.

 

The User “just wants to print”.

 

[gwp]  As an implementer you ar= e should have the following concerns

First of all: = What are you the implementer of?

  1. An applica= tion developer invoking a print action from a print menu selection
    1. The application will actually invoke a Print Clien= t
  2. An inte= rnal/external Print Client developer capturing Print Intent and creating a = Print Job.
  3. A pr= inter vendor developer wanting to provide Cloud Print support for my printe= rs.
  4. A Cloud Pro= vider developer wanting to support Printing.

=  

In all the implementer cases above you want = the APIs for interfacing with the Print Service associated with a Physical = Printer.   And you don’t know, want to know or care “= where” the Print Service is; you only want to know how to access it a= nd that it uses a common (defined, standardized) set of API for printing. &= nbsp; You don’t know, want to know or care how the Print Service= communicates with the Physical Printer; only that the Print Service can co= mmunication with the Physical Printer.  The Print Service will support= the implementer (ultimately the User) by providing capability information,= Print Job submission, reporting Printing Status, State & Error informa= tion and there is likely some security issues.   Note that Print = Service does not know, want to know or care if specific User has access to = the Physical Printer or not; that is job of the Cloud Provider to support (= secure) association.   If a print vendor provides a fully impleme= nt Cloud; then that Cloud is classified as a Cloud Provider.

 

So, do= es the implementer know if there is fan-out or fan-in; that there is “= ;Print Manager”?  No.

Does implementer know about common or individual queues? No, the P= rint Service API provides Print Jobs info (queue info) for the specific Phy= sical Printer.  (Yes, there may be a system rollup; but that is an adm= in operation.)

 

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

In summary: Users see Print Clients<= o:p>

        &nb= sp;            =    Implementers see Print Services

=  

So Print Client =F3 Print Services !!!!

 

Also, how does all of this work with federation between Clo= uds?!?!?! (If allowed) A Print Service of any Cloud Provider could be ̶= 0;registered” with the Users’ Cloud Provider.  This is a c= omplete transparent functionality (yes, there a security issues) but the Us= er set their Print Intent and the Print Client sends the Print Job the User= ’s Cloud Provider who federates (forwards) the Print Job to the other= Cloud Provider and, so, forth.

=  <= /span>

So where you have in the last drawing= – Vendor M and Vendor N, are those print services from different pri= nt vendors or?

 

Yes

 

 

Larry

 

From: cl= oud-bounces@pwg.org [= mailto:cloud-bounces@pwg.org] On Behalf Of Petrie, Glen
Se= nt: Friday, April 06, 2012 10:35 AM
To: Michael Sweet
C= c: ipp@pwg.org; cloud@pwg.org
Subject: [Cloud] RE: [IPP] Where i= s the Cloud Print Manager in the PWG: Cloud Model

 

Mike,

 

Thanks for the update.   I= was reviewing the diagram again and I had noted there was no actual print = entity “in the cloud”; that is, as an SAAS in cloud terminology= ; so adding the Cloud Print Service at least provides a cloud print SAAS.

 

 

Some more discussion ----------

&nbs= p;

I am still having a problem with the use of a Cloud P= rint Manager (in the printer) concept (an the name) in the general context = of being a cloud citizen and with associating a User with an individual Pri= nt Service (Printers).  That is, it is not modeled from User’s, = use-case or Cloud Provider developers’ point of view.  As curren= tly defined, the current Cloud Print Manager is an artifact of a particular= implementation (like DocuPrint; maybe even CUPS) for a fan out with a sing= le controller (Print Servcie?); from a reference model or architecture poin= t of view it should not matter if there is such an entity providing this fu= nction.  This means your simple diagram reduces to <= /p>

 

 

                 =        Cloud Print Provider

    Client  <--->  Cloud Print= Service <---> Printer

 =

With “””””R= 21;maybe””””” the Printer =3D [ Cloud Print M= anager <---> Printer(s) ]  as seen from Cloud Print Provider

 

A= ctually, I see no reason to add the Print qualifier to the Provider; that i= s,

 

                   &= nbsp;         Cloud Provider

    Client  <--->  C= loud Print Service <---> Printer

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

This model states that a Client, as a proxy for the User, can a= ccess a Print Service, of the User’s Cloud Provider, to print to a Us= er’s register print device.

 

This model can be used to represent several different soluti= ons or implementations:

 

  1. The “Cloud Provider” is Print Cloud (like HP’= s or Epson’s or)

&nbs= p;                   &nbs= p;     Print Cloud Provider

    Client  <--->  Cloud Print Service &l= t;---> Printer<= o:p>

    1. A good and bad model – requires other Cloud Solution to federate= with Print Cloud Provider.   This would be a big development eff= ort for print vendors.

 

 

 

  1. Cloud Print Services are integrated into a Cloud Provide= r like Google Cloud

  =                    &= nbsp;       Cloud Provider

    Client  <--->  Cloud Print S= ervice <---> Printer

    1. Again, good and bad.   Good for print ve= ndor in that the Cloud Provider manages Print Service; bad for the same rea= son.

&n= bsp;

 

 

  1. The Cloud Print Service is a “mini-cloud” or a “plug-in= cloud” (but still in the Cloud) that is callable by a Cloud Provider= .

 

           = ;                &nb= sp; Cloud Provider

    Client  <--->    \ &nbs= p;           \  = ;        

     &nbs= p;            &= nbsp;           \ &n= bsp;          \

=

  \ Cloud Print Servi= ce <---> Printer

Where there is cloud around both Cloud Print and Cloud Print Ser= vice

&n= bsp;

    1. Ye= s, this looks like model in the current specification but with some slight = differences.

         &n= bsp;            = ;            &n= bsp;            = ;            &n= bsp;   i.&nbs= p;     The Cloud Print Services are in the= cloud; thus, they are cloud SAAS

1.      Yes, the Print Service cou= ld be in the physical printer but virtually linked (“registered”= ;) in the Cloud

          &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;            ii.    = ;  A printer is associated with a single Cloud Print Serv= ice

1.    &= nbsp; >From the User’s and the Cloud Provider’s= point-of-view, one Print Service is associated with one Printer. &nbs= p; The User and Cloud Provider developers never know about fan-out, fin-in,= fan-up, fan-down or any kind of fan; they know there an associated Print S= ervices for a specific Printer.  

a.       Internally, an i= ndividual “Print Service” can support 2, 700,039 Printers; that= is something the print vendor does as part of their implementation detail.=    It will not affect the API’s the Cloud Provider develope= rs uses to print to the printer.  And has nothing to do with the PWG C= loud Print specification.

2.&n= bsp;     >From the User’s and the= Cloud Provider’s point-of-view, one Print Service (associated with o= ne Printer) has its own queue.  

a.       <= ![endif]>If a prin= t vendor wants to have individual queues (the “bucket” of Print= Jobs) for each printer or have one giant queue (a big “bucket”= ) that individual printers pull jobs from, this again, is a print vendor im= plementation detail.   And has nothing to do with the PWG Cloud P= rint specification.

          =             &nb= sp;            =             &nb= sp;           iii.=      = From the Cloud Provider’s point-of-view, the above defi= nitions makes all Cloud Print Service interfaces look the same; that it,

1.      <= /span>An individual Printer is registered and has an associated a sin= gle Print Service

2.  =     The Cloud Provider only talks to the Printe= r’s Print Service for all APIs and actions.

3.      Print Jobs= are submitted to the Print Service for the target printer (no matter how t= he queue is implemented)

         &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            iv.    &n= bsp; Thus, the goal of the PWG Cloud activity is to define the= API’s and data for the Cloud Provider to/from a Cloud Print Service<= o:p>

1.=      = I know – use IPP

= a.       = I don’t thin= k IPP will be used by everyone.   (Who is using it now for Cloud?= )  What “will be used” is the PWG:PJT, which does not requ= ire IPP to be useful.   PWG:PJT make federation of the Print Jobs= very simple.  In general PWG:PJT is a perfect candidate for cloud pri= nt.

 

So the final mo= del is something like

 

<= p class=3DMsoNormal>               =              Cloud = Provider           &= nbsp;        |------- a Directory/Regist= ry of Vendor Print Clouds

    Client  <--->    \ &n= bsp;           \ < ---= ----------------- register Printers (and its Print Service) to a User =

  &nbs= p;            &= nbsp;           &nbs= p;  \           &nbs= p;\

       = ;            &n= bsp;            = ;      \ Vendor M Print Cloud    &n= bsp;            = ;            &n= bsp;      \ Vendor N Print Cloud

         &nb= sp;             = ;            &n= bsp;            Prin= t Service <---> Printer        &nb= sp;            =             &nb= sp;          Print Service <= ;---> Printer

    = ;             &= nbsp;           &nbs= p;            &= nbsp;     Print Service <---> Printer  =              &n= bsp;            = ;            &n= bsp;   Print Service <---> Printer

          &n= bsp;            &nbs= p;            &= nbsp;           Print Ser= vice <---> Printer         &n= bsp;            = ;            &n= bsp;         Print Service <---&= gt; Printer

    &nbs= p;             =             &nb= sp;            =      Print Service <---> Printer   = ;             &= nbsp;           &nbs= p;            &= nbsp;  Print Service <---> Printer

            &n= bsp;            = ;            &n= bsp;          Print Service &l= t;---> Printer          &nb= sp;            =             &nb= sp;        Print Service <---> Pri= nter

      = ;             &= nbsp;           &nbs= p;            &= nbsp;   Print Service <---> Printer    =              &n= bsp;            = ;            &n= bsp; Print Service <---> Printer

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

glen

 

 

 

=  


From: Michael Sweet [mailto:msweet@apple.com]
Sent: Friday, April 06, 2012= 9:00 AM
To: Petrie, Glen
Cc: Peter Zehler; Ira Mcdonal= d; ipp@pwg.org; cloud@pwg.org
Subject: Re: [IPP] Where is the Cloud = Print Manager in the PWG: Cloud Model

 

[Adding cloud@pwg.org since this is a cloud discussio= n]

 

Glen,

&n= bsp;

In the original BOF-generated= functional model, the Cloud Print Manager is either located in the Printer= or attached to the Printer (e.g. in the local print server).  The Clo= ud Print Manager manages communications between the lower-level printer int= erface and the Cloud Print Provider.

 

Based on our l= ast telecon, we have introduced a Cloud Print Service into the model which = is the service in/under the Cloud Print Provider (which acts as a System Co= ntrol Service in the Semantic Model sense) that manages the jobs/queue in t= he cloud for the Cloud Print Manager.  The rough ASCII art diagram in = my mind looks like this:

 

 

             =      Cloud Print Provider

    Client  <--->  Cloud Print Servi= ce  <--->  Cloud Print Manager <---> Printer(s)<= /o:p>

 

Thus, Clients and Cloud Print Managers talk directly to = the Cloud Print Provider and corresponding Cloud Print Service, but never d= irectly to each other, and only the Cloud Print Manager actually talks dire= ctly with the Printer(s) (physical or logical) it is registering/sharing wi= th the Cloud Print Provider/Service.

 

There can pote= ntially be multiple logical or physical printers behind the Cloud Print Man= ager (think traditional fan-out configurations and reprographic services) a= nd those printers *may* be addressable using the IPP/SM output device attri= butes/elements, but there is only a single Cloud Print Service per Cloud Pr= int Manager and to the Client it will appear to be a single "queue&quo= t; with one or more output devices associated with it.

=

 

 

On Apr 6= , 2012, at 8:34 AM, "Petrie, Glen" <glen.petrie@eitc.epson.com> wrote:

 

Ira, Pete,

 

I = believe it was stated in the last conference call that the Cloud Print Mana= ger in the cloud model diagram “is not in the cloud”. &nbs= p; Is this true?  If so, where is it “located”? =

 

Glen

 


-- 
This message has been scanned for virus= es and 
dangerous conten= t by MailScanner, and is 
believed to = be clean. _______________________________________________
ipp mailing li= st
ipp@pwg.o= rg
https://www.pwg.org/mailman/listinfo/ipp
=

 

____________________________________= ______________

= Michael Sweet, Senior Printing System Engineer, PWG Chair

 


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


--= =20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0C55_01CD140E.B1496F90-- --===============0273886279== 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 --===============0273886279==-- From ipp-bounces@pwg.org Fri Apr 6 19:32:26 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 699D321F857A for ; Fri, 6 Apr 2012 19:32:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g6b13Qpsbza2 for ; Fri, 6 Apr 2012 19:32:25 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9B521F8559 for ; Fri, 6 Apr 2012 19:32:25 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C51F4796A4; Fri, 6 Apr 2012 22:32:02 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@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 73C827969F for ; Fri, 6 Apr 2012 22:31:45 -0400 (EDT) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta09.westchester.pa.mail.comcast.net with comcast id uqVS1i0050cZkys59qXljr; Sat, 07 Apr 2012 02:31:45 +0000 Received: from VistaBusiness ([98.216.178.129]) by omta10.westchester.pa.mail.comcast.net with comcast id uqXl1i00J2ntzM63WqXlY8; Sat, 07 Apr 2012 02:31:45 +0000 From: "William Wagner" To: "'Michael Sweet'" References: <4042A850-05EE-439B-889E-8F62CFC208AD@apple.com> In-Reply-To: <4042A850-05EE-439B-889E-8F62CFC208AD@apple.com> Date: Fri, 6 Apr 2012 22:31:42 -0400 Message-ID: <000601cd1466$924c5c30$b6e51490$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac0UHdaQR2HC83zZStan0iWjwKZIVwASHRzg Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] IPP Meeting Monday 9 April? 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="===============1835266541==" 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: C51F4796A4.A913E X-pwg-MailScanner-From: ipp-bounces@pwg.org This is a multi-part message in MIME format. --===============1835266541== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01CD1445.0B3ABC30" Content-Language: en-us This is a multi-part message in MIME format. ------=_NextPart_000_0007_01CD1445.0B3ABC30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Will there be a IPP call on Monday? It is listed in the last IPP minutes, but not mentioned in the Cloud/IPP minutes. Thanks, Bill Wagner -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------=_NextPart_000_0007_01CD1445.0B3ABC30 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Will ther= e be a IPP call on Monday? It is listed in the last IPP minutes, but not me= ntioned in the Cloud/IPP minutes.

Thanks, Bill Wagner


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. ------=_NextPart_000_0007_01CD1445.0B3ABC30-- --===============1835266541== 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 --===============1835266541==-- From ipp-bounces@pwg.org Sat Apr 7 07:31:06 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B46C921F8566 for ; Sat, 7 Apr 2012 07:31:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-1alJOyATDd for ; Sat, 7 Apr 2012 07:31:05 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id A447E21F8554 for ; Sat, 7 Apr 2012 07:31:05 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id ED6E37969F; Sat, 7 Apr 2012 10:30:46 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by pwg.org (Postfix) with ESMTP id 331117969C for ; Sat, 7 Apr 2012 10:30:29 -0400 (EDT) Received: by wgbdq13 with SMTP id dq13so2389208wgb.11 for ; Sat, 07 Apr 2012 07:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZKfmloeiLMpAkmHUfzWCB23J9yXlTBwpOfGR6h00UEU=; b=QjdqUO/AzVTrR073LKfXu4SqcTHynm1nXeujrP3+tfcD0k9yBCm2ZjnleBJRMoGfKf Q3lz/VRG/TlzO0dHNrg8IPKglHfqd7b+Uj3KD/JEWd0v0ik2V38KYEkyVp+ss+B7xGnl kc3CetEgJv1ymEG5dvVB3NBybhI56vkgYM29P/DYHtIrR3IVluyN5wDU4FM72IyH54YA HDUUViN1nQxMf5txV43f/j+taLVQ1xq6YC7oC+Cai6Yfds0j7YLYjY4dsLOJ+RZpEL6Q Cc4hFMnS4ilF8Oh5CkfHL7O3mi4lH8oYCxzdEEuYpkUywvlZw1+p8K4pfJns8KIbS6mj oAkg== MIME-Version: 1.0 Received: by 10.180.24.35 with SMTP id r3mr3657849wif.7.1333809029305; Sat, 07 Apr 2012 07:30:29 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Sat, 7 Apr 2012 07:30:29 -0700 (PDT) In-Reply-To: <000601cd1466$924c5c30$b6e51490$@net> References: <4042A850-05EE-439B-889E-8F62CFC208AD@apple.com> <000601cd1466$924c5c30$b6e51490$@net> Date: Sat, 7 Apr 2012 10:30:29 -0400 Message-ID: Subject: Re: [IPP] IPP Meeting Monday 9 April? From: Ira McDonald To: William Wagner , 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="===============1040993113==" 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: ED6E37969F.A9222 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1040993113== Content-Type: multipart/alternative; boundary=f46d043bdf2063d52304bd179d9b --f46d043bdf2063d52304bd179d9b Content-Type: text/plain; charset=ISO-8859-1 Hi Bill, Yes, there will be an IPP WG meeting this Monday. Review updated LDAP Printer Schema and (if available) updated IPP Everywhere, plus F2F planning. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Apr 6, 2012 at 10:31 PM, William Wagner wrote: > Will there be a IPP call on Monday? It is listed in the last IPP minutes, > but not mentioned in the Cloud/IPP minutes.**** > > Thanks, Bill Wagner **** > > -- > 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. --f46d043bdf2063d52304bd179d9b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Bill,

Yes, there will be an IPP WG meeting this Monday.

Re= view updated LDAP Printer Schema and (if
available) updated IPP Everywhe= re, plus F2F
planning.

Cheers,
- Ira

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



On Fri, Apr 6, 2012 at 10:31 PM, William= Wagner <wamw= agner@comcast.net> wrote:

Will there be a IPP call on Monday? It is li= sted in the last IPP minutes, but not mentioned in the Cloud/IPP minutes.

Thanks, Bill Wagner


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

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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d043bdf2063d52304bd179d9b-- --===============1040993113== 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 --===============1040993113==-- From ipp-bounces@pwg.org Sat Apr 7 14:08:00 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2C621F84CE for ; Sat, 7 Apr 2012 14:08:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.85 X-Spam-Level: X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[AWL=-1.248, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_HTML_MOSTLY=0.001, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mS7w3z1rPAxF for ; Sat, 7 Apr 2012 14:07:58 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8160721F84A2 for ; Sat, 7 Apr 2012 14:07:58 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 787EE796C2; Sat, 7 Apr 2012 17:07:32 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by pwg.org (Postfix) with ESMTP id 050F2796B8; Sat, 7 Apr 2012 17:07:14 -0400 (EDT) Received: by wgbdq13 with SMTP id dq13so2520638wgb.11 for ; Sat, 07 Apr 2012 14:07:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3yzBLxz52SBDeXY+KUWQ2I0FeNNAwuraCuSH5Tym+ig=; b=gqYTMKPnLJ0JEev9GHZW+ZHpIEeXNAwKGsJysqvTg+jW8OoGGUyCcpwoOuHTqwdCgq 4RQhENkdLn06w2w7JGfMZ0iJrPPNJpBVBMTUvHWlGIC8iNSVnfbCx/b6Ca0SU5OK99Qr Rj+l5LWc8r1NbsWMPiXMa1DcKax2jlL/DJpxr7kK/dX4dt3WJoSVwWCldOeBAEH/rm2z qXytYS75SCDQXk5Miw0y/4w6JCZFyBEAQZ0cRxnB5eMybDZnLRTRqhfyrvFRlCIstEUE aPQS9uBraBbcZW61dKqdsL6yQWXH9h+aCfudlW4xsfaUiSqDxEIbrYKmQjf8UqADjoNB +H4g== MIME-Version: 1.0 Received: by 10.180.107.101 with SMTP id hb5mr5178559wib.7.1333832834039; Sat, 07 Apr 2012 14:07:14 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Sat, 7 Apr 2012 14:07:13 -0700 (PDT) In-Reply-To: <0c2501cd1432$8c414320$a4c3c960$@comcast.net> References: <0c2501cd1432$8c414320$a4c3c960$@comcast.net> Date: Sat, 7 Apr 2012 17:07:13 -0400 Message-ID: Subject: Re: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: Cloud Model From: Ira McDonald To: larryupthegrove , Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org, cloud@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0759150450==" 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: 787EE796C2.A9E93 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0759150450== Content-Type: multipart/alternative; boundary=e89a8f3bb0cf43409d04bd1d2843 --e89a8f3bb0cf43409d04bd1d2843 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, I strongly urge that we keep the first class object Cloud Print Manager in the functional model. How the CPM communicates with actual Print Devices (Printers) is now and SHOULD remain completely out-of-scope. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Apr 6, 2012 at 4:19 PM, larryupthegrove wrote: > Glen,**** > > ** ** > > I=92m struggling with a number of statements, I agree the connection betw= een > the user and the cloud is one part of the model, and the other part is the > connection of the cloud to a logical print something or other (within my > system). Since the model started as an imaging model, I believe the clo= ud > to print connection should also be usable for a scan to cloud, with > different elements.**** > > ** ** > > As a user and implementer I=92m focusing on where the connection to the > cloud originates, and where the connection from the cloud is terminates.** > ** > > ** ** > > So where you have in the last drawing =96 Vendor M and Vendor N, are those > print services from different print vendors or?**** > > ** ** > > Larry**** > > ** ** > > *From:* cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] *On Behalf > Of *Petrie, Glen > *Sent:* Friday, April 06, 2012 10:35 AM > *To:* Michael Sweet > *Cc:* ipp@pwg.org; cloud@pwg.org > *Subject:* [Cloud] RE: [IPP] Where is the Cloud Print Manager in the PWG: > Cloud Model**** > > ** ** > > Mike,**** > > ** ** > > Thanks for the update. I was reviewing the diagram again and I had noted > there was no actual print entity =93in the cloud=94; that is, as an SAAS = in > cloud terminology; so adding the Cloud Print Service at least provides a > cloud print SAAS.**** > > ** ** > > ** ** > > Some more discussion ----------**** > > ** ** > > I am still having a problem with the use of a Cloud Print Manager (in the > printer) concept (an the name) in the general context of being a cloud > citizen and with associating a User with an individual Print Service > (Printers). That is, it is not modeled from User=92s, use-case or Cloud > Provider developers=92 point of view. As currently defined, the current > Cloud Print Manager is an artifact of a particular implementation (like > DocuPrint; maybe even CUPS) for a fan out with a single controller (Print > Servcie?); from a reference model or architecture point of view it should > not matter if there is such an entity providing this function. This means > your simple diagram reduces to **** > > ** ** > > ** ** > > Cloud Print Provider**** > > Client <---> Cloud Print Service <---> Printer**** > > ** ** > > With =93=94=94=94=94=94maybe=94=94=94=94=94 the Printer =3D [ Cloud Print= Manager <---> Printer(s) > ] as seen from Cloud Print Provider**** > > ** ** > > Actually, I see no reason to add the Print qualifier to the Provider; that > is,**** > > ** ** > > Cloud Provider**** > > Client <---> Cloud Print Service <---> Printer**** > > ** ** > > This model states that a Client, as a proxy for the User, can access a > Print Service, of the User=92s Cloud Provider, to print to a User=92s reg= ister > print device. **** > > ** ** > > This model can be used to represent several different solutions or > implementations:**** > > ** ** > > 1. The =93Cloud Provider=94 is Print Cloud (like HP=92s or Epson=92s o= r)**** > > Print Cloud Provider**** > > Client <---> Cloud Print Service <---> Printer**** > > 1. A good and bad model =96 requires other Cloud Solution to federate > with Print Cloud Provider. This would be a big development effort= for > print vendors. **** > > ** ** > > ** ** > > ** ** > > 1. Cloud Print Services are integrated into a Cloud Provider like > Google Cloud**** > > Cloud Provider**** > > Client <---> Cloud Print Service <---> Printer**** > > 1. Again, good and bad. Good for print vendor in that the Cloud > Provider manages Print Service; bad for the same reason.**** > > ** ** > > ** ** > > ** ** > > 1. The Cloud Print Service is a =93mini-cloud=94 or a =93plug-in cloud= =94 (but > still in the Cloud) that is callable by a Cloud Provider. **** > > ** ** > > Cloud Provider**** > > Client <---> \ \ **** > > \ \**** > > \ Cloud Print Service <---> Printer**** > > Where there is cloud around both Cloud Print and Cloud Print Service**** > > ** ** > > 1. Yes, this looks like model in the current specification but with > some slight differences.**** > > ** i. * > *The Cloud Print Services are in the cloud; thus, they are cloud SAAS **** > > **1. **Yes, the Print Service could be in the physical printer but > virtually linked (=93registered=94) in the Cloud**** > > ** ii. *= *A > printer is associated with a single Cloud Print Service**** > > **1. **>From the User=92s and the Cloud Provider=92s point-of-view, = one > Print Service is associated with one Printer. The User and Cloud Provid= er > developers never know about fan-out, fin-in, fan-up, fan-down or any kind > of fan; they know there an associated Print Services for a specific > Printer. **** > > **a. **Internally, an individual =93Print Service=94 can support 2, > 700,039 Printers; that is something the print vendor does as part of their > implementation detail. It will not affect the API=92s the Cloud Provider > developers uses to print to the printer. And has nothing to do with the > PWG Cloud Print specification.**** > > **2. **>From the User=92s and the Cloud Provider=92s point-of-view, = one > Print Service (associated with one Printer) has its own queue. **** > > **a. **If a print vendor wants to have individual queues (the > =93bucket=94 of Print Jobs) for each printer or have one giant queue (a b= ig > =93bucket=94) that individual printers pull jobs from, this again, is a p= rint > vendor implementation detail. And has nothing to do with the PWG Cloud > Print specification.**** > > ** iii. **= From > the Cloud Provider=92s point-of-view, the above definitions makes all Clo= ud > Print Service interfaces look the same; that it,**** > > **1. **An individual Printer is registered and has an associated a > single Print Service**** > > **2. **The Cloud Provider only talks to the Printer=92s Print Service > for all APIs and actions. **** > > **3. **Print Jobs are submitted to the Print Service for the target > printer (no matter how the queue is implemented)**** > > ** iv. **T= hus, > the goal of the PWG Cloud activity is to define the API=92s and data for = the > Cloud Provider to/from a Cloud Print Service**** > > **1. **I know =96 use IPP**** > > **a. **I don=92t think IPP will be used by everyone. (Who is using > it now for Cloud?) What =93will be used=94 is the PWG:PJT, which does not > require IPP to be useful. PWG:PJT make federation of the Print Jobs very > simple. In general PWG:PJT is a perfect candidate for cloud print. **** > > ** ** > > So the final model is something like**** > > ** ** > > Cloud Provider |------- a > Directory/Registry of Vendor Print Clouds**** > > Client <---> \ \ < -------------------- register > Printers (and its Print Service) to a User **** > > \ \**** > > \ Vendor M Print Cloud > \ Vendor N Print Cloud**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > Print Service <---> > Printer Print Service <---> > Printer**** > > ** ** > > glen**** > > ** ** > > ** ** > > ** ** > > ** ** > ------------------------------ > > *From:* Michael Sweet [mailto:msweet@apple.com] > *Sent:* Friday, April 06, 2012 9:00 AM > *To:* Petrie, Glen > *Cc:* Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org > *Subject:* Re: [IPP] Where is the Cloud Print Manager in the PWG: Cloud > Model**** > > ** ** > > [Adding cloud@pwg.org since this is a cloud discussion]**** > > ** ** > > Glen,**** > > ** ** > > In the original BOF-generated functional model, the Cloud Print Manager is > either located in the Printer or attached to the Printer (e.g. in the loc= al > print server). The Cloud Print Manager manages communications between the > lower-level printer interface and the Cloud Print Provider.**** > > ** ** > > Based on our last telecon, we have introduced a Cloud Print Service into > the model which is the service in/under the Cloud Print Provider (which > acts as a System Control Service in the Semantic Model sense) that manages > the jobs/queue in the cloud for the Cloud Print Manager. The rough ASCII > art diagram in my mind looks like this:**** > > ** ** > > ** ** > > Cloud Print Provider**** > > Client <---> Cloud Print Service <---> Cloud Print Manager <---> > Printer(s)**** > > ** ** > > Thus, Clients and Cloud Print Managers talk directly to the Cloud Print > Provider and corresponding Cloud Print Service, but never directly to each > other, and only the Cloud Print Manager actually talks directly with the > Printer(s) (physical or logical) it is registering/sharing with the Cloud > Print Provider/Service.**** > > ** ** > > There can potentially be multiple logical or physical printers behind the > Cloud Print Manager (think traditional fan-out configurations and > reprographic services) and those printers *may* be addressable using the > IPP/SM output device attributes/elements, but there is only a single Cloud > Print Service per Cloud Print Manager and to the Client it will appear to > be a single "queue" with one or more output devices associated with it.*** > * > > ** ** > > ** ** > > On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" > wrote:**** > > ** ** > > Ira, Pete,**** > > **** > > I believe it was stated in the last conference call that the Cloud Print > Manager in the cloud model diagram =93is not in the cloud=94. Is this t= rue? > If so, where is it =93located=94? **** > > **** > > Glen**** > > **** > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp**** > > ** ** > > __________________________________________________**** > > Michael Sweet, Senior Printing System Engineer, PWG Chair**** > > ** ** > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. **** > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e89a8f3bb0cf43409d04bd1d2843 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi,

I strongly urge that we keep the first class object Cloud
Pri= nt Manager in the functional model.=A0 How the CPM
communicates with act= ual Print Devices (Printers) is
now and SHOULD remain completely out-of-= scope.

Cheers,
- Ira

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



On Fri, Apr 6, 2012 at 4:19 PM, larryupt= hegrove <larryupthegrove@comcast.net> wrote:

Glen,

=A0

I=92m struggling with a n= umber of statements, I agree the connection between the user and the cloud = is one part of the model, and the other part is the connection of the cloud= to a logical print something or other (within my system).=A0=A0 Since the = model started as an imaging model, I believe the cloud to print connection = should also be usable for a scan to cloud, with different elements.<= u>

=A0<= /p>

As a user and implemen= ter I=92m focusing on where the connection to the cloud originates, and whe= re the connection from the cloud is terminates.

=A0<= /p>

So where you have in t= he last drawing =96 Vendor M and Vendor N, are those print services from di= fferent print vendors or?

=A0<= /p>

Larry

=A0<= /p>

From: cloud-bounces@pwg.org [mailto:cloud= -bounces@pwg.org] On Behalf Of Petrie, Glen
Sent: Friday, April 06, 2012 10:35 AM
To: Michael SweetCc: ipp@pwg.org; cloud@pwg.org
= Subject: [Cloud] RE: [IPP] Where is the Cloud Print Manager in the P= WG: Cloud Model

=A0=

Mike,

=A0

Thanks for the update.=A0=A0 I was reviewing the d= iagram again and I had noted there was no actual print entity =93in the clo= ud=94; that is, as an SAAS in cloud terminology; so adding the Cloud Print = Service at least provides a cloud print SAAS.

=A0

=A0

Some more discussion ----------

=A0

I am still having a problem with the use of a Clou= d Print Manager (in the printer) concept (an the name) in the general conte= xt of being a cloud citizen and with associating a User with an individual = Print Service (Printers).=A0 That is, it is not modeled from User=92s, use-= case or Cloud Provider developers=92 point of view. =A0As currently defined= , the current Cloud Print Manager is an artifact of a particular implementa= tion (like DocuPrint; maybe even CUPS) for a fan out with a single controll= er (Print Servcie?); from a reference model or architecture point of view i= t should not matter if there is such an entity providing this function.=A0 = This means your simple diagram reduces to

=A0

=A0

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0= =A0 Cloud Print Provider

=A0 =A0 Cl= ient =A0<---> =A0Cloud Print Service <---> Printer

=A0

With =93=94=94=94=94=94maybe=94=94=94=94=94 the Prin= ter =3D [ Cloud Print Manager <---> Printer(s) ]=A0 as seen from Clou= d Print Provider

=A0<= /p>

Actually, I see no reason to add the Print qualif= ier to the Provider; that is,

=A0

=A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0Cloud Provider

=A0 =A0 Client =A0<---> =A0Clo= ud Print Service <---> Printer

=A0

This model states that a Client, as a proxy for the User, can access a P= rint Service, of the User=92s Cloud Provider, to print to a User=92s regist= er print device.

=A0

This model can be used to represent several different solutions or imple= mentations:

=A0

  1. = The =93Cl= oud Provider=94 is Print Cloud (like HP=92s or Epson=92s or)<= /span>

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0= =A0=A0=A0 =A0Print Cloud Provider

= =A0 =A0 Client =A0<---> =A0Cloud Print Service <---> Printer<= u>

    1. <= span style=3D"font-family:"Cambria","serif"">A good and= bad model =96 requires other Cloud Solution to federate with Print Cloud P= rovider.=A0=A0 This would be a big development effort for print vendors.

=A0

=A0

=A0

  1. Cloud Pri= nt Services are integrated into a Cloud Provider like Google Cloud

=A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0Cloud Provider

=A0 =A0 Client =A0<---> =A0Cloud Print Service= <---> Printer

    1. Again, go= od and bad.=A0=A0 Good for print vendor in that the Cloud Provider manages = Print Service; bad for the same reason.
=

=A0

=A0

=A0

  1. The Cloud= Print Service is a =93mini-cloud=94 or a =93plug-in cloud=94 (but still in= the Cloud) that is callable by a Cloud Provider.

=A0

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0= =A0=A0=A0 =A0=A0=A0=A0Cloud Provider

=A0 =A0 Client =A0<--= -> =A0=A0 \=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 \=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0 \=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0\

=A0 \ Cloud Print Servic= e <---> Printer

Where there is cloud around both Cloud Print and Cloud Print= Service

=A0

  1. Yes, this loo= ks like model in the current specification but with some slight differences= .

=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0 i.=A0=A0=A0=A0=A0 The Cloud Print Servi= ces are in the cloud; thus, they are cloud SAAS

1.=A0=A0=A0=A0=A0 Yes, the Print Service could be in the physical printer = but virtually linked (=93registered=94) in the Cloud

=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 ii.=A0=A0= =A0=A0=A0 A printer is associated with a sing= le Cloud Print Service

1.=A0=A0=A0=A0=A0 >From the User=92s and the Cloud Provider=92s point-o= f-view, one Print Service is associated with one Printer.=A0=A0 The User an= d Cloud Provider developers never know about fan-out, fin-in, fan-up, fan-d= own or any kind of fan; they know there an associated Print Services for a = specific Printer. =A0

a.=A0=A0=A0=A0=A0=A0 <= /span>Internally, an individual =93Print Service=94 can sup= port 2, 700,039 Printers; that is something the print vendor does as part o= f their implementation detail.=A0=A0 It will not affect the API=92s the Clo= ud Provider developers uses to print to the printer. =A0And has nothing to = do with the PWG Cloud Print specification.

2.=A0=A0=A0=A0=A0 >From the User=92s and the Cloud Provider=92s point-o= f-view, one Print Service (associated with one Printer) has its own queue.= =A0=A0

a.=A0=A0=A0=A0=A0=A0 <= /span>If a print vendor wants to have individual queues (th= e =93bucket=94 of Print Jobs) for each printer or have one giant queue (a b= ig =93bucket=94) that individual printers pull jobs from, this again, is a = print vendor implementation detail. =A0=A0And has nothing to do with the PW= G Cloud Print specification.

=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 iii.=A0=A0=A0= =A0=A0 From the Cloud Provider=92s point-of-v= iew, the above definitions makes all Cloud Print Service interfaces look th= e same; that it,

1.=A0=A0=A0=A0=A0 An individual Printer is registered and has an associate= d a single Print Service

2.=A0=A0=A0=A0=A0 The Cloud Provider only talks to the Printer=92s Print S= ervice for all APIs and actions.

3.=A0=A0=A0=A0=A0 Print Jobs are submitted to the Print Service for the ta= rget printer (no matter how the queue is implemented)<= /p>

=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 iv.=A0=A0=A0=A0= =A0 Thus, the goal of the PWG Cloud activity = is to define the API=92s and data for the Cloud Provider to/from a Cloud Pr= int Service

1.=A0=A0=A0=A0=A0 I know =96 use IPP

a.=A0=A0=A0=A0=A0=A0 <= /span>I don=92t think IPP will be used by everyone.=A0=A0 (= Who is using it now for Cloud?) =A0What =93will be used=94 is the PWG:PJT, = which does not require IPP to be useful. =A0=A0PWG:PJT make federation of t= he Print Jobs very simple.=A0 In general PWG:PJT is a perfect candidate for= cloud print.

=A0

So the final model is something like

=A0

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0Cloud P= rovider=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |------- a= Directory/Registry of Vendor Print Clouds

=A0 =A0 Client =A0<--= -> =A0=A0 \=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 \ < -----------------= --- register Printers (and its Print Service) to a User

<= p class=3D"MsoNormal" style=3D"margin-left:.25in"> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 \=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0\

=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0\ Vendor M Print Cloud= =A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0\ Vendor N Print Cloud

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Print Se= rvice <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 Print Service <---> Printer

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Print= Service <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 Print Service <---> Printer

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 Print Service <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 Print Service <---> Printer

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0 Print Service <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 Print Service <---> Printer=

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 Print Service <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 Print Service <---> Printer

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0 Print Service <---> Printer=A0=A0=A0=A0=A0=A0=A0 =A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0 Print Service <---> Printer=

=A0

glen

=A0

=A0

=A0

=A0


From: Mi= chael Sweet = [mailto:msweet@apple.com]
Sent: Friday, April 06, 2012 9:00 AM
To: Petrie, Glen
<= b>Cc: Peter Zehler; Ira Mcdonald; ipp@pwg.org; cloud@pwg.org
Subject: Re: [IPP] Where is the Cloud Print Manager in the PWG: Clou= d Model

=A0<= /u>

[Adding cloud@pwg.org since this is a cloud discussion]

=A0

Glen,

=A0

In the original BOF-generated funct= ional model, the Cloud Print Manager is either located in the Printer or at= tached to the Printer (e.g. in the local print server). =A0The Cloud Print = Manager manages communications between the lower-level printer interface an= d the Cloud Print Provider.

=A0

Based on our last telecon, we have introduced a Cloud Print = Service into the model which is the service in/under the Cloud Print Provid= er (which acts as a System Control Service in the Semantic Model sense) tha= t manages the jobs/queue in the cloud for the Cloud Print Manager. =A0The r= ough ASCII art diagram in my mind looks like this:

=A0

=A0

=A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Cloud Print Provider

=A0 =A0 Client =A0<---> =A0Cloud Print Service =A0<---> =A0Clou= d Print Manager <---> Printer(s)

=A0

Thus,= Clients and Cloud Print Managers talk directly to the Cloud Print Provider= and corresponding Cloud Print Service, but never directly to each other, a= nd only the Cloud Print Manager actually talks directly with the Printer(s)= (physical or logical) it is registering/sharing with the Cloud Print Provi= der/Service.

=A0

There can potentially be multiple logical or physical printe= rs behind the Cloud Print Manager (think traditional fan-out configurations= and reprographic services) and those printers *may* be addressable using t= he IPP/SM output device attributes/elements, but there is only a single Clo= ud Print Service per Cloud Print Manager and to the Client it will appear t= o be a single "queue" with one or more output devices associated = with it.

=A0

=A0

On Apr 6, 2012, at 8:34 AM, "Petrie, Glen" <glen.petrie@eitc.epson.c= om> wrote:

=A0

Ira, Pete,

=A0

I believe it was stated in the = last conference call that the Cloud Print Manager in the cloud model diagra= m =93is not in the cloud=94.=A0=A0 Is this true?=A0 If so, where is it =93l= ocated=94?=A0

=A0

Glen

=A0


--=A0
This message has been scanned for viruses and= =A0
dangerous content by=A0MailScann= er, and is=A0
believed to be clean. _______________________________________________
ip= p mailing list
ipp@pwg.org
htt= ps://www.pwg.org/mailman/listinfo/ipp

=A0

_____________________________________________= _____

Michael Sweet, Senior Prin= ting System=A0Engineer, PWG Chair

=A0


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


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

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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e89a8f3bb0cf43409d04bd1d2843-- --===============0759150450== 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 --===============0759150450==-- From ipp-bounces@pwg.org Sat Apr 7 15:56:44 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0A521F8534 for ; Sat, 7 Apr 2012 15:56:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8KEz2IrrDcF for ; Sat, 7 Apr 2012 15:56:43 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id C284521F84DD for ; Sat, 7 Apr 2012 15:56:43 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 37C28796BA; Sat, 7 Apr 2012 18:56:23 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 173657969E for ; Sat, 7 Apr 2012 18:56:05 -0400 (EDT) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2400K43T1BGRN0@mail-out.apple.com> for ipp@pwg.org; Sat, 07 Apr 2012 15:56:05 -0700 (PDT) X-AuditID: 11807134-b7fea6d000003dbe-a1-4f80c604b9aa Received: from [17.151.67.230] (Unknown_Domain [17.151.67.230]) by relay14.apple.com (Apple SCV relay) with SMTP id BB.60.15806.406C08F4; Sat, 07 Apr 2012 15:56:04 -0700 (PDT) From: Michael Sweet In-reply-to: <000601cd1466$924c5c30$b6e51490$@net> Date: Sat, 07 Apr 2012 15:56:22 -0700 Message-id: <10C0E1E1-87AD-4187-BEF8-769D97D1F324@apple.com> References: <4042A850-05EE-439B-889E-8F62CFC208AD@apple.com> <000601cd1466$924c5c30$b6e51490$@net> To: William Wagner X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUiON35mS7LsQZ/gwNzTS2O7XvJYnHkW6zF uQuKDsweW0/+YPOY/HgOo8e8xdOZApijuGxSUnMyy1KL9O0SuDLeXCwvWKJc0dMl0MD4U66L kZNDQsBE4teug6wQtpjEhXvr2UBsIYGNjBIbWsBqhAU0JKZM+McOYvMKGErMfNUOVs8skCBx a9tmsDibgJrE70l9YHFOASOJ3/Nngs1hEVCROHJhERNEPb/Ewd4PzBBzbCSWdc4FsrmAdvUz ScxdvB+sQURAS+LTg+OMEAfJStw+uJ9pAiPfLCS7ZyHZDWFrSyxb+Jp5FiMHkK0jMXkhI6ow hP3x/BGmBYxsqxgFi1JzEisNTfQSCwpyUvWS83M3MYICtqHQZAfjwZ/8hxgFOBiVeHgtdzf4 C7EmlhVX5h5ilOBgVhLhvX8YKMSbklhZlVqUH19UmpNafIhRmoNFSZw3TLvKX0ggPbEkNTs1 tSC1CCbLxMEp1cCoYdTioZU3NcSrOfFCzuJqNw6+67fCztRpLY99Zx21u2Fitlq2efjFnVF/ ujz57y95ulHattBgqeqlaXoiswwl9n/x2CMpZdjSVNA5Rfb56Z+nq+fXyi88pfJxrufTC74K orp1Ml9ibzLnvPdyUNhwub/mwpb0TXPeRppcN3D3ZDV9vNZ1SpoSS3FGoqEWc1FxIgD+YM3/ VAIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org Subject: [IPP] Re: IPP Meeting Monday 9 April? 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="===============2017997136==" 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: 37C28796BA.A946C X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2017997136== Content-type: multipart/alternative; boundary="Boundary_(ID_98aYEph/2oXLxhmINp48Dg)" --Boundary_(ID_98aYEph/2oXLxhmINp48Dg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Bill, Yes, at the usual time. Assuming that Ira will post an official agenda, this is the planned agenda based on our last meeting: 0. Administrivia 1. Status of everything 2. Review of LDAP Printer Schema 3. Review of IPP Everywhere 4. Next Steps On Apr 6, 2012, at 7:31 PM, William Wagner wrote: > Will there be a IPP call on Monday? It is listed in the last IPP minutes, but not mentioned in the Cloud/IPP minutes. > Thanks, Bill Wagner _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_98aYEph/2oXLxhmINp48Dg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable
Will there be a IPP call on Mo= nday? It is listed in the last IPP minutes, but not mentioned in the Cloud/= IPP minutes.
Thanks, Bill Wagner<= o:p>

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_98aYEph/2oXLxhmINp48Dg)-- --===============2017997136== 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 --===============2017997136==-- From ipp-bounces@pwg.org Sun Apr 8 08:07:42 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6562421F8533 for ; Sun, 8 Apr 2012 08:07:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InFn96tuUg+u for ; Sun, 8 Apr 2012 08:07:41 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6554921F852A for ; Sun, 8 Apr 2012 08:07:40 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id AEC177969B; Sun, 8 Apr 2012 11:07:23 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by pwg.org (Postfix) with ESMTP id E521A7969B for ; Sun, 8 Apr 2012 11:07:02 -0400 (EDT) Received: by wibhr14 with SMTP id hr14so1525280wib.11 for ; Sun, 08 Apr 2012 08:07:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=o9e5xXqYoniXHewVDm8jiNuxeKQnxYM3vIkeWrF9Zt4=; b=EAxbxYpuTHzVY9KDiwdKWVttbyGi8XdqzB61Dp+KNlVPKSr00pESflIF0UOaBkK1lm xx8AaLThOnZ2mfngqqNwZB5Y0177HIXyZD/sssD09gY/Lhq7DnNr41DoqH6QOT8nXJNc 2ArXXW/YqbA9nsS1NDACodiva6Hqfx6XZjwY42lUfZ8xkTnMWQM3rIZMcpabcYEjVVHw OSRFN5m4f9zc94bYZiiXlgVM0fPxbfB8wKUDZx1banAGo2PNT5NBFlqDxKrm0xS0v/PA Et42eSUgdalwDVUMWyi4JLxundpS8yGtblZgmOSsztxT2XHdPQnkuzpxXf4bOR2EXktk Idvw== MIME-Version: 1.0 Received: by 10.180.76.240 with SMTP id n16mr9543624wiw.10.1333897621783; Sun, 08 Apr 2012 08:07:01 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Sun, 8 Apr 2012 08:07:01 -0700 (PDT) Date: Sun, 8 Apr 2012 11:07:01 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Agenda - 3-5pm EDT Monday 9 April 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0944878392==" 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: AEC177969B.AA02E X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0944878392== Content-Type: multipart/alternative; boundary=f46d043c7b22e9c52104bd2c3d69 --f46d043c7b22e9c52104bd2c3d69 Content-Type: text/plain; charset=ISO-8859-1 Hi, Our next IPP WG call will be next Monday for TWO HOURS! Monday 9 April 12-2pm US PDT / 3-5pm US 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. ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://appleinc.webex.com/appleinc/j.php?ED=196599942&UID=0&PW=NZmQ4YmNmNjI1&RT=MiM0 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: pwg123 4. Click "Join". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link: https://appleinc.webex.com/appleinc/j.php?ED=196599942&UID=0&PW=NZmQ4YmNmNjI1&ORT=MiM0 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://appleinc.webex.com/appleinc/mc 2. On the left navigation bar, click "Support". *** Main Objective - Review LDAP Printer Schema and IPP Everywhere specs *** Agenda: (1) PWG IP Policy and Minute Taker - Mike? (2) Approve IPP minutes from previous meeting - ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120326.pdf (3) Status of PWG Raster vote (ends 13 April) - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20120314.pdf (4) Status of IPP Everywhere specs - planning for WG last calls before April F2F (5) Review of LDAP Printer Schema - ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ldap-printer-schema-01-20120403.pdf - PDF of plaintext w/ line numbers (6) Review of IPP Everywhere - to be posted by Mike (7) Next Steps - IPP WG session on Wednesday 25 April at Joint PWG/OPS meeting - IPP WG teleconference on Monday 7 May Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d043c7b22e9c52104bd2c3d69 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

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

=A0 Monday 9 April 12-2pm US PDT / 3-5pm US EDT

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

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

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


-------------------------------------------------------
To join = the online meeting (Now from mobile devices!)
--------------------------= -----------------------------
1. Go to https://appleinc.webex.com/appleinc/j.php?ED=3D196599942&UID= =3D0&PW=3DNZmQ4YmNmNjI1&RT=3DMiM0
2. If requested, enter your name and email address.
3. If a password is = required, enter the meeting password: pwg123
4. Click "Join".<= br>5. Follow the instructions that appear on your screen.
To view in oth= er time zones or languages, please click the link:
https://appleinc.webex.com/appl= einc/j.php?ED=3D196599942&UID=3D0&PW=3DNZmQ4YmNmNjI1&ORT=3DMiM0=

-------------------------------------------------------
For assistance
-------------------------------------------------------1. Go to https://apple= inc.webex.com/appleinc/mc
2. On the left navigation bar, click "= ;Support".


*** Main Objective - Review LDAP Printer Schema and IPP Everywhere specs **= *

Agenda:

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

(2) Approve IPP minutes from previous meeting
=A0=A0 =A0 - = ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120326.pdf<= /a>

(3) Status of PWG Raster vote (ends 13 April)
=A0=A0=A0=A0 -
ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraste= r10-20120314.pdf

(4) Status of IPP Everywhere specs
=A0=A0=A0= =A0 - planning for WG last calls before April F2F

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d043c7b22e9c52104bd2c3d69-- --===============0944878392== 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 --===============0944878392==-- From ipp-bounces@pwg.org Sun Apr 8 08:11:07 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88F821F855D for ; Sun, 8 Apr 2012 08:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.432 X-Spam-Level: X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTIfKTg+4CeW for ; Sun, 8 Apr 2012 08:11:06 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id AC2CD21F84FE for ; Sun, 8 Apr 2012 08:11:06 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 7E07D7965A; Sun, 8 Apr 2012 11:10:50 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by pwg.org (Postfix) with ESMTP id AF54779653 for ; Sun, 8 Apr 2012 11:10:34 -0400 (EDT) Received: by wgbds11 with SMTP id ds11so1561674wgb.5 for ; Sun, 08 Apr 2012 08:10:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=9R8BKe04pmsKGy3L+z+9TlN9Wk/LHoUibj33L6EWGQg=; b=AviKep9v9xLB5siTVURO58j0rh309+bK82AV+ROunWLr6URzKi/R9kaLgOxdZ+Ca/Q WxorCh9gyptsBnRGj2U0GN3y+ardQxNyOL2XJGuTYw9LTJxonIsZCpqSexr588zqoETz wqdi+9kJxYJ7fWexlju5ujv5A9z1sjWxJohwkJkcRBCetiWPv8rHJtU1CXuOWofWwzcB 9cfKYASUKIhkCeRLJIf6yYh8Ls5rWpjfnQFSR4PSjd8HIn22geOpUS6+/t4VGdn2q+1b GfxYk1FdeUiTb5IruJaJM9YMbLdUAg70hzVXfpepzRvl8WE1z00ZohrWv9Ud4zFiqT4w 0FPQ== MIME-Version: 1.0 Received: by 10.180.24.66 with SMTP id s2mr9658107wif.7.1333897833800; Sun, 08 Apr 2012 08:10:33 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Sun, 8 Apr 2012 08:10:33 -0700 (PDT) Date: Sun, 8 Apr 2012 11:10:33 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] Revised - IPP Agenda - 3-5pm EDT Monday 9 April 2012 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1573849010==" 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: 7E07D7965A.A9C71 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1573849010== Content-Type: multipart/alternative; boundary=f46d043be1d08ce21304bd2c4a41 --f46d043be1d08ce21304bd2c4a41 Content-Type: text/plain; charset=ISO-8859-1 [Corrected link to IPP minutes below] On Sun, Apr 8, 2012 at 11:07 AM, Ira McDonald wrote: > Hi, > > Our next IPP WG call will be next Monday for TWO HOURS! > > Monday 9 April 12-2pm US PDT / 3-5pm US 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. > > > ------------------------------------------------------- > To join the online meeting (Now from mobile devices!) > ------------------------------------------------------- > 1. Go to > https://appleinc.webex.com/appleinc/j.php?ED=196599942&UID=0&PW=NZmQ4YmNmNjI1&RT=MiM0 > 2. If requested, enter your name and email address. > 3. If a password is required, enter the meeting password: pwg123 > 4. Click "Join". > 5. Follow the instructions that appear on your screen. > To view in other time zones or languages, please click the link: > > https://appleinc.webex.com/appleinc/j.php?ED=196599942&UID=0&PW=NZmQ4YmNmNjI1&ORT=MiM0 > > ------------------------------------------------------- > For assistance > ------------------------------------------------------- > 1. Go to https://appleinc.webex.com/appleinc/mc > 2. On the left navigation bar, click "Support". > > > *** Main Objective - Review LDAP Printer Schema and IPP Everywhere specs > *** > > Agenda: > > (1) PWG IP Policy and Minute Taker > - Mike? > > (2) Approve IPP minutes from previous meeting > - > ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120326.pdf > > (3) Status of PWG Raster vote (ends 13 April) > - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20120314.pdf > > (4) Status of IPP Everywhere specs > - planning for WG last calls before April F2F > > (5) Review of LDAP Printer Schema > - > ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ldap-printer-schema-01-20120403.pdf > - PDF of plaintext w/ line numbers > > (6) Review of IPP Everywhere > - to be posted by Mike > > (7) Next Steps > - IPP WG session on Wednesday 25 April at Joint PWG/OPS meeting > - IPP WG teleconference on Monday 7 May > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - TCG Embedded Systems Hardcopy SG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music/High North Inc > http://sites.google.com/site/blueroofmusic > http://sites.google.com/site/highnorthinc > mailto:blueroofmusic@gmail.com > Winter 579 Park Place Saline, MI 48176 734-944-0094 > Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d043be1d08ce21304bd2c4a41 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable [Corrected link to IPP minutes below]

On = Sun, Apr 8, 2012 at 11:07 AM, Ira McDonald <blueroofmusic@gmail.com> wro= te:
Hi,

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

=A0 Monday 9 April 12-2pm US PDT / 3-5pm US EDT

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

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

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


-------------------------------------------------------
To join = the online meeting (Now from mobile devices!)
--------------------------= -----------------------------
1. Go to https://appleinc.webex.com/appleinc/j.php?ED=3D= 196599942&UID=3D0&PW=3DNZmQ4YmNmNjI1&RT=3DMiM0
2. If requested, enter your name and email address.
3. If a password is = required, enter the meeting password: pwg123
4. Click "Join".<= br>5. Follow the instructions that appear on your screen.
To view in oth= er time zones or languages, please click the link:
https://apple= inc.webex.com/appleinc/j.php?ED=3D196599942&UID=3D0&PW=3DNZmQ4YmNmN= jI1&ORT=3DMiM0

-------------------------------------------------------
For assistance
-------------------------------------------------------1. Go to https://appleinc.webex.com/appleinc/mc
2. On the left navigatio= n bar, click "Support".


*** Main Objective - Review LDAP Printer Schema and IPP Everywhere specs **= *

Agenda:

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

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

(3) Status of PWG Raster vote (ends 13 April)
=A0=A0=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraste= r10-20120314.pdf

(4) Status of IPP Everywhere specs
=A0=A0=A0= =A0 - planning for WG last calls before April F2F

(5) Review of LDAP Printer Schema
=A0=A0=A0=A0 - ftp://ftp.pwg.org/pub/pwg/ipp/wd/draft-mcdonald-ldap-pr= inter-schema-01-20120403.pdf
=A0=A0=A0=A0=A0=A0 - PDF of plaintext w/ line numbers

(6) Review of = IPP Everywhere
=A0=A0=A0=A0 - to be posted by Mike

(7) Next Steps=
=A0=A0=A0=A0 - IPP WG session on Wednesday 25 April at Joint PWG/OPS me= eting
=A0=A0=A0=A0 - IPP WG teleconference on Monday 7 May

Cheers,
- Ira


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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d043be1d08ce21304bd2c4a41-- --===============1573849010== 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 --===============1573849010==-- From pwg-announce-bounces@pwg.org Sun Apr 8 15:00:59 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8280021F84F6 for ; Sun, 8 Apr 2012 15:00:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8qRSPRLMCgC for ; Sun, 8 Apr 2012 15:00:58 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 94C8F21F84B5 for ; Sun, 8 Apr 2012 15:00:58 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id BE06A796B6; Sun, 8 Apr 2012 18:00:38 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id EA707796AF for ; Sun, 8 Apr 2012 18:00:20 -0400 (EDT) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2600C6PL4KG510@mail-out.apple.com> for pwg-announce@pwg.org; Sun, 08 Apr 2012 15:00:20 -0700 (PDT) X-AuditID: 11807136-b7f056d0000026ba-83-4f820a6b2203 Received: from [17.151.73.238] (Unknown_Domain [17.151.73.238]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id 4D.13.09914.17A028F4; Sun, 08 Apr 2012 15:00:19 -0700 (PDT) From: Michael Sweet Date: Sun, 08 Apr 2012 15:00:09 -0700 To: pwg-announce@pwg.org Message-id: <711F40ED-F6A6-47A4-8335-65CD2B5D3E10@apple.com> X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUiON3znW4xV5O/wZbbNhZHvsVarGtdzezA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZUw984KlYJJmxcebf5kbGCepdDFyckgImEhc XLKeGcIWk7hwbz1bFyMXh5DAVCaJ/98vsIAk2ATUJH5P6mMFsZkFEiSatjwBa2ARUJHYPOUI WI2wQIzEs//XwWwRAQmJad3zwOp5BWwkNrS+ZoOwDSVmvmpnhVgmK3H74H6mCYzcs5CMnYWk DCKuLbFs4WugOAeQrSMxeSEjqjCE/fH8EaYFjGyrGAWLUnMSKw1N9RILCnJS9ZLzczcxgkKr odBsB+OOv3KHGAU4GJV4eB/uaPAXYk0sK67MPcQowcGsJML78FqjvxBvSmJlVWpRfnxRaU5q 8SFGaQ4WJXHecO0qfyGB9MSS1OzU1ILUIpgsEwenVAPjtskzzgaU/lUrv/f/WJz0k8SnL9i3 5Zi8jzhWZfzB5sfBNavneYXdKeUX2L/w9VzdSsW+PVyNk0VkvvTedDP2M5dgXl19OCZ/b4fZ xhXrCuY92ftsi3f8+U0Vk95dipt0YskevbnFcQsFrj+bpCvHdHwZ941l4f47Fhje5Nb5wR4q 3Xc9zjI2SImlOCPRUIu5qDgRAAvLjXApAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] REMINDER: Joint PWG/Open Printing April 2012 Face-to-Face meeting in Cupertino, CA X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1696638896==" 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: BE06A796B6.AC840 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1696638896== Content-type: multipart/alternative; boundary="Boundary_(ID_lexJg0aqVbB6lIs/A+IuSQ)" --Boundary_(ID_lexJg0aqVbB6lIs/A+IuSQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT [THIS IS A REMINDER FOR ALL OF YOU THAT HAVEN'T GONE TO THE SURVEY PAGE YET...] All, The joint PWG/OpenPrinting face-to-face meeting page for April 2012 is now available. The agenda and venue information can be found at: http://www.pwg.org/chair/meeting-info/april_2012_cupertino.html This page will be updated with document links as the material becomes available. Please visit the April 2012 survey page PRIOR TO APRIL 13, 2012 and indicate whether you plan to participate in person or call in: http://www.surveymonkey.com/s/3XNMDK8 For those not able to attend in person, the usual telephone bridge number will be provided. The details of the conference call are: Call-in toll-free number (US/Canada): +1 866 469-3239 Call-in toll number (US/Canada): +1 650 429-3300 Call-in toll number (US/Canada): +1 408 856-9570 Attendee access code: Please request from the PWG Chair (msweet@apple.com) if you need it. ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_lexJg0aqVbB6lIs/A+IuSQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable
[THIS IS A REMINDER F= OR ALL OF YOU THAT HAVEN'T GONE TO THE SURVEY PAGE YET...]

All,

The joint PWG/OpenPrinting face-to-face meeting= page for April 2012 is now available. The agenda and venue infor= mation can be found at:


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

Please visit the April 2012 survey page PRIOR TO APRIL 13,= 2012 and indicate whether you plan to participate in person or call in:


For tho= se not able to attend in person, the usual telephone bridge number will&nbs= p;be provided. The details of the conference call are:

Call-in toll-free number (US/Canada): +1 866 469-3239
Call-in toll nu= mber (US/Canada): +1 650 429-3300
Call-in toll number (US/Canada): +1 40= 8 856-9570

Attendee access code: Please request from the = PWG Chair (msweet@apple.com) if you= need it.

_______________________________________________________= _________________
Michael Sweet, Senior Printing System Engineer,= PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_lexJg0aqVbB6lIs/A+IuSQ)-- --===============1696638896== 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 --===============1696638896==-- From ipp-bounces@pwg.org Sun Apr 8 20:58:33 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC46421F8623 for ; Sun, 8 Apr 2012 20:58:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZatiarClKLVN for ; Sun, 8 Apr 2012 20:58:33 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0A621F8627 for ; Sun, 8 Apr 2012 20:58:33 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CA2E0796C6; Sun, 8 Apr 2012 23:58:11 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 9523A796BE for ; Sun, 8 Apr 2012 23:57:54 -0400 (EDT) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2700CGF1OHG5C0@mail-out.apple.com> for ipp@pwg.org; Sun, 08 Apr 2012 20:57:53 -0700 (PDT) X-AuditID: 11807134-b7fea6d000003dbe-62-4f825e39f42c Received: from [17.151.74.56] (Unknown_Domain [17.151.74.56]) (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.01.15806.E3E528F4; Sun, 08 Apr 2012 20:57:53 -0700 (PDT) From: Michael Sweet Date: Sun, 08 Apr 2012 20:57:43 -0700 To: ipp@pwg.org Message-id: <41AA0201-6365-4D2E-936D-84D9A40B4854@apple.com> X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiON3LQtcxrsnfYNsneYtj+16yWBz5FuvA 5LH15A82j3mLpzMFMEVx2aSk5mSWpRbp2yVwZTw+pFxwXq5i3a4u5gbGq9JdjJwcEgImEpNn /mGEsMUkLtxbzwZiCwlMZpKYuK0SxGYTUJP4PamPFcRmFkiQaNrwngnEZhFQkTixoRmsV1hA R6Ln1EEWEFtEgF9i4kWIel4BG4kXT19D2YYSM1+1s0LskpW4fXA/0wRG7llIxs5CUgYRl5fY /nYO8yxGDiBbR2LyQkaIsLbEsoWvmWHsj+ePMC1gZFvFKFiUmpNYaWiil1hQkJOql5yfu4kR FFYNhSY7GA/+5D/EKMDBqMTDqyjb5C/EmlhWXJl7iFGCg1lJhPfhtUZ/Id6UxMqq1KL8+KLS nNTiQ4zSHCxK4rxh2lX+QgLpiSWp2ampBalFMFkmDk6pBkYWw2XlLUvcV9+4dO0k28r1ufIv 1R05FaxXTEwRYlq9bWHSm5Byw6XimWxCF2+nzXm0MFHuwREtAxaO+P3LZq73bDJ/26ZRN+dz DWeRc7/MtEtJhbEndVY4hhfM+N6j32TmMUlZr+Jl6IPcFQaFvjEHD9++s2Dam9sBJ/2Z/zh+ W86wiVvSuVSJpTgj0VCLuag4EQAIk2UUJwIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Updated IPP Everywhere draft posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1108414634==" 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: CA2E0796C6.A909A X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1108414634== Content-type: multipart/alternative; boundary="Boundary_(ID_XdpXTLbdywR99EP4t0aVPg)" --Boundary_(ID_XdpXTLbdywR99EP4t0aVPg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted an updated IPP Everywhere draft to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve10-20120408.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve10-20120408.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve10-20120408-rev.pdf For review at the IPP conference call. ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_XdpXTLbdywR99EP4t0aVPg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted an updated IPP Everywhere draft to:


=
For review at the IPP conference call.

=
_______________________________________________________= _________________
Michael Sweet, Senior Printing System Engineer,= PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_XdpXTLbdywR99EP4t0aVPg)-- --===============1108414634== 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 --===============1108414634==-- From pwg-announce-bounces@pwg.org Mon Apr 9 08:40:33 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C64321F8741 for ; Mon, 9 Apr 2012 08:40:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXa1pRdbId67 for ; Mon, 9 Apr 2012 08:40:31 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id AF8F421F8745 for ; Mon, 9 Apr 2012 08:40:31 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id A49E7796D0; Mon, 9 Apr 2012 11:40:05 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by pwg.org (Postfix) with ESMTP id CCB5D796CF for ; Mon, 9 Apr 2012 11:39:48 -0400 (EDT) Received: by wibhr17 with SMTP id hr17so2244282wib.5 for ; Mon, 09 Apr 2012 08:39:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lBcGJiUwEX+7uKu4sqoOYAXMNgMWV99GLc4EcOqCv4w=; b=S/grrSGleqoC65WUj6kD9ev9c5AeLh7EQ69giY/JIZXHVv1j2z71QFBjcSL71OW/NA 6k8mJyuwtOx5N51rylHgYKRT3gsJQlIkXcZIK2opRuYqw3ws0SXW4UE7nQFt8wRM5Uns PLtU4hs4PssEWn0Nkm5zIXFAh5Mz99gav7Lrxejp7oOfRqgY/3fCa0CbF2sqX7pUaacK jWOtLLsyMRDaClSZubKRurg8DXipXRqoANwB/A7GnFPY8E0L2NXjF1tYY1N1JjGgkXeZ HFEA1QLHAaEWnJQFxcRHUjZ7A934y3pStMwXWDy0IpLQrDmONZVFmEU4bgjNpOMJS+zO xG8Q== MIME-Version: 1.0 Received: by 10.216.135.219 with SMTP id u69mr4154785wei.89.1333985987934; Mon, 09 Apr 2012 08:39:47 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Mon, 9 Apr 2012 08:39:47 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Apr 2012 11:39:47 -0400 Message-ID: From: Ira McDonald To: pwg-announce@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [Pwg-Announce] Re: [ONE more vote] PWG Raster Formal Vote (17 March to 13 April 2012) X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1279959679==" 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: A49E7796D0.AD5BA X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1279959679== Content-Type: multipart/alternative; boundary=0016e6de14e1f23acd04bd40d093 --0016e6de14e1f23acd04bd40d093 Content-Type: text/plain; charset=ISO-8859-1 Hi, Please help out - we need ONE more vote to reach quorum on PWG Raster. Cheers, - Ira (PWG Secretary). On Sat, Mar 17, 2012 at 11:22 AM, Ira McDonald wrote: > Greetings: > > VOTES ARE CONFIDENTIAL! See voting instructions below. > > This email initiates the Formal Approval vote by the PWG membership on the > PWG Raster Format, which is located at: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20120314.pdf > > The complete list of PWG Last Call issues and resolutions is located at: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-ippraster10.txt > > > VOTING PERIOD: This Formal Vote will start today on Saturday 17 March > 2012 > and will end at 10pm (US Pacific Time) on Friday 13 April 2012. > > 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. > > > HOW TO VOTE: > > Send an email with *exactly* the following subject line format: > > PWG Raster Formal Vote-- name>- > > Example: > > PWG Raster Formal Vote-Acme-McGee-Yes > > > Rules: > > (1) Any "No" vote MUST state the reason for the "No" vote and MUST contain > a description of the *technical* changes required to turn the "No" voteinto a > "Yes" vote - otherwise the "No" vote will NOT be counted, per PWGProcess/3.0. > > (2) Any "No" vote MUST NOT contain *editorial* comments, per PWGProcess/3.0. > > (3) Any "Yes" vote MAY contain "editorial" comments, per PWG Process/3.0. > > (4) Any "Yes" vote MUST NOT contain any *technical* comments, per PWG > Process/3.0. > > (5) Any "Abstain" vote counts toward quorum, but not approval. > > > WHERE TO SEND YOUR VOTE: > > Please send your vote to *all* of the following email addresses (replacing > "dot" with '.' and "at" with '@'): > > msweet "at" apple "dot" com (Mike Sweet, PWG Chair, PWG Raster Editor) > > blueroofmusic "at" gmail "dot" com (Ira McDonald, PWG Secretary, IPP WG > Co-Chair) > > ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) > > > Please do NOT simply reply to this note on PWG-Announce or the > IPP WG list (to preserve the confidentiality of your vote). > > > Notes: > > (1) This Formal Vote is being conducted under the rules of the PWG > Process/3.0 > and the current PWG Policy on Intellectual Property and Confidentiality > agreement. > The 2012 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 2012 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 > > Cheers, > - Ira McDonald (PWG Secretary, IPP WG Co-Chair) > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - TCG Embedded Systems Hardcopy SG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music/High North Inc > http://sites.google.com/site/blueroofmusic > http://sites.google.com/site/highnorthinc > mailto:blueroofmusic@gmail.com > Winter 579 Park Place Saline, MI 48176 734-944-0094 > Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --0016e6de14e1f23acd04bd40d093 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Please help out - we need ONE more vote to reach quorum
on PW= G Raster.

Cheers,
- Ira (PWG Secretary).


On Sat, Mar 17, 2012 at 11:22 AM, Ira McDonald = <blueroofmu= sic@gmail.com> wrote:
Greetings:

VOTES ARE CONFIDENTIAL!=A0= See voting instructions below.

This email initiates the Forma= l Approval vote by the PWG membership on t= he
PWG Raster Format, which is located at:

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

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

=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-ippraster10.txt<= br>

VOTING PERIOD:=A0 This Formal Vote wil= l start today on Saturday 17 March 2012
and will end at 10pm (US Pacific Time) on Friday 13 April 2012.

Vali= d votes are: Yes, No, No (with Strong Objection), Abstain.


Repre= sentatives from PWG member companies are strongly encouraged t= o
exercise their right to vote.

PWG Privacy Policy:=A0 Your vote is confident= ial and will not be disclosed
by PWG officers or document e= ditors.


HOW TO VOTE:

Send an email with *exactly* the following subject line format:

= =A0 PWG Raster Formal Vote-<company name>-&= lt;voter's last name>-<Yes/No/Abstain>

Example:

=A0 PWG Raster Formal Vote-Ac= me-McGee-Yes


Rules:

(1) Any "No" vote MUST state the reason for the "No" vote and MUST= contain
a description of the *technical* changes required to turn the "No"= ; vote into a
"Yes" vote - otherwise the "No" vote= will NOT be counted, per PWG Process/3.0.

(2) A= ny "No" vote MUST NOT contain *editorial* comments, = per PWG Process/3.0.

(3) Any "Yes" vote MAY contain "editorial&q= uot; comments, per PWG Process/3.0.
=A0
(4) Any "Yes" vote MUST NOT contain any=A0 *t= echnical* comments, per PWG
Process/3.0.

(5) Any &qu= ot;Abstain" vote counts toward quorum, but not approval.<= br>

WHERE TO SEND YOUR VOTE:

Please send your vote to *all* of the following email addr= esses (replacing
"dot" with '.' and "at" wit= h '@'):

msweet "at" apple "dot" com (Mik= e Sweet, PWG Chair, PWG Raster Editor)

blueroofmusic "at" gmail "dot" com (Ira McDonald, PWG S= ecretary, IPP WG Co-Chair)

ptykodi "at" tykodi "dot&q= uot; com (Paul Tykodi, IPP WG Co-Chair)


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

Notes:

(1) This Formal Vote is be= ing conducted under the rules of the PWG=A0 Process/3.0
and the current PWG Policy on Intellectual Property and Confid= entiality agreement.
The 2012 PWG Membership Agreement calls out both of these docu= ments and
the links are provided below.

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

The PWG Definition of the Standards Development Process Ve= rsion 3.0 is
located at:

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

The PWG Policy on Intellectual Property and Confidentialit= y is located at:

=A0 http://www.pwg.org/c= hair/membership_docs/pwg-ip-policy.pdf

Cheers,
- Ira McDonald (PWG Secretary, IPP WG Co-Chair)


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



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --0016e6de14e1f23acd04bd40d093-- --===============1279959679== 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 --===============1279959679==-- From ipp-bounces@pwg.org Mon Apr 9 10:25:28 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F98321F87B4 for ; Mon, 9 Apr 2012 10:25:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJ9W9xyP8mhZ for ; Mon, 9 Apr 2012 10:25:27 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 51BBE21F87B2 for ; Mon, 9 Apr 2012 10:25:27 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9857F7967F; Mon, 9 Apr 2012 13:25:05 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by pwg.org (Postfix) with ESMTP id 1EAC679683 for ; Mon, 9 Apr 2012 13:24:48 -0400 (EDT) Received: from cm-omr5 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q39HOjl1011260 for ; Mon, 9 Apr 2012 13:24:46 -0400 Authentication-Results: cm-omr5 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:57699] helo=[192.168.1.114]) by cm-omr5 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id 6D/4E-14453-D5B138F4; Mon, 09 Apr 2012 13:24:45 -0400 From: Randy Turner Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Mon, 9 Apr 2012 10:24:45 -0700 Message-Id: To: ipp@pwg.org Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] proposed mods to IPP everywhere spec (per my action item) 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: 9857F7967F.A859E X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi Guys, Proposed mods for wd-ippeve10-20120201: 4.2.2 Geo-Location (LOC) Site administrators MUST (should this be a "SHOULD" ?) publish LOC records = (RFC 1876) to provide the physical location of a printer.=20 4.2.3 Service Information (TXT) Site administrators MUST publish ("SHOULD" ?)=85. This document is placing requirements on devices for future compliance with= an IPP everywhere standard -- however, DNS requirements are NOT requiremen= ts placed on a device, but rather administrative requirements for the site = DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. There's nothing a printer vendor can do to be "compliant" with 4.2.2 and 4.= 2.3 We may want a separate section of our documents that place requirements on = the "site" where devices are installed. Comments? Randy --=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 Apr 9 11:00:06 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B935421F87CA for ; Mon, 9 Apr 2012 11:00:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.165 X-Spam-Level: X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34xdymhH4e4Z for ; Mon, 9 Apr 2012 11:00:06 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 000DB21F87B4 for ; Mon, 9 Apr 2012 11:00:05 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 10C72796D5; Mon, 9 Apr 2012 13:59:47 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 0FA49796D5 for ; Mon, 9 Apr 2012 13:59:30 -0400 (EDT) MIME-version: 1.0 Content-type: text/plain; charset=windows-1252 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2800K834LW7H71@mail-out.apple.com> for ipp@pwg.org; Mon, 09 Apr 2012 10:59:30 -0700 (PDT) X-AuditID: 11807136-b7f056d0000026ba-a7-4f832382e28a Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id B2.B8.09914.283238F4; Mon, 09 Apr 2012 10:59:30 -0700 (PDT) Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) From: Michael Sweet In-reply-to: Date: Mon, 09 Apr 2012 10:59:30 -0700 Content-transfer-encoding: quoted-printable Message-id: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> References: To: Randy Turner X-Mailer: Apple Mail (2.1276) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLLMWRmVeSWpSXmKPExsUieFRTW7dJudnfoHOVlMWxfS9ZLI58i7XY s/YPmwOzx/KTX5g9tp78weYxb/F0pgDmKC6blNSczLLUIn27BK6MRVvbmAuuc1W8bL/G0sB4 naOLkZNDQsBEYvvsTcwQtpjEhXvr2boYuTiEBKYzSax/tY8NJCEs4COxpa+RBcTmFTCUePTm OlgDs4CexI7rv1hBbDYBNYnfk/rAbE4BV4mJp/6D2SwCKhIvln5lg6jnlzjY+wGqV1ti2cLX zBAzbST2bP4OViMk4CKxds1qRhBbREBHou3pORaI42QlLnb1MU1g5J+F5IxZSM6YhWTsAkbm VYyCRak5iZWGpnqJBQU5qXrJ+bmbGEGB2FBotoNxx1+5Q4wCHIxKPLydfM3+QqyJZcWVuYcY JTiYlUR4i541+QvxpiRWVqUW5ccXleakFh9ilOZgURLnTRcAqhZITyxJzU5NLUgtgskycXBK NTBqX5xWNTG95ZjGbWUWmXX5ujuZ9fxmn6v8J/u/1enRAsu/JjfruVYlTmOeXnjRvXP3NCau 2UmxeYaJJ6WMQ3MVYhPS5myxTEvy38h+RnvCka21SZMPZM5P/1zgeOYKQ33dHvtHq974CZgs Kt4tlLnxfd3tnEOlRz+2dL07/u64x8PESKk1L5uUWIozEg21mIuKEwH5b8SqQAIAAA== X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 10C72796D5.A9127 X-pwg-MailScanner-From: ipp-bounces@pwg.org Randy, Thanks for the text. Comments below. On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: >=20 > Hi Guys, >=20 > Proposed mods for wd-ippeve10-20120201: >=20 > 4.2.2 Geo-Location (LOC) >=20 > Site administrators MUST (should this be a "SHOULD" ?) publish LOC record= s (RFC 1876) to provide the physical location of a printer.=20 >=20 > 4.2.3 Service Information (TXT) > Site administrators MUST publish ("SHOULD" ?)=85. >=20 >=20 > This document is placing requirements on devices for future compliance wi= th an IPP everywhere standard -- however, DNS requirements are NOT requirem= ents placed on a device, but rather administrative requirements for the sit= e DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. Multicast DNS (part of Bonjour, and a perennial draft awaiting love from th= e IETF DNS WG) is not managed by site administrators and is part of IPP Eve= rywhere. Also, printers *can* register their own DNS records with traditional DNS in= frastructure using dynamic DNS updates (RFC 2136) and many already have sup= port for this... Anyways, I am happy to note that these are requirements for Multicast DNS a= nd recommendations for traditional DNS. ________________________________________________________________________ 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 Apr 9 11:05:38 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB70C21F87D5 for ; Mon, 9 Apr 2012 11:05:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCicx87EifyP for ; Mon, 9 Apr 2012 11:05:37 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3072C21F87D2 for ; Mon, 9 Apr 2012 11:05:37 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8D066796DC; Mon, 9 Apr 2012 14:05:21 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by pwg.org (Postfix) with ESMTP id 73BD0796D6 for ; Mon, 9 Apr 2012 14:05:05 -0400 (EDT) Received: from cm-omr6 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q39I54tr026393 for ; Mon, 9 Apr 2012 14:05:05 -0400 Authentication-Results: cm-omr6 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:58751] helo=[192.168.1.114]) by cm-omr6 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id DC/EA-22382-FC4238F4; Mon, 09 Apr 2012 14:05:03 -0400 Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Randy Turner In-Reply-To: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> Date: Mon, 9 Apr 2012 11:05:03 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> To: Michael Sweet X-Mailer: Apple Mail (2.1257) X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 8D066796DC.A8B69 X-pwg-MailScanner-From: ipp-bounces@pwg.org Hi Mike, You're right about multicast DNS not requiring site administration, but dyn= amic DNS is only designed to update A/AAAA records in a zone. I'm not awar= e of anyone using dynamic DNS to update TXT, SRV, or other resource records= . I haven't seen this done. Randy On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: > Randy, >=20 > Thanks for the text. Comments below. >=20 > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: >>=20 >> Hi Guys, >>=20 >> Proposed mods for wd-ippeve10-20120201: >>=20 >> 4.2.2 Geo-Location (LOC) >>=20 >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC recor= ds (RFC 1876) to provide the physical location of a printer.=20 >>=20 >> 4.2.3 Service Information (TXT) >> Site administrators MUST publish ("SHOULD" ?)=85. >>=20 >>=20 >> This document is placing requirements on devices for future compliance w= ith an IPP everywhere standard -- however, DNS requirements are NOT require= ments placed on a device, but rather administrative requirements for the si= te DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. >=20 > Multicast DNS (part of Bonjour, and a perennial draft awaiting love from = the IETF DNS WG) is not managed by site administrators and is part of IPP E= verywhere. >=20 > Also, printers *can* register their own DNS records with traditional DNS = infrastructure using dynamic DNS updates (RFC 2136) and many already have s= upport for this... >=20 > Anyways, I am happy to note that these are requirements for Multicast DNS= and recommendations for traditional DNS. >=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Apr 9 11:44:50 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528CF21F86D4 for ; Mon, 9 Apr 2012 11:44:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVKauSIgGEFv for ; Mon, 9 Apr 2012 11:44:49 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2089121F8622 for ; Mon, 9 Apr 2012 11:44:49 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 072D47969D; Mon, 9 Apr 2012 14:44:32 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by pwg.org (Postfix) with ESMTP id 5C2DE79613 for ; Mon, 9 Apr 2012 14:44:14 -0400 (EDT) Received: by wibhr14 with SMTP id hr14so2302882wib.11 for ; Mon, 09 Apr 2012 11:44:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KPWBOa9ItA0TLhOFvN1L9ayVuImwIRhhblkWOhUoj24=; b=BINtXXSkelZ2F0oYtrQFJ49mlCkIz01C85lueEhcvpNNfczn74nkjCqw1/mGLNg6r6 qZYqUg5IPhuAVanzDbIYsq4rwPU8YkBmUcpXYxyKFj/M6raRJWg9krJyPpCq5Tszlhlz NQ58BIR0Nuk7hBjdmknjK8AfOdRqXulxMt2HefecL5BCbMWcK25OKlqFkiyfz+EbGClP T4MfTpCDOtXRWaccP1IEcLW5M0iyXC0yf6HXZQzK6sl6MU3C7KyOvmqITZSdCGMeA/yE 930axmBAtCwimUzYZ6LJggdBFvheMqSMLElNd7gAP49pj5uf5s1/ucXApGhV8xkDibzj pj/g== MIME-Version: 1.0 Received: by 10.180.102.102 with SMTP id fn6mr213987wib.10.1333997053525; Mon, 09 Apr 2012 11:44:13 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Mon, 9 Apr 2012 11:44:13 -0700 (PDT) In-Reply-To: <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> Date: Mon, 9 Apr 2012 14:44:13 -0400 Message-ID: Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) From: Ira McDonald To: Randy Turner , 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="===============1490163904==" 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: 072D47969D.A9C14 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1490163904== Content-Type: multipart/alternative; boundary=f46d0444ef5581bce104bd43645a --f46d0444ef5581bce104bd43645a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Randy, Printers already commonly publish themselves in SLP (if servers are present) and LDAP/Active Directory automatically. Adding the IPP Everywhere MDNS requirement for DNS-SD publish of LOC and TXT records is a matter of parity in discovery protocols. Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Apr 9, 2012 at 2:05 PM, Randy Turner wro= te: > > Hi Mike, > > You're right about multicast DNS not requiring site administration, but > dynamic DNS is only designed to update A/AAAA records in a zone. I'm not > aware of anyone using dynamic DNS to update TXT, SRV, or other resource > records. I haven't seen this done. > > Randy > > On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: > > > Randy, > > > > Thanks for the text. Comments below. > > > > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: > >> > >> Hi Guys, > >> > >> Proposed mods for wd-ippeve10-20120201: > >> > >> 4.2.2 Geo-Location (LOC) > >> > >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC > records (RFC 1876) to provide the physical location of a printer. > >> > >> 4.2.3 Service Information (TXT) > >> Site administrators MUST publish ("SHOULD" ?)=85. > >> > >> > >> This document is placing requirements on devices for future compliance > with an IPP everywhere standard -- however, DNS requirements are NOT > requirements placed on a device, but rather administrative requirements f= or > the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this > document. > > > > Multicast DNS (part of Bonjour, and a perennial draft awaiting love from > the IETF DNS WG) is not managed by site administrators and is part of IPP > Everywhere. > > > > Also, printers *can* register their own DNS records with traditional DNS > infrastructure using dynamic DNS updates (RFC 2136) and many already have > support for this... > > > > Anyways, I am happy to note that these are requirements for Multicast > DNS and recommendations for traditional DNS. > > > > ________________________________________________________________________ > > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d0444ef5581bce104bd43645a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Randy,

Printers already commonly publish themselves in SLP (if se= rvers are
present) and LDAP/Active Directory automatically.

Addin= g the IPP Everywhere MDNS requirement for DNS-SD publish
of LOC and TXT = records is a matter of parity in discovery protocols.

Cheers,
- Ira

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



On Mon, Apr 9, 2012 at 2:05 PM, Randy Tu= rner <rtu= rner@amalfisystems.com> wrote:

Hi Mike,

You're right about multicast DNS not requiring site administration, but= dynamic DNS is only designed to update A/AAAA records in a zone. =A0I'= m not aware of anyone using dynamic DNS to update TXT, SRV, or other resour= ce records. =A0I haven't seen this done.

Randy

On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:

> Randy,
>
> Thanks for the text. =A0Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) p= ublish LOC records (RFC 1876) to provide the physical location of a printer= .
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)=85.
>>
>>
>> This document is placing requirements on devices for future compli= ance with an IPP everywhere standard -- however, DNS requirements are NOT r= equirements placed on a device, but rather administrative requirements for = the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this doc= ument.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere.
>
> Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS.
>
> ______________________________________________________________________= __
> 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
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. --f46d0444ef5581bce104bd43645a-- --===============1490163904== 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 --===============1490163904==-- From ipp-bounces@pwg.org Mon Apr 9 13:01:38 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6049D21F8697 for ; Mon, 9 Apr 2012 13:01:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SV2Swpncjbqs for ; Mon, 9 Apr 2012 13:01:37 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 18ACD21F8674 for ; Mon, 9 Apr 2012 13:01:37 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CB6DD796A1; Mon, 9 Apr 2012 16:01:16 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by pwg.org (Postfix) with ESMTP id C34A6795DE for ; Mon, 9 Apr 2012 16:00:59 -0400 (EDT) Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q39K0xK3003574 for ; Mon, 9 Apr 2012 16:00:59 -0400 Authentication-Results: cm-omr4 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:58918] helo=[192.168.1.114]) by cm-omr4 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id 39/53-12885-AFF338F4; Mon, 09 Apr 2012 16:00:59 -0400 From: Randy Turner Mime-Version: 1.0 (Apple Message framework v1257) Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) Date: Mon, 9 Apr 2012 13:00:59 -0700 In-Reply-To: To: ipp@pwg.org References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> Message-Id: <15D36243-48F9-42FD-9B78-E19510180B0D@amalfisystems.com> X-Mailer: Apple Mail (2.1257) 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="===============0219974358==" 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: CB6DD796A1.A909E X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0219974358== Content-Type: multipart/alternative; boundary="Apple-Mail=_733CC28C-D99D-43A3-A6A2-09FE9CC39AE1" --Apple-Mail=_733CC28C-D99D-43A3-A6A2-09FE9CC39AE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Yes, I understand that DNS-SD allows "self-publication" and I'm fine with t= hat. I guess it's the DNS server case that still (I believe) requires administra= tive assistance. R. On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote: > Hi Randy, >=20 > Printers already commonly publish themselves in SLP (if servers are > present) and LDAP/Active Directory automatically. >=20 > Adding the IPP Everywhere MDNS requirement for DNS-SD publish > of LOC and TXT records is a matter of parity in discovery protocols. >=20 > Cheers, > - Ira >=20 > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - TCG Embedded Systems Hardcopy SG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music/High North Inc > http://sites.google.com/site/blueroofmusic > http://sites.google.com/site/highnorthinc > mailto:blueroofmusic@gmail.com > Winter 579 Park Place Saline, MI 48176 734-944-0094 > Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Mon, Apr 9, 2012 at 2:05 PM, Randy Turner = wrote: >=20 > Hi Mike, >=20 > You're right about multicast DNS not requiring site administration, but d= ynamic DNS is only designed to update A/AAAA records in a zone. I'm not aw= are of anyone using dynamic DNS to update TXT, SRV, or other resource recor= ds. I haven't seen this done. >=20 > Randy >=20 > On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: >=20 > > Randy, > > > > Thanks for the text. Comments below. > > > > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: > >> > >> Hi Guys, > >> > >> Proposed mods for wd-ippeve10-20120201: > >> > >> 4.2.2 Geo-Location (LOC) > >> > >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC rec= ords (RFC 1876) to provide the physical location of a printer. > >> > >> 4.2.3 Service Information (TXT) > >> Site administrators MUST publish ("SHOULD" ?)=85. > >> > >> > >> This document is placing requirements on devices for future compliance= with an IPP everywhere standard -- however, DNS requirements are NOT requi= rements placed on a device, but rather administrative requirements for the = site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. > > > > Multicast DNS (part of Bonjour, and a perennial draft awaiting love fro= m the IETF DNS WG) is not managed by site administrators and is part of IPP= Everywhere. > > > > Also, printers *can* register their own DNS records with traditional DN= S infrastructure using dynamic DNS updates (RFC 2136) and many already have= support for this... > > > > Anyways, I am happy to note that these are requirements for Multicast D= NS and recommendations for traditional DNS. > > > > ________________________________________________________________________ > > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > > >=20 >=20 > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Apple-Mail=_733CC28C-D99D-43A3-A6A2-09FE9CC39AE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

Yes, I unde= rstand that DNS-SD allows "self-publication" and I'm fine with that.
I guess it's the DNS server case that still (I believe) requir= es administrative assistance.

R.


On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote:
Hi Randy= ,

Printers already commonly publish themselves in SLP (if servers ar= e
present) and LDAP/Active Directory automatically.

Adding the IP= P Everywhere MDNS requirement for DNS-SD publish
of LOC and TXT records = is a matter of parity in discovery protocols.

Cheers,
- Ira

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



On Mon, Apr 9, 2012 at 2:05 PM, Randy Tu= rner <rtu= rner@amalfisystems.com> wrote:

Hi Mike,

You're right about multicast DNS not requiring site administration, but dyn= amic DNS is only designed to update A/AAAA records in a zone.  I'm not= aware of anyone using dynamic DNS to update TXT, SRV, or other resource re= cords.  I haven't seen this done.

Randy

On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:

> Randy,
>
> Thanks for the text.  Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) publish LOC= records (RFC 1876) to provide the physical location of a printer.
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)=85.
>>
>>
>> This document is placing requirements on devices for future compli= ance with an IPP everywhere standard -- however, DNS requirements are NOT r= equirements placed on a device, but rather administrative requirements for = the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this documen= t.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere.
>
> Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS.
>
> ______________________________________________________________________= __
> 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
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. --Apple-Mail=_733CC28C-D99D-43A3-A6A2-09FE9CC39AE1-- --===============0219974358== 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 --===============0219974358==-- From ipp-bounces@pwg.org Mon Apr 9 15:21:40 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C633321F86CE for ; Mon, 9 Apr 2012 15:21:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.273 X-Spam-Level: X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcKiCQe1Rol6 for ; Mon, 9 Apr 2012 15:21:40 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 04CD221F86A0 for ; Mon, 9 Apr 2012 15:21:40 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 53057796D0; Mon, 9 Apr 2012 18:21:21 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 2503A796CC for ; Mon, 9 Apr 2012 18:21:04 -0400 (EDT) MIME-version: 1.0 Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2800GM9GOFZ1H2@mail-out.apple.com> for ipp@pwg.org; Mon, 09 Apr 2012 15:21:04 -0700 (PDT) X-AuditID: 11807112-b7fc86d000003fc1-30-4f8360cf213f 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 relay17.apple.com (Apple SCV relay) with SMTP id 81.DA.16321.0D0638F4; Mon, 09 Apr 2012 15:21:04 -0700 (PDT) From: Michael Sweet Date: Mon, 09 Apr 2012 15:21:03 -0700 To: "" Message-id: <3436C22B-B90E-4F93-96FD-ED43F1D9B655@apple.com> X-Mailer: Apple Mail (2.1276) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUieFRTW/dCQrO/wcLHzBbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyrh94zlTwRTpis4nog2MXRJdjJwcEgImEucf 3WOGsMUkLtxbz9bFyMUhJDCdSWLHscdMIAk2ATWJ35P6WEFsZoEEiaeXjrKA2CwCKhI3XzaD xYUFdCQOLj8KZosIKEr8nLadsYuRg4NXwEbiz7MQkDCvgKHEozfXoXbJSlzs6mOawMg9C8nU WUjKIOLaEssWvgayOYBsHYnJCxlRhSHsj+ePMC1gZFvFKFiUmpNYaWiul1hQkJOql5yfu4kR FFYNhUI7GO/v0jvEKMDBqMTDa8jT7C/EmlhWXJl7iFGCg1lJhHeaFVCINyWxsiq1KD++qDQn tfgQozQHi5I4b5YAUEogPbEkNTs1tSC1CCbLxMEp1cBY9+Tm6+svXPenbzpm7a13ZN59w+g2 yweLE85EP26NkX05O6xK5pLv85OJ7lVhGir37F5oic55mbH767PMQxcK2O/aumbor37kdfj/ lsmyG2X5DSb29H5TZn7Fqs84/4rsAYmTcrvedlhZtev/sU06bnrrt73Z51kX5z3OedgVspXD baGAA89SJZbijERDLeai4kQAu6ytEycCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Minutes posted from today's concall X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1084216552==" 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: 53057796D0.A70A5 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1084216552== Content-type: multipart/alternative; boundary="Boundary_(ID_u+tbSvWIJLhGoGiPX5X7CA)" --Boundary_(ID_u+tbSvWIJLhGoGiPX5X7CA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the minutes from today's conference call to: ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20120409.pdf Our next conference call will be Monday, April 16 at 3:00pm Eastern Time, shared with the Cloud Imaging WG. New action items: - Ira to check syntax for multi-valued strings and length limits in LDAP Printer schema - Ira to update charter to use Media Standardized Names for MSN2 title - Mike to update MSN2 title back to Media Standardized Names ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_u+tbSvWIJLhGoGiPX5X7CA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

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


Our next conference call will be Monday, = April 16 at 3:00pm Eastern Time, shared with the Cloud Imaging WG.

New action items:

- Ira to check = syntax for multi-valued strings and length limits in LDAP Printer schema
- Ira to update charter to use Media Standardized Names for MSN2 tit= le
= - Mike to update MSN2 title back to Media Standardized Names

___________________________= _____________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair<= /div>


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_u+tbSvWIJLhGoGiPX5X7CA)-- --===============1084216552== 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 --===============1084216552==-- From ipp-bounces@pwg.org Mon Apr 9 17:09:27 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DEAA21F8782 for ; Mon, 9 Apr 2012 17:09:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.338 X-Spam-Level: X-Spam-Status: No, score=-102.338 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ6vTRVy3h12 for ; Mon, 9 Apr 2012 17:09:26 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8D98621F875B for ; Mon, 9 Apr 2012 17:09:26 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 87B71796CA; Mon, 9 Apr 2012 20:09:07 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id CADFC796CA for ; Mon, 9 Apr 2012 20:08:48 -0400 (EDT) MIME-version: 1.0 Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2800GV3LPOZ1X2@mail-out.apple.com> for ipp@pwg.org; Mon, 09 Apr 2012 17:08:22 -0700 (PDT) X-AuditID: 11807134-b7fea6d000003dbe-c6-4f8379f67ea1 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 F3.23.15806.6F9738F4; Mon, 09 Apr 2012 17:08:22 -0700 (PDT) From: Michael Sweet Date: Mon, 09 Apr 2012 17:08:21 -0700 To: "" Message-id: <69953762-5138-4689-B855-37AC5E27BF20@apple.com> X-Mailer: Apple Mail (2.1276) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUieFRTW/dbZbO/wZpV3BbH9r1ksTjyLdaB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgymhcv4OloF21Yv++fSwNjHsUuxg5OSQETCTe HF7DDmGLSVy4t56ti5GLQ0hgOpPEp5W7WUESbAJqEr8n9YHZzAIJEmfWfQBrYBFQkeiYsB4s LizgK/HkdTMLiC0ioCjxc9p2RhCbV8BGYkr3aiYI21Di0ZvrzBDLZCUudvUxTWDknoVk7Cwk ZRBxeYntb+cA2RxAto7E5IWMEGFtiWULXzPD2B/PH2FawMi2ilGwKDUnsdLQRC+xoCAnVS85 P3cTIyi0GgpNdjAe/Ml/iFGAg1GJh9eQp9lfiDWxrLgy9xCjBAezkgjvNCugEG9KYmVValF+ fFFpTmrxIUZpDhYlcd40AaCUQHpiSWp2ampBahFMlomDU6qBUUEza0FkVf4r28kCdY6+hoeS F91vsTYTPXVI6P1Ky9NbPz4q4WTac36Ne+eeWDHWzK09de4GsyfNmjinlSHowobZ/req9xvz 7q5fk+giz5e3OLfW8tOUrBShDs5P37XuzKjUt7lRdT3mofg2BpHVSgnWUUK/Eg/OW6h1wG6C ih2T+4TH2jkuSizFGYmGWsxFxYkAPA9CuSkCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Stable draft of IPP Job and Printer Extensions - Set 3 (JPS3) posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1049505380==" 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: 87B71796CA.A874C X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1049505380== Content-type: multipart/alternative; boundary="Boundary_(ID_yJHkUtg0tzPzQQqTnhsxUg)" --Boundary_(ID_yJHkUtg0tzPzQQqTnhsxUg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted a stable draft of JPS3 to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409-rev.pdf My next email will announce the WG Last Call for this specification. ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_yJHkUtg0tzPzQQqTnhsxUg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted a stable draft of JPS3 to:


M= y next email will announce the WG Last Call for this specification.

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_yJHkUtg0tzPzQQqTnhsxUg)-- --===============1049505380== 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 --===============1049505380==-- From ipp-bounces@pwg.org Mon Apr 9 17:14:25 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AEE721F879B for ; Mon, 9 Apr 2012 17:14:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.381 X-Spam-Level: X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghEhv1uq-oel for ; Mon, 9 Apr 2012 17:14:24 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D74621F8768 for ; Mon, 9 Apr 2012 17:14:20 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8BC23796DF; Mon, 9 Apr 2012 20:14:01 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 24667796A1 for ; Mon, 9 Apr 2012 20:13:46 -0400 (EDT) MIME-version: 1.0 Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2800BJJLSSU703@mail-out.apple.com> for ipp@pwg.org; Mon, 09 Apr 2012 17:13:45 -0700 (PDT) X-AuditID: 11807112-b7fc86d000003fc1-5a-4f837b392068 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 relay17.apple.com (Apple SCV relay) with SMTP id 4A.18.16321.93B738F4; Mon, 09 Apr 2012 17:13:45 -0700 (PDT) From: Michael Sweet Date: Mon, 09 Apr 2012 17:13:45 -0700 To: "" Message-id: X-Mailer: Apple Mail (2.1276) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUieFRTW9eyutnfoHGtosWxfS9ZLI58i3Vg 8th68gebx7zF05kCmKK4bFJSczLLUov07RK4Mn4c1Cn4rVWx9sMC1gbGWWpdjJwcEgImEqv/ 72SDsMUkLtxbD2RzcQgJTGeSuLb3BBNIgk1ATeL3pD5WEJtZIEHizOODjCA2i4CKxNmda1lA bGGBNImmbTfBakQEFCV+TtsOVMPBwStgI3HhVDVImFfAUOLRm+vMELtkJS529TFNYOSehWTq LCRlEHFtiWULXwPZHEC2jsTkhYyowhD2x/NHmBYwsq1iFCxKzUmsNDTXSywoyEnVS87P3cQI CquGQqEdjPd36R1iFOBgVOLhNeRp9hdiTSwrrsw9xCjBwawkwjvNCijEm5JYWZValB9fVJqT WnyIUZqDRUmcN0sAKCWQnliSmp2aWpBaBJNl4uCUamAs8Ylb/PhTq8qxAB7DjdeCr/ZZsl6+ 3sUyi1t1eQeL4D4v9csXpr9mPJK7Tpkjo+fkrZorhx6lfbg1+VzdN1dJM7WrTkl6/hMeuybG LF+4/eKUbInJ66dG6mRwptvEXVy785693tUfk1/mpOpXvu3mb/B3EFkWNvvlolU+XSfrONkM 0m9ce1WixFKckWioxVxUnAgAtzmUQycCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1663286459==" 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: 8BC23796DF.A8257 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1663286459== Content-type: multipart/alternative; boundary="Boundary_(ID_WL5LhqNidjuNw52KnFKzEQ)" --Boundary_(ID_WL5LhqNidjuNw52KnFKzEQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, This message initiates the IPP Working Group last call of the IPP Job and Printer Extensions - Set 3 (JPS3) specification that has been in extended development since last year. The latest stable draft can be found here: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409-rev.pdf Please send all feedback to the IPP mailing list (reply-all works fine for this) and it will be collected and processed as quickly as possible. Our intent is to move JPS3 to PWG Last Call to span the April 2012 F2F. Thank you! ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_WL5LhqNidjuNw52KnFKzEQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

Th= is message initiates the IPP Working Group last call of the IPP Job and Pri= nter Extensions - Set 3 (JPS3) specification that has been in extended deve= lopment since last year. The latest stable draft can be found here:




<= /div>
________________________= ________________________________________________
Michael Sweet, S= enior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by
MailScanner, and is
believed to be clean. --Boundary_(ID_WL5LhqNidjuNw52KnFKzEQ)-- --===============1663286459== 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 --===============1663286459==-- From ipp-bounces@pwg.org Tue Apr 10 08:31:09 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B93A11E80F3 for ; Tue, 10 Apr 2012 08:31:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.473 X-Spam-Level: X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ncZ9cfuTcja7 for ; Tue, 10 Apr 2012 08:31:08 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B3B4211E80DF for ; Tue, 10 Apr 2012 08:31:08 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E8B9B796F6; Tue, 10 Apr 2012 11:30:51 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by pwg.org (Postfix) with ESMTP id 923C3796F3 for ; Tue, 10 Apr 2012 11:30:36 -0400 (EDT) Received: by wgbdq13 with SMTP id dq13so4204165wgb.11 for ; Tue, 10 Apr 2012 08:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=X5bRfe7H+xZoMlW8GH675s9N8D7QD1Z4sfR45wxJmxI=; b=XH4B8Y8Vskx4vdMsISjEywo50vs5J/xGzmA1xPHveg7gA951H8FI9FQRDqWDqZk+pS /32xVSjTFPu351ZUKqqe8Ez+DIkETfFq1JQVJzofOyMJyBQwe6Yell3q/amN/CP/trNH y4WOfBJ/Ws/xbfqJAEpmw7MorKTehpJbppgU8mIKm0VDunIFP92jFCy4rK+3j9k6YpMF IxTwSN5Rnn4wwvhyIS1WgA17ynrHWUtYY35h4IcGry/n4IS1ZyWJe9nSQl7mEn+3U2pu xQhyljAinZY2S6CcPfw1sRLdHaga5I4u++JqlpD14wxdgMOhH9DWmqVWVJxs/5uCXcG9 i+qg== MIME-Version: 1.0 Received: by 10.180.24.35 with SMTP id r3mr8039649wif.7.1334071835550; Tue, 10 Apr 2012 08:30:35 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Tue, 10 Apr 2012 08:30:35 -0700 (PDT) Date: Tue, 10 Apr 2012 11:30:35 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Charter - updated draft (10 April 2012) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1764179611==" 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: E8B9B796F6.A8D40 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1764179611== Content-Type: multipart/alternative; boundary=f46d043bdf20dce58604bd54cdce --f46d043bdf20dce58604bd54cdce Content-Type: text/plain; charset=ISO-8859-1 Hi, [For review at this week's IPP WG meeting and this week's PWG Steering Committee meeting] Per the discussion at the IPP WG teleconference on 9 April 2012, I've just posted a Stable draft of an updated IPP Charter for the renamed IPP Everywhere and IPP Multifunction projects: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410.pdf - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410-rev.pdf - redlines copy w/ line numbers Changed name of MSN2 to "Media Standardized Names" (without the original erroneous "Standard for ..." prefix in title of MSN1). Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d043bdf20dce58604bd54cdce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

[For review at this week's IPP WG meeting and t= his week's PWG Steering
Committee meeting]


Per the discu= ssion at the IPP WG teleconference on 9 April 2012, I've just posted a Stable draft of an updated IPP Charter for the = renamed IPP Everywhere and IPP
Multifunction = projects:

=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippev= erywhere-charter-20120410.pdf
=A0 - clean copy w/ line numbers
=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp= everywhere-charter-20120410-rev.pdf
=A0 - redlines copy w/ line numbers

Changed name of MSN2 to "Me= dia Standardized Names" (without the original
erroneous "Stand= ard for ..." prefix in title of MSN1).

Comments?

Cheers,=
- Ira


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --f46d043bdf20dce58604bd54cdce-- --===============1764179611== 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 --===============1764179611==-- From ipp-bounces@pwg.org Tue Apr 10 09:47:08 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC7011E8118 for ; Tue, 10 Apr 2012 09:47:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyD2QWwoYak6 for ; Tue, 10 Apr 2012 09:47:07 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0372611E80F3 for ; Tue, 10 Apr 2012 09:47:04 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 43DB7796C7; Tue, 10 Apr 2012 12:46:44 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id D793A7968F for ; Tue, 10 Apr 2012 12:46:28 -0400 (EDT) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M29005T0VWK6KW2@mail-out.apple.com> for ipp@pwg.org; Tue, 10 Apr 2012 09:46:28 -0700 (PDT) X-AuditID: 11807130-b7f5e6d000000682-99-4f8463e324a1 Received: from [17.151.80.86] (Unknown_Domain [17.151.80.86]) (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 01.51.01666.3E3648F4; Tue, 10 Apr 2012 09:46:28 -0700 (PDT) Subject: Re: [IPP] IPP Charter - updated draft (10 April 2012) From: Michael Sweet In-reply-to: Date: Tue, 10 Apr 2012 09:46:27 -0700 Message-id: References: To: Ira McDonald X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUiOD0gTPdJcou/QdtTRovXr5ayWxzb95LF 4si3WAdmj60nf7B57Jx1l91j3uLpTAHMUVw2Kak5mWWpRfp2CVwZV3ZGFPy2q3h2awVjA+ND sy5GTg4JAROJ7gfd7BC2mMSFe+vZuhi5OIQEJjNJdM9+zAKSEBawk9h+9wKYzStgKDHzVTsr iM0skCAx/+YJZhCbTUBN4vekPrA4p0CgxK9VWxlBbBYBVYmPDfuZIOr5JQ72fgCq5wCaYyOx c7UMSFhIIEDi79KvjCBhEQEtiSXPFSHOkZW4fXA/0wRGvllIFs9CshjC1pZYtvA1lK0n8bLp HTumuK7ExXWTGBcwsq1iFCxKzUmsNDTUSywoyEnVS87P3cQICtmGQoMdjGt/8h9iFOBgVOLh 9fRt8RdiTSwrrsw9xCjBwawkwvsoFCjEm5JYWZValB9fVJqTWnyIUZqDRUmcN1mg2V9IID2x JDU7NbUgtQgmy8TBKdXAaLfMKemI1YyPCh/NJvio1txJeMYvoNEjk/LAJFE6++cePSvZAM2D kZFq0uzsuuavcyfNsYk3Ui66pNE604rpY1Xg/P/TctfVmzbPN97KMMH0lYSWSS7/+loV8bW3 5I9JbeELU665lLyJ6Yz0H9eJUUfLqrXPBeUpXtjmflFUql76DsMi12VKLMUZiYZazEXFiQBx gy8eVQIAAA== 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="===============1565885623==" 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: 43DB7796C7.A970F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1565885623== Content-type: multipart/alternative; boundary="Boundary_(ID_noQTX+IIS889ZAWOb84S3w)" --Boundary_(ID_noQTX+IIS889ZAWOb84S3w) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Ira, One more title fix: "PWG Raster Format" (the charter is missing the "Format" in the list of documents and in the milestones) Also, just to confirm we are including the version number in the title for MSN2? Ultimately this will end up being 5101.1-2012, so I just want to be sure. (and I notice you didn't include the version number in the MSN milestones) On Apr 10, 2012, at 8:30 AM, Ira McDonald wrote: > Hi, > > [For review at this week's IPP WG meeting and this week's PWG Steering > Committee meeting] > > > Per the discussion at the IPP WG teleconference on 9 April 2012, I've just posted > a Stable draft of an updated IPP Charter for the renamed IPP Everywhere and IPP > Multifunction projects: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410.pdf > - clean copy w/ line numbers > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410-rev.pdf > - redlines copy w/ line numbers > > Changed name of MSN2 to "Media Standardized Names" (without the original > erroneous "Standard for ..." prefix in title of MSN1). > > Comments? > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - TCG Embedded Systems Hardcopy SG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music/High North Inc > http://sites.google.com/site/blueroofmusic > http://sites.google.com/site/highnorthinc > mailto:blueroofmusic@gmail.com > Winter 579 Park Place Saline, MI 48176 734-944-0094 > Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_noQTX+IIS889ZAWOb84S3w) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Ira,

On= e more title fix: "PWG Raster Format" (the charter is missing the "Format" = in the list of documents and in the milestones)

Al= so, just to confirm we are including the version number in the title for MS= N2? Ultimately this will end up being 5101.1-2012, so I just want to be sur= e. (and I notice you didn't include the version number in the MSN milestone= s)


On Apr 10, 2012, at 8:= 30 AM, Ira McDonald wrote:

Hi,

[For review at this week's IPP WG m= eeting and this week's PWG Steering
Committee meeting]

Per the discussion at the IPP WG teleconference on 9 April 2012, I've jus= t posted
a Stable draft of an updated IPP Charter for the = renamed IPP Everywhere and IPP
Multifunction = projects:

  ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ip= peverywhere-charter-20120410.pdf
  - clean copy w/ line numbers=

  ftp://ftp.pwg.org/pub/pwg/ipp/= wd/wd-ippeverywhere-charter-20120410-rev.pdf
  - redlines copy w/ line numbers

Changed name of MSN2 to "Medi= a Standardized Names" (without the original
erroneous "Standard for ..."= prefix in title of MSN1).

Comments?

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)=
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Prin= ter Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trus= ted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP &a= mp; Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthincmailto:bluer= oofmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094=
Summer  PO Box 221  Grand Marais, MI 49839  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/l= istinfo/ipp

_______________________________________________________= _________________
Michael Sweet, Senior Printing System Engineer,= PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_noQTX+IIS889ZAWOb84S3w)-- --===============1565885623== 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 --===============1565885623==-- From ipp-bounces@pwg.org Tue Apr 10 09:59:29 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C4B11E8128 for ; Tue, 10 Apr 2012 09:59:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxryeWBxXMO1 for ; Tue, 10 Apr 2012 09:59:28 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 457A211E80E8 for ; Tue, 10 Apr 2012 09:59:28 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 255BC795FF; Tue, 10 Apr 2012 12:59:08 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by pwg.org (Postfix) with ESMTP id BA1FD795FF for ; Tue, 10 Apr 2012 12:58:51 -0400 (EDT) Received: by wibhr17 with SMTP id hr17so3235134wib.5 for ; Tue, 10 Apr 2012 09:58:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XX+ykrL0TlOqF1G1ShZ5udzsI2V9TaDf9ysWMMQ+NxE=; b=C6Oo/lhoD++FhIRaCVXi/Rrj7Qcmri+Zd/GnxR8/vLY8/Qsb2GyTh63mS4WMT67Twl yzZ9yx8E5vil7jJa1CLwLSEAcVNABpTY5Df9fx7tYKkLcCDKp1jyrIpI2Rh1jkPsq982 F2QpFBGFE6fvT67mxbD1NoDWQNWKkMFTV7n0zCiVOv8H9OCU9aLOZSVKrapBsTYJtkU7 9SxrNDtk2O5Wbd3kfNBUCIMOPMxhQug43iC8gEgN+rvDSsC4R7DgvNhG/43PCTEQeX8L lwNGA1ufyGVrgmkRypIOoaNW9FjU+NIIpl99EtQqiWcyIfBAD9BrjLHE/QGQhadf1CoW iqKw== MIME-Version: 1.0 Received: by 10.180.103.134 with SMTP id fw6mr10252825wib.0.1334077130784; Tue, 10 Apr 2012 09:58:50 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Tue, 10 Apr 2012 09:58:50 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Apr 2012 12:58:50 -0400 Message-ID: Subject: Re: [IPP] IPP Charter - updated draft (10 April 2012) 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="===============2032902283==" 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: 255BC795FF.A95C6 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2032902283== Content-Type: multipart/alternative; boundary=f46d044304427bbf5c04bd56091c --f46d044304427bbf5c04bd56091c Content-Type: text/plain; charset=ISO-8859-1 Hi, Replies inline below - let's get out ducks in a row and then I'll turn the charter once more later today (overwriting the flawed one). Cheers, - Ira On Tue, Apr 10, 2012 at 12:46 PM, Michael Sweet wrote: > Ira, > > One more title fix: "PWG Raster Format" (the charter is missing the > "Format" in the list of documents and in the milestones) > > - ira - OK, I'll fix it. > Also, just to confirm we are including the version number in the title for > MSN2? Ultimately this will end up being 5101.1-2012, so I just want to be > sure. (and I notice you didn't include the version number in the MSN > milestones) > > - ira - I think my version number there was an artifact of earlier thought processes - I suggest that it NOT be a part of the title for better stability in references from CIP4 JDF, DMTF CIM, and other external standards. > > On Apr 10, 2012, at 8:30 AM, Ira McDonald wrote: > > Hi, > > [For review at this week's IPP WG meeting and this week's PWG Steering > Committee meeting] > > > Per the discussion at the IPP WG teleconference on 9 April 2012, I've just > posted > a Stable draft of an updated IPP Charter for the renamed IPP Everywhere > and IPP > Multifunction projects: > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410.pdf > - clean copy w/ line numbers > > > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120410-rev.pdf > - redlines copy w/ line numbers > > Changed name of MSN2 to "Media Standardized Names" (without the original > erroneous "Standard for ..." prefix in title of MSN1). > > Comments? > > Cheers, > - Ira > > > Ira McDonald (Musician / Software Architect) > Chair - Linux Foundation Open Printing WG > Secretary - IEEE-ISTO Printer Working Group > Co-Chair - IEEE-ISTO PWG IPP WG > Co-Chair - TCG Trusted Mobility Solutions WG > Chair - TCG Embedded Systems Hardcopy SG > IETF Designated Expert - IPP & Printer MIB > Blue Roof Music/High North Inc > http://sites.google.com/site/blueroofmusic > http://sites.google.com/site/highnorthinc > mailto:blueroofmusic@gmail.com > Winter 579 Park Place Saline, MI 48176 734-944-0094 > Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --f46d044304427bbf5c04bd56091c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Replies inline below - let's get out ducks in a row and then= I'll
turn the charter once more later today (overwriting the flawed=
one).

Cheers,
- Ira

On Tue, Apr 10, 2012 at 12:46 PM, Michael Sw= eet <msweet@apple.= com> wrote:
Ira,

One more title = fix: "PWG Raster Format" (the charter is missing the "Format= " in the list of documents and in the milestones)

- ira - OK, I&= #39;ll fix it.
=A0
Also, just to confirm w= e are including the version number in the title for MSN2? Ultimately this w= ill end up being 5101.1-2012, so I just want to be sure. (and I notice you = didn't include the version number in the MSN milestones)

- ira - I think my version number there was an artifact of earlier thought=
processes - I suggest that it NOT be a part of the title for better sta= bility
in references from CIP4 JDF, DMTF CIM,= and other external standards.

On Apr 10, 2012, at 8:30 AM, Ira McDonald wrote:
Hi,
[For review at this week's IPP WG meeting and this week= 9;s PWG Steering
Committee meeting]


Per the discussion at th= e IPP WG teleconference on 9 April 2012, I've just posted
a Stable draft of an updated IPP Charter for the = renamed IPP Everywhere and IPP
Multifunction = projects:

=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippev= erywhere-charter-20120410.pdf
=A0 - clean copy w/ line numbers
=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp= everywhere-charter-20120410-rev.pdf
=A0 - redlines copy w/ line numbers

Changed name of MSN2 to "Me= dia Standardized Names" (without the original
erroneous "Stand= ard for ..." prefix in title of MSN1).

Comments?

Cheers,=
- Ira


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. _______________________________________________
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. --f46d044304427bbf5c04bd56091c-- --===============2032902283== 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 --===============2032902283==-- From geral@o-sitio.com Tue Apr 10 12:21:38 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F8621F8471 for ; Tue, 10 Apr 2012 12:21:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oyfnNEff2+Gr for ; Tue, 10 Apr 2012 12:21:36 -0700 (PDT) Received: from iberweb3b.ibername.com (iberweb-3b-1.ibername.com [188.93.230.16]) by ietfa.amsl.com (Postfix) with ESMTP id A118A21F843A for ; Tue, 10 Apr 2012 12:21:30 -0700 (PDT) Received: from bl14-96-250.dsl.telepac.pt ([85.247.96.250] helo=fos-5mkgugpcpfe) by iberweb3b.ibername.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1SHeRh-00022g-1c; Tue, 10 Apr 2012 18:01:33 +0100 Message-ID: <781494.140625-sendEmail@fos-5mkgugpcpfe> From: "geral@o-sitio.com" Reply-To: "comercial@francisco-oliveira.com" To: "comercial@francisco-oliveira.com" Subject: Fazemos Sites na Internet - 6 euros / mes - N/Ref: 412764 Date: Tue, 10 Apr 2012 17:01:25 +0000 X-Mailer: sendEmail-1.56 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-397460.9375" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - iberweb3b.ibername.com X-AntiAbuse: Original Domain - lists.ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - o-sitio.com X-Source: X-Source-Args: X-Source-Dir: This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program. ------MIME delimiter for sendEmail-397460.9375 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit EasyNet4You - Construo e Manuteno de Sites na Internet Website: www.easynet4you.com E-Mail: easynet4you@gmail.com Rua Filipe Folque, N 10 G Apartado 12058 1061- 001 Lisboa Assunto: Construo e Manuteno de Sites na Internet ( 6 euros / ms ). Podem ter o Site da vossa Empresa na Internet em 5 dias uteis por 6 euros / ms (este valor inclui a Construo do Site, Alojamento, Dominio, E-Mails, e Manuteno), se no entanto no tiverem neste momento verba disponivel e se mesmo assim gostassem de ter um Site, ns tambm disponibilizamos uma opo de Sites Gratuitos, em que podem ter um Site mais elementar mas igualmente eficaz, com Design Atrativo, completamente gratuito, totalmente configurvel com vrios Designs e possibilidade de alterar contedos, de imediato e em menos de 15 minutos, basta fazerem o registo no nosso Site ! fundamental para qualquer Actividade assegurar a sua presena com um Site na Internet, pois porporciona: - Melhoria da Imagem Corporativa - Melhoria do Servio a Clientes - Melhoria da Comunicao - Expanso - Novas oportunidades de negcio - Transaces On-Line - Reduo de Custos - Informao sempre disponivel, 24 horas / 7 dias da semana Estas so apenas algumas das vantagens de estar na Internet. So muitos os benefcios que podem ser obtidos utilizando a tecnologia certa e a grande rede da Internet. Temos experincia em criar Sites para vrias reas de negcio, e em trabalhos, desde Lojas Virtuais e Sites altamente dinmicos, at trabalhos de simples pginas, estticas, de presena na Internet. Apostamos fortemente em solues de qualidade feitas medida, personalizveis ao gosto do cliente, baixo custo, tempos mnimos de desenvolvimento, relao fcil e flexivel sem burocracias e on-line, assistncia 24/7, e servidores dedicados que garantem alta disponibilidade, e grande velocidade de acesso. Se estiver interessado em saber mais informaes sobre os nossos servios poder consultar o nosso Site www.easynet4you.com, ou entrar em contacto connosco para o e-mail easynet4you@gmail.com, que teremos todo o gosto em esclarecer e aprsesentar as nossas melhores solues para o vosso caso. Sem outro assunto de momento, e agradeendo antecipadamente a ateno que V. Exas iro prestar ao assunto, subscrevo-mos-nos. Com os melhores cumprimentos, e considerao, EasyNet4You Construo e Manuteno de Sites na Internet www.easynet4you.com easynet4you@gmail.com Rua Filipe Folque, N 10 G Apartado 12058 1061- 001 Lisboa Nota: Se no quiser receber mais correspondncia nossa, poder retirar o seu endereo desta lista de distribuio no seguinte endereo http://www.francisco-oliveira.com/retirar.htm Note: If don't want to receive more e-mails from us, you will be able to remove your address from this distribution list in the following address http://www.francisco-oliveira.com/retirar.htm ------MIME delimiter for sendEmail-397460.9375-- From ipp-bounces@pwg.org Tue Apr 10 14:31:03 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F16421F85D4 for ; Tue, 10 Apr 2012 14:31:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jOmoOvjCwV7L for ; Tue, 10 Apr 2012 14:31:02 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id D110B21F85D0 for ; Tue, 10 Apr 2012 14:31:01 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 963AA795E8; Tue, 10 Apr 2012 17:30:43 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by pwg.org (Postfix) with ESMTP id E397A796F7 for ; Tue, 10 Apr 2012 17:30:23 -0400 (EDT) Received: from cm-omr9 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3ALUJ5g021008 for ; Tue, 10 Apr 2012 17:30:19 -0400 Authentication-Results: cm-omr9 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:49508] helo=[192.168.1.114]) by cm-omr9 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id 76/8A-19853-A66A48F4; Tue, 10 Apr 2012 17:30:19 -0400 From: Randy Turner Mime-Version: 1.0 (Apple Message framework v1257) Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) Date: Tue, 10 Apr 2012 14:30:22 -0700 In-Reply-To: <15D36243-48F9-42FD-9B78-E19510180B0D@amalfisystems.com> To: ipp@pwg.org References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> <15D36243-48F9-42FD-9B78-E19510180B0D@amalfisystems.com> Message-Id: <9D4F451D-83DE-40EE-B574-EC2395308403@amalfisystems.com> X-Mailer: Apple Mail (2.1257) 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="===============0356708155==" 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: 963AA795E8.A9A75 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0356708155== Content-Type: multipart/alternative; boundary="Apple-Mail=_93269102-C73A-4A14-B305-8B859DFD09E6" --Apple-Mail=_93269102-C73A-4A14-B305-8B859DFD09E6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi Guys, In theory, RFC 2136 would allow a client to update any RRset in a zone in D= NS -- however, no one implements just RFC 2136 by itself, since the securit= y implications would be enormous. RFC 2136 would require a vendor to allocate a fair amount of development re= sources for implementation and testing. In addition, early recommendations strongly suggested any implementation of= RFC 2136 to also include an implementation of RFC 2137, which would requir= e a bit more development and testing time. However, RFC 2137 has been obsoleted through the introduction of DNSSEC mec= hanisms (RFC 4033, 4034, and 4035), which require a bit more development. = It would also require the site to move their DNS servers to use DNSSEC. Even with these pre-conditions, I'm still trying to determine if DNS server= policies would allow arbitrary RRset updates (other than A/AAAA RR types) Of course, MDNS (DNS-SD, ZeroConf, etc.) only requires mechanisms on the cl= ient (as everyone probably knows), and many imaging devices already support= this technology, so I don't see any problem (at least for now) with making= a "MUST" for MDNS records that assist IPP everywhere. For server-based DNS, I would recommend against making this a "MUST", becau= se the implications on vendors and sites may be too high -- I recommend mak= ing this requirement a "SHOULD" or "MAY". I'll follow up some suggested wording for section 4.2.2, taking into accoun= t the above information. Randy On Apr 9, 2012, at 1:00 PM, Randy Turner wrote: >=20 > Yes, I understand that DNS-SD allows "self-publication" and I'm fine with= that. >=20 > I guess it's the DNS server case that still (I believe) requires administ= rative assistance. >=20 > R. >=20 >=20 > On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote: >=20 >> Hi Randy, >>=20 >> Printers already commonly publish themselves in SLP (if servers are >> present) and LDAP/Active Directory automatically. >>=20 >> Adding the IPP Everywhere MDNS requirement for DNS-SD publish >> of LOC and TXT records is a matter of parity in discovery protocols. >>=20 >> Cheers, >> - Ira >>=20 >> Ira McDonald (Musician / Software Architect) >> Chair - Linux Foundation Open Printing WG >> Secretary - IEEE-ISTO Printer Working Group >> Co-Chair - IEEE-ISTO PWG IPP WG >> Co-Chair - TCG Trusted Mobility Solutions WG >> Chair - TCG Embedded Systems Hardcopy SG >> IETF Designated Expert - IPP & Printer MIB >> Blue Roof Music/High North Inc >> http://sites.google.com/site/blueroofmusic >> http://sites.google.com/site/highnorthinc >> mailto:blueroofmusic@gmail.com >> Winter 579 Park Place Saline, MI 48176 734-944-0094 >> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 >>=20 >>=20 >>=20 >> On Mon, Apr 9, 2012 at 2:05 PM, Randy Turner = wrote: >>=20 >> Hi Mike, >>=20 >> You're right about multicast DNS not requiring site administration, but = dynamic DNS is only designed to update A/AAAA records in a zone. I'm not a= ware of anyone using dynamic DNS to update TXT, SRV, or other resource reco= rds. I haven't seen this done. >>=20 >> Randy >>=20 >> On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: >>=20 >> > Randy, >> > >> > Thanks for the text. Comments below. >> > >> > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: >> >> >> >> Hi Guys, >> >> >> >> Proposed mods for wd-ippeve10-20120201: >> >> >> >> 4.2.2 Geo-Location (LOC) >> >> >> >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC re= cords (RFC 1876) to provide the physical location of a printer. >> >> >> >> 4.2.3 Service Information (TXT) >> >> Site administrators MUST publish ("SHOULD" ?)=85. >> >> >> >> >> >> This document is placing requirements on devices for future complianc= e with an IPP everywhere standard -- however, DNS requirements are NOT requ= irements placed on a device, but rather administrative requirements for the= site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. >> > >> > Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere. >> > >> > Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this... >> > >> > Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS. >> > >> > ______________________________________________________________________= __ >> > Michael Sweet, Senior Printing System Engineer, PWG Chair >> > >> > >>=20 >>=20 >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >>=20 >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >>=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 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Apple-Mail=_93269102-C73A-4A14-B305-8B859DFD09E6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

Hi Guys,
In theory, RFC 2136 would allow a client to update any RRs= et in a zone in DNS -- however, no one implements just RFC 2136 by itself, = since the security implications would be enormous.

RFC 2136 would require a vendor to allocate a fair amount of development r= esources for implementation and testing.

In additi= on, early recommendations strongly suggested any implementation of RFC 2136= to also include an implementation of RFC 2137, which would require a bit m= ore development and testing time.

However, RFC 213= 7 has been obsoleted through the introduction of DNSSEC mechanisms (RFC 403= 3, 4034, and 4035), which require a bit more development.  It would al= so require the site to move their DNS servers to use DNSSEC.

=
Even with these pre-conditions, I'm still trying to determine if= DNS server policies would allow arbitrary RRset updates (other than A/AAAA= RR types)

Of course, MDNS (DNS-SD, ZeroConf, etc.= ) only requires mechanisms on the client (as everyone probably knows), and = many imaging devices already support this technology, so I don't see any pr= oblem (at least for now) with making a "MUST" for MDNS records that assist = IPP everywhere.

For server-based DNS, I would reco= mmend against making this a "MUST", because the implications on vendors and= sites may be too high -- I recommend making this requirement a "SHOULD" or= "MAY".

I'll follow up some suggested wording for = section 4.2.2, taking into account the above information.

Randy


On Apr 9, 2= 012, at 1:00 PM, Randy Turner wrote:


Yes, I understand that DNS-SD allows "self-publication" and I'm fine with= that.

I guess it's the DNS server case that still (I be= lieve) requires administrative assistance.

R.


On Apr 9, 2012, at 11:44 AM, Ira McDonal= d wrote:

Hi Randy,

Printers already commonly publish themselves in SLP (= if servers are
present) and LDAP/Active Directory automatically.

= Adding the IPP Everywhere MDNS requirement for DNS-SD publish
of LOC and= TXT records is a matter of parity in discovery protocols.

Cheers,
- Ira

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



On Mon, Apr 9, 2012 at 2:05 PM, Randy Tu= rner <rtu= rner@amalfisystems.com> wrote:

Hi Mike,

You're right about multicast DNS not requiring site administration, but dyn= amic DNS is only designed to update A/AAAA records in a zone.  I'm not= aware of anyone using dynamic DNS to update TXT, SRV, or other resource re= cords.  I haven't seen this done.

Randy

On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:

> Randy,
>
> Thanks for the text.  Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) publish LOC= records (RFC 1876) to provide the physical location of a printer.
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)=85.
>>
>>
>> This document is placing requirements on devices for future compli= ance with an IPP everywhere standard -- however, DNS requirements are NOT r= equirements placed on a device, but rather administrative requirements for = the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this documen= t.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere.
>
> Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS.
>
> ______________________________________________________________________= __
> 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
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.
_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/l= istinfo/ipp


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Apple-Mail=_93269102-C73A-4A14-B305-8B859DFD09E6-- --===============0356708155== 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 --===============0356708155==-- From ipp-bounces@pwg.org Tue Apr 10 16:44:25 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7DD11E80DE for ; Tue, 10 Apr 2012 16:44:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wCfJJQ+LnXHC for ; Tue, 10 Apr 2012 16:44:24 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id BB21E11E8081 for ; Tue, 10 Apr 2012 16:44:23 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 627AB79662; Tue, 10 Apr 2012 19:44:00 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 7BC79796F3 for ; Tue, 10 Apr 2012 19:43:40 -0400 (EDT) MIME-version: 1.0 Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2A00LPCF7RM630@mail-out.apple.com> for ipp@pwg.org; Tue, 10 Apr 2012 16:43:11 -0700 (PDT) X-AuditID: 11807130-b7f5e6d000000682-ea-4f84c58e891a Received: from [17.151.77.11] (Unknown_Domain [17.151.77.11]) (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 78.AA.01666.E85C48F4; Tue, 10 Apr 2012 16:43:10 -0700 (PDT) Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) From: Michael Sweet In-reply-to: <9D4F451D-83DE-40EE-B574-EC2395308403@amalfisystems.com> Date: Tue, 10 Apr 2012 16:43:09 -0700 Message-id: References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> <15D36243-48F9-42FD-9B78-E19510180B0D@amalfisystems.com> <9D4F451D-83DE-40EE-B574-EC2395308403@amalfisystems.com> To: Randy Turner X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUiON2XW7fvaIu/wf0juhbH9r1ksTjyLdZi z9o/bA7MHstPfmH22HryB5vHvMXTmQKYo7hsUlJzMstSi/TtErgyrjzZzV6wo7pi8a7vLA2M kzK7GDk4JARMJPoueHYxcgKZYhIX7q1n62Lk4hASmMwk0fB2JhNIQljAR2JLXyMLiM0rYCgx 81U7K4jNLJAgcbpjBVgNm4CaxO9JfWBxTgFXiTcrzjOD2CwCqhIf399hhqjnlzjY+4EZYo6N xP9995kglj1lknj/8x4bSEJEQEei7ek5FoiLZCVuH9zPNIGRbxaS3bOQ7IawtSWWLXzNDGEb SDztfMWKKa4v8ebdHKYFjGyrGAWLUnMSKw0N9RILCnJS9ZLzczcxggK3odBgB+Pan/yHGAU4 GJV4eD19W/yFWBPLiitzDzFKcDArifC6zAYK8aYkVlalFuXHF5XmpBYfYpTmYFES500WaPYX EkhPLEnNTk0tSC2CyTJxcEo1MMor8k77YCThrBm4LPjWgpmT3pf2SG3auEpW4n6h+r2N1X9m rpm791P5521PXq/h+8slEvFi97r6qLU7t6Xzsm2zPPbxQM2RCz6nbdf4ffdQUdvcIbRFITP1 q7y6+80U84uxUQVVN6MvfKh3SD4+hf9jjt3aM9nBLTJNDzIrdk+/Hv56Js/ehwuVWIozEg21 mIuKEwHBZshSWAIAAA== 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="===============0481296676==" 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: 627AB79662.A91FD X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0481296676== Content-type: multipart/alternative; boundary="Boundary_(ID_vXn5hC0fq1+Bri78xr+uXA)" --Boundary_(ID_vXn5hC0fq1+Bri78xr+uXA) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Randy, See: http://dns-sd.org/ServerSetup.html On Apr 10, 2012, at 2:30 PM, Randy Turner wrote: >=20 > Hi Guys, >=20 > In theory, RFC 2136 would allow a client to update any RRset in a zone in= DNS -- however, no one implements just RFC 2136 by itself, since the secur= ity implications would be enormous. >=20 > RFC 2136 would require a vendor to allocate a fair amount of development = resources for implementation and testing. >=20 > In addition, early recommendations strongly suggested any implementation = of RFC 2136 to also include an implementation of RFC 2137, which would requ= ire a bit more development and testing time. >=20 > However, RFC 2137 has been obsoleted through the introduction of DNSSEC m= echanisms (RFC 4033, 4034, and 4035), which require a bit more development.= It would also require the site to move their DNS servers to use DNSSEC. >=20 > Even with these pre-conditions, I'm still trying to determine if DNS serv= er policies would allow arbitrary RRset updates (other than A/AAAA RR types) >=20 > Of course, MDNS (DNS-SD, ZeroConf, etc.) only requires mechanisms on the = client (as everyone probably knows), and many imaging devices already suppo= rt this technology, so I don't see any problem (at least for now) with maki= ng a "MUST" for MDNS records that assist IPP everywhere. >=20 > For server-based DNS, I would recommend against making this a "MUST", bec= ause the implications on vendors and sites may be too high -- I recommend m= aking this requirement a "SHOULD" or "MAY". >=20 > I'll follow up some suggested wording for section 4.2.2, taking into acco= unt the above information. >=20 > Randy >=20 >=20 > On Apr 9, 2012, at 1:00 PM, Randy Turner wrote: >=20 >>=20 >> Yes, I understand that DNS-SD allows "self-publication" and I'm fine wit= h that. >>=20 >> I guess it's the DNS server case that still (I believe) requires adminis= trative assistance. >>=20 >> R. >>=20 >>=20 >> On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote: >>=20 >>> Hi Randy, >>>=20 >>> Printers already commonly publish themselves in SLP (if servers are >>> present) and LDAP/Active Directory automatically. >>>=20 >>> Adding the IPP Everywhere MDNS requirement for DNS-SD publish >>> of LOC and TXT records is a matter of parity in discovery protocols. >>>=20 >>> Cheers, >>> - Ira >>>=20 >>> Ira McDonald (Musician / Software Architect) >>> Chair - Linux Foundation Open Printing WG >>> Secretary - IEEE-ISTO Printer Working Group >>> Co-Chair - IEEE-ISTO PWG IPP WG >>> Co-Chair - TCG Trusted Mobility Solutions WG >>> Chair - TCG Embedded Systems Hardcopy SG >>> IETF Designated Expert - IPP & Printer MIB >>> Blue Roof Music/High North Inc >>> http://sites.google.com/site/blueroofmusic >>> http://sites.google.com/site/highnorthinc >>> mailto:blueroofmusic@gmail.com >>> Winter 579 Park Place Saline, MI 48176 734-944-0094 >>> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 >>>=20 >>>=20 >>>=20 >>> On Mon, Apr 9, 2012 at 2:05 PM, Randy Turner wrote: >>>=20 >>> Hi Mike, >>>=20 >>> You're right about multicast DNS not requiring site administration, but= dynamic DNS is only designed to update A/AAAA records in a zone. I'm not = aware of anyone using dynamic DNS to update TXT, SRV, or other resource rec= ords. I haven't seen this done. >>>=20 >>> Randy >>>=20 >>> On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: >>>=20 >>> > Randy, >>> > >>> > Thanks for the text. Comments below. >>> > >>> > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: >>> >> >>> >> Hi Guys, >>> >> >>> >> Proposed mods for wd-ippeve10-20120201: >>> >> >>> >> 4.2.2 Geo-Location (LOC) >>> >> >>> >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC r= ecords (RFC 1876) to provide the physical location of a printer. >>> >> >>> >> 4.2.3 Service Information (TXT) >>> >> Site administrators MUST publish ("SHOULD" ?)=85. >>> >> >>> >> >>> >> This document is placing requirements on devices for future complian= ce with an IPP everywhere standard -- however, DNS requirements are NOT req= uirements placed on a device, but rather administrative requirements for th= e site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. >>> > >>> > Multicast DNS (part of Bonjour, and a perennial draft awaiting love f= rom the IETF DNS WG) is not managed by site administrators and is part of I= PP Everywhere. >>> > >>> > Also, printers *can* register their own DNS records with traditional = DNS infrastructure using dynamic DNS updates (RFC 2136) and many already ha= ve support for this... >>> > >>> > Anyways, I am happy to note that these are requirements for Multicast= DNS and recommendations for traditional DNS. >>> > >>> > _____________________________________________________________________= ___ >>> > Michael Sweet, Senior Printing System Engineer, PWG Chair >>> > >>> > >>>=20 >>>=20 >>> -- >>> This message has been scanned for viruses and >>> dangerous content by MailScanner, and is >>> believed to be clean. >>>=20 >>> _______________________________________________ >>> ipp mailing list >>> ipp@pwg.org >>> https://www.pwg.org/mailman/listinfo/ipp >>>=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 >=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_vXn5hC0fq1+Bri78xr+uXA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable Randy,

= See:



On Apr 10, 2012, at 2:30 PM, Randy Turner wrote:


Hi Guys,

In theory, RFC 2136 would a= llow a client to update any RRset in a zone in DNS -- however, no one imple= ments just RFC 2136 by itself, since the security implications would be eno= rmous.

RFC 2136 would require a vendor to allocate= a fair amount of development resources for implementation and testing.

In addition, early recommendations strongly suggested= any implementation of RFC 2136 to also include an implementation of RFC 21= 37, which would require a bit more development and testing time.
=
However, RFC 2137 has been obsoleted through the introductio= n of DNSSEC mechanisms (RFC 4033, 4034, and 4035), which require a bit more= development.  It would also require the site to move their DNS server= s to use DNSSEC.

Even with these pre-conditions, I= 'm still trying to determine if DNS server policies would allow arbitrary R= Rset updates (other than A/AAAA RR types)

Of cours= e, MDNS (DNS-SD, ZeroConf, etc.) only requires mechanisms on the client (as= everyone probably knows), and many imaging devices already support this te= chnology, so I don't see any problem (at least for now) with making a "MUST= " for MDNS records that assist IPP everywhere.

For= server-based DNS, I would recommend against making this a "MUST", because = the implications on vendors and sites may be too high -- I recommend making= this requirement a "SHOULD" or "MAY".

I'll follow= up some suggested wording for section 4.2.2, taking into account the above= information.

Randy


<= /div>
On Apr 9, 2012, at 1:00 PM, Randy Turner wrote:

Yes, I understand that DNS-SD allows "sel= f-publication" and I'm fine with that.

I guess it's the = DNS server case that still (I believe) requires administrative assistance.<= /div>

R.


On Apr 9= , 2012, at 11:44 AM, Ira McDonald wrote:

Hi Randy,

Printers already comm= only publish themselves in SLP (if servers are
present) and LDAP/Active = Directory automatically.

Adding the IPP Everywhere MDNS requirement = for DNS-SD publish
of LOC and TXT records is a matter of parity in disco= very protocols.

Cheers,
- Ira

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



On Mon, Apr 9, 2012 at 2:05 PM, Randy Tu= rner <rtu= rner@amalfisystems.com> wrote:

Hi Mike,

You're right about multicast DNS not requiring site administration, but dyn= amic DNS is only designed to update A/AAAA records in a zone.  I'm not= aware of anyone using dynamic DNS to update TXT, SRV, or other resource re= cords.  I haven't seen this done.

Randy

On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:

> Randy,
>
> Thanks for the text.  Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) publish LOC= records (RFC 1876) to provide the physical location of a printer.
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)=85.
>>
>>
>> This document is placing requirements on devices for future compli= ance with an IPP everywhere standard -- however, DNS requirements are NOT r= equirements placed on a device, but rather administrative requirements for = the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this documen= t.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere.
>
> Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS.
>
> ______________________________________________________________________= __
> 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
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.
_______________________________________________
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/l= istinfo/ipp

____________________= ____________________________________________________
Michael Swee= t, Senior Printing System Engineer, PWG Chair


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_vXn5hC0fq1+Bri78xr+uXA)-- --===============0481296676== 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 --===============0481296676==-- From ipp-bounces@pwg.org Tue Apr 10 18:58:20 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D2A11E813E for ; Tue, 10 Apr 2012 18:58:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6wJXfspVpYw for ; Tue, 10 Apr 2012 18:58:19 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id BB36211E8081 for ; Tue, 10 Apr 2012 18:58:18 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id CB9DB79708; Tue, 10 Apr 2012 21:57:58 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr15.networksolutionsemail.com (omr15.networksolutionsemail.com [205.178.146.65]) by pwg.org (Postfix) with ESMTP id 6D39979707 for ; Tue, 10 Apr 2012 21:57:41 -0400 (EDT) Received: from cm-omr10 (mail.networksolutionsemail.com [205.178.146.50]) by omr15.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3B1vcLr025194 for ; Tue, 10 Apr 2012 21:57:38 -0400 Authentication-Results: cm-omr10 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:53221] helo=[192.168.1.114]) by cm-omr10 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id 75/06-30492-215E48F4; Tue, 10 Apr 2012 21:57:38 -0400 From: Randy Turner Mime-Version: 1.0 (Apple Message framework v1257) Subject: Re: [IPP] proposed mods to IPP everywhere spec (per my action item) Date: Tue, 10 Apr 2012 18:57:37 -0700 In-Reply-To: To: ipp@pwg.org References: <69CF758F-1BB7-4706-867A-217AF090DD50@apple.com> <1CD44784-55B0-4DD6-8C77-7A5D25C54170@amalfisystems.com> <15D36243-48F9-42FD-9B78-E19510180B0D@amalfisystems.com> <9D4F451D-83DE-40EE-B574-EC2395308403@amalfisystems.com> Message-Id: <75D85FCB-2AE3-4654-9666-EDA5146E5569@amalfisystems.com> X-Mailer: Apple Mail (2.1257) 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="===============0253750421==" 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: CB9DB79708.A981A X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0253750421== Content-Type: multipart/alternative; boundary="Apple-Mail=_6DB2F2BB-3B90-46EA-A4D6-12E65DF8A6B2" --Apple-Mail=_6DB2F2BB-3B90-46EA-A4D6-12E65DF8A6B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Yeah, RFC 2845 pre-dates DNSSEC, and you can enable dns update (BIND 9) wit= h 2845 mechanisms (TSIG), but it still requires administrative support (con= figuration), so it doesn't address my earlier point about administrative/si= te support. 2136 with 2845 would be easier to implement in clients than that described = in my previous email, but there is a key management issue with 2845, includ= ing the fact that it uses an HMAC based on a deprecated hash function (MD5). I think anything that requires admin support (wide-area bonjour or hierarch= ical DNS service) should probably be a "SHOULD". I'm not sure sites that = are moving to DNSSEC would enable an older form of security if they're goin= g to the trouble of implementing DNSSEC. As I mentioned before, we could add a section to our documents that talks a= bout compliance and "site requirements", which would address anything "NOT"= in the device. Randy On Apr 10, 2012, at 4:43 PM, Michael Sweet wrote: > Randy, >=20 > See: >=20 > http://dns-sd.org/ServerSetup.html >=20 >=20 > On Apr 10, 2012, at 2:30 PM, Randy Turner wrote: >=20 >>=20 >> Hi Guys, >>=20 >> In theory, RFC 2136 would allow a client to update any RRset in a zone i= n DNS -- however, no one implements just RFC 2136 by itself, since the secu= rity implications would be enormous. >>=20 >> RFC 2136 would require a vendor to allocate a fair amount of development= resources for implementation and testing. >>=20 >> In addition, early recommendations strongly suggested any implementation= of RFC 2136 to also include an implementation of RFC 2137, which would req= uire a bit more development and testing time. >>=20 >> However, RFC 2137 has been obsoleted through the introduction of DNSSEC = mechanisms (RFC 4033, 4034, and 4035), which require a bit more development= . It would also require the site to move their DNS servers to use DNSSEC. >>=20 >> Even with these pre-conditions, I'm still trying to determine if DNS ser= ver policies would allow arbitrary RRset updates (other than A/AAAA RR type= s) >>=20 >> Of course, MDNS (DNS-SD, ZeroConf, etc.) only requires mechanisms on the= client (as everyone probably knows), and many imaging devices already supp= ort this technology, so I don't see any problem (at least for now) with mak= ing a "MUST" for MDNS records that assist IPP everywhere. >>=20 >> For server-based DNS, I would recommend against making this a "MUST", be= cause the implications on vendors and sites may be too high -- I recommend = making this requirement a "SHOULD" or "MAY". >>=20 >> I'll follow up some suggested wording for section 4.2.2, taking into acc= ount the above information. >>=20 >> Randy >>=20 >>=20 >> On Apr 9, 2012, at 1:00 PM, Randy Turner wrote: >>=20 >>>=20 >>> Yes, I understand that DNS-SD allows "self-publication" and I'm fine wi= th that. >>>=20 >>> I guess it's the DNS server case that still (I believe) requires admini= strative assistance. >>>=20 >>> R. >>>=20 >>>=20 >>> On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote: >>>=20 >>>> Hi Randy, >>>>=20 >>>> Printers already commonly publish themselves in SLP (if servers are >>>> present) and LDAP/Active Directory automatically. >>>>=20 >>>> Adding the IPP Everywhere MDNS requirement for DNS-SD publish >>>> of LOC and TXT records is a matter of parity in discovery protocols. >>>>=20 >>>> Cheers, >>>> - Ira >>>>=20 >>>> Ira McDonald (Musician / Software Architect) >>>> Chair - Linux Foundation Open Printing WG >>>> Secretary - IEEE-ISTO Printer Working Group >>>> Co-Chair - IEEE-ISTO PWG IPP WG >>>> Co-Chair - TCG Trusted Mobility Solutions WG >>>> Chair - TCG Embedded Systems Hardcopy SG >>>> IETF Designated Expert - IPP & Printer MIB >>>> Blue Roof Music/High North Inc >>>> http://sites.google.com/site/blueroofmusic >>>> http://sites.google.com/site/highnorthinc >>>> mailto:blueroofmusic@gmail.com >>>> Winter 579 Park Place Saline, MI 48176 734-944-0094 >>>> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 >>>>=20 >>>>=20 >>>>=20 >>>> On Mon, Apr 9, 2012 at 2:05 PM, Randy Turner wrote: >>>>=20 >>>> Hi Mike, >>>>=20 >>>> You're right about multicast DNS not requiring site administration, bu= t dynamic DNS is only designed to update A/AAAA records in a zone. I'm not= aware of anyone using dynamic DNS to update TXT, SRV, or other resource re= cords. I haven't seen this done. >>>>=20 >>>> Randy >>>>=20 >>>> On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote: >>>>=20 >>>> > Randy, >>>> > >>>> > Thanks for the text. Comments below. >>>> > >>>> > On Apr 9, 2012, at 10:24 AM, Randy Turner wrote: >>>> >> >>>> >> Hi Guys, >>>> >> >>>> >> Proposed mods for wd-ippeve10-20120201: >>>> >> >>>> >> 4.2.2 Geo-Location (LOC) >>>> >> >>>> >> Site administrators MUST (should this be a "SHOULD" ?) publish LOC = records (RFC 1876) to provide the physical location of a printer. >>>> >> >>>> >> 4.2.3 Service Information (TXT) >>>> >> Site administrators MUST publish ("SHOULD" ?)=85. >>>> >> >>>> >> >>>> >> This document is placing requirements on devices for future complia= nce with an IPP everywhere standard -- however, DNS requirements are NOT re= quirements placed on a device, but rather administrative requirements for t= he site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this document. >>>> > >>>> > Multicast DNS (part of Bonjour, and a perennial draft awaiting love = from the IETF DNS WG) is not managed by site administrators and is part of = IPP Everywhere. >>>> > >>>> > Also, printers *can* register their own DNS records with traditional= DNS infrastructure using dynamic DNS updates (RFC 2136) and many already h= ave support for this... >>>> > >>>> > Anyways, I am happy to note that these are requirements for Multicas= t DNS and recommendations for traditional DNS. >>>> > >>>> > ____________________________________________________________________= ____ >>>> > Michael Sweet, Senior Printing System Engineer, PWG Chair >>>> > >>>> > >>>>=20 >>>>=20 >>>> -- >>>> This message has been scanned for viruses and >>>> dangerous content by MailScanner, and is >>>> believed to be clean. >>>>=20 >>>> _______________________________________________ >>>> ipp mailing list >>>> ipp@pwg.org >>>> https://www.pwg.org/mailman/listinfo/ipp >>>>=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 >>=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 >=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Apple-Mail=_6DB2F2BB-3B90-46EA-A4D6-12E65DF8A6B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252

Yeah, RFC 2= 845 pre-dates DNSSEC, and you can enable dns update (BIND 9) with 2845 mech= anisms (TSIG), but it still requires administrative support (configuration)= , so it doesn't address my earlier point about administrative/site support.=

2136 with 2845 would be easier to implement in clients = than that described in my previous email, but there is a key management iss= ue with 2845, including the fact that it uses an HMAC based on a deprecated= hash function (MD5).

I think anything that requir= es admin support (wide-area bonjour or hierarchical DNS service) should pro= bably be a "SHOULD".   I'm not sure sites that are moving to DNSSEC wo= uld enable an older form of security if they're going to the trouble of imp= lementing DNSSEC.

As I mentioned before, we could = add a section to our documents that talks about compliance and "site requir= ements", which would address anything "NOT" in the device.

Randy


On Apr 10, 2012,= at 4:43 PM, Michael Sweet wrote:

Randy,

<= /div>
See:



On Apr 10, 2012, at 2:30 PM, Randy Turner wrote:


Hi Guys,

In theory, RFC 21= 36 would allow a client to update any RRset in a zone in DNS -- however, no= one implements just RFC 2136 by itself, since the security implications wo= uld be enormous.

RFC 2136 would require a vendor t= o allocate a fair amount of development resources for implementation and te= sting.

In addition, early recommendations strongly= suggested any implementation of RFC 2136 to also include an implementation= of RFC 2137, which would require a bit more development and testing time.<= /div>

However, RFC 2137 has been obsoleted through the i= ntroduction of DNSSEC mechanisms (RFC 4033, 4034, and 4035), which require = a bit more development.  It would also require the site to move their = DNS servers to use DNSSEC.

Even with these pre-con= ditions, I'm still trying to determine if DNS server policies would allow a= rbitrary RRset updates (other than A/AAAA RR types)

Of course, MDNS (DNS-SD, ZeroConf, etc.) only requires mechanisms on the = client (as everyone probably knows), and many imaging devices already suppo= rt this technology, so I don't see any problem (at least for now) with maki= ng a "MUST" for MDNS records that assist IPP everywhere.

For server-based DNS, I would recommend against making this a "MUST"= , because the implications on vendors and sites may be too high -- I recomm= end making this requirement a "SHOULD" or "MAY".

I= 'll follow up some suggested wording for section 4.2.2, taking into account= the above information.

Randy

=

On Apr 9, 2012, at 1:00 PM, Randy Turner wrot= e:

<= div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-= break: after-white-space; ">

Yes, I understand that DNS-SD al= lows "self-publication" and I'm fine with that.

I guess = it's the DNS server case that still (I believe) requires administrative ass= istance.

R.


On Apr 9, 2012, at 11:44 AM, Ira McDonald wrote:

Hi Randy,

Printers alr= eady commonly publish themselves in SLP (if servers are
present) and LDA= P/Active Directory automatically.

Adding the IPP Everywhere MDNS req= uirement for DNS-SD publish
of LOC and TXT records is a matter of parity= in discovery protocols.

Cheers,
- Ira

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



On Mon, Apr 9, 2012 at 2:05 PM, Randy Tu= rner <rtu= rner@amalfisystems.com> wrote:

Hi Mike,

You're right about multicast DNS not requiring site administration, but dyn= amic DNS is only designed to update A/AAAA records in a zone.  I'm not= aware of anyone using dynamic DNS to update TXT, SRV, or other resource re= cords.  I haven't seen this done.

Randy

On Apr 9, 2012, at 10:59 AM, Michael Sweet wrote:

> Randy,
>
> Thanks for the text.  Comments below.
>
> On Apr 9, 2012, at 10:24 AM, Randy Turner wrote:
>>
>> Hi Guys,
>>
>> Proposed mods for wd-ippeve10-20120201:
>>
>> 4.2.2 Geo-Location (LOC)
>>
>> Site administrators MUST (should this be a "SHOULD" ?) publish LOC= records (RFC 1876) to provide the physical location of a printer.
>>
>> 4.2.3 Service Information (TXT)
>> Site administrators MUST publish ("SHOULD" ?)=85.
>>
>>
>> This document is placing requirements on devices for future compli= ance with an IPP everywhere standard -- however, DNS requirements are NOT r= equirements placed on a device, but rather administrative requirements for = the site DNS -- so I'm not sure that 4.2.2 and 4.2.3 belong in this documen= t.
>
> Multicast DNS (part of Bonjour, and a perennial draft awaiting love fr= om the IETF DNS WG) is not managed by site administrators and is part of IP= P Everywhere.
>
> Also, printers *can* register their own DNS records with traditional D= NS infrastructure using dynamic DNS updates (RFC 2136) and many already hav= e support for this...
>
> Anyways, I am happy to note that these are requirements for Multicast = DNS and recommendations for traditional DNS.
>
> ______________________________________________________________________= __
> 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
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.
_______________________________________________
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

=
_________________________________________= _______________________________
Michael Sweet, Senior Printing Sy= stem Engineer, PWG Chair



--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Apple-Mail=_6DB2F2BB-3B90-46EA-A4D6-12E65DF8A6B2-- --===============0253750421== 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 --===============0253750421==-- From ipp-bounces@pwg.org Sun Apr 15 21:44:48 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F172C21F879F for ; Sun, 15 Apr 2012 21:44:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.391 X-Spam-Level: X-Spam-Status: No, score=-101.391 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEX6fR2sYLxn for ; Sun, 15 Apr 2012 21:44:47 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8941621F8796 for ; Sun, 15 Apr 2012 21:44:46 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E59B9795CA; Mon, 16 Apr 2012 00:43:59 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 0B03179595; Mon, 16 Apr 2012 00:43:34 -0400 (EDT) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2K00DKB2GMKP01@mail-out.apple.com>; Sun, 15 Apr 2012 21:43:34 -0700 (PDT) X-AuditID: 11807136-b7f516d000003f9b-fb-4f8ba37534e6 Received: from [17.151.70.69] (Unknown_Domain [17.151.70.69]) by relay15.apple.com (Apple SCV relay) with SMTP id 3A.63.16283.573AB8F4; Sun, 15 Apr 2012 21:43:33 -0700 (PDT) From: Michael Sweet Date: Sun, 15 Apr 2012 21:43:39 -0700 Message-id: <2E4E836D-65E4-4C33-A0AC-26815830D6BB@apple.com> To: ipp@pwg.org X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLLMWRmVeSWpSXmKPExsUiON3NVbd0cbe/wdvv1haXtx9gtTi27yWL A5PHvMXTmQIYo7hsUlJzMstSi/TtErgyVu9ezlRwXaTi1f36BsbDQl2MnBwSAiYSr67vZIaw xSQu3FvP1sXIxSEksJ5R4t6VWUwgCTYBNYnfk/pYQWxmgQSJtTengtnCAqoSS/+cZQSxWYDs mx1rwOK8AjYSveteskHUC0p8bW0AmyMiwC8x8WIfVI2hxMxX7awQi2Ulbh/czzSBkWcWkhWz kJRBxOUltr+dwzyLkQPI1pGYvJARIqwtsWzha2YY++P5I0wLGNlWMQoWpeYkVhqa6iUWFOSk 6iXn525iBAVaQ6HZDsYdf+UOMQpwMCrx8K6K6/YXYk0sK67MPcQowcGsJMIbIwsU4k1JrKxK LcqPLyrNSS0+xCjNwaIkzpsu0OwvJJCeWJKanZpakFoEk2Xi4JRqYLSZtW5DTbDS/v+Tj7pf 3qMptOQ168mHWgm/+GtdSma9nu0amc8+zapY98KZ33FxZdb+fNXJd1e/fOhrIXV8Gavsmr5t CRzxT9LNPkQs89RXu2xgYvm8RVyl0OUcr2Gb2a/wF6Ga8dMmt3Dm711dw7b51MuWqRrzTHsy Gp8kCp10aVAUMy1bqsRSnJFoqMVcVJwIAFiAx48wAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: cloud@pwg.org Subject: [IPP] Draft slides for IPP session 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="===============0400134875==" 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: E59B9795CA.A858B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============0400134875== Content-type: multipart/alternative; boundary="Boundary_(ID_rVJcoE9tsS9VC6WPoSkPUQ)" --Boundary_(ID_rVJcoE9tsS9VC6WPoSkPUQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the draft slides for the IPP session to: ftp://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-12d1.pdf For discussion in Monday's concall. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_rVJcoE9tsS9VC6WPoSkPUQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted the draft slides for the IPP session to:

ftp:= //ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-12d1.pdf

For discussion in Monday's concall.

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_rVJcoE9tsS9VC6WPoSkPUQ)-- --===============0400134875== 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 --===============0400134875==-- From ipp-bounces@pwg.org Mon Apr 16 14:15:09 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44BCD21F855B for ; Mon, 16 Apr 2012 14:15:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.412 X-Spam-Level: X-Spam-Status: No, score=-102.412 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dKdRWZQ+P7Q for ; Mon, 16 Apr 2012 14:15:08 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 783EB21F8559 for ; Mon, 16 Apr 2012 14:15:08 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 877DF795EF; Mon, 16 Apr 2012 17:14:37 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 0A983795DE; Mon, 16 Apr 2012 17:14:18 -0400 (EDT) MIME-version: 1.0 Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2L00I2KCAVQA62@mail-out.apple.com>; Mon, 16 Apr 2012 14:14:18 -0700 (PDT) X-AuditID: 11807136-b7f516d000003f9b-a1-4f8c8baa56bb Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay15.apple.com (Apple SCV relay) with SMTP id EC.45.16283.AAB8C8F4; Mon, 16 Apr 2012 14:14:18 -0700 (PDT) From: Michael Sweet Date: Mon, 16 Apr 2012 14:14:18 -0700 To: cloud@pwg.org Message-id: X-Mailer: Apple Mail (2.1278) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUieFRTW3dVd4+/wcy9nBaXtx9gtTi27yWL xZFvsQ7MHltP/mDzmLd4OlMAUxSXTUpqTmZZapG+XQJXxu2WT0wFHfIVXdseMjcwfpfuYuTk kBAwkXi06TYrhC0mceHeejYQW0hgOpNE6+EyEJtNQE3i96Q+sBpeAUOJ/y2/mLsYOTiYBRIk vkwwBAmzCKhKXLu/DKxEWMBM4se2HYwgNrOAosSy6X/A4iICghLnD9xgghhjI3Gmr5sJYq2s xO3mCewTGHlmIdkwC2HDLLBJ8hLb386BCutITF7ICBHWlli28DUzjP3x/BGmBYxsqxgFi1Jz EisNTfUSCwpyUvWS83M3MYLCrqHQbAfjjr9yhxgFOBiVeHhnGvb4C7EmlhVX5h5ilOBgVhLh FSoECvGmJFZWpRblxxeV5qQWH2KU5mBREudNF2j2FxJITyxJzU5NLUgtgskycXBKNTBOePX0 QG5ulmHYGs3LAgp1rAmWJmf8ndd4rQk6tP+Bi3W1zWupQmvn8zbhy3PnzVnz78fJLWtND0Vd YcoL3q68QK/8UezsNQlFPtebhKfb6Xho/Hzj9i+QuWrbjSfzesWe/HnMdPDlvP/3w5/2vYia onv1y/W/d7Z+dTAzPab66NF/08LaM5w9SizFGYmGWsxFxYkAZWeyJjcCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "" Subject: [IPP] Minutes posted from today's Cloud/IPP concall X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2036069903==" 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: 877DF795EF.A915B X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============2036069903== Content-type: multipart/alternative; boundary="Boundary_(ID_o3XKiwb4LxdE2kjlv8eyng)" --Boundary_(ID_o3XKiwb4LxdE2kjlv8eyng) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted the minutes from today's combined Cloud/IPP conference call to: ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20120416.pdf ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_o3XKiwb4LxdE2kjlv8eyng) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

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


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_o3XKiwb4LxdE2kjlv8eyng)-- --===============2036069903== 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 --===============2036069903==-- From pwg-announce-bounces@pwg.org Mon Apr 16 15:17:37 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E434611E80CC for ; Mon, 16 Apr 2012 15:17:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.436 X-Spam-Level: X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vy-slSDlr6tQ for ; Mon, 16 Apr 2012 15:17:37 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC1911E80C1 for ; Mon, 16 Apr 2012 15:17:37 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 05BD379606; Mon, 16 Apr 2012 18:17:14 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 7ACBA795EA for ; Mon, 16 Apr 2012 18:16:59 -0400 (EDT) MIME-version: 1.0 Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2L00IWTF83QAE2@mail-out.apple.com> for pwg-announce@pwg.org; Mon, 16 Apr 2012 15:16:57 -0700 (PDT) X-AuditID: 11807137-b7f536d000006fcc-99-4f8c9a581106 Received: from msweet.apple.com (msweet.apple.com [17.197.41.43]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 51.30.28620.85A9C8F4; Mon, 16 Apr 2012 15:16:56 -0700 (PDT) From: Michael Sweet Date: Mon, 16 Apr 2012 15:16:56 -0700 To: pwg-announce@pwg.org Message-id: <91FD7951-1B18-4E2A-A646-A2F1CA2E3989@apple.com> X-Mailer: Apple Mail (2.1278) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUieFRTWzdiVo+/Qc9TG4sj32It1rWuZnZg 8th68gebx7zF05kCmKK4bFJSczLLUov07RK4Mh5P6mQt+Kxc8XXicbYGxl/yXYwcHBICJhIN 1xW6GDmBTDGJC/fWs3UxcnEICUxnknj6/QYLSIJNQE3i96Q+VhCbWSBB4uzL62A2i4CqxI5Z z9hAbGEBF4ndOzYzg9giAhIS07rngdXwCthIvOpazA5hG0r8b/nFDLFMVuJ28wT2CYzcs5CM nYWkDCKuLbFs4WsgmwPI1pGYvJARVRjC/nj+CNMCRrZVjIJFqTmJlYZmeokFBTmpesn5uZsY QYHVUGi+g3H7X7lDjAIcjEo8vDMNe/yFWBPLiitzDzFKcDArifAKFQKFeFMSK6tSi/Lji0pz UosPMUpzsCiJ82YKNPsLCaQnlqRmp6YWpBbBZJk4OKUaGGMeTK47OFdXZ1n0c06PmQeOyL3/ lnVR/Omar3v8bqj94rDeUvTqRFzbuatNVikNYqLpOXOYl7znUnD6M2mL+OSwY2eC+K9UaXrz 30hO5JH2nVJ93cVU/Ovin+t4NljzdXj/CuFUMVy5j3lf26cy121c/SUKHsKt3lq6DguNNnlP LThdIeO5VomlOCPRUIu5qDgRAP/XcAgoAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] NOTICE: Room Change for April 2012 PWG Face-to-Face Meeting 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="===============0867989794==" 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: 05BD379606.AB6FD X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0867989794== Content-type: multipart/alternative; boundary="Boundary_(ID_p0B2rfAohqooictClqWgVA)" --Boundary_(ID_p0B2rfAohqooictClqWgVA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, The April 2012 PWG Face-to-Face Meeting has MOVED to the "Beatles" conference room in the De Anza 3 building (just across the street from the main campus) located at: 10500 N. De Anza Blvd Cupertino, CA 95014 An updated map and directions have been posted to the meeting page at: http://www.pwg.org/chair/meeting-info/april_2012_cupertino.html ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_p0B2rfAohqooictClqWgVA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

Th= e April 2012 PWG Face-to-Face Meeting has MOVED to the "Beatles" confe= rence room in the De Anza 3 building (just across the street from the = main campus) located at:

10500 N. De Anza Blvd
Cupertino, CA= 95014

An updated map and directions have been pos= ted to the meeting page at:


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_p0B2rfAohqooictClqWgVA)-- --===============0867989794== 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 --===============0867989794==-- From pwg-announce-bounces@pwg.org Tue Apr 17 07:18:07 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FCE11E8080 for ; Tue, 17 Apr 2012 07:18:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1ee6hguNHwB for ; Tue, 17 Apr 2012 07:18:03 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 556E011E8098 for ; Tue, 17 Apr 2012 07:17:54 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 9866879638; Tue, 17 Apr 2012 10:17:12 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 4036479625; Tue, 17 Apr 2012 10:16:52 -0400 (EDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq8BAJN6jU8NKeYdmWdsb2JhbABBA4JGrmMiAQEBAQEICwsHFCeCCwMCDwEMEQMvLAEqBgwLAQdFEgEEARIIiAmmNgGTaYplgmmCRmMEiFygUIE8 Received: from usa7109ht003.na.xerox.net ([13.41.230.29]) by USA7109MR001.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 17 Apr 2012 09:16:51 -0500 Received: from USA7061GW002.na.xerox.net (13.151.210.15) by USA7109HT003.na.xerox.net (13.41.230.29) with Microsoft SMTP Server id 14.1.355.2; Tue, 17 Apr 2012 09:16:51 -0500 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 17 Apr 2012 07:16:17 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 17 Apr 2012 07:16:15 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: The Transform Service specification to be used at the upcoming Face to Face meeting is available Thread-Index: Ac0cpKQv7t8Pz51PTDiAluxKIGg7Cw== From: "Zehler, Peter" To: , X-OriginalArrivalTime: 17 Apr 2012 14:16:17.0234 (UTC) FILETIME=[A7668320:01CD1CA4] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [Pwg-Announce] The Transform Service specification to be used at the upcoming Face to Face meeting is available 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="===============1592852195==" 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: 9866879638.ABA4C X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============1592852195== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD1CA4.A728C175" ------_=_NextPart_001_01CD1CA4.A728C175 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 The updated Transform Service specification is available at =20 (As usual the docx version and the -rev versions are also available.)=20 =20 This is the version that will be reviewed at the upcoming Face to Face meeting hosted by Apple. =20 Pete =20 =20 Peter Zehler Xerox Research Center Webster Email: Peter.Zehler@Xerox.com =20 Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701=20 =20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CD1CA4.A728C175 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,<= /p>

 

The updat= ed Transform Service specification is available at

<ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdtransformmode= l01-20120412.pdf>

(As usual the = docx version and the  –rev versions are also available.)

 

This= is the version that will be reviewed at the upcoming Face to Face meeting = hosted by Apple.

 

Pete

 

 

Peter Zehler

Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265= -8755
FAX: (585) 265-7441<= /span>
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_01CD1CA4.A728C175-- --===============1592852195== 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 --===============1592852195==-- From almoxarifado@mvlmaquinas.com.br Wed Apr 18 20:32:31 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D23411E8075; Wed, 18 Apr 2012 20:32:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.772 X-Spam-Level: **** X-Spam-Status: No, score=4.772 tagged_above=-999 required=5 tests=[BAYES_99=3.5, SARE_HEAD_XLIB_INDY2=1.272] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzTjwchqbdtq; Wed, 18 Apr 2012 20:32:27 -0700 (PDT) Received: from n27.c07.mtsvc.net (n27.c07.mtsvc.net [205.186.180.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6D34A11E807F; Wed, 18 Apr 2012 20:32:27 -0700 (PDT) Received: from 187-25-138-184.3g.claro.net.br ([187.25.138.184]:2048 helo=propriet-74476c) by n27.c07.mtsvc.net with esmtpa (Exim 4.69) (envelope-from ) id 1SKi6Y-0000D5-IP; Wed, 18 Apr 2012 20:32:23 -0700 From: "Comprovante" Subject: Transferido em 18/04/2012 To: ipplatina@hotmail.com Content-Type: text/plain; Reply-To: almoxarifado@mvlmaquinas.com.br Date: Thu, 19 Apr 2012 00:32:39 -0300 X-Priority: 3 X-Library: Indy 8.0.25 Message-Id: X-Authenticated-User: 107477 almoxarifado@mvlmaquinas.com.br Estou enviando o comprovante da transferencia efetuada para sua conta corrente, nesta segunda-feira dia 18 de Abril. Por favor confirme o valor e os dados no comprovante em anexo a baixo. Anexo: http://dc472.4shared.com/download/4rIH2QEz/Comprovante.zip Qual quer dvida responda este e-mail. Atenciosamente, Carlos Henrique From almoxarifado@mvlmaquinas.com.br Wed Apr 18 20:32:31 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D23411E8075; Wed, 18 Apr 2012 20:32:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.772 X-Spam-Level: **** X-Spam-Status: No, score=4.772 tagged_above=-999 required=5 tests=[BAYES_99=3.5, SARE_HEAD_XLIB_INDY2=1.272] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzTjwchqbdtq; Wed, 18 Apr 2012 20:32:27 -0700 (PDT) Received: from n27.c07.mtsvc.net (n27.c07.mtsvc.net [205.186.180.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6D34A11E807F; Wed, 18 Apr 2012 20:32:27 -0700 (PDT) Received: from 187-25-138-184.3g.claro.net.br ([187.25.138.184]:2048 helo=propriet-74476c) by n27.c07.mtsvc.net with esmtpa (Exim 4.69) (envelope-from ) id 1SKi6Y-0000D5-IP; Wed, 18 Apr 2012 20:32:23 -0700 From: "Comprovante" Subject: Transferido em 18/04/2012 To: ipplatina@hotmail.com Content-Type: text/plain; Reply-To: almoxarifado@mvlmaquinas.com.br Date: Thu, 19 Apr 2012 00:32:39 -0300 X-Priority: 3 X-Library: Indy 8.0.25 Message-Id: X-Authenticated-User: 107477 almoxarifado@mvlmaquinas.com.br Estou enviando o comprovante da transferencia efetuada para sua conta corrente, nesta segunda-feira dia 18 de Abril. Por favor confirme o valor e os dados no comprovante em anexo a baixo. Anexo: http://dc472.4shared.com/download/4rIH2QEz/Comprovante.zip Qual quer dvida responda este e-mail. Atenciosamente, Carlos Henrique From ipp-bounces@pwg.org Thu Apr 19 08:45:05 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722FD21F866E for ; Thu, 19 Apr 2012 08:45:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.391 X-Spam-Level: X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRugp1oKTIQK for ; Thu, 19 Apr 2012 08:45:01 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1235721F8672 for ; Thu, 19 Apr 2012 08:45:01 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 6E0DD79636; Thu, 19 Apr 2012 11:44:37 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by pwg.org (Postfix) with ESMTP id 38D1A79636 for ; Thu, 19 Apr 2012 11:44:14 -0400 (EDT) Received: by wibhr14 with SMTP id hr14so1663344wib.11 for ; Thu, 19 Apr 2012 08:44:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=uQB3poSRGykjLt8sp13t89v/ecd7ALJBa6o7VZZxp9c=; b=LkS5BV8x6HGRAzXBtK+GfdcKPsOyuDoepyoRSoPAD2f5goNANDWDHq2sdF4dFVSRmc fNTdKRRtgN4AiwG0i7jwIPoV6bSERw7Ycc5wH59zBlwB4AFpI+yY8hYDtvkaIoxQgI1h 77bUXas95s1qOL4B5cLQzJiKWGi63oCmZukB4XQrd14AGbKMKo0K754xL5j8wi69WboT ik5GWug2HfmKtqUryjA6yHcgD2mV5ppXkLXqWXTYteSAsfvXgO24TAA3yRLIL4Y1YGMp igX8pHemuyY3sxYLZAnr8sJUJyGhYNQoCupCzDw2Ws0Fqm53GamE5ScdfzVSTwswgA7X oofw== MIME-Version: 1.0 Received: by 10.180.107.104 with SMTP id hb8mr6449068wib.8.1334850254280; Thu, 19 Apr 2012 08:44:14 -0700 (PDT) Received: by 10.223.143.18 with HTTP; Thu, 19 Apr 2012 08:44:14 -0700 (PDT) Date: Thu, 19 Apr 2012 11:44:14 -0400 Message-ID: From: Ira McDonald To: ipp@pwg.org, Ira McDonald X-pwg-MailScanner: Found to be clean, Found to be clean Cc: Subject: [IPP] IPP Charter - updated draft (19 April 2012) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1132630345==" 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: 6E0DD79636.A907F X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1132630345== Content-Type: multipart/alternative; boundary=e89a8f234ce53c18b304be0a0b3f --e89a8f234ce53c18b304be0a0b3f Content-Type: text/plain; charset=ISO-8859-1 Hi, [For review and approval at today's PWG Steering Committee meeting] Per the discussion at the IPP WG teleconference on 9 April 2012, I've just posted a Stable draft of an updated IPP Charter for the renamed IPP Everywhere and IPP Multifunction projects: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120419.pdf - clean copy w/ line numbers ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20120419-rev.pdf - redlines copy w/ line numbers Changed PWG Raster to "PWG Raster Format" and changes MSN2 name to "Media Standardized Names 2.0" (with version number added to the document title). Comments? Cheers, - Ira Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --e89a8f234ce53c18b304be0a0b3f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

[For review and approval at today's PWG Steerin= g Committee meeting]


Per the discussion at the IPP WG teleconfer= ence on 9 April 2012, I've just posted
a Stable draft of an updated IPP Charter for the = renamed IPP Everywhere and IPP
Multifunction = projects:

=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippev= erywhere-charter-20120419.pdf
=A0 - clean copy w/ line numbers
=A0 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp= everywhere-charter-20120419-rev.pdf
=A0 - redlines copy w/ line numbers

Changed PWG Raster to "PWG = Raster Format" and changes MSN2 name to "Media
Standardized N= ames 2.0" (with version number added to the document title).

Comments?

Cheers,
- Ira


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --e89a8f234ce53c18b304be0a0b3f-- --===============1132630345== 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 --===============1132630345==-- From ipp-bounces@pwg.org Thu Apr 19 10:15:14 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59C421F86B2 for ; Thu, 19 Apr 2012 10:15:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CS3hDxWxn-uZ for ; Thu, 19 Apr 2012 10:15:11 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B83FD21F8692 for ; Thu, 19 Apr 2012 10:15:10 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id D307779650; Thu, 19 Apr 2012 13:14:40 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR003.ACS-INC.COM (usa7109mr003.acs-inc.com [63.101.151.12]) by pwg.org (Postfix) with ESMTP id D31E979633 for ; Thu, 19 Apr 2012 13:14:21 -0400 (EDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgEAApHkE8NKeYegWdsb2JhbABAA4JGrn4iAQEWJieCCQEBAQICDwEMEQMvDxsCAQgOAwQBAQsGDAcEAQYBRQkIAQEEARIIiAqnHQGUAopxgkyCR2MEiFygVYE8 Received: from usa7109ht004.na.xerox.net ([13.41.230.30]) by USA7109MR003.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 19 Apr 2012 12:14:20 -0500 Received: from USA7061GW001.na.xerox.net (13.151.209.15) by USA7109HT004.na.xerox.net (13.41.230.30) with Microsoft SMTP Server id 14.1.355.2; Thu, 19 Apr 2012 12:14:20 -0500 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA7061GW001.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 19 Apr 2012 10:14:16 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) Date: Thu, 19 Apr 2012 10:14:11 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) Thread-Index: Ac0WrwTKCacBBXfBQfOX4cl28Kgs9AHn5dLw References: From: "Zehler, Peter" To: Michael Sweet , X-OriginalArrivalTime: 19 Apr 2012 17:14:16.0841 (UTC) FILETIME=[D9C4B790:01CD1E4F] 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="===============1727852895==" 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: D307779650.AA89E X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1727852895== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD1E4F.D9882983" ------_=_NextPart_001_01CD1E4F.D9882983 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Xerox has a strong objection to making the value 'process-monochrome" REQUIRED for color printers. We want it changed to OPTIONAL. For laser printers, process monochrome function causes trouble with drums and/or developers. It also can cause a degradation in print quality.=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 From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Monday, April 09, 2012 8:14 PM To: Subject: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) =20 All, =20 This message initiates the IPP Working Group last call of the IPP Job and Printer Extensions - Set 3 (JPS3) specification that has been in extended development since last year. The latest stable draft can be found here: =20 =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.docx =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409.pdf =20 ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120409-rev.pd f =20 Please send all feedback to the IPP mailing list (reply-all works fine for this) and it will be collected and processed as quickly as possible. Our intent is to move JPS3 to PWG Last Call to span the April 2012 F2F. =20 Thank you! =20 ________________________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair =20 --=20 This message has been scanned for viruses and=20 dangerous content by MailScanner , and is believed to be clean.=20 --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------_=_NextPart_001_01CD1E4F.D9882983 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Xerox has= a strong objection to making the value ‘process-monochrome” RE= QUIRED for color printers.  We want it changed to OPTIONAL.  For = laser printers, process monochrome function causes trouble with drums and/o= r developers.  It also can cause a degradation in print quality. =  

 <= /span>

 

Peter Zehler

Xerox Resea= rch 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<= span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F= 497D'>
Webster NY, 14580-9701

=  

From:<= span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ipp-boun= ces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet<= br>Sent: Monday, April 09, 2012 8:14 PM
To: <ipp@pwg.or= g>
Subject: [IPP] WG Last Call - IPP Job and Printer Extension= s - Set 3 (JPS3) (April 9 through April 18, 2012)

 

All,=

 

This message initiates the IPP Working Group last call o= f the IPP Job and Printer Extensions - Set 3 (JPS3) specification that has = been in extended development since last year. The latest stable draft can b= e found here:

 

=

 

Please send all feedback to the IPP mailing list (reply-all works fine = for this) and it will be collected and processed as quickly as possible. Ou= r intent is to move JPS3 to PWG Last Call to span the April 2012 F2F.<= /o:p>

 

Thank you!

 

<= span style=3D'font-size:13.5pt;font-family:"Monaco","serif";color:black'>__= ______________________________________________________________________=

Michael Sweet, Senior Print= ing System Engineer, PWG Chair

 


--
This message has been scanned for viruses and
dangerous con= tent by MailScanner, an= d 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_01CD1E4F.D9882983-- --===============1727852895== 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 --===============1727852895==-- From ipp-bounces@pwg.org Thu Apr 19 10:47:00 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F32221F8616 for ; Thu, 19 Apr 2012 10:47:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.447 X-Spam-Level: X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpuHrLQEvQsE for ; Thu, 19 Apr 2012 10:46:59 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9FD21F845E for ; Thu, 19 Apr 2012 10:46:56 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 57ABB79662; Thu, 19 Apr 2012 13:46:37 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 48BE07965D for ; Thu, 19 Apr 2012 13:46:20 -0400 (EDT) MIME-version: 1.0 Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2Q002DVMP7HNS0@mail-out.apple.com> for ipp@pwg.org; Thu, 19 Apr 2012 10:46:20 -0700 (PDT) X-AuditID: 11807112-b7f826d000004103-f9-4f904f6bf40b Received: from [17.151.81.192] (Unknown_Domain [17.151.81.192]) by relay17.apple.com (Apple SCV relay) with SMTP id B2.E6.16643.B6F409F4; Thu, 19 Apr 2012 10:46:20 -0700 (PDT) Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) From: Michael Sweet In-reply-to: Date: Thu, 19 Apr 2012 10:46:22 -0700 Message-id: References: To: "Zehler, Peter" X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUiOD3wgG6O/wR/g9afYhbH9r1ksTjyLdai 48lKVgdmj60nf7B5zFs8nclj+an1bAHMUVw2Kak5mWWpRfp2CVwZW74LFLQ3M1Y8PbyYpYFx SnEXIyeHhICJxI95i1khbDGJC/fWs3UxcnEICWxklGg4uIYJJCEsUCDxdt87dhCbV8BQYuar drAGZoEEif4p18FsNgE1id+T+sBsToEAiaenD7KB2CwCqhLts/4wQtTzSxzs/cDcxcgBNMdG Yu1BqF0NjBJ/398Emy8ioCOx8eF+ZoiDZCVuH9zPNIGRbxaS1bOQrIawtSWWLXzNDGEbSDzt fIVFXF/izbs5TAsY2VYxChal5iRWGprrJRYU5KTqJefnbmIEBW5DodAOxvu79A4xCnAwKvHw cklM8BdiTSwrrsw9xCjBwawkwjsfJMSbklhZlVqUH19UmpNafIhRmoNFSZx3uVO/v5BAemJJ anZqakFqEUyWiYNTqoHR8E8dY8YM2QP6yyWlV2x6ExXQHGa77cC+nQF1bl4V/OwuLROUpumY J13vv8a3xeLZLUW1ab/4A1W/1qqvlMy9GG92/WhN/He+efrPmCY+WP1t+gKzt0wxaz39HXPm NiyTErDUT/v/t7jMd7fAjE/Rt8p/h6Yu2Pao/3trrUnd3RXLtrNOm6OkxFKckWioxVxUnAgA Pjhp+lgCAAA= 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="===============1940165842==" 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: 57ABB79662.AA3C7 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1940165842== Content-type: multipart/alternative; boundary="Boundary_(ID_CyQSI9j44YU+12IEL+fPTw)" --Boundary_(ID_CyQSI9j44YU+12IEL+fPTw) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable Pete, I've received the same concerns from a couple people offline (yes, I asked = them to post their comments to the list..) - changed process-monochrome to = OPTIONAL but left monochrome, color, and auto as REQUIRED. I have also adde= d a note for this explaining why process-monochrome is OPTIONAL. On Apr 19, 2012, at 10:14 AM, Zehler, Peter wrote: > Xerox has a strong objection to making the value =91process-monochrome=94= REQUIRED for color printers. We want it changed to OPTIONAL. For laser p= rinters, process monochrome function causes trouble with drums and/or devel= opers. It also can cause a degradation in print quality.=20=20=20 >=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 > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Micha= el Sweet > Sent: Monday, April 09, 2012 8:14 PM > To: > Subject: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS= 3) (April 9 through April 18, 2012) >=20=20 > All, >=20=20 > This message initiates the IPP Working Group last call of the IPP Job and= Printer Extensions - Set 3 (JPS3) specification that has been in extended = development since last year. The latest stable draft can be found here: >=20=20 > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-2012= 0409.docx > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-2012= 0409.pdf > ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-2012= 0409-rev.pdf >=20=20 > Please send all feedback to the IPP mailing list (reply-all works fine fo= r this) and it will be collected and processed as quickly as possible. Our = intent is to move JPS3 to PWG Last Call to span the April 2012 F2F. >=20=20 > Thank you! >=20=20 > ________________________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20=20 >=20 > --=20 > This message has been scanned for viruses and=20 > dangerous content by MailScanner, and is=20 > believed to be clean. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_CyQSI9j44YU+12IEL+fPTw) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable
Xerox has a strong objec= tion to making the value =91process-monochrome=94 REQUIRED for color printe= rs.  We want it changed to OPTIONAL.  For laser printers, process= monochrome function causes trouble with drums and/or developers.  It = also can cause a degradation in print quality.   
 
 
Peter Zehler

Xerox Research Center Webster
Emai= l: Pet= er.Zehler@Xerox.com
Voice: (585)= 265-8755
FAX: (585) 265-7441=
US Mail: Peter Zehler
Xerox Corp.
800 P= hillips Rd.
M/S 128-25E
Webster NY, 14580-9701<= /span>
 
From: ipp-bounces@pwg.or= g [mailto:ipp-bounces= @pwg.org] On Behalf Of=  Michael Sweet
= Sent: Monday, April 0= 9, 2012 8:14 PM
To: <ipp@pwg.org>
Subject: [IPP] WG Last Call - IPP Job and Printer Ext= ensions - Set 3 (JPS3) (April 9 through April 18, 2012)
 
All,
&n= bsp;
This message initiates the IPP Working Group la= st call of the IPP Job and Printer Extensions - Set 3 (JPS3) specification = that has been in extended development since last year. The latest stable dr= aft can be found here:
 
<= /div>
 
Please s= end all feedback to the IPP mailing list (reply-all works fine for this) an= d it will be collected and processed as quickly as possible. Our intent is = to move JPS3 to PWG Last Call to span the April 2012 F2F.
<= /div>
 
Thank you!
 
______= __________________________________________________________________
Michael Sweet, Senior Printing System Enginee= r, PWG Chair
&nb= sp;

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

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_CyQSI9j44YU+12IEL+fPTw)-- --===============1940165842== 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 --===============1940165842==-- From ipp-bounces@pwg.org Thu Apr 19 14:44:33 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F29E711E80D6 for ; Thu, 19 Apr 2012 14:44:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.963 X-Spam-Level: X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.636, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4w5HBMlz4Jp for ; Thu, 19 Apr 2012 14:44:32 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD5111E80D2 for ; Thu, 19 Apr 2012 14:44:32 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id C327E79676; Thu, 19 Apr 2012 17:44:14 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from eagle.jhcloos.com (eagle.jhcloos.com [207.210.242.212]) by pwg.org (Postfix) with ESMTP id 4AC7D7962B for ; Thu, 19 Apr 2012 17:43:57 -0400 (EDT) Received: by eagle.jhcloos.com (Postfix, from userid 10) id 3B1394007A; Thu, 19 Apr 2012 21:43:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jhcloos.com; s=eagle; t=1334871836; bh=D4FpxCp9bqvckTKbyAfuzBKOw6uGlGVFNi5eEz8qMAY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=UEeUyqLgMqdzjO4JhIo80huy486DAGZ13apB/NM6saPi7G9veFqB6C5QeaUUg+GbO 6BRsH2jUUCLfWXErXdUSEPukwF6QPpgQKBtp5cTPIeysCAwMt8P+C2xnxKVg33dBom z37J2RtYAU9fLd0EQZoPALj/PH9hQMDDg3AbtpgU= Received: by carbon.jhcloos.org (Postfix, from userid 500) id 1FE1736004D; Thu, 19 Apr 2012 21:30:50 +0000 (UTC) From: James Cloos To: ipp@pwg.org Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) In-Reply-To: (Michael Sweet's message of "Thu, 19 Apr 2012 10:46:22 -0700") References: User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.1.50 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAABAAAAAQAgMAAABinRfyAAAACVBMVEX///8ZGXBQKKnCrDQ3 AAAAJElEQVQImWNgQAAXzwQg4SKASgAlXIEEiwsSIYBEcLaAtMEAADJnB+kKcKioAAAAAElFTkSu QmCC Copyright: Copyright 2012 James Cloos OpenPGP: ED7DAEA6; url=http://jhcloos.com/public_key/0xED7DAEA6.asc OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 Date: Thu, 19 Apr 2012 17:30:50 -0400 Message-ID: Lines: 8 MIME-Version: 1.0 Content-Type: text/plain X-Hashcash: 1:30:120419:ipp@pwg.org::fjuEo73hrReQ4nh7:00000GNKvX X-Hashcash: 1:30:120419:peter.zehler@xerox.com::m2IWfJlycGvJW+hK:00000000000000000000000000000000000000PP9k8 X-Hashcash: 1:30:120419:msweet@apple.com::mpXxP8hcEn4DntmI:wZ6RB 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: C327E79676.A9186 X-pwg-MailScanner-From: ipp-bounces@pwg.org Apologies for the stupid question, but I couldn't find an explanation.... For a colour printer, what is the difference between monochrome and process-monochome? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Apr 19 17:12:12 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22BA521F855D for ; Thu, 19 Apr 2012 17:12:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.464 X-Spam-Level: X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e2nn6EtoNNV7 for ; Thu, 19 Apr 2012 17:12:11 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3308D21F855B for ; Thu, 19 Apr 2012 17:12:11 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 37AF079682; Thu, 19 Apr 2012 20:11:54 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id DF2837967F for ; Thu, 19 Apr 2012 20:11:34 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2R0022P4J7HNO1@mail-out.apple.com> for ipp@pwg.org; Thu, 19 Apr 2012 17:11:33 -0700 (PDT) X-AuditID: 11807137-b7f536d000006fcc-21-4f90a9b493d8 Received: from [17.151.81.192] (Unknown_Domain [17.151.81.192]) by relay16.apple.com (Apple SCV relay) with SMTP id A0.BB.28620.5B9A09F4; Thu, 19 Apr 2012 17:11:33 -0700 (PDT) Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) From: Michael Sweet In-reply-to: Date: Thu, 19 Apr 2012 17:11:35 -0700 Message-id: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> References: To: James Cloos X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUiOD3wgO7WlRP8Db5u4rW4OHcOm8WxfS9Z LI58i7XoeLKS1YHFY+vJH2welxZvZfWYt3g6k8fyU+vZAliiuGxSUnMyy1KL9O0SuDJOdjay FNxlqbjdvIuxgfEdcxcjB4eEgInEzhPxXYycQKaYxIV769m6GLk4hAQ2Mko0rf/FDJIQFiiQ eLvvHTuIzStgKDHzVTsriM0soCVx499LJhCbTUBN4vekPlaQmZwCBhL/QOZwcrAIqErsWbaA EaLcWuLV7B1QtrbEsoWvmSFG2khM27qYFWLvVUaJtV2PwWaKCChL/P/wjBXiOFmJ2wf3M01g 5J+F5IxZSM6YhWTuAkbmVYyCRak5iZWGZnqJBQU5qXrJ+bmbGEGh2VBovoNx+1+5Q4wCHIxK PLycEhP8hVgTy4orcw8xSnAwK4nwzgcJ8aYkVlalFuXHF5XmpBYfYpTmYFES5xXIBUoJpCeW pGanphakFsFkmTg4pRoYtzjN/HopZnGz+9sKbqsWobiH71n3Os+ZrF96O2Hp9R7uV7zf93Gc k/m0hE2b01NB1rKatezZ+ZiI9dWP9kQ33Ti316Gc3eNr95trf0T082z+7l8x78/Ox/+Wlee/ z7l2alPvtRk6HppvOio8JRk91XexOAlLH5i4h1csiLF45Wae2Uvyt782UWIpzkg01GIuKk4E APgoa1VJAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 37AF079682.A7ECE X-pwg-MailScanner-From: ipp-bounces@pwg.org James, On Apr 19, 2012, at 2:30 PM, James Cloos wrote: > Apologies for the stupid question, but I couldn't find an explanation.... > > For a colour printer, what is the difference between monochrome and > process-monochome? monochrome is black using 1 color (black). process-monochrome is black using many colors (typically black plus varying amounts of cyan, magenta, and yellow, although it can also apply to black from just cyan, magenta, and yellow). _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Apr 19 17:56:18 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25BA011E8073 for ; Thu, 19 Apr 2012 17:56:18 -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=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qnBuV1tgf3sd for ; Thu, 19 Apr 2012 17:56:14 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5000811E80A1 for ; Thu, 19 Apr 2012 17:56:14 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 84BFD79689; Thu, 19 Apr 2012 20:55:52 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by pwg.org (Postfix) with ESMTP id 68B8979688 for ; Thu, 19 Apr 2012 20:55:37 -0400 (EDT) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta15.westchester.pa.mail.comcast.net with comcast id 00jA1j00817dt5G5F0vd4H; Fri, 20 Apr 2012 00:55:37 +0000 Received: from VistaBusiness ([98.216.178.129]) by omta13.westchester.pa.mail.comcast.net with comcast id 00vd1j01M2ntzM63Z0veEc; Fri, 20 Apr 2012 00:55:38 +0000 From: "William Wagner" To: "'Michael Sweet'" , "'James Cloos'" References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> In-Reply-To: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> Subject: RE: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) Date: Thu, 19 Apr 2012 20:55:33 -0400 Message-ID: <004901cd1e90$4aa7d790$dff786b0$@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: Ac0eijxSzZFooY1DTcO/FNtlScFqFQABKsIA Content-Language: en-us X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 84BFD79689.A8804 X-pwg-MailScanner-From: ipp-bounces@pwg.org Michael, My memory might be off, but although the distinction between monochrome and process monochrome as referring to marking with a single colorant versus obtaining that color from multiple colorants is right, I thought that we used the term 'monochrome' rather than just 'black' to refer to one-color printing, where that color was usually but not necessarily black. But perhaps it is an unimportant distinction. Thanks, Bill Wagner -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Thursday, April 19, 2012 8:12 PM To: James Cloos Cc: ipp@pwg.org Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) James, On Apr 19, 2012, at 2:30 PM, James Cloos wrote: > Apologies for the stupid question, but I couldn't find an explanation.... > > For a colour printer, what is the difference between monochrome and > process-monochome? monochrome is black using 1 color (black). process-monochrome is black using many colors (typically black plus varying amounts of cyan, magenta, and yellow, although it can also apply to black from just cyan, magenta, and yellow). _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Apr 19 18:04:21 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7134911E80CE for ; Thu, 19 Apr 2012 18:04:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.478 X-Spam-Level: X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CypCOBJzxIp for ; Thu, 19 Apr 2012 18:04:20 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8337E11E80AA for ; Thu, 19 Apr 2012 18:04:20 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 54C2879690; Thu, 19 Apr 2012 21:04:03 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 9F1C479684 for ; Thu, 19 Apr 2012 21:03:47 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2R00A5K6VZKGZ0@mail-out.apple.com> for ipp@pwg.org; Thu, 19 Apr 2012 18:02:28 -0700 (PDT) X-AuditID: 1180711d-b7f406d000004330-d0-4f90b5a3c373 Received: from [17.151.81.192] (Unknown_Domain [17.151.81.192]) by relay13.apple.com (Apple SCV relay) with SMTP id 72.8F.17200.3A5B09F4; Thu, 19 Apr 2012 18:02:27 -0700 (PDT) Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3) (April 9 through April 18, 2012) From: Michael Sweet In-reply-to: <004901cd1e90$4aa7d790$dff786b0$@net> Date: Thu, 19 Apr 2012 18:02:29 -0700 Message-id: References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> <004901cd1e90$4aa7d790$dff786b0$@net> To: William Wagner X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUiOD3wgO7irRP8DU5/NLe4OHcOm8WxfS9Z LI58i7U4d0HRgcVj68kfbB6TH89h9Li0eCurx7zF05kCWKK4bFJSczLLUov07RK4MvbuWcFU cFegYsHXR0wNjEd5uxg5OSQETCQWLD7MCmGLSVy4t56ti5GLQ0hgI6NEx5v9zCAJYYECibf7 3rGD2LwChhIzX7WDNTALaEnc+PeSCcRmE1CT+D2pDyzOKWAkce7/XDYQm0VAVeLq6mnMEPUm Ev2fG6BsbYllC18D2RxAM20k7vVzQuxdwySxc91EsDkiQPM/PTjOCHGcrMTtg/uZJjDyz0Jy xiwkZ8xCMnYBI/MqRsGi1JzESkNjvcSCgpxUveT83E2MoNBsKJTdwbj/J/8hRgEORiUeXk6J Cf5CrIllxZW5hxglOJiVRHjng4R4UxIrq1KL8uOLSnNSiw8xSnOwKInzcuUCpQTSE0tSs1NT C1KLYLJMHJxSDYyesgHyFgk/LyzZorXg/43ZR1f6H/8hU7koZJ1E0N6VS5ZrM55u/XSIe9Hs P6vNZKfOc+F7c7RHlklr5vltnj7hz7rU2ztcFCWd2lY4TM69HdnNOP3GySmbalaIrPpWd2T+ pu0z1qWtYn1yn2/z8j2v80oUD3TW3rwh3dI4f4b8DcEbDedDts8RVmIpzkg01GIuKk4EAILp G6RJAgAA X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 54C2879690.A9ADC X-pwg-MailScanner-From: ipp-bounces@pwg.org Bill, We do, in fact, define "monochrome" as being 1 colorant, typically black. A vendor might choose to implement an IPP Printer that uses blue ink, for example, but I expect the mainstream usage to be black ink. On Apr 19, 2012, at 5:55 PM, William Wagner wrote: > Michael, > My memory might be off, but although the distinction between monochrome and > process monochrome as referring to marking with a single colorant versus > obtaining that color from multiple colorants is right, I thought that we > used the term 'monochrome' rather than just 'black' to refer to one-color > printing, where that color was usually but not necessarily black. But > perhaps it is an unimportant distinction. > Thanks, > Bill Wagner > > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael > Sweet > Sent: Thursday, April 19, 2012 8:12 PM > To: James Cloos > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 > (JPS3) (April 9 through April 18, 2012) > > James, > > On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >> Apologies for the stupid question, but I couldn't find an explanation.... >> >> For a colour printer, what is the difference between monochrome and >> process-monochome? > > > monochrome is black using 1 color (black). > > process-monochrome is black using many colors (typically black plus varying > amounts of cyan, magenta, and yellow, although it can also apply to black > from just cyan, magenta, and yellow). > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Apr 20 02:39:24 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4409B21F8704 for ; Fri, 20 Apr 2012 02:39:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89QefdVSnniT for ; Fri, 20 Apr 2012 02:39:23 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9DE21F8707 for ; Fri, 20 Apr 2012 02:39:23 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E9A06796A0; Fri, 20 Apr 2012 05:39:02 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from USA7109MR001.ACS-INC.COM (usa7109mr001.acs-inc.com [63.101.151.9]) by pwg.org (Postfix) with ESMTP id 08DCA7969E for ; Fri, 20 Apr 2012 05:38:46 -0400 (EDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApACAN0tkU8NKeYgmWdsb2JhbABAA7E9IgEBAQEBCAsLBxQnggkBAQEDAQEBAQwBIAolDwsFBwQCAQgOAwQBAQEKBgwCBQQBBgEmHwkIAQEEAQ0FCIgCCAimbwGUEgSKcYJMgkdjBIhjoFqBPA Received: from usa7109ht002.na.xerox.net ([13.41.230.32]) by USA7109MR001.ACS-INC.COM with ESMTP/TLS/AES128-SHA; 20 Apr 2012 04:38:46 -0500 Received: from USA0300GW001.na.xerox.net (13.135.209.15) by USA7109HT002.na.xerox.net (13.41.230.32) with Microsoft SMTP Server id 14.1.355.2; Fri, 20 Apr 2012 04:38:45 -0500 Received: from USA7061MS04.na.xerox.net ([13.151.235.15]) by USA0300GW001.na.xerox.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Apr 2012 05:38:44 -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 Subject: RE: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Date: Fri, 20 Apr 2012 02:38:37 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Thread-Index: Ac0ekZM6N/r1KoRWSVe8JLxy5trBhwAR1ENA References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com><004901cd1e90$4aa7d790$dff786b0$@net> From: "Zehler, Peter" To: Michael Sweet , William Wagner X-OriginalArrivalTime: 20 Apr 2012 09:38:44.0964 (UTC) FILETIME=[611D0240:01CD1ED9] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: E9A06796A0.A9008 X-pwg-MailScanner-From: ipp-bounces@pwg.org Perhaps the description of 'process-monochrome' and 'process-bi-level' could include the clarification "(more than 1 colorant)". 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 Michael Sweet Sent: Thursday, April 19, 2012 9:02 PM To: William Wagner Cc: ipp@pwg.org Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Bill, We do, in fact, define "monochrome" as being 1 colorant, typically black. A vendor might choose to implement an IPP Printer that uses blue ink, for example, but I expect the mainstream usage to be black ink. On Apr 19, 2012, at 5:55 PM, William Wagner wrote: > Michael, > My memory might be off, but although the distinction between=20 > monochrome and process monochrome as referring to marking with a=20 > single colorant versus obtaining that color from multiple colorants is > right, I thought that we used the term 'monochrome' rather than just=20 > 'black' to refer to one-color printing, where that color was usually=20 > but not necessarily black. But perhaps it is an unimportant distinction. > Thanks, > Bill Wagner >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of=20 > Michael Sweet > Sent: Thursday, April 19, 2012 8:12 PM > To: James Cloos > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set > 3 > (JPS3) (April 9 through April 18, 2012) >=20 > James, >=20 > On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >> Apologies for the stupid question, but I couldn't find an explanation.... >>=20 >> For a colour printer, what is the difference between monochrome and=20 >> process-monochome? >=20 >=20 > monochrome is black using 1 color (black). >=20 > process-monochrome is black using many colors (typically black plus=20 > varying amounts of cyan, magenta, and yellow, although it can also=20 > apply to black from just cyan, magenta, and yellow). >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 > -- > This message has been scanned for viruses and dangerous content by=20 > MailScanner, and is believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Apr 20 07:40:04 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6953121F872B for ; Fri, 20 Apr 2012 07:40:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aesS5lwtY2qo for ; Fri, 20 Apr 2012 07:40:03 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id B263921F872A for ; Fri, 20 Apr 2012 07:40:02 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 99501796AF; Fri, 20 Apr 2012 10:39:43 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 3F715796AE for ; Fri, 20 Apr 2012 10:39:26 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2S00F738OVYJP0@mail-out.apple.com> for ipp@pwg.org; Fri, 20 Apr 2012 07:39:25 -0700 (PDT) X-AuditID: 1180711d-b7f406d000004330-5d-4f91751caa9a Received: from [17.113.0.252] (Unknown_Domain [17.113.0.252]) by relay13.apple.com (Apple SCV relay) with SMTP id 8D.A3.17200.C15719F4; Fri, 20 Apr 2012 07:39:25 -0700 (PDT) References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> <004901cd1e90$4aa7d790$dff786b0$@net> In-reply-to: Message-id: <7E19F654-28E8-43A2-83FF-1B72BF2C2D24@apple.com> X-Mailer: iPhone Mail (9B176) From: Michael R Sweet Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Date: Fri, 20 Apr 2012 07:39:20 -0700 To: "Zehler, Peter" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrILMWRmVeSWpSXmKPExsUiWMjwR1e2dKK/QetkJYtj+16yWBz5FmvR 8WQlq8W5C4oOLB5bT/5g85j8eA6jx7zF05k8lp9azxbAEsVlk5Kak1mWWqRvl8CV8W/KN/aC Y5IVSz43MjUw7hHpYuTkkBAwkWg5eJEdwhaTuHBvPRuILSSwnlFiw8RUCHshs8SbjhwQm1Mg QOL2zDksXYwcHLwC4hJXD/qAmMwCOhKTFzKCVPAK2Ei83LMYbCKzgLzE9rdzmCFsd4mvnaeY ITbJSpz60cEKYrMJaEhsebgBbKuwQL7E7Q9/WEBsFgFViafdj5hAbBGg8Rsf7meewMg/C2Hx LITFs5AsW8DIvIpRsCg1J7HS0FgvsaAgJ1UvOT93EyMoIBsKZXcw7v/Jf4hRgINRiYeXU2KC vxBrYllxZe4hRgkOZiUR3pM5E/2FeFMSK6tSi/Lji0pzUosPMUpzsCiJ83LlAlULpCeWpGan phakFsFkmTg4pRoYs6KnrXumkGhdJSz2eOYtG3GO+gaRtbt7erKX3G9lbT7002VH9Y6CfMeA b9+/HXG8476TT/D5ar/ZvXd3pZpNb/3nM+fOWgM+L84AMV1utT1e/3eHM4VkT3u587voMund T/V7JJc9e7PPaKW5eHacJEdG7MS32U9DN7rLpnw+slS+0HJW6MkAJZbijERDLeai4kQAlFwc N0QCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: "ipp@pwg.org" X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 99501796AF.A986B X-pwg-MailScanner-From: ipp-bounces@pwg.org Works for me! Sent from my iPhone On Apr 20, 2012, at 2:38 AM, "Zehler, Peter" wrote: > Perhaps the description of 'process-monochrome' and 'process-bi-level' > could include the clarification "(more than 1 colorant)". > > > 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 > Michael Sweet > Sent: Thursday, April 19, 2012 9:02 PM > To: William Wagner > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 > (JPS3)(April 9 through April 18, 2012) > > Bill, > > We do, in fact, define "monochrome" as being 1 colorant, typically > black. A vendor might choose to implement an IPP Printer that uses blue > ink, for example, but I expect the mainstream usage to be black ink. > > > On Apr 19, 2012, at 5:55 PM, William Wagner wrote: > >> Michael, >> My memory might be off, but although the distinction between >> monochrome and process monochrome as referring to marking with a >> single colorant versus obtaining that color from multiple colorants is > >> right, I thought that we used the term 'monochrome' rather than just >> 'black' to refer to one-color printing, where that color was usually >> but not necessarily black. But perhaps it is an unimportant > distinction. >> Thanks, >> Bill Wagner >> >> -----Original Message----- >> From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of >> Michael Sweet >> Sent: Thursday, April 19, 2012 8:12 PM >> To: James Cloos >> Cc: ipp@pwg.org >> Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set > >> 3 >> (JPS3) (April 9 through April 18, 2012) >> >> James, >> >> On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >>> Apologies for the stupid question, but I couldn't find an > explanation.... >>> >>> For a colour printer, what is the difference between monochrome and >>> process-monochome? >> >> >> monochrome is black using 1 color (black). >> >> process-monochrome is black using many colors (typically black plus >> varying amounts of cyan, magenta, and yellow, although it can also >> apply to black from just cyan, magenta, and yellow). >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer, PWG Chair >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Apr 20 08:05:34 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7184E21F8780 for ; Fri, 20 Apr 2012 08:05:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.401 X-Spam-Level: X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_00=-2.599, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUkUw1F12AU1 for ; Fri, 20 Apr 2012 08:05:33 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 93F3C21F876D for ; Fri, 20 Apr 2012 08:05:33 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 8EB22796B5; Fri, 20 Apr 2012 11:05:15 -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 26FC6796B2 for ; Fri, 20 Apr 2012 11:04:59 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Apr 2012 08:05: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] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Date: Fri, 20 Apr 2012 08:04:58 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Thread-Index: Ac0ekYb3f/EC4Dg5T56t6/Bz/8xiBwAcbK2Q References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com><004901cd1e90$4aa7d790$dff786b0$@net> From: "Petrie, Glen" To: "Michael Sweet" , "William Wagner" X-OriginalArrivalTime: 20 Apr 2012 15:05:00.0767 (UTC) FILETIME=[F5337EF0:01CD1F06] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 8EB22796B5.A907A X-pwg-MailScanner-From: ipp-bounces@pwg.org Monochrome is defined as "the range of shades of a single Color to white" and not a single colorant and not just black.=20=20=20 In the days when we have just black/white printers, monochrome came to mean half-tone printing using the black colorant only; which is really binary printing (one colorant and the white of the media) using halftone technques to simulate the color "gray" (shading) versus true monochrome printing that prints using various shades of the actual color gray. Today, """"Black"""" monochrome printing is printing the color gray over the range from black to white. Since gray is produced using all colorants, it is processed-monochrome that is important. Another common case of actually monochrome is Sepia. The color sepia is not a single colorant but a single composite color (a combination of rgb).=20=20=20 So if you want a definition using a single colorant, then this binary printing using halftoning to simulation "shades" (intensity variations of the colorant). =20 Glen =20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Thursday, April 19, 2012 6:02 PM To: William Wagner Cc: ipp@pwg.org Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Bill, We do, in fact, define "monochrome" as being 1 colorant, typically black. A vendor might choose to implement an IPP Printer that uses blue ink, for example, but I expect the mainstream usage to be black ink. On Apr 19, 2012, at 5:55 PM, William Wagner wrote: > Michael, > My memory might be off, but although the distinction between monochrome and > process monochrome as referring to marking with a single colorant versus > obtaining that color from multiple colorants is right, I thought that we > used the term 'monochrome' rather than just 'black' to refer to one-color > printing, where that color was usually but not necessarily black. But > perhaps it is an unimportant distinction. > Thanks, > Bill Wagner >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael > Sweet > Sent: Thursday, April 19, 2012 8:12 PM > To: James Cloos > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 > (JPS3) (April 9 through April 18, 2012) >=20 > James, >=20 > On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >> Apologies for the stupid question, but I couldn't find an explanation.... >>=20 >> For a colour printer, what is the difference between monochrome and=20 >> process-monochome? >=20 >=20 > monochrome is black using 1 color (black). >=20 > process-monochrome is black using many colors (typically black plus varying > amounts of cyan, magenta, and yellow, although it can also apply to black > from just cyan, magenta, and yellow). >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=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 --=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 Fri Apr 20 08:17:44 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D8021F87A0 for ; Fri, 20 Apr 2012 08:17:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.361 X-Spam-Level: X-Spam-Status: No, score=-1.361 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJETCRNfXakF for ; Fri, 20 Apr 2012 08:17:43 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id BE4CD21F878B for ; Fri, 20 Apr 2012 08:17:43 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5F35A796BA; Fri, 20 Apr 2012 11:17:23 -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 C28A779693 for ; Fri, 20 Apr 2012 11:17:04 -0400 (EDT) Received: from EEAEX02.us.epson.net ([148.130.64.7]) by EEAEX01.us.epson.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Apr 2012 08:17:05 -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] WG Last Call - IPP Job and Printer Extensions - Set 3(JPS3)(April 9 through April 18, 2012) Date: Fri, 20 Apr 2012 08:17:04 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3(JPS3)(April 9 through April 18, 2012) Thread-Index: Ac0ekYb3f/EC4Dg5T56t6/Bz/8xiBwAcbK2QAAFN7kA= References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com><004901cd1e90$4aa7d790$dff786b0$@net> From: "Petrie, Glen" To: "Petrie, Glen" , "Michael Sweet" , "William Wagner" X-OriginalArrivalTime: 20 Apr 2012 15:17:05.0675 (UTC) FILETIME=[A547ADB0:01CD1F08] X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 5F35A796BA.A8DEA X-pwg-MailScanner-From: ipp-bounces@pwg.org In fact, I believe we should introduce a new term Color Printing Mono-Chrome Printing Mono-Colorant Printing B/W-Printing This is much clearer=20 Glen -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Petrie, Glen Sent: Friday, April 20, 2012 8:05 AM To: Michael Sweet; William Wagner Cc: ipp@pwg.org Subject: RE: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3(JPS3)(April 9 through April 18, 2012) Monochrome is defined as "the range of shades of a single Color to white" and not a single colorant and not just black.=20=20=20 In the days when we have just black/white printers, monochrome came to mean half-tone printing using the black colorant only; which is really binary printing (one colorant and the white of the media) using halftone technques to simulate the color "gray" (shading) versus true monochrome printing that prints using various shades of the actual color gray. Today, """"Black"""" monochrome printing is printing the color gray over the range from black to white. Since gray is produced using all colorants, it is processed-monochrome that is important. Another common case of actually monochrome is Sepia. The color sepia is not a single colorant but a single composite color (a combination of rgb).=20=20=20 So if you want a definition using a single colorant, then this binary printing using halftoning to simulation "shades" (intensity variations of the colorant). =20 Glen =20 -----Original Message----- From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael Sweet Sent: Thursday, April 19, 2012 6:02 PM To: William Wagner Cc: ipp@pwg.org Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) Bill, We do, in fact, define "monochrome" as being 1 colorant, typically black. A vendor might choose to implement an IPP Printer that uses blue ink, for example, but I expect the mainstream usage to be black ink. On Apr 19, 2012, at 5:55 PM, William Wagner wrote: > Michael, > My memory might be off, but although the distinction between monochrome and > process monochrome as referring to marking with a single colorant versus > obtaining that color from multiple colorants is right, I thought that we > used the term 'monochrome' rather than just 'black' to refer to one-color > printing, where that color was usually but not necessarily black. But > perhaps it is an unimportant distinction. > Thanks, > Bill Wagner >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of Michael > Sweet > Sent: Thursday, April 19, 2012 8:12 PM > To: James Cloos > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 > (JPS3) (April 9 through April 18, 2012) >=20 > James, >=20 > On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >> Apologies for the stupid question, but I couldn't find an explanation.... >>=20 >> For a colour printer, what is the difference between monochrome and=20 >> process-monochome? >=20 >=20 > monochrome is black using 1 color (black). >=20 > process-monochrome is black using many colors (typically black plus varying > amounts of cyan, magenta, and yellow, although it can also apply to black > from just cyan, magenta, and yellow). >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=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 --=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 Fri Apr 20 08:43:54 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D47721F87AE for ; Fri, 20 Apr 2012 08:43:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, WEIRD_QUOTING=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqR8WFipGWfr for ; Fri, 20 Apr 2012 08:43:53 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 715CF21F87A2 for ; Fri, 20 Apr 2012 08:43:53 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 1BF57796C3; Fri, 20 Apr 2012 11:43:34 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by pwg.org (Postfix) with ESMTP id 8A358796C2 for ; Fri, 20 Apr 2012 11:43:16 -0400 (EDT) Received: from cm-omr14 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3KFhCOD015263 for ; Fri, 20 Apr 2012 11:43:12 -0400 Authentication-Results: cm-omr14 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5) X-Authenticated-UID: rturner@amalfisystems.com Received: from [98.151.18.90] ([98.151.18.90:51140] helo=[192.168.1.114]) by cm-omr14 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA) id 6F/1C-22702-014819F4; Fri, 20 Apr 2012 11:43:12 -0400 Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3(JPS3)(April 9 through April 18, 2012) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Randy Turner In-Reply-To: Date: Fri, 20 Apr 2012 08:43:17 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com><004901cd1e90$4aa7d790$dff786b0$@net> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1257) X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 1BF57796C3.A8DBB X-pwg-MailScanner-From: ipp-bounces@pwg.org Amazing, I can remember this argument in 1993/1994 when we were working on = the Printer MIB=85 I guess there are some questions which will never have a definitive answer= =85 :) R. On Apr 20, 2012, at 8:17 AM, Petrie, Glen wrote: > In fact, I believe we should introduce a new term >=20 > Color Printing > Mono-Chrome Printing > Mono-Colorant Printing > B/W-Printing >=20 > This is much clearer=20 >=20 > Glen >=20 >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of > Petrie, Glen > Sent: Friday, April 20, 2012 8:05 AM > To: Michael Sweet; William Wagner > Cc: ipp@pwg.org > Subject: RE: [IPP] WG Last Call - IPP Job and Printer Extensions - Set > 3(JPS3)(April 9 through April 18, 2012) >=20 > Monochrome is defined as "the range of shades of a single Color to > white" and not a single colorant and not just black.=20=20=20 >=20 > In the days when we have just black/white printers, monochrome came to > mean half-tone printing using the black colorant only; which is really > binary printing (one colorant and the white of the media) using halftone > technques to simulate the color "gray" (shading) versus true monochrome > printing that prints using various shades of the actual color gray. >=20 > Today, """"Black"""" monochrome printing is printing the color gray over > the range from black to white. Since gray is produced using all > colorants, it is processed-monochrome that is important. >=20 > Another common case of actually monochrome is Sepia. The color sepia > is not a single colorant but a single composite color (a combination of > rgb).=20=20=20 >=20 > So if you want a definition using a single colorant, then this binary > printing using halftoning to simulation "shades" (intensity variations > of the colorant). >=20 > Glen >=20 >=20 >=20 >=20 > -----Original Message----- > From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of > Michael Sweet > Sent: Thursday, April 19, 2012 6:02 PM > To: William Wagner > Cc: ipp@pwg.org > Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 > (JPS3)(April 9 through April 18, 2012) >=20 > Bill, >=20 > We do, in fact, define "monochrome" as being 1 colorant, typically > black. A vendor might choose to implement an IPP Printer that uses blue > ink, for example, but I expect the mainstream usage to be black ink. >=20 >=20 > On Apr 19, 2012, at 5:55 PM, William Wagner wrote: >=20 >> Michael, >> My memory might be off, but although the distinction between > monochrome and >> process monochrome as referring to marking with a single colorant > versus >> obtaining that color from multiple colorants is right, I thought that > we >> used the term 'monochrome' rather than just 'black' to refer to > one-color >> printing, where that color was usually but not necessarily black. But >> perhaps it is an unimportant distinction. >> Thanks, >> Bill Wagner >>=20 >> -----Original Message----- >> From: ipp-bounces@pwg.org [mailto:ipp-bounces@pwg.org] On Behalf Of > Michael >> Sweet >> Sent: Thursday, April 19, 2012 8:12 PM >> To: James Cloos >> Cc: ipp@pwg.org >> Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set > 3 >> (JPS3) (April 9 through April 18, 2012) >>=20 >> James, >>=20 >> On Apr 19, 2012, at 2:30 PM, James Cloos wrote: >>> Apologies for the stupid question, but I couldn't find an > explanation.... >>>=20 >>> For a colour printer, what is the difference between monochrome and=20 >>> process-monochome? >>=20 >>=20 >> monochrome is black using 1 color (black). >>=20 >> process-monochrome is black using many colors (typically black plus > varying >> amounts of cyan, magenta, and yellow, although it can also apply to > black >> from just cyan, magenta, and yellow). >>=20 >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer, PWG Chair >>=20 >>=20 >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >>=20 >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >>=20 >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer, PWG Chair >=20 >=20 > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 > --=20 > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 --=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 Fri Apr 20 09:37:48 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E89421F85D0 for ; Fri, 20 Apr 2012 09:37:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.454 X-Spam-Level: X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aDuFUowlVy4g for ; Fri, 20 Apr 2012 09:37:47 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 22F3E21F8631 for ; Fri, 20 Apr 2012 09:37:47 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 62E6D796C7; Fri, 20 Apr 2012 12:37:30 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 69646796C6 for ; Fri, 20 Apr 2012 12:37:15 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2S00F2RE55YJF1@mail-out.apple.com> for ipp@pwg.org; Fri, 20 Apr 2012 09:37:14 -0700 (PDT) X-AuditID: 1180711d-b7f406d000004330-72-4f9190bad0e1 Received: from da0704a-dhcp86.apple.com (da0704a-dhcp86.apple.com [17.197.43.86]) by relay13.apple.com (Apple SCV relay) with SMTP id BD.DB.17200.AB0919F4; Fri, 20 Apr 2012 09:37:14 -0700 (PDT) Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3 (JPS3)(April 9 through April 18, 2012) From: Michael Sweet In-reply-to: Date: Fri, 20 Apr 2012 09:37:19 -0700 Message-id: References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> <004901cd1e90$4aa7d790$dff786b0$@net> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOLMWRmVeSWpSXmKPExsUieFQ7THfXhIn+BnM261psP/uLxeLYvpcs Fke+xVqcu6DowOKx9eQPNo/Jj+cwehycP4vdY97i6UwBLFFcNimpOZllqUX6dglcGd82vWQt +MhecenVb/YGxl1sXYycHBICJhKzNrWxQ9hiEhfurQeKc3EICRxmlFjWu4UJJCEskC9x+8Mf FhCbV8BQYuardlYQm1lAS+LGv5dgNWwCahK/J/WBxTkFvCQu37sKNpRFQFXiUfd5Zoh6S4nj nzvZIWxtiWULXzNDzLSR+L+mmwli8Wxmibl334ENFRHQl/j0cTMTxHWyErcP7meawMg/C8kd s5DcMQvJ3AWMzKsYBYtScxIrDY31EgsKclL1kvNzNzGCgrOhUHYH4/6f/IcYBTgYlXh4V7VO 9BdiTSwrrsw9xCjBwawkwnsyByjEm5JYWZValB9fVJqTWnyIUZqDRUmclyt3gr+QQHpiSWp2 ampBahFMlomDU6qBUVhfvo1l0RR5jX/aSkq8jZnrLGfZNGxfHhacFbyxIdxY50D/lxmnpPWm Ni6Lmhv7LYmj8vuddQL7jUymb20OqlqnWLfgaa1leYyvtXfFt1dnGH69OFr5b/OFL24xIot6 +TpE2APa334KPvTT/Lf1foYtT10ubmrWfaO886Jay1ZLZ9uarstpSizFGYmGWsxFxYkAiZMA nUoCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 62E6D796C7.A99EC X-pwg-MailScanner-From: ipp-bounces@pwg.org Glen, On Apr 20, 2012, at 8:04 AM, Petrie, Glen wrote: > Monochrome is defined as "the range of shades of a single Color to > white" and not a single colorant and not just black. As defined in JPS3, monochrome is output using a single colorant. This was the definition that everyone agreed to 2 years ago after hours of discussion at the December 2010 F2F. "process-monochrome" was added at that meeting to address the many use cases where a vendor might want to use multiple colorants to produce a single color - typically black but it could be any color/effect. Further definition/clarification about halftoning and continuous tone printing was deemed too implementation-specific to be added - the compromise was to add bi-level and process-bi-level for threshold output with monochrome and process-monochrome mapping to grayscale/shaded output. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Apr 20 09:39:54 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F30CB21F85C5 for ; Fri, 20 Apr 2012 09:39:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.469 X-Spam-Level: X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrpX3nIVGvmg for ; Fri, 20 Apr 2012 09:39:53 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5F74C21F85C4 for ; Fri, 20 Apr 2012 09:39:53 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 5D455796D1; Fri, 20 Apr 2012 12:39:23 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id B7BA5796EC for ; Fri, 20 Apr 2012 12:38:52 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2S00EN7E7P3WE2@mail-out.apple.com> for ipp@pwg.org; Fri, 20 Apr 2012 09:38:52 -0700 (PDT) X-AuditID: 11807112-b7f826d000004103-85-4f91911c903e Received: from da0704a-dhcp86.apple.com (da0704a-dhcp86.apple.com [17.197.43.86]) by relay17.apple.com (Apple SCV relay) with SMTP id 1D.9B.16643.C11919F4; Fri, 20 Apr 2012 09:38:52 -0700 (PDT) Subject: Re: [IPP] WG Last Call - IPP Job and Printer Extensions - Set 3(JPS3)(April 9 through April 18, 2012) From: Michael Sweet In-reply-to: Date: Fri, 20 Apr 2012 09:38:57 -0700 Message-id: <5D6155CD-C040-4945-9504-B7EDBDB0D986@apple.com> References: <459719E9-EED5-41F1-9048-CA6BF479EFD8@apple.com> <004901cd1e90$4aa7d790$dff786b0$@net> To: "Petrie, Glen" X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUieFQ7TFdm4kR/g5cL2S22n/3FYnFs30sW iyPfYi3OXVB0YPHYevIHm8fkx3MYPQ7On8XuMW/xdKYAligum5TUnMyy1CJ9uwSujN0nulgL 5jBX3Pp9nbWB8QRTFyMnh4SAicTN9b9ZIWwxiQv31rN1MXJxCAkcZpS4/PUucxcjB4ewQJ5E 82IJkBpeAUOJma/aweqZBbQkbvx7CTaHTUBN4vekPlaQck4BL4mdZx1AwiwCqhJLWrczQ5Rb Shz/3MkOYctLbH87hxlipI3E7PfTGSHW3mSW2DxlFyNIQkRAX+LTx81Qd8pK3D64n2kCI/8s JGfMQnLGLCRzFzAyr2IULErNSaw0NNdLLCjISdVLzs/dxAgKzIZCoR2M93fpHWIU4GBU4uEN bJ7oL8SaWFZcmXuIUYKDWUmE92QOUIg3JbGyKrUoP76oNCe1+BCjNAeLkjivYO4EfyGB9MSS 1OzU1ILUIpgsEwenVAOjzxz7g3+PHWFd1TbFP0j6xl075vv6aXrxP903s59UubmiQCmc5Vtm /k3j7ZJ7uW9MfdvhwjzJTl87SHvimmrvOeorXBTO/Ne832NQ93YF66yL9ckB8d2KG203d32Y dfI438tT2q28mnMVV58/edlR5lxAS9ZL38MP4rT9btxbx/mwtzp0vqaDEktxRqKhFnNRcSIA 6HcpxEgCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Cc: ipp@pwg.org X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipp-bounces@pwg.org Errors-To: ipp-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: 5D455796D1.A98C8 X-pwg-MailScanner-From: ipp-bounces@pwg.org Glen, On Apr 20, 2012, at 8:17 AM, Petrie, Glen wrote: > In fact, I believe we should introduce a new term > > Color Printing > Mono-Chrome Printing > Mono-Colorant Printing > B/W-Printing > > This is much clearer It wasn't clearer when this was brought up 2 years ago... _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From pwg-announce-bounces@pwg.org Fri Apr 20 11:05:52 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F53921F859F for ; Fri, 20 Apr 2012 11:05:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.48 X-Spam-Level: X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfxXvh+tTAeQ for ; Fri, 20 Apr 2012 11:05:50 -0700 (PDT) Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id D00E321F8598 for ; Fri, 20 Apr 2012 11:05:49 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id F0CEE796D4; Fri, 20 Apr 2012 14:05:29 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by pwg.org (Postfix) with ESMTP id 3F5C7796D1 for ; Fri, 20 Apr 2012 14:05:12 -0400 (EDT) MIME-version: 1.0 Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0M2S00GEWI5WJA40@mail-out.apple.com> for pwg-announce@pwg.org; Fri, 20 Apr 2012 11:05:11 -0700 (PDT) X-AuditID: 1180711d-b7f406d000004330-8b-4f91a557088c Received: from da0704a-dhcp86.apple.com (da0704a-dhcp86.apple.com [17.197.43.86]) by relay13.apple.com (Apple SCV relay) with SMTP id 87.31.17200.755A19F4; Fri, 20 Apr 2012 11:05:11 -0700 (PDT) From: Michael Sweet Date: Fri, 20 Apr 2012 11:05:16 -0700 To: pwg-announce@pwg.org Message-id: X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUieFQ7TDd86UR/g/OzxS2OfIu1WNe6mtmB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgyjj8/BxzwQTxilv3NjE2MD4W6WLk5JAQMJFY vq6FHcIWk7hwbz1bFyMXh5DAYUaJjrXzwRJsAmoSvyf1sYLYzAIJEv9erwaLswioSrR1TWEE sYUF7CV+bToFZosISEhM654HVs8rYCNx9+hxFgjbUGLmq3ZWiGWyErcP7meawMg9C8nYWUjK IOLaEssWvmaexcgBZOtITF7IiCoMYX88f4RpASPbKkbBotScxEpDY73EgoKcVL3k/NxNjKDQ aiiU3cG4/yf/IUYBDkYlHt5VrRP9hVgTy4orcw8xSnAwK4nwnp4EFOJNSaysSi3Kjy8qzUkt PsQozcGiJM7LlTvBX0ggPbEkNTs1tSC1CCbLxMEp1cDYuajIzn7K25CDVk8XsnzcN9/szM1f Td1OmzeVP9foPfOpNXDu3dV8l2fFuP94//3gwZBzcrV96/JWRl6pfDbFijU0YSVrsvDmEzs+ Lu3Ju6Jcu31e1C4nkydWt4948rQ78B854pUoN22q+fm7ZziElGeZFjIqVT+LtZPZuCrF7lvO sgvNbgaWSizFGYmGWsxFxYkAahlWoykCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG Candidate Standard 5102.4-2012 - PWG Raster Format 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="===============0433799923==" 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: F0CEE796D4.ACA6E X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org --===============0433799923== Content-type: multipart/alternative; boundary="Boundary_(ID_iN3n0mbRyuhTPA3KiiM7Vg)" --Boundary_(ID_iN3n0mbRyuhTPA3KiiM7Vg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, The PWG Candidate Standard 5102.4-2012 - PWG Raster Format was recently approved. It is now available at: http://www.cups.org/standards.html and: ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippraster10-20120420-5102.4.pdf _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_iN3n0mbRyuhTPA3KiiM7Vg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

Th= e PWG Candidate Standard 5102.4-2012 - PWG Raster Format was recently appro= ved. It is now available at:


=
and:


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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_iN3n0mbRyuhTPA3KiiM7Vg)-- --===============0433799923== 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 --===============0433799923==-- From ipp-bounces@pwg.org Fri Apr 20 11:52:28 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA4621F8624 for ; Fri, 20 Apr 2012 11:52:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.49 X-Spam-Level: X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTzuveDvBNzF for ; Fri, 20 Apr 2012 11:52:22 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 123F521F8659 for ; Fri, 20 Apr 2012 11:52:22 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id 0B4A6796DE; Fri, 20 Apr 2012 14:51:59 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by pwg.org (Postfix) with ESMTP id 9D262796CA for ; Fri, 20 Apr 2012 14:51:40 -0400 (EDT) MIME-version: 1.0 Received: from relay17.apple.com ([17.128.113.18]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2S00FS7KBZYJS1@mail-out.apple.com> for ipp@pwg.org; Fri, 20 Apr 2012 11:51:37 -0700 (PDT) X-AuditID: 11807112-b7f826d000004103-3d-4f91b038f363 Received: from da0704a-dhcp86.apple.com (da0704a-dhcp86.apple.com [17.197.43.86]) by relay17.apple.com (Apple SCV relay) with SMTP id BA.F1.16643.830B19F4; Fri, 20 Apr 2012 11:51:36 -0700 (PDT) From: Michael Sweet Date: Fri, 20 Apr 2012 11:51:42 -0700 To: ipp@pwg.org Message-id: <7B6FF45A-535F-4746-99C9-795DD8D49016@apple.com> X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUieFQ7TNdiw0R/g+vHLS2O7XvJYnHkW6wD k8fWkz/YPOYtns4UwBTFZZOSmpNZllqkb5fAlTGjYwFbQZ90xebnx5gbGLdIdDFyckgImEhM ffWRDcIWk7hwbz2QzcUhJHCYUWLTutXMIAk2ATWJ35P6WEFsZoEEiQlnOhlBbBYBVYl/H7cw gdjCAr4ST143s4DYIgL8EhMvQtTzCthIHF7bwwJhG0rMfNXOCrFMVuL2wf1MExi5ZyEZOwtJ GURcW2LZwtfMsxg5gGwdickLGVGFIeyP548wLWBkW8UoWJSak1hpaK6XWFCQk6qXnJ+7iREU Wg2FQjsY7+/SO8QowMGoxMMb2DzRX4g1say4MvcQowQHs5II7+lJQCHelMTKqtSi/Pii0pzU 4kOM0hwsSuK8grkT/IUE0hNLUrNTUwtSi2CyTBycUg2Myi0n+E05nbra2tNM/0UfncUUubax Lv5n5NFXR24u0dhVmtQYdUarSsxd86XVjiTf3RcaskujYqIUmy6y/li6vY/z0vGTKpsdM5Tt z7ycdbFMunrxKWuuHuW4H50/buR8NNqm2b7+aUWNFfeE2cmbq37odU6QPjjxP8O6Bz8+bK85 vy4vyZJFiaU4I9FQi7moOBEAWoGHgSkCAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [IPP] Stable draft of IPP Job and Printer Extensions - Set 3 (JPS3) posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Internet Printing Protocol \(current\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1332057988==" 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: 0B4A6796DE.A99B3 X-pwg-MailScanner-From: ipp-bounces@pwg.org --===============1332057988== Content-type: multipart/alternative; boundary="Boundary_(ID_jq29J9jv934Ko5FoKkXGXw)" --Boundary_(ID_jq29J9jv934Ko5FoKkXGXw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, I have posted a stable draft of the IPP Job and Printer Extensions - Set 3 (JPS3) to: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420.pdf ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420-rev.pdf This version will shortly go to PWG Last Call. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Boundary_(ID_jq29J9jv934Ko5FoKkXGXw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

I = have posted a stable draft of the IPP Job and Printer Extensions - Set 3 (J= PS3) to:

<= a href=3D"ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420= -rev.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420= -rev.pdf

This version will shortly go to= PWG Last Call.

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


--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. --Boundary_(ID_jq29J9jv934Ko5FoKkXGXw)-- --===============1332057988== 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 --===============1332057988==-- From pwg-announce-bounces@pwg.org Fri Apr 20 12:01:48 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62EF21F85AF for ; Fri, 20 Apr 2012 12:01:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.499 X-Spam-Level: X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7MZBq1o67iD for ; Fri, 20 Apr 2012 12:01:48 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id E1BBA21F8568 for ; Fri, 20 Apr 2012 12:01:46 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E2E607975B; Fri, 20 Apr 2012 14:59:57 -0400 (EDT) X-Original-To: pwg-announce@pwg.org Delivered-To: pwg-announce@pwg.org Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by pwg.org (Postfix) with ESMTP id 1723A796A1 for ; Fri, 20 Apr 2012 14:58:40 -0400 (EDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0M2S00EVVKPSCXI0@mail-out.apple.com> for pwg-announce@pwg.org; Fri, 20 Apr 2012 11:58:40 -0700 (PDT) X-AuditID: 11807136-b7f516d000003f9b-1a-4f91b1e092c2 Received: from da0704a-dhcp86.apple.com (da0704a-dhcp86.apple.com [17.197.43.86]) by relay15.apple.com (Apple SCV relay) with SMTP id 7E.A5.16283.0E1B19F4; Fri, 20 Apr 2012 11:58:40 -0700 (PDT) From: Michael Sweet Date: Fri, 20 Apr 2012 11:58:45 -0700 To: pwg-announce@pwg.org Message-id: X-Mailer: Apple Mail (2.1257) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPJMWRmVeSWpSXmKPExsUieFQ7TPfBxon+BtvbRCyOfIu1WNe6mtmB yWPryR9sHvMWT2cKYIrisklJzcksSy3St0vgypj++BtLwVL+ijUXvzI3MK7l6WLk5JAQMJE4 2v2MDcIWk7hwbz2QzcUhJHCYUaLz5212kASbgJrE70l9rCA2s4CWxI1/L5kgbG2JZQtfM4PY LAKqEtd29oPVCAvESDyYuh6sV0RAQmJa9zywOK+AjcTbY5MYIWxDiZmv2lkhFstK3D64n2kC I88sJCtmIVkxC0nLAkbmVYyCRak5iZWGpnqJBQU5qXrJ+bmbGEHB0lBotoNxx1+5Q4wCHIxK PLyBzRP9hVgTy4orcw8xSnAwK4nwnp4EFOJNSaysSi3Kjy8qzUktPsQozcGiJM7LnzvBX0gg PbEkNTs1tSC1CCbLxMEp1cBY5KKy8PXTg+wbBLSEqp9+jFmmUvlH0oHJ/N7Prt4Vr9tLhKd+ 3GlS8Czo+/L5rZnzbjUyLP9/ZdWJDfanyzP5o95HTF1TqSzF47zFc73GC/9j07Qyz7Em/bk0 eW49/6SgHZx6bbwr/x2r2Fxb7OX1pmHZQ+1lTseefXPhMv/HnC86xdU2/7qnEktxRqKhFnNR cSIAh3gxhhICAAA= X-pwg-MailScanner: Found to be clean, Found to be clean Subject: [Pwg-Announce] PWG Last Call of IPP Job and Printer Extensions - Set 3 (JPS3) (4/20/12 to 5/18/12) X-BeenThere: pwg-announce@pwg.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Printer Working Group Announcement List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: pwg-announce-bounces@pwg.org Errors-To: pwg-announce-bounces@pwg.org X-pwg-MailScanner-Information: Please contact the ISP for more information X-pwg-MailScanner-ID: E2E607975B.AC299 X-pwg-MailScanner-From: pwg-announce-bounces@pwg.org All, [This PWG Last Call starts today Friday April 20, 2012 and ends Friday April 18, 2012 at 10pm US PST.] This is the formal announcement of the PWG Last Call for the IPP Job and Printer Extensions - Set 3 (JPS3) specification, located at: ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120420.pdf All required attributes and values defined in this document have been prototyped by Apple and/or other vendors. The IPP WG has completed extensive review of the various revisions of this document and an IPP WG last call. The PWG Process/3.0 requires that a quorum (30%) of PWG voting members must acknowledge a PWG Last Call (with or without comments), before any document can progress to PWG Formal Vote. This PWG Last Call is NOT a Formal Vote but it DOES require your review acknowledgment. HOW TO RESPOND Send an email with *exactly* the following subject line format: Subject: has reviewed the IPP JPS3 specification and has [no] comments WHERE TO SEND YOUR RESPONSE Please send your response to *all* of the following email addresses (replacing "dot" with '.' and "at" with '@'): ipp "at" pwg "dot" com (IPP WG mailing list - you must be subscribed!) blueroofmusic "at" gmail "dot" com (Ira McDonald, IPP WG Co-Chair) ptykodi "at" tykodi "dot" com (Paul Tykodi, IPP WG Co-Chair) msweet "at" apple "dot" com (Michael Sweet, IPP WG Secretary and IPP JPS3 Editor) Note that you must be subscribed to the IPP WG mailing list to send email there - otherwise your email will be silently discarded. Please do NOT simply reply to this note on the PWG-Announce list. Note: The PWG Definition of the Standards Development Process Version 3.0 is located at: http://www.pwg.org/chair/membership_docs/pwg-process30.pdf _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ pwg-announce mailing list pwg-announce@pwg.org https://www.pwg.org/mailman/listinfo/pwg-announce From ipp-bounces@pwg.org Fri Apr 20 14:04:05 2012 Return-Path: X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789A121E8037 for ; Fri, 20 Apr 2012 14:04:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.135 X-Spam-Level: * X-Spam-Status: No, score=1.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, MIME_HTML_MOSTLY=0.001, UNRESOLVED_TEMPLATE=3.132] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwezbDkz25hC for ; Fri, 20 Apr 2012 14:04:03 -0700 (PDT) Received: from pwg.org (pwg.org [192.146.101.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA9721E8032 for ; Fri, 20 Apr 2012 14:04:03 -0700 (PDT) Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org (Postfix) with ESMTP id E14AC796A1; Fri, 20 Apr 2012 17:03:34 -0400 (EDT) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by pwg.org (Postfix) with ESMTP id B21577969A for ; Fri, 20 Apr 2012 17:03:14 -0400 (EDT) Received: from mail175-tx2-R.bigfish.com (10.9.14.240) by TX2EHSOBE005.bigfish.com (10.9.40.25) with Microsoft SMTP Server id 14.1.225.23; Fri, 20 Apr 2012 21:03:14 +0000 Received: from mail175-tx2 (localhost [127.0.0.1]) by mail175-tx2-R.bigfish.com (Postfix) with ESMTP id 156591C054D for ; Fri, 20 Apr 2012 21:03:14 +0000 (UTC) X-SpamScore: -6 X-BigFish: VS-6(zz9371Ic85fh103dK98dKzz1202hzz8275eh8275bh8275dha1495iz2fh2a8h683h839hd25h) X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC103.redmond.corp.microsoft.com; RD:none; EFVD:NLI Received-SPF: pass (mail175-tx2: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=justhu@microsoft.com; helo=TK5EX14MLTC103.redmond.corp.microsoft.com ; icrosoft.com ; Received: from mail175-tx2 (localhost.localdomain [127.0.0.1]) by mail175-tx2 (MessageSwitch) id 1334955791911570_21048; Fri, 20 Apr 2012 21:03:11 +0000 (UTC) Received: from TX2EHSMHS017.bigfish.com (unknown [10.9.14.238]) by mail175-tx2.bigfish.com (Postfix) with ESMTP id D9D55240072 for ; Fri, 20 Apr 2012 21:03:11 +0000 (UTC) Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.8) by TX2EHSMHS017.bigfish.com (10.9.99.117) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 20 Apr 2012 21:03:09 +0000 Received: from CH1EHSOBE005.bigfish.com (157.54.51.80) by mail.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.2.283.4; Fri, 20 Apr 2012 21:03:08 +0000 Received: from mail79-ch1-R.bigfish.com (10.43.68.229) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Fri, 20 Apr 2012 21:03:07 +0000 Received: from mail79-ch1 (localhost [127.0.0.1]) by mail79-ch1-R.bigfish.com (Postfix) with ESMTP id F38D64E03B8 for ; Fri, 20 Apr 2012 21:03:07 +0000 (UTC) Received: from mail79-ch1 (localhost.localdomain [127.0.0.1]) by mail79-ch1 (MessageSwitch) id 1334955785386476_8386; Fri, 20 Apr 2012 21:03:05 +0000 (UTC) Received: from CH1EHSMHS017.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.231]) by mail79-ch1.bigfish.com (Postfix) with ESMTP id 57CAD16004C; Fri, 20 Apr 2012 21:03:05 +0000 (UTC) Received: from BL2PRD0310HT001.namprd03.prod.outlook.com (157.56.240.21) by CH1EHSMHS017.bigfish.com (10.43.70.17) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 20 Apr 2012 21:03:04 +0000 Received: from BL2PRD0310MB386.namprd03.prod.outlook.com ([169.254.11.6]) by BL2PRD0310HT001.namprd03.prod.outlook.com ([10.255.97.36]) with mapi id 14.16.0143.004; Fri, 20 Apr 2012 21:03:04 +0000 From: Justin Hutchings To: Michael Sweet , Justin Hutchings Subject: RE: [IPP] WS-discovery binding for IPP Everywhere Thread-Topic: [IPP] WS-discovery binding for IPP Everywhere Thread-Index: AczoH+2HVR0K6p4fQg2sacQwZa4/UQr6ZWOAAsvJBPA= Date: Fri, 20 Apr 2012 21:03:04 +0000 Message-ID: References: <15713B46EB868E4FB0CF6D8BFD33617E51865C69@TK5EX14MBXC110.redmond.corp.microsoft.com> <9CAE8BBE-60F7-42B8-A37A-AE12839D635A@apple.com> In-Reply-To: <9CAE8BBE-60F7-42B8-A37A-AE12839D635A@apple.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [131.107.192.18] MIME-Version: 1.0 X-OrganizationHeadersPreserved: BL2PRD0310HT001.namprd03.prod.outlook.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%APPLE.COM$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn% X-FOPE-CONNECTOR: Id%59$Dn%PWG.ORG$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn% X-CrossPremisesHeadersPromoted: TK5EX14MLTC103.redmond.corp.microsoft.com X-CrossPremisesHeadersFiltered: TK5EX14MLTC103.redmond.corp.microsoft.com X-OriginatorOrg: microsoft.com 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: