Browse Prior Art Database

High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals (RFC3705)

IP.com Disclosure Number: IPCOM000021809D
Original Publication Date: 2004-Feb-01
Included in the Prior Art Database: 2004-Feb-10
Document File: 12 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Ray: AUTHOR [+2]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group B. Ray

Request for Comments: 3705 PESA Switching Systems

Category: Standards Track R. Abbi

Alcatel

February 2004

High Capacity Textual Conventions for MIB Modules Using

Performance History Based on 15 Minute Intervals

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

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.

Table of Contents

1. The Internet-Standard Management Framework . . . . . . . . . . 2

2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

3. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 3

4. Intellectual Property Statement. . . . . . . . . . . . . . . . 8

5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.1. Normative References . . . . . . . . . . . . . . . . . . 8

5.2. Informative References . . . . . . . . . . . . . . . . . 9

6. Security Considerations. . . . . . . . . . . . . . . . . . . . 10

7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10

8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10

9. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 11

Ray & Abbi Standards Track [Page 1]

RFC 3705 High Capacity Perfhist TC MIB February 2004

1. The Internet-Standard Management Framework

For a detailed overview of the documents that describe the current

Internet-Standard Management Framework, please refer to section 7 of

RFC 3410 [RFC3410].

Managed objects are accessed via a virtual information store, termed

the Management Information Base or MIB. MIB objects are generally

accessed through the Simple Network Management Protocol (SNMP).

Objects in the MIB are defined using the mechanisms defined in the

Structure of Management Information (SMI). This memo specifies a MIB

module that is compliant to the SMIv2, which is described in STD 58,

RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580

[RFC2580].

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in [RFC2119].

2. Overview

In cases where a manager must obtain performance history data about

the behavior of equipment it manages, several strategies can be

followed in the design of a MIB module that represents the managed

equipment, including:

- The agent counts events on a...