draft-ietf-openpgp-camellia-02.txt   draft-ietf-openpgp-camellia-03.txt 
Network Working Group D. Shaw Network Working Group D. Shaw
Updates: 4880 (if approved) Updates: 4880 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: October 16, 2008 Expires: October 27, 2008
The Camellia Cipher in OpenPGP The Camellia Cipher in OpenPGP
draft-ietf-openpgp-camellia-02 draft-ietf-openpgp-camellia-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 16, 2008. This Internet-Draft will expire on October 27, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document presents the necessary information to use the Camellia This document presents the necessary information to use the Camellia
symmetric block cipher in the OpenPGP protocol. symmetric block cipher in the OpenPGP protocol.
skipping to change at page 3, line 20 skipping to change at page 3, line 20
2. Requirements notation 2. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Camellia 3. Camellia
Camellia is specified in [RFC3713]. It is a 128-bit block cipher (as Camellia is specified in [RFC3713]. It is a 128-bit block cipher (as
is AES and Twofish in OpenPGP), that supports 128-bit, 192-bit, and are AES and Twofish in OpenPGP), that supports 128-bit, 192-bit, and
256-bit keys. This document defines the use of Camellia in OpenPGP. 256-bit keys. This document defines the use of Camellia in OpenPGP.
+---------------------+----------------------------------------+ +---------------------+----------------------------------------+
| Camellia Key Length | OpenPGP Symmetric-Key Algorithm Number | | Camellia Key Length | OpenPGP Symmetric-Key Algorithm Number |
+---------------------+----------------------------------------+ +---------------------+----------------------------------------+
| 128 | XXXX | | 128 | XXXX |
| 192 | YYYY | | 192 | YYYY |
| 256 | ZZZZ | | 256 | ZZZZ |
+---------------------+----------------------------------------+ +---------------------+----------------------------------------+
skipping to change at page 4, line 16 skipping to change at page 4, line 16
At publication time, there are no known weak keys for Camellia, and At publication time, there are no known weak keys for Camellia, and
the Camellia algorithm is believed to be strong. However, as with the Camellia algorithm is believed to be strong. However, as with
any technology involving cryptography, implementers should check the any technology involving cryptography, implementers should check the
current literature, as well as the Camellia home page at current literature, as well as the Camellia home page at
<http://info.isl.ntt.co.jp/camellia/>, to determine if Camellia has <http://info.isl.ntt.co.jp/camellia/>, to determine if Camellia has
been found to be vulnerable to attack. been found to be vulnerable to attack.
5. IANA Considerations 5. IANA Considerations
This document requires IANA to assign two algorithm numbers from the This document requires IANA to assign three algorithm numbers from
registry of OpenPGP Symmetric-Key Algorithms that was created by the registry of OpenPGP Symmetric-Key Algorithms that was created by
[RFC4880]. [RFC4880].
6. Normative References 6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3713] Matsui, M., Nakajima, J., and S. Moriai, "A Description of [RFC3713] Matsui, M., Nakajima, J., and S. Moriai, "A Description of
the Camellia Encryption Algorithm", RFC 3713, April 2004. the Camellia Encryption Algorithm", RFC 3713, April 2004.
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/