Re: [Adslmib] Issue with HCTC Perf Interval MIB (and thereforewith the VDSL MIB)
"Randy Presuhn" <randy_presuhn@mindspring.com> Thu, 20 November 2003 19:28 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19726 for <adslmib-archive@odin.ietf.org>; Thu, 20 Nov 2003 14:28:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuTD-0002s3-H3 for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 14:28:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKJS3lZ011031 for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 14:28:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuTD-0002rq-EC for adslmib-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 14:28:03 -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 OAA19707 for <adslmib-web-archive@ietf.org>; Thu, 20 Nov 2003 14:27:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMuTA-0000m9-00 for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 14:28:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AMuTA-0000m2-00 for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 14:28:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuTB-0002ra-FO; Thu, 20 Nov 2003 14:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuSu-0002rK-Qs for adslmib@optimus.ietf.org; Thu, 20 Nov 2003 14:27:44 -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 OAA19697 for <adslmib@ietf.org>; Thu, 20 Nov 2003 14:27:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMuSs-0000ll-00 for adslmib@ietf.org; Thu, 20 Nov 2003 14:27:42 -0500
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74]) by ietf-mx with esmtp (Exim 4.12) id 1AMuSr-0000li-00 for adslmib@ietf.org; Thu, 20 Nov 2003 14:27:41 -0500
Received: from h-68-164-78-60.snvacaid.dynamic.covad.net ([68.164.78.60] helo=oemcomputer) by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AMuSr-00014s-00 for adslmib@ietf.org; Thu, 20 Nov 2003 11:27:41 -0800
Message-ID: <012901c3af9c$9c448100$7f1afea9@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: adslmib mail list <adslmib@ietf.org>
References: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com> <1069254898.27942.2.camel@localhost.localdomain>
Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and thereforewith the VDSL MIB)
Date: Thu, 20 Nov 2003 11:29:26 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>
Hi - > From: "Bob Ray" <rray@pesa.com> > To: "Mike Sneed" <sneedmike@hotmail.com> > Cc: "adslmib mail list" <adslmib@ietf.org> > Sent: Wednesday, November 19, 2003 7:14 AM > Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and thereforewith the VDSL MIB) > > 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. > > > > > > Does anyone wish to comment on this change before the editors put in in a > > new draft? > > Anyone have an objection? A chorus of 'No's would be appreciated. Or at > least one. :) ... In the spirit of collaboration, I'll say that I dislike like the proposed change, and support it *solely* for reasons of compatibility. The MIB review guidelines make it pretty clear that Gauge32 would be the preferred data type, given the semantics. Randy _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib