Trap conventions

Michael Shurman <michael@lannet.com> Fri, 28 February 1992 08:48 UTC

Received: from nri.nri.reston.va.us by ietf.ietf.NRI.Reston.VA.US id aa08587; 28 Feb 92 3:48 EST
Received: from [192.33.4.17] by NRI.NRI.Reston.VA.US id aa01420; 28 Feb 92 3:48 EST
Received: by lists.psi.com (5.61/2.1-PSINet Operations ) id AA28577; Fri, 28 Feb 92 02:36:07 -0500
Received: from uu.psi.com by lists.psi.com (5.61/2.1-PSINet Operations ) id AA28481; Fri, 28 Feb 92 02:29:18 -0500
Received: from batcher.psi.com by uu.psi.com (5.65b/4.1.011392-PSI/PSINet) id AB19149; Fri, 28 Feb 92 02:27:40 -0500
Received: from lannet.com (lannet.com.3.84.192.in-addr.arpa) by batcher.psi.com (4.0/3.1.072291-PSI/PSINet) id AA11158; Thu, 27 Feb 92 13:07:53 EST
Received: from moon.lannet.com ([149.49.50.12]) by lannet.com (4.1/3.1.090690-Lannet Data Communications) id AA01422; Thu, 27 Feb 92 17:05:11 IST
Received: from jerusalem.lannet.com by moon.lannet.com (4.1/SMI-4.1) id AA26754; Thu, 27 Feb 92 17:09:18 IST
Date: Thu, 27 Feb 1992 17:09:17 -0000
From: Michael Shurman <michael@lannet.com>
Message-Id: <9202271509.AA26754@moon.lannet.com>
To: snmp@uu.psi.com
Subject: Trap conventions

Hi everybody,

The RFC1215 defines:

* 2.1.1.  Mapping of the ENTERPRISE clause
* 
*    The ENTERPRISE clause, which must be present, defines the management
*    enterprise under whose registration authority this trap is defined
*    (for a discussion on delegation of registration authority, see the
*    SMI [3]).  This value is placed inside the enterprise field of the
*    SNMP Trap-PDU.
* 
*    By convention, if the value of the ENTERPRISE clause is
* 
* SNMP Working Group                                              [Page 3]
* RFC 1215             Convention for Defining Traps            March 1991
* 
* 
*                 snmp   OBJECT IDENTIFIER ::= { mib-2 11 }
* 
*    as defined in MIB-II [7], then instead of using this value, the value
*    of sysObjectID is placed in the enterprise field of the SNMP Trap-
*    PDU.  This provides a simple means of using the TRAP-TYPE macro to
*    represent the existing standard SNMP traps; it is not intended to
*    provide a means to define additional standard SNMP traps.

I see some problems with this definition for experimental MIB's.
Assume we use Bridge MIB which defines:

*          newRoot TRAP-TYPE
*              ENTERPRISE  dot1dBridge
*              DESCRIPTION
*                      "The newRoot trap indicates that the sending agent
*                      has become the new root of the Spanning Tree; the
*                      trap is sent by a bridge soon after its election
*                      as the new root, e.g., upon expiration of the
*                      Topology Change Timer immediately subsequent to
*                      its election."
*              ::= 1
* 
*          topologyChange TRAP-TYPE
*              ENTERPRISE  dot1dBridge
*              DESCRIPTION
*                      "A topologyChange trap is sent by a bridge when
*                      any of its configured ports transitions from the
*                      Learning state to the Forwarding state, or from
*                      the Forwarding state to the Blocking state.  The
*                      trap is not sent if a newRoot trap is sent for the
*                      same transition."
*              ::= 2

if we will put sysObjectID in the enterprise field how one will know 
that a trap belong to the Bridge MIB? What will be the trap type ?
What will be fate of these traps once the Bridge MIB will become 
standard ? Will these traps become new SNMP standard traps ( 7 and 8 ?) ?

Please send me responses to lannet.hellnet.org ( not lannet.com ! )