RFC 3705 on High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
rfc-editor@rfc-editor.org Tue, 10 February 2004 18:49 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02151 for <ietf-announce-archive@odin.ietf.org>; Tue, 10 Feb 2004 13:49:28 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1Aqcfa-00039o-7p for ietf-announce-list@asgard.ietf.org; Tue, 10 Feb 2004 13:31:38 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1Aqcf8-00039K-EI for all-ietf@asgard.ietf.org; Tue, 10 Feb 2004 13:31:10 -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 NAA01412 for <all-ietf@ietf.org>; Tue, 10 Feb 2004 13:31:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aqcf7-00072b-00 for all-ietf@ietf.org; Tue, 10 Feb 2004 13:31:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqceD-0006wf-00 for all-ietf@ietf.org; Tue, 10 Feb 2004 13:30:14 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1Aqcdm-0006qD-00; Tue, 10 Feb 2004 13:29:46 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i1AITjk13384; Tue, 10 Feb 2004 10:29:45 -0800 (PST)
Message-Id: <200402101829.i1AITjk13384@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3705 on High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
Cc: rfc-editor@rfc-editor.org, adslmib@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 10 Feb 2004 10:29:45 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3705 Title: High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals Author(s): B. Ray, R. Abbi Status: Standards Track Date: February 2004 Mailbox: rray@pesa.com, Rajesh.Abbi@alcatel.com Pages: 11 Characters: 24158 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-adslmib-hc-tc-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3705.txt This document presents a set of High Capacity Textual Conventions for use in MIB modules which require performance history based upon 15 minute intervals. The Textual Conventions defined in this document extend the conventions presented in RFC 3593 to 64 bit resolution using the conventions presented in RFC 2856. This document is a product of the ADSL MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.