From pwg-announce-owner@pwg.org Sat Apr 01 08:54:36 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPgYm-00069y-NU; Sat, 01 Apr 2006 08:54:36 -0500 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPgYl-00010y-4w; Sat, 01 Apr 2006 08:54:36 -0500 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k31DsWJG008053; Sat, 1 Apr 2006 08:54:34 -0500 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k31DsWkq008050; Sat, 1 Apr 2006 08:54:32 -0500 Received: by pwg.org (bulk_mailer v1.13); Sat, 1 Apr 2006 08:52:20 -0500 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k31DqGek007665 for ; Sat, 1 Apr 2006 08:52:18 -0500 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k31DqGnw007662 for pwg-announce-out; Sat, 1 Apr 2006 08:52:16 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65593.518D8894" Subject: PWG-ANNOUNCE> PWG Semantic Model Agenda for PWG F-F April 6 Date: Sat, 1 Apr 2006 08:51:04 -0500 Message-ID: <52E6C34603975546B27FD219BA65014103AC53@WCXLMAIL.wcrt.xeroxlabs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PWG Semantic Model Agenda for PWG F-F April 6 Thread-Index: AcZVAZ5bb3HqzBgORA+StgRup/9PtgAiYWZw From: "Zehler, Peter" To: X-OriginalArrivalTime: 01 Apr 2006 13:51:04.0124 (UTC) FILETIME=[516C3FC0:01C65593] Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.2 (/) X-Scan-Signature: f560cc438c8be83d0aa5c816c29b481c This is a multi-part message in MIME format. ------_=_NextPart_001_01C65593.518D8894 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 Here is the agenda for the Semantic Model portion of the PWG face to face. I need someone at the face to face to run the MyMeetings (I think it is powered by WebEx) for me. I would like to test it before the meeting. Could someone volunteer and let me know a good time to test it with them before the meeting? =20 *Date/Time:=20 - April 6 2006=20 - 9am - 1pm eastern=20 *Dial-In=20 - Tele-Con Number: 1-866-365-4406=20 - PassCode: 2635888=20 *WebEx Meeting Details (http://www.mymeetings.com ): - Meeting Number: 747275324 Meeting Passcode: PwgSm Meeting Host: Peter Zehler Join Instructions for Instant Net Conference: 1. Join the meeting now: http://www.mymeetings.com/xerox/nc/join.php?i=3D747275324&p=3DPwgSm&t=3Dc= =20 2. Enter the required fields. 3. Indicate that you have read the Privacy Policy. 4. Click on Proceed.=20 =20 *Agenda:=20 =20 -9:00 - 9:15:=20 * Convene=20 -9:15 - 9:30:=20 * Intros=20 * Agenda bashing=20 -9:30 - 10:30=20 * Presentation slides and discussion=20 -10:30 - 10:45=20 * Break=20 -10:45 - 11:30=20 * JDF Office discussion=20 -11:30 - 1:00=20 * Decide on priority & dates=20 * Detailed discussion=20 =20 I have placed the PowerPoint version of the presentation on the PWG site at . I will post a PDF version soon. =20 Pete =20 Peter Zehler=20 XEROX=20 Xerox Innovation Group=20 Email: Peter.Zehler@XeroxLabs.com=20 Voice: (585) 265-8755=20 FAX: (585) 265-7441=20 US Mail: Peter Zehler Xerox Corp.=20 800 Phillips Rd.=20 M/S 128-25E=20 Webster NY, 14580-9701=20 ------_=_NextPart_001_01C65593.518D8894 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
All,
 
Here is the agenda for the Semantic Model = portion of=20 the PWG face to face.  I need someone at the face to face to run = the=20 MyMeetings (I think it is powered by WebEx) for me.  I would like = to test=20 it before the meeting.  Could someone volunteer and let me know a = good time=20 to test it with them before the meeting?
 
•Date/Time:
–    April 6 2006=20
–    9am – 1pm = eastern=20
•Dial-In=20
–    Tele-Con = Number:  1-866-365-4406 =
–    PassCode: = 2635888
•WebEx=20 Meeting Details (http://www.mymeetings.com): =
–    Meeting=20 Number: 747275324
   =20 Meeting Passcode:       =20 PwgSm
    Meeting=20 Host:           &n= bsp;Peter = Zehler
Join = Instructions for Instant=20 Net Conference:
    1. Join the meeting = now:
http://www.mymeetings.com/xerox/nc/join.php?i=3D747275324&p=3D= PwgSm&t=3Dc
    2. = Enter the=20 required fields.
    = 3.=20 Indicate that you have read the Privacy Policy.
    4. Click on = Proceed.=20
 
•Agenda:
 
–9:00 -=20 9:15:
•   Convene =
–9:15 -=20 9:30:
•   Intros =
•   Agenda bashing =
–9:30 -=20 10:30
•   Presentation slides and = discussion=20
–10:30 -=20 10:45
•   Break =
–10:45 –=20 11:30
•   JDF Office discussion=20
–11:30 –=20 1:00
•   Decide on priority & = dates=20
•   Detailed discussion=20
 
I have placed the PowerPoint version of the=20 presentation on the PWG site at <ftp://ftp.pwg.org/pub/pwg/Semantic-Model/Minutes/PWG-SM-0= 60406-Presentation.ppt>. =20 I will post a PDF version soon.
 
Pete
 

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

------_=_NextPart_001_01C65593.518D8894-- From pwg-announce-owner@pwg.org Sun Apr 02 16:51:13 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQ9XV-0000zx-DG; Sun, 02 Apr 2006 16:51:13 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQ9XU-0001Dw-37; Sun, 02 Apr 2006 16:51:13 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k32Kp9nU031918; Sun, 2 Apr 2006 16:51:11 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k32Kp9nu031915; Sun, 2 Apr 2006 16:51:09 -0400 Received: by pwg.org (bulk_mailer v1.13); Sun, 2 Apr 2006 16:48:46 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k32KmgCt031515 for ; Sun, 2 Apr 2006 16:48:44 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k32KmgvV031512 for pwg-announce-out; Sun, 2 Apr 2006 16:48:42 -0400 Message-ID: <789E617C880666438EDEE30C2A3E8D10EDAB@mailsrvnt05.enet.sharplabs.com> From: "McDonald, Ira" To: "'Zehler, Peter'" , pwg-announce@pwg.org Subject: RE: PWG-ANNOUNCE> [PDF slides posted] PWG Semantic Model Agenda f or PWG F-F April 6 Date: Sun, 2 Apr 2006 13:48:32 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: amavisd-new at sharplabs.com Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Hi, PDF of Pete's presentation slides posted in the directory: ftp://ftp.pwg.org/pub/pwg/Semantic-Model/Minutes/ in the file: PWG-SM-060406-Presentation.pdf Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: owner-pwg-announce@pwg.org [mailto:owner-pwg-announce@pwg.org]On Behalf Of Zehler, Peter Sent: Saturday, April 01, 2006 8:51 AM To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> PWG Semantic Model Agenda for PWG F-F April 6 All, Here is the agenda for the Semantic Model portion of the PWG face to face. I need someone at the face to face to run the MyMeetings (I think it is powered by WebEx) for me. I would like to test it before the meeting. Could someone volunteer and let me know a good time to test it with them before the meeting? *Date/Time: - April 6 2006 - 9am - 1pm eastern *Dial-In - Tele-Con Number: 1-866-365-4406 - PassCode: 2635888 *WebEx Meeting Details (http://www.mymeetings.com): - Meeting Number: 747275324 Meeting Passcode: PwgSm Meeting Host: Peter Zehler Join Instructions for Instant Net Conference: 1. Join the meeting now: http://www.mymeetings.com/xerox/nc/join.php?i=747275324&p=PwgSm&t=c 2. Enter the required fields. 3. Indicate that you have read the Privacy Policy. 4. Click on Proceed. *Agenda: -9:00 - 9:15: * Convene -9:15 - 9:30: * Intros * Agenda bashing -9:30 - 10:30 * Presentation slides and discussion -10:30 - 10:45 * Break -10:45 - 11:30 * JDF Office discussion -11:30 - 1:00 * Decide on priority & dates * Detailed discussion I have placed the PowerPoint version of the presentation on the PWG site at . I will post a PDF version soon. Pete Peter Zehler XEROX Xerox Innovation Group Email: Peter.Zehler@XeroxLabs.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 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.4/299 - Release Date: 3/31/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.4/299 - Release Date: 3/31/2006 From pwg-announce-owner@pwg.org Mon Apr 03 15:04:53 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQUM9-0002M8-29; Mon, 03 Apr 2006 15:04:53 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQUM6-0007n2-K5; Mon, 03 Apr 2006 15:04:53 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k33J4lbp029650; Mon, 3 Apr 2006 15:04:49 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k33J4lKY029646; Mon, 3 Apr 2006 15:04:47 -0400 Received: by pwg.org (bulk_mailer v1.13); Mon, 3 Apr 2006 15:02:25 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k33J2LOT029232 for ; Mon, 3 Apr 2006 15:02:23 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k33J2Lla029229 for pwg-announce-out; Mon, 3 Apr 2006 15:02:21 -0400 From: wamwagner@comcast.net To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> WIMS WG Status - PWG Plenary F-F April 5 Date: Mon, 03 Apr 2006 19:02:16 +0000 Message-Id: <040320061902.15200.44317138000965AD00003B6022070009539D0A02090E99030E99@comcast.net> X-Mailer: AT&T Message Center Version 1 (Aug 4 2005) X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_15200_1144090936_0" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a --NextPart_Webmail_9m3u9jl4l_15200_1144090936_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Greetings: Slides giving WIMS WG status (including CIM Project) for the April 5 PWG Plenary meeting are posted at: ftp://ftp.pwg.org/pub/pwg/general/presentations/WIMS_APR_20060405.pdf. NOTE WELL: PWG Call for Objections on the PWG CIM Printing Refresh v1.0 (16 March 2006) white paper at ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscimprint10-20060316.htm and the Change Request (CR)to be submitted to DMTF for changes to be made to the CIM_Printer.mof in CIMv2.11 ftp://ftp.pwg.org/pub/pwg/wims/wd/CIMCoreNNNNN.000-20060322.htm will end at this weeks Plenary meeting. Pending discussion of objections, these docuements will be submitted as the first installement of PWG corrections to the CIM Model for Printing. Also Note (From Jerry Thrasher's message): The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol and nine associated XML schema files from the WIMS WG of the Printer Working Group have been submitted for a Formal Approval vote by the PWG membership. The voting period will close close at 10PM (Pacific Time) on Friday April 21, 2006. The Working Draft being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf The schema files being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip The list of comments that were addressed as part of the Last Call are located at: ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf INFORMATIVE WSDL files that implement the WIMS Abstract Protocol can be downloaded at the following links: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl - WIMS Agent Interface WSDL/1.1 v0.20 ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl - WIMS Manager Interface WSDL/1.1 v0.20 Bill Wagner, Chairman, WIMS WG/PWG --NextPart_Webmail_9m3u9jl4l_15200_1144090936_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
Greetings:
 
