RFC 1224: Techniques for managing asynchronously generated alerts
In plain English — editorial summary, not part of the RFC
This memo defines common mechanisms for managing asynchronously produced alerts in a manner consistent with current network management protocols. This memo specifies an Experimental Protocol for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1224
- Published
- May 1991
- Authors
- L. Steinberg
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- mgt
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1229Extensions to the generic-interface MIBObsoleted
May 1991
- RFC 1230IEEE 802.4 Token Bus MIBUpdated
May 1991
- RFC 1231IEEE 802.5 Token Ring MIBObsoleted
May 1991
- RFC 1232Definitions of managed objects for the DS1 Interface typeObsoleted
May 1991
- RFC 1215Convention for defining traps for use with the SNMPCurrent
March 1991
- RFC 1233Definitions of managed objects for the DS3 Interface typeObsoleted
May 1991
- RFC 1214OSI internet management: Management Information BaseCurrent
April 1991
- RFC 1213Management Information Base for Network Management of TCP/IP-based internets: MIB-IIUpdated
March 1991
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?