Re: something to read

[Jon Saperia <saperia@jdscons.com>]

Juergen,

There are some valuable lessons to be learned from the
process. Unfortunately statements like:

> Acknowledgments
> 
>    The author would like to thank all the people who were involved in
>    this silly project over the years for their optimism and patience,
>    misguided though it may have been.
> 

suggest problems not listed. They suggest an attitude of members of the
WG and the community to some extent about management and SNMP. There are
in fact vendor implementations of some important portions of the two MIB
modules described and there is work underway investigating a
revision. From what I can tell, vendor self-interest has held up progress
in re-consolidation of the variations. This problem exists through the
MIB namespace. Specifically that there are standards which are
implemented in the private space of vendors or slightly modified and
implemented in the private space of vendors. This particular problem is
not technical at all and has nothing to do with SNMP-based technology.

Workable extensible agent technology in the public domain did hur. The
SMI is a small issue. Complicated 'databases' like the DNS will
necessarily have complicated indices. There are things to be done to
help with this, but I do not think it was ever a real show stopper in
terms of implementation while the extensible agent issues were more
problematic.

Just FYI, I have commented several times about the language in the
document and it appears to have remained unchanged. One important lesson
learned is that management technology of any type can not be forced on
people who do not want it or see a need for it.

> 
> For those of you who are doing MIBs and who have not seen it yet, I
> recommend to take a few seconds to look at the following document.
> 
> <draft-ietf-dnsext-dnsmib-historical-00.txt>
> 
> /js
> 
> 

Thanks,
/jon
--

Jon Saperia		     saperia@jdscons.com
			     Phone: 617-744-1079
			     Fax:   617-249-0874
			     http://www.jdscons.com/