INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
MIB-Controlled ATM Accounting Management
draft-ietf-atommib-acct-00.txt
February 22, 1996
Anil Prasad (editor)
MCI Telecommunications Corporation
7502332@mcimail.com
Wedge Greene
MCI Telecommunications Corporation
5540088@mcimail.com
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. Internet Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet
Drafts as reference material or to cite them other than as a "working
draft" or "work in progress."
Please check the I-D abstract listing contained in each Internet
Draft directory to learn the current status of this or any other
Internet Draft.
Abstract
This document states requirements for ATM accounting management, and
proposes MIB control objects to facilitate logging and retrieval of
accounting information by ATM network elements.
Draft Expires August 23, 1996 [page 1]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
Table of Contents
1.0 Introduction.....................................................1
2.0 Requirements for ATM Accounting Management.......................3
3.0 ATM SVC Logging ASN.1 MIB Control Objects........................3
4.0 ATM PVC Logging ASN.1 MIB Control Objects........................4
5.0 Base Information Items for PVC and SVC Accounting Management.....6
6.0 References.......................................................20
7.0 Security Considerations..........................................20
8.0 Editors Contact Information.....................................20
Draft Expires August 23, 1996 [page 2]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
1.0 Introduction
This document consolidates several proposals (listed below in reference
section 6) on logging for ATM accounting management support. It also
proposes new MIB objects (as supplements to the AToM MIB) that relate
to the accounting information items to be logged, and proposes MIB
control objects to facilitate logging.
The intent is to support basic accounting requirements listed in
section 2.0, and to define information items and control MIB objects
for logging; additional functionality may be defined in enterprise-
specific vendor MIB modules.
Accounting management is a key consideration for service providers,
who have voiced the need for ATM PVC and SVC accounting information
support in the AToM MIB for several reasons, including the following:
1. Without a common specification of the accounting data items and
log file structure, accounting management would have to be handled in
a vendor-dependent manner, and service providers would have to develop
customized software for each switch vendor to integrate the switches
into the service provider's accounting management system.
Specifying the data items and log structure in the AToM MIB would
foster data consistency across switch vendors and greatly facilitate
integration of different vendor devices into accounting management
systems of service providers.
2. This would facilitate usage based accounting, which would force
users to use sensible connection parameter values when they are
negotiating connection setup.
3. Align with work in the ATM Forum Network Management subworking
group, specifically, to meet the high level requirements for
accounting objects (within the SNMP domain).
Note: The subject of log files for accounting management has been
discussed at the AToM MIB Working Group before. There was informal
agreement at the AToMMIB WG session in Spring '95 to:
1. Support MIB controlled logs
2. Have Optional support for logs, but exact conformance when
supporting.
Key reasons for supporting log files for accounting management included
the following:
1. Log files satisfy stringent accounting and billing requirements
that most service providers have regarding non-volatile storage of
accounting information, amount of storage, loss of information,
frequency of polling, etc. A file transfer protocol would be more
robust and efficient than SNMP.
2. Log files may be easier for switch vendors to implement.
Draft Expires August 23, 1996 [page 3]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
2.0 Requirements for ATM Accounting Management
Key requirements for supporting accounting management in the AToM MIB
that have been discussed in the past include the following:
1. Accounting management information support for ATM PVCs and SVCs.
2. Optional support for logging PVC and SVC accounting management
information; however, if accounting management logging is supported,
vendors must conform to the AToM MIB specification for logging.
3. Logging of PVC and SVC information in seperate log files, but with
similar control mechanisms and associated MIB control objects.
4. Optional support for turning logging on and off per interface
(with optional trap notification of change of logging state) via the
MIB.
5. Support for inspecting the structure and accounting information
item types in the log files, via the MIB, and optionally being able to
configure (via Set requests) logging of these accounting management
information items.
6. Optional support for log file field delimiter and line termination
character sequences in the MIB.
7. Optional support for checkpoint (data dump) time control features;
capability to "dump to file after connection release", or "dump to file
every x seconds from now".
8. Flexibility in defining information items for PVC and SVC
accounting logging, to support future enhancements.
Note: The log files could be transferred to the service provider via
FTP or TFTP on demand, at regular time intervals, or when the maximum
log size was exceeded; this is implementation dependent, and
specification of the mechanism of data transfer is left to the vendor.
The MIB defined in this document only specifies the basic accounting
information and control objects for logging via MIB variables;
additional functionality may be defined in vendor enterprise-specific
MIB modules.
Additional requirements which are not met currently in the enclosed
defined MIB are as follows (the intention is to define these during
the next working session):
9. The accounting records are collected to a log file that has a
maximum defined size. A MIB object is required to support this.
10. A trap can be generated if a high water mark is exceeded in the
above log file.
Draft Expires August 23, 1996 [page 4]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
11. MIB control object(s) is/are required to specify the low level
encoding of the accounting data items when stored in the log file.
This encoding should include:
- ASCII
- BER encoded type/length/value tuples.
12. A single operation by the manager should save and clear the file.
Once cleared, the contents of all new accounting records will be as
specified by the current contents of the Log Data Configuration object
identifer table.
When the log file is saved, the present contents of the object id
table is saved; this saved table can be later used to intepret the
contents of the next saved accounting record file.
Draft Expires August 23, 1996 [page 5]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
3.0 ATM SVC Logging ASN.1 MIB Objects
This section provides the definitions of ASN.1 MIB objects to support
the requirements listed in section 2.0, for SVCs.
NOTE: Objects listed in this section are OPTIONAL.
atmAccounting OBJECT IDENTIFIER ::= { xxx }
atmSvcLog OBJECT IDENTIFIER ::= { atmAccounting 1 }
atmSvcLogConf OBJECT IDENTIFIER ::= { atmSvcLog 1 }
atmSvcLogSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of entries supported by this log.
What happens when this value is exceeded, depends on
implementation.
For example, a vendor may auto-FTP the file to a remote
host, or generate a trap notification, or wrap the log
file."
::= { atmSvcLogConf 1 }
atmSvcLogCount OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of entries in the SVC log."
::= { atmSvcLogConf 2 }
atmSvcLogConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmSvcLogConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains SVC accounting Log configuration
information."
::= { atmSvcLogConf 3 }
atmSvcLogConfEntry OBJECT-TYPE
SYNTAX AtmSvcLogConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entry in atmSvcLogConfTable represents accounting Log
configuration information per switch interface."
INDEX { ifIndex }
::= { atmSvcLogConfTable 1 }
Draft Expires August 23, 1996 [page 6]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
AtmSvcLogConfEntry ::= SEQUENCE {
atmAccountingLoggingControl
INTEGER,
atmLoggingPeriod
INTEGER
}
atmAccountingLoggingControl OBJECT-TYPE
SYNTAX INTEGER {
noLogging(1),
loggingOnRelease(2),
loggingDuringLifetimeAndOnRelease(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Controls SVC accounting logging by turning it on or off.
If on, accounting records are created in the log file either
only when the connection is released or also during the
lifetime of the connection."
DEFVAL { noLogging }
::= { atmSvcLogConfEntry 1 }
atmLoggingPeriod OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Accounting logging period in seconds for the interface,
with the reference starting point as the time this object
was set. This object is used only when
atmAccountingLoggingControl has the
loggingDuringLifetimeAndOnRelease(3) value."
::= { atmSvcLogConfEntry 2 }
atmSvcLogFieldSeperator OBJECT-TYPE
SYNTAX OCTET-STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The field seperator character sequence for the SVC log."
::= { atmSvcLogConf 4 }
atmSvcLogLineSeperator OBJECT-TYPE
SYNTAX OCTET-STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The line seperator character sequence for the SVC log."
::= { atmSvcLogConf 4 }
Draft Expires August 23, 1996 [page 7]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
-- This table specifies the accounting information items that will be
-- logged, for all interfaces for
-- which accounting logging is enabled. This table permits the service
-- provider to query and
-- inspect the structure and data items in the log file.
-- This table could optionally be read-write to
-- enable the service provider to individually turn on or off the
-- logging for each item, to customize it
-- to the service provider's accounting system. The agent populates
-- this table with entries corresponding to all accounting data items
-- it can support.
atmSvcLogDataConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmSvcLogDataConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table specifies the accounting information
items that will be logged, for all
interfaces for which accounting logging is enabled.
This table permits the service provider to query and
inspect the structure and data items in the log file.
This table could optionally be read-write to enable
the service provider to individually turn on or off
the logging for each item, to customize it to the
service provider's accounting system.
The agent populates this table with entries
corresponding to all accounting data items it can
support."
::= { atmSvcLogConf 5 }
atmSvcLogDataConfEntry OBJECT-TYPE
SYNTAX AtmSvcLogDataConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of atmSvcLogDataConfTable."
INDEX { atmSvcLogDataFieldIndex }
::= { atmSvcLogDataConfTable 1 }
AtmSvcLogDataConfEntry ::= SEQUENCE {
atmSvcLogDataFieldIndex
INTEGER,
atmSvcLogDataItem
OBJECT IDENTIFIER,
atmSvcLoggingStatus
INTEGER
}
Draft Expires August 23, 1996 [page 8]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
atmSvcLogDataFieldIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The sequence number of the data field within the
SVC Log file."
::= { atmSvcLogDataConfEntry 1}
atmSvcLogDataItem OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A object identifier pointer to the SVC-related MIB
object for this field."
::= { atmSvcLogDataConfEntry 2 }
atmSvcLoggingStatus
SYNTAX INTEGER {
loggingEnabled(1)
loggingDisabled(2)
supportedInFuture(3)
available(4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The logging status for this data item."
::= { atmSvcLogDataConfEntry 3 }
Draft Expires August 23, 1996 [page 9]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
4.0 ATM PVC Logging ASN.1 MIB Objects
This section provides the definitions of ASN.1 MIB objects to support
the requirements listed in section 2.0, for PVCs.
NOTE: Objects listed in this section are OPTIONAL.
atmPvcLog OBJECT IDENTIFIER ::= { atmAccounting 2 }
atmPvcLogConf OBJECT IDENTIFIER ::= { atmPvcLog 1 }
atmPvcLogSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of entries supported by this log.
What happens when this value is exceeded, depends on
implementation.
For example, a vendor may auto-FTP the file to a remote
host, or generate a trap notification, or wrap the log
file."
::= { atmPvcLogConf 1 }
atmPvcLogCount OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total number of entries in the PVC log."
::= { atmPvcLogConf 2 }
atmPvcLogConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmPvcLogConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains PVC accounting Log configuration
information."
::= { atmPvcLogConf 3 }
atmPvcLogConfEntry OBJECT-TYPE
SYNTAX AtmPvcLogConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entry in atmPvcLogConfTable represents accounting Log
configuration information per switch interface."
INDEX { ifIndex }
::= { atmPvcLogConfTable 1 }
Draft Expires August 23, 1996 [page 10]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
AtmPvcLogConfEntry ::= SEQUENCE {
atmAccountingLoggingControl
INTEGER,
atmLoggingPeriod
INTEGER
}
atmAccountingLoggingControl OBJECT-TYPE
SYNTAX INTEGER {
noLogging(1),
logging(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Controls PVC accounting logging by turning it on or off."
DEFVAL { noLogging }
::= { atmPvcLogConfEntry 1 }
atmLoggingPeriod OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Accounting logging period in seconds for the interface, with
the reference starting point as the time this object was set.
This object is used only when atmAccountingLoggingControl
has loggingDuringLifetimeAndOnRelease(3) value."
::= { atmPvcLogConfEntry 2 }
atmPvcLogFieldSeperator OBJECT-TYPE
SYNTAX OCTET-STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The field seperator character sequence for the PVC log."
::= { atmPvcLogConf 4 }
atmPvcLogLineSeperator OBJECT-TYPE
SYNTAX OCTET-STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The line seperator character sequence for the PVC log."
::= { atmPvcLogConf 4 }
Draft Expires August 23, 1996 [page 11]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
-- This table specifies the accounting information items that will be
-- logged, for all interfaces for
-- which accounting logging is enabled. This table permits the service
-- provider to query and
-- inspect the structure and data items in the log file.
-- This table could optionally be read-write to
-- enable the service provider to individually turn on or off the
-- logging for each item, to customize it
-- to the service provider's accounting system. Also, this would
-- facilitate resequencing or changing
-- the order of the accounting log data items in the log file. The
-- agent populates this table with
-- entries corresponding to all accounting data items it can support.
atmPvcLogDataConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtmPvcLogDataConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table specifies the accounting information
items that will be logged, for all
interfaces for which accounting logging is enabled.
This table permits the service provider to query and
inspect the structure and data items in
the log file. This table could optionally be read-
write to enable the service provider to individually
turn on or off the logging for each
item, to customize it to the service provider's
accounting system.
The agent populates this table with entries
corresponding to all accounting data items it can
support."
::= { atmPvcLogConf 5 }
atmPvcLogDataConfEntry OBJECT-TYPE
SYNTAX AtmPvcLogDataConfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of atmPvcLogDataConfTable."
INDEX { atmPvcLogDataFieldIndex }
::= { atmPvcLogDataConfTable 1 }
AtmPvcLogDataConfEntry ::= SEQUENCE {
atmPvcLogDataFieldIndex
INTEGER,
atmPvcLogDataItem
OBJECT IDENTIFIER,
atmPvcLogDataRowStatus
INTEGER
}
Draft Expires August 23, 1996 [page 12]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
atmPvcLogDataFieldIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The sequence number of the data field within the
PVC Log file."
::= { atmPvcLogDataConfEntry 1}
atmPvcLogDataItem OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A object identifier pointer to the PVC-related MIB
object for this field."
::= { atmPvcLogDataConfEntry 2 }
atmPvcLoggingStatus
SYNTAX INTEGER {
loggingEnabled(1)
loggingDisabled(2)
supportedInFuture(3)
available(4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The logging status for this data item."
::= { atmPvcLogDataConfEntry 3 }
Draft Expires August 23, 1996 [page 13]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
5.0 Base Information Items for PVC and SVC Accounting
This section lists base accounting information item types that can be
pointed to from the PVC and SVC log data configuration tables.
atmAccountingLogDataTypes OBJECT IDENTIFIER ::=
{ atmAccounting 3 }
logFileIndexValue OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the logFileIndexValue
type for a field in the log file that serves as an index to the
file information."
::= { atmAccountingLogDataTypes 1 }
deviceIdentifier OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the deviceIdentifier
type for a field in the log file that serves to identify the
device."
::= { atmAccountingLogDataTypes 2 }
interfaceIndex OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the interfaceIndex
type."
::= { atmAccountingLogDataTypes 3 }
vpiValue OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the vpiValue
type."
::= { atmAccountingLogDataTypes 4 }
vciValue OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the vciValue
type."
::= { atmAccountingLogDataTypes 5 }
timeLogged OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the timeLogged
type. The field should show both date and time."
::= { atmAccountingLogDataTypes 6 }
Draft Expires August 23, 1996 [page 14]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
creationTime OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the PVC or SVC creationTime
type."
::= { atmAccountingLogDataTypes 7 }
deletionTime OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the SVC deletionTime
type."
::= { atmAccountingLogDataTypes 8 }
callingPartyAddress OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the callingPartyAddress
type."
::= { atmAccountingLogDataTypes 9 }
calledPartyAddress OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the calledPartyAddress
type."
::= { atmAccountingLogDataTypes 10 }
callReference OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"Call Reference carried in the call reference
information element of the call SETUP message. The
call reference doesn't have end-to-end signifiance
across ATM-network."
::= { atmAccountingLogDataTypes 11 }
connectionConfiguration OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the connectionConfiguration
type (p-2-p / p-2-mp / other)."
::= { atmAccountingLogDataTypes 12 }
transmitTrafficDescrType OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"The value of this object is taken from
atmTrafficDescrType entry of traffic descriptor for this
connection (rfc1695)."
::= { atmAccountingLogDataTypes 13 }
Draft Expires August 23, 1996 [page 15]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
transmitTrafficDescrParam1 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitTrafficDescrParam1
type."
::= { atmAccountingLogDataTypes 14 }
transmitTrafficDescrParam2 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitTrafficDescrParam2
type."
::= { atmAccountingLogDataTypes 15 }
transmitTrafficDescrParam3 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitTrafficDescrParam3 type."
::= { atmAccountingLogDataTypes 16 }
transmitTrafficDescrParam4 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitTrafficDescrParam4
type."
::= { atmAccountingLogDataTypes 17 }
transmitTrafficDescrParam5 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitTrafficDescrParam5
type."
::= { atmAccountingLogDataTypes 18 }
transmitQosClass OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitQosClass
type."
::= { atmAccountingLogDataTypes 19 }
transmitMaxDelay OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitMaxDelay QoS parameter
type."
::= { atmAccountingLogDataTypes 20 }
transmitMeanDelay OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitMeanDelay QoS parameter type."
::= { atmAccountingLogDataTypes 21 }
Draft Expires August 23, 1996 [page 16]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
transmitCellLossRatio OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitCellLossRatio QoS parameter
type."
::= { atmAccountingLogDataTypes 22 }
transmitCDV OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitCDV QoS parameter
type."
::= { atmAccountingLogDataTypes 23 }
receiveTrafficDescrType OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"The value of this object is taken from
atmTrafficDescrType entry of traffic descriptor for this
connection (rfc1695)."
::= { atmAccountingLogDataTypes 24 }
receiveTrafficDescrParam1 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveTrafficDescrParam1
type."
::= { atmAccountingLogDataTypes 25 }
receiveTrafficDescrParam2 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveTrafficDescrParam2
type."
::= { atmAccountingLogDataTypes 26 }
receiveTrafficDescrParam3 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveTrafficDescrParam3
type."
::= { atmAccountingLogDataTypes 27 }
receiveTrafficDescrParam4 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveTrafficDescrParam4
type."
::= { atmAccountingLogDataTypes 28 }
Draft Expires August 23, 1996 [page 17]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
receiveTrafficDescrParam5 OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveTrafficDescrParam5
type."
::= { atmAccountingLogDataTypes 29 }
receiveQosClass OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveQosClass
type."
::= { atmAccountingLogDataTypes 30 }
receiveMaxDelay OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveMaxDelay QoS parameter
type."
::= { atmAccountingLogDataTypes 31 }
receiveMeanDelay OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveMeanDelay QoS parameter
type."
::= { atmAccountingLogDataTypes 32 }
receiveCellLossRatio OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveCellLossRatio QoS parameter
type."
::= { atmAccountingLogDataTypes 33 }
receiveCDV OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receiveCDV QoS parameter
type."
::= { atmAccountingLogDataTypes 34 }
bhliType OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"The value of this object is taken from
atmSigDescrParamBhliType entry of Signalling Descriptor
for this connection (draft-ietf-atommib-atm2-03.txt)."
::= { atmAccountingLogDataTypes 35 }
Draft Expires August 23, 1996 [page 18]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
bhliInfo OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"The value of this object is taken from
atmSigDescrParamBhliInfo entry of Signalling Descriptor
for this connection (draft-ietf-atommib-atm2-03.txt)."
::= { atmAccountingLogDataTypes 36 }
svcClearCause OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the svcClearCause
type. The cause of the clearing of this connection. Zero
value may indicate that the call has not been cleared yet."
::= { atmAccountingLogDataTypes 37 }
transmittedCells OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmittedCells
type."
::= { atmAccountingLogDataTypes 38 }
receivedCells OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receivedCells
type."
::= { atmAccountingLogDataTypes 39 }
transmittedCellsWithCLPSet OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the transmitCellsWithCLPSet
type."
::= { atmAccountingLogDataTypes 40 }
receivedCellsWithCLPSet OBJECT-IDENTITY
STATUS mandatory
DESCRIPTION
"This identifies the receivedCellsWithCLPSet
type."
::= { atmAccountingLogDataTypes 41 }
Draft Expires August 23, 1996 [page 19]
INTERNET-DRAFT MIB-Controlled ATM Accounting Management February 1996
6.0 References
[1]. RFC 1695, ATM Management Objects, August 1994
[2]. E-mail proposal to AToM MIB WG by Juha Viinikainen (Telecom
Finland Ltd), 7/12/95
[3]. E-mail proposal to AToM MIB WG by Juha Viinikainen (Telecom
Finland Ltd), Jul 05, 1995
[4]. E-mail proposal to AToM MIB WG by Juha Heinanen (Telecom Finland
Ltd), Nov. 24, 1995
[5]. E-mail proposal to AToM MIB WG by Jean-Bernard Schmitt (IBM)
7.0 Security Considerations
Security issues are not discussed in this memo.
8.0 Editors Contact Information
Anil Prasad
MCI Telecommunications Corporation
901 International Parkway
Richardson, Texas 75081
Phone: 214-498-1325
Fax: 214-498-1300
E-mail: 7502332@mcimail.com
Draft Expires August 23, 1996 [page 20]
