From pwg-announce-owner@pwg.org Mon Dec 2 13:08:14 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29922; Mon, 2 Dec 2002 13:08:13 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id NAA18640; Mon, 2 Dec 2002 13:10:24 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Mon, 2 Dec 2002 13:07:25 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id NAA18423 for pwg-announce-outgoing; Mon, 2 Dec 2002 13:07:15 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C29A2D.9B4294CF" Subject: RE: PWG-ANNOUNCE> July conflict with IETF Date: Mon, 2 Dec 2002 10:06:58 -0800 Message-ID: Thread-Topic: PWG-ANNOUNCE> July conflict with IETF Thread-Index: AcKVAsRL/VnbghePTDGqTvKudGjX2QFJzjmA From: "Farrell, Lee" To: "Harry Lewis" , Sender: owner-pwg-announce@pwg.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C29A2D.9B4294CF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Given the two choices, I would strongly prefer the week of June 16. = [However, I'm not sure I understand why June 23 wasn't offered as well. = That would be my personal preference.] Otherwise, I would opt for July = 21. =20 Historically, the PWG has avoided conflict with both the W3C Advisory = Council and the IETF Plenary meetings -- even though only a few PWG = individuals attend both. I see no reason why we should change that = policy now. Because these events only happen 2 and 3 times per year, = respectively, it is especially onerous to have to miss one because of a = conflict. =20 Further, although it is not yet clear what role the IETF will take in = the area of XML Configuration, the possible PWG activity of Device = Management might need to pay close attention to the progress of this = effort. Scheduling the PWG meetings on the same week would not help. =20 Cheers, =20 lee =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=20 Lee Farrell=20 Canon Development Americas=20 110 Innovation Drive=20 Irvine, CA 92612=20 (949) 856-7163 - voice=20 (949) 856-7510 - fax=20 lee.farrell@cda.canon.com=20 =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=20 =20 =20 -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Monday, November 25, 2002 8:14 PM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> July conflict with IETF It has been pointed out that our July 2003 meeting date (14-18) is the = same week as the IETF meeting in Vienna.=20 I would like to gauge the severity of this conflict to PWG members and = preferences should a our schedule need to be modified. If you have an = opinion please indicate=20 1. Prefer to keep current PWG July 14 -18 meeting date=20 2. Prefer to move PWG meeting to week of June 16=20 3. Prefer to move PWG meeting to week of July 21=20 I do not feel any other dates are viable due to the proximity of USA = Independence Day and the common practice of extending this holiday with = vacation.=20 No response will be considered a "don't care" NOT a "leave as is".=20 Please respond by Thursday Dec 12.=20 ----------------------------------------------=20 Harry Lewis=20 IBM Printing Systems=20 ----------------------------------------------=20 ------_=_NextPart_001_01C29A2D.9B4294CF Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Given=20 the two choices, I would strongly prefer the week of June 16. = [However,=20 I'm not sure I understand why June 23 wasn't offered as well. That = would=20 be my personal preference.] Otherwise, I would opt for July=20 21.

Historically, the PWG has avoided conflict = with both=20 the W3C Advisory Council and the IETF Plenary meetings -- even = though only=20 a few PWG individuals attend both. I see no reason why we = should=20 change that policy now. Because these events only = happen 2 and 3=20 times per year, respectively, it is especially onerous to have to miss = one=20 because of a conflict.

Further, although it is not yet clear what = role the=20 IETF will take in the area of XML Configuration, the possible PWG = activity of=20 Device Management might need to pay close attention to the progress of = this=20 effort. Scheduling the PWG meetings on the same week would not=20 help.

Cheers,

lee

=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
Lee Farrell
Canon=20 Development Americas
110 = Innovation=20 Drive
Irvine, CA = 92612
(949) 856-7163 - voice
(949) 856-7510 - fax
lee.farrell@cda.canon.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

-----Original Message-----
From: Harry Lewis=20 [mailto:harryl@us.ibm.com]
Sent: Monday, November 25, 2002 = 8:14=20 PM
To: pwg-announce@pwg.org
Subject: = PWG-ANNOUNCE> July=20 conflict with IETF

It has = been pointed=20 out that our July 2003 meeting date (14-18) is the same week as the IETF = meeting=20 in Vienna.

I would like to gauge = the=20 severity of this conflict to PWG members and preferences should a our = schedule=20 need to be modified. If you have an opinion please indicate=20

