SNMP MIB Extension for the X.25 Packet Layer
RFC 1382

Document Type RFC - Proposed Standard (November 1992; No errata)
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 1382 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                  D. Throop, Editor
Request for Comments: 1382                      Data General Corporation
                                                           November 1992

              SNMP MIB Extension for the X.25 Packet Layer

Status of this Memo

   This RFC specifies an IAB standards track protocol for the Internet
   community, and requests discussion and suggestions for improvements.
   Please refer to the current edition of the "IAB Official Protocol
   Standards" for the standardization state and status of this protocol.
   Distribution of this memo is unlimited.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing the Packet Layer of
   X.25.  The objects defined here, along with the objects in the "SNMP
   MIB Extension for LAPB" [9] and the "Definitions of Managed Objects
   for RS-232-like Hardware Devices" [8], combine to allow management of
   an X.25 protocol stack.

Table of Contents

   1. The Network Management Framework .......................    2
   2. Objects ................................................    2
   2.1 Format of Definitions .................................    3
   3. Overview ...............................................    3
   3.1 Informal Overview .....................................    3
   3.2 Textual Conventions ...................................    4
   3.3 Structure of MIB ......................................    4
   3.4 Tables ................................................    5
   3.5 Table Usage ...........................................    6
   3.6 Conformance ...........................................    6
   4. Object Definitions .....................................    7
   5. Appendix: Revision History .............................   62
      July 30 1992 ...........................................   62
      June 26 1992 ...........................................   62
      June 1992 ..............................................   63
      April 1992 .............................................   63
      February 1992 ..........................................   65
      October 1991 ...........................................   65
      June 1991 ..............................................   66
      April 1991 .............................................   66
   6. Acknowledgements .......................................   66

Throop                                                          [Page 1]
RFC 1382                 X.25 Packet Layer MIB             November 1992

   7. References .............................................   67
   8. Security Considerations ................................   68
   9. Author's Address .......................................   69

1.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  These components give the rules for defining objects,
   the definitions of objects, and the protocol for manipulating
   objects.

   The network management framework structures objects in an abstract
   information tree. The branches of the tree name objects and the
   leaves of the tree contain the values manipulated to effect
   management. This tree is called the Management Information Base or
   MIB. The concepts of this tree are given in STD 16/RFC 1155, "The
   Structure of Management Information" or SMI [1]. The SMI defines the
   trunk of the tree and the types of objects used when defining the
   leaves. STD 16/RFC 1212, "Towards Concise MIB Definitions" [4],
   defines a more concise description mechanism that preserves all the
   principals of the SMI.

   The core MIB definitions for the Internet suite of protocols can be
   found in RFC 1156 [2] "Management Information Base for Network
   Management of TCP/IP-based internets". STD 17/RFC 1213 [5] defines
   MIB-II, an evolution of MIB-I with changes to incorporate
   implementation experience and new operational requirements.

   STD 15/RFC 1157 [3] defines the SNMP protocol itself. The protocol
   defines how to manipulate the objects in a remote MIB.

   The tree structure of the MIB allows new objects to be defined for
   the purpose of experimentation and evaluation.

2.  Objects

   The definition of an object in the MIB requires an object name and
   type.  Object names and types are defined using the subset of
   Abstract Syntax Notation One (ASN.1) [6] defined in the SMI [1].
   Objects are named using ASN.1 object identifiers, administratively
   assigned names, to specify object types.  The object name, together
   with an optional object instance, uniquely identifies a specific
   instance of an object.  For human convenience, we often use a textual
   string, termed the OBJECT DESCRIPTOR, to also refer to objects.

   Objects also have a syntax that defines the abstract data structure
Show full document text