Re: Review comments on draft-ietf-bridge-bridgemib-smiv2-07.txt

On Fri, Dec 31, 2004 at 10:48:40AM -0800, C. M. Heard wrote:
 
> > If we can do this, it would move the mib up under mib-2, and eliminate
> > the forward reference (issue #757). 
> > It would also place the object and notification subtrees under the
> > dot1dBridge MODULE-IDENTITY, approximating the recommended practices
> > from draft-ietf-ops-mib-review-guidelines Suggested OID layout. 
> 
> All of these sound to me like Good Things.

I have applied the changes. Here is the current tree structure:

  --dot1dBridge(1.3.6.1.2.1.17)		# MODULE-IDENTITY
    +--dot1dNotifications(0)
    +--dot1dBase(1)
    +--dot1dStp(2)
    +--dot1dSr(3)
    +--dot1dTp(4)
    +--dot1dStatic(5)
    +--dot1dConformance(8)
       +--dot1dGroups(1)
       +--dot1dCompliances(2)

And this is the relevant part of the MIB module:

  -- ---------------------------------------------------------- --
  -- subtrees in the Bridge MIB
  -- ---------------------------------------------------------- --

  dot1dNotifications  OBJECT IDENTIFIER ::= { dot1dBridge 0 }

  dot1dBase           OBJECT IDENTIFIER ::= { dot1dBridge 1 }
  dot1dStp            OBJECT IDENTIFIER ::= { dot1dBridge 2 }

  dot1dSr             OBJECT IDENTIFIER ::= { dot1dBridge 3 }
  -- documented in RFC 1525

  dot1dTp             OBJECT IDENTIFIER ::= { dot1dBridge 4 }
  dot1dStatic         OBJECT IDENTIFIER ::= { dot1dBridge 5 }

  -- Subtrees used by Bridge MIB Extensions:
  --      pBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 6 }
  --      qBridgeMIB  MODULE-IDENTITY   ::= { dot1dBridge 7 }
  -- Note that the practice of registering related MIB modules
  -- below dot1dBridge has been discouraged since there is no
  -- robust mechanism to track such registrations.
  
  dot1dConformance    OBJECT IDENTIFIER ::= { dot1dBridge 8 }

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany