RFC relevance of reference

As per Relevance of the word reference, we have this rfc below:

Network Working Group D.
Request for Comments: 1381 Data General
F.
Advanced Computer
November 1992

SNMP MIB Extension for X.25

Status of this

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

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 Link Layer
X.25, LAPB. The objects defined here, along with the objects in
"SNMP MIB Extension for the Packet Layer of X.25" [9] and
"Definitions of Managed Objects for RS-232-like Hardware Devices
[8], combine to allow management of an X.25 protocol stack

Table of

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 Formal overview ....................................... 4
3.4 Tables ................................................ 5
3.5 Traps ................................................. 6
4. Object Definitions ..................................... 6
5. Appendix: Revision History ............................. 27
July 30, 1992 .......................................... 27
June 12, 1992 .......................................... 27
May 18, 1992 ........................................... 28
April 8, 1992 .......................................... 28
February 1992 .......................................... 28
October 1991 ........................................... 29
June 1991 .............................................. 30
April 1991 ............................................. 30

Throop & Baker [Page 1]

RFC 1381 X.25 LAPB MIB November 1992

6. Acknowledgements ....................................... 30
7. References ............................................. 31
8. Security Considerations ................................ 33
9. Authors' Addresses ..................................... 33

1. The Network Management

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

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

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

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

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

2.

The definition of an object in the MIB requires an object name
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,
assigned names, to specify object types. The object name,
with an optional object instance, uniquely identifies a
instance of an object. For human convenience, we often use a
string, termed the OBJECT DESCRIPTOR, to also refer to objects

Objects also have a syntax that defines the abstract data
corresponding to that object type. The ASN.1 language [6]

Throop & Baker [Page 2]

RFC 1381 X.25 LAPB MIB November 1992

the primitives used for this purpose. The SMI [1]
restricts the ASN.1 constructs which may be used for simplicity
ease of implementation. The encoding of an object type
describes how to represent an object using ASN.1 encoding rules [7],
for purposes of dealing with the SNMP protocol

2.1. Format of

Section 4 contains the specification of all object types defined
this MIB module. The object definitions use the conventions given
the SMI [1] as amended by the concise MIB definitions [4].

3.

3.1. Informal

This section describes how the objects defined below relate
other MIBs. This section is only informational to help
how the pieces fit together

The objects defined below are to be used in conjunction with MIB-
and other MIBs such as the X.25 packet level MIB [9]. A system
a complete X.25 stack running over a synchronous line will have
least two interfaces in the ifTable defined in MIB-II. There will
an interface for LAPB and another interface for the packet layer
X.25. There will also be objects defined in the RS-232-like MIB
the physical sync line

Each software interface identifies the layer below it used to
and receive packets. The X.25 MIB object, x25InfoDataLinkId
specifies an instance of lapbAdmnIndex for the LAPB interface
that X.25. The LAPB object, lapbOperPortId, defined below,
an instance of the rs232PortIndex for the the Sync line used by LAPB

For X.25 running over LAPB over Ethernet, the lapbAdmnPortId
identify the instance of ifIndex for the Ethernet interface

Each X.25 subnetwork will have separate entries in the ifTable.
a system with two X.25 lines would have two ifTable entries for
two X.25 packet layers and two other entries for the two
interfaces. Each X.25 Packet Layer MIB would identify the instance
the LAPB MIB below it. Each LAPB MIB would identify the Sync
below it. The system would also have two entries for rs232
and rs232SyncPortTable for the two physical lines

Since the ifTable as defined in MIB-II is device independent,
doesn't have anything specific for any type of interface.
objects below define the LAPB specific information for an

Throop & Baker [Page 3]

RFC 1381 X.25 LAPB MIB November 1992

of type LAPB. Different LAPB interfaces can also be differentiated
matching the values of ifIndex with lapbAdmnIndex

3.2. Textual

Two new data types are introduced as a textual conventions in
MIB document. These textual conventions enhance the readability
the specification and can ease comparison with other
if appropriate. It should be noted that the introduction of
textual conventions has no effect on either the syntax nor
semantics of any managed objects. The use of these is merely
artifact of the explanatory method used. Objects defined in terms
one of these methods are always encoded by means of the rules
define the primitive type. Hence, no changes to the SMI or the
are necessary to accommodate these textual conventions which
adopted merely for the convenience of readers and writers in
of the elusive goal of clear, concise, and unambiguous MIB documents

This MIB introduces the data types of

3.3. Formal

Instances of the objects defined below represent attributes of a
interface. LAPB interfaces are identified by an ifType object in
Internet-standard MIB [5]

lapb(16).

For these interfaces, the value of the ifSpecific variable in
MIB-II [5] has the OBJECT IDENTIFIER value

lapb OBJECT IDENTIFIER ::= { transmission 16 }

The relationship between a LAPB interface and an interface in
context of the Internet-standard MIB [5] is one-to-one. As such,
value of an ifIndex object instance can be directly used to
corresponding instances of the objects defined below

