Re: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore with the VDSL MIB)
Bob Ray <rray@pesa.com> Mon, 24 November 2003 15:30 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12508 for <adslmib-archive@odin.ietf.org>; Mon, 24 Nov 2003 10:30:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOIf8-000101-0y for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 10:30:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOFU6JE003840 for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 10:30:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOIf7-0000zr-Sf for adslmib-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 10:30:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12475 for <adslmib-web-archive@ietf.org>; Mon, 24 Nov 2003 10:29:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOIf5-0006n3-00 for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 10:30:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AOIf5-0006mz-00 for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 10:30:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOIf4-0000zW-RB; Mon, 24 Nov 2003 10:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AOIef-0000yo-IP for adslmib@optimus.ietf.org; Mon, 24 Nov 2003 10:29:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12467 for <adslmib@ietf.org>; Mon, 24 Nov 2003 10:29:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AOIed-0006mp-00 for adslmib@ietf.org; Mon, 24 Nov 2003 10:29:35 -0500
Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 1AOIec-0006mm-00 for adslmib@ietf.org; Mon, 24 Nov 2003 10:29:34 -0500
Received: from pesa.com ([216.180.38.253]) by mail.hiwaay.net (8.12.10/8.12.10) with ESMTP id hAOFTWtx1004731 for <adslmib@ietf.org>; Mon, 24 Nov 2003 09:29:33 -0600 (CST)
Received: from 192.168.0.122 ([192.168.0.122]) by pesa.com (pesa.com [127.0.0.1]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 60-md50000000197.tmp for <adslmib@ietf.org>; Mon, 24 Nov 2003 09:29:31 -0600
Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore with the VDSL MIB)
From: Bob Ray <rray@pesa.com>
Reply-To: rray@pesa.com
To: Mike Sneed <sneedmike@hotmail.com>
Cc: adslmib mail list <adslmib@ietf.org>
In-Reply-To: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
References: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
Content-Type: text/plain
Message-Id: <1069687770.2734.30.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5)
Date: Mon, 24 Nov 2003 09:29:30 -0600
Content-Transfer-Encoding: 7bit
X-Spam-Processed: pesa.com, Mon, 24 Nov 2003 09:29:31 -0600 (not processed: message from valid local sender)
X-MDRemoteIP: 192.168.0.122
X-Return-Path: rray@pesa.com
X-MDaemon-Deliver-To: adslmib@ietf.org
Content-Transfer-Encoding: 7bit
Sender: adslmib-admin@ietf.org
Errors-To: adslmib-admin@ietf.org
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Id: ADSLMIB <adslmib.ietf.org>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
On Mon, 2003-11-17 at 11:06, Michael Sneed wrote: > During the IETF Last Call process there were some concerns expressed in the > IESG about the HCTC Performance Interval MIB > (draft-ietf-adslmib-hc-tc-06.txt) that we have recommended to go to Proposed > Standard. In a nutshell, the problem is one of alignment of the various > MIBs that deal with this topic (namely RFC3593 and 2856). > > As a result of this discussion, it has been recommended that we change > > - HCPerfTimeElapsed, Gauge32 (0...86399) > - HCPerfValidIntervals, Gauge32 (0...96) > - HCPerfInvalidIntervals, Gauge32 (0...96) > > to type Integer32. draft-ietf-adslmib-hc-tc-07.txt has been submitted with the above changes. -- Bob Ray <rray@pesa.com> _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib