Debian Codegraph @

rfc5581.html

raw
1 <pre>Network Working Group D. Shaw
2 Request for Comments: 5581 June 2009
3 Updates: <a href="./rfc4880">4880</a>
4 Category: Informational
5
6
7 <span class="h1">The Camellia Cipher in OpenPGP</span>
8
9 Status of This Memo
10
11 This memo provides information for the Internet community. It does
12 not specify an Internet standard of any kind. Distribution of this
13 memo is unlimited.
14
15 Copyright Notice
16
17 Copyright (c) 2009 IETF Trust and the persons identified as the
18 document authors. All rights reserved.
19
20 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
21 Provisions Relating to IETF Documents in effect on the date of
22 publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
23 Please review these documents carefully, as they describe your rights
24 and restrictions with respect to this document.
25
26 Abstract
27
28 This document presents the necessary information to use the Camellia
29 symmetric block cipher in the OpenPGP protocol.
30
31 Table of Contents
32
33 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
34 <a href="#section-2">2</a>. Requirements Notation . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
35 <a href="#section-3">3</a>. Camellia . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
36 <a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
37 <a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
38 <a href="#section-6">6</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Shaw Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5581">RFC 5581</a> The Camellia Cipher in OpenPGP June 2009</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 The OpenPGP protocol [<a href="./rfc4880" title="&quot;OpenPGP Message Format&quot;">RFC4880</a>] can support many different symmetric
60 ciphers. This document presents the necessary information to use the
61 Camellia [<a href="./rfc3713" title="&quot;A Description of the Camellia Encryption Algorithm&quot;">RFC3713</a>] symmetric cipher in the OpenPGP protocol.
62
63 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Notation</span>
64
65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
67 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
68
69 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Camellia</span>
70
71 Camellia is specified in [<a href="./rfc3713" title="&quot;A Description of the Camellia Encryption Algorithm&quot;">RFC3713</a>]. It is a 128-bit symmetric block
72 cipher (as are AES and Twofish in OpenPGP) that supports 128-bit,
73 192-bit, and 256-bit keys. This document defines the use of Camellia
74 in OpenPGP.
75
76 +---------------------+----------------------------------------+
77 | Camellia Key Length | OpenPGP Symmetric-Key Algorithm Number |
78 +---------------------+----------------------------------------+
79 | 128 | 11 |
80 | 192 | 12 |
81 | 256 | 13 |
82 +---------------------+----------------------------------------+
83
84 OpenPGP applications MAY implement Camellia. If implemented,
85 Camellia may be used in any place in OpenPGP where a symmetric cipher
86 is usable, and it is subject to the same usage requirements (such as
87 its presence in the Preferred Symmetric Algorithms signature
88 subpacket) as the other symmetric ciphers in OpenPGP.
89
90 While the OpenPGP algorithm preferences system prevents
91 interoperability problems with public key encrypted messages, if
92 Camellia (or any other optional cipher) is used for encrypting
93 private keys, there could be interoperability problems when migrating
94 a private key from one system to another. A similar issue can arise
95 when using an optional cipher for symmetrically encrypted messages,
96 as this OpenPGP message type does not use the algorithm preferences
97 system. Those using optional ciphers in this manner should take care
98 they are using a cipher that their intended recipient can decrypt.
99
100 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
101
102 At publication time, there are no known weak keys for Camellia, and
103 the Camellia algorithm is believed to be strong. However, as with
104 any technology involving cryptography, implementers should check the
105
106
107
108 <span class="grey">Shaw Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5581">RFC 5581</a> The Camellia Cipher in OpenPGP June 2009</span>
111
112
113 current literature, as well as the Camellia home page at
114 <a href="http://info.isl.ntt.co.jp/camellia/">http://info.isl.ntt.co.jp/camellia/</a> to determine if Camellia has been
115 found to be vulnerable to attack.
116
117 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
118
119 IANA assigned three algorithm numbers from the registry of OpenPGP
120 Symmetric-Key Algorithms that was created by [<a href="./rfc4880" title="&quot;OpenPGP Message Format&quot;">RFC4880</a>].
121
122 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
123
124 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
125 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
126
127 [<a id="ref-RFC3713">RFC3713</a>] Matsui, M., Nakajima, J., and S. Moriai, "A Description of
128 the Camellia Encryption Algorithm", <a href="./rfc3713">RFC 3713</a>, April 2004.
129
130 [<a id="ref-RFC4880">RFC4880</a>] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
131 Thayer, "OpenPGP Message Format", <a href="./rfc4880">RFC 4880</a>, November 2007.
132
133 Author's Address
134
135 David Shaw
136
137 EMail: [email protected]
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 Shaw Informational [Page 3]
165 </pre>