[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 RFC 5529

Network Working Group                                            A. Kato
Internet-Draft                                  NTT Software Corporation
Intended status: Standards Track                                M. Kanda
Expires: August 30, 2009                  Nippon Telegraph and Telephone
                                                             Corporation
                                                                S. Kanno
                                                NTT Software Corporation
                                                       February 26, 2009


           Modes of Operation for Camellia for Use With IPsec
                   draft-kato-ipsec-camellia-modes-10

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.  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.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on August 30, 2009.

Copyright Notice




Kato, et al.             Expires August 30, 2009                [Page 1]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


   Copyright (c) 2009 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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.











































Kato, et al.             Expires August 30, 2009                [Page 2]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


Abstract

   This document describes the use of the Camellia block cipher
   algorithm in Cipher Block Chaining (CBC) mode, Counter (CTR) mode,
   and Counter with CBC-MAC (CCM) mode, as an IKEv2 and Encapsulating
   Security Payload (ESP) mechanism to provide confidentiality, data
   origin authentication, and connectionless integrity.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  The Camellia Cipher Algorithm  . . . . . . . . . . . . . . . .  5
     2.1.  Block Size and Padding . . . . . . . . . . . . . . . . . .  5
     2.2.  Performance  . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Modes  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  Cipher Block Chaining  . . . . . . . . . . . . . . . . . .  6
     3.2.  Counter and Counter with CBC-MAC . . . . . . . . . . . . .  6
   4.  IKEv2 Conventions  . . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  Keying Material  . . . . . . . . . . . . . . . . . . . . .  7
     4.2.  Transform Type 1 . . . . . . . . . . . . . . . . . . . . .  8
     4.3.  Key Length Attribute . . . . . . . . . . . . . . . . . . .  8
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 11
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     8.1.  Normative  . . . . . . . . . . . . . . . . . . . . . . . . 12
     8.2.  Informative  . . . . . . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14





















Kato, et al.             Expires August 30, 2009                [Page 3]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


1.  Introduction

   This document describes the use of the Camellia block cipher
   algorithm in Cipher Block Chaining (CBC) mode, Counter (CTR) mode,
   and Counter with CBC-MAC (CCM) mode, as an IKEv2 [1] and
   Encapsulating Security Payload (ESP) [2] mechanism to provide
   confidentiality, data origin authentication, and connectionless
   integrity.

   Since optimized source code is provided under several open source
   licenses [9], Camellia is also adopted by several open source
   projects (OpenSSL, FreeBSD, Linux, and Firefox Gran Paradiso).

   The algorithm specification and object identifiers are described in
   [3].

   The Camellia web site [10] contains a wealth of information about
   Camellia, including detailed specification, security analysis,
   performance figures, reference implementation, optimized
   implementation, test vectors, and intellectual property information.

   The remainder of this document specifies use of various modes of
   operation for Camellia within the context of IPsec ESP.  For further
   information on how the various pieces of IPsec in general and ESP in
   particular fit together to provide security services, please refer to
   [11] and [2].

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 [4].



















Kato, et al.             Expires August 30, 2009                [Page 4]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


2.  The Camellia Cipher Algorithm

   All symmetric block cipher algorithms share common characteristics
   and variables, including mode, key size, weak keys, block size, and
   rounds.  The relevant characteristics of Camellia describes in [3].

2.1.  Block Size and Padding

   Camellia uses a block size of 16 octets (128 bits).

   Padding requirements are described:

   a) Camellia Padding requirement is specified in [2],
   b) Camellia-CBC Padding requirement is specified in [2],
   c) Camellia-CCM Padding requirement is specified in [5],
   d) ESP Padding requirement is specified in [2].

2.2.  Performance

   Performance figures for Camellia are available at [10].  The NESSIE
   project has reported on the performance of optimized implementations
   independently [12].





























Kato, et al.             Expires August 30, 2009                [Page 5]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


3.  Modes

   This document describes three modes of operation(CBC (Cipher Block
   Chaining), CTR (Counter), CCM (Counter with CBC MAC)) for Camellia on
   IPsec.

