Ira,
You know better than that! Of course I want to make MIBs USEFUL. However,
continuing to put bandaides on a bleeding patient does not make that patient
well. There are some serious peformance and usability issues with this
approach for doing job monitoring which I feel obligated to point out. For
example, as of yet, no one has addressed the issue of the semantics of
having multiple values.
It won't do any good to just harp at me. My concerns warrent being
addressed in a profession and civilized manner!
Mike
> -----Original Message-----
> From: Ira McDonald [mailto:imcdonal at sdsp.mc.xerox.com]
> Sent: Tuesday, June 29, 1999 10:53 AM
> To: Joe.Filion at usa.xerox.com; Mike.Elvers at usa.xerox.com;
>imcdonal at sdsp.mc.xerox.com> Cc: Angelo.Caruso at usa.xerox.com; hastings at cp10.es.xerox.com;
>jmp at pwg.org> Subject: RE: JMP> FW: Document Action: Job Monitoring MIB - V1 to
> Informat ional
>>> Hi Mike,
>> OK - I see that you don't want to get a useful method for
> accessing attribute-based MIBs. I think this is unfortunate,
> because (among other things) LDAP and SLP are becoming common
> in deployment and they have 'open-ended' objects which have a
> (few) Mandatory attributes and a (lot of) Optional attributes.
>> My work in the XCMI Comms Config MIB since last December on
> the Comms Directory Record and Comms Directory Attribute/String
> tables allows a direct representation in the MIB of an LDAP
> or SLP 'named object' with a bunch of attributes. We can't
> possibly constrain the accesses of Xerox network devices to
> rigid sets of mandatory attributes in LDAP objects, so I was
> hoping for more refinement to arise here on the PWG Job Mon
> MIB that was useful in the XCMI CC Directory, HRX Device Detail,
> and Svc Mon Service Detail applications.
>> I realize that 'jobs' (because they are very dynamic in their
> attributes present and attribute values over short intervals)
> are quite different from essentially all 'resource' objects
> (servers, repositories, etc). There are many more 'jobs'
> of interest and they have to be presented to the end user
> in a GUI because they ARE dynamic.
>> I hope we can work to make use of the HRX and Svc Mon Detail
> groups and the newer CC Directory groups as useful as possible
> to SNMP agent implementors as well as native and Web client
> implementors.
>> Cheers,
> - Ira
>>