RFC 6367: Addition of the Camellia Cipher Suites to Transport Layer Security (TLS)
In plain English — editorial summary, not part of the RFC
This document specifies forty-two cipher suites for the Transport Security Layer (TLS) protocol to support the Camellia encryption algorithm as a block cipher. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6367
- Published
- September 2011
- Authors
- S. Kanno; M. Kanda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5932Camellia Cipher Suites for TLSUpdated
June 2010
- RFC 5487Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois Counter ModeUpdated
March 2009
- RFC 6358Additional Master Secret Inputs for TLSCurrent
January 2012
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
- RFC 6012Datagram Transport Layer Security (DTLS) Transport Mapping for SyslogUpdated
October 2010
- RFC 6797HTTP Strict Transport Security (HSTS)Current
November 2012
- RFC 5929Channel Bindings for TLSUpdated
July 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?