forked from usnistgov/ACVP
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathacvp_sub_kdf135_tls.txt
672 lines (424 loc) · 26 KB
/
acvp_sub_kdf135_tls.txt
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
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
TBD B. Fussell, Ed.
Internet-Draft Cisco Systems, Inc.
Intended status: Informational August 1, 2018
Expires: February 2, 2019
ACVP TLS Key Derivation Function Algorithm JSON Specification
draft-ietf-acvp-subkdf135--tls-1.0
Abstract
This document defines the JSON schema for using SP800-135 TLS KDF
algorithms with the ACVP specification.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 2, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) 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.
Fussell Expires February 2, 2019 [Page 1]
Internet-Draft Sym Alg JSON August 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Capabilities Registration . . . . . . . . . . . . . . . . . . 2
2.1. Required Prerequisite Algorithms for KDF135 TLS
Validations . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. KDF135 TLS Algorithm Capabilities JSON Values . . . . . . 4
3. Test Vectors . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Test Groups JSON Schema . . . . . . . . . . . . . . . . . 6
3.2. Test Case JSON Schema . . . . . . . . . . . . . . . . . . 7
4. Test Vector Responses . . . . . . . . . . . . . . . . . . . . 8
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Normative References . . . . . . . . . . . . . . . . . . . . 10
Appendix A. Example SP800-135 TLS KDF Capabilities JSON Object . 10
Appendix B. Example Test Vectors JSON Object . . . . . . . . . . 10
Appendix C. Example Test Results JSON Object . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The Automated Crypto Validation Protocol (ACVP) defines a mechanism
to automatically verify the cryptographic implementation of a
software or hardware crypto module. The ACVP specification defines
how a crypto module communicates with an ACVP server, including
crypto capabilities negotiation, session management, authentication,
vector processing and more. The ACVP specification does not define
algorithm specific JSON constructs for performing the crypto
validation. A series of ACVP sub-specifications define the
constructs for testing individual crypto algorithms. Each sub-
specification addresses a specific class of crypto algorithms. This
sub-specification defines the JSON constructs for testing SP800-135
TLS KDF algorithms using ACVP.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted in RFC 2119 [RFC2119].
2. Capabilities Registration
ACVP requires crypto modules to register their capabilities. This
allows the crypto module to advertise support for specific
algorithms, notifying the ACVP server which algorithms need test
vectors generated for the validation process. This section describes
Fussell Expires February 2, 2019 [Page 2]
Internet-Draft Sym Alg JSON August 2018
the constructs for advertising support of SP800-135 TLS KDF
algorithms to the ACVP server.
The algorithm capabilities are advertised as JSON objects within the
'algorithms' value of the ACVP registration message. The
'algorithms' value is an array, where each array element is an
individual JSON object defined in this section. The 'algorithms'
value is part of the 'capability_exchange' element of the ACVP JSON
registration message. See the ACVP specification for details on the
registration message. Each KDF algorithm capability advertised is a
self-contained JSON object.
2.1. Required Prerequisite Algorithms for KDF135 TLS Validations
Some KDF135 algorithm implementations rely on other cryptographic
primitives. For example, TLS uses an underlying SHA algorithm. Each
of these underlying algorithm primitives must be validated, either
separately or as part of the same submission. ACVP provides a
mechanism for specifying the required prerequisites:
+--------------+--------------+---------------+----------+----------+
| JSON Value | Description | JSON type | Valid | Optional |
| | | | Values | |
+--------------+--------------+---------------+----------+----------+
| algorithm | a | value | HMAC, | No |
| | prerequisite | | SHA | |
| | algorithm | | | |
| | | | | |
| valValue | algorithm | value | actual | No |
| | validation | | number | |
| | number | | or | |
| | | | "same" | |
| | | | | |
| prereqAlgVal | prerequistie | object with | see | No |
| | algorithm | algorithm and | above | |
| | validation | valValue | | |
| | | properties | | |
| | | | | |
| prereqVals | prerequistie | array of | see | No |
| | algorithm | prereqAlgVal | above | |
| | validations | objects | | |
+--------------+--------------+---------------+----------+----------+
Table 1: Required Prerequisite Algorithms JSON Values
Fussell Expires February 2, 2019 [Page 3]
Internet-Draft Sym Alg JSON August 2018
2.2. KDF135 TLS Algorithm Capabilities JSON Values
Each algorithm capability advertised is a self-contained JSON object
using the following values.
Fussell Expires February 2, 2019 [Page 4]
Internet-Draft Sym Alg JSON August 2018
+----------+-------------+-------------+-----------------+----------+
| JSON | Description | JSON type | Valid Values | Optional |
| Value | | | | |
+----------+-------------+-------------+-----------------+----------+
| algorith | The KDF to | value | "kdf- | No |
| m | be | | components" | |
| | validated | | | |
| | | | | |
| mode | The KDF- | value | "tls" | No |
| | Component | | | |
| | to be | | | |
| | validated | | | |
| | | | | |
| revision | The | value | "1.0" | No |
| | algorithm | | | |
| | testing | | | |
| | revision to | | | |
| | use. | | | |
| | | | | |
| prereqVa | Prerequisit | array of pr | See Section 2.1 | No |
| ls | e algorithm | ereqAlgVal | | |
| | validations | objects | | |
| | | | | |
| tlsVersi | The version | array | "v1.0/1.1", and | No |
| on | of TLS | | "v1.2" | |
| | supported. | | | |
| | | | | |
| hashAlg | SHA | array | SHA2-256, | Yes |
| | functions | | SHA2-384, | |
| | supported | | SHA2-512 | |
| | if TLS | | | |
| | Version | | | |
| | "v1.2" is | | | |
| | included in | | | |
| | the registr | | | |
| | ation. Note | | | |
| | this field | | | |
| | is only | | | |
| | required | | | |
| | when "v1.2" | | | |
| | is present. | | | |
+----------+-------------+-------------+-----------------+----------+
Table 2: SP800-135 TLS KDF Algorithm Capabilities JSON Values
Note: Some optional values are required depending on the algorithm.
Failure to provide these values will result in the ACVP server
returning an error to the ACVP client during registration.
Fussell Expires February 2, 2019 [Page 5]
Internet-Draft Sym Alg JSON August 2018
3. Test Vectors
The ACVP server provides test vectors to the ACVP client, which are
then processed and returned to the ACVP server for validation. A
typical ACVP validation session would require multiple test vector
sets to be downloaded and processed by the ACVP client. Each test
vector set represents an individual Key Derivation Function (KDF),
such as SNMP, SSH, etc. This section describes the JSON schema for a
test vector set used with SP800-135 TLS KDF algorithms.
The test vector set JSON schema is a multi-level hierarchy that
contains meta data for the entire vector set as well as individual
test vectors to be processed by the ACVP client.The following table
describes the JSON elements at the top level of the hierarchy.
+------------+---------------------------------------------+--------+
| JSON Value | Description | JSON |
| | | type |
+------------+---------------------------------------------+--------+
| acvVersion | Protocol version identifier | value |
| | | |
| vsId | Unique numeric identifier for the vector | value |
| | set | |
| | | |
| algorithm | "kdf-components" | value |
| | | |
| mode | "tls" | value |
| | | |
| revision | "1.0" | value |
| | | |
| testGroups | Array of test group JSON objects, which are | array |
| | defined in Section 3.1 | |
+------------+---------------------------------------------+--------+
Table 3: Vector Set JSON Object
3.1. Test Groups JSON Schema
The testGroups element at the top level in the test vector JSON
object is an array of test groups. Test vectors are grouped into
similar test cases to reduce the amount of data transmitted in the
vector set. For instance, all test vectors that use the same key
size would be grouped together. The Test Group JSON object contains
meta data that applies to all test vectors within the group. The
following table describes the secure hash JSON elements of the Test
Group JSON object.
The KDF test group for TLS is as follows:
Fussell Expires February 2, 2019 [Page 6]
Internet-Draft Sym Alg JSON August 2018
+-----------------------+------------------------+-------+----------+
| JSON Value | Description | JSON | Optional |
| | | type | |
+-----------------------+------------------------+-------+----------+
| tgId | Numeric identifier for | value | No |
| | the test group, unique | | |
| | across the entire | | |
| | vector set. | | |
| | | | |
| tlsVersion | The version of TLS | value | No |
| | used in the test group | | |
| | | | |
| hashAlg | SHA version used | value | Yes |
| | | | |
| preMasterSecretLength | Pre-master secret | value | No |
| | length in bits | | |
| | | | |
| keyBlockLength | Key block length in | value | No |
| | bits | | |
| | | | |
| tests | Array of individual | array | No |
| | test vector JSON | | |
| | objects, which are | | |
| | defined in Section 3.2 | | |
| | | | |
+-----------------------+------------------------+-------+----------+
Table 4: Vector Group JSON Object
3.2. Test Case JSON Schema
Each test group contains an array of one or more test cases. Each
test case is a JSON object that represents a single test vector to be
processed by the ACVP client. The following table describes the JSON
elements for each SP800-135 TLS KDF test vector.
Fussell Expires February 2, 2019 [Page 7]
Internet-Draft Sym Alg JSON August 2018
+-------------------+----------------------------+-------+----------+
| JSON Value | Description | JSON | Optional |
| | | type | |
+-------------------+----------------------------+-------+----------+
| tcId | Numeric identifier for the | value | No |
| | test case, unique across | | |
| | the entire vector set. | | |
| | | | |
| preMasterSecret | Pre-master secret value | value | No |
| | | | |
| serverHelloRandom | Server Hello random value | value | No |
| | | | |
| clientHelloRandom | Client Hello random value | value | No |
| | | | |
| serverRandom | Server random value | value | No |
| | | | |
| clientRandom | Client random value | value | No |
+-------------------+----------------------------+-------+----------+
Table 5: Test Case JSON Object
4. Test Vector Responses
After the ACVP client downloads and processes a vector set, it must
send the response vectors back to the ACVP server. The following
table describes the JSON object that represents a vector set
response.
+------------+---------------------------------------------+--------+
| JSON Value | Description | JSON |
| | | type |
+------------+---------------------------------------------+--------+
| acvVersion | Protocol version identifier | value |
| | | |
| vsId | Unique numeric identifier for the vector | value |
| | set | |
| | | |
| testGroups | Array of JSON objects that represent each | array |
| | test vector group. See | |
| | Table 7 | |
| | | |
+------------+---------------------------------------------+--------+
Table 6: Vector Set Response JSON Object
The testGroups section is used to organize the ACVP client response
in a similar manner to how it receives vectors. Several algorithms
Fussell Expires February 2, 2019 [Page 8]
Internet-Draft Sym Alg JSON August 2018
SHALL require the client to send back group level properties in their
response. This structure helps accommodate that.
+-----------+--------------------------------------------+----------+
| JSON | Description | JSON |
| Value | | type |
+-----------+--------------------------------------------+----------+
| tgId | The test group Id | value |
| | | |
| tests | The tests associated to the group | value |
| | specified in tgId | |
| | | |
+-----------+--------------------------------------------+----------+
Table 7: Vector Set Group Response JSON Object
The following table describes the JSON object that represents a
vector set response for TLS.
+--------------+-------------------------------------------+--------+
| JSON Value | Description | JSON |
| | | type |
+--------------+-------------------------------------------+--------+
| tcId | Numeric identifier for the test case, | value |
| | unique across the entire vector set. | |
| | | |
| masterSecret | Master secret value | value |
| | | |
| keyBlock | Key block value of the expansion step | value |
| | | |
+--------------+-------------------------------------------+--------+
Table 8: Vector Set Response JSON Object
5. Acknowledgements
TBD...
6. IANA Considerations
This memo includes no request to IANA.
7. Security Considerations
Security considerations are addressed by the ACVP specification.
Fussell Expires February 2, 2019 [Page 9]
Internet-Draft Sym Alg JSON August 2018
8. Normative References
[ACVP] authSurName, authInitials., "ACVP Specification", 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
Appendix A. Example SP800-135 TLS KDF Capabilities JSON Object
The following is a example JSON object advertising support for SHA-
256.
{
"algorithm": "kdf-components",
"mode": "tls",
"revision": "1.0",
"prereqVals": [
{
"algorithm": "HMAC",
"valValue": "123456"
},
{
"algorithm": "SHA",
"valValue": "123456"
}
],
"tlsVersion": [
"v1.0/1.1",
"v1.2"
],
"hashAlg": [
"SHA2-256",
"SHA2-384",
"SHA2-512"
]
}
Appendix B. Example Test Vectors JSON Object
The following is a example JSON object for SP800-135 TLS KDF test
vectors sent from the ACVP server to the crypto module.
Fussell Expires February 2, 2019 [Page 10]
Internet-Draft Sym Alg JSON August 2018
[
{
"acvVersion": <acvp-version>
},
{
"vsId": 1564,
"algorithm": "kdf-components",
"mode": "tls",
"revision": "1.0",
"testGroups": [
{
"tgId": 1,
"tlsVersion": "v1.0/1.1",
"hashAlg": "SHA-1",
"preMasterSecretLength": 384,
"keyBlockLength": 832,
"tests": [
{
"tcId": 1,
"clientHelloRandom": "00D5EDFC0A7D8B0913DEB191B592B7AE03503F48E876D702CD7A467E823A416B",
"serverHelloRandom": "14D06FC8F2792762BA9E5894147583C65D3BF0DA8D9FAE4CC46A443A675AF274",
"clientRandom": "DDFB77CB1304A0541C6CC07779441F5018385111E368CE4D69C8E8E455737601",
"serverRandom": "D59EB4E444005709409C572BA8A160EE10A8BAEFC5C70BBBDD79E57D648B8ADD",
"preMasterSecret": "2F0D26CC2487169D83D95064A17BC70AE8C775A8C5228227A21184211B0EE26442520D7C9DA07578F8046A6A9D791351"
}
]
}
]
}
]
Appendix C. Example Test Results JSON Object
The following is a example JSON object for SP800-135 TLS KDF test
results sent from the crypto module to the ACVP server.
Fussell Expires February 2, 2019 [Page 11]
Internet-Draft Sym Alg JSON August 2018
[{
"acvVersion": <acvp-version>
},
{
"vsId": 1564,
"testGroups": [{
"tgId": 1,
"tests": [{
"tcId": 1,
"masterSecret": "38E544579C06B3F515E1CE556E8F63D72694BAD1CC27F0896EFF2C0BC0BA82B958CB2B008191656DD76FCDD0A30A1375",
"keyBlock": "9F39392B46ABF3D852F4F31BE188909738749CAAF93A4AB6F1EBE645EAACE04B2F1792EFD16946D63674CEB0D75F44210502108ACDF4B2A6630E1706480807EC068FE16127430FF8B9C87EDE119BC91A9890D2761131169E1FB7DAC72282BB32B772BEC716C2D549"
}]
}]
}
]
Author's Address
Barry Fussell (editor)
Cisco Systems, Inc.
170 West Tasman Dr.
San Jose, CA 95134
USA
Email: [email protected]
Fussell Expires February 2, 2019 [Page 12]