Slides giving WIMS WG status (including CIM Project) for the April 5 PWG Plenary meeting are posted at: ftp://ftp.pwg.org/pub/pwg/general/presentations/WIMS_APR_20060405.pdf.
 
NOTE WELL:  PWG Call for Objections on the PWG CIM Printing Refresh v1.0 (16 March 2006) white paper at ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscimprint10-20060316.htm and the Change Request (CR)to be submitted to DMTF for changes to be made to the CIM_Printer.mof in CIMv2.11

ftp://ftp.pwg.org/pub/pwg/wims/wd/CIMCoreNNNNN.000-20060322.htm

will end at this weeks Plenary meeting. Pending discussion of objections, these docuements will be submitted as the first installement of PWG corrections to the CIM Model for Printing.

 
Also Note (From Jerry Thrasher's message):
 
The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol and nine associated XML schema files from the WIMS WG of the Printer Working Group  have been submitted for a Formal Approval vote by the PWG membership. The voting period will close close at 10PM (Pacific Time) on Friday April 21, 2006.

The Working Draft being submitted can be downloaded at:
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf

The schema files being submitted can be downloaded at:
ftp:/! /ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip

The list of comments that were addressed as part of the Last Call
are located at:
ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf

INFORMATIVE WSDL files that implement the WIMS Abstract Protocol
can be downloaded at the following links:
ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip
    - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note
ftp://ftp.pwg.or! g/pub/pw g/wims/schemas/Agent-20060324.wsdl
    - WIMS Agent Interface WSDL/1.1 v0.20
ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl
    - WIMS Manager Interface WSDL/1.1 v0.20

Bill Wagner, Chairman, WIMS WG/PWG
--NextPart_Webmail_9m3u9jl4l_15200_1144090936_0-- From pwg-announce-owner@pwg.org Tue Apr 04 13:45:32 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQpat-0002xX-WF; Tue, 04 Apr 2006 13:45:32 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQpas-0001Kt-Ly; Tue, 04 Apr 2006 13:45:31 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k34HjRCO006078; Tue, 4 Apr 2006 13:45:29 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k34HjRRr006075; Tue, 4 Apr 2006 13:45:27 -0400 Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Apr 2006 13:43:19 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k34HhGgr005663 for ; Tue, 4 Apr 2006 13:43:18 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k34HhGlM005660 for pwg-announce-out; Tue, 4 Apr 2006 13:43:16 -0400 Message-ID: <789E617C880666438EDEE30C2A3E8D10EDB1@mailsrvnt05.enet.sharplabs.com> From: "McDonald, Ira" To: "'pwg-announce@pwg.org'" Cc: "'Paul Tykodi'" Subject: PWG-ANNOUNCE> Wed 5 April 1pm EDT - Slides for PWG MIB Implementors Guide BOF Date: Tue, 4 Apr 2006 10:43:03 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: amavisd-new at sharplabs.com Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Hi, I've just posted Paul Tykodi's PDF slides and PowerPoint source for PWG MIB Implementors Guide BOF in the directory: ftp://ftp.pwg.org/pub/pwg/general/presentations in the files: PWG-MIB-Imp-Guide-BOF-April-2006.pdf PWG-MIB-Imp-Guide-BOF-April-2006.ppt Please join us for this important topic tomorrow: Wednesday 5 April 2006 - 1pm US EDT Dial In: 1-866-365-4406 Toll #: 1-303-248-9655 Passcode: 2635888# Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/4/2006 From pwg-announce-owner@pwg.org Tue Apr 04 18:58:47 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQuU3-0008K7-Ip; Tue, 04 Apr 2006 18:58:47 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQuU2-00067j-50; Tue, 04 Apr 2006 18:58:47 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k34MwhYq014817; Tue, 4 Apr 2006 18:58:45 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k34MwhK1014814; Tue, 4 Apr 2006 18:58:43 -0400 Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Apr 2006 18:56:35 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k34MuW1w014417 for ; Tue, 4 Apr 2006 18:56:34 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k34MuWZn014414 for pwg-announce-out; Tue, 4 Apr 2006 18:56:32 -0400 From: wamwagner@comcast.net To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> WIMS CIM Session Slides - PWG F-F April 5 Date: Tue, 04 Apr 2006 22:56:26 +0000 Message-Id: <040420062256.23703.4432F99A0004DFC000005C9722058891169D0A02090E99030E99@comcast.net> X-Mailer: AT&T Message Center Version 1 (Aug 4 2005) X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_23703_1144191386_0" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f --NextPart_Webmail_9m3u9jl4l_23703_1144191386_0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by pwg.org id k34MwhYq014817 Brief slides for the WIMS/CIM session on 5 April are posted at ftp://ftp.= pwg.org/pub/pwg/general/presentations/WIMS-CIM_Apr_2006.pdf Craig Whittle, Co-chair, will be chairing the session. The session will start after the Plenary meeting. Agenda for the session = is: =20 lDMTF/PWG CIM Realignment=20 =96 Statement of Alliance, Three Phase Approach, Status of Phase 1=20 =96 Brief Presentation of Printer Class "White" Paper and CR=20 =96 Solicitation and Consideration of "Call for Objections" issues=20 l PWG Printer Management data model in Web Services =96=20 =96 Presentation on Web Services by Rick Landau=20 =96ftp://ftp.pwg.org/pub/pwg/wims/cim/PWG%20-%20Intro%20to%20WS-Managemen= t%2020060404.pdf=20 =96Discussion=20 =95 Get the Management Data Model Right! Argument for relying on updated CIM to ensure compatible printer ma= nagemennt model in WS Other Topics=20 =96 WSDM "Showcase" printer support=20 =96 Handling of MFP Management=20 Bill Wagner, Chairman, WIMS WG/PWG --NextPart_Webmail_9m3u9jl4l_23703_1144191386_0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by pwg.org id k34MwhYq014817
Brief slides for the WIMS/CIM session on 5 April are posted at ftp://ftp.pwg.org/pub/pwg/general/presentations/WIMS-CIM_Apr_2006.pdf=
 
Craig Whittle, Co-chair, will be chairing the session.
 
The session will start after the Plenary meeting. Agenda for the ses= sion is:
 
lDMTF/PWG CIM Realignment =
=96   &nb= sp;  Statement of Alliance, Three Phase Approach, Status of Phase 1 =
=96   &nb= sp;  Brief Presentation of Printer Class "White" Paper and CR
=96      Solicitati= on and Consideration of "Call for Objections" issues
l PWG Printer Management data model = in Web Services =96
=96      Presentati= on on Web Services by Rick Landau
=96%20Intro%20to%20WS-Management%2020060404.pdf<= /FONT>
=96Discussion
=95      Get the Management= Data Model Right!
      Argument for relying on updated CIM = to ensure compatible printer managemennt model in WS
Other Topics
=96        &nbs= p;   WSDM "Showcase" printer support
=96          &nb= sp; Handling of MFP Management
 
Bill Wagner, Chairman,= WIMS WG/PWG
--NextPart_Webmail_9m3u9jl4l_23703_1144191386_0-- From pwg-announce-owner@pwg.org Wed Apr 05 00:45:12 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQztI-0001Vx-5k; Wed, 05 Apr 2006 00:45:12 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQztG-0002RQ-S2; Wed, 05 Apr 2006 00:45:12 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k354j8i3022565; Wed, 5 Apr 2006 00:45:10 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k354j8EO022562; Wed, 5 Apr 2006 00:45:08 -0400 Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Apr 2006 00:43:00 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k354gups022175 for ; Wed, 5 Apr 2006 00:42:58 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k354guWQ022172 for pwg-announce-out; Wed, 5 Apr 2006 00:42:56 -0400 Message-ID: <789E617C880666438EDEE30C2A3E8D10EDB7@mailsrvnt05.enet.sharplabs.com> From: "McDonald, Ira" To: "'pwg-announce@pwg.org'" Subject: PWG-ANNOUNCE> FW: PMP> Thu 6 April 2-4pm EDT - MFP Alerts Presentation Date: Tue, 4 Apr 2006 21:42:48 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6586B.3D95DBA9" X-Virus-Scanned: amavisd-new at sharplabs.com Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.6 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C6586B.3D95DBA9 Content-Type: text/plain; charset="ISO-8859-1" Hi, Forwarded to PWG Announce mailing list, per the PWG process for face-to-face meetings. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf Of Bergman, Ron Sent: Wednesday, March 29, 2006 6:22 PM To: pmp@pwg.org Subject: PMP> Thu 6 April 2-4pm EDT - MFP Alerts Presentation The outline for my presentation at the PWG MFP Alerts meeting is available at: HYPERLINK "ftp://ftp.pwg.org/pub/pwg/pmp/presentations/MFP-PRINTER-MIB-ALERTS.pdf"ftp: //ftp.pwg.org/pub/pwg/pmp/presentations/MFP-PRINTER-MIB-ALERTS.pdf The MFP Alerts meeting is scheduled for April 6, 2006 from 2 to 4 PM EDT. Ron -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.3/296 - Release Date: 3/29/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: 4/4/2006 ------_=_NextPart_001_01C6586B.3D95DBA9 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable MFP Alerts Presentation 20060406
Hi,
 
Forwarded to PWG Announce mailing list, per = the PWG=20 process for
face-to-face meetings.
 
Cheers,
-=20 Ira
 

Ira McDonald (Musician / Software Architect)
Blue = Roof Music=20 / High North Inc
PO Box 221  Grand Marais, MI  = 49839
phone:=20 +1-906-494-2434
email: imcdonald@sharplabs.com

-----Original Message-----
From: pmp-owner@pwg.org=20 [mailto:pmp-owner@pwg.org]On Behalf Of Bergman, = Ron
Sent:=20 Wednesday, March 29, 2006 6:22 PM
To: = pmp@pwg.org
Subject:=20 PMP> Thu 6 April 2-4pm EDT - MFP Alerts = Presentation

The outline for my presentation at the = PWG MFP Alerts=20 meeting is available at:

   ftp://ftp.pwg.org/pub/pwg/pmp/presentations/MFP-PRINTER-MIB-ALER= TS.pdf=20

The MFP Alerts meeting is scheduled for = April 6, 2006=20 from 2 to 4 PM EDT.

        Ron=20



--
No virus found in this incoming = message.
Checked by AVG=20 Free Edition.
Version: 7.1.385 / Virus Database: 268.3.3/296 - = Release Date:=20 3/29/2006


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/301 - Release Date: = 4/4/2006

------_=_NextPart_001_01C6586B.3D95DBA9-- From pmp-owner@pwg.org Wed Apr 05 16:29:42 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FREdK-0003J7-Ln for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 16:29:42 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FREdK-0003Iv-5p for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 16:29:42 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35KTcEq016363 for ; Wed, 5 Apr 2006 16:29:40 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k35KTco1016360 for ; Wed, 5 Apr 2006 16:29:38 -0400 Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Apr 2006 16:28:59 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35KSt2K016263 for ; Wed, 5 Apr 2006 16:28:57 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k35KStCj016260 for pmp-out; Wed, 5 Apr 2006 16:28:55 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C658EF.95411807" X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: PMP> MIB Implementers Guide BOF Date: Wed, 5 Apr 2006 13:29:03 -0700 Message-ID: <9A6213D6CEDE5147A5FA6559410C363DC54968@Mail1.ktd.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PMP> MIB Implementers Guide BOF Thread-Index: AcZY75Rscr0d3L5MQNKGFdlDoVAk+Q== From: "Stuart Rowley" To: Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad This is a multi-part message in MIME format. ------_=_NextPart_001_01C658EF.95411807 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable All, =20 Much of the discussion hinged around getting printer vendors to improve their implementations, to perform interoperability or certification, and to provide readily accessible information on the level of their implementations, etc. so that software applications can more successfully manage devices from multiple vendors. =20 As I think Harry mentioned, the original intent of the printer MIB effort was in large part to have third party vendors and the major enterprise management apps, such as Tivoli, Unicenter, and OpenView, develop robust printer management implementations. When this failed to materialize, virtually all printer vendors developed their own software to manage their devices and, to a lesser extent, competitors devices as well. (or maybe the printer vendors shot themselves in the foot by releasing these free printer management apps and killing the incentive for other development). =20 I think many printer vendors may be resigned to the fact that the majority of print device management will be done by their own management apps and they don't have too much incentive to improve their partial management of competitors' devices. =20 Thus, these vendors may have difficulty seeing the benefit of the effort involved to move forward with much of the work that was proposed during the discussion. Perhaps a listing of the benefits to the printer vendors would be necessary to spur interest. Until there is market pressure to improve poor SNMP/MIB implementations or a clearly defined tangible benefit, I think some printer vendors may not be willing to allocate resources to these efforts.=20 =20 Regards, =20 Stuart =20 Stuart Rowley, Network Product Mgr. stuart.rowley@ktd-kyocera.com 925 849-3306 925 849-3399 (fax) =20 Kyocera Technology Development Inc. 1855 Gateway Blvd. Suite 400 Concord, CA 94520 ************************************=20 If this email is not intended for you, or you are not responsible for the delivery of this message to the addressee, please note that this message may contain Kyocera Technology Development Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to anyone. You should destroy this message and kindly notify the sender by reply email. Information contained in this message that does not relate to the business of Kyocera Technology Development is neither endorsed by nor attributable to Kyocera Technology Development.=20 ************************************ =20 =20 =20 ------_=_NextPart_001_01C658EF.95411807 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

All,

 

Much of the discussion hinged around getting printer vendors to improve their implementations, to perform interoperability or certification, and to = provide readily accessible information on the level of their implementations, = etc. so that software applications can more successfully manage devices from = multiple vendors.

 

As I think Harry mentioned, the original intent of the printer MIB effort was = in large part to have third party vendors and the major enterprise = management apps, such as Tivoli, Unicenter, and OpenView, develop robust printer management = implementations. When this failed to materialize, virtually all printer vendors developed = their own software to manage their devices and, to a lesser extent, competitors = devices as well. (or maybe the printer vendors shot themselves in the foot by = releasing these free printer management apps and killing the incentive for other development).

 

I think many printer vendors may be resigned to the fact that the majority = of print device management will be done by their own management apps and = they don’t have too much incentive to improve their partial management of = competitors’ devices.

 

Thus, these vendors may have difficulty seeing the benefit of the effort = involved to move forward with much of the work that was proposed during the = discussion. Perhaps a listing of the benefits to the printer vendors would be necessary to = spur interest. Until there is market pressure to improve poor SNMP/MIB implementations = or a clearly defined tangible benefit, I think some printer vendors may not be = willing to allocate resources to these efforts.

 

Regards,

 

Stuart

 

Stuart = Rowley, Network Product = Mgr.

stuart.rowley@ktd-kyocera.com   = ;   925 849-3306     925 849-3399 = (fax)

 

Kyocera Technology Development = Inc.

1855 Gateway Blvd. Suite 400

Concord, CA 94520

************************************ =

If this email is not intended for you, or you = are not responsible for the delivery of this message to the addressee, please = note that this message may contain Kyocera Technology Development = Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to = anyone. You should destroy this message and kindly notify the sender by reply = email. Information contained in this message that does not relate to the = business of Kyocera Technology Development is neither endorsed by nor attributable = to Kyocera Technology Development.

************************************

 

 

 

------_=_NextPart_001_01C658EF.95411807-- From pmp-owner@pwg.org Wed Apr 05 16:59:50 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRF6U-0002tM-Jg for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 16:59:50 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRF6U-0004jh-1u for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 16:59:50 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35Kxh0K017646 for ; Wed, 5 Apr 2006 16:59:45 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k35KxhND017643 for ; Wed, 5 Apr 2006 16:59:43 -0400 Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Apr 2006 16:59:14 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35KxC9Z017547 for ; Wed, 5 Apr 2006 16:59:14 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k35KxCnW017544 for pmp-out; Wed, 5 Apr 2006 16:59:12 -0400 From: wamwagner@comcast.net To: "Stuart Rowley" , Subject: Re: PMP> MIB Implementers Guide BOF Date: Wed, 05 Apr 2006 20:59:05 +0000 Message-Id: <040520062059.23609.44342F990004731F00005C3922070009539D0A02090E99030E99@comcast.net> X-Mailer: AT&T Message Center Version 1 (Aug 4 2005) X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_23609_1144270745_0" Sender: pmp-owner@pwg.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4 --NextPart_Webmail_9m3u9jl4l_23609_1144270745_0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by pwg.org id k35Kxh0K017646 Stuart, I agree absolutely. Without an economic incentive, the there is little li= kelihood that many vendors will put in any effort to improve or even publ= icize their public MIB implementations. There must be a perception of cus= tomer demand for general manage-ability of a mixed fleet, products of mul= tiple vendors managed by a single application.=20 Several years ago I expected the trend to third party fleet maintainers (= e.g., Danka, Ikon, Pitney Bowles) to prompt such a demand; but these comp= anies have been silent. More recently I would have expected the popularit= y of assay and hard-copy billing applications (many of which could sure s= tand access to job information from printers) to create a demand for cons= istent job mib implementation; but all I have seen are special deals with= individual companies to use proprietary features. Unless compliance with standard MIB (indeed, any management) implementati= ons becomes readily identifiable and is demanded as a checkoff item on pu= rchase requests, I suspect that there will be little motivation to includ= e, update or improve implementations. Bill Wagner -------------- Original message --------------=20 From: "Stuart Rowley" =20 All, =20 Much of the discussion hinged around getting printer vendors to improve t= heir implementations, to perform interoperability or certification, and t= o provide readily accessible information on the level of their implementa= tions, etc. so that software applications can more successfully manage de= vices from multiple vendors. =20 As I think Harry mentioned, the original intent of the printer MIB effort= was in large part to have third party vendors and the major enterprise m= anagement apps, such as Tivoli, Unicenter, and OpenView, develop robust p= rinter management implementations. When this failed to materialize, virtu= ally all printer vendors developed their own software to manage their dev= ices and, to a lesser extent, competitors devices as well. (or maybe the = printer vendors shot themselves in the foot by releasing these free print= er management apps and killing the incentive for other development). =20 I think many printer vendors may be resigned to the fact that the majorit= y of print device management will be done by their own management apps an= d they don=92t have too much incentive to improve their partial managemen= t of competitors=92 devices. =20 Thus, these vendors may have difficulty seeing the benefit of the effort = involved to move forward with much of the work that was proposed during t= he discussion. Perhaps a listing of the benefits to the printer vendors w= ould be necessary to spur interest. Until there is market pressure to imp= rove poor SNMP/MIB implementations or a clearly defined tangible benefit,= I think some printer vendors may not be willing to allocate resources to= these efforts.=20 =20 Regards, =20 Stuart =20 Stuart Rowley, Network Product Mgr. stuart.rowley@ktd-kyocera.com 925 849-3306 925 849-3399 (fax) =20 Kyocera Technology Development Inc. 1855 Gateway Blvd. Suite 400 Concord, CA 94520 ************************************=20 If this email is not intended for you, or you are not responsible for the= delivery of this message to the addressee, please note that this message= may contain Kyocera Technology Development Privileged/Proprietary Inform= ation. In such a case, you may not copy or deliver this message to anyone= . You should destroy this message and kindly notify the sender by reply e= mail. Information contained in this message that does not relate to the b= usiness of Kyocera Technology Development is neither endorsed by nor attr= ibutable to Kyocera Technology Development.=20 ************************************ =20 =20 =20 --NextPart_Webmail_9m3u9jl4l_23609_1144270745_0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by pwg.org id k35Kxh0K017646
Stuart,
 
I agree absolutely. Without an economic incentive, the there is litt= le likelihood that many vendors will put in any effort to improve or even= publicize their public MIB implementations. There must be a perception o= f customer demand for general manage-ability of a mixed fleet, products o= f multiple vendors managed by a single application.
 
Several years ago I expected the trend to third party fleet maintain= ers (e.g., Danka, Ikon, Pitney Bowles) to prompt such a demand; but these= companies have been silent. More recently I would have expected the popu= larity of assay and hard-copy billing applications (many of which could s= ure stand access to job information from printers) to create a demand for= consistent job mib implementation; but all I have seen are special deals= with individual companies to use proprietary features.
 
Unless compliance with standard MIB (indeed, any management) impleme= ntations becomes readily identifiable and is demanded as a checkoff = item on purchase requests, I suspect that there will be little motivation= to include, update or  improve implementations.
 
Bill Wagner
 
-------------- Original message --------------
From:= "Stuart Rowley" <Stuart.Rowley@ktd-kyocera.com>

All,

 

Much of the discussion hinged around getting printer vendors to i= mprove their implementations, to perform interoperability or certificatio= n, and to provide readily accessible information on the level of their im= plementations, etc. so that software applications can more successfully m= anage devices from multiple vendors.

 

As I think Harry mentioned, the original intent of the printer MI= B effort was in large part to have third party vendors and the major ente= rprise management apps, such as Tivoli, Unicenter, and OpenView, d= evelop robust printer management implementations. When this failed to mat= erialize, virtually all printer vendors developed their own software to m= anage their devices and, to a lesser extent, competitors devices as well.= (or maybe the printer vendors shot themselves in the foot by releasing t= hese free printer management apps and killing the incentive for other dev= elopment).

 

I think many printer vendors may be resigned to the fact that the= majority of print device management will be done by their own management= apps and they don=92t have too much incentive to improve their partial m= anagement of competitors=92 devices.

 

Thus, these vendors may have difficulty seeing the benefit of the= effort involved to move forward with much of the work that was proposed = during the discussion. Perhaps a listing of the benefits to the printer v= endors would be necessary to spur interest. Until there is market pressur= e to improve poor SNMP/MIB implementations or a clearly defined tangible = benefit, I think some printer vendors may not be willing to allocate reso= urces to these efforts.

 

Regards,

 

Stuart

 

= Stuart Rowley= , Network Product Mgr.

stuart.rowley@ktd-kyocera.com      925 8= 49-3306     925 849-3399 (fax)

 

Kyocera Technology Development Inc.

1855 Gateway Blv= d. Suite 400

Concord, CA 94520

************************************

If this email is not intended for you, or you are not responsible= for the delivery of this message to the addressee, please note that this= message may contain Kyocera Technology Development Privileged/Proprietar= y Information. In such a case, you may not copy or deliver this message t= o anyone. You should destroy this message and kindly notify the sender by= reply email. Information contained in this message that does not relate = to the business of Kyocera Technology Development is neither endorsed by = nor attributable to Kyocera Technology Development.

************************************

 

 

 

--NextPart_Webmail_9m3u9jl4l_23609_1144270745_0-- From pmp-owner@pwg.org Wed Apr 05 18:11:21 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRGDh-0004uc-Lj for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 18:11:21 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRGDh-0000CL-1T for printmib-archive@lists.ietf.org; Wed, 05 Apr 2006 18:11:21 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35MBI8O019029 for ; Wed, 5 Apr 2006 18:11:20 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k35MBIwk019026 for ; Wed, 5 Apr 2006 18:11:18 -0400 Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Apr 2006 18:10:47 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k35MAifu018932 for ; Wed, 5 Apr 2006 18:10:46 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k35MAi06018929 for pmp-out; Wed, 5 Apr 2006 18:10:44 -0400 X-IronPort-AV: i="4.04,91,1144040400"; d="scan'208,217"; a="405182889:sNHT1872393216" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C658FD.BAB97F23" Subject: RE: PMP> MIB Implementers Guide BOF Date: Wed, 5 Apr 2006 17:10:20 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PMP> MIB Implementers Guide BOF Thread-Index: AcZY9D4EjY9eiKDBSqaSuM0t1U/9hwABpCqg From: To: , , X-OriginalArrivalTime: 05 Apr 2006 22:10:21.0526 (UTC) FILETIME=[BB140760:01C658FD] Sender: pmp-owner@pwg.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 23336e92cd9b2f166f17126afcdd84ec This is a multi-part message in MIME format. ------_=_NextPart_001_01C658FD.BAB97F23 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable (I'm sorry I missed the discussion this afternoon.) I would like to agree and disagree at the same time. Agreed, without an economic incentive, vendors are unlikely to undertake programs to improve their implementations. They won't allocate resources specifically aimed at that goal. On the other hand, I think that most vendors, as part of normal maintenance, make minor improvements to come closer to compliance with specifications over time. At least I have observed that in the past. If there were tighter descriptions of the semantics of some items in the MIB, in an implementer's guide or revised spec, I think that vendors might sneak up on correct implementations over time. =20 =20 If we kept our effort really small and focused on a handful of properties in Printer MIB and Host Resources MIB -- choose the worst offenders first -- we might be able to get people's attention. (I'd be willing to work on a smallish effort.) =20 rick ________________________________ From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org] On Behalf Of wamwagner@comcast.net Sent: Wednesday, April 05, 2006 15:59 To: Stuart Rowley; pmp@pwg.org Subject: Re: PMP> MIB Implementers Guide BOF Stuart, =20 I agree absolutely. Without an economic incentive, the there is little likelihood that many vendors will put in any effort to improve or even publicize their public MIB implementations. There must be a perception of customer demand for general manage-ability of a mixed fleet, products of multiple vendors managed by a single application.=20 =20 Several years ago I expected the trend to third party fleet maintainers (e.g., Danka, Ikon, Pitney Bowles) to prompt such a demand; but these companies have been silent. More recently I would have expected the popularity of assay and hard-copy billing applications (many of which could sure stand access to job information from printers) to create a demand for consistent job mib implementation; but all I have seen are special deals with individual companies to use proprietary features. =20 Unless compliance with standard MIB (indeed, any management) implementations becomes readily identifiable and is demanded as a checkoff item on purchase requests, I suspect that there will be little motivation to include, update or improve implementations. =20 Bill Wagner =20 -------------- Original message --------------=20 From: "Stuart Rowley" =20 =09 All, =20 Much of the discussion hinged around getting printer vendors to improve their implementations, to perform interoperability or certification, and to provide readily accessible information on the level of their implementations, etc. so that software applications can more successfully manage devices from multiple vendors. =20 As I think Harry mentioned, the original intent of the printer MIB effort was in large part to have third party vendors and the major enterprise management apps, such as Tivoli, Unicenter, and OpenView, develop robust printer management implementations. When this failed to materialize, virtually all printer vendors developed their own software to manage their devices and, to a lesser extent, competitors devices as well. (or maybe the printer vendors shot themselves in the foot by releasing these free printer management apps and killing the incentive for other development). =20 I think many printer vendors may be resigned to the fact that the majority of print device management will be done by their own management apps and they don=12t have too much incentive to improve = their partial management of competitors=12 devices. =20 Thus, these vendors may have difficulty seeing the benefit of the effort involved to move forward with much of the work that was proposed during the discussion. Perhaps a listing of the benefits to the printer vendors would be necessary to spur interest. Until there is market pressure to improve poor SNMP/MIB implementations or a clearly defined tangible benefit, I think some printer vendors may not be willing to allocate resources to these efforts.=20 =20 Regards, =20 Stuart =20 Stuart Rowley, Network Product Mgr. stuart.rowley@ktd-kyocera.com 925 849-3306 925 849-3399 (fax) =20 Kyocera Technology Development Inc. 1855 Gateway Blvd. Suite 400 Concord, CA 94520 ************************************=20 If this email is not intended for you, or you are not responsible for the delivery of this message to the addressee, please note that this message may contain Kyocera Technology Development Privileged/Proprietary Information. In such a case, you may not copy or deliver this message to anyone. You should destroy this message and kindly notify the sender by reply email. Information contained in this message that does not relate to the business of Kyocera Technology Development is neither endorsed by nor attributable to Kyocera Technology Development.=20 ************************************ =20 =20 =20 ------_=_NextPart_001_01C658FD.BAB97F23 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
(I'm sorry I missed the discussion this = afternoon.)  I would=20 like to agree and disagree at the same time.  Agreed, without an = economic=20 incentive, vendors are unlikely to undertake programs to improve their=20 implementations.  They won't allocate resources specifically aimed = at that=20 goal.  On the other hand, I think that most vendors, as part of = normal=20 maintenance, make minor improvements to come closer to compliance with=20 specifications over time.  At least I have observed that in the = past. =20 If there were tighter descriptions of the semantics of some items in the = MIB, in=20 an implementer's guide or revised spec, I think that vendors might = sneak up=20 on correct implementations over time. 
 
If we kept=20 our effort really small and focused on a handful of properties in = Printer MIB=20 and Host Resources MIB -- choose the worst offenders first -- we = might be=20 able to get people's attention.  (I'd be willing to work on a = smallish=20 effort.)
 
rick

From: pmp-owner@pwg.org = [mailto:pmp-owner@pwg.org]=20 On Behalf Of wamwagner@comcast.net
Sent: Wednesday, = April 05,=20 2006 15:59
To: Stuart Rowley; pmp@pwg.org
Subject: = Re:=20 PMP> MIB Implementers Guide BOF

Stuart,
 
I agree absolutely. Without an economic incentive, the there is = little=20 likelihood that many vendors will put in any effort to improve or even = publicize=20 their public MIB implementations. There must be a perception of customer = demand=20 for general manage-ability of a mixed fleet, products of multiple = vendors=20 managed by a single application.
 
Several years ago I expected the trend to third party fleet = maintainers=20 (e.g., Danka, Ikon, Pitney Bowles) to prompt such a demand; but these = companies=20 have been silent. More recently I would have expected the popularity of = assay=20 and hard-copy billing applications (many of which could sure stand = access to job=20 information from printers) to create a demand for consistent job mib=20 implementation; but all I have seen are special deals with individual = companies=20 to use proprietary features.
 
Unless compliance with standard MIB (indeed, any management)=20 implementations becomes readily identifiable and is demanded as a = checkoff=20 item on purchase requests, I suspect that there will be little = motivation to=20 include, update or  improve implementations.
 
Bill Wagner
 
--------------=20 Original message --------------
From: "Stuart Rowley"=20 <Stuart.Rowley@ktd-kyocera.com>
------_=_NextPart_001_01C658FD.BAB97F23-- From pmp-owner@pwg.org Fri Apr 07 10:42:21 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRsAH-0003m6-Fo for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 10:42:21 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRsAE-0007Qk-4Z for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 10:42:21 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37EgFhP000409 for ; Fri, 7 Apr 2006 10:42:17 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k37EgFWg000406 for ; Fri, 7 Apr 2006 10:42:15 -0400 Received: by pwg.org (bulk_mailer v1.13); Fri, 7 Apr 2006 10:41:34 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37EfUZK000301 for ; Fri, 7 Apr 2006 10:41:32 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k37EfU9R032766 for pmp-out; Fri, 7 Apr 2006 10:41:30 -0400 Message-ID: <20060407144131.14710.qmail@hm316.locaweb.com.br> From: "Mateus Bicalho" Date: Fri, 7 Apr 2006 11:41:31 -0300 To: pmp@pwg.org Subject: PMP> Printers that support RFC 2707 References: In-Reply-To: X-Mailer: LocaMail X-IPAddress: 200.251.234.135 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: ** (2.105) AWL,BAYES_50 Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Hello ! I'm starting a research on Job Monitoring on printers, and I have noticed that RFC 2707 is one of possibilities that can support me. But, when I was testing it, I couldn't find any printer that implements RFC 2707. Does anyone know a list of printers that supports the RFC 2707 or when I can find it? Thanks in advance, Mateus Bicalho From pwg-announce-owner@pwg.org Fri Apr 07 15:24:43 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRwZX-00024u-G9; Fri, 07 Apr 2006 15:24:43 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRwZW-0002yk-0k; Fri, 07 Apr 2006 15:24:43 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37JOdKm004880; Fri, 7 Apr 2006 15:24:41 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k37JObpC004870; Fri, 7 Apr 2006 15:24:39 -0400 Received: by pwg.org (bulk_mailer v1.13); Fri, 7 Apr 2006 15:22:11 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37JM8SN004477 for ; Fri, 7 Apr 2006 15:22:10 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k37JM8Ao004474 for pwg-announce-out; Fri, 7 Apr 2006 15:22:08 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65A78.832696D1" Subject: PWG-ANNOUNCE> Semantic Model Working Group Update Date: Fri, 7 Apr 2006 15:21:45 -0400 Message-ID: <52E6C34603975546B27FD219BA650141066BBB@WCXLMAIL.wcrt.xeroxlabs.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Semantic Model Working Group Update Thread-Index: AcZaX1SbHXTFW8xnRiuYoRepYoNu2AAGHIww From: "Zehler, Peter" To: X-OriginalArrivalTime: 07 Apr 2006 19:21:46.0730 (UTC) FILETIME=[830424A0:01C65A78] Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e This is a multi-part message in MIME format. ------_=_NextPart_001_01C65A78.832696D1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 The Semantic Model Working Group has been reactivated. Interested parties should subscribe to the Semantic Model mail list. All discussions will occur on that list. There will be a teleconference on April 19. The details will be posted on the Semantic Model mail list. Included below is a note covering my action item from this week's face to face. =20 Pete =20 Peter Zehler XEROX Xerox Innovation Group Email: Peter.Zehler@XeroxLabs.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: Zehler, Peter=20 Sent: Friday, April 07, 2006 12:22 PM To: 'sm@pwg.org' Subject: SM Schema update All, =20 I have created an updated version of the SM schema. I hope this can be the basis for extension work.=20 A local version (i.e. relative links to schema files stored in the same directory) of the schema is available at >. I have included an XMLSPY project file. =20 The date when I can have an straw man schema that includes Subunits, Counters and Imaging Device Services Framework is right now. =20 What I have done is=20 1) Added the subunits as a peer of the services (e.g. Printer) 2) Added services for an Imaging device (e.g. FaxIn) 3) Included Counters which I believe are up to date with the approved specification 4) Added includes to all subschema so that each is valid on its own (makes it easier to edit and traverse) 5) Update the SM namespace =20 What I have not done is 1) Resolve the name conflict between Subunits and SM (I put Subunits in its own namespace as a stopgap solution) 2) Renamed the services to be consistent with WIMS 3) Added WIMS (except for Subunits) 4) Updated the master list of elements 5) Done anything to the SM specification =20 Pete Peter Zehler=20 XEROX=20 Xerox Innovation Group=20 Email: Peter.Zehler@XeroxLabs.com=20 Voice: (585) 265-8755=20 FAX: (585) 265-7441=20 US Mail: Peter Zehler Xerox Corp.=20 800 Phillips Rd.=20 M/S 128-25E=20 Webster NY, 14580-9701=20 =20 ------_=_NextPart_001_01C65A78.832696D1 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
All,
 
The Semantic Model Working Group has been=20 reactivated.  Interested parties should subscribe to the Semantic = Model=20 mail list.  All discussions will occur on that list.  There = will be a=20 teleconference on April 19.  The details will be posted on the = Semantic=20 Model mail list.  Included below is a note covering my action item = from=20 this week's face to face.
 
Pete
 

All,

 

Much of the=20 discussion hinged around getting printer vendors to improve their=20 implementations, to perform interoperability or certification, and to = provide=20 readily accessible information on the level of their implementations, = etc. so=20 that software applications can more successfully manage devices from = multiple=20 vendors.

 

As I think=20 Harry mentioned, the original intent of the printer MIB effort was in = large=20 part to have third party vendors and the major enterprise management = apps,=20 such as Tivoli, Unicenter, and OpenView, = develop=20 robust printer management implementations. When this failed to = materialize,=20 virtually all printer vendors developed their own software to manage = their=20 devices and, to a lesser extent, competitors devices as well. (or = maybe the=20 printer vendors shot themselves in the foot by releasing these free = printer=20 management apps and killing the incentive for other=20 development).

 

I think many=20 printer vendors may be resigned to the fact that the majority of print = device=20 management will be done by their own management apps and they don=12t = have too=20 much incentive to improve their partial management of competitors=12=20 devices.

 

Thus, these=20 vendors may have difficulty seeing the benefit of the effort involved = to move=20 forward with much of the work that was proposed during the discussion. = Perhaps=20 a listing of the benefits to the printer vendors would be necessary to = spur=20 interest. Until there is market pressure to improve poor SNMP/MIB=20 implementations or a clearly defined tangible benefit, I think some = printer=20 vendors may not be willing to allocate resources to these efforts.=20

 

Regards,

 

Stuart

 

Stuart=20 Rowley, = Network=20 Product Mgr.

stuart.rowley@ktd-kyocera.com     =20 925 849-3306     925 849-3399=20 (fax)

 

Kyocera=20 Technology Development Inc.

1855 Gateway Blvd. Suite=20 400

Concord, CA = 94520

************************************=20

If this=20 email is not intended for you, or you are not responsible for the = delivery of=20 this message to the addressee, please note that this message may = contain=20 Kyocera Technology Development Privileged/Proprietary Information. In = such a=20 case, you may not copy or deliver this message to anyone. You should = destroy=20 this message and kindly notify the sender by reply email. Information=20 contained in this message that does not relate to the business of = Kyocera=20 Technology Development is neither endorsed by nor attributable to = Kyocera=20 Technology Development.

************************************

 

 

 

Peter = Zehler
XEROX
Xerox Innovation = Group
Email:=20 Peter.Zehler@XeroxLabs.com
Voice:    (585)=20 265-8755
FAX:      (585)=20 265-7441
US Mail: Peter Zehler
         &nb= sp;   =20 Xerox = Corp.
          &nbs= p;  =20 800 Phillips Rd.
          &nbs= p;  =20 M/S 128-25E
         = ;    =20 Webster NY, = 14580-9701

 

From: Zehler, Peter
Sent: = Friday,=20 April 07, 2006 12:22 PM
To: 'sm@pwg.org'
Subject: SM = Schema=20 update

All,
 
I have = created an=20 updated version of the SM schema.  I hope this can be the basis for = extension work. 
A = local version=20 (i.e. relative links to schema files stored in the same = directory) of the=20 schema is available at
<ftp://ftp.pwg.org/pub/pwg/Semantic-Model/Schema/PWG-SM-040706.zip>.  I have included = an XMLSPY=20 project file.
 
The = date when I can=20 have an straw man schema that includes Subunits, Counters and = Imaging=20 Device Services Framework is right = now.
 
What I = have done is=20
1) = Added the=20 subunits as a peer of the services (e.g. Printer)
2) = Added services=20 for an Imaging device (e.g. FaxIn)
3) = Included Counters=20 which I believe are up to date with the approved=20 specification
4) = Added includes to=20 all subschema so that each is valid on its own (makes it easier to edit = and=20 traverse)
5) = Update the SM=20 namespace
 
What I = have not done=20 is
1) = Resolve the name=20 conflict between Subunits and SM (I put Subunits in its own namespace as = a=20 stopgap solution)
2) = Renamed the=20 services to be consistent with WIMS
3) = Added WIMS=20 (except for Subunits)
4) = Updated the=20 master list of elements
5) = Done anything to=20 the SM specification
 
Pete

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

 
------_=_NextPart_001_01C65A78.832696D1-- From pmp-owner@pwg.org Fri Apr 07 19:12:28 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FS07w-0005v4-Cd for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 19:12:28 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FS07v-0001JK-3m for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 19:12:28 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37NCONk012352 for ; Fri, 7 Apr 2006 19:12:26 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k37NCOIx012349 for ; Fri, 7 Apr 2006 19:12:24 -0400 Received: by pwg.org (bulk_mailer v1.13); Fri, 7 Apr 2006 19:11:54 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37NBpPv012255 for ; Fri, 7 Apr 2006 19:11:53 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k37NBpfl012252 for pmp-out; Fri, 7 Apr 2006 19:11:51 -0400 Message-ID: <789E617C880666438EDEE30C2A3E8D10EDBB@mailsrvnt05.enet.sharplabs.com> From: "McDonald, Ira" To: "'Mateus Bicalho'" , pmp@pwg.org Subject: RE: PMP> Printers that support RFC 2707 Date: Fri, 7 Apr 2006 16:11:40 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: amavisd-new at sharplabs.com Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Hello, I hope that printer manufacturers will answer your question. The PWG does not have a list of implementations of RFC 2707. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com > -----Original Message----- > From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf Of Mateus > Bicalho > Sent: Friday, April 07, 2006 10:42 AM > To: pmp@pwg.org > Subject: PMP> Printers that support RFC 2707 > > > Hello ! > > I'm starting a research on Job Monitoring on printers, and I > have noticed that RFC 2707 is one of possibilities that can > support me. But, when I was testing it, I couldn't find any > printer that implements RFC 2707. Does anyone know a list of > printers that supports the RFC 2707 or when I can find it? > > > Thanks in advance, > > Mateus Bicalho > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.4.0/304 - Release > Date: 4/7/2006 > > -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/304 - Release Date: 4/7/2006 From pmp-owner@pwg.org Fri Apr 07 19:29:53 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FS0On-0000HM-M0 for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 19:29:53 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FS0Om-0001tZ-8q for printmib-archive@lists.ietf.org; Fri, 07 Apr 2006 19:29:53 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37NTnlX013370 for ; Fri, 7 Apr 2006 19:29:51 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k37NTnk3013367 for ; Fri, 7 Apr 2006 19:29:49 -0400 Received: by pwg.org (bulk_mailer v1.13); Fri, 7 Apr 2006 19:29:23 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k37NTKhS013273 for ; Fri, 7 Apr 2006 19:29:22 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k37NTK4P013270 for pmp-out; Fri, 7 Apr 2006 19:29:20 -0400 From: wamwagner@comcast.net To: "McDonald, Ira" , "'Mateus Bicalho'" , pmp@pwg.org Subject: RE: PMP> Printers that support RFC 2707 Date: Fri, 07 Apr 2006 23:29:14 +0000 Message-Id: <040720062329.4774.4436F5CA0001A9A0000012A622007374789D0A02090E99030E99@comcast.net> X-Mailer: AT&T Message Center Version 1 (Aug 4 2005) X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_4774_1144452554_0" Sender: pmp-owner@pwg.org X-Spam-Score: 0.8 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 --NextPart_Webmail_9m3u9jl4l_4774_1144452554_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit But your question comes at at very opportune time, since the PWG has received several queries of this type and has been considering how to encourage and publicize correct implementation of public MIBs, such as the Job Monitoring MIB. Ultimately, it is the recognition by manufacturers that these capabilities are needed and used that will make them readily and correctly implemented. Bill Wagner, TIC -------------- Original message -------------- From: "McDonald, Ira" > Hello, > > I hope that printer manufacturers will answer your question. > The PWG does not have a list of implementations of RFC 2707. > > Cheers, > - Ira > > Ira McDonald (Musician / Software Architect) > Blue Roof Music / High North Inc > PO Box 221 Grand Marais, MI 49839 > phone: +1-906-494-2434 > email: imcdonald@sharplabs.com > > > -----Original Message----- > > From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf Of Mateus > > Bicalho > > Sent: Friday, April 07, 2006 10:42 AM > > To: pmp@pwg.org > > Subject: PMP> Printers that support RFC 2707 > > > > > > Hello ! > > > > I'm starting a research on Job Monitoring on printers, and I > > have noticed that RFC 2707 is one of possibilities that can > > support me. But, when I was testing it, I couldn't find any > > printer that implements RFC 2707. Does anyone know a list of > > printers that supports the RFC 2707 or when I can find it? > > > > > > Thanks in advance, > > > > Mateus Bicalho > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.1.385 / Virus Database: 268.4.0/304 - Release > > Date: 4/7/2006 > > > > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.4.0/304 - Release Date: 4/7/2006 > --NextPart_Webmail_9m3u9jl4l_4774_1144452554_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
But your question comes at at very opportune time, since the PWG has received several queries of this type and has been considering how to encourage and publicize correct implementation of public MIBs, such as the Job Monitoring MIB. Ultimately, it is the recognition by manufacturers that these capabilities are needed and used  that will make them readily and correctly implemented.
 
