IETF Logo Mail Archive

Re: PerfHist-TC-MIB

Jeff Johnson <jeff@redbacknetworks.com> Tue, 02 June 1998 23:36 UTC

Delivery-Date: Tue, 02 Jun 1998 19:36:08 -0400
Return-Path: jeff@redbacknetworks.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 TAA01337 for <ietf-archive@ietf.org>; Tue, 2 Jun 1998 19:36:02 -0400 (EDT)
Received: from jindo.cisco.com (jindo.cisco.com [171.69.43.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA11151 for <ietf-archive@cnri.reston.va.us>; Tue, 2 Jun 1998 19:38:20 -0400 (EDT)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by jindo.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id QAA20957 for <extdom.trunk-mib@aliashost.cisco.com>; Tue, 2 Jun 1998 16:29:42 -0700 (PDT)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id QAA08755 for <trunk-mib@external.cisco.com>; Tue, 2 Jun 1998 16:29:41 -0700 (PDT)
Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id QAA16937 for <trunk-mib@external.cisco.com>; Tue, 2 Jun 1998 16:29:39 -0700 (PDT)
Received: from wacko.redbacknetworks.com(155.53.130.200) by proxy2.cisco.com via smap (V2.0) id xma016929; Tue, 2 Jun 98 23:29:34 GMT
X-SMAP-Received-From: outside
Received: from smeghead.redbacknetworks.com (smeghead.redbacknetworks.com [155.53.180.10]) by wacko.redbacknetworks.COM (8.8.5/8.8.5) with SMTP id QAA04363; Tue, 2 Jun 1998 16:19:06 -0700 (PDT)
Message-Id: <3.0.3.32.19980602161555.007b6c40@pop.redbacknetworks.com>
X-Sender: jeff@pop.redbacknetworks.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 02 Jun 1998 16:15:55 -0700
To: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
From: Jeff Johnson <jeff@redbacknetworks.com>
Subject: Re: PerfHist-TC-MIB
In-Reply-To: <9805281312.AA02602@joker>
References: <356C871E.73F4CF4F@newbridge.com> <Pine.BSF.3.96.980527095847.18276D-100000@shell16.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

I've been doing the IESG quality review on this document.  There are two
issues which I would like to get the list(s) feedback on.

1) Currently all three TCs have a syntax of Gauge32.  IMO this implies
certain semantics which the TCs and the underlying MIB objects do not
possess.  I'd prefer to see these all changed to Unsigned32.  Note that
Gauge32 and Unsigned32 are encoded identicially, so there would be no
change to the data on the wire.

2) The xyzInvalidIntervals DESCRIPTION states simply "The number of
intervals for which no valid data is available."  When an agent which
supports 96 intervals is initially powered up, should the invalid interval
counter be 0 or 96?  In other words, are there initially 96 intervals which
are all invalid, or are there zero intervals?

thanks
/jeff

v2.23.0 | Report a Bug | By Email