Right, I agree... this is how I see it, also which is why I'm surprised
that there is contention about this fitting within the (proposed) Charter.
----------------------------------------------
Harry Lewis
IBM Printing Systems
----------------------------------------------
"MARKLE,CATHY (HP-Boise,ex1)" <cathy_markle at hp.com>
02/07/2003 01:16 PM
To: Harry Lewis/Boulder/IBM at IBMUS, wbmm at pwg.org
cc:
Subject: RE: WBMM> Differences
Harry,
I see your second option as they way to solve the first option. This
doesn't make them two different problems. It seems to me that maybe
management/monitoring through the firewall is the charter and using SOAP
and XML in a device is the scope/requirement on how to do this. Of
course, for legacy devices with SNMP, there will need to be a proxy to
handle this. I'm not sure that I'm using the terminology for scope and
requirement correctly but this is how I see the problem resolved.
Cathy
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Friday, February 07, 2003 12:41 PM
To: wbmm at pwg.org
Subject: WBMM> Differences
I'd like to try and resolve some of the (unfortunate) differences we are
having regarding Charter, Scope, Requirements.
>From what I can decipher, there is a well established interest in solving
the problem "I've been getting at my (device) management data remotely,
within my enterprise just fine... but, now, how can I access it across the
firewall" (maybe to provide services to multiple enterprises etc.).
Others also want to solve... "... and what is the standard protocol and
data model that lends itself to the web services environment that may be
employed by proxy servers and/or directly in the embedded device".
Of course, we will have legacy SNMP devices to manage for quite some time
but I don't think the current existence of SNMP is the answer to the 2nd
question.
----------------------------------------------
Harry Lewis
IBM Printing Systems
----------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20030207/00ab0543/attachment-0001.html