Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2
RFC 1695

Document Type RFC - Proposed Standard (August 1994; No errata)
Obsoleted by RFC 2515
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1695 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           M. Ahmed
Request for Comments: 1695                                     K. Tesink
Category: Standards Track                                        Editors
                                            Bell Communications Research
                                                             August 1994

                     Definitions of Managed Objects
                     for ATM Management Version 8.0
                              using SMIv2

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.

Table of Contents

   1. Introduction .............................................    2
   2. The SNMPv2 Network Management Framework ..................    2
   3. Object Definitions .......................................    2
   4. ATM Terminology ..........................................    3
   4.1 VCL/VPL and VCC/VPC .....................................    3
   4.2 PVC and SVC .............................................    5
   4.3 Traffic Management Parameters ...........................    5
   4.3.1 Traffic Policing and Traffic Shaping  Parameters ......    5
   4.3.2 Cell Loss Priority ....................................    6
   4.3.3 QoS Class .............................................    6
   5. Overview .................................................    7
   5.1 Background ..............................................    7
   5.2 Structure of the MIB ....................................    7
   5.3 ATM Interface Configuration Group .......................    7
   5.4 ATM Interface DS3 PLCP and TC Layer Groups ..............    8
   5.5 ATM Virtual Link and Cross-Connect Groups ...............    8
   6. Application of MIB II to ATM .............................    8
   6.1 The System Group ........................................    8
   6.2 The Interface Group .....................................    8
   6.2.1 Support of the ATM Cell Layer by ifTable ..............    9
   7. Support of the AAL3/4 Based Interfaces ...................   10
   8. Support of the AAL5 Managed Objects ......................   10
   8.1 Managing AAL5 in a Switch ...............................   11
   8.2 Managing AAL5 in a Host .................................   12
   8.3 Support of AAL5 by ifTable ..............................   13
   8.4 Support of Proprietary Virtual Interface  by  ifT-able ..   14
   8.5 AAL5 Connection Performance Statistics Group ............   15

Ahmed & Tesink                                                  [Page 1]
RFC 1695                 ATM Management Objects              August 1994

   9. ILMI MIB and the ATM Managed Objects .....................   15
   10. Definitions .............................................   18
   11. Acknowledgments .........................................   72
   12. References ..............................................   72
   13. Security Considerations .................................   73
   14. Authors' Addresses ......................................   73

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 objects used for managing ATM-based
   interfaces, devices, networks and services.

   This memo specifies a MIB module in a manner that is both compliant
   to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
   definitions.

2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      0    RFC 1442 [1] which defines the SMI, the mechanisms used
           for describing and naming objects for the purpose of
           management.

      0    STD 17, RFC 1213 [2] defines MIB-II, the core set of
           managed objects for the Internet suite of protocols.

      0    RFC 1445 [3] which defines the administrative and other
           architectural aspects of the framework.

      0    RFC 1448 [4] which defines the protocol used for network
           access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

3.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
Show full document text