Bill Wagner, TIC
 
-------------- Original message --------------
From: "McDonald, Ira" <imcdonald@sharplabs.com>

> Hello,
>
> I hope that printer manufacturers will answer your question.
> The PWG does not have a list of implementations of RFC 2707.
>
> Cheers,
> - Ira
>
> Ira McDonald (Musician / Software Architect)
> Blue Roof Music / High North Inc
> PO Box 221 Grand Marais, MI 49839
> phone: +1-906-494-2434
> email: imcdonald@sharplabs.com
>
> > -----Original Message-----
> > From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf Of Mateus
> > Bicalho
> > Sent: Friday, April 07, 2006 10:42 AM
> > To: pmp@pwg.org
> > Subject: PMP> Printers that support RFC 2707
> >
> >
> > Hello !
> > > > I'm starting a research on Job Monitoring on printers, and I
> > have noticed that RFC 2707 is one of possibilities that can
> > support me. But, when I was testing it, I couldn't find any
> > printer that implements RFC 2707. Does anyone know a list of
> > printers that supports the RFC 2707 or when I can find it?
> >
> >
> > Thanks in advance,
> >
> > Mateus Bicalho
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.385 / Virus Database: 268.4.0/304 - Release
> > Date: 4/7/2006
> >
> >
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.4.0/304 - Release Date: 4/7/2006
>
--NextPart_Webmail_9m3u9jl4l_4774_1144452554_0-- From pwg-announce-owner@pwg.org Mon Apr 10 11:12:36 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FSy4C-00051W-Gd; Mon, 10 Apr 2006 11:12:36 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FSy4A-0005ti-KO; Mon, 10 Apr 2006 11:12:36 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3AFCVC0000490; Mon, 10 Apr 2006 11:12:33 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3AFCUq6000486; Mon, 10 Apr 2006 11:12:31 -0400 Received: by pwg.org (bulk_mailer v1.13); Mon, 10 Apr 2006 11:09:42 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3AF9cAj032542 for ; Mon, 10 Apr 2006 11:09:40 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3AF9cNX032539 for pwg-announce-out; Mon, 10 Apr 2006 11:09:38 -0400 From: wamwagner@comcast.net To: pwg-announce@pwg.org Subject: Re: PWG-ANNOUNCE> Formal Vote announcement for PWG WIMS V1.0 Abstract Protocol and schema Date: Mon, 10 Apr 2006 15:09:28 +0000 Message-Id: <041020061509.12511.443A7528000C8638000030DF22070009539D0A02090E99030E99@comcast.net> X-Mailer: AT&T Message Center Version 1 (Aug 4 2005) X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_12511_1144681768_0" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 1.5 (+) X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c --NextPart_Webmail_9m3u9jl4l_12511_1144681768_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit All, Just a reminder that the WIMS Protocol document and associated XML Schema are up for a vote to PWG candidate standard. Even if you are not interested in WIMS, please understand that the schema impact other PWG efforts to standardize management of Imaging Devices by Web Services, and indeed, that the schema may affect the management modeling of MFP devices. Approval of the schema (or NO votes with identification of desired changes) appear to be a prerequisite for proceeding with certain other planned Semantic Model activities. Although the WIMS protocol incorporates some novel and, we believe, useful ideas for Imaging Services management and we suggest that you take a look at it, it is possible that some may want to split their votes between the protocol and the schema. Jerry's instructions do not appear to allow for this, with a ballot counting for the set of spec and schema. (Note that certain of the schmea are normative to the spec, but that the schema can stand by themselves.) If the ability for separate vote on the Protocol Spec and the schema set is desired, please notify the balloting recipients: thrasher"at"lexmark"dot"com wamwagner"at"comcast"dot"net harryl"at"us"dot"ibm"dot"com and we will consider some mechanism to allow this. Many thanks, Bill Wagner, Chairman, WIMS WG/PWG -------------- Original message -------------- From: thrasher@lexmark.com Greetings: The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol and nine associated XML schema files from the WIMS WG of the Printer Working Group have completed the Last Call process. The Working Draft document and schema are being submitted by the WIMS Working Group chair for a Formal Approval vote by the PWG membership. The Working Draft being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf The schema files being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip The list of comments that were addressed as part of the Last Call are located at: ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf INFORMATIVE WSDL files that implement the WIMS Abstract Protocol can be downloaded at the following links: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl - WIMS Agent Interface WSDL/1.1 v0.20 ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl - WIMS Manager Interface WSDL/1.1 v0.20 REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE PROVIDED FOR INFORMATION ONLY !!! The voting period will open on Wednesday March 29, 2006 and close at 10PM (Pacific Time) on Friday April 21, 2006. Valid votes are: Yes, No, No (with strong objection), Abstain. Any No vote requires that the voter state the reason for the No vote and a description of the changes required to turn the No vote to a Yes. Representatives from PWG member companies are strongly encouraged to submit a vote. To cast a vote, please send an email with the following subject line format: "WIMS Spec. 1.0 Formal Vote---" Example: WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes No votes MUST contain a reason in the body of the email. Please send your vote to the following email addresses: (Replacing "dot" with . and "at" with @): thrasher"at"lexmark"dot"com wamwagner"at"comcast"dot"net harryl"at"us"dot"ibm"dot"com Note: The PWG Definition of the Standards Development Process Version 2.0 located at: ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf has now been adopted and contains new voting requirements. Contact Info. for the Primary and Alternate representatives from PWG member companies will be provided to the working group chair in case "reminder" notices are necessary to meet the voting requirements listed in the process document. Jerry Thrasher PWG Secretary --NextPart_Webmail_9m3u9jl4l_12511_1144681768_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
All,
 
