Protocol Action: Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals to Draft Standard
The IESG <iesg-secretary@ietf.org> Tue, 08 April 2003 21:06 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02231; Tue, 8 Apr 2003 17:06:26 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 1930VH-0003rV-00 for ietf-announce-list@ran.ietf.org; Tue, 08 Apr 2003 17:19:39 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 1930VD-0003pg-00 for all-ietf@ran.ietf.org; Tue, 08 Apr 2003 17:19:35 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02047; Tue, 8 Apr 2003 17:01:12 -0400 (EDT)
Message-Id: <200304082101.RAA02047@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>, atommib@research.telcordia.com
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals to Draft Standard
Date: Tue, 08 Apr 2003 17:01:12 -0400
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
The IESG has approved the Internet-Draft 'Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals' <draft-ietf-atommib-rfc2493bis-01.txt> as a Draft Standard. This document is the product of the AToM MIB Working Group. The IESG contact persons are Thomas Narten and Erik Nordmark. The implementation report may be viewed at http://www.ietf.org/IESG/Implementations/RFC2493-Implementation.txt Technical Summary This document defines a set of Textual Conventions for MIB modules which make use of performance history data based on 15 minute intervals. Working Group Summary There was WG consensus to advance the document. Protocol Quality The document has been reviewed for the IESG by Erik Nordmark and Bert Wijnen. Note: Please change 2. Note on Invalid Data and Proxy to 2. Note on Invalid Data and Proxies