3.1.  Cipher Block Chaining

   Camellia CBC mode is defined in [6].

3.2.  Counter and Counter with CBC-MAC

   Camellia in CTR and CCM modes is used in IPsec as AES in [7] and [8].
   In this specification, CCM is used with the Camellia [13] block
   cipher.




































Kato, et al.             Expires August 30, 2009                [Page 6]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


4.  IKEv2 Conventions

   This section describes the transform ID and conventions used to
   generate keying material for use with ENCR_CAMELLIA_CBC,
   ENCR_CAMELLIA_CTR and ENCR_CAMELLIA_CCM using the Internet Key
   Exchange (IKEv2) [1].

4.1.  Keying Material

   The size of KEYMAT MUST be equal or longer than the associated
   Camellia key.  The keying material is used as follows:

   Camellia-CBC with a 128-bit key
      The KEYMAT requested for each Camellia-CBC key is 16 octets.  The
      whole octets are the 128-bit Camellia key.

   Camellia-CBC with a 192-bit key
      The KEYMAT requested for each Camellia-CBC key is 24 octets.  The
      whole octets are the 192-bit Camellia key.

   Camellia-CBC with a 256-bit key
      The KEYMAT requested for each Camellia-CBC key is 32 octets.  The
      whole octets are the 256-bit Camellia key.

   Camellia-CTR with a 128-bit key
      The KEYMAT requested for each Camellia-CTR key is 20 octets.  The
      first 16 octets are the 128-bit Camellia key, and the remaining
      four octets are used as the nonce value in the counter block.

   Camellia-CTR with a 192-bit key
      The KEYMAT requested for each Camellia-CTR key is 28 octets.  The
      first 24 octets are the 192-bit Camellia key, and the remaining
      four octets are used as the nonce value in the counter block.

   Camellia-CTR with a 256-bit key
      The KEYMAT requested for each Camellia-CTR key is 36 octets.  The
      first 32 octets are the 256-bit Camellia key, and the remaining
      four octets are used as the nonce value in the counter block.

   Camellia-CCM with a 128-bit key
      The KEYMAT requested for each Camellia-CCM key is 19 octets.  The
      first 16 octets are the 128-bit Camellia key, and the remaining
      three octets are used as the salt value in the counter block.

   Camellia-CCM with a 192-bit key
      The KEYMAT requested for each Camellia-CCM key is 27 octets.  The
      first 24 octets are the 192-bit Camellia key, and the remaining
      three octets are used as the salt value in the counter block.



Kato, et al.             Expires August 30, 2009                [Page 7]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


   Camellia-CCM with a 256-bit key
      The KEYMAT requested for each Camellia-CCM key is 35 octets.  The
      first 32 octets are the 256-bit Camellia key, and the remaining
      three octets are used as the salt value in the counter block.

4.2.  Transform Type 1

   For IKEv2 negotiations, IANA has assigned five ESP Transform
   Identifiers for Camellia-CBC, Camellia-CTR and Camellia-CCM:

         <TBD1> for Camellia-CBC with explicit IV;
         <TBD2> for Camellia-CTR with explicit IV;
         <TBD3> for Camellia-CCM with an 8-octet ICV;
         <TBD4> for Camellia-CCM with a 12-octet ICV; and
         <TBD5> for Camellia-CCM with a 16-octet ICV.

4.3.  Key Length Attribute

   Since Camellia supports three key lengths, the Key Length attribute
   MUST be specified in the IKE exchange [1].  The Key Length attribute
   MUST have a value of 128, 192, or 256 bits.






























Kato, et al.             Expires August 30, 2009                [Page 8]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


5.  Security Considerations

   About security considerations of CTR and CCM mode, this document
   refers to Section 9. of [7] and Section 7. of [8].

   No security problem has been found for Camellia [14], [12].













































Kato, et al.             Expires August 30, 2009                [Page 9]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


6.  IANA Considerations

   IANA has assigned IKEv2 parameters for use with Camellia-CTR, and
   Camellia-CCM for Transform Type 1 (Encryption Algorithm):

         <TBD1> for ENCR_CAMELLIA_CBC;
         <TBD2> for ENCR_CAMELLIA_CTR;
         <TBD3> for ENCR_CAMELLIA_CCM with an 8-octet ICV;
         <TBD4> for ENCR_CAMELLIA_CCM with a 12-octet ICV; and
         <TBD5> for ENCR_CAMELLIA_CCM with a 16-octet ICV.









































Kato, et al.             Expires August 30, 2009               [Page 10]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


7.  Acknowledgments

   We thank Tim Polk and Tero Kivinen for their initial review of this
   document.  Thanks to Derek Atkins, Rui Hodai for their comments and
   suggestions.  Special thanks to Alfred Hoenes for several very
   detailed reviews and suggestions.













































Kato, et al.             Expires August 30, 2009               [Page 11]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


8.  References

8.1.  Normative

   [1]   Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
         RFC 4306, December 2005.

   [2]   Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303,
         December 2005.

   [3]   Matsui, M., Nakajima, J., and S. Moriai, "A Description of the
         Camellia Encryption Algorithm", RFC 3713, April 2004.

   [4]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", BCP 14, RFC 2119, March 1997.

   [5]   Dworkin, M., "Recommendation for Block Cipher Modes of
         Operation: the CCM Mode for Authentication and
         Confidentiality", NIST Special Publication 800-38C, July 2007,
         <http://csrc.nist.gov/publications/nistpubs/800-38C/
         SP800-38C_updated-July20_2007.pdf>.

   [6]   Kato, A., Moriai, S., and M. Kanda, "The Camellia Cipher
         Algorithm and Its Use With IPsec", RFC 4312, December 2005.

   [7]   Housley, R., "Using Advanced Encryption Standard (AES) CCM Mode
         with IPsec Encapsulating Security Payload (ESP)", RFC 4309,
         December 2005.

   [8]   Housley, R., "Using Advanced Encryption Standard (AES) Counter
         Mode With IPsec Encapsulating Security Payload (ESP)",
         RFC 3686, January 2004.

8.2.  Informative

   [9]   "Camellia open source software",
         <http://info.isl.ntt.co.jp/crypt/eng/camellia/source.html>.

   [10]  "Camellia web site", <http://info.isl.ntt.co.jp/camellia/>.

   [11]  Kent, S. and K. Seo, "Security Architecture for the Internet
         Protocol", RFC 4301, December 2005.

   [12]  "The NESSIE project (New European Schemes for Signatures,
         Integrity and Encryption)",
         <http://www.cosic.esat.kuleuven.ac.be/nessie/>.

   [13]  Kato, A., Kanda, M., and S. Kanno, "Camellia Counter mode and



Kato, et al.             Expires August 30, 2009               [Page 12]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


         Camellia Counter with CBC Mac mode algorithms",
         draft-kato-camellia-ctrccm-05 (work in progress),
         February 2009.

   [14]  Information-technology Promotion Agency (IPA), "Cryptography
         Research and Evaluation Committees",
         <http://www.ipa.go.jp/security/enc/CRYPTREC/index-e.html>.












































Kato, et al.             Expires August 30, 2009               [Page 13]

Internet-Draft  Modes of Operation for Camellia for IPsec  February 2009


Authors' Addresses

   Akihiro Kato
   NTT Software Corporation

   Phone: +81-45-212-7577
   Fax:   +81-45-212-9800
   Email: akato@po.ntts.co.jp


   Masayuki Kanda
   Nippon Telegraph and Telephone Corporation

   Phone: +81-422-59-3456
   Fax:   +81-422-59-4015
   Email: kanda.masayuki@lab.ntt.co.jp


   Satoru Kanno
   NTT Software Corporation

   Phone: +81-45-212-7577
   Fax:   +81-45-212-9800
   Email: kanno-s@po.ntts.co.jp



























Kato, et al.             Expires August 30, 2009               [Page 14]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/