Internet DRAFT - draft-ietf-atommib-rfc2493bis


A new Request for Comments is now available in online RFC libraries.

        RFC 3593

        Title:      Textual Conventions for MIB Modules Using
                    Performance History Based on 15 Minute Intervals
        Author(s):  K. Tesink, Ed.
        Status:     Standards Track
        Date:       September 2003
        Pages:      10
        Characters: 20363
        Obsoletes:  2493

        I-D Tag:    draft-ietf-atommib-rfc2493bis-01.txt


This document defines a set of Textual Conventions for MIB
modules that make use of performance history data based on 15
minute intervals.

This memo replaces RFC 2493.  Changes relative to RFC 2493 are
summarized in the MIB module's REVISION clause.

This document is a product of the AToM MIB Working Group of the IETF.

This is now a Draft 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

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.