attachment-0001

<!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.1276" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>Hi Harry,</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>I agree with Bill.  An Agent on a Managed Entity must be configured to be </FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>managed </FONT></SPAN><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>by a particular outside the firewall Manager (Mgmt Station).</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>And, we plan to make the return of RegisterForManagement be a Schedule</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>(eliminating the separate GetSchedule, now only needed to complete an</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>embedded UpdateSchedule action in an existing Schedule).</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>The SetSchedule will probably always remain OPTIONAL and not REQUIRED.</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>The IEEE P2600 effort would certainly recommend this.</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>Cheers,</FONT></SPAN></DIV> <DIV><SPAN class=711482522-03052004><FONT face=Arial color=#0000ff size=2>- Ira</FONT></SPAN></DIV> <DIV> </DIV> <P><FONT size=2>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</FONT> </P> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Wagner,William [mailto:WWagner@NetSilicon.com]<BR><B>Sent:</B> Monday, May 03, 2004 4:08 PM<BR><B>To:</B> Harry Lewis<BR><B>Cc:</B> wbmm@pwg.org<BR><B>Subject:</B> RE: WBMM> Setting the Schedule<BR><BR></FONT></DIV> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=293060520-03052004>Correct. That is the way it is described in the spec.</SPAN> <SPAN class=293060520-03052004>The notion is that only a  device  which has been configured  to be managed can be managed, only by the </SPAN>M<SPAN class=293060520-03052004>anagement station to which  it has been configured.</SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=293060520-03052004></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=293060520-03052004>Bill Wagner</SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2></FONT></FONT></FONT> </DIV> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=293060520-03052004> </SPAN></FONT></FONT></FONT><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Harry Lewis [mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Monday, May 03, 2004 3:59 PM<BR><B>To:</B> Wagner,William<BR><B>Cc:</B> wbmm@pwg.org<BR><B>Subject:</B> RE: WBMM> Setting the Schedule<BR><BR></DIV></FONT> <BLOCKQUOTE><BR><FONT face=sans-serif size=2>I'm just thinking about the firewall. </FONT><BR><BR><FONT face=sans-serif size=2>You are saying, somehow, the Management Station is somehow discovered and/or administratively configured, the Agent (in the enterprise proxy... let's say) performs a RegisterForManagement operation (which does pass the firewall) and, if a valid response is received from the Manager, then the Agent performs a GetSchedule operation. Right?</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><BR><BR><BR> <TABLE width="100%"> <TBODY> <TR vAlign=top> <TD width="40%"><FONT face=sans-serif size=1><B>"Wagner,William" <WWagner@NetSilicon.com></B> </FONT><BR><FONT face=sans-serif size=1>Sent by: owner-wbmm@pwg.org</FONT> <P><FONT face=sans-serif size=1>05/03/2004 01:09 PM</FONT> </P> <TD width="59%"> <TABLE width="100%"> <TBODY> <TR> <TD> <DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV> <TD vAlign=top><FONT face=sans-serif size=1>Harry Lewis/Boulder/IBM@IBMUS, <wbmm@pwg.org></FONT> <TR> <TD> <DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV> <TD vAlign=top> <TR> <TD> <DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV> <TD vAlign=top><FONT face=sans-serif size=1>RE: WBMM> Setting the Schedule</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 face=Arial color=blue size=2>Harry,</FONT> <BR><FONT size=3> </FONT> <BR><FONT face=Arial color=blue 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> <BR><FONT size=3> </FONT> <BR><FONT face=Arial color=blue 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> <BR><FONT size=3> </FONT> <BR><FONT face=Arial color=blue size=2>Of course, if you  want to implement an SNMP based protocol, that's fine.  But the SetSchedule  operation is optional.</FONT> <BR><FONT size=3> </FONT> <BR><FONT face=Arial color=blue size=2>For either binding,  the remote management is  enabled by  the Register</FONT><FONT face=Tahoma size=2>forMnagement operation.</FONT> <BR><FONT face=Tahoma size=3><BR></FONT><BR><FONT face=Arial color=blue size=2>Bill Wagner</FONT> <BR><FONT face=Tahoma size=3> </FONT> <BR><FONT face=Tahoma size=3> </FONT> <BR><FONT face=Tahoma size=2> -----Original Message-----<B><BR>From:</B> Harry Lewis [mailto:harryl@us.ibm.com]<B><BR>Sent:</B> Monday, May 03, 2004 1:36 P<B><BR>To:</B> wbmm@pwg.org<B><BR>Subject:</B> WBMM> Setting the Schedule<BR></FONT><BR><FONT face=sans-serif size=2><BR>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><FONT size=3> </FONT><FONT face=sans-serif size=2><BR>---------------------------------------------- <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><BR></BLOCKQUOTE></BODY></HTML>