RFC 5675: Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
In plain English — editorial summary, not part of the RFC
This memo defines a mapping from Simple Network Management Protocol (SNMP) notifications to SYSLOG messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5675
- Published
- October 2009
- Authors
- V. Marinov; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5676Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) NotificationsCurrent
October 2009
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 6765xDSL Multi-Pair Bonding (G.Bond) MIBCurrent
February 2013
- RFC 6766xDSL Multi-Pair Bonding Using Time-Division Inverse Multiplexing (G.Bond/TDIM) MIBCurrent
February 2013
- RFC 6767Ethernet-Based xDSL Multi-Pair Bonding (G.Bond/Ethernet) MIBCurrent
February 2013
- RFC 6768ATM-Based xDSL Bonded Interfaces MIBCurrent
February 2013
- RFC 5607Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) ManagementCurrent
July 2009
- RFC 5592Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)Current
June 2009
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?