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