RFC 6587: Transmission of Syslog Messages over TCP
In plain English — editorial summary, not part of the RFC
There have been many implementations and deployments of legacy syslog over TCP for many years. That protocol has evolved without being standardized and has proven to be quite interoperable in practice. This memo describes how TCP has been used as a transport for syslog messages. This document defines a Historic Document for the Internet community.
Document record
- Document ID
- RFC6587
- Published
- April 2012
- Authors
- R. Gerhards; C. Lonvick
- Status
- HISTORIC
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5848Signed Syslog MessagesCurrent
May 2010
- RFC 5676Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) NotificationsCurrent
October 2009
- RFC 5675Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG MessagesCurrent
October 2009
- RFC 5674Alarms in SyslogCurrent
October 2009
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
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?