The objects defined below are defined in the context of ISO 7776 [10]
and ISO 8885 [11]. Access to those documents maybe useful (but isn'
essential) to understand the names and semantics of some objects
Where possible the object descriptions use the terminology of
7776; for example, one commonly used term refers to the peer LAPB
the DCE/remote DTE. This terminology does not restrict
instrumented LAPB to function only as a DTE. This MIB maybe

Throop & Baker [Page 4]

RFC 1381 X.25 LAPB MIB November 1992

to a LAPB configured as either a DCE or a DTE

To the extent that some attributes defined in the Internet
MIB [5] are applicable to LAPB, those objects have not
duplicated here. In some instances some clarification of how
apply those objects to LAPB has been given

Some objects defined below include a DEFVAL clause. This
provides reasonable (but not mandatory) default values to use
creating these objects. This does not imply this MIB defines
mechanism for creating or deleting LAPB interfaces. The creation
deletion of the objects of this MIB depend on the
method for creating and deleting LAPB interfaces. The DEFVAL
provides reasonable defaults to allow further extension of the MIB
define methods for creating and deleting LAPB interfaces
having to deprecate these objects for the lack of a DEFVAL clause

3.4.

This extension adds four tables to the MIB. These tables are

lapbAdmnTable
lapbOperTable
lapbFlowTable,
lapbXidTable

The lapbAdmnTable provides objects for common parameters used by
such as the T1 retransmission timer or the N2 retransmission counter
Changes to objects in this table need not affect a running
but provides access to the values used to initialize an interface
These values are read-write

The lapbOperTable provides objects to determine the
actually in use by an interface. These objects are read only.
values currently in use maybe different from the lapbAdmnTable
if the lapbAdmnTable was changed after interface initialization or
XID negotiation selected different values

The lapbFlowTable provides objects that report how the LAPB
performs. These are read-only objects used to monitor operation

The lapbXidTable is not required for systems that do not transmit
frames. For systems that do transmit XID frames, this table
the values for the fields of the XID frame that are not
present in the lapbAdmnTable. The objects in this table are read
write

Throop & Baker [Page 5]

RFC 1381 X.25 LAPB MIB November 1992

3.5.

Since all LAPB interfaces have entries in the ifTable,
changes in the state of the interface should send a linkUp
linkDown trap. Thus an interface that receives or sends a
Reject frame should send a linkDown trap. If the interface
comes back up, it should then send a linkUP trap

4. Object

RFC1381-MIB DEFINITIONS ::=

FROM RFC1155-

FROM RFC1213-
OBJECT-
FROM RFC-1212;

-- LAPB

lapb OBJECT IDENTIFIER ::= { transmission 16 }

PositiveInteger ::= INTEGER (0..2147483647)

IfIndexType ::= INTEGER (1..2147483647)
-- IfIndexType specifies an index object for a
-- with entries that match entries in the MIB-II ifTable
-- The value of the index for the table will match
-- ifIndex entry for same interface in the ifTable
-- The values of this object range from 1 to
-- inclusive

-- ###########################################################
-- LAPB Admn
-- ###########################################################

-- Support of the lapbAdmnTable is mandatory for
-- agents of systems that implement LAPB

lapbAdmnTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS

Throop & Baker [Page 6]

RFC 1381 X.25 LAPB MIB November 1992

"This table contains objects that can
changed to manage a LAPB interface
Changing one of these parameters may
effect in the operating LAPB immediately
may wait until the interface is
depending on the details of
implementation

Most of the objects in this read-write
have corresponding read-only objects in
lapbOperTable that return the
operating value

The operating values may be different
these configured values if changed by
negotiation or if a configured parameter
changed after the interface was started."
::= { lapb 1 }

lapbAdmnEntry OBJECT-
SYNTAX
ACCESS not-
STATUS

"Configured parameter values for a
LAPB."
INDEX { lapbAdmnIndex }
::= { lapbAdmnTable 1 }

LapbAdmnEntry ::= SEQUENCE {

IfIndexType

INTEGER

INTEGER
lapbAdmnTransmitN1
PositiveInteger
lapbAdmnReceiveN1
PositiveInteger

INTEGER

INTEGER
lapbAdmnN2
INTEGER
lapbAdmnT1

Throop & Baker [Page 7]

RFC 1381 X.25 LAPB MIB November 1992

PositiveInteger
lapbAdmnT2
PositiveInteger
lapbAdmnT3
PositiveInteger
lapbAdmnT4
PositiveInteger

INTEGER

}

lapbAdmnIndex OBJECT-
SYNTAX
ACCESS read-
STATUS

"The ifIndex value for the LAPB interface."
::= { lapbAdmnEntry 1 }

lapbAdmnStationType OBJECT-
SYNTAX INTEGER {
dte (1),
dce (2),
dxe (3)
}
ACCESS read-
STATUS

"Identifies the desired station type of
interface."
REFERENCE "ISO 7776 section 3.1"
DEFVAL { dte }
::= { lapbAdmnEntry 2 }

lapbAdmnControlField OBJECT-
SYNTAX INTEGER {
modulo8 (1),
modulo128 (2)
}
ACCESS read-
STATUS

