datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Addition of Camellia Cipher Suites to Transport Layer Security (TLS)
RFC 4132

Document type: RFC - Proposed Standard (July 2005)
Obsoleted by RFC 5932
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4132 (Proposed Standard)
Responsible AD: Russ Housley
Send notices to: <treese@acm.org>, ekr@rtfm.com,shiho@rd.scei.sony.co.jp,akato@po.ntts.co.jp,

Network Working Group                                          S. Moriai
Request for Comments: 4132              Sony Computer Entertainment Inc.
Category: Standards Track                                        A. Kato
                                                NTT Software Corporation
                                                                M. Kanda
                              Nippon Telegraph and Telephone Corporation
                                                               July 2005

  Addition of Camellia Cipher Suites to Transport Layer Security (TLS)

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document proposes the addition of new cipher suites to the
   Transport Layer Security (TLS) protocol to support the Camellia
   encryption algorithm as a bulk cipher algorithm.

1.  Introduction

   This document proposes the addition of new cipher suites to the TLS
   protocol [TLS] to support the Camellia encryption algorithm as a bulk
   cipher algorithm.  This proposal provides a new option for fast and
   efficient bulk cipher algorithms.

   Note: This work was done when the first author worked for NTT.

1.1.  Camellia

   Camellia was selected as a recommended cryptographic primitive by the
   EU NESSIE (New European Schemes for Signatures, Integrity and
   Encryption) project [NESSIE] and included in the list of
   cryptographic techniques for Japanese e-Government systems, which
   were selected by the Japan CRYPTREC (Cryptography Research and
   Evaluation Committees) [CRYPTREC].  Camellia is also included in
   specification of the TV-Anytime Forum [TV-ANYTIME].  The TV-Anytime
   Forum is an association of organizations that seeks to develop

Moriai, et al.              Standards Track                     [Page 1]
RFC 4132             Camellia Cipher Suites for TLS            July 2005

   specifications to enable audio-visual and other services based on
   mass-market high-volume digital storage in consumer platforms.
   Camellia is specified as Cipher Suite in TLS used by Phase 1 S-7
   (Bi-directional Metadata Delivery Protection) specification and S-5
   (TV-Anytime Rights Management and Protection Information for
   Broadcast Applications) specification.  Camellia has been submitted
   to other several standardization bodies such as ISO (ISO/IEC 18033)
   and IETF S/MIME Mail Security Working Group [Camellia-CMS].

   Camellia supports 128-bit block size and 128-, 192-, and 256-bit key
   sizes; i.e., the same interface specifications as the Advanced
   Encryption Standard (AES) [AES].

   Camellia was jointly developed by NTT and Mitsubishi Electric
   Corporation in 2000 [CamelliaTech].  It was carefully designed to
   withstand all known cryptanalytic attacks and even to have a
   sufficiently large security leeway.  It has been scrutinized by
   worldwide cryptographic experts.

   Camellia was also designed to be suitable for both software and
   hardware implementations and to cover all possible encryption
   applications, from low-cost smart cards to high-speed network
   systems.  Compared to the AES, Camellia offers at least comparable
   encryption speed in software and hardware.  In addition, a
   distinguishing feature is its small hardware design.  Camellia
   perfectly meets one of the current TLS market requirements, for which
   low power consumption is mandatory.

   The algorithm specification and object identifiers are described in
   [Camellia-Desc].  The Camellia homepage,
   http://info.isl.ntt.co.jp/camellia/, contains a wealth of information
   about camellia, including detailed specification, security analysis,
   performance figures, reference implementation, and test vectors.

1.2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT",
   "RECOMMENDED", "MAY", and "OPTIONAL" in this document (in uppercase,
   as shown) are to be interpreted as described in [RFC2119].

2.  Proposed Cipher Suites

   The new cipher suites proposed here have the following definitions:

   CipherSuite TLS_RSA_WITH_CAMELLIA_128_CBC_SHA      = { 0x00,0x41 };
   CipherSuite TLS_DH_DSS_WITH_CAMELLIA_128_CBC_SHA   = { 0x00,0x42 };
   CipherSuite TLS_DH_RSA_WITH_CAMELLIA_128_CBC_SHA   = { 0x00,0x43 };
   CipherSuite TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA  = { 0x00,0x44 };

[include full document text]