Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework
RFC 1452
Document | Type |
RFC - Proposed Standard
(April 1993; No errata)
Obsoleted by RFC 1908
|
|
---|---|---|---|
Authors | Jeff Case , Keith McCloghrie , Marshall Rose , Steven Waldbusser | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 1452 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group J. Case Request for Comments: 1452 SNMP Research, Inc. K. McCloghrie Hughes LAN Systems M. Rose Dover Beach Consulting, Inc. S. Waldbusser Carnegie Mellon University April 1993 Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework Status of this Memo This RFC specifes 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. Table of Contents 1 Introduction .......................................... 2 2 Management Information ................................ 3 2.1 Object Definitions .................................. 3 2.2 Trap Definitions .................................... 6 2.3 Compliance Statements ............................... 7 2.4 Capabilities Statements ............................. 7 3 Protocol Operations ................................... 8 3.1 Proxy Agent Behavior ................................ 8 3.1.1 SNMPv2 -> SNMPv1 .................................. 8 3.1.2 SNMPv1 -> SNMPv2 .................................. 8 3.2 Bi-lingual Manager Behavior ......................... 10 4 Acknowledgements ...................................... 11 5 References ............................................ 15 6 Security Considerations ............................... 17 7 Authors' Addresses .................................... 17 Case, McCloghrie, Rose & Waldbusser [Page 1] RFC 1452 Coexistence between SNMPv1 and SNMPv2 April 1993 1. Introduction The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1), which consists of these three documents: RFC 1155 [2] which defines the Structure of Management Information (SMI), the mechanisms used for describing and naming objects for the purpose of management. RFC 1212 [3] which defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1157 [4] which defines the Simple Network Management Protocol (SNMP), the protocol used for network access to managed objects. Case, McCloghrie, Rose & Waldbusser [Page 2] RFC 1452 Coexistence between SNMPv1 and SNMPv2 April 1993 2. Management Information The SNMPv2 approach towards describing collections of managed objects is nearly a proper superset of the approach defined in the Internet-standard Network Management Framework. For example, both approaches use ASN.1 [5] as the basis for a formal descriptive notation. Indeed, one might note that the SNMPv2 approach largely codifies the existing practice for defining MIB modules, based on extensive experience with the current framework. The SNMPv2 documents which deal with information modules are: Structure of Management Information for SNMPv2 [6], which defines concise notations for describing information modules, managed objects and notifications; Textual Conventions for SNMPv2 [7], which defines a concise notation for describing textual conventions, and also defines some initial conventions; and, Conformance Statements for SNMPv2 [8], which defines concise notation for describing compliance and capabilities statements. The following sections consider the three areas: MIB modules, compliance statements, and capabilities statements. MIB modules defined using the current framework may continue to be used with the SNMPv2 protocol. However, for the MIBShow full document text