RFC 5424: The Syslog Protocol

This document describes the syslog protocol, which is used to convey event notification messages. This protocol utilizes a layered architecture, which allows…

Read RFC 5424 on the RFC Editor

Outgoing relationships (15 related RFCs)

Obsoletes, Informative reference — RFC 3164: The BSD Syslog Protocol
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 1035: Domain names - implementation and specification
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 1034: Domain names - concepts and facilities
Normative reference — RFC 2578: Structure of Management Information Version 2 (SMIv2)
Normative reference — RFC 4291: IP Version 6 Addressing Architecture
Normative reference — RFC 3339: Date and Time on the Internet: Timestamps
Normative reference — RFC 2914: Congestion Control Principles
Normative reference — RFC 3418: Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
Normative reference — RFC 4646: Tags for Identifying Languages
Normative reference — RFC 5425: Transport Layer Security (TLS) Transport Mapping for Syslog
Normative reference — RFC 5426: Transmission of Syslog Messages over UDP

Incoming relationships (26 related RFCs)

Normatively referenced by — RFC 7285: Application-Layer Traffic Optimization (ALTO) Protocol
Normatively referenced by — RFC 6363: Forward Error Correction (FEC) Framework
Normatively referenced by — RFC 5425: Transport Layer Security (TLS) Transport Mapping for Syslog
Normatively referenced by — RFC 6661: Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation
Normatively referenced by — RFC 6662: Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Normatively referenced by — RFC 7269: NAT64 Deployment Options and Experience
Normatively referenced by — RFC 5848: Signed Syslog Messages
Normatively referenced by — RFC 5427: Textual Conventions for Syslog Management
Normatively referenced by — RFC 5674: Alarms in Syslog
Normatively referenced by — RFC 6587: Transmission of Syslog Messages over TCP
Normatively referenced by — RFC 9742: A YANG Data Model for Syslog Management
Informatively referenced by — RFC 6125: Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Informatively referenced by — RFC 5706: Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions
Informatively referenced by — RFC 5612: Enterprise Number for Documentation Use
Informatively referenced by — RFC 7426: Software-Defined Networking (SDN): Layers and Architecture Terminology
Informatively referenced by — RFC 7297: IP Connectivity Provisioning Profile (CPP)
Informatively referenced by — RFC 7491: A PCE-Based Architecture for Application-Based Network Operations
Informatively referenced by — RFC 5590: Transport Subsystem for the Simple Network Management Protocol (SNMP)
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 6872: The Common Log Format (CLF) for the Session Initiation Protocol (SIP): Framework and Information Model
Informatively referenced by — RFC 6873: Format for the Session Initiation Protocol (SIP) Common Log Format (CLF)
Informatively referenced by — RFC 7574: Peer-to-Peer Streaming Peer Protocol (PPSPP)
Informatively referenced by — RFC 8158: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
Informatively referenced by — RFC 9371: Registration Procedures for Private Enterprise Numbers (PENs)
Informatively referenced by — RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Informatively referenced by — RFC 9003: Extended BGP Administrative Shutdown Communication