Re: Re: Draft-iet-bridge-bridgemib-smiv2-09.txt

On Thu, Jan 27, 2005 at 08:34:14PM -0500, David B Harrington wrote:
 
> If, for accuracy reasons, we're going to list required objects from
> other mib modules, then we need to be accurate.

Here is another proposal.

3.2  Relationship to Other MIB Modules

   As described above, some IEEE 802.1D management objects have not
   been included in this MIB module because they overlap with objects
   in other MIB modules applicable to a bridge implementing this MIB
   module.

3.2.1  Relationship to the SNMPv2-MIB

   The SNMPv2-MIB [RFC3418] defines objects that are generally
   applicable to managed devices. These objects apply to the device as
   a whole irrespective of whether the device's sole functionality is
   bridging, or whether bridging is only a subset of the device's
   functionality. 

   As explained in section 3.1, full support for the 802.1D management
   objects requires that the objects sysDescr and sysUpTime of the
   SNMPv2-MIB [RFC3418] are implemented. Note that compliance to the
   current SNMPv2-MIB module requires additional objects and
   notifications to be implemented as specified in RFC 3418 [RFC3418].

3.2.2  Relationship to the IF-MIB

   The IF-MIB [RFC2863] defines managed objects used for managing
   network interface. A network interface is thought of as being
   attached to a `subnetwork'. (Note that this term is not to be
   confused with `subnet' which refers to an addressing partitioning
   scheme used in the Internet suite of protocols.)  The term
   'segment' is used in this memo to refer to such a subnetwork,
   whether it be an Ethernet segment, a 'ring', a WAN link, or even an
   X.25 virtual circuit.

   As explained in section 3.1, full support for the 802.1D management
   objects requires that the objects ifIndex, ifType, ifDescr,
   ifPhysAddress, and ifLastChange of the IF-MIB [RFC2863] are
   implemented. Note that compliance to the current IF-MIB module
   requires additional objects and notifications to be implemented as
   specified in RFC 2863 [RFC2863].

/js

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