RFC 5424: The Syslog Protocol
In plain English — editorial summary, not part of the RFC
This document describes the syslog protocol, which is used to convey event notification messages. This protocol utilizes a layered architecture, which allows the use of any number of transport protocols for transmission of syslog messages. It also provides a message format that allows vendor-specific extensions to be provided in a structured way. This document has been written with the original design goals for traditional syslog in mind. The need for a new layered specification has arisen because standardization efforts for reliable and secure syslog extensions suffer from the lack of a Standards-Track and transport-independent RFC. Without this document, each other standard needs to define its own syslog packet format and transport mechanism, which over time will introduce subtle compatibility issues. This document tries to provide a foundation that syslog extensions can build on. This layered architecture approach also provides a solid basis that allows code to be written once for each syslog feature rather than once for each transport. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5424
- Published
- March 2009
- Authors
- R. Gerhards
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 38
- Also known as
- —
- Obsoletes:
- RFC 3164
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5425Transport Layer Security (TLS) Transport Mapping for SyslogUpdated
March 2009
- RFC 9019A Firmware Update Architecture for Internet of ThingsCurrent
April 2021
- RFC 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5036LDP SpecificationUpdated
October 2007
- RFC 3685SIEVE Email Filtering: Spamtest and VirusTest ExtensionsObsoleted
February 2004
- RFC 3215LDP State MachineCurrent
January 2002
- RFC 3214LSP Modification Using CR-LDPCurrent
January 2002
- RFC 3213Applicability Statement for CR-LDPCurrent
January 2002
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?