Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 3164

Author:

R. Gerhards

Stream:

IETF

Source:

syslog (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5424

Discuss this RFC: Send questions or comments to the mailing listsyslog@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5424

Abstract

This document describes the syslog protocol, which is used to conveyevent notification messages. This protocol utilizes a layeredarchitecture, which allows the use of any number of transportprotocols for transmission of syslog messages. It also provides amessage format that allows vendor-specific extensions to be providedin a structured way.

This document has been written with the original design goals fortraditional syslog in mind. The need for a new layered specificationhas arisen because standardization efforts for reliable and securesyslog extensions suffer from the lack of a Standards-Track andtransport-independent RFC. Without this document, each otherstandard needs to define its own syslog packet format and transportmechanism, which over time will introduce subtle compatibilityissues. This document tries to provide a foundation that syslogextensions can build on. This layered architecture approach alsoprovides a solid basis that allows code to be written once for eachsyslog feature rather than once for each transport. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.