RE: Fw: I-D ACTION:draft-yadawad-disman-ahcf-00.txt
"Romascanu, Dan (Dan)" <[email protected]>
| Newsgroups | gmane.ietf.disman |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F038A9C8A@is0004avexu1.global.avaya.com> |
> > > operations/management functions this MIB module provides that are > > not covered by existing MIB modules. > ... > > To the extent that the script MIB supports languages that are Turing > complete, one could reasonably argue that all other MIBs are > superfluous. > Of course, a problem with such a line of argument would be the > amount of pain required to use such a system. That is why > the expression > MIB and the script MIB were both put out as Proposed Standards. > > The motivation for the expression MIB was that it was supposed to be > simpler to implement and use. Whether it adequately met those > criteria is being questioned. From my perspective it looks like > draft-yadawad-disman-ahcf-00.txt presents another factoring of > the problem. I am far from convinced that it is *the* solution, but > (as WG chair) I think it's appropriate to include it in the discussion > of whether the expression MIB requires some re-thinking. > I was not going that far, and actually I did not have the expression MIB in mind. What I am seeing are mechanisms like RMON alarm and usrHistory being reinvented, and objects like ituSeverity from the Alarm MIB being duplicated. Dan > Randy > > > >