"The desired size of the sequence
used to number frames."
REFERENCE "ISO 8885 Table 3, Name: HDLC Option - 10"
DEFVAL { modulo8 }

Throop & Baker [Page 8]

RFC 1381 X.25 LAPB MIB November 1992

::= { lapbAdmnEntry 3 }

lapbAdmnTransmitN1FrameSize OBJECT-
SYNTAX
ACCESS read-
STATUS

"The default maximum N1 frame size
in number of bits for a frame transmitted
this DTE. This excludes flags and 0
inserted for transparency."
REFERENCE "ISO 8885 Table 3,
Name: Information Field length
DEFVAL { 36000 } -- 4500 * 8; 802.5 Frame
::= { lapbAdmnEntry 4 }

lapbAdmnReceiveN1FrameSize OBJECT-
SYNTAX
ACCESS read-
STATUS

"The default maximum N1 frame size
in number of bits for a frame the DCE/
DTE transmits to this DTE. This
flags and 0 bits inserted for transparency."
DEFVAL { 36000 } -- 4500 * 8; 802.5 Frame
::= { lapbAdmnEntry 5 }

lapbAdmnTransmitKWindowSize OBJECT-
SYNTAX INTEGER (1..127)
ACCESS read-
STATUS

"The default transmit window size for
Interface. This is the maximum number
unacknowledged sequenced PDUs that may
outstanding from this DTE at any one time."
REFERENCE "ISO 8885 Table 3, Name: Window size
DEFVAL { 7 }
::= { lapbAdmnEntry 6 }

lapbAdmnReceiveKWindowSize OBJECT-
SYNTAX INTEGER (1..127)
ACCESS read-
STATUS

"The default receive window size for
Interface. This is the maximum number

Throop & Baker [Page 9]

RFC 1381 X.25 LAPB MIB November 1992

unacknowledged sequenced PDUs that may
outstanding from the DCE/remote DTE at
one time."
REFERENCE "ISO 8885 Table 3, Name: Window size
DEFVAL { 7 }
::= { lapbAdmnEntry 7 }

lapbAdmnN2RxmitCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS

"The default N2 retry counter for
interface. This specifies the number
times a PDU will be resent after the T
timer expires without an acknowledgement
the PDU."
REFERENCE "ISO 8885 Table 3,
Name: Retransmission Attempts
DEFVAL { 20 }
::= { lapbAdmnEntry 8 }

lapbAdmnT1AckTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The default T1 timer for this interface
This specifies the maximum time
Milliseconds to wait for acknowledgment of
PDU."
REFERENCE "ISO 8885 Table 3, Name
Acknowledgement timer
DEFVAL { 3000 }
::= { lapbAdmnEntry 9 }

lapbAdmnT2AckDelayTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The default T2 timer for this interface
This specifies the maximum time
Milliseconds to wait before sending
acknowledgment for a sequenced PDU. A
of zero means there will be no delay
acknowledgement generation."
REFERENCE "ISO 8885 Table 3,

Throop & Baker [Page 10]

RFC 1381 X.25 LAPB MIB November 1992

Name: Reply delay timer
DEFVAL { 0 }
::= { lapbAdmnEntry 10 }

lapbAdmnT3DisconnectTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The T3 timer for this interface.
specifies the time in Milliseconds to
before considering the link disconnected.
value of zero indicates the link will
considered disconnected upon completion
the frame exchange to disconnect the link."
REFERENCE "ISO 7776 section 5.7.1.3"
DEFVAL { 60000 }
::= { lapbAdmnEntry 11 }

lapbAdmnT4IdleTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The T4 timer for this interface.
specifies the maximum time in
to allow without frames being exchanged
the data link. A value of 2147483647
indicates no idle timer is being kept."
REFERENCE "ISO 7776 section 5.7.1.4"
DEFVAL { 2147483647 }
::= { lapbAdmnEntry 12 }

lapbAdmnActionInitiate OBJECT-
SYNTAX INTEGER {
sendSABM (1),
sendDISC (2),
sendDM (3),
none (4),
other (5)
}
ACCESS read-
STATUS

"This identifies the action LAPB will
to initiate link set-up."
DEFVAL { sendSABM }
::= { lapbAdmnEntry 13 }

Throop & Baker [Page 11]

RFC 1381 X.25 LAPB MIB November 1992

lapbAdmnActionRecvDM OBJECT-
SYNTAX INTEGER {
sendSABM (1),
sendDISC (2),
other (3)
}
ACCESS read-
STATUS

"This identifies the action LAPB will
when it receives a DM response."
DEFVAL { sendSABM }
::= { lapbAdmnEntry 14 }

-- ###########################################################
-- LAPB operating parameters
-- ###########################################################

-- Support of the lapbOperTable is mandatory for
-- agents of systems that implement LAPB

lapbOperTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS

"This table contains
information about interface
currently set in the interface. Many
these objects have corresponding objects
the lapbAdmnTable."
::= { lapb 2 }

lapbOperEntry OBJECT-
SYNTAX
ACCESS not-
STATUS