1. Prefer to keep current PWG July 14 -18 = meeting=20 date
2. Prefer to move PWG meeting to = week of=20 June 16
3. Prefer to move PWG meeting = to week=20 of July 21

I do not feel any = other dates=20 are viable due to the proximity of USA Independence Day and the common = practice=20 of extending this holiday with vacation. No response will be = considered=20 a "don't care" NOT a "leave as is".

Please=20 respond by Thursday Dec 12.
----------------------------------------------
Harry Lewis =
IBM=20 Printing Systems
----------------------------------------------=20 ------_=_NextPart_001_01C29A2D.9B4294CF-- From pwg-announce-owner@pwg.org Mon Dec 2 13:29:42 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01155; Mon, 2 Dec 2002 13:29:36 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id NAA20494; Mon, 2 Dec 2002 13:31:48 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Mon, 2 Dec 2002 13:30:31 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id NAA20306 for pwg-announce-outgoing; Mon, 2 Dec 2002 13:30:27 -0500 (EST) Message-ID: <499DC368E25AD411B3F100902740AD650E6AD4A4@xrose03.rose.hp.com> From: "BERKEMA,ALAN C (HP-Roseville,ex1)" To: "'don@lexmark.com'" , Harry Lewis Cc: pwg-announce@pwg.org Subject: RE: PWG-ANNOUNCE> July conflict with IETF Date: Mon, 2 Dec 2002 13:29:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org I'll go along with Don's choices. Alan > -----Original Message----- > From: don@lexmark.com [mailto:don@lexmark.com] > Sent: Tuesday, November 26, 2002 5:54 AM > To: Harry Lewis > Cc: pwg-announce@pwg.org > Subject: Re: PWG-ANNOUNCE> July conflict with IETF > > > > My choices, in order of preference: > > July 21 > Leave as is (July 14) > June 16 > > ********************************************** > Don Wright don@lexmark.com > > Member, IEEE SA Standards Board > PatCom Chair, SCC Liaison > Member, IEEE-ISTO Board of Directors > f.wright@ieee.org / f.wright@computer.org > > Director, Alliances & Standards > Lexmark International > 740 New Circle Rd > Lexington, Ky 40550 > 859-825-4808 (phone) 603-963-8352 (fax) > ********************************************** > > > > > > "Harry Lewis" @pwg.org on 11/25/2002 11:14:01 PM > > Sent by: owner-pwg-announce@pwg.org > > > To: pwg-announce@pwg.org > cc: > Subject: PWG-ANNOUNCE> July conflict with IETF > > > It has been pointed out that our July 2003 meeting date (14-18) is the > same week as the IETF meeting in Vienna. > > I would like to gauge the severity of this conflict to PWG members and > preferences should a our schedule need to be modified. If you have an > opinion please indicate > > 1. Prefer to keep current PWG July 14 -18 meeting date > 2. Prefer to move PWG meeting to week of June 16 > 3. Prefer to move PWG meeting to week of July 21 > > I do not feel any other dates are viable due to the proximity of USA > Independence Day and the common practice of extending this > holiday with > vacation. > > No response will be considered a "don't care" NOT a "leave as is". > > Please respond by Thursday Dec 12. > > ---------------------------------------------- > Harry Lewis > IBM Printing Systems > ---------------------------------------------- > (See attached file: C.htm) > > > From pwg-announce-owner@pwg.org Mon Dec 2 15:36:19 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08747; Mon, 2 Dec 2002 15:36:13 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id PAA26350; Mon, 2 Dec 2002 15:38:21 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Mon, 2 Dec 2002 15:36:02 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id PAA26152 for pwg-announce-outgoing; Mon, 2 Dec 2002 15:35:59 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: PWG-ANNOUNCE> Web Based Monitoring and Management Date: Mon, 2 Dec 2002 15:35:46 -0500 Message-ID: <7F2C5DA4096E9D44B70E967CB54EEEDB0E848B@mamail.digi.com> Thread-Topic: PWG-ANNOUNCE> Character repertoires in printers Thread-Index: AcJ5JYcGWAucXi2rTOSMbpjA07RPrAhG1Kfg From: "Wagner,William" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id PAA26149 Sender: owner-pwg-announce@pwg.org Content-Transfer-Encoding: 8bit Greetings: I am submitting the following as a Charter draft for a Web Base Monitoring and Management Working group, in line with the scheduled BOF at the January PWG Plenary. I invite comments. I have also established a directory for materials related to this subject at ftp://ftp.pwg.org/pub/pwg/wsm (Web Services Management). Harry, can we set up a mailing list so that we don't overload "announce" with project specific comments? Thanks. Best regards, Bill Wagner, NetSilicon ------------------------------------------------------------------------------------------ Charter Proposal for PWG WEB-Based Device Monitoring and Management Abstract There exists a need for remote monitoring and maintenance of office imaging devices for several purposes, including: 1. Enterprise management and configuration of equipment in remote offices 2. Service Company monitoring of leased equipment or services for charging and maintenance 3. Equipment Supplier access of sold or leased equipment to maintain and update equipment This need is has been intensified by the increased complexity of equipment in scattered locations and the need to reduce costs of maintenance and support. Various mechanisms have been used to provide remote maintenance, including · telephone hookups, where the equipment calls out on a modem, · built in radio paging transmitters, · various network connections, often using a proprietary protocol Telephone and pager solutions are costly both for the equipment and in recurring charges. Custom network approaches typically require special MIS actions to communicate through the ever-necessary firewall. There is no standardization among the various approaches, so that different implementations are not compatible. The prevalence of the "Web" and the consistent support of Web Browsers across enterprise, soho and home environments suggest an effective and inexpensive method of addressing this need. Indeed, there are some implementations in place using this mechanism. Using the WEB to allow devices to contact an internet-accessible management server parallels and may indeed compliment the structure resulting from the PSI initiative. As has been observed in the PSI charter, "When a new problem presents itself ... there will be some initial, proprietary, solutions and some early adopters. Experience shows that standardizing certain critical components of the solution and making the standard freely available assures interoperability among implementations. This ultimately results in the broadest, most competitive market for the new solution. Customer sentiment generally supports and reinforces this experience as long as the standardization effort is concluded in a timely manner and the standardization process yields widespread adoption and demonstrable interoperability." In keeping with this, it is desirable to formalize the transport use in Web Based Device Monitoring and Management and to standardize the method of communication in an extensible way to allow interoperability between different manufacturers' imaging products and the various data base and management programs involved in the remote monitoring and management. In accord with this general objective, the working group should address: Monitoring (both on an alert and a periodic basis) Monitoring Configuration (identifying attributes to be monitored, frequency of monitoring, conditions for reporting) Management (configuring and/or controlling operation of the device) Transfer of files to the Device (communicating executable updates, fonts, options, address lists etc, along with the instructions of what to do with these files) The implementation of these functions must address: 1. Costs 2. Security 3. Operability within typical enterprise network constraints 4. Compatibility with existing data base and management capabilities 5. Compatibility with existing and anticipated infrastructure, including MIBs, the Semantic Model and PSI. 6. Support of the installed equipment base as well as providing for inclusion in future equipment To the extent possible, the working group should utilize protocols, techniques and procedures already in place, both to leverage extant technology and to avoid conflict with or infringement upon proprietary solutions. To this end, it should be aware of the work of the following organizations, as well as any publicly documented proprietary solutions. · IETF xmlconf activity (http://www.ietf.org/proceedings/02jul/index.html) · IETF webdav (http://www.ietf.org/html.charters/webdav-charter.html) · IETF BEEP (The Blocks Extensible Exchange Protocol Core {RFC 3080})(Mapping the BEEP Core onto TCP {RFC 3081}) · OASIS (https://www.oasis-open.org/committees/mgmtprotocol/) Milestones Because of increased activity in this area and the increasing deployment of proprietary approaches, it is important that the standardization activity proceed forthwith. On the other hand, the various aspects must be given adequate consideration. The following schedule should be achievable, but may be to long. It is suggested that the working group consider developing and disseminating a Monitoring Specification first, and then proceeding to a full specification of the standard including more general Management capabilities. Charter Stage BOF and Charter Discussion January 2003 Requirements Statement February 2003 Charter Formal Approval March 2003 Requirements Formal Approval March 2003 Analysis Stage Consideration of Similar Initiatives May 2003 Selection of Component Protocols and Techniques June 2002 Specification Stage Presentation of Initial Draft July 2003 Proposed Draft Standard Last Call October 2003 Draft Standard Formal Approval December 2002 Interoperability Event Q1 2004 Proposed Standard Last Call Q2 2004 Published Standard Q2 2004 From pwg-announce-owner@pwg.org Tue Dec 3 12:22:06 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04293; Tue, 3 Dec 2002 12:22:00 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id MAA07952; Tue, 3 Dec 2002 12:24:12 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Tue, 3 Dec 2002 12:21:46 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id MAA07754 for pwg-announce-outgoing; Tue, 3 Dec 2002 12:21:41 -0500 (EST) Subject: PWG-ANNOUNCE> IPPFax Working Group Last Call for "PDF Image-Streamable Format - PDF/is" and "IPPFAX/1.0 Protocol" to move to Draft To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: "Gail Songer" Date: Tue, 3 Dec 2002 09:22:56 -0800 X-MIMETrack: Serialize by Router on NotesAdmin1/Netreon/US(Release 5.0.11 |July 24, 2002) at 12/03/2002 09:24:02 AM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id MAA07751 Sender: owner-pwg-announce@pwg.org Content-Transfer-Encoding: 8bit Do NOT send comments by a Reply-All to this email. Instead, send comments to the ifx@pwg.org DL (to which you must be subscribed). All, This is a working group Last Call to move the specifications "PDF Image-Streamable Format - PDF/is" and "IPPFAX/1.0 Protocol" to Draft. PDF and Word versions of the drafts are posted at the pwg web site as: ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.doc ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.pdf ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.doc ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.pdf The Last Call notice follows: This is a formal request for final within the IPPFax Working Group in order to move two documents to Draft Standard. These documents are "PDF Image-Streamable Format - PDF/is" and the "IPPFAX/1.0 Protocol". These are IPP Working Group products, which have been discussed since early 2001. It is the intent, once all comments have been address, to progress these documents to Draft Standard. Last Calls are for a minimum of 2 weeks. The period for the Working Group comments will close on Dec 20, 2002(US Pacific time reference). The relevant documents are: Title : IPPFAX/1.0 Protocol Author(s) : Thomas N. Hastings, Ira McDonald, Paul Moore, Gail Songer, John Pulera, Rick Seeler Filename : ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.pdf Pages : 69 Date : 22 Nov 2002 IPPFAX is used to provide a synchronous, reliable exchange of image Documents between clients and servers. The primary use envisaged of this protocol is to provide a synchronous image transmission service for the Internet. Contrast this with the Internet FAX protocol specified in [RFC2305] and [RFC2532] that uses the SMTP mail protocol as a transport. The IPPFAX/1.0 protocol is a specialization of the IPP/1.1 [RFC2911], [RFC2910] protocol supporting a subset of the IPP operations with increased conformance requirements in some cases, some restrictions in other cases, and some additional REQUIRED attributes. The IPPFAX Protocol uses the 'ippfax' URL scheme (instead of the 'ipp' URL scheme) in all its operations. Most of the new attributes defined in this document MAY be supported by IPP Printers as OPTIONAL extensions to IPP as well. In addition, IPPFAX/1.0 REQUIRES the support of the IPP Event Notification mechanism [ipp-ntfy] using the 'ippget' Pull Delivery Method [ipp-get-method]. An IPPFAX Printer object is called a Receiver. A Receiver MUST support at least the PDF/is S Profile as specified in [ifx-pdfis] which is defined for the 'application/pdf' document format MIME type . A Print System MAY be configured to support both the IPPFAX and IPP protocols concurrently, but each protocol requires separate Printer objects with distinct URLs. Title : PDF Image-Streamable Format - PDF/is Author(s) : Rick Seeler Filename : ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.pdf Pages : 33 Date : 22 Nov 2002 PDF/is is an image document format intended for use by, but not limited to, the IPPFAX protocol, which is used to provide a synchronous, reliable exchange of image Documents between Senders and Receivers. PDF/is makes reference to the PDF 1.4 Reference [pdf], which describes the PDF representation of image data specified by the ITU-T Recommendations for black-and-white facsimile (see [T.4], [T.6]), the ISO/IEC Specifications for Digital Compression and Coding of Continuous-Tone Still Images (see [jpeg]), and Lossy/Lossless Coding of Bi-Level Images (see [jbig2]), and the general purpose Flate compression methods (see [RFC1950] and [RFC1951]). PDF/is is an image-only, streamable, subset specification of PDF 1.4 [pdf] and, as such, follows all of the specification requirements of PDF. Gail Songer Peerless Systems Corp 650.358.8875 From pwg-announce-owner@pwg.org Mon Dec 9 16:41:58 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03448; Mon, 9 Dec 2002 16:41:57 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id QAA06307; Mon, 9 Dec 2002 16:44:20 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Mon, 9 Dec 2002 16:41:05 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id QAA06099 for pwg-announce-outgoing; Mon, 9 Dec 2002 16:40:57 -0500 (EST) Subject: PWG-ANNOUNCE> IPPFax Working Group Last Call for "PDF Image-Streamable Format - PDF/is" and "IPPFAX/1.0 Protocol" to move to Proposed To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: "Gail Songer" Date: Mon, 9 Dec 2002 13:42:54 -0800 X-MIMETrack: Serialize by Router on NotesAdmin1/Netreon/US(Release 5.0.11 |July 24, 2002) at 12/09/2002 01:43:27 PM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id QAA06096 Sender: owner-pwg-announce@pwg.org Content-Transfer-Encoding: 8bit The last "Last Call" incorrectly requested that the two documents in question be moved to DRAFT. They instead should be moved to PROPOSED. The modified "Last Call" is attached. __________________ Do NOT send comments by a Reply-All to this email. Instead, send comments to the ifx@pwg.org DL (to which you must be subscribed). All, This is a working group Last Call to move the specifications "PDF Image-Streamable Format - PDF/is" and "IPPFAX/1.0 Protocol" to Proposed. PDF and Word versions of the drafts are posted at the pwg web site as: ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.doc ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.pdf ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.doc ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.pdf The Last Call notice follows: This is a formal request for final within the IPPFax Working Group in order to move two documents to Proposed Standard. These documents are "PDF Image-Streamable Format - PDF/is" and the "IPPFAX/1.0 Protocol". These are IPP Working Group products, which have been discussed since early 2001. It is the intent, once all comments have been address, to progress these documents to Proposed Standard. Last Calls are for a minimum of 2 weeks. The period for the Working Group comments will close on Dec 20, 2002(US Pacific time reference). The relevant documents are: Title : IPPFAX/1.0 Protocol Author(s) : Thomas N. Hastings, Ira McDonald, Paul Moore, Gail Songer, John Pulera, Rick Seeler Filename : ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-ippfax-P13-021122.pdf Pages : 69 Date : 22 Nov 2002 IPPFAX is used to provide a synchronous, reliable exchange of image Documents between clients and servers. The primary use envisaged of this protocol is to provide a synchronous image transmission service for the Internet. Contrast this with the Internet FAX protocol specified in [RFC2305] and [RFC2532] that uses the SMTP mail protocol as a transport. The IPPFAX/1.0 protocol is a specialization of the IPP/1.1 [RFC2911], [RFC2910] protocol supporting a subset of the IPP operations with increased conformance requirements in some cases, some restrictions in other cases, and some additional REQUIRED attributes. The IPPFAX Protocol uses the 'ippfax' URL scheme (instead of the 'ipp' URL scheme) in all its operations. Most of the new attributes defined in this document MAY be supported by IPP Printers as OPTIONAL extensions to IPP as well. In addition, IPPFAX/1.0 REQUIRES the support of the IPP Event Notification mechanism [ipp-ntfy] using the 'ippget' Pull Delivery Method [ipp-get-method]. An IPPFAX Printer object is called a Receiver. A Receiver MUST support at least the PDF/is S Profile as specified in [ifx-pdfis] which is defined for the 'application/pdf' document format MIME type . A Print System MAY be configured to support both the IPPFAX and IPP protocols concurrently, but each protocol requires separate Printer objects with distinct URLs. Title : PDF Image-Streamable Format - PDF/is Author(s) : Rick Seeler Filename : ftp://ftp.pwg.org/pub/pwg/QUALDOCS/pwg-ifx-pdfis-P04-021122.pdf Pages : 33 Date : 22 Nov 2002 PDF/is is an image document format intended for use by, but not limited to, the IPPFAX protocol, which is used to provide a synchronous, reliable exchange of image Documents between Senders and Receivers. PDF/is makes reference to the PDF 1.4 Reference [pdf], which describes the PDF representation of image data specified by the ITU-T Recommendations for black-and-white facsimile (see [T.4], [T.6]), the ISO/IEC Specifications for Digital Compression and Coding of Continuous-Tone Still Images (see [jpeg]), and Lossy/Lossless Coding of Bi-Level Images (see [jbig2]), and the general purpose Flate compression methods (see [RFC1950] and [RFC1951]). PDF/is is an image-only, streamable, subset specification of PDF 1.4 [pdf] and, as such, follows all of the specification requirements of PDF. Gail Songer Peerless Systems Corp 650.358.8875 From pwg-announce-owner@pwg.org Tue Dec 10 11:03:22 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11596; Tue, 10 Dec 2002 11:03:15 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id LAA19320; Tue, 10 Dec 2002 11:05:29 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Tue, 10 Dec 2002 11:04:06 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id LAA19126 for pwg-announce-outgoing; Tue, 10 Dec 2002 11:04:01 -0500 (EST) Message-ID: From: "Zehler, Peter" To: "'Gail Songer'" Cc: "PWG Announce (E-mail)" Subject: PWG-ANNOUNCE> RE: SM> This week's SM teleconference agenda and information Date: Tue, 10 Dec 2002 11:03:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-pwg-announce@pwg.org Gail, Yes, it is a cut and paste error. The date for the teleconference is 12/12/02. Sorry about that, Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 -----Original Message----- From: Gail Songer [mailto:gsonger@peerless.com] Sent: Tuesday, December 10, 2002 10:23 AM To: Zehler, Peter Subject: Re: SM> This week's SM teleconference agenda and information Hi Pete, The date says 12/5/02. Is that just a typo? Gail |---------+----------------------------> | | "Zehler, Peter" | | | | | | Sent by: | | | owner-sm@pwg.org | | | | | | | | | 12/10/2002 07:12 | | | AM | | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: "PWG Semantic Model WG (E-mail)" | | cc: | | Subject: SM> This week's SM teleconference agenda and information | >--------------------------------------------------------------------------- ---------------------------------------------------| All, This Thursday at 1pm EDT is the Semantic Model teleconference. The teleconference is one hour long. It will be run using both phone and Webex. Anyone that does not yet have Webex installed should do that before Thursday. Information for the phone and Webex are included below. The agenda for the Semantic Model teleconference is 1) Adjust agenda 2) Review "-actual" specification (See below for more information from Dennis Carney.) Note that this conversation is IPP specific. Specification is located at: "ftp://ftp.pwg.org/pub/pwg/ipp/new_ACT/pwg-ipp-actual-attrs-v02-021205.pdf" 3) Discuss Bob Taylor's Media schema issue (See below) 3) Status on Semantic Model and associated schema 4) Next steps Pete Peter Zehler XEROX Xerox Architecture Center Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 265-8871 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-30E Webster NY, 14580-9701 PS to Bob Taylor: Let me know if there is any problem with Webex for this week. ________________________________________________________ Dial in Info: Phone Number: (877) 776-6306 (Phone Number for Xerox Employees: 8*594-0576) PARTICIPANT PASSCODE: 437874# ________________________________________________ webex info: We will also use an on line tool called webex, if you have not used this before, setup up by following the First Time Users instructions. Do this in advance of the meeting. ------------------------- FIRST TIME USERS: ------------------------- For fully interactive meetings, including the ability to present your documents and applications, a one-time setup takes less than 10 minutes. Click this URL to set up now: http://hp.webex.com Then click New User. ------------------------- On Thursday use: https://hp.webex.com/join/ Then click join unlisted meeting. Use the info below: ------------------------- Webex MEETING SUMMARY ------------------------- Name: PWG Semantic Model Date: 12/5/2002 Time: 1:00PM, (GMT -04:00) Eastern Time, USA & Canada (Daylight Time) 10:00AM, (GMT -07:00) Pacific Time, USA & Canada (Daylight Time) Meeting Number: 21366675 Meeting Password: pwg_sm Host: Bob Taylor (HP) ___________________________________________________ ____________________________________________________________________________ _________ "-actual" information from Dennis Carney: I have copied version 0.2 of the IPP "-actual" attributes spec to the PWG ftp site: ftp://ftp.pwg.org/pub/pwg/ipp/new_ACT/pwg-ipp-actual-attrs-v02-021205.pdf ftp://ftp.pwg.org/pub/pwg/ipp/new_ACT/pwg-ipp-actual-attrs-v02-021205.doc ftp://ftp.pwg.org/pub/pwg/ipp/new_ACT/pwg-ipp-actual-attrs-v02-021205-rev.pd f ftp://ftp.pwg.org/pub/pwg/ipp/new_ACT/pwg-ipp-actual-attrs-v02-021205-rev.do c This version includes the decisions made on the telecon and at the New Orleans meeting. The spec is 16 pages long, of which 6 1/2 pages contain the "meat" of the proposal. This version will be used as the basis for the discussion that is planned to occur at next week's Semantic Model teleconference (December 12, 2002). It was agreed that all discussion of this spec will occur on the Semantic Model mailing list. However, I copied this announcement to the IPP mailing list so the existence of the spec was known. The abstract: This document defines an extension to the Internet Printing Protocol/1.0 (IPP/1.0) [RFC2566, RFC2565] & IPP/1.1 [RFC2911, RFC2910] for the OPTIONAL "-actual" set of Job Description attributes that correspond to Job Template attributes defined in IPP. These "-actual" attributes allow the client to determine the true results of a print job regardless of what was specified in the Create-Job or Print-Job operation. ____________________________________________________________________________ _________ Media Schema issue from Bob Taylor: One schema structure issue we're running into: the current handling of MediaElements is a little confusing. The intent is that you just import PWGSemanticElements.xsd into other schemas, but if you also import MediaElements.xsd, you get redefinition validation errors. The answer might just be "don't do that", but I'd like to talk about it briefly on Thursday - i.e., should we change the way MediaElements relates to PWGSemanticElements to make it a little less error prone, or do we just document the problem away? ____________________________________________________________________________ ___________ From pwg-announce-owner@pwg.org Mon Dec 16 11:27:23 2002 Received: from pwg.org (www.pwg.org [192.146.101.49]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09922; Mon, 16 Dec 2002 11:27:22 -0500 (EST) Received: from localhost (daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) with SMTP id LAA15160; Mon, 16 Dec 2002 11:29:44 -0500 (EST) Received: by pwg.org (bulk_mailer v1.5); Mon, 16 Dec 2002 11:26:59 -0500 Received: (from daemon@localhost) by pwg.org (8.9.3+Sun/8.9.2) id LAA14981 for pwg-announce-outgoing; Mon, 16 Dec 2002 11:26:55 -0500 (EST) From: a.s.patel@ieee.org Importance: High X-Priority: 1 (High) Subject: PWG-ANNOUNCE> REMINDER:Re: January 20-24, 2003, Maui Hawaii Registration Update To: pwg-announce@pwg.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: Date: Mon, 16 Dec 2002 11:26:49 -0500 X-MIMETrack: Serialize by Router on Buzz/US/IEEE(Release 5.0.8 |June 18, 2001) at 12/16/2002 11:26:51 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-pwg-announce@pwg.org Hello All, This is a reminder to please register ( https://www.ieee-isto.org/pwg/registration.html) to attend the upcoming January 20-24, 2003 meeting in Maui, Hawaii. The deadline for reserving sleeping accomodations at the Sheraton Kaanapali Beach Resort is Friday, December 27, 2002. Please make your reservations by completing the reservation form on the registration site and faxing it to +1-808-661-0458 to make your reservations. Additional information regarding the specific meeting room location and details about the local area will be provided to you in a future update. If you have any questions or concerns regarding your reservations or anything else, please do not hesitate to contact me. With Kindest Regards, **************************************************************** Ami Patel IEEE-ISTO c/o The Printer Working Group Administrative Assistant Phone: 732 465 6477 Fax: +1 651 318 7292 AIM: Shortjunior email: a.s.patel@ieee.org **************************************************************** Ami Patel To: pwg-announce@pwg.org 11/22/2002 cc: 04:19 PM Subject: January 20-24, 2003, Maui Hawaii Registration Update Greetings All, The PWG Registration page is now available at http://www.ieee-isto.org/pwg/registration.html. Please register to attend the upcoming January 20-24, 2003 PWG Meeting in Maui, Hawaii. There is a daily attendance fee of US$45.00. (Payments are processed on the first day of the meeting series.) This fee is to cover food/beverage and meeting accomodations at the Bouboun Orleans. The deadline for reserving sleeping accommodations at the Sheraton Maui Resort is December 27, 2002. Please use the reservation form on the registration page to make your reservations. If you have any problems with making your sleeping room reservations, please contact me directly so that I may notify the hotel. If you have any other questions or concerns, please do not hesitate to contact me at any time. With Kind Regards, ~Ami Adminstrative Assistant IEEE-ISTO c/o The Printer Working Group Phone: 732-465-6477