Just a reminder that the WIMS Protocol document and associated XML Schema are up for a vote to PWG candidate standard. Even if you are not interested in WIMS, please understand that the schema impact other PWG efforts to standardize management of Imaging Devices by Web Services, and indeed, that the schema may affect the management modeling of MFP devices. Approval of the schema (or NO votes with identification of desired changes) appear to be a prerequisite for proceeding with certain other planned Semantic Model activities.
 
Although the WIMS protocol incorporates some novel and, we believe, useful ideas for Imaging Services management and we suggest that you take a look at it, it is possible that some may want to split their votes between the protocol and the schema. Jerry's instructions do not appear to allow for this, with a ballot counting for the set of spec and schema. (Note that certain of the schmea are normative to the spec, but that the schema can stand by themselves.) If the ability for separate vote on the Protocol Spec and the schema set is desired, please notify the balloting recipients:
 
thrasher"at"lexmark"dot"com
wamwagner"at"comcast"dot"net
harryl"at"us"dot"ibm"dot"com
and we will consider some mechanism to allow this.
 
Many thanks,
 
Bill Wagner, Chairman, WIMS WG/PWG
-------------- Original message --------------
From: thrasher@lexmark.com

Greetings:

The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol
and nine associated XML schema files from the WIMS WG of the Printer Working Group
have completed the Last Call process.

The Working Draft document and schema are being submitted by the WIMS
Working Group chair for a Formal Approval vote by the PWG membership.

The Working Draft being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf

The schema files being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip

The list of comments that were addressed as part of the Last Call
are located at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf

INFORMATIVE WSDL files that implement the WIMS Abstract Protocol
can be downloaded at the following links:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip
    - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl
    - WIMS Agen! t Interf ace WSDL/1.1 v0.20

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl
    - WIMS Manager Interface WSDL/1.1 v0.20

REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE
PROVIDED FOR INFORMATION ONLY !!!

The voting period will open on Wednesday March 29, 2006 and close at 10PM
(Pacific Time) on Friday April 21, 2006.

Valid votes are: Yes, No, No (with strong objection), Abstain.

Any No vote requires that the voter state the reason for the No vote
and a description of the changes required to turn the No vote to a Yes.

Representati! ves from PWG member companies are strongly encouraged to submit a vote.


To cast a vote, please send an email with the following subject line format:

"WIMS Spec. 1.0 Formal Vote-<company name>-<last name of voter>-<yes/no/abstain>"

Example:  WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes

No votes MUST contain a reason in the body of the email.


Please send your vote to the following email addresses:
(Replacing "dot" with . and "at" with @):

thrasher"at"lexmark"dot"com
wamwagner"at"comcast"dot"net
harryl"at"us"dot"ibm"dot"com


Note:
The PWG Def! inition of the Standards Development Process Version 2.0 located at:

ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf

has now been adopted and contains new voting requirements.

Contact Info. for the Primary and Alternate representatives from PWG
member companies will be provided to the working group chair in case
"reminder" notices are necessary to meet the voting requirements listed
in the process document.

Jerry Thrasher

PWG Secretary
--NextPart_Webmail_9m3u9jl4l_12511_1144681768_0-- From pmp-owner@pwg.org Tue Apr 11 17:46:53 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTQhJ-0003E9-IC for printmib-archive@lists.ietf.org; Tue, 11 Apr 2006 17:46:53 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTQhI-0005Aj-79 for printmib-archive@lists.ietf.org; Tue, 11 Apr 2006 17:46:53 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3BLknGK003801 for ; Tue, 11 Apr 2006 17:46:51 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3BLknLY003798 for ; Tue, 11 Apr 2006 17:46:49 -0400 Received: by pwg.org (bulk_mailer v1.13); Tue, 11 Apr 2006 17:46:16 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3BLkCLo003690 for ; Tue, 11 Apr 2006 17:46:14 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3BLkCQv003687 for pmp-out; Tue, 11 Apr 2006 17:46:12 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65DB1.57448E95" Subject: PMP> MFP Alerts Meeting minutes available Date: Tue, 11 Apr 2006 14:46:08 -0700 Message-ID: <41A3AA9A3516CB418C179FFDEF9E5A821547E6@exchange2k.hitachi-ps.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MFP Alerts Meeting minutes available Thread-Index: AcZdsVdPCFDrgLRATg2KvEhMYg5fdA== From: "Bergman, Ron" To: Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb This is a multi-part message in MIME format. ------_=_NextPart_001_01C65DB1.57448E95 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The MFP Alerts Meeting minutes from the face-to-face meeting in New = Jersey are available at: ftp://ftp.pwg.org/pub/pwg/pmp/minutes/mfp/MFP_Minutes_20060406.pdf ------_=_NextPart_001_01C65DB1.57448E95 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MFP Alerts Meeting minutes available

