RFC 9662: Updates to the Cipher Suites in Secure Syslog
In plain English — editorial summary, not part of the RFC
RFCs 5425 and 6012 describe using TLS and DTLS to securely transport syslog messages. This document updates the cipher suites required by RFC 5245 (TLS Transport Mapping for Syslog) and RFC 6012 (DTLS Transport Mapping for Syslog). It also updates the protocol recommended by RFC 6012 for secure datagram transport.
Document record
- Document ID
- RFC9662
- Published
- October 2024
- Authors
- C. Lonvick; S. Turner; J. Salowey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7525Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Obsoleted
May 2015
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
- RFC 6358Additional Master Secret Inputs for TLSCurrent
January 2012
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 9765RADIUS/1.1: Leveraging Application-Layer Protocol Negotiation (ALPN) to Remove MD5Current
April 2025
- RFC 9850The SSLKEYLOGFILE Format for TLSCurrent
July 2026
- RFC 9851TLS 1.2 is in Feature FreezeCurrent
July 2026
- RFC 9852New Protocols Using TLS Must Require TLS 1.3Current
July 2026
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?