attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff size=2>Bill, et al., </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff>Thanks again for more clarifications.  Glad to hear that we're all much on the same page.  </FONT></SPAN><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff>I look forward to contributing to making progress on all these fronts.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=321181616-13062005><FONT face=Arial color=#0000ff>rick</FONT></SPAN></DIV><BR> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma size=2><B>From:</B> wamwagner@comcast.net [mailto:wamwagner@comcast.net] <BR><B>Sent:</B> Friday, June 10, 2005 19:24<BR><B>To:</B> Landau, Richard; harryl@us.ibm.com<BR><B>Cc:</B> imcdonald@sharplabs.com; thrasher@lexmark.com; wims@pwg.org<BR><B>Subject:</B> Re: WIMS> RE: Brief minutes from WIMS 8 June 2005<BR></FONT><BR></DIV> <DIV></DIV> <DIV> <DIV>Rick,</DIV> <DIV> </DIV> <DIV>Your comments are very valuable, not just because of your extensive knowledge of the industry but because a prospective user can see problems that those of us close to the project do not see.</DIV> <DIV> </DIV> <DIV>As Ira has pointed out, the ExecuteAction operation in the Manager Interface does allow for a manager to initiate an immediate action, without a schedule. Although the same thing can be done with a SetSchedule operation with the execute timing set to immediate, the ExecuteAction operation was considered simpler.</DIV> <DIV> We do need to do a major cleanup on the <A href="ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20050322rev.doc">ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wims10-20050322rev.doc</A> draft, but it does include  use models and interaction diagrams. Some more specific help on where these fail would be appreciated.</DIV> <DIV> </DIV> <DIV>We too understand that Web Services has advanced greatly since we started WIMS. We had spent some looking at what was being worked on before we started, and it seemed that WEB Based enterprise management , in general, was indeed being addressed.  We felt that an activity that addressed fleet management in combination with the development of a management model for multifunction devices expressible in XML, which was necessary for any Web based management, would be useful. I think that remains true, although we may be not satisfactorily addressing this.</DIV> <DIV> </DIV> <DIV>And we certainly agree with you comment on proxies.</DIV> <DIV> </DIV> <DIV>I would like to try and wrap up the counter spec as soon as possible so that we can get on with WIMS protocol, and perhaps an extension to WIMS protocol. I hope you, and others, will continue to contribute to this effort.</DIV> <DIV> </DIV> <DIV>Bill Wagner, WIMS Chariman</DIV> <DIV> </DIV> <DIV>-------------- Original message -------------- <BR></DIV> <META content="MSHTML 6.00.2800.1479" name=GENERATOR></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff size=2>Bill, thanks for the historical perspective.  I appreciate that, having been away from this business for a few (apparently interesting) years.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>My questions really stemmed from two fundamental concerns.  (I will write real requirements later at some length.)</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>1.  I found it very difficult to grasp the document as it stands.  I came away with the impression that only scheduled operations are supported, and I think that anyone but the most serious reader would make similar mistakes.  Introductory information that describes usage models and message exchange sequences would be very helpful in this regard.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>2.  I appreciate the need for a fleet management protocol, but not to the exclusion of other, simpler models.  Two years ago when WIMS was conceived and written, web services were exotic and heavyweight.  No longer true.  Web services will be the new SNMP, eventually, in endpoint devices.  They will be just another transport mechanism for the same management information in the device.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>Didn't early SNMP specs talk about proxy implementations?  I haven't seen any new SNMP proxy implementations lately.  Web services will follow the same path: there will be early proxy implementations to front for legacy devices, but they will migrate into endpoint devices -- and much more quickly than SNMP did.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>I would like to see the WIMS model *extended*, not changed, to embrace modest groups of printers/MFDs managed from within, which is still a much more common deployment in our experience.  To support that model, I think we need to consider extensions such as polled management, event notification, service advertising, and resource discovery.  Scheduled, reverse-communications (benign Trojan horse) operations suitable for fleet management can be entirely layered on top of such a simpler model, I believe.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>Enough tirade for one day.  I apologize for its length.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>I cannot make the call this coming Wed., 6/15, sorry; out of town.  </FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=281403919-09062005><FONT face=Arial color=#0000ff>rick</FONT></SPAN></DIV> <DIV><FONT face=Arial color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff></FONT> </DIV> <DIV><BR></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma size=2><B>From:</B> Harry Lewis [mailto:harryl@us.ibm.com] <BR><B>Sent:</B> Wednesday, June 08, 2005 22:59<BR><B>To:</B> wamwagner@comcast.net<BR><B>Cc:</B> McDonald, Ira; Landau, Richard; thrasher@lexmark.com; wims@pwg.org<BR><B>Subject:</B> Re: Brief minutes from WIMS 8 June 2005<BR></FONT><BR></DIV> <DIV> </DIV><BR><FONT face=sans-serif size=2>Excellent response, Bill. I agree with getting the current Counter Spec (and WIMS... if possible) to CS w/o too much perturbation and building (into Enterprise mgt) from there... UNLESS... someone has some powerhouse recommendations that generate a great deal of new interest.</FONT> <BR><FONT face=sans-serif size=2>---------------------------------------------- <BR>Harry Lewis <BR>IBM STSM<BR>Chairman - IEEE-ISTO Printer Working Group<BR>http://www.pwg.org<BR>IBM Printing Systems <BR>http://www.ibm.com/printers<BR>303-924-5337<BR>---------------------------------------------- </FONT><BR><BR><BR> <TABLE width="100%"> <TBODY> <TR vAlign=top> <TD width="40%"><FONT face=sans-serif size=1><B>wamwagner@comcast.net</B> </FONT> <P><FONT face=sans-serif size=1>06/08/2005 05:46 PM</FONT> </P> <TD width="59%"> <TABLE width="100%"> <TBODY> <TR vAlign=top> <TD> <DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV> <TD><FONT face=sans-serif size=1>"McDonald, Ira" <imcdonald@sharplabs.com>, Harry Lewis/Boulder/IBM@IBMUS, "McDonald, Ira" <imcdonald@sharplabs.com>, thrasher@lexmark.com, Richard_Landau@Dell.com</FONT> <TR vAlign=top> <TD> <DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV> <TD><FONT face=sans-serif size=1>wims@pwg.org</FONT> <TR vAlign=top> <TD> <DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV> <TD><FONT face=sans-serif size=1>Re: Brief minutes from WIMS 8 June 2005</FONT></TD></TR></TBODY></TABLE><BR> <TABLE> <TBODY> <TR vAlign=top> <TD> <TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><FONT size=3>Rick's questions are interesting, and to an extent reflect the sort of capability that HP  wanted to include in WIMS, before they withdrew. </FONT><BR><FONT size=3> </FONT> <BR><FONT size=3>The answers to the questions are quite simply that WIMS was intended for fleet management, and was specifically aimed at increasing  the efficiency and potential market of companies like Danka and Ikon (and the service arms of several MFD manufacturers), which account for a vast number of multifuntion products in place today. Indeed, it appears that most small and midsized companies and indeed many large enterprises do not buy or maintain MFD products with internal resources.</FONT> <BR><FONT size=3> </FONT> <BR><FONT size=3>It was recognized that some of the capabilities included in WIMS would be useful for enterprise level management as well, and some features were added to support this application. With HPs sudden withdrawal from what had been active participation, the remaining members of the WG decided to concentrate on the original scope.</FONT> <BR><FONT size=3> </FONT> <BR><FONT size=3>If Dell or any other companies would like to expand the WIMS scope, I am sure the WG would be happy to support this. However, I want to follow through with the objective of getting the basic WIMS ideas in some recoverable form, probably a candidate specification. The additional features could be addressed by a subsequent document.</FONT> <BR><FONT size=3> </FONT> <SPAN class=281403919-09062005><FONT face=Arial color=#0000ff size=2>  </FONT></SPAN><BR><FONT size=3>It has turned out that, for whatever reason, we have been unable to get active participation from those companies that would most directly benifit from WIMS. On the other hand, manufacturers appear more interested in pursuing private solutions with the intent of locking customers into using their products. It would seem that a company that sold products OEM'ed from multiple manufacturers would prefer a standard solution. At any rate, it is with the belief that a standard means of facilitating third-party fleet management is needed and that this need will be recognized eventually that we wanted to document the fleed-management WIMS.</FONT> <BR><FONT size=3> </FONT> <BR><FONT size=3>Because third-party fleet management concerns are not generally trusted  with anything except the minimum information necessary to bill and maintain their equipment, many of the features that an enterprise management capability would want would need to be disabled for third-party fleet management.</FONT> <BR><FONT size=3> </FONT> <BR><FONT size=3>In direct answer to Rick's questions:</FONT> <BR><FONT size=3> </FONT> <BR><FONT size=3> (1) Why is the WIMS Protocol only explained in terms of the <BR>> Schedule and fleet management / firewall traversal? </FONT><BR><FONT size=3> - In facilitating third party management,  particularly for small sites, the intent was to utilize the existing network facilities and require a minimum installation activity. The approach taken was to use existing web access capability (with whatever protection the site normally provides for). </FONT><BR><FONT size=3>- The schedule approach reflects the premise that all communication is to be initiated by from the site. This supports both the use of an unaltered web access facility at the side, and the requirement that the site retains control over what what the manager has access to.</FONT> <BR><FONT size=3><BR>> <BR>> (2) Why isn't there a second top-level diagram showing the use <BR>> of WIMS _within_ an enterprise, specifically _without_ a <BR>> proxy (i.e., small network of WIMS-capable imaging systems)? </FONT><BR><FONT size=3> </FONT> <BR><FONT size=3>-This was one of the scenarios that was proposed by HP. See</FONT> <BR><A href="ftp://ftp.pwg.org/pub/pwg/wbmm/white/Use_Cases_7.pdf"><FONT color=blue size=3><U>ftp://ftp.pwg.org/pub/pwg/wbmm/white/Use_Cases_7.pdf</U></FONT></A><FONT size=3>, the basis for a requirements document, but now almost two years old. In refocusing the spec to the original intent, the operations that might be desirable to support this mode were dropped. Perhaps we should also have dropped any reference to the use of WIMS for internal management, but it was felt that WIMS does include features useful for this mode as well.</FONT> <BR><FONT size=3><BR>> <BR>> (3) For WIMS within an enterprise, the model of direct admin <BR>> preconfiguration of lots of WIMS Agents doesn't work. </FONT><BR><FONT size=3> </FONT> <BR><FONT size=3>- WIMS specifically did not include either service advertizing or discovery. The third party fleet model, such capabilities would be a security risk. The intent was that the right to obtain information from a service must be initiated at the site; indeed, all communication must be initiated from the site. For internal management, other protocols exist to allow discovery. SLP and LDAP might be good choices. UPNP would seem to be inapplicable.<BR>> <BR>> (3a) What protocols for service advertising (SLP, UPnP) <BR>> should a WIMS Agent use? </FONT><BR><FONT size=3> </FONT> <BR><FONT size=3>> <BR>> (3b) What protocols for service discovery (SNMP Ping, LDAP, <BR>> DNS-SD, UDDI) should a WIMS Manager use? <BR>> <BR>> (4) How can a WIMS Manager immediately begin management of a <BR>> WIMS Agent (i.e., where is the Management Interface operation <BR>> 'BeginManagement')? </FONT><BR><FONT size=3>- Again, the premise is that a manager cannot begin management of a device until that device has directly or indirectly (through a proxy) granted the manager that right. </FONT><BR><FONT size=3> </FONT> <BR><FONT size=3>Bill Wagner, Chairman, WIMS</FONT> <BR><FONT size=3>-------------- Original message -------------- <BR><BR>> Hi, <BR>> <BR>> [This just _bounced_ from 'wims@pwg.org' - huh?] <BR>> <BR>> Only Rick Landau (Dell) and I called in today. While we waited <BR>> for ephemeral others, Rick asked some questions about the WIMS <BR>> Protocol itself: <BR>> <BR>> (1) Why is the WIMS Protocol only explained in terms of the <BR>> Schedule and fleet management / firewall traversal? <BR>> <BR>> (2) Why isn't there a second top-level diagram showing the use <BR>> of WIMS _within_ an enterprise, specifically _without_ a <BR>> proxy (i.e., small network of WIMS-capable imaging systems)? <BR>> <BR>> (3) For WIMS within an enterprise, the model of direct admin <BR>> preconfiguration of lots of WIMS Agents doesn't work. <BR>> <BR>> (3a) What protocols for service advertising (SLP, UPnP) <BR>> should a W! IMS Agent use? <BR>> <BR>> (3b) What protocols for service discovery (SNMP Ping, LDAP, <BR>> DNS-SD, UDDI) should a WIMS Manager use? <BR>> <BR>> (4) How can a WIMS Manager immediately begin management of a <BR>> WIMS Agent (i.e., where is the Management Interface operation <BR>> 'BeginManagement')? <BR>> (This assumes that an LDAP or Kerberos user identity (e.g.) <BR>> already exists for both the WIMS Manager and WIMS Agent.) <BR>> <BR>> Good questions that need clear answers in the spec. <BR>> <BR>> I'd like to note that Rick feels that Dell wouldn't consider <BR>> deployment of WIMS for enterprise service management based on <BR>> the Schedule-centric fleet management operations sequences. <BR>> <BR>> Rick volunteered to write paragraphs describing solutions to <BR>> some of the above questions for addition to the spec. At present, <BR>> Rick can't volunteer to be the principal editor of the WIMS spec. <BR>> > In the interests of encouraging actual deployment of WIMS, I <BR>> agree with Rick that the spec should support both models <BR>> (enterprise and fleet management)? <BR>> <BR>> Same time next week - Wednesday 15 June <BR>> <BR>> Call-in US Toll-free: 1-866-365-4406 <BR>> Call-in International/Toll: 1-303-248-9655 <BR>> Participant Identification number: 2635888# <BR>> <BR>> Cheers, <BR>> - Ira <BR>> <BR>> <BR>> Ira McDonald (Musician / Software Architect) <BR>> Blue Roof Music / High North Inc <BR>> PO Box 221 Grand Marais, MI 49839 <BR>> phone: +1-906-494-2434 <BR>> email: imcdonald@sharplabs.com <BR>> <BR>> Ira McDonald (Musician / Software Architect) <BR>> Blue Roof Music / High North Inc <BR>> PO Box 221 Grand Marais, MI 49839 <BR>> phone: +1-906-494-2434 <BR>> email: imcdonald@sharplabs.com <BR>> <BR>> -----Original Message----- <BR>> From: Harry Lewis [mailto:harryl@us.ibm.com] <BR>> Sent: Wednesday, June 08, 2005 3:33 PM <BR>> To: imcdonald@shar! plabs.com; thrasher@lexmark.com; wamwagner@comcast.net; <BR>> Richard_Landau@Dell.com <BR>> Subject: Sorry I missed WIMS call today - will be available next week <BR>> <BR>> <BR>> <BR>> Sorry, after posting my warning to you folks... I ended up in a strategic <BR>> customer briefing that I just could not escape from. <BR>> I have had to postpone my vacation for business reasons which should make me <BR>> available for a call on the 15th (I'd previously begged off that one). <BR>> Was there a call today? Minutes? <BR>> ---------------------------------------------- <BR>> Harry Lewis <BR>> IBM STSM <BR>> Chairman - IEEE-ISTO Printer Working Group <BR>> http://www.pwg.org <BR>> IBM Printing Systems <BR>> http://www.ibm.com/printers <BR>> 303-924-5337 <BR>> ---------------------------------------------- </FONT><BR></BLOCKQUOTE></BODY></HTML>