very rough draft: generic repeater mib proposal
"Jeffrey T. Johnson" <jjohnson@cisco.com> Thu, 13 July 1995 01:20 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18066; 12 Jul 95 21:20 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18062; 12 Jul 95 21:20 EDT
Received: from hp.com by CNRI.Reston.VA.US id aa20641; 12 Jul 95 21:20 EDT
Received: from hprnd.rose.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA082328436; Wed, 12 Jul 1995 18:20:36 -0700
Received: from relay.hp.com by hprnd.rose.hp.com with ESMTP (1.37.109.14/15.5+ECS 3.3) id AA126708426; Wed, 12 Jul 1995 18:20:27 -0700
Received: from feta.cisco.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA040478426; Wed, 12 Jul 1995 18:20:26 -0700
Received: (jjohnson@localhost) by feta.cisco.com (8.6.8+c/CISCO.SERVER.1.1) id SAA29348; Wed, 12 Jul 1995 18:12:12 -0700
Date: Wed, 12 Jul 1995 18:12:12 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Jeffrey T. Johnson" <jjohnson@cisco.com>
Message-Id: <199507130112.SAA29348@feta.cisco.com>
To: hubmib@baynetworks.com, kdegraaf@chipcom.com, vgmib@hprnd.rose.hp.com
Subject: very rough draft: generic repeater mib proposal
Sorry for the rough format of this proposal. I'll be prepared to give a more formal presentation to the hubmib WG in Stockholm. Background: o Multiple repeater MIBs are being developed by the IETF. o Every repeater MIB under development consists of generic objects as well as media-specific objects, with the generic objects replicated in multiple MIBs. o This is inconsistent with the approach taken for interfaces, which have a generic core MIB that is enhanced by media- specific MIBs. o A generic core repeater MIB would promote consistency, provide a common basis for the management of all repeaters, and would reduce the number of MIB objects. MIBs Evaluated: o 802.3 Repeater MIB (RFC 1516) o 802.3u Repeater MIB (draft from DeGraaf & Lui) o 802.12 Repeater MIB (draft-ietf-vgmib-repeater-dev-00) But the generic MIB should not be limited to ethernet-type media. I forsee a generic repeater MIB which contains the following groupings of MIB objects ========================================================================= Basic Repeater Information: o Group Capacity o Operational Status o Health Text o Reset Button o Non-Disruptive Test Button Basic Group Information: o Group Description o Group Object ID o Group Opertional Status o Group Status Change Timestamp o Group Port Capacity Basic Port Information: o Port Administrative Status o Port Operational Status Group Monitor Information: o Group Total Frames o Group Total Octets o Group Total Errors Port Monitor Information: o Readable Frames o Readable Octets o Error Frames Port Address Tracking: o Address Changes o Last Address /jeff
- very rough draft: generic repeater mib proposal Jeffrey T. Johnson
- Re: very rough draft: generic repeater mib propos… Donna McMaster