RFC 5932: Camellia Cipher Suites for TLS
In plain English — editorial summary, not part of the RFC
This document specifies a set of cipher suites for the Transport Security Layer (TLS) protocol to support the Camellia encryption algorithm as a block cipher. It amends the cipher suites originally specified in RFC 4132 by introducing counterparts using the newer cryptographic hash algorithms from the SHA-2 family. This document obsoletes RFC 4132. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5932
- Published
- June 2010
- Authors
- A. Kato; M. Kanda; S. Kanno
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5529Modes of Operation for Camellia for Use with IPsecCurrent
April 2009
- RFC 5528Camellia Counter Mode and Camellia Counter with CBC-MAC Mode AlgorithmsCurrent
April 2009
- RFC 6367Addition of the Camellia Cipher Suites to Transport Layer Security (TLS)Updated
September 2011
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 8937Randomness Improvements for Security ProtocolsCurrent
October 2020
- RFC 5929Channel Bindings for TLSUpdated
July 2010
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 2010
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?