Debian Codegraph @

rfc6379.html

raw
1 <pre>Internet Engineering Task Force (IETF) L. Law
2 Request for Comments: 6379 J. Solinas
3 Obsoletes: <a href="./rfc4869">4869</a> NSA
4 Category: Informational October 2011
5 ISSN: 2070-1721
6
7
8 <span class="h1">Suite B Cryptographic Suites for IPsec</span>
9
10 Abstract
11
12 This document proposes four cryptographic user interface suites
13 ("UI suites") for IP Security (IPsec), similar to the two suites
14 specified in <a href="./rfc4308">RFC 4308</a>. The four new suites provide compatibility
15 with the United States National Security Agency's Suite B
16 specifications. This document obsoletes <a href="./rfc4869">RFC 4869</a>, which presented
17 earlier versions of these suites.
18
19 Status of This Memo
20
21 This document is not an Internet Standards Track specification; it is
22 published for informational purposes.
23
24 This document is a product of the Internet Engineering Task Force
25 (IETF). It represents the consensus of the IETF community. It has
26 received public review and has been approved for publication by the
27 Internet Engineering Steering Group (IESG). Not all documents
28 approved by the IESG are a candidate for any level of Internet
29 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
30
31 Information about the current status of this document, any errata,
32 and how to provide feedback on it may be obtained at
33 <a href="http://www.rfc-editor.org/info/rfc6379">http://www.rfc-editor.org/info/rfc6379</a>.
34
35 Copyright Notice
36
37 Copyright (c) 2011 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
39
40 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
49
50
51
52 <span class="grey">Law &amp; Solinas Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
60 <a href="#section-2">2</a>. Requirements Terminology ........................................<a href="#page-2">2</a>
61 <a href="#section-3">3</a>. New UI Suites ...................................................<a href="#page-2">2</a>
62 <a href="#section-3.1">3.1</a>. Suite "Suite-B-GCM-128" ....................................<a href="#page-3">3</a>
63 <a href="#section-3.2">3.2</a>. Suite "Suite-B-GCM-256" ....................................<a href="#page-3">3</a>
64 <a href="#section-3.3">3.3</a>. Suite "Suite-B-GMAC-128" ...................................<a href="#page-4">4</a>
65 <a href="#section-3.4">3.4</a>. Suite "Suite-B-GMAC-256" ...................................<a href="#page-4">4</a>
66 <a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-4">4</a>
67 <a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
68 <a href="#section-6">6</a>. Changes from <a href="./rfc4869">RFC 4869</a> ...........................................<a href="#page-5">5</a>
69 <a href="#section-7">7</a>. References ......................................................<a href="#page-5">5</a>
70 <a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-5">5</a>
71 <a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-6">6</a>
72
73 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
74
75 [<a id="ref-RFC4308">RFC4308</a>] proposes two optional cryptographic user interface suites
76 ("UI suites") for IPsec. The two suites, VPN-A and VPN-B, represent
77 commonly used present day corporate VPN security choices and
78 anticipated future choices, respectively. [<a href="./rfc4869" title="&quot;Suite B Cryptographic Suites for IPsec&quot;">RFC4869</a>] proposed four
79 new UI suites based on implementations of the United States National
80 Security Agency's Suite B algorithms (see [<a href="#ref-SuiteB" title="&quot;NSA Suite B Cryptography&quot;">SuiteB</a>]).
81
82 As with the VPN suites, the Suite B suites are simply collections of
83 values for some options in IPsec. Use of UI suites does not change
84 the IPsec protocols in any way.
85
86 This document reduces the scope of the suites in [<a href="./rfc4869" title="&quot;Suite B Cryptographic Suites for IPsec&quot;">RFC4869</a>] while
87 retaining the original suite names. A detailed list of the changes
88 is given in <a href="#section-6">Section 6</a>. This document obsoletes <a href="./rfc4869">RFC 4869</a>.
89
90 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Terminology</span>
91
92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
94 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>].
95
96 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. New UI Suites</span>
97
98 Each of the following UI suites provides choices for ESP (see
99 [<a href="./rfc4303" title="&quot;IP Encapsulating Security Payload (ESP)&quot;">RFC4303</a>]) and for Internet Key Exchange (IKEv2) (see [<a href="./rfc5996" title="&quot;Internet Key Exchange Protocol Version 2 (IKEv2)&quot;">RFC5996</a>]).
100 The four suites are differentiated by the choice of cryptographic
101 algorithm strengths, and a choice of whether the Encapsulating
102 Security Payload (ESP) is to provide both confidentiality and
103 integrity or integrity only. The suite names are based on the
104
105
106
107
108 <span class="grey">Law &amp; Solinas Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
111
112
113 Advanced Encryption Standard [<a href="#ref-AES" title="&quot;Advanced Encryption Standard (AES)&quot;">AES</a>] mode and AES key length specified
114 for ESP.
115
116 IPsec implementations that use these UI suites MUST use the suite
117 names listed here. IPsec implementations SHOULD NOT use names
118 different than those listed here for the suites that are described,
119 and MUST NOT use the names listed here for suites that do not match
120 these values. These requirements are necessary for interoperability.
121
122 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Suite "Suite-B-GCM-128"</span>
123
124 This suite provides ESP integrity protection and confidentiality
125 using 128-bit AES-GCM (see [<a href="./rfc4106" title="&quot;The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)&quot;">RFC4106</a>]). This suite or the following
126 suite should be used when ESP integrity protection and encryption are
127 both needed.
128
129 ESP:
130 Encryption AES with 128-bit keys and 16-octet Integrity
131 Check Value (ICV) in GCM mode [<a href="./rfc4106" title="&quot;The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)&quot;">RFC4106</a>]
132 Integrity NULL
133
134 IKEv2:
135 Encryption AES with 128-bit keys in CBC mode
136 [<a href="./rfc3602" title="&quot;The AES-CBC Cipher Algorithm and Its Use with IPsec&quot;">RFC3602</a>]
137 Pseudo-random function HMAC-SHA-256 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
138 Integrity HMAC-SHA-256-128 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
139 Diffie-Hellman group 256-bit random ECP group [<a href="./rfc5903" title="&quot;Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2&quot;">RFC5903</a>]
140
141 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Suite "Suite-B-GCM-256"</span>
142
143 This suite provides ESP integrity protection and confidentiality
144 using 256-bit AES-GCM (see [<a href="./rfc4106" title="&quot;The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)&quot;">RFC4106</a>]). This suite or the preceding
145 suite should be used when ESP integrity protection and encryption are
146 both needed.
147
148 ESP:
149 Encryption AES with 256-bit keys and 16-octet ICV in GCM mode
150 [<a href="./rfc4106" title="&quot;The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)&quot;">RFC4106</a>]
151 Integrity NULL
152
153 IKEv2:
154 Encryption AES with 256-bit keys in CBC mode
155 [<a href="./rfc3602" title="&quot;The AES-CBC Cipher Algorithm and Its Use with IPsec&quot;">RFC3602</a>]
156 Pseudo-random function HMAC-SHA-384 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
157 Integrity HMAC-SHA-384-192 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
158 Diffie-Hellman group 384-bit random ECP group [<a href="./rfc5903" title="&quot;Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2&quot;">RFC5903</a>]
159
160
161
162
163
164 <span class="grey">Law &amp; Solinas Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
167
168
169 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Suite "Suite-B-GMAC-128"</span>
170
171 This suite provides ESP integrity protection using 128-bit AES-GMAC
172 (see [<a href="./rfc4543" title="&quot;The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH&quot;">RFC4543</a>]) but does not provide confidentiality. This suite or
173 the following suite should be used only when there is no need for ESP
174 encryption.
175
176 ESP:
177 Encryption NULL
178 Integrity AES with 128-bit keys in GMAC mode [<a href="./rfc4543" title="&quot;The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH&quot;">RFC4543</a>]
179
180 IKEv2:
181 Encryption AES with 128-bit keys in CBC mode
182 [<a href="./rfc3602" title="&quot;The AES-CBC Cipher Algorithm and Its Use with IPsec&quot;">RFC3602</a>]
183 Pseudo-random function HMAC-SHA-256 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
184 Integrity HMAC-SHA-256-128 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
185 Diffie-Hellman group 256-bit random ECP group [<a href="./rfc5903" title="&quot;Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2&quot;">RFC5903</a>]
186
187 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Suite "Suite-B-GMAC-256"</span>
188
189 This suite provides ESP integrity protection using 256-bit AES-GMAC
190 (see [<a href="./rfc4543" title="&quot;The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH&quot;">RFC4543</a>]) but does not provide confidentiality. This suite or
191 the preceding suite should be used only when there is no need for ESP
192 encryption.
193
194 ESP:
195 Encryption NULL
196 Integrity AES with 256-bit keys in GMAC mode [<a href="./rfc4543" title="&quot;The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH&quot;">RFC4543</a>]
197
198 IKEv2:
199 Encryption AES with 256-bit keys in CBC mode
200 [<a href="./rfc3602" title="&quot;The AES-CBC Cipher Algorithm and Its Use with IPsec&quot;">RFC3602</a>]
201 Pseudo-random function HMAC-SHA-384 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
202 Integrity HMAC-SHA-384-192 [<a href="./rfc4868" title="&quot;Using HMAC-SHA-256, HMAC- SHA-384, and HMAC-SHA-512 with IPsec&quot;">RFC4868</a>]
203 Diffie-Hellman group 384-bit random ECP group [<a href="./rfc5903" title="&quot;Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2&quot;">RFC5903</a>]
204
205 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
206
207 This document inherits all of the security considerations of the
208 IPsec and IKEv2 documents.
209
210 Some of the security options specified in these suites may be found
211 in the future to have properties significantly weaker than those that
212 were believed at the time this document was produced.
213
214
215
216
217
218
219
220 <span class="grey">Law &amp; Solinas Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
223
224
225 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
226
227 IANA maintains a registry called "Cryptographic Suites for IKEv1,
228 IKEv2, and IPsec" (see [<a href="#ref-IANA-Suites" title="&quot;Cryptographic Suites for IKEv1, IKEv2, and IPsec&quot;">IANA-Suites</a>]). The registry consists of a
229 text string and an RFC number that lists the associated transforms.
230 The four suites in this document have been listed with this document
231 as the RFC reference. These entries will be updated upon approval of
232 this document.
233
234 The updated values for the registry are:
235
236 Identifier Defined in
237 Suite-B-GCM-128 <a href="./rfc6379">RFC 6379</a>
238 Suite-B-GCM-256 <a href="./rfc6379">RFC 6379</a>
239 Suite-B-GMAC-128 <a href="./rfc6379">RFC 6379</a>
240 Suite-B-GMAC-256 <a href="./rfc6379">RFC 6379</a>
241
242 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Changes from <a href="./rfc4869">RFC 4869</a></span>
243
244 The changes from [<a href="./rfc4869" title="&quot;Suite B Cryptographic Suites for IPsec&quot;">RFC4869</a>] are:
245
246 1. Removed definitions of the suites for IKEv1.
247
248 2. Removed IKE authentication methods from the suite definitions.
249 These now appear in [<a href="./rfc6380" title="&quot;Suite B Profile for Internet Protocol Security (IPsec)&quot;">RFC6380</a>].
250
251 3. Removed the requirements on rekeying in IKEv2.
252
253 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
254
255 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
256
257 [<a id="ref-IANA-Suites">IANA-Suites</a>] Internet Assigned Numbers Authority, "Cryptographic
258 Suites for IKEv1, IKEv2, and IPsec",
259 &lt;<a href="http://www.iana.org/assignments/crypto-suites">http://www.iana.org/assignments/crypto-suites</a>&gt;.
260
261 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
262 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
263
264 [<a id="ref-RFC3602">RFC3602</a>] Frankel, S., Glenn, R., and S. Kelly, "The AES-CBC
265 Cipher Algorithm and Its Use with IPsec", <a href="./rfc3602">RFC 3602</a>,
266 September 2003.
267
268 [<a id="ref-RFC4106">RFC4106</a>] Viega, J. and D. McGrew, "The Use of Galois/Counter
269 Mode (GCM) in IPsec Encapsulating Security Payload
270 (ESP)", <a href="./rfc4106">RFC 4106</a>, June 2005.
271
272
273
274
275
276 <span class="grey">Law &amp; Solinas Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
279
280
281 [<a id="ref-RFC4303">RFC4303</a>] Kent, S., "IP Encapsulating Security Payload (ESP)",
282 <a href="./rfc4303">RFC 4303</a>, December 2005.
283
284 [<a id="ref-RFC4308">RFC4308</a>] Hoffman, P., "Cryptographic Suites for IPsec", <a href="./rfc4308">RFC</a>
285 <a href="./rfc4308">4308</a>, December 2005.
286
287 [<a id="ref-RFC4543">RFC4543</a>] McGrew, D. and J. Viega, "The Use of Galois Message
288 Authentication Code (GMAC) in IPsec ESP and AH", <a href="./rfc4543">RFC</a>
289 <a href="./rfc4543">4543</a>, May 2006.
290
291 [<a id="ref-RFC4868">RFC4868</a>] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-
292 SHA-384, and HMAC-SHA-512 with IPsec", <a href="./rfc4868">RFC 4868</a>, May
293 2007.
294
295 [<a id="ref-RFC4869">RFC4869</a>] Law, L. and J. Solinas, "Suite B Cryptographic Suites
296 for IPsec", <a href="./rfc4869">RFC 4869</a>, May 2007.
297
298 [<a id="ref-RFC5903">RFC5903</a>] Fu, D. and J. Solinas, "Elliptic Curve Groups modulo a
299 Prime (ECP Groups) for IKE and IKEv2", <a href="./rfc5903">RFC 5903</a>, June
300 2010.
301
302 [<a id="ref-RFC5996">RFC5996</a>] Kaufman, C., Hoffman, P., Nir, Y., and P. Eronen,
303 "Internet Key Exchange Protocol Version 2 (IKEv2)", <a href="./rfc5996">RFC</a>
304 <a href="./rfc5996">5996</a>, September 2010.
305
306 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
307
308 [<a id="ref-AES">AES</a>] U.S. Department of Commerce/National Institute of
309 Standards and Technology, "Advanced Encryption Standard
310 (AES)", FIPS PUB 197, November 2001,
311 &lt;<a href="http://csrc.nist.gov/publications/fips/index.html">http://csrc.nist.gov/publications/fips/index.html</a>&gt;.
312
313 [<a id="ref-RFC6380">RFC6380</a>] Burgin, K. and M. Peck, "Suite B Profile for Internet
314 Protocol Security (IPsec)", <a href="./rfc6380">RFC 6380</a>, October 2011.
315
316 [<a id="ref-SuiteB">SuiteB</a>] U.S. National Security Agency, "NSA Suite B
317 Cryptography", January 2009, &lt;<a href="http://www.nsa.gov/ia/programs/suiteb_cryptography/">http://www.nsa.gov/</a>
318 <a href="http://www.nsa.gov/ia/programs/suiteb_cryptography/">ia/programs/suiteb_cryptography/</a>&gt;.
319
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Law &amp; Solinas Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6379">RFC 6379</a> Suite B Crypto for IPsec October 2011</span>
335
336
337 Authors' Addresses
338
339 Laurie E. Law
340 National Security Agency
341
342 EMail: [email protected]
343
344
345 Jerome A. Solinas
346 National Security Agency
347
348 EMail: [email protected]
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 Law &amp; Solinas Informational [Page 7]
389 </pre>