The Syslog Protocol
RFC 5424
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes the syslog protocol, which is used to convey event notification messages. This protocol … Received changes through RFC Editor sync (changed abstract to '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]') |
2015-10-14
|
(System) | Notify list changed from syslog-chairs@ietf.org to (None) |
2009-03-10
|
Cindy Morgan | [Note]: 'RFC 5426; RFC 5424' added by Cindy Morgan |
2009-03-10
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
2009-03-10
|
Cindy Morgan | [Note]: 'RFC 5426' added by Cindy Morgan |
2009-03-10
|
(System) | RFC published |