Definitions of Managed Objects for the SIP Interface Type
RFC 1304

Document Type RFC - Proposed Standard (February 1992; No errata)
Obsoleted by RFC 1694
Last updated 2013-03-02
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1304 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             T. Cox
Request For Comments: 1304                                     K. Tesink
                                                                 Editors
                                            Bell Communications Research
                                                           February 1992

                     Definitions of Managed Objects
                       for the SIP Interface Type

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 SIP (SMDS Interface
   Protocol) objects.

Table of Contents

   1. The Network Management Framework ............................    2
   2. Objects .....................................................    2
   2.1 Format of Definitions ......................................    3
   3. Overview ....................................................    3
   4. Object Definitions ..........................................    4
   4.1 The SIP Level 3 group ......................................    4
   4.2 The SIP Level 2 group ......................................    8
   4.3 The SIP PLCP group .........................................   11
   4.3.1 The SIP DS1 PLCP group ...................................   12
   4.3.2 The SIP DS3 PLCP group ...................................   14
   4.4 The SMDS Applications group ................................   16
   4.5 The SMDS Carrier Selection group ...........................   18
   4.6 The SIP Error Log group ....................................   18
   5. Acknowledgments .............................................   23
   6. References ..................................................   23
   7. Security Considerations......................................   25
   8. Authors' Addresses...........................................   25

SNMP Working Group                                              [Page 1]
RFC 1304                      SIP Objects                  February 1992

1.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

      RFC 1155 [3] which defines the SMI, the mechanisms used for
      describing and naming objects for the purpose of management.  RFC
      1212 [9] defines a more concise description mechanism, which is
      wholly consistent with the SMI.

      RFC 1156 [4] which defines MIB-I, the core set of managed objects
      for the Internet suite of protocols.  RFC 1213 [6], defines MIB-
      II, an evolution of MIB-I based on implementation experience and
      new operational requirements.

      RFC 1157 [5] which defines the SNMP, the protocol used for network
      access to managed objects.

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

2.  Objects

   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)
   International Standard 8824 [7] defined in the SMI.  In particular,
   each object has a name, a syntax, and an encoding.  The name is an
   object identifier, an administratively assigned name, which specifies
   an object type.  The object type together with an object instance
   serves to uniquely identify a specific instantiation of the object.
   For human convenience, we often use a textual string, termed the
   OBJECT DESCRIPTOR, to also refer to the object type.

   The syntax of an object type defines the abstract data structure
   corresponding to that object type.  The ASN.1 language is used for
   this purpose.  However, the SMI RFC 1155 [3] purposely restricts the
   ASN.1 constructs which may be used.  These restrictions are
   explicitly made for simplicity.

   The encoding of an object type is simply how that object type is
   represented using the object type's syntax.  Implicitly tied to the
   notion of an object type's syntax and encoding is how the object type
   is represented when being transmitted on the network.  The SMI
   specifies the use of the basic encoding rules of ASN.1 International
   Standard 8825 [8], subject to the additional requirements imposed by
   the SNMP.

SNMP Working Group                                              [Page 2]
RFC 1304                      SIP Objects                  February 1992

2.1.  Format of Definitions

   Section 4 contains contains the specification of all object types
Show full document text