As per Relevance of the word indicate, we have this rfc below:
Network Working Group B. Stewart,
Request for Comments: 1316 Xyplex, Inc
April 1992
Definitions of Managed
for Character Stream
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
1.
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 the management of
stream devices
2. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
RFC 1155 which defines the SMI, the mechanisms used for
and naming objects for the purpose of management. RFC 1212 defines
more concise description mechanism, which is wholly consistent
the SMI
RFC 1156 which defines MIB-I, the core set of managed objects for
Internet suite of protocols. RFC 1213, defines MIB-II, an
of MIB-I based on implementation experience and new
requirements
RFC 1157 which defines the SNMP, the protocol used for network
to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
3.
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
Character MIB Working Group [Page 1]
RFC 1316 Character MIB April 1992
defined using the subset of Abstract Syntax Notation One (ASN.1) [7]
defined in the SMI. In particular, each object has a name, a syntax
and an encoding. The name is an object identifier,
administratively assigned name, which specifies an object type
The object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the
DESCRIPTOR, to also refer to the object type
The syntax of an object type defines the abstract data
corresponding to that object type. The ASN.1 language is used
this purpose. However, the SMI [3] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly
for simplicity
The encoding of an object type is simply how that object type
represented using the object type's syntax. Implicitly tied to
notion of an object type's syntax and encoding is how the object
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
3.1. Format of
Section 5 contains the specification of all object types contained
this MIB module. The object types are defined using the
defined in the SMI, as amended by the extensions specified in [9,10].
4.
The Character MIB applies to interface ports that carry a
stream, whether physical or virtual, serial or parallel,
or asynchronous. The most common example of a character port is
hardware terminal port with an RS-232 interface. Another
hardware example is a parallel printer port, say with a
interface. The concept also includes virtual terminal ports, such
a software connection point for a remote console
The Character MIB is one of a set of MIBs designed for
use. At this writing, the set comprises
Character
PPP
RS-232-like
Parallel-printer-like
Character MIB Working Group [Page 2]
RFC 1316 Character MIB April 1992
The RS-232-like MIB and the Parallel-printer-like MIB represent
physical layer, providing service to higher layers such as
Character MIB or PPP MIB. Further MIBs may appear above these
The following diagram shows two possible "MIB stacks", each using
RS-232-like MIB
.-----------------.
.-----------------. | Standard MIB |
| Telnet MIB | | Interface Group |
|-----------------| |-----------------|
| Character MIB | | PPP MIB |
|-----------------| |-----------------|
| RS-232-like MIB | | RS-232-like MIB |
`-----------------' `-----------------'
The intent of the model is for the physical-level MIBs to
the lowest level, regardless of the higher level that may be
it. In turn, separate higher level MIBs represent
applications, such as a terminal (the Character MIB) or a
connection (the PPP MIB).
For the most part, character ports are distinct from
interfaces (which are already covered by the Interface group).
general, they are attachment points for non-network devices.
exception is a character port that can support a network protocol
such as SLIP or PPP. This implies the existence of a
entry in the Interfaces table, with ifOperStatus of 'off' while
port is not running a network protocol and 'on' if it is. The
is that such usage is exclusive of non-network character
usage. That is, while switched to network use,
would be 'down' and Character MIB operational values such
charPortInFlowState and charPortInCharacters would be inactive
The Character MIB is mandatory for all systems that offer
ports. This includes, for example, terminal servers, general-
time-sharing hosts, and even such systems as a bridge with
(virtual) console port. It may or may not include character
that do not support network sessions, depending on the system'
needs
The Character MIB's central abstraction is a port. Physical
have a one-to-one correspondence with hardware ports. Virtual
are software entities analogous to physical ports, but with
hardware connector
Each port supports one or more sessions. A session represents
virtual connection that carries characters between the port and
Character MIB Working Group [Page 3]
RFC 1316 Character MIB April 1992
partner. Sessions typically operate over a stack of
protocols. A typical session, for example, uses Telnet over TCP
The MIB comprises one base object and two tables, detailed in
following sections. The tables contain objects for ports
sessions
The MIB intentionally contains no distinction between what is
called permanent and operational or volatile data bases. For
purposes of this MIB, handling of such distinctions is
specific
5.
RFC1316-MIB DEFINITIONS ::=
Counter, TimeTicks,
FROM RFC1155-
FROM RFC1213-
OBJECT-
FROM RFC-1212;
-- this is the MIB module for character stream
char OBJECT IDENTIFIER ::= { mib-2 19 }
-- Textual
AutonomousType ::= OBJECT
-- The object identifier is an independently extensible
-- identification value. It may, for example indicate
-- particular sub-tree with further MIB definitions,
-- define something like a protocol type or type
-- hardware
InstancePointer ::= OBJECT
-- The object identifier is a pointer to a specific
-- of a MIB object in this agent's implemented MIB.
-- convention, it is the first object in the conceptual
-- for the instance
Character MIB Working Group [Page 4]
RFC 1316 Character MIB April 1992
-- the generic Character
-- Implementation of this group is mandatory for
-- systems that offer character
charNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of entries in charPortTable,
of their current state."
::= { char 1 }
-- the Character Port
charPortTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A list of port entries. The number of entries
given by the value of charNumber."
::= { char 2 }
charPortEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Status and parameter values for a character port."
INDEX { charPortIndex }
::= { charPortTable 1 }
CharPortEntry ::=
SEQUENCE {
INTEGER
DisplayString
INTEGER
AutonomousType
INTEGER
Character MIB Working Group [Page 5]
RFC 1316 Character MIB April 1992
INTEGER
INTEGER
TimeTicks
INTEGER
INTEGER
INTEGER
INTEGER
Counter
Counter
INTEGER
INTEGER
Gauge
}
charPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"A unique value for each character port. Its
ranges between 1 and the value of charNumber.
convention and if possible, hardware port
come first, with a simple, direct mapping.
value for each port must remain constant at
from one re-initialization of the network
agent to the next."
::= { charPortEntry 1 }
charPortName OBJECT-
SYNTAX DisplayString (SIZE (0..32))
ACCESS read-
STATUS
"An administratively assigned name for the port
typically with some local significance."
Character MIB Working Group [Page 6]
RFC 1316 Character MIB April 1992
::= { charPortEntry 2 }
charPortType OBJECT-
SYNTAX INTEGER { physical(1), virtual(2) }
ACCESS read-
STATUS
"The port's type, 'physical' if the port
an external hardware connector, 'virtual' if it
not."
::= { charPortEntry 3 }
charPortHardware OBJECT-
SYNTAX
ACCESS read-
STATUS
"A reference to hardware MIB definitions specific
a physical port's external connector. For example
if the connector is RS-232, then the value of
object refers to a MIB sub-tree defining
specific to RS-232. If an agent is not
to have such values, the agent returns the
identifier
nullHardware OBJECT IDENTIFIER ::= { 0 0 }
"
::= { charPortEntry 4 }
charPortReset OBJECT-
SYNTAX INTEGER { ready(1), execute(2) }
ACCESS read-
STATUS
"A control to force the port into a clean,
state, both hardware and software, disconnecting
the port's existing sessions. In response to
get-request or get-next-request, the agent
returns 'ready' as the value. Setting the value
'execute' causes a reset."
::= { charPortEntry 5 }
charPortAdminStatus OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2), off(3),
maintenance(4) }
ACCESS read-
STATUS
Character MIB Working Group [Page 7]
RFC 1316 Character MIB April 1992
"The port's desired state, independent of
control. 'enabled' indicates that the port
allowed to pass characters and form new sessions
'disabled' indicates that the port is allowed
pass characters but not form new sessions. 'off
indicates that the port is not allowed to
characters or have any sessions. 'maintenance
indicates a maintenance mode, exclusive of
operation, such as running a test."
::= { charPortEntry 6 }
charPortOperStatus OBJECT-
SYNTAX INTEGER { up(1), down(2),
maintenance(3), absent(4), active(5) }
ACCESS read-
STATUS
"The port's actual, operational state,
of flow control. 'up' indicates able to
normally. 'down' indicates inability to
for administrative or operational reasons
'maintenance' indicates a maintenance mode
exclusive of normal operation, such as running
test. 'absent' indicates that port hardware is
present. 'active' indicates up with a user
(e.g. logged in)."
::= { charPortEntry 7 }
charPortLastChange OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of sysUpTime at the time the port
its current operational state. If the current
was entered prior to the last reinitialization
the local network management subsystem, then
object contains a zero value."
::= { charPortEntry 8 }
charPortInFlowType OBJECT-
SYNTAX INTEGER { none(1), xonXoff(2), hardware(3),
ctsRts(4), dsrDtr(5) }
ACCESS read-
STATUS
"The port's type of input flow control. 'none
indicates no flow control at this level or below
Character MIB Working Group [Page 8]
RFC 1316 Character MIB April 1992
'xonXoff' indicates software flow control
recognizing XON and XOFF characters. 'hardware
indicates flow control delegated to the lower level
for example a parallel port
'ctsRts' and 'dsrDtr' are specific to RS-232-
ports. Although not architecturally pure, they
included here for simplicity's sake."
::= { charPortEntry 9 }
charPortOutFlowType OBJECT-
SYNTAX INTEGER { none(1), xonXoff(2), hardware(3),
ctsRts(4), dsrDtr(5) }
ACCESS read-
STATUS
"The port's type of output flow control. 'none
indicates no flow control at this level or below
'xonXoff' indicates software flow control
recognizing XON and XOFF characters. 'hardware
indicates flow control delegated to the lower level
for example a parallel port
'ctsRts' and 'dsrDtr' are specific to RS-232-
ports. Although not architecturally pure, they
included here for simplicy's sake."
::= { charPortEntry 10 }
charPortInFlowState OBJECT-
SYNTAX INTEGER { none(1), unknown(2), stop(3), go(4) }
ACCESS read-
STATUS
"The current operational state of input flow
on the port. 'none' indicates not applicable
'unknown' indicates this level does not know
'stop' indicates flow not allowed. 'go'
flow allowed."
::= { charPortEntry 11 }
charPortOutFlowState OBJECT-
SYNTAX INTEGER { none(1), unknown(2), stop(3), go(4) }
ACCESS read-
STATUS
"The current operational state of output
control on the port. 'none' indicates
applicable. 'unknown' indicates this level does
Character MIB Working Group [Page 9]
RFC 1316 Character MIB April 1992
know. 'stop' indicates flow not allowed. 'go
indicates flow allowed."
::= { charPortEntry 12 }
charPortInCharacters OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of characters detected as input
the port since system re-initialization and
the port operational state was 'up', 'active',
'maintenance', including, for example, framing,
control (i.e. XON and XOFF), each occurrence of
BREAK condition, locally-processed input, and
sent to all sessions."
::= { charPortEntry 13 }
charPortOutCharacters OBJECT-
SYNTAX
ACCESS read-
STATUS
"Total number of characters detected as output
the port since system re-initialization and
the port operational state was 'up', 'active',
'maintenance', including, for example, framing,
control (i.e. XON and XOFF), each occurrence of
BREAK condition, locally-created output, and
received from all sessions."
::= { charPortEntry 14 }
charPortAdminOrigin OBJECT-
SYNTAX INTEGER { dynamic(1), network(2), local(3),
none(4) }
ACCESS read-
STATUS
"The administratively allowed origin
establishing session on the port. 'dynamic'
'network' or 'local' session establishment. 'none
disallows session establishment."
::= { charPortEntry 15 }
charPortSessionMaximum OBJECT-
SYNTAX
ACCESS read-
STATUS
Character MIB Working Group [Page 10]
RFC 1316 Character MIB April 1992
"The maximum number of concurrent sessions
on the port. A value of -1 indicates no maximum
Setting the maximum to less than the current
of sessions has unspecified results."
::= { charPortEntry 16 }
charPortSessionNumber OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of open sessions on the port that are
the connecting, connected, or disconnecting state."
::= { charPortEntry 17 }
charPortSessionIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of charSessIndex for the port's first
only active session. If the port has no
session, the agent returns the value zero."
::= { charPortEntry 18 }
-- the Character Session
charSessTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A list of port session entries."
::= { char 3 }
charSessEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Status and parameter values for a character
session."
INDEX { charSessPortIndex, charSessIndex }
::= { charSessTable 1 }
Character MIB Working Group [Page 11]
RFC 1316 Character MIB April 1992
CharSessEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
INTEGER
AutonomousType
INTEGER
Counter
Counter
InstancePointer
}
charSessPortIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of charPortIndex for the port to
this session belongs."
::= { charSessEntry 1 }
charSessIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The session index in the context of the port,
non-zero positive integer. Session indexes within
port need not be sequential. Session indexes may
reused for different ports. For example, port 1
port 3 may both have a session 2 at the same time
Session indexes may have any valid integer value
with any meaning convenient to the
implementation."
::= { charSessEntry 2 }
Character MIB Working Group [Page 12]
RFC 1316 Character MIB April 1992
charSessKill OBJECT-
SYNTAX INTEGER { ready(1), execute(2) }
ACCESS read-
STATUS
"A control to terminate the session. In response
a get-request or get-next-request, the agent
returns 'ready' as the value. Setting the value
'execute' causes termination."
::= { charSessEntry 3 }
charSessState OBJECT-
SYNTAX INTEGER { connecting(1), connected(2),
disconnecting(3) }
ACCESS read-
STATUS
"The current operational state of the session
disregarding flow control. 'connected'
that character data could flow on the network
of session. 'connecting' indicates moving
nonexistent toward 'connected'. 'disconnecting
indicates moving from 'connected' or 'connecting'
nonexistent."
::= { charSessEntry 4 }
charSessProtocol OBJECT-
SYNTAX
ACCESS read-
STATUS
"The network protocol over which the session
running. Other OBJECT IDENTIFIER values may
defined elsewhere, in association with
protocols. However, this document assigns those
known interest as of this writing."
::= { charSessEntry 5 }
wellKnownProtocols OBJECT IDENTIFIER ::= { char 4 }
protocolOther OBJECT IDENTIFIER ::= {wellKnownProtocols 1}
protocolTelnet OBJECT IDENTIFIER ::= {wellKnownProtocols 2}
protocolRlogin OBJECT IDENTIFIER ::= {wellKnownProtocols 3}
protocolLat OBJECT IDENTIFIER ::= {wellKnownProtocols 4}
protocolX29 OBJECT IDENTIFIER ::= {wellKnownProtocols 5}
protocolVtp OBJECT IDENTIFIER ::= {wellKnownProtocols 6}
Character MIB Working Group [Page 13]
RFC 1316 Character MIB April 1992
charSessOperOrigin OBJECT-
SYNTAX INTEGER { unknown(1), network(2), local(3) }
ACCESS read-
STATUS
"The session's source of establishment."
::= { charSessEntry 6 }
charSessInCharacters OBJECT-
SYNTAX
ACCESS read-
STATUS
"This session's subset of charPortInCharacters."
::= { charSessEntry 7 }
charSessOutCharacters OBJECT-
SYNTAX
ACCESS read-
STATUS
"This session's subset of charPortOutCharacters."
::= { charSessEntry 8 }
charSessConnectionId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A reference to additional local MIB information
This should be the highest available related MIB
corresponding to charSessProtocol, such as Telnet
For example, the value for a TCP connection (in
absence of a Telnet MIB) is the object identifier
tcpConnState. If an agent is not configured to
such values, the agent returns the
identifier
nullConnectionId OBJECT IDENTIFIER ::= { 0 0 }
"
::= { charSessEntry 9 }
charSessStartTime OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of sysUpTime in MIB-2 when the
Character MIB Working Group [Page 14]
RFC 1316 Character MIB April 1992
entered connecting state."
::= { charSessEntry 10 }
6.
Based on several private MIBs, this document was produced by
Character MIB Working Group
Anne Ambler,
Charles Bazaar,
Christopher Bucci,
Anthony Chung, Hughes LAN
George Conant,
John Cook,
James Davin, MIT-
Shawn Gallagher,
Tom Grant,
Frank Huang,
David Jordan,
Satish Joshi,
Frank Kastenholz,
Ken Key, University of
Jim Kinder,
Rajeev Kochhar, 3
John LoVerso,
Keith McCloghrie, Hughes LAN
Donald Merritt,
David Perkins, 3
Jim Reinstedler, Ungerman-
Marshall Rose,
Ron Strich,
Dean Throop,
Bill Townsend,
Jesse Walker,
David Waitzman,
Bill Westfield,
7.
[1] Cerf, V., "IAB Recommendations for the Development
Internet Network Management Standards", RFC 1052, NRI
April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc
Management Review Group", RFC 1109, NRI, August 1989.
Character MIB Working Group [Page 15]
RFC 1316 Character MIB April 1992
[3] Rose M., and K. McCloghrie, "Structure
Identification of Management Information for TCP/IP-
internets", RFC 1155, Performance Systems International
Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information
for Network Management of TCP/IP-based internets",
1156, Hughes LAN Systems, Performance
International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin
"Simple Network Management Protocol", RFC 1157,
Research, Performance Systems International,
Systems International, MIT Laboratory for Computer Science
May 1990.
[6] McCloghrie K., and M. Rose, Editors, "
Information Base for Network Management of TCP/IP-
internets", RFC 1213, Performance Systems International
March 1991.
[7] Information processing systems - Open
Interconnection - Specification of Abstract Syntax
One (ASN.1), International Organization
Standardization, International Standard 8824,
1987.
[8] Information processing systems - Open
Interconnection - Specification of Basic Encoding Rules
Abstract Notation One (ASN.1), International
for Standardization, International Standard 8825,
1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise
Definitions", RFC 1212, Performance Systems International
Hughes LAN Systems, March 1991.
[10] Rose, M., Editor, "A Convention for Defining Traps
use with the SNMP", RFC 1215, Performance
International, March 1991.
8. Security
Security issues are not discussed in this memo
Character MIB Working Group [Page 16]
RFC 1316 Character MIB April 1992
9. Author's
Bob
Xyplex, Inc
330 Codman Hill
Boxborough, MA 01719
Phone: (508) 264-9900
EMail: rlstewart@eng.xyplex.
Character MIB Working Group [Page 17]
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
