Hi Harry,
I agree with Bill. An Agent on a Managed Entity must be configured to be
managed by a particular outside the firewall Manager (Mgmt Station).
And, we plan to make the return of RegisterForManagement be a Schedule
(eliminating the separate GetSchedule, now only needed to complete an
embedded UpdateSchedule action in an existing Schedule).
The SetSchedule will probably always remain OPTIONAL and not REQUIRED.
The IEEE P2600 effort would certainly recommend this.
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: Wagner,William [mailto:WWagner@NetSilicon.com]
Sent: Monday, May 03, 2004 4:08 PM
To: Harry Lewis
Cc: wbmm@pwg.org
Subject: RE: WBMM> Setting the Schedule
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.
Bill Wagner
-----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
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
----------------------------------------------
"Wagner,William" <WWagner@NetSilicon.com>
Sent by: owner-wbmm@pwg.org
05/03/2004 01:09 PM
To
Harry Lewis/Boulder/IBM@IBMUS, <wbmm@pwg.org>
cc
Subject
RE: WBMM> Setting the Schedule
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
----------------------------------------------
This archive was generated by hypermail 2b29 : Mon May 03 2004 - 18:29:07 EDT