[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Methods in the NIM requirements



> Let me cite an example outside of the management domain. Lets use routing
> protocols - standards right. We can all point to the RFCs, but for a router
> to not be bug for bug compatible with Cisco is a fatal flaw.

I know of some products which are "bug for bug compatible with Cisco",
and we're trying to fix them :-).

> Other examples
> in the management area are, vendors claiming compliance with a standard that
> has been inadequately/incompletely specified. Many MIB modules that are
> standards-track RFCs represent the least common denominator. Vendors claim
> compliance with them, yet have large proprietary MIB modules for all the
> good stuff.

The only way that standard MIBs could get close to 100% coverage would
be for all vendors' products to be exactly the same.  Except for "clone"
markets, it is the nature of business that vendors try to differentiate
their products by making them different.  The purpose of standard
protocols is to make different products interoperate, not to make all
products the same.  So, while not having 100% coverage does make it harder
to write management applications, it's always going to be like that,
and the desires of network/policy management is not going to change it.

Keith.