IETF Logo Mail Archive

Re: PerfHist-TC-MIB

Ken Chapman <KChapman@Argon.com> Thu, 28 May 1998 17:36 UTC

Delivery-Date: Thu, 28 May 1998 13:36:55 -0400
Return-Path: KChapman@Argon.com
Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA05954 for <ietf-archive@ietf.org>; Thu, 28 May 1998 13:36:50 -0400 (EDT)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA16704 for <ietf-archive@cnri.reston.va.us>; Thu, 28 May 1998 13:39:13 -0400 (EDT)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by kickme.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.GATE.1.1) with ESMTP id KAA13299 for <trunk-mib@external.cisco.com>; Thu, 28 May 1998 10:30:57 -0700 (PDT)
Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id KAA12919 for <trunk-mib@external.cisco.com>; Thu, 28 May 1998 10:30:55 -0700 (PDT)
Received: from shultz.argon.com(208.234.161.2) by proxy2.cisco.com via smap (V2.0) id xma012908; Thu, 28 May 98 17:30:50 GMT
X-SMAP-Received-From: outside
Received: from aruba (aruba.argon.com [208.234.161.60]) by shultz.argon.com (8.8.6/8.8.6) with SMTP id NAA11034; Thu, 28 May 1998 13:19:13 -0400 (EDT)
Message-Id: <3.0.32.19980528131907.0096cd50@shultz.argon.com>
X-Sender: kchapman@shultz.argon.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 28 May 1998 13:19:08 -0400
To: Kaj Tesink <kaj@cc.bellcore.com>, atommib@thumper.bellcore.com, trunk-mib@external.cisco.com, David Fowler <davef@newbridge.com>, "C. M. Heard/VVNET, Inc." <heard@vvnet.com>
From: Ken Chapman <KChapman@Argon.com>
Subject: Re: PerfHist-TC-MIB
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

I agree.  I was not thinking of the PROCESS when I raised the issue.
It just seemed to make sence to put all the TCs together in one MIB.  
I'll draft a Supplemental-PerfHist-TC-MIB to go along with the 
DS1, DS3 and SONET Supplemental MIBs.

Now that I've got your attention, I have an important question of scope.
I think that each supplemental MIB should just address a specific 
standard, in this case ANSI T1.231.  Does anyone think otherwise?
Actually I want to submit another new MIB for SONET APS, but I don't think
it should be bundled in.  Likewise, I looked at the draft of the
DS3 sup MIB and think that the PLCP stuff belongs somewhere else.
	Ken

At 09:11 AM 5/28/98 -0400, Kaj Tesink wrote:
>At 05:36 PM 5/27/98 -0400, David Fowler wrote:
>>> Why not put PerfDayCount
>>> (and any other TCs needed to support the supplemental trunk MIBs) in a
>>> Supplemental-PerfHist-TC-MIB?
>>
>>Exactly.  The trunk MIBs have taken forever to get out.  Let's get them
done and
>>then add new things.
>
>I agree with this. And one more point:
>
>It would be questionable to define TCs that are not actually used in
>any MIB module (to date). We can only stick in TCs in the current 
>TC module that are used elsewhere or where we are very sure
>that 
>a) they will be used elsewhere within the foreseeable future
>b) they are correct
>
>Ken asked recently whether there is interest in a Supplemental
>SONET/SDH MIB that would be a potential user of such TCs.
>Is there any interest? Ken has some good stuff that can be leveraged.
>
>And what about the Supplemental DS0/1/2/3 MIBs?
>
>Kaj
>
>
>
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>_/                                                                      _/
>_/  Kaj Tesink                                                          _/
>_/  Bellcore                                                            _/
>_/  Business Internet Professional Services  vmail (732) 758-5254       _/
>_/  331 Newman Springs Rd.                   email kaj@cc.bellcore.com  _/
>_/  Red Bank, NJ 07701                     faxmail (732) 758-2269       _/
>_/                                                                      _/
>_/  * NOTE AREA CODE CHANGE (908) --> (732) EFFECTIVE JUNE 1, 1997 *    _/
>_/                                                                      _/
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>
>

v2.23.0 | Report a Bug | By Email