RIP Version 2 MIB Extension
RFC 1724
Document | Type |
RFC - Draft Standard
(November 1994; Errata)
Obsoletes RFC 1389
|
|
---|---|---|---|
Authors | Fred Baker , Gary Malkin | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 1724 (Draft Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group G. Malkin Request for Comments: 1724 Xylogics, Inc. Obsoletes: 1389 F. Baker Category: Standards Track Cisco Systems November 1994 RIP Version 2 MIB Extension Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) 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 RIP Version 2. Acknowledgements The authors would like to thank the IETF ripv2 Working Group for their help in improving the RIP-2 MIB extension. Table of Contents 1. The Network Management Framework ...................... 2 2. Objects ............................................... 2 2.1 Format of Definitions ................................ 3 3. Overview .............................................. 3 3.1 Textual Conventions .................................. 3 3.2 Structure of MIB ..................................... 3 3.3 Modifications from RFC 1389 .......................... 3 4. Definitions ........................................... 5 4.1 Global Counters ...................................... 6 4.2 RIP Interface Tables ................................. 6 4.3 Peer Table ........................................... 12 5. References ............................................ 17 6. Security Considerations ............................... 18 7. Authors' Addresses .................................... 18 Malkin & Baker [Page 1] RFC 1724 RIP-2 MIB Extension November 1994 1. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: STD 16/RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16/RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 which defines MIB-I, the core set of managed objects for the Internet suite of protocols. STD 17/RFC 1213 defines MIB- II, an evolution of MIB-I based on implementation experience and new operational requirements. STD 15/RFC 1157 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) [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 [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 [8], subject to the additional requirements imposed by the SNMP. Malkin & Baker [Page 2] RFC 1724 RIP-2 MIB Extension November 1994 2.1 Format of Definitions Section 4 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 [9]. 3. Overview 3.1 Textual Conventions Several new data types are introduced as a textual convention in thisShow full document text