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.1400" name=GENERATOR></HEAD> <BODY> <DIV>Correct. That is the way it is described in the spec. The notion is that only a  device  which has been configured  to be managed can be managed, only by the Management station to which  it has been configured.</DIV> <DIV> </DIV> <DIV>Bill Wagner</DIV> <DIV> </DIV> <DIV> -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Monday, May 03, 2004 3:59 PM To: Wagner,William Cc: wbmm@pwg.org Subject: RE: WBMM> Setting the Schedule </DIV> <BLOCKQUOTE> I'm just thinking about the firewall. 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? ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- <TABLE width="100%"> <TBODY> <TR vAlign=top> <TD width="40%">"Wagner,William" <WWagner@NetSilicon.com> Sent by: owner-wbmm@pwg.org 05/03/2004 01:09 PM <TD width="59%"> <TABLE width="100%"> <TBODY> <TR> <TD> <DIV align=right>To</DIV> <TD vAlign=top>Harry Lewis/Boulder/IBM@IBMUS, <wbmm@pwg.org> <TR> <TD> <DIV align=right>cc</DIV> <TD vAlign=top> <TR> <TD> <DIV align=right>Subject</DIV> <TD vAlign=top>RE: WBMM> Setting the Schedule</TR></TBODY></TABLE> <TABLE> <TBODY> <TR vAlign=top> <TD> <TD></TR></TBODY></TABLE> </TR></TBODY></TABLE> Harry,   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.     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.   Of course, if you  want to implement an SNMP based protocol, that's fine.  But the SetSchedule  operation is optional.   For either binding,  the remote management is  enabled by  the RegisterforMnagement operation. Bill Wagner      -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Monday, May 03, 2004 1:36 P To: wbmm@pwg.org Subject: WBMM> Setting the Schedule 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. ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- </BLOCKQUOTE></BODY></HTML>