Definitions of Managed Objects for ATM Management
RFC 2515

Document Type RFC - Proposed Standard (February 1999; No errata)
Obsoletes RFC 1695
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 2515 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                 K. Tesink, Editor
Request for Comments: 2515                 Bell Communications Research
Obsoletes: 1695                                           February 1999
Category: Standards Track

                     Definitions of Managed Objects
                           for ATM Management

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 (1999).  All Rights Reserved.

Table of Contents

   1 Abstract  .............................................    2
   2 The SNMP Network Management Framework .................    2
   3 ATM Terminology .......................................    3
   3.1 VCL/VPL and VCC/VPC .................................    3
   3.2 PVC, SVC and Soft PVC ...............................    5
   3.3 Traffic Management Parameters .......................    6
   3.3.1 Traffic Policing and Traffic Shaping  Parameters
        ....................................................    6
   3.3.2 Cell Loss Priority ................................    6
   3.3.3 QoS Class .........................................    6
   3.3.4 Service Category ..................................    7
   3.4 Max Active and Max Current VPI and VCI Bits .........    7
   4 Overview ..............................................    8
   4.1 Background ..........................................    8
   4.2 Structure of the MIB ................................    9
   4.3 ATM Interface Configuration Table ...................    9
   4.4 ATM Interface DS3 PLCP and TC Layer Tables ..........    9
   4.5 ATM Virtual Link and Cross-Connect Tables ...........    9
   5 Application of MIB II to ATM ..........................   10
   5.1 The System Group ....................................   10
   5.2 The Interface Group .................................   10
   5.2.1 Support of the ATM Cell Layer by ifTable ..........   10
   6 Support of the AAL3/4 Based Interfaces ................   12
   7 Support of the AAL5 Managed Objects ...................   12
   7.1 Managing AAL5 in a Switch ...........................   12

Tesink                      Standards Track                     [Page 1]
RFC 2515                 ATM Management Objects            February 1999

   7.2 Managing AAL5 in a Host .............................   14
   7.3 Support of AAL5 by ifTable ..........................   15
   7.4 Support of Proprietary Virtual Interface  by  ifT-
        able ...............................................   16
   7.5 AAL5 Connection Performance Statistics Table ........   17
   8 ILMI MIBs and the ATM Managed Objects .................   18
   9 Definitions ...........................................   20
   10 Acknowledgments ......................................   83
   11 References ...........................................   83
   12 Security Considerations ..............................   85
   13 Author's Address .....................................   85
   14 Intellectual Property ................................   86
   15 Full Copyright Statement .............................   87

1.  Abstract

   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 replaces RFC 1695 [24].  Changes relative to RFC 1695 are
   summarized in the MIB module's REVISION clause.

   Textual Conventions used in this MIB are defined in [6] and [19].

2.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

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

   0    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 STD 16, RFC 1155 [2], STD 16, 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].

   0    Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, 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].

Tesink                      Standards Track                     [Page 2]
RFC 2515                 ATM Management Objects            February 1999
Show full document text