The MFP Alerts Meeting minutes from the = face-to-face meeting in New Jersey are available
at:  ftp://ftp.pwg.org/pub/pwg/pmp/minutes/mfp/MFP_Minutes_20060406.pdf=

------_=_NextPart_001_01C65DB1.57448E95-- From pmp-owner@pwg.org Tue Apr 11 18:02:27 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTQwN-0005Dz-Do for printmib-archive@lists.ietf.org; Tue, 11 Apr 2006 18:02:27 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTQwM-0005t5-6M for printmib-archive@lists.ietf.org; Tue, 11 Apr 2006 18:02:27 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3BM2NMU004888 for ; Tue, 11 Apr 2006 18:02:25 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3BM2NCr004885 for ; Tue, 11 Apr 2006 18:02:23 -0400 Received: by pwg.org (bulk_mailer v1.13); Tue, 11 Apr 2006 18:01:58 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3BM1uo8004791 for ; Tue, 11 Apr 2006 18:01:58 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3BM1ul5004788 for pmp-out; Tue, 11 Apr 2006 18:01:56 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65DB3.8A560BB3" Subject: PMP> Minutes from MIB Implementer's Guide BOF at New Jersey Meeting Date: Tue, 11 Apr 2006 15:01:52 -0700 Message-ID: <41A3AA9A3516CB418C179FFDEF9E5A821547E8@exchange2k.hitachi-ps.us> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Minutes from MIB Implementer's Guide BOF at New Jersey Meeting Thread-Index: AcZds4p22/H/OU/zQQWtlD228LMWxw== From: "Bergman, Ron" To: Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 This is a multi-part message in MIME format. ------_=_NextPart_001_01C65DB3.8A560BB3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The minutes from the MIB Implementer's Guide BOF at the New Jersey = face-to-face meeting can be found at: = ftp://ftp.pwg.org/pub/pwg/BOFs/MIB-Guide/MIB_IMP_GUIDE_BOF_Minutes_200604= 05.pdf ------_=_NextPart_001_01C65DB3.8A560BB3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Minutes from MIB Implementer's Guide BOF at New Jersey = Meeting

The minutes from the MIB Implementer's = Guide BOF at the New Jersey face-to-face meeting
can be found at:

        ftp://ftp.pwg.org/pub/pwg/BOFs/MIB-Guide/MIB_IMP_GUIDE_BO= F_Minutes_20060405.pdf

------_=_NextPart_001_01C65DB3.8A560BB3-- From pwg-announce-owner@pwg.org Wed Apr 12 14:25:32 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FTk20-0001OT-Ee; Wed, 12 Apr 2006 14:25:32 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTk1z-0007vH-3m; Wed, 12 Apr 2006 14:25:32 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3CIPSZV031517; Wed, 12 Apr 2006 14:25:30 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3CIPStp031514; Wed, 12 Apr 2006 14:25:28 -0400 Received: by pwg.org (bulk_mailer v1.13); Wed, 12 Apr 2006 14:23:13 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3CINAtP031122 for ; Wed, 12 Apr 2006 14:23:12 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3CINAss031119 for pwg-announce-out; Wed, 12 Apr 2006 14:23:10 -0400 To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> April 2006 PWG Plenary Meeting Minutes Posted MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Wed, 12 Apr 2006 14:19:06 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at 04/12/2006 14:19:08, Serialize complete at 04/12/2006 14:19:08 Content-Type: multipart/alternative; boundary="=_alternative 0064CEB18525714E_=" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa This is a multipart message in MIME format. --=_alternative 0064CEB18525714E_= Content-Type: text/plain; charset="us-ascii" The minutes from the April 5, 2006 PWG Plenary Meeting in Mt. Laurel NJ hosted by Oki Data have been posted to the PWG's ftp site at: ftp://ftp.pwg.org/pub/pwg/general/minutes/pwg_plenary_minutes_20060405.pdf Jerry Thrasher PWG Secretary --=_alternative 0064CEB18525714E_= Content-Type: text/html; charset="us-ascii"
The minutes from the April 5, 2006  PWG Plenary Meeting in Mt. Laurel NJ hosted by Oki Data have been posted to the PWG's ftp site at:

ftp://ftp.pwg.org/pub/pwg/general/minutes/pwg_plenary_minutes_20060405.pdf

Jerry Thrasher
PWG Secretary











--=_alternative 0064CEB18525714E_=-- From pmp-owner@pwg.org Tue Apr 18 17:17:19 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVxZX-0000Vz-46 for printmib-archive@lists.ietf.org; Tue, 18 Apr 2006 17:17:19 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVxZV-0007Lc-P3 for printmib-archive@lists.ietf.org; Tue, 18 Apr 2006 17:17:19 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3ILHFEG032683 for ; Tue, 18 Apr 2006 17:17:17 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3ILHEVi032680 for ; Tue, 18 Apr 2006 17:17:15 -0400 Received: by pwg.org (bulk_mailer v1.13); Tue, 18 Apr 2006 17:16:42 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3ILGclo032583 for ; Tue, 18 Apr 2006 17:16:40 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3ILGcpK032580 for pmp-out; Tue, 18 Apr 2006 17:16:38 -0400 Message-ID: <789E617C880666438EDEE30C2A3E8D10EDD6@mailsrvnt05.enet.sharplabs.com> From: "McDonald, Ira" To: "'pmp@pwg.org'" Subject: PMP> Posted Imaging System MIB draft (18 April 2006) Date: Tue, 18 Apr 2006 14:16:31 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="ISO-8859-1" X-Virus-Scanned: amavisd-new at sharplabs.com Sender: pmp-owner@pwg.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Hi, I just posted a PWG Imaging System MIB draft at: ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-pmpimagingmib10-20060418.mib This is the third draft of the Imaging System MIB, reduced in scope and complexity to meet the needs of MFP alerts support, consistent with our last MFP alerts telecon. This MIB is semantically aligned with the PWG Imaging Counters MIB and defines: (a) Services based on PWG Imaging System Counters (PWG 5106.1); (b) Subunits based on IETF Printer MIB (RFC 1759/3805). This MIB is warning-free in SMICng and Epilogue compilers. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.4/318 - Release Date: 4/18/2006 From pwg-announce-owner@pwg.org Thu Apr 20 08:04:56 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWXu4-0003l9-D6; Thu, 20 Apr 2006 08:04:56 -0400 Received: from www.pwg.org ([192.146.101.49] helo=pwg.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWXu2-00031B-SP; Thu, 20 Apr 2006 08:04:56 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3KC4qXm019297; Thu, 20 Apr 2006 08:04:54 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3KC4qlH019294; Thu, 20 Apr 2006 08:04:52 -0400 Received: by pwg.org (bulk_mailer v1.13); Thu, 20 Apr 2006 08:02:36 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3KC2WGm018904 for ; Thu, 20 Apr 2006 08:02:34 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3KC2Wqw018901 for pwg-announce-out; Thu, 20 Apr 2006 08:02:32 -0400 To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> Reminder: Formal Vote for PWG WIMS V1.0 Abstract Protocol and schema ends April 21... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Thu, 20 Apr 2006 08:02:25 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at 04/20/2006 08:02:28, Serialize complete at 04/20/2006 08:02:28 Content-Type: multipart/alternative; boundary="=_alternative 0042222B85257156_=" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc This is a multipart message in MIME format. --=_alternative 0042222B85257156_= Content-Type: text/plain; charset="us-ascii" Please remember to cast a vote by April 21, 10:00 PM Pacific Time. Original vote announcement below. Greetings: The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol and nine associated XML schema files from the WIMS WG of the Printer Working Group have completed the Last Call process. The Working Draft document and schema are being submitted by the WIMS Working Group chair for a Formal Approval vote by the PWG membership. The Working Draft being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf The schema files being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip The list of comments that were addressed as part of the Last Call are located at: ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf INFORMATIVE WSDL files that implement the WIMS Abstract Protocol can be downloaded at the following links: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl - WIMS Agent Interface WSDL/1.1 v0.20 ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl - WIMS Manager Interface WSDL/1.1 v0.20 REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE PROVIDED FOR INFORMATION ONLY !!! The voting period will open on Wednesday March 29, 2006 and close at 10PM (Pacific Time) on Friday April 21, 2006. Valid votes are: Yes, No, No (with strong objection), Abstain. Any No vote requires that the voter state the reason for the No vote and a description of the changes required to turn the No vote to a Yes. Representatives from PWG member companies are strongly encouraged to submit a vote. To cast a vote, please send an email with the following subject line format: "WIMS Spec. 1.0 Formal Vote---" Example: WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes No votes MUST contain a reason in the body of the email. Please send your vote to the following email addresses: (Replacing "dot" with . and "at" with @): thrasher"at"lexmark"dot"com wamwagner"at"comcast"dot"net harryl"at"us"dot"ibm"dot"com Note: The PWG Definition of the Standards Development Process Version 2.0 located at: ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf has now been adopted and contains new voting requirements. Contact Info. for the Primary and Alternate representatives from PWG member companies will be provided to the working group chair in case "reminder" notices are necessary to meet the voting requirements listed in the process document. Jerry Thrasher PWG Secretary --=_alternative 0042222B85257156_= Content-Type: text/html; charset="us-ascii"
Please remember to cast a vote by April 21, 10:00 PM Pacific Time.

Original vote announcement below.

Greetings:

The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol
and nine associated XML schema files from the WIMS WG of the Printer Working Group
have completed the Last Call process.

The Working Draft document and schema are being submitted by the WIMS
Working Group chair for a Formal Approval vote by the PWG membership.

The Working Draft being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf

The schema files being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip

The list of comments that were addressed as part of the Last Call
are located at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf

INFORMATIVE WSDL files that implement the WIMS Abstract Protocol
can be downloaded at the following links:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip
    - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl
    - WIMS Agent Interface WSDL/1.1 v0.20

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl
    - WIMS Manager Interface WSDL/1.1 v0.20

REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE
PROVIDED FOR INFORMATION ONLY !!!

The voting period will open on Wednesday March 29, 2006 and close at 10PM
(Pacific Time) on Friday April 21, 2006.

Valid votes are: Yes, No, No (with strong objection), Abstain.

Any No vote requires that the voter state the reason for the No vote
and a description of the changes required to turn the No vote to a Yes.

Representatives from PWG member companies are strongly encouraged to submit a vote.


To cast a vote, please send an email with the following subject line format:

"WIMS Spec. 1.0 Formal Vote-<company name>-<last name of voter>-<yes/no/abstain>"

Example:  WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes

No votes MUST contain a reason in the body of the email.


Please send your vote to the following email addresses:
(Replacing "dot" with . and "at" with @):

thrasher"at"lexmark"dot"com
wamwagner"at"comcast"dot"net
harryl"at"us"dot"ibm"dot"com


Note:
The PWG Definition of the Standards Development Process Version 2.0 located at:

ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf

has now been adopted and contains new voting requirements.

Contact Info. for the Primary and Alternate representatives from PWG
member companies will be provided to the working group chair in case
"reminder" notices are necessary to meet the voting requirements listed
in the process document.

Jerry Thrasher

PWG Secretary
--=_alternative 0042222B85257156_=-- From pwg-announce-owner@pwg.org Thu Apr 20 11:16:13 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWatB-00028a-6L; Thu, 20 Apr 2006 11:16:13 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWat9-0004qj-I9; Thu, 20 Apr 2006 11:16:13 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3KFG8uF026435; Thu, 20 Apr 2006 11:16:10 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3KFG81U026432; Thu, 20 Apr 2006 11:16:08 -0400 Received: by pwg.org (bulk_mailer v1.13); Thu, 20 Apr 2006 11:13:54 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3KFDqbr026022 for ; Thu, 20 Apr 2006 11:13:54 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3KFDqjW026019 for pwg-announce-out; Thu, 20 Apr 2006 11:13:52 -0400 To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> Reminder: - 24 Hours - WIMS V1.0 Abstract Protocol and Schema voting ends MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 Message-ID: From: Harry Lewis Date: Thu, 20 Apr 2006 09:16:38 -0600 X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 6.53HF654 | July 22, 2005) at 04/20/2006 09:16:40, Serialize complete at 04/20/2006 09:16:40 Content-Type: multipart/alternative; boundary="=_alternative 00539E5F87257156_=" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.1 (/) X-Scan-Signature: be922d419820e291bde1362184dc32fd This is a multipart message in MIME format. --=_alternative 00539E5F87257156_= Content-Type: text/plain; charset="US-ASCII" Per Jerry's note, with links and information below, please cast your vote regarding WIMS Protocol and Schema before the end of the voting period which concludes 10PM PDT tomorrow. ---------------------------------------------- Harry Lewis IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- ----- Forwarded by Harry Lewis/Boulder/IBM on 04/20/2006 09:09 AM ----- thrasher@lexmark.com Sent by: owner-pwg-announce@pwg.org 04/20/2006 06:02 AM To pwg-announce@pwg.org cc Subject PWG-ANNOUNCE> Reminder: Formal Vote for PWG WIMS V1.0 Abstract Protocol and schema ends April 21... Please remember to cast a vote by April 21, 10:00 PM Pacific Time. Original vote announcement below. Greetings: The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol and nine associated XML schema files from the WIMS WG of the Printer Working Group have completed the Last Call process. The Working Draft document and schema are being submitted by the WIMS Working Group chair for a Formal Approval vote by the PWG membership. The Working Draft being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf The schema files being submitted can be downloaded at: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip The list of comments that were addressed as part of the Last Call are located at: ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf INFORMATIVE WSDL files that implement the WIMS Abstract Protocol can be downloaded at the following links: ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl - WIMS Agent Interface WSDL/1.1 v0.20 ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl - WIMS Manager Interface WSDL/1.1 v0.20 REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE PROVIDED FOR INFORMATION ONLY !!! The voting period will open on Wednesday March 29, 2006 and close at 10PM (Pacific Time) on Friday April 21, 2006. Valid votes are: Yes, No, No (with strong objection), Abstain. Any No vote requires that the voter state the reason for the No vote and a description of the changes required to turn the No vote to a Yes. Representatives from PWG member companies are strongly encouraged to submit a vote. To cast a vote, please send an email with the following subject line format: "WIMS Spec. 1.0 Formal Vote---" Example: WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes No votes MUST contain a reason in the body of the email. Please send your vote to the following email addresses: (Replacing "dot" with . and "at" with @): thrasher"at"lexmark"dot"com wamwagner"at"comcast"dot"net harryl"at"us"dot"ibm"dot"com Note: The PWG Definition of the Standards Development Process Version 2.0 located at: ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf has now been adopted and contains new voting requirements. Contact Info. for the Primary and Alternate representatives from PWG member companies will be provided to the working group chair in case "reminder" notices are necessary to meet the voting requirements listed in the process document. Jerry Thrasher PWG Secretary --=_alternative 00539E5F87257156_= Content-Type: text/html; charset="US-ASCII"
Per Jerry's note, with links and information below, please cast your vote regarding WIMS Protocol and Schema before the end of the voting period which concludes 10PM PDT tomorrow.
----------------------------------------------
Harry Lewis
IBM STSM
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------
----- Forwarded by Harry Lewis/Boulder/IBM on 04/20/2006 09:09 AM -----
thrasher@lexmark.com
Sent by: owner-pwg-announce@pwg.org