"Currently set parameter values for
specific LAPB."
INDEX { lapbOperIndex }
::= { lapbOperTable 1 }

LapbOperEntry ::= SEQUENCE {

IfIndexType

Throop & Baker [Page 12]

RFC 1381 X.25 LAPB MIB November 1992

INTEGER

INTEGER
lapbOperTransmitN1
PositiveInteger
lapbOperReceiveN1
PositiveInteger

INTEGER

INTEGER
lapbOperN2
INTEGER
lapbOperT1
PositiveInteger
lapbOperT2
PositiveInteger
lapbOperT3
PositiveInteger
lapbOperT4
PositiveInteger

OBJECT IDENTIFIER

OBJECT
}

lapbOperIndex OBJECT-
SYNTAX
ACCESS read-
STATUS

"The ifIndex value for the LAPB interface."
::= { lapbOperEntry 1 }

lapbOperStationType OBJECT-
SYNTAX INTEGER {
dte (1),
dce (2),
dxe (3)
}
ACCESS read-
STATUS

"Identifies the current operating
type of this interface. A value of dxe (3)
indicates XID negotiation has not yet
place."

Throop & Baker [Page 13]

RFC 1381 X.25 LAPB MIB November 1992

REFERENCE "ISO 7776 section 3.1"
::= { lapbOperEntry 2 }

lapbOperControlField OBJECT-
SYNTAX INTEGER {
modulo8 (1),
modulo128 (2)
}
ACCESS read-
STATUS

"The current operating size of the
numbers used to number frames."
REFERENCE "ISO 7776 section 3.3"
::= { lapbOperEntry 3 }

lapbOperTransmitN1FrameSize OBJECT-
SYNTAX
ACCESS read-
STATUS

"The current operating N1 frame size
for the maximum number of bits in a
this DTE can transmit. This excludes
and 0 bits inserted for transparency."
REFERENCE "ISO 7776 section 5.7.3"
::= { lapbOperEntry 4 }

lapbOperReceiveN1FrameSize OBJECT-
SYNTAX
ACCESS read-
STATUS
-- See lapbOperTransmitN1FrameSize

"The current operating N1 frame size
for the maximum number of bits in a
the DCE/remote DTE can transmit.
excludes flags and 0 bits inserted
transparency."
::= { lapbOperEntry 5 }

lapbOperTransmitKWindowSize OBJECT-
SYNTAX INTEGER (1..127)
ACCESS read-
STATUS

"The current PDU window size this
uses to transmit. This is the

Throop & Baker [Page 14]

RFC 1381 X.25 LAPB MIB November 1992

number of unacknowledged sequenced PDUs
may be outstanding from this DTE at any
time."
REFERENCE "ISO 7776 section 5.7.4"
::= { lapbOperEntry 6 }

lapbOperReceiveKWindowSize OBJECT-
SYNTAX INTEGER (1..127)
ACCESS read-
STATUS

"The current receive PDU window size
this Interface. This is the maximum
of unacknowledged sequenced PDUs that may
outstanding from the DCE/remote DTE at
one time."
REFERENCE "ISO 7776 section 5.7.4"
::= { lapbOperEntry 7 }

lapbOperN2RxmitCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS

"The current N2 retry counter used for
interface. This specifies the number
times a PDU will be resent after the T
timer expires without an acknowledgement
the PDU."
REFERENCE "ISO 7776 section 5.7.2"
::= { lapbOperEntry 8 }

lapbOperT1AckTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The current T1 timer for this interface
This specifies the maximum time
Milliseconds to wait for acknowledgment of
PDU."
REFERENCE "ISO 7776 section 5.7.1.1"
::= { lapbOperEntry 9 }

lapbOperT2AckDelayTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

Throop & Baker [Page 15]

RFC 1381 X.25 LAPB MIB November 1992

"The current T2 timer for this interface
This specifies the maximum time
Milliseconds to wait before sending
acknowledgment for a sequenced PDU. A
of zero means there will be no delay
acknowledgement generation."
REFERENCE "ISO 7776 section 5.7.1.2"
::= { lapbOperEntry 10 }

lapbOperT3DisconnectTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The current T3 timer for this interface
This specifies the time in Milliseconds
wait before considering the
disconnected. A value of zero indicates
link will be considered disconnected
completion of the frame exchange
disconnect the link."
REFERENCE "ISO 7776 section 5.7.1.3"
::= { lapbOperEntry 11 }

lapbOperT4IdleTimer OBJECT-
SYNTAX
ACCESS read-
STATUS

"The current T4 timer for this interface
This specifies the maximum time
Milliseconds to allow without frames
exchanged on the data link. A value
2147483647 indicates no idle timer is
kept."
REFERENCE "ISO 7776 section 5.7.1.4"
::= { lapbOperEntry 12 }

lapbOperPortId OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS

"This object identifies an instance of
index object in the first group of
in the MIB specific to the physical
or interface used to send and

Throop & Baker [Page 16]

RFC 1381 X.25 LAPB MIB November 1992

