attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2>Harry,</FONT></SPAN></DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2>That is one mode, but I would not  say that  it is the main mode  since it  is an optional  operation. We have agreed that SOAP can use either  SMTP   or  HTTP.  The SetSchedule operation (to  my mind) make  sense primarily in an entirely email oriented implementation.  </FONT></SPAN></DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2>In many cases, MFPs  are not managed by the IP  group and an easy,  non-IT dependent mode  of operation is desirable.  Having to  set up a mail account  for every printer is a bother (although this can be reduced by using a proxy).  Using the  basic terminal web access is  generally easier and  involves  less  people in an organization.</FONT></SPAN></DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2>Of course, if you  want to implement an SNMP based protocol, that's fine.  But the SetSchedule  operation is optional.</FONT></SPAN></DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff size=2>For either binding,  the remote management is  enabled by  the Register<FONT face=Tahoma color=#000000>forMnagement operation.</FONT></FONT></SPAN></DIV><SPAN class=415074818-03052004></SPAN><FONT face=Tahoma> <DIV><BR><FONT size=2><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff></FONT></SPAN></FONT> </DIV> <DIV><FONT size=2><SPAN class=415074818-03052004><FONT face=Arial color=#0000ff>Bill Wagner</FONT></SPAN></FONT></DIV> <DIV><FONT size=2><SPAN class=415074818-03052004></SPAN></FONT> </DIV> <DIV><FONT size=2><SPAN class=415074818-03052004></SPAN></FONT> </DIV> <DIV><FONT size=2><SPAN class=415074818-03052004> </SPAN>-----Original Message-----<BR><B>From:</B> Harry Lewis [mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Monday, May 03, 2004 1:36 P<BR><B>To:</B> wbmm@pwg.org<BR><B>Subject:</B> WBMM> Setting the Schedule<BR><BR></DIV></FONT></FONT> <BLOCKQUOTE><BR><FONT face=sans-serif size=2>I want to reaffirm that the (main) mode we are anticipating for getting a schedule set in a managed entity is for the Manager, using SMTP, to send a SetSchedule operation which includes a UpdateSchedule Action in the Schedule... whereby the Agent will perform a GetSchedule.</FONT> <BR><FONT face=sans-serif size=2>---------------------------------------------- <BR>Harry Lewis <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></BLOCKQUOTE></BODY></HTML>