04/20/2006 06:02 AM

To
pwg-announce@pwg.org
cc
Subject
PWG-ANNOUNCE> Reminder:  Formal Vote  for PWG WIMS V1.0 Abstract Protocol and schema ends April 21...






Please remember to cast a vote by April 21, 10:00 PM Pacific Time.

Original vote announcement below.

Greetings:

The PWG Standard for Web-based Imaging Management Service V1.0 Abstract Protocol
and nine associated XML schema files from the WIMS WG of the Printer Working Group
have completed the Last Call process.

The Working Draft document and schema are being submitted by the WIMS
Working Group chair for a Formal Approval vote by the PWG membership.

The Working Draft being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20060322.pdf

The schema files being submitted can be downloaded at:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-schemas-20060320.zip

The list of comments that were addressed as part of the Last Call
are located at:

ftp://ftp.pwg.org/pub/pwg/wims/wd/WIMS10-LastCallResolutionComments-20060322.pdf

INFORMATIVE WSDL files that implement the WIMS Abstract Protocol
can be downloaded at the following links:

ftp://ftp.pwg.org/pub/pwg/wims/schemas/wims-wsdl-20060324.zip
   - ZIP of WIMS WSDL/2.0, WIMS WSDL/1.1, and release note

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Agent-20060324.wsdl
   - WIMS Agent Interface WSDL/1.1 v0.20

ftp://ftp.pwg.org/pub/pwg/wims/schemas/Manager-20060324.wsdl
   - WIMS Manager Interface WSDL/1.1 v0.20

REMINDER THESE WSDL FILES ARE NOT PART OF THE FORMAL VOTE AND ARE
PROVIDED FOR INFORMATION ONLY !!!

The voting period will open on Wednesday March 29, 2006 and close at 10PM
(Pacific Time) on Friday April 21, 2006.

Valid votes are: Yes, No, No (with strong objection), Abstain.

Any No vote requires that the voter state the reason for the No vote
and a description of the changes required to turn the No vote to a Yes.

Representatives from PWG member companies are strongly encouraged to submit a vote.


To cast a vote, please send an email with the following subject line format:

"WIMS Spec. 1.0 Formal Vote-<company name>-<last name of voter>-<yes/no/abstain>"

Example:  WIMS Spec. 1.0 Formal Vote-Lexmark-thrasher-yes

No votes MUST contain a reason in the body of the email.


Please send your vote to the following email addresses:
(Replacing "dot" with . and "at" with @):

thrasher"at"lexmark"dot"com
wamwagner"at"comcast"dot"net
harryl"at"us"dot"ibm"dot"com


Note:
The PWG Definition of the Standards Development Process Version 2.0 located at:

ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf

has now been adopted and contains new voting requirements.

Contact Info. for the Primary and Alternate representatives from PWG
member companies will be provided to the working group chair in case
"reminder" notices are necessary to meet the voting requirements listed
in the process document.

Jerry Thrasher

PWG Secretary --=_alternative 00539E5F87257156_=-- From pwg-announce-owner@pwg.org Mon Apr 24 16:55:30 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FY85i-0003s2-4u; Mon, 24 Apr 2006 16:55:30 -0400 Received: from pwg.org ([192.146.101.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FY85f-0001Yl-Ox; Mon, 24 Apr 2006 16:55:30 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3OKtPW8026669; Mon, 24 Apr 2006 16:55:27 -0400 Received: from localhost (mail@localhost) by pwg.org (8.13.1/8.13.1/Submit) with SMTP id k3OKtO1n026666; Mon, 24 Apr 2006 16:55:25 -0400 Received: by pwg.org (bulk_mailer v1.13); Mon, 24 Apr 2006 16:53:00 -0400 Received: from pwg.org (localhost.localdomain [127.0.0.1]) by pwg.org with ESMTP id k3OKquQO026264 for ; Mon, 24 Apr 2006 16:52:58 -0400 Received: (from majordom@localhost) by pwg.org (8.13.1/8.13.1/Submit) id k3OKqunS026261 for pwg-announce-out; Mon, 24 Apr 2006 16:52:56 -0400 To: pwg-announce@pwg.org Subject: PWG-ANNOUNCE> PWG WIMS V1.0 Abstract Protocol and Schema Formal Vote Results MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: thrasher@lexmark.com Date: Mon, 24 Apr 2006 16:52:51 -0400 X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at 04/24/2006 16:52:52, Serialize complete at 04/24/2006 16:52:52 Content-Type: multipart/alternative; boundary="=_alternative 0072B3588525715A_=" Sender: owner-pwg-announce@pwg.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca This is a multipart message in MIME format. --=_alternative 0072B3588525715A_= Content-Type: text/plain; charset="us-ascii" The results of the recently completed PWG Formal Vote for the Printer Working Group WIMS V1.0 Abstract Protocol and Schema to be advanced to Candidate Standard are as follows: Vote Count: Yes: 7 No: 0 Abstain: 7 PWG Process Document 2.0 Criteria: 1. Met the 25 percent participation (needed at least 7 votes). 2. Met the 66 percent yes votes. (yes vs no) 3. Met the 50 percent of votes either yes or no....(needed at least 7) PWG WIMS V1.0 Abstract Protocol and Schema Formal Vote passes. Jerry Thrasher PWG Secretary --=_alternative 0072B3588525715A_= Content-Type: text/html; charset="us-ascii"
The results of the recently completed PWG Formal Vote for the
Printer Working Group WIMS V1.0 Abstract Protocol and Schema to be advanced
to Candidate Standard are as follows:

Vote Count:

Yes:           7
No:            0
Abstain:       7

PWG Process Document 2.0 Criteria:

1. Met the 25 percent participation (needed at least 7 votes).
2. Met the 66 percent yes votes. (yes vs no)
3. Met the 50 percent of votes either yes or no....(needed at least 7)

PWG WIMS V1.0 Abstract Protocol and Schema Formal Vote passes.

Jerry Thrasher
PWG Secretary
--=_alternative 0072B3588525715A_=--