frames. If an agent does not support
such objects, it should return
OBJECT IDENTIFIER {0 0}."
::= { lapbOperEntry 13 }

lapbOperProtocolVersionId OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS

"This object identifies the version of
lapb protocol implemented by
interface."
::= { lapbOperEntry 14 }

-- ###########################################################
-- LAPB Flow
-- ###########################################################

-- Support of the lapbFlowTable is mandatory for
-- agents of systems that implement LAPB

lapbFlowTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS

"This table defines the objects recorded
LAPB to provide information about
traffic flow through the interface."
::= { lapb 3 }

lapbFlowEntry OBJECT-
SYNTAX
ACCESS not-
STATUS

"The information regarding the effects
flow controls in LAPB."
INDEX { lapbFlowIfIndex }
::= { lapbFlowTable 1 }

LapbFlowEntry ::= SEQUENCE {

IfIndexType

Counter

Throop & Baker [Page 17]

RFC 1381 X.25 LAPB MIB November 1992

INTEGER

INTEGER

Counter

Counter

Counter
lapbFlowT1
Counter

OCTET STRING

OCTET STRING

OCTET
}

lapbFlowIfIndex OBJECT-
SYNTAX
ACCESS read-
STATUS

"The ifIndex value for the LAPB Interface."
::= { lapbFlowEntry 1 }

lapbFlowStateChanges OBJECT-
SYNTAX
ACCESS read-
STATUS

"The number of LAPB State Changes,
resets."
::= { lapbFlowEntry 2 }

lapbFlowChangeReason OBJECT-
SYNTAX INTEGER {
notStarted (1), -- Initial
abmEntered (2), -- SABM or
abmeEntered (3), -- SABME or
abmReset (4), -- SABM in
abmeReset (5), -- SABME in
dmReceived (6), -- DM
dmSent (7), -- DM
discReceived (8), -- DISC
discSent (9), -- DISC

Throop & Baker [Page 18]

RFC 1381 X.25 LAPB MIB November 1992

frmrReceived (10), -- FRMR
frmrSent (11), -- FRMR
n2Timeout (12), -- N2 Timer
other (13)
}
ACCESS read-
STATUS

"The reason for the most recent
of lapbFlowStateChanges. A DM or DISC
generated to initiate link set-up does
alter this object. When the MIB-II
ifOperStatus does not have a value
testing, there exists a correlation
this object and ifOperStatus.
will have a value of up when this
contains: abmEntered, abmeEntered
abmReset, or abmeReset. IfOperStatus
have a value of down when this object has
value of notStarted, or dmReceived
n2Timeout. There is no correlation
this object has the value other."
::= { lapbFlowEntry 3 }

lapbFlowCurrentMode OBJECT-
SYNTAX INTEGER {
disconnected (1),
-- initial state or DISC

linkSetup (2),
-- SABM

frameReject (3),
-- Invalid frame received
-- FRMR

disconnectRequest (4),
-- DISC

informationTransfer (5),
-- normal information transfer
-- SABM(E) sent and UA received,
-- SABM(E) received and UA

rejFrameSent (6),
-- invalid NS received and REJ

waitingAcknowledgement (7),

Throop & Baker [Page 19]

RFC 1381 X.25 LAPB MIB November 1992

-- T1 expired and RR

stationBusy (8),
-- RNR

remoteStationBusy (9),
-- RNR

bothStationsBusy (10),
-- RNR received and RNR

waitingAckStationBusy (11),
-- T1 expired, RNR

waitingAckRemoteBusy (12),
-- T1 expired, RNR

waitingAckBothBusy (13),
-- T1 expired, RNR sent
-- and RNR

rejFrameSentRemoteBusy (14),
-- REJ sent and RNR

xidFrameSent (15),
-- XID frame

error (16),
-- An error state other
-- a one defined

other (17)
-- A state not listed
}
ACCESS read-
STATUS

"The current condition of the conversation."
::= { lapbFlowEntry 4 }

lapbFlowBusyDefers OBJECT-
SYNTAX
ACCESS read-
STATUS

"The number of times this device was
to transmit a frame due to a
remote busy condition. Busy conditions

Throop & Baker [Page 20]

RFC 1381 X.25 LAPB MIB November 1992

result from the receipt of an RNR from
remote device, the lack of valid
number space (window saturation), or
conditions."
::= { lapbFlowEntry 5 }

lapbFlowRejOutPkts OBJECT-
SYNTAX
ACCESS read-
STATUS

"The number of REJ or SREJ frames sent
this station."
::= { lapbFlowEntry 6 }

lapbFlowRejInPkts OBJECT-
SYNTAX
ACCESS read-
STATUS

"The number of REJ or SREJ frames
by this station."
::= { lapbFlowEntry 7 }

lapbFlowT1Timeouts OBJECT-
SYNTAX
ACCESS read-
STATUS

"The number of times a re-transmission
effected by the T1 Timer expiring."
::= { lapbFlowEntry 8 }

lapbFlowFrmrSent OBJECT-
SYNTAX OCTET STRING (SIZE (0..7))
ACCESS read-
STATUS

