Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks
draft-ietf-atommib-acct-06

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (atommib WG)
Authors Keith McCloghrie , Juha Heinanen  , Wedge Greene  , Anil Prasad 
Last updated 2013-03-02 (latest revision 1998-10-05)
Stream Internet Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2513 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                         Keith McCloghrie
INTERNET DRAFT                                       Cisco Systems, Inc.
Expires January 1999                                       Juha Heinanen
                                                     Telia Finland, Inc.
                                                            Wedge Greene
                                            MCI Telecommunications Corp.
                                                             Anil Prasad
                                                     Cisco Systems, Inc.
                                                          4 October 1998

             Managed Objects for Controlling the Collection
               and Storage of Accounting Information for
                      Connection-Oriented Networks

                     draft-ietf-atommib-acct-06.txt

Status of this Memo

This document is an Internet-Draft.  Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups.  Note that other groups may also distribute working
documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.''

To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).

Copyright Notice

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




Internet-Draft     Connection-Oriented Accounting MIB       October 1998

1.  Introduction

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for controlling the
collection and storage of accounting information for connection-oriented
networks such as ATM.  The accounting data is collected into files for
later retrieval via a file transfer protocol.  For information on data
which can be collected for ATM networks, see [19].

2.  The SNMP Network Management Framework

The SNMP Management Framework presently consists of five major
components:

o    An overall architecture, described in RFC 2271 [1].

o    Mechanisms for describing and naming objects and events for the
     purpose of management.  The first version of this Structure of
     Management Information (SMI) is called SMIv1 and described in RFC
     1155 [2], RFC 1212 [3] and RFC 1215 [4].  The second version,
     called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC
     1904 [7].

o    Message protocols for transferring management information.  The
     first version of the SNMP message protocol is called SNMPv1 and
     described in RFC 1157 [8].  A second version of the SNMP message
     protocol, which is not an Internet standards track protocol, is
     called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
     The third version of the message protocol is called SNMPv3 and
     described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].

o    Protocol operations for accessing management information.  The
     first set of protocol operations and associated PDU formats is
     described in RFC 1157 [8].  A second set of protocol operations and
     associated PDU formats is described in RFC 1905 [13].

o    A set of fundamental applications described in RFC 2273 [14] and
     the view-based access control mechanism described in RFC 2275 [15].

Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB.  Objects in the MIB are defined
using the mechanisms defined in the SMI.

Expires April 1999                                              [Page 2]



Internet-Draft     Connection-Oriented Accounting MIB       October 1998

This memo specifies a MIB module that is compliant to the SMIv2.  A MIB
conforming to the SMIv1 can be produced through the appropriate
translations.  The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (e.g., use of Counter64).  Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process.  However, this loss of machine
readable information is not considered to change the semantics of the
MIB.

3.  Overview

In some connection-oriented network environments, there is a need for
the network administrator to be able to collect accounting data on the
usage of bandwidth/resources by connections (e.g., ATM connections)
within the network.  Data collection should be available for switched
virtual connections (SVCs and SVPs), and permanent virtual connections
Show full document text