rfc-5932

Camellia Cipher Suites for TLS

A. Kato, M. Kanda, S. Kanno
date2010-06 streamIETF wgnon working group statusPROPOSED STANDARD pages6 canonicalhttps://www.rfc-editor.org/rfc/rfc5932 doi10.17487/RFC5932
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]

obsoletes

Extracted elements (12)

design-rationale §1

This document amends RFC 4132 by adding SHA-2 family counterparts to the original Camellia cipher suites, which used only SHA-1. The motivation is to modernize the cipher suite portfolio as SHA-2 became the preferred hash family for TLS 1.2.

tls, crypto

interoperability-note §3.1

The RSA, DHE_RSA, DH_RSA, DHE_DSS, DH_DSS, and DH_anon key exchanges are performed exactly as defined in RFC 5246, ensuring compatibility with existing TLS implementations for key exchange procedures.

tls, crypto

normative-requirement §3.3.2 MUST NOT

Clients MUST NOT offer the _SHA256 cipher suites if they do not offer TLS 1.2 or later.

tls, crypto

normative-requirement §3.3.2 MUST NOT

Servers that select an earlier version of TLS MUST NOT select one of the _SHA256 cipher suites.

tls, crypto

normative-requirement §3.3.2 MUST NOT

The SHA-256 cipher suites MUST NOT be negotiated by TLS 1.1 or earlier versions.

tls, crypto

protocol-element §3.3.1

Cipher suites ending with _SHA use HMAC-SHA1 as the MAC algorithm and the PRF as specified in the applicable TLS version (prior to 1.2).

tls, crypto

protocol-element §3.3.2

Cipher suites ending with _SHA256 use HMAC-SHA-256 as the MAC algorithm, and the PRF is the TLS PRF (RFC 5246) with SHA-256 as the hash function, intended for use with TLS 1.2 or later.

tls, crypto

protocol-element §2

RFC 5932 defines 24 Camellia cipher suites for TLS, covering 128-bit and 256-bit key variants with both SHA-1 and SHA-256 MAC algorithms, across RSA, DH_DSS, DH_RSA, DHE_DSS, DHE_RSA, and DH_anon key exchange methods.

tls, crypto

protocol-element §3.2

The CAMELLIA_128_CBC cipher suites use Camellia in CBC mode with a 128-bit key and 128-bit IV; the CAMELLIA_256_CBC cipher suites use a 256-bit key and 128-bit IV.

tls, crypto

registry §4

IANA updated entries for 12 Camellia cipher suite numbers previously allocated in RFC 4132 (0x00,0x41–0x46 and 0x00,0x84–0x89) to reference RFC 5932, and allocated 12 new numbers (0x00,0xBA–0xBF and 0x00,0xC0–0xC5) in the TLS Cipher Suite Registry for the SHA-256 variants.

tls, registry, crypto

security-consideration §5

At the time of writing, no known weak keys exist for Camellia and no security problems have been found, as evaluated by NESSIE, CRYPTREC, and independent cryptanalysis research. Security issues in TLS more broadly are discussed in RFC 5246 Appendices D, E, and F.

tls, crypto, security

wire-format §2

Each cipher suite is identified by a 2-byte TLS CipherSuite value; for example, TLS_RSA_WITH_CAMELLIA_128_CBC_SHA is {0x00, 0x41} and TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 is {0x00, 0xC0}.

tls, crypto