"The Information Field of the FRMR
recently sent. If no FRMR has been
(the normal case) or the information isn'
available, this will be an OCTET STRING
zero length."
REFERENCE "ISO 7776 Section 4.3.9, tables 7 and 8"
::= { lapbFlowEntry 9 }

lapbFlowFrmrReceived OBJECT-
SYNTAX OCTET STRING (SIZE (0..7))

Throop & Baker [Page 21]

RFC 1381 X.25 LAPB MIB November 1992

ACCESS read-
STATUS

"The Information Field of the FRMR
recently received. If no FRMR has
received (the normal case) or
information isn't available, this will be
OCTET STRING of zero length."
REFERENCE "ISO 7776 Section 4.3.9, tables 7 and 8"
::= { lapbFlowEntry 10 }

lapbFlowXidReceived OBJECT-
SYNTAX OCTET STRING (SIZE (0..8206))
ACCESS read-
STATUS

"The Information Field of the XID frame
recently received. If no XID frame has
received, this will be an OCTET STRING
zero length."
REFERENCE "ISO 8885"
::= { lapbFlowEntry 11 }

-- ###########################################################
-- LAPB XID
-- ###########################################################

-- Support for the lapbXidTable is mandatory for all
-- of systems that have a LAPB implementation using
-- negotiation. Agents of systems without XID
-- support should not implement this table

lapbXidTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS

"This table defines values to use for
negotiation that are not found in
lapbAdmnTable. This table is optional
implementations that don't support XID
mandatory for implementations that
initiate XID negotiation."
::= { lapb 4 }

lapbXidEntry OBJECT-
SYNTAX

Throop & Baker [Page 22]

RFC 1381 X.25 LAPB MIB November 1992

ACCESS not-
STATUS

"XId negotiation parameter values for
specific LAPB."
INDEX { lapbXidIndex }
::= { lapbXidTable 1 }

LapbXidEntry ::= SEQUENCE {

IfIndexType

OCTET STRING

OCTET STRING

OCTET STRING

OCTET STRING

OCTET STRING

OCTET
}

lapbXidIndex OBJECT-
SYNTAX
ACCESS read-
STATUS

"The ifIndex value for the LAPB interface."
::= { lapbXidEntry 1 }

lapbXidAdRIdentifier OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS

"The value of the Address
Identifier. A zero length string
no Identifier value has been assigned."
REFERENCE "ISO 8885 Table 2, Name: Identifier
DEFVAL { ''h }
::= { lapbXidEntry 2 }

lapbXidAdRAddress OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))

Throop & Baker [Page 23]

RFC 1381 X.25 LAPB MIB November 1992

ACCESS read-
STATUS

"The value of the Address
Address. A zero length string indicates
Address value has been assigned."
REFERENCE "ISO 8885 Table 2, Name: Address
DEFVAL { ''h }
::= { lapbXidEntry 3 }

lapbXidParameterUniqueIdentifier OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS

"The value of the parameter
Identifier. A zero length string
no Unique identifier value has
assigned."
REFERENCE "ISO 8885 Table 3, Name: Identifier
DEFVAL { ''h }
::= { lapbXidEntry 4 }

lapbXidGroupAddress OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS

"The value of the parameter Group address
A zero length string indicates no
address value has been assigned."
REFERENCE "ISO 8885 Table 3, Name: Group address
DEFVAL { ''h }
::= { lapbXidEntry 5 }

lapbXidPortNumber OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
ACCESS read-
STATUS

"The port number assigned for this link.
zero length string indicates no local
number identifier has been assigned."
REFERENCE "ISO 8885 Table 3, Name: Port number
DEFVAL { ''h }
::= { lapbXidEntry 6 }

lapbXidUserDataSubfield OBJECT-

Throop & Baker [Page 24]

RFC 1381 X.25 LAPB MIB November 1992

SYNTAX OCTET STRING (SIZE (0..8206))
ACCESS read-
STATUS

"A user data subfield, if any, to
transmitted in an XID frame. A zero
frame indicates no user data subfield
been assigned. The octet string
include both the User data identifier
User data field as shown in Figures 1
4."
REFERENCE "ISO 8885 section 4.3"
DEFVAL { ''h }
::= { lapbXidEntry 7 }

-- ###########################################################
-- LAPB protocol
-- ###########################################################

lapbProtocolVersion OBJECT
::= { lapb 5 }

lapbProtocolIso7776v1986 OBJECT
::= { lapbProtocolVersion 1 }

lapbProtocolCcittV1980 OBJECT
::= { lapbProtocolVersion 2 }

lapbProtocolCcittV1984 OBJECT
::= { lapbProtocolVersion 3 }

-- The following describes some of the MIB-II
-- objects and their relationship with the objects in
-- MIB extension

-- ifDescr: describes the interface. It should
-- identification information for the physical line and
-- description of the network. For connections to PDNs
-- it should name the PDN

-- ifMtu: the maximum number of octets an upper layer
-- pass to this interface as a single frame

-- ifSpeed

