Re: FddiTime, and update to Path config table

[Ahmet Tuncay <[e-mail]>]

Anil wrote:

    As a matter of curiosity: does your nms have specific knowledge of fddi/
    do you have an application rather than a vanilla nms with compiler.

    Please don't rigidly stick to "consistency" as a reason on this type
    of issue.  The ANSI folks made fddi work.  The job this forum is trying
    to get done is make it manageable, from the point of view of a network
    manager rather than that of an implementor. 

I would like to ask if you seriously think that FDDI can be managed using a
generic SNMP manager without specific knowledge of FDDI???  What do your 
users think about hundreds of useless objects scrolling down in their
screens??  Have you though about how an SNMP to SMT proxy should work??

    The former could
    care less about how times are internally represented.  Consistency
    is important to the extent that the protocol specified is adequately
    instrumented.  I would argue that a range of half what is required is
    more of a consistency problem.

This is largely true, however, you haven't made the case of why it should
be changed to something in-consistent with how things are actually 
instrumented to make the media protocol work :-).

    I was involved in a mib where time was represented in 1/256 seconds in the
    relevant IEEE standard!  We changed over to a more human-readable format.
    Mibs ought be reasonably usable without higher level applications or
    special features.

    Anyway, the vote is 3-1 against making this change so far and there
    are bigger and better issues yet to be resolved on this mib, so
    let's move on! :-)

Let's change the vote.

    Anil

Ahmet Tuncay
[e-mail]