RFC 2263: SNMPv3 Applications
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2273.
Current document in this lineage: RFC 3413 — Simple Network Management Protocol (SNMP) Applications
In plain English — editorial summary, not part of the RFC
This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2263
- Published
- January 1998
- Authors
- D. Levi; P. Meyer; B. Stewart
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 70
- Also known as
- —
- Obsoleted by:
- RFC 2273
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2263 (1998)
- RFC 2273 (1998)
- RFC 2573 (1999)
- RFC 3413 (2002) ✓
Read the full history of Simple Network Management Protocol (SNMP) Applications →
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 2573SNMP ApplicationsObsoleted
April 1999
- RFC 2261An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
- RFC 2257Agent Extensibility (AgentX) Protocol Version 1Obsoleted
January 1998
- RFC 2571An Architecture for Describing SNMP Management FrameworksObsoleted
April 1999
- RFC 2737Entity MIB (Version 2)Obsoleted
December 1999
- RFC 3216SMIng ObjectivesCurrent
December 2001
- RFC 2248Network Services Monitoring MIBObsoleted
January 1998
- 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?