Subject: [Isis-wg] Minor comments on draft-ietf-isis-wg-mib-13.txt
From: Jeff Parker <[email-masked]>
To: "[email-masked]'" <[email-masked]>, [email-masked], Jeff Parker <[email-masked]>, [email-masked]
Date: Mon, 5 Apr 2004 16:21:47 -0400
List-Id: IETF IS-IS working group <isis-wg.ietf.org>

More private comments on the Mib: the issue of Corrupted LSP and
AuthFailures.  Relevant portions of mib are below.  

1) The isisCorruptedLSPDetected states that it is to announce the detection
of an in-mmeory corruption.  I have found it much more useful to announce
the detection of on-the wire corrupted LSPs.  

Proposal: 
	A) modify the Description to include Corrupted LSPs found on the
wire
	B) modify the object to include the isisCircIfIndex where we found
the packet.  If the LSP is really corrupted, the sysid would be suspect.  

2) For isisAuthenticationTypeFailure and isisAuthenticationFailure, we
include the packet header, level, and circ index.  Would it be useful to
include the packet type?  While this is contained in the PDU fragment, it
may help developers working on trap handlers to know the packet type.  If
so, do we want all packet types, or just to distinguish between hello
packets and the rest, as the authenetication for these packets are
configured differently.

Proposal: Add an object to both Auth Traps that will ease dispatching on
packet type.  

- jeff parker

    isisCorruptedLSPDetected NOTIFICATION-TYPE
        OBJECTS {
            isisSysInstance,
            isisSysLevelIndex,
            isisPduLspId
        }
        STATUS current
        DESCRIPTION
            "This notification is generated when we find that
             an LSP that was stored in memory has become
             corrupted.  The number of times this has been
             generated is counted by isisSysCorrLSPs.

             We forward an LSP ID.  We may have independent
             knowledge of the ID, but in some implementations
             there is a chance that the ID itself will be
             corrupted."

    ::= { isisTrapPrefix 3 }

    isisAuthenticationTypeFailure NOTIFICATION-TYPE
        OBJECTS {
            isisSysInstance,
            isisSysLevelIndex,
            isisCircIfIndex,
            isisPduFragment
        }
        STATUS current
        DESCRIPTION
            "A notification sent when we receive a PDU
             with the wrong authentication type field.
             This notification includes the header of the
             packet, which may help a network manager
             identify the source of the confusion.

             This should be an edge-triggered notification.
             We should not send a second notification about
             PDUs received from what seem to be the same source."

    ::= { isisTrapPrefix 9 }

    isisAuthenticationFailure NOTIFICATION-TYPE
        OBJECTS {
            isisSysInstance,
            isisSysLevelIndex,
            isisCircIfIndex,
            isisPduFragment
        }
        STATUS current
        DESCRIPTION
            "A notification sent when we receive a PDU
             with incorrect authentication information
             field.  This notification includes the header
             of the packet, which may help a network manager
             identify the source of the confusion.

             This should be an edge-triggered notification.
             We should not send a second notification about
             PDUs received from what seem to be the same source."

    ::= { isisTrapPrefix 10 }

- jeff parker
- axiowave networks
- As scarce as truth is, the supply has always been in excess of the demand
- Josh Billings

_______________________________________________
Isis-wg mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/isis-wg