Throop & Baker [Page 25]

RFC 1381 X.25 LAPB MIB November 1992

-- ifAdminStatus

-- ifOperStatus

-- ifLastChange: the last time the state of the
-- changed. A reset is considered an instantaneous change
-- the ndm state and back to abm or abme. This will be
-- last time that lapbFlowChangeReason and
-- changed

-- ifInOctets: contains the number of
-- received from the peer LAPB including FCS

-- ifInUcastPkts: contains the number of I-frames
-- by this interface to a higher layer interface

-- ifInDiscards: contains the number of
-- frames discarded because of internal
-- (such as lack of buffering).

-- ifInErrors: contains the number of Invalid frames received
-- This does not have any relationship with the number REJ
-- or RNR frames sent or received

-- ifInUnknownProtos: contains the number of
-- that were correct but were dropped because
-- were inappropriate for the current state.
-- includes an invalid Poll bit, an unknown address
-- or other condition such as an RNR when
-- not established. This also includes the number
-- DISC or other frames that were ignored because
-- link was not established and this interface was
-- configured to perform link setup on that type frame

-- ifOutOctets: number of octets sent to peer
-- FCS octets

-- ifOutUcastPkts: number of I-frames received
-- a higher layer for transmission to peer

-- ifOutDiscards: number of frames to be sent that
-- dropped due to internal conditions such as buffering etc

-- ifOutErrors: number of transmissions that
-- due to errors or were considered invalid by the receiver
-- This does not have any relationship with the number REJ
-- or RNR frames sent or received

Throop & Baker [Page 26]

RFC 1381 X.25 LAPB MIB November 1992

-- ifOutQLen: number of frames waiting to be transmitted

-- This MIB does not provide any support for
-- Multilink procedure (MLP) in ISO 7776 section 6
-- LLC Pbit
-- LLC REJ
-- LLC Busy State Timer 7.8.1.4

-- ###########################################################

5. Appendix: Revision

July 30, 1992

The July revision of this document (Editor's Internal Reference 2.10)
incorporated the comments of the SNMP directorate

The ifIndexType textual convention was added and used as the
for all index objects

The enumeration xidDetection of the lapbAdmnStationType
changed to dxe to be consistent with other similar enumerations

Conformance statements were added at before every table as ASN.1
comments

June 12, 1992

The June 12, 1992 revision of this document (Editor's
Reference 2.9) incorporated some clarifications and updated
status

The range on PositiveInteger was changed to start at 0 rather
1.

The syntax of lapbXidIndex was changed to PositiveInteger

A value of dxe was added to lapbOperStationType

The range of lapbAdmnN2RxmitCount was change to (0..65535).

The definition of ifInOctets, ifInUcastPkts, ifInErrors
ifInUnknownProtos, ifOutOctets, and ifoutUcastPkts was clarified

Throop & Baker [Page 27]

RFC 1381 X.25 LAPB MIB November 1992

May 18, 1992

The May 18, 1992 revision of this document (Editor's
Reference 2.8) incorporated the following changes

The states of lapbFlowCurrentMode were redefined

The default value for lapbAdmnControlField was changed
module8 to modulo8.

April 8, 1992

The April 8, 1992 revision of this document (Editor's
Reference 2.4) incorporated the following changes

All reference comments in the MIB were moved to the
field of the OBJECT-TYPE macro

A type of PositiveInteger was introduced and used for
integer values including all timers. This effectively made
maximum value for timers 2147483646 milliseconds. The type of
frame size was changed to positiveInteger

The reference to ISO 7776 has been broadened to say the
descriptions use the terminology of ISO 7776.

A comment was added to the overview section discussing
and deletion of tables

The objects in the lapbParmTable and lapbDefTable
redistributed to create a lapbOperTable, a lapbAdmnTable, and
lapbXidTable. The lapbParmTable and lapbDefTable were deleted
Objects were included in the Admn table for t3 and t4.

An object identifier was added to identify the protocol version

A DEFVAL clause was added for all writable objects

Some more overview text was included

February 1992

The February 1992 revision of this document (Editor's
Reference 1.17) incorporated the following changes

The name was changed from HDLC to LAPB. This change was
because other flavors of HDLC such as LAPD, SDLC, and raw
framing, are different enough that this MIB will not

Throop & Baker [Page 28]

RFC 1381 X.25 LAPB MIB November 1992

manage them

The Historical Perspective section at the beginning of
document has been replaced with a more concise Network
Framework section

The name lapbParmKWindowSize was changed
lapbParmTransmitKWindowSize and the
lapbParmReceiveKWindowSize was added. This change was made
section 5.7.4 of ISO 7776 and Table 3 of ISO 8885 have
for different values for the transmit and receive window size

The name lapbParmN1FrameSize was changed
lapbParmTransmitN1FrameSize and the
lapbParmReceiveN1FrameSize was added. This change was made
section 5.7.3 of ISO 7776 and Table 3 of ISO 8886 have
for different values for the transmit and receive maximum
size

The object lapbParmPortIndex was deleted and the description
lapbParmPortId was changed. The object lapbParmPortId
identifies an instance of the index object for the MIB of
physical device or interface below LAPB

The units for the timers were changed to Milliseconds to
consistent with ISO 8885; see table 3.

The objects lapbParamT2AckDelayTimer
lapbParamT3DisconnectTimer both allow values of 0 to indicate
timer is not being used

The object lapbParamT4IdleTimer has a value to indicate timer
in use

The object lapbFlowXidReceived was added to the flow table

The lapbDefTable was added

Ranges and sizes were added for all INTEGERs and OCTET
that didn't have them

October 1991

The October 1991 revision of this document basically changed the
from LAPB to HDLC to make the objects more appropriate for a
range of uses. A number of minor changes were made to bring
objects in line with established conventions. These changes are
follows

Throop & Baker [Page 29]

RFC 1381 X.25 LAPB MIB November 1992

The enumerated values of hdlcParmStationType were renumbered
0 and 1 to 1 and 2.

The object hdlcFlowBusyDefer was renamed hdlcFlowBusyDefers

The object hdlcFlowRejSent was rename hdlcFlowRejOutPkts

The object hdlcFlowRejReceived was renamed hdlcFlowRejInPkts

June 1991

The June revision of this document incorporated much of the E-
discussion of the first draft. In particular it replaced
lapbStatTable (and all contents) with the lapbFlowTable

April 1991

The April 24 version of this document was the first release. At
time this document was basically a bunch of objects synthesized
various vendor MIBs and a quick reading of ISO 7776 [10]. On
reading it appeared to instrument too many LAPB normal functions
too few exceptional conditions. The lapbStatTable was too long
needed to be redone

6.

This document was produced by the x25mib working group

Fred Baker,
Art Berggreen,
Frank
Gary Bjerke,
Bill Bowman,
Christopher Bucci,
Charles Carvalho,
Jeff Case, Snmp
Angela Chen,
Carson Cheung,
Tom Daniel, Spider
Chuck Davin,
Billy Durham,
Richard Fox,
Doug Geller, Data
Herve Goguely, LIR
Andy Goldthorpe, british-
Walter D.
David
Steve Huston, Process Software

Throop & Baker [Page 30]

RFC 1381 X.25 LAPB MIB November 1992

Jon Infante,
Frank Kastenholz,
Zbigniew Kielczewski,
Cheryl Krupezak, Georgia
Mats Lindstrom, Diab Data
Andrew Malis,
Evan McGinnis, 3
Gary (G.P.)Mussar,
Chandy Nilakantan, 3
Randy Pafford, Data
Ragnar Paulson, The Software Group
Dave Perkins,
Walter Pinkarschewsky,
Karen Quidley, Data
Chris Ranch,
Paul S. Rarey, DHL Systems Inc
Jim Roche, Newbridge
Philippe Roger, LIR Corp
Timon
Mike Shand,
Brad Steina,
Bob Stewart,
Tom Sullivan, Data
Rodney Thayer, Sable Technology
Mark Therieau,
Jane Thorn, Data
Dean Throop, Data
Maurice Turcotte, Racal
Mike Zendels, Data

In addition, the comments of the following individuals are
acknowledged

Keith

7.

[1] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, Performance Systems International, Hughes LAN Systems,
1990.

[2] McCloghrie K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.

[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "

Throop & Baker [Page 31]

RFC 1381 X.25 LAPB MIB November 1992

Network Management Protocol", STD 15, RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.

[4] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
STD 16, RFC 1212, Performance Systems International, Hughes
Systems, March 1991.

[5] Rose M., Editor, "Management Information Base for
Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213,
Performance Systems International, March 1991.

[6] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.

[7] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation
(ASN.1), International Organization for Standardization
International Standard 8825, December 1987.

[8] Stewart, B., Editor, "Definitions of Managed Objects for RS-232-
like Hardware Devices", RFC 1317, Xyplex, Inc., April 1992.

[9] Throop, D., Editor, "SNMP MIB extension for the Packet Layer
X.25", RFC 1382, Data General Corporation, November 1992.

[10] "Information processing systems - Data communication - High-
data link control procedure - Description of the X.25 LAPB
compatible DTE data link procedures", International
for Standardization, International Standard 7776, December 1986.

[11] "Information technology - Telecommunications and
exchange between systems - High-level data link control (HDLC
procedures - General purpose XID frame information field
and format", International Organization for Standardization
International Standard 8885.

Throop & Baker [Page 32]

RFC 1381 X.25 LAPB MIB November 1992

8. Security

Security issues are not discussed in this memo

9. Authors'

Dean D.
Data General
62 Alexander Dr
Research Triangle Park, NC 27709

Phone: (919)248-8421
EMail: throop@dg-rtp.dg.

Fred
Advanced Computer
315 Bollay
Santa Barbara, CA 93101

Phone: (805) 685-4455
EMail: fbaker@acc.

While the working group has completed discussion of this document
comments are still welcome. Please send comments to the x25
working group at: x25mib@dg-rtp.dg.

Throop & Baker [Page 33]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX