[Adslmib] AD review of draft-ietf-adslmib-hc-tc-04.txt
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Sat, 20 September 2003 02:36 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04400 for <adslmib-archive@odin.ietf.org>; Fri, 19 Sep 2003 22:36:57 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.12.8/8.12.8) with ESMTP id h8K1VhFP020140 for <adslmib-archive@odin.ietf.org>; Fri, 19 Sep 2003 21:37:36 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R6AstY004241 for adslmib-archive@odin.ietf.org; Wed, 27 Aug 2003 02:10:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rqs1-0000LU-GA for adslmib-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 23:21:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12016 for <adslmib-web-archive@ietf.org>; Tue, 26 Aug 2003 23:21:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rqrz-0002Kw-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 23:21:15 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rqry-0002Kt-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 23:21:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rn7S-0006NN-0j; Tue, 26 Aug 2003 19:20:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rgP6-0007PB-2g for adslmib@optimus.ietf.org; Tue, 26 Aug 2003 12:10:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12646 for <adslmib@ietf.org>; Tue, 26 Aug 2003 12:10:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rgP4-00031f-00 for adslmib@ietf.org; Tue, 26 Aug 2003 12:10:42 -0400
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19rgP3-00031Z-00 for adslmib@ietf.org; Tue, 26 Aug 2003 12:10:41 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7QGA6U22369 for <adslmib@ietf.org>; Tue, 26 Aug 2003 11:10:07 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <Q88X1C48>; Tue, 26 Aug 2003 18:10:04 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550245BE83@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Michael Sneed <sneedmike@hotmail.com>, Rajesh Abbi <Rajesh.Abbi@alcatel.com>, Bob Ray <rray@pesa.com>
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, "Adslmib (E-mail)" <adslmib@ietf.org>
Date: Tue, 26 Aug 2003 18:10:03 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Adslmib] AD review of draft-ietf-adslmib-hc-tc-04.txt
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>
I have these minor comments. Can either be fixed right away or be taken care of by RFC-Editor - References to RFC2578,2579,2580 occur both in normative and informative references. The ones in informative reference section can/should be removed - We have various references to RFCs that are imminent to be obsoleted, RFC2498, RFC2558,... we may want to make sure that we get them updated during AUTH48 call from RFC-Editor - If we do anything to the security considerations section, then I think I would replace the whole section with: Security Considerations This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. This document has therefore no impact on the security of the Internet. - I wonder, if it would make sense to "generalize" the TCs HCPerfValidIntervals HCPerfInvalidIntervals HCPerfTimeElapsed HCPerfIntervalThreshold So that they could also be used with the RFC2493bis TCs. I think they basically are, but their prefix of HC seems to indicate they are specific to the HC related TCs. Thanks, Bert > -----Original Message----- > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com] > Sent: donderdag 14 augustus 2003 21:35 > To: Wijnen, Bert (Bert) > Cc: Michael Sneed; Rajesh Abbi; Bob Ray > Subject: Re: VDSL MIB > > > Hi - > > I also looked at draft-ietf-adslmib-hc-tc-04.txt > and did not spot any problems. > > Although the security considerations section > doesn't follow the current boilerplate, I think > this is a non-issue since this MIB module only > contains TCs. > > Randy > > _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib
- [Adslmib] AD review of draft-ietf-adslmib-hc-tc-0… Wijnen, Bert (Bert)