datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Camellia Cipher Suites for TLS
RFC 5932

Document type: RFC - Proposed Standard (June 2010)
Obsoletes RFC 4132
Was draft-kato-tls-rfc4132bis (individual in sec area)
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 5932 (Proposed Standard)
Responsible AD: Tim Polk
Send notices to: akato@po.ntts.co.jp, kanda.masayuki@lab.ntt.co.jp, kanno-s@po.ntts.co.jp, draft-kato-tls-rfc4132bis@tools.ietf.org

Internet Engineering Task Force (IETF)                           A. Kato
Request for Comments: 5932                      NTT Software Corporation
Obsoletes: 4132                                                 M. Kanda
Category: Standards Track                                            NTT
ISSN: 2070-1721                                                 S. Kanno
                                                NTT Software Corporation
                                                               June 2010

                     Camellia Cipher Suites for TLS

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5932.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kato, et al.                 Standards Track                    [Page 1]
RFC 5932             Camellia Cipher Suites for TLS            June 2010

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

1.  Introduction

   This document proposes the addition of new cipher suites to the
   Transport Layer Security (TLS) [RFC5246] protocol to support the
   Camellia [RFC3713] encryption algorithm as a block cipher algorithm,
   adding variants using the SHA-2 family of cryptographic hash
   algorithms [FIPS180-3] to the TLS cipher suite portfolio originally
   specified in RFC 4132 [RFC4132].  This document obsoletes RFC 4132.

   The Camellia algorithm and its properties are described in [RFC3713].

1.1.  Terminology

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

2.  Proposed Cipher Suites

   The cipher suites defined here have the following identifiers:

  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 };
  CipherSuite TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA     = { 0x00,0x45 };
  CipherSuite TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA     = { 0x00,0x46 };

  CipherSuite TLS_RSA_WITH_CAMELLIA_256_CBC_SHA         = { 0x00,0x84 };
  CipherSuite TLS_DH_DSS_WITH_CAMELLIA_256_CBC_SHA      = { 0x00,0x85 };
  CipherSuite TLS_DH_RSA_WITH_CAMELLIA_256_CBC_SHA      = { 0x00,0x86 };
  CipherSuite TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA     = { 0x00,0x87 };
  CipherSuite TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA     = { 0x00,0x88 };

[include full document text]