A Description of the Camellia Encryption Algorithm
draft-nakajima-camellia-03

[Ballot comment]
This document defines MUST/SHOULD/etc. and references RFC 2119 but as far as
I can tell never uses the terms. If this is indeed the case the definitions
and reference should be removed in the interest of minimizing clutter.

Notified authors that the document could be published with the following note:

  This document is not a product of the IETF and is published only for
  information to the Internet community. The mechanism described in 
  this document has not been evaluated by the IETF with regard to its
  strength, suitability, or security. This document does not represent 
  an Internet standard of any type. At the time of publication of this 
  document, the IETF practice with regard to cryptographic algorithms is
  to standardize only those algorithms that have been evaluated and 
  accepted by bodies qualified to make such a determination, or those
  that are in sufficiently widespread use as to constitute de facto
  standards.

1. Firstly, Camellia is under active consideration in several working
groups in Security Area in IETF.

The TLS WG decided to publish the internet-draft "Addition of the
Camellia Encryption Algorithm to TLS"
as an Informational RFC at the 51st IETF meeting in London last summer
and we are waiting for the last call now.  We have also been waiting
for this I-D "A Description of the Camellia Encryption Algorithm"
to be published as an Informational
RFC (for almost 1 year!), since it will be the best reference of the
Camellia algorithm in the IETF community.

Recently we also submitted a working-group I-D to the S/MIME WG
"Use of the Camellia Encryption Algorithm in CMS"
and Camellia is going to be
included in an updated version of of the I-D "Additional XML Security
URIs" .

2. Secondly, Camellia is under active consideration in other standards
than IETF.

Camellia is under active consideration in the following
standardization bodies and evaluation projects on cryptographic
primitives:

-- ISO/IEC 18033 "Information technology - Security techniques -
  Encryption algorithms"
        http://www.din.de/ni/sc27/
-- NESSIE project: (EC project)
        http://www.cosic.esat.kuleuven.ac.be/nessie/
-- CRYPTREC project (Japan e-Government project)
        http://www.ipa.go.jp/security/enc/CRYPTREC/index-e.html
-- TV-Anytime Forum, Rights Management and Protection 
http://www.tv-anytime.org/
-- OMA (WAP), WAP TLS Profile
http://www.openmobilealliance.org/

3. Thirdly, Camellia is not a "proprietary" encryption algorithm.

Camellia is worldwide royalty-free available: we submitted an IPR
statement to IETF as well as other standardization bodies.  In this
sense, I believe that it is not a "proprietary" encryption algorithm.