draft-ietf-openpgp-camellia-03.txt   draft-ietf-openpgp-camellia-04.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 27, 2008 Expires: June 8, 2009
The Camellia Cipher in OpenPGP The Camellia Cipher in OpenPGP
draft-ietf-openpgp-camellia-03 draft-ietf-openpgp-camellia-04
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 27, 2008. This Internet-Draft will expire on June 8, 2009.
Copyright Notice
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 3, line 45 skipping to change at page 3, line 45
Camellia may be used in any place in OpenPGP where a symmetric cipher Camellia may be used in any place in OpenPGP where a symmetric cipher
is usable, and is subject to the same usage requirements (such as its is usable, and is subject to the same usage requirements (such as its
presence in the Preferred Symmetric Algorithms signature subpacket) presence in the Preferred Symmetric Algorithms signature subpacket)
as the other symmetric ciphers in OpenPGP. as the other symmetric ciphers in OpenPGP.
While the OpenPGP algorithm preferences system prevents While the OpenPGP algorithm preferences system prevents
interoperability problems with public key encrypted messages, if interoperability problems with public key encrypted messages, if
Camellia (or any other optional cipher) is used for encrypting Camellia (or any other optional cipher) is used for encrypting
private keys, there could be interoperability problems when migrating private keys, there could be interoperability problems when migrating
a private key from one system to another. A similar issue can arise a private key from one system to another. A similar issue can arise
when using an optional cipher for symmetric-only encrypted messages, when using an optional cipher for symmetrically encrypted messages,
as this OpenPGP message type does not perform cipher negotiation. as this OpenPGP message type does not perform cipher negotiation.
Those using optional ciphers in this manner should take care they are Those using optional ciphers in this manner should take care they are
using a cipher that their intended recipient can decrypt. using a cipher that their intended recipient can decrypt.
4. Security Considerations 4. Security Considerations
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
skipping to change at page 5, line 44 skipping to change at line 168
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 5 change blocks. 
8 lines changed or deleted 4 lines changed or added

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