WBMM> Scope and Starting Point Conference call

WBMM> Scope and Starting Point Conference call

WBMM> Scope and Starting Point Conference call

ElliottBradshaw at oaktech.com ElliottBradshaw at oaktech.com
Wed Feb 26 15:47:15 EST 2003


I think your document is a good start.  The scenarios are more or less
described at the right level for this discussion.  I am confused, however,
about the difference between Scenarios 1 and 2.  Aren't they both part of
the same story?

The firewall issue is, of course, critical.  Whatever we do has to be
acceptable to the majority of IT groups, and we should test that.  Maybe we
should each ask our local IT folks whether they would allow a printer that
automatically talks to an external server, and whether their answer depends
on the selection of port #, type of data traffic, etc.  If we find major
resistance to the idea, then we should stop.  This is the issue that drives
the HTTP questions, and I can't imagine any non-HTTP scheme that would be

With regard to SNMP compatibility, my sense is you have picked up on the
most useful scenarios for the the Printer MIB.  I think WBMM should align
with Printer MIB wherever it makes sense, but I would not start with a
fundamental requirement that everything Printer MIB can do can also be done
by WBMM.  We may end up re-implementing some pretty rarely used functions,
and we can always add them in later.

I'm not sure I follow the discussion of semantics, but we do want a scheme
that provides interoperability.  That means we have to describe the actual
encoding of each operation.  So, I think that does mean we do need to nail
the basic semantics.  It seems reasonable to do this using SM, although
this is not a fundamental requirement if some other approach solves the

Control over allowed operations will be important.  I can imagine an IT
department that allows alerts but not file transfers, and certainly not the
more operational actions like going on or offline, if we decide to include
them.  We should treat this as a primary requirement, with questions of
granularity, grouping, etc. to come later.

See you (?) at the teleconference...


Elliott Bradshaw
Director, Software Engineering
Oak Technology Imaging Group
781 638-7534

                    m"                   To:     "'Wbmm (E-mail)" <wbmm at pwg.org>               
                    <WWagner at NetSi       cc:                                                   
                    licon.com>           Subject:     WBMM> Scope and Starting Point           
                    Sent by:              Conference call                                      
                    owner-wbmm at pwg                                                             
                    03:06 PM                                                                   


I have received several messages indicating that 4 March 4-5 PM EST (1-2
PST)  would be a good time for a conference call. There were also some
suggestions that  we establish a list of issues and try to get as many
issues a possible resolved before the conference call. There has been some
discussion of issues in the message I sent on Friday, and I solicit more
comments. I will come up with a preliminary list of issues with discussion
and an agenda later this week, and an updated agenda next Monday. Please
forward your concerns and issues to the list or to me for inclusion.

This is a simple telephone conference call. Parameters are:

    Time: 4:00 PM 4 March 2003

    Call-in US: 1-877-628-1350

    Call-in International: 1-712-421-1160

    Participant Identification number: 415259

Best regards,

Bill Wagner/NetSilicon, a Digi International Company

More information about the Wims mailing list