Internet Draft Integrated Services MIB December 1995
Intgrated Services Management Information Base
draft-ietf-int-serv-mib-00.txt
Tue Nov 21 13:35:16 PST 1995
Fred Baker
Cisco Systems
519 Lado Drive
Santa Barbara, California 93111
fred@cisco.com
John Krawczyk
Bay Networks, Inc
2 Federal Street
Billerica, Massachusetts 01021
jkrawczyk@BayNetworks.com
1. Status of this Memo
This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet
Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted
by other documents at any time. It is not appropriate to use
Internet Drafts as reference material or to cite them other
than as a "working draft" or "work in progress."
Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this
or any other Internet Draft.
Baker and Krawczyk Expires May 1996 [Page 1]
Internet Draft Integrated Services MIB December 1995
2. 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 the the interface attributes defined in the
Integrated Services Model. Comments should be made to the
Integrated Services Working Group, int-serv@isi.edu.
This memo does not, in its draft form, specify a standard for
the Internet community.
Baker and Krawczyk Expires May 1996 [Page 2]
Internet Draft Integrated Services MIB December 1995
3. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1441 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of
management.
o RFC 1213 defines MIB-II, the core set of managed objects
for the Internet suite of protocols.
o RFC 1445 which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 which defines the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
3.1. Object Definitions
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) defined in the SMI. In particular, each object
object type is named by an OBJECT IDENTIFIER, an
administratively assigned name. 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 descriptor, to refer to the
object type.
4. Overview
4.1. Textual Conventions
Several new data types are introduced as a textual convention
in this MIB document. These textual conventions enhance the
readability of the specification and can ease comparison with
other specifications if appropriate. It should be noted that
the introduction of the these textual conventions has no
Baker and Krawczyk Expires May 1996 [Page 3]
Internet Draft Integrated Services MIB December 1995
effect on either the syntax nor the semantics of any managed
objects. The use of these is merely an artifact of the
explanatory method used. Objects defined in terms of one of
these methods are always encoded by means of the rules that
define the primitive type. Hence, no changes to the SMI or
the SNMP are necessary to accommodate these textual
conventions which are adopted merely for the convenience of
readers and writers in pursuit of the elusive goal of clear,
concise, and unambiguous MIB documents.
The new data types are ...
4.2. Structure of MIB
The MIB is composed of the following sections:
Integrated Services
Interface Attributes Table
Interface Flows Table
Notifications
5. Definitions
INTEGRATED-SERVICES-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Gauge32,
Integer32, IpAddress, experimental FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [9].
intSrv MODULE-IDENTITY
LAST-UPDATED "9511211335Z" -- Tue Nov 21 13:35:16 PST 1995
ORGANIZATION "IETF Integrated Services Working Group"
CONTACT-INFO
" Fred Baker
Postal: Cisco Systems
519 Lado Drive
Santa Barbara, California 93111
Tel: +1 805 681 0115
E-Mail: fred@cisco.com
Baker and Krawczyk Expires May 1996 [Page 4]
Internet Draft Integrated Services MIB December 1995
John Krawczyk
Postal: Bay Networks, Inc
2 Federal Street
Billerica, Massachusetts 01021
Tel: +1 508 436 3811
E-Mail: jkrawczyk@BayNetworks.com"
DESCRIPTION
"The MIB module to describe the RSVP and Integrated
Services Protocol"
::= { experimental 9998 } -- he who uses this gets what he deserves
intSrvObjects OBJECT IDENTIFIER ::= { intSrv 1 }
intSrvNotifications OBJECT IDENTIFIER ::= { intSrv 2 }
intSrvConformance OBJECT IDENTIFIER ::= { intSrv 3 }
-- Textual Conventions
--
Protocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the IP Protocol field of an IP Datagram
Header. This identifies the protocol layer above IP.
For example, the value 6 is used for TCP and the value
17 is used for UDP. The values of this field are
defined in the Assigned Numbers RFC.
Zero is used as a flag value indicating 'any protocol
value'."
SYNTAX INTEGER (0..255)
Port ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the UDP or TCP Source or Destination Port
field. This pair, when coupled with the IP Addresses
of the source and destination system and the IP
protocol field, uniquely identifies a data stream.
Zero is used as a fill value when the protocol
indicated by IP Protocol does not have port numbers in
the place that UDP and TCP put them."
SYNTAX INTEGER (0..'FFFF'h)
BitRate ::= TEXTUAL-CONVENTION
Baker and Krawczyk Expires May 1996 [Page 5]
Internet Draft Integrated Services MIB December 1995
STATUS current
DESCRIPTION
"The rate, in KBPS, that data may move in the context.
Applicable contexts minimally include the speed of an
interface or virtual circuit, the data rate of a
(potentially aggregated) data flow, or the data rate to
be allocated for use by a flow."
SYNTAX INTEGER (0..'7FFFFFFF'h)
Baker and Krawczyk Expires May 1996 [Page 6]
Internet Draft Integrated Services MIB December 1995
-- The RSVP Session Statistics Database displays statistics
-- relating to the number of senders and receivers in each
-- session.
intSrvSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF IntSrvSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Statistics concerning the sessions seen by a
given system."
::= { intSrvObjects 1 }
intSrvSessionEntry OBJECT-TYPE
SYNTAX IntSrvSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Statistics concerning a single session seen by
a given system."
INDEX { intSrvSessionAddress, intSrvSessionProtocol, intSrvSessionPort }
::= { intSrvSessionTable 1 }
IntSrvSessionEntry ::=
SEQUENCE {
intSrvSessionAddress IpAddress,
intSrvSessionProtocol Protocol,
intSrvSessionPort Port,
intSrvSessionSenders Gauge32,
intSrvSessionReceivers Gauge32,
intSrvSessionRequests Gauge32
}
intSrvSessionAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP Address used as a destination address
for all senders in this session."
::= { intSrvSessionEntry 1 }
Baker and Krawczyk Expires May 1996 [Page 7]
Internet Draft Integrated Services MIB December 1995
intSrvSessionProtocol OBJECT-TYPE
SYNTAX Protocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP Protocol used by a session."
::= { intSrvSessionEntry 2 }
intSrvSessionPort OBJECT-TYPE
SYNTAX Port
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP or TCP port number used as a destina-
tion port for all senders in this session. A
value of zero indicates that any port is ac-
cepted or an IP Protocol other than UDP or TCP
is in use. The IP protocol in use is specified
by intSrvSessionProtocol."
::= { intSrvSessionEntry 3 }
intSrvSessionSenders OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of senders currently known to be
part of this session."
::= { intSrvSessionEntry 4 }
intSrvSessionReceivers OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of reservations being requested of
this system for this session."
::= { intSrvSessionEntry 5 }
Baker and Krawczyk Expires May 1996 [Page 8]
Internet Draft Integrated Services MIB December 1995
intSrvSessionRequests OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of reservation requestss this sys-
tem is sending upstream for this session."
::= { intSrvSessionEntry 6 }
-- Note that this is a read only table. If the corresponding
-- intSrvSenderTable, intSrvResvTable, and intSrvReqTable entries all
-- are removed, this entry goes away also.
Baker and Krawczyk Expires May 1996 [Page 9]
Internet Draft Integrated Services MIB December 1995
-- The Integrated Services Interface Attributes Database
-- contains information that is shared with other reservation
-- procedures such as ST-II.
intSrvIfAttribTable OBJECT-TYPE
SYNTAX SEQUENCE OF IntSrvIfAttribEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reservable attributes of the system's in-
terfaces."
::= { intSrvObjects 2 }
intSrvIfAttribEntry OBJECT-TYPE
SYNTAX IntSrvIfAttribEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reservable attributes of a given inter-
face."
INDEX { ifIndex }
::= { intSrvIfAttribTable 1 }
IntSrvIfAttribEntry ::=
SEQUENCE {
intSrvIfAttribAllocatedBits BitRate,
intSrvIfAttribMaxAllocatedBits BitRate,
intSrvIfAttribStatus RowStatus
}
intSrvIfAttribAllocatedBits OBJECT-TYPE
SYNTAX BitRate
UNITS "Kilobits per Second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of KBPS currently allocated to
reserved sessions on the interface."
::= { intSrvIfAttribEntry 1 }
Baker and Krawczyk Expires May 1996 [Page 10]
Internet Draft Integrated Services MIB December 1995
intSrvIfAttribMaxAllocatedBits OBJECT-TYPE
SYNTAX BitRate
UNITS "Kilobits per Second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The maximum number of KBPS that may be allo-
cated to reserved sessions on the interface."
::= { intSrvIfAttribEntry 2 }
intSrvIfAttribStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"'valid' on interfaces that are configured for
RSVP."
::= { intSrvIfAttribEntry 3 }
Baker and Krawczyk Expires May 1996 [Page 11]
Internet Draft Integrated Services MIB December 1995
-- The Integrated Services Interface Flows Database
-- lists all flows configured on an interface, including
-- relevant attributes.
intSrvFlowTable OBJECT-TYPE
SYNTAX SEQUENCE OF IntSrvFlowEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the reserved flows us-
ing the system's interfaces."
::= { intSrvObjects 3 }
intSrvFlowEntry OBJECT-TYPE
SYNTAX IntSrvFlowEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the use of a given in-
terface by a given flow."
INDEX { intSrvFlowDestination, intSrvFlowDestinationProtocol,
intSrvFlowDestinationPort,
intSrvFlowSource, intSrvFlowPort, ifIndex }
::= { intSrvFlowTable 1 }
IntSrvFlowEntry ::=
SEQUENCE {
intSrvFlowDestination IpAddress,
intSrvFlowDestinationProtocol Protocol,
intSrvFlowDestinationPort Port,
intSrvFlowSource IpAddress,
intSrvFlowPort Port,
intSrvFlowRate BitRate,
intSrvFlowWeight Integer32,
intSrvFlowQueue Integer32,
intSrvFlowDelay Gauge32
}
Baker and Krawczyk Expires May 1996 [Page 12]
Internet Draft Integrated Services MIB December 1995
intSrvFlowDestination OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP Address used as a destination address
for all senders in this flow."
::= { intSrvFlowEntry 1 }
intSrvFlowDestinationProtocol OBJECT-TYPE
SYNTAX Protocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the IP Protocol field in this
flow, typically UDP or TCP. A value of zero
indicates that any protocol is accepted; it
also implies that intSrvFlowDestinationPort and
intSrvFlowPort must be zero."
::= { intSrvFlowEntry 2 }
intSrvFlowDestinationPort OBJECT-TYPE
SYNTAX Port
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP or TCP port number used as a destina-
tion port for all senders in this flow. A value
of zero indicates that any port is accepted or
an IP Protocol other than UDP or TCP is in use.
The IP protocol in use is specified by
intSrvFlowDestinationProtocol."
::= { intSrvFlowEntry 3 }
Baker and Krawczyk Expires May 1996 [Page 13]
Internet Draft Integrated Services MIB December 1995
intSrvFlowSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP Address used as a source address by
this sender in this flow. If zero, all senders
are included in the class."
::= { intSrvFlowEntry 4 }
intSrvFlowPort OBJECT-TYPE
SYNTAX Port
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP or TCP port number used as a source
port by this sender in this flow. A value of
zero indicates that any port is accepted or an
IP Protocol other than UDP or TCP is in use.
The IP protocol in use is specified by
intSrvFlowDestinationProtocol."
::= { intSrvFlowEntry 5 }
intSrvFlowRate OBJECT-TYPE
SYNTAX BitRate
UNITS "kilobits per second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Average Bit Rate of the sender's data
stream, in Kilobits. The rate may be arbi-
trarily fast during a short interval such as
the duration of a video frame. However, over
any two such intervals it will not average fas-
ter than the average rate as transmitted by the
sender."
::= { intSrvFlowEntry 6 }
Baker and Krawczyk Expires May 1996 [Page 14]
Internet Draft Integrated Services MIB December 1995
intSrvFlowWeight OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The weight used to prioritize the traffic.
Note that the interpretation of this object is
implementation-specific, as implementations
vary in their use of weighting procedures."
::= { intSrvFlowEntry 7 }
intSrvFlowQueue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of the queue used by this traffic.
Note that the interpretation of this object is
implementation-specific, as implementations
vary in their use of queue identifiers."
::= { intSrvFlowEntry 8 }
intSrvFlowDelay OBJECT-TYPE
SYNTAX Gauge32
UNITS "microseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mean delay being experienced by this
flow."
::= { intSrvFlowEntry 9 }
Baker and Krawczyk Expires May 1996 [Page 15]
Internet Draft Integrated Services MIB December 1995
-- No notifications are currently defined
Baker and Krawczyk Expires May 1996 [Page 16]
Internet Draft Integrated Services MIB December 1995
-- conformance information
intSrvGroups OBJECT IDENTIFIER ::= { intSrvConformance 1 }
intSrvCompliances OBJECT IDENTIFIER ::= { intSrvConformance 2 }
-- compliance statements
intSrvCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement "
MODULE -- this module
MANDATORY-GROUPS {
intSrvSessionGroup, intSrvIfAttribGroup, intSrvFlowGroup
}
::= { intSrvCompliances 1 }
intSrvSessionGroup OBJECT-GROUP
OBJECTS {
intSrvSessionAddress, intSrvSessionProtocol,
intSrvSessionPort, intSrvSessionSenders,
intSrvSessionReceivers, intSrvSessionRequests
}
STATUS current
DESCRIPTION
"These objects are required for Systems sup-
porting the Integrated Services Architecture."
::= { intSrvGroups 1 }
intSrvIfAttribGroup OBJECT-GROUP
OBJECTS {
intSrvIfAttribAllocatedBits, intSrvIfAttribMaxAllocatedBits,
intSrvIfAttribStatus
}
STATUS current
DESCRIPTION
"These objects are required for Systems sup-
porting the Integrated Services Architecture."
::= { intSrvGroups 2 }
Baker and Krawczyk Expires May 1996 [Page 17]
Internet Draft Integrated Services MIB December 1995
intSrvFlowGroup OBJECT-GROUP
OBJECTS {
intSrvFlowDestination, intSrvFlowDestinationProtocol,
intSrvFlowDestinationPort, intSrvFlowSource,
intSrvFlowPort, intSrvFlowRate, intSrvFlowWeight,
intSrvFlowQueue, intSrvFlowDelay
}
STATUS current
DESCRIPTION
"These objects are required for Systems sup-
porting the Integrated Services Architecture."
::= { intSrvGroups 3 }
END
Baker and Krawczyk Expires May 1996 [Page 18]
Internet Draft Integrated Services MIB December 1995
6. Acknowledgements
This document was produced by the Integrated Services Working
Group.
Baker and Krawczyk Expires May 1996 [Page 19]
Internet Draft Integrated Services MIB December 1995
7. References
[1] M.T. Rose (editor), Management Information Base for
Network Management of TCP/IP-based internets, Internet
Working Group Request for Comments 1213. Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[2] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), International Organization for
Standardization. International Standard 8824, (December,
1987).
[3] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, (December, 1987).
Baker and Krawczyk Expires May 1996 [Page 20]
Internet Draft Integrated Services MIB December 1995
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 2
3 The SNMPv2 Network Management Framework ............... 3
3.1 Object Definitions .................................. 3
4 Overview .............................................. 3
4.1 Textual Conventions ................................. 3
4.2 Structure of MIB .................................... 4
5 Definitions ........................................... 4
5.1 RSVP Session Statistics Database .................... 6
5.7 Integrated Services Interface Attributes Database
.................................................... 9
5.1 Integrated Services Interface Flows Database ........ 11
5.2 Integrated Services Notifications ................... 15
6 Acknowledgements ...................................... 19
7 References ............................................ 20
Baker and Krawczyk Expires May 1996 [Page 21]
