HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 03:22:09 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Thu, 11 Jul 1996 22:20:00 GMT ETag: "2edc91-36dd-31e57e10" Accept-Ranges: bytes Content-Length: 14045 Connection: close Content-Type: text/plain Internet Draft Integrated Services MIB March 1996 Integrated Services Management Information Base draft-ietf-int-serv-mib-02.txt Fri Jun 14 15:30:50 PDT 1996 Fred Baker Cisco Systems 519 Lado Drive Santa Barbara, California 93111 fred@cisco.com John Krawczyk Bay Networks, Inc 2 Federal Street Billerica, Massachusetts 01821 jj@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 September 1996 [Page 1] Internet Draft Integrated Services MIB March 1996 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 September 1996 [Page 2] Internet Draft Integrated Services MIB March 1996 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 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 effect on either the syntax nor the semantics of any managed Baker and Krawczyk Expires September 1996 [Page 3] Internet Draft Integrated Services MIB March 1996 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 5. Definitions INTEGRATED-SERVICES-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Gauge32, Integer32, 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 "9511030500Z" -- Fri Jun 14 15:30:50 PDT 1996 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 John Krawczyk Postal: Bay Networks, Inc Baker and Krawczyk Expires September 1996 [Page 4] Internet Draft Integrated Services MIB March 1996 2 Federal Street Billerica, Massachusetts 01821 Tel: +1 508 436 3811 E-Mail: jj@BayNetworks.com" DESCRIPTION "The MIB module to describe the Integrated Services Protocol" ::= { experimental 72 } intSrvObjects OBJECT IDENTIFIER ::= { intSrv 1 } intSrvNotifications OBJECT IDENTIFIER ::= { intSrv 2 } intSrvConformance OBJECT IDENTIFIER ::= { intSrv 3 } -- Textual Conventions -- BitRate ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The rate, in kilobits/second, that data may move in the context. Applicable contexts minimally include the speed of an interface or virtual circuit, the data rate of a (potential- ly aggregated) data flow, or the data rate to be allocated for use by a flow." SYNTAX INTEGER (0..'7FFFFFFF'h) BurstSize ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The number of octets of IP Data, including IP Headers, that a stream may send without concern for policing." SYNTAX INTEGER (0..'7FFFFFFF'h) Baker and Krawczyk Expires September 1996 [Page 5] Internet Draft Integrated Services MIB March 1996 -- The Integrated Services Interface Attributes Database contains -- information about resources allocated by resource reservation -- protocols, such as RSVP and 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, intSrvIfAttribAllocatedBuffer BurstSize, intSrvIfAttribFlows Gauge32, intSrvIfAttribPropagationDelay Integer32, intSrvIfAttribStatus RowStatus } Baker and Krawczyk Expires September 1996 [Page 6] Internet Draft Integrated Services MIB March 1996 intSrvIfAttribAllocatedBits OBJECT-TYPE SYNTAX BitRate UNITS "Kilobits per Second" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of kilobits/second currently allo- cated to reserved sessions on the interface." ::= { intSrvIfAttribEntry 1 } intSrvIfAttribMaxAllocatedBits OBJECT-TYPE SYNTAX BitRate UNITS "kilobits/second" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of kilobits/second that may be allocated to reserved sessions on the inter- face." ::= { intSrvIfAttribEntry 2 } intSrvIfAttribAllocatedBuffer OBJECT-TYPE SYNTAX BurstSize UNITS "Bits" MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of buffer space required to hold the simultaneous burst of all reserved flows on the interface." ::= { intSrvIfAttribEntry 3 } Baker and Krawczyk Expires September 1996 [Page 7] Internet Draft Integrated Services MIB March 1996 intSrvIfAttribFlows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of reserved flows currently active on this interface. A flow can be created ei- ther from a reservation protocol (such as RSVP or ST-II) or via configuration information." ::= { intSrvIfAttribEntry 4 } intSrvIfAttribPropagationDelay OBJECT-TYPE SYNTAX Integer32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The amount of propagation delay that this in- terface introduces in addition to that which would be expected by dividing the message size in bits by its bit rate. For example, one would expect a typical satellite link to add 272 milliseconds in addition to the bit de- lays." DEFVAL { 0 }-- by default, interfaces are presumed to add no extra delays ::= { intSrvIfAttribEntry 5 } intSrvIfAttribStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "'valid' on interfaces that are configured for RSVP." ::= { intSrvIfAttribEntry 6 } Baker and Krawczyk Expires September 1996 [Page 8] Internet Draft Integrated Services MIB March 1996 -- 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 { intSrvIfAttribGroup } ::= { intSrvCompliances 1 } intSrvIfAttribGroup OBJECT-GROUP OBJECTS { intSrvIfAttribAllocatedBits, intSrvIfAttribMaxAllocatedBits, intSrvIfAttribAllocatedBuffer, intSrvIfAttribFlows, intSrvIfAttribPropagationDelay, intSrvIfAttribStatus } STATUS current DESCRIPTION "These objects are required for Systems sup- porting the Integrated Services Architecture." ::= { intSrvGroups 2 } END Baker and Krawczyk Expires September 1996 [Page 9] Internet Draft Integrated Services MIB March 1996 6. Acknowledgements This document was produced by the Integrated Services Working Group. Baker and Krawczyk Expires September 1996 [Page 10] Internet Draft Integrated Services MIB March 1996 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 September 1996 [Page 11] Internet Draft Integrated Services MIB March 1996 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.2 Interface Attributes Database ....................... 5 6 Acknowledgements ...................................... 10 7 References ............................................ 11 Baker and Krawczyk Expires September 1996 [Page 12]