📄 rfc1304.txt
字号:
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
contained in this MIB module. The object types are defined using the
conventions defined in the SMI, as amended by the extensions
specified in RFC 1212 [9].
3. Overview
These objects are used when the particular media being used to
realize an interface is a SIP interface. At present, this applies to
these values of the ifType variable in the Internet-standard MIB:
sip (31)
For these interfaces, the value of the ifSpecific variable in the
MIB-II [6] has the OBJECT IDENTIFIER value:
sip OBJECT IDENTIFIER ::= { transmission 31 }
The definitions contained herein are based on the SIP specifications
in Bellcore TR-TSV-000772 and TR-TSV-000773 [11,12].
The SIP (SMDS Interface Protocol) protocol stack is defined as
follows in TR-TSV-000772 [11]:
___________________
| |
| SIP Level 3 [11] |
|___________________|
| |
| SIP Level 2 [11] |
|___________________|
| |
| PLCP [12] |
|___________________|
| |
| DS1 or DS3 [12] |
|___________________|
The PLCP (Physical Layer Convergence Procedure) adapts the
capabilities of the transmission system (DS1 or DS3 formats) to the
service expected by SIP Level 2. Managed objects for DS1 and DS3
Interface Types are defined in RFC 1232 [13] and RFC 1233 [14]
respectively (and amended in RFC 1239 [17]), and can be utilized for
management of SIP interfaces. This document defines managed objects
for the remaining protocol levels of the SIP Interface Type. This
document does not specify objects for the management of subscription
SNMP Working Group [Page 3]
RFC 1304 SIP Objects February 1992
or configuration of Subscriber-Network Interfaces (SNIs). Those
objects are defined in Definitions of Managed Objects for SMDS
Subscription [18]. Bellcore requirements on these objects are
specified in TA-TSV-001062 [16].
4. Object Definitions
RFC1304-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter, TimeTicks, IpAddress
FROM RFC1155-SMI
transmission
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro
-- as defined in RFC-1212.
-- This is the MIB module for the SIP objects.
sip OBJECT IDENTIFIER ::= { transmission 31 }
-- All representations of SMDS addresses in this MIB
-- module use, as a textual convention (i.e., this
-- convention does not affect their encoding), the
-- data type:
SMDSAddress ::= OCTET STRING (SIZE (8))
-- the 60-bit SMDS address, preceded by 4 bits with the
-- following values:
-- "1100" when representing an individual address
-- "1110" when representing a group address
-- The SIP Level 3 group
-- Implementation of the SIP Level 3 group is mandatory
-- for all systems implementing SIP Level 3.
sipL3Table OBJECT-TYPE
SYNTAX SEQUENCE OF SipL3Entry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains SIP L3 parameters and
state variables, one entry per SIP port."
SNMP Working Group [Page 4]
RFC 1304 SIP Objects February 1992
::= { sip 1 }
sipL3Entry OBJECT-TYPE
SYNTAX SipL3Entry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This list contains SIP L3 parameters and
state variables."
INDEX { sipL3Index }
::= { sipL3Table 1 }
SipL3Entry ::= SEQUENCE {
sipL3Index
INTEGER,
sipL3ReceivedIndividualDAs
Counter,
sipL3ReceivedGAs
Counter,
sipL3UnrecognizedIndividualDAs
Counter,
sipL3UnrecognizedGAs
Counter,
sipL3SentIndividualDAs
Counter,
sipL3SentGAs
Counter,
sipL3Errors
Counter,
sipL3InvalidSMDSAddressTypes
Counter,
sipL3VersionSupport
INTEGER
}
sipL3Index OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object identifies the SIP
port interface for which this entry contains
management information. The value of this
object for a particular interface has the same
value as the ifIndex object, defined in RFC
1156 and RFC 1213, for the same interface."
::= { sipL3Entry 1 }
SNMP Working Group [Page 5]
RFC 1304 SIP Objects February 1992
sipL3ReceivedIndividualDAs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of individually addressed SIP
Level 3 PDUs received from the remote system
across the SNI. The total includes only
unerrored L3PDUs."
::= { sipL3Entry 2 }
sipL3ReceivedGAs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of group addressed SIP Level 3
PDUs received from the remote system across the
SNI. The total includes only unerrored L3PDUs."
::= { sipL3Entry 3 }
sipL3UnrecognizedIndividualDAs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of SIP Level 3 PDUs received from the
remote system with invalid or unknown individual
destination addresses (Destination Address
Screening violations are not included). See SMDS
Subscription MIB module."
::= { sipL3Entry 4 }
sipL3UnrecognizedGAs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of SIP Level 3 PDUs received from the
remote system with invalid or unknown group
addresses. (Destination Address Screening
violations are not included). See SMDS
Subscription MIB module."
::= { sipL3Entry 5 }
sipL3SentIndividualDAs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
SNMP Working Group [Page 6]
RFC 1304 SIP Objects February 1992
STATUS mandatory
DESCRIPTION
"The number of individually addressed SIP Level 3
PDUs that have been sent by this system across the
SNI."
::= { sipL3Entry 6 }
sipL3SentGAs OBJECT-TYPE
SYNTAX Counter
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -