Re: draft-ietf-entmib-sensor-mib-02.txt

Bob Burget <[email protected]>
Newsgroups gmane.ietf.entmib
Organization MSSBU WAN Engineering
Message-ID <[email protected]>
The changes I proposed are largely editorial, but I believe they
would significantly improve the usability of the MIB.

The technical problems with this MIB are limited to current users
and implementors of Cisco products. Since much of this MIB seems
to have been copied from a previously used Cisco proprietary MIB,
the the re-used names of the objects cause the MIB to be very
difficult to implement by those who have already implemented the
previous MIB. Since the existing MIB eclipses the proposed MIB
with additional features and capability, the obvious solution is
not to implement the new IETF MIB at all. This is less than ideal
for all concerned, so I proposed to enhance the new MIB's names.


 Thanks for your consideration,

   Bob B.

Margaret Wasserman wrote:
> 
> Hi Bob,
> 
> The sensor MIB has already been approved by the IESG for publication
> as a Proposed Standard RFC.  So, it is too late in the process to
> make editorial or non-critical changes to the document.  I have looked
> through your proposed changes, and they appear to be editorial in
> nature.
> 
> If you believe that the issues that you have raised represent serious
> technical problems that would make it difficult to implement this MIB
> and/or use it for its primary purpose, please explain further.
> 
> Thanks,
> Margaret
> 
> At 09:15 PM 10/4/02, Bob Burget wrote:
> >Dear IETF Working Group;
> >
> >I have recently become aware that a new MIB for physical sensors,
> >(as defined by an entPhysicalClass value of 'sensor(8)') has been
> >proposed for the IETF standards track.
> >
> >I request that the MIB text be modified to include some indication
> >in the object descriptors that this MIB is for Physical entities.
> >I hope to ensure that the relationship between the proposed MIB
> >and the entPhysicalTable in the ENTITY-MIB is clarified.
> >A similar case for reference is the existing entPhysicalContainsTable
> >which also has the entPhysicalIndex as its INDEX.
> >
> >Attached is a text file that shows how this can be done.
> >Please let me know if there would be any problems with this.
> >
> >    Thanks,
> >
> >--
> >    Bob Burget, [email protected]

-- 
   Bob Burget, [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.