RFC 1283: SNMP over OSI
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1418.
Current document in this lineage: RFC 1418 — SNMP over OSI
In plain English — editorial summary, not part of the RFC
This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard.
Document record
- Document ID
- RFC1283
- Published
- December 1991
- Authors
- M. Rose
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- mgt
- Pages
- 8
- Also known as
- —
- Obsoleted by:
- RFC 1418
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1161 (1990)
- RFC 1283 (1991)
- RFC 1418 (1993) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1284Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
December 1991
- RFC 1398Definitions of Managed Objects for the Ethernet-Like Interface TypesObsoleted
January 1993
- RFC 1658Definitions of Managed Objects for Character Stream Devices using SMIv2Current
July 1994
- RFC 1659Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2Current
July 1994
- RFC 1660Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2Current
July 1994
- RFC 2011SNMPv2 Management Information Base for the Internet Protocol using SMIv2Obsoleted
November 1996
- RFC 2012SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2Obsoleted
November 1996
- RFC 2013SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2Obsoleted
November 1996
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?