RFC 1407 (rfc1407) - Page 3 of 43
Definitions of Managed Objects for the DS3/E3 Interface Type
Alternative Format: Original Text Document
RFC 1407 DS3/E3 MIB January 1993
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 [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 [8], subject
to the additional requirements imposed by the SNMP.
2.1. Format of Definitions
Section 4 contains contains the specification of all object types
contained in this MIB module. The object types are defined using the
conventions defined in the SMI, as amended by the extensions
specified in STD 16, RFC 1212 [13].
2.2. Changes from RFC 1233
This MIB obsoletes RFC 1233. The changes from RFC 1233 are the
following:
-- This MIB module contains information to manage
an E3 interface, also.
-- This MIB module contains three groups:
DS3/E3 Near End Group which is mandatory,
DS3 Far End Group which is optional, and
DS3 Fractional Group which is optional.
-- The DS3 Far End Group is a new group and contains
configuration information and statistics
that are collected from the far end DS3/E3 interface.
Presently, the Far End Group may only be implemented by
DS3 systems that use C-bit Parity or SYNTRAN.
-- The DS3 Fractional Group is a new group and is
modeled after the DS1 Fractional Group.
-- ds3CSUIndex has been redefined and renamed
to dsx3LineIndex. This object
is the identifier of a DS3/E3 Interface on a device.
On a CSU, a single DS3/E3 data stream will cross two DS3/E3
interfaces, which have separate dsx3LineIndex values.
Trunk MIB Working Group