RFC 2089: V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2576.
Current document in this lineage: RFC 3584 — Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
In plain English — editorial summary, not part of the RFC
The goal of this memo is to document a common way of mapping an SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2089
- Published
- January 1997
- Authors
- B. Wijnen; D. Levi
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 2576
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?