forked from usnistgov/ACVP
-
Notifications
You must be signed in to change notification settings - Fork 0
/
acvp_sub_kas_ffc.html
5061 lines (4981 loc) · 209 KB
/
acvp_sub_kas_ffc.html
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
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>ACVP KAS FFC JSON Specification</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents">
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction">
<link href="#rfc.section.1.1" rel="Chapter" title="1.1 Requirements Language">
<link href="#rfc.section.2" rel="Chapter" title="2 Test Types and Test Coverage">
<link href="#rfc.section.2.1" rel="Chapter" title="2.1 Test Coverage">
<link href="#rfc.section.2.1.1" rel="Chapter" title="2.1.1 KAS-ECC Requirements Covered">
<link href="#rfc.section.2.1.2" rel="Chapter" title="2.1.2 KAS-ECC Requirements Not Covered">
<link href="#rfc.section.3" rel="Chapter" title="3 Capabilities Registration">
<link href="#rfc.section.3.1" rel="Chapter" title="3.1 Required Prerequisite Algorithms for KAS FFC Validations">
<link href="#rfc.section.3.2" rel="Chapter" title="3.2 KAS FFC Algorithm Capabilities JSON Values">
<link href="#rfc.section.3.3" rel="Chapter" title="3.3 Supported KAS FFC Functions">
<link href="#rfc.section.3.4" rel="Chapter" title="3.4 KAS FFC Schemes">
<link href="#rfc.section.3.4.1" rel="Chapter" title="3.4.1 KAS FFC Scheme Capabilities JSON Values">
<link href="#rfc.section.3.4.2" rel="Chapter" title="3.4.2 Supported KAS FFC Schemes">
<link href="#rfc.section.3.5" rel="Chapter" title="3.5 KAS FFC Modes">
<link href="#rfc.section.3.5.1" rel="Chapter" title="3.5.1 KAS FFC noKdfNoKc">
<link href="#rfc.section.3.5.2" rel="Chapter" title="3.5.2 KAS FFC kdfNoKc">
<link href="#rfc.section.3.5.3" rel="Chapter" title="3.5.3 KAS FFC kdfKc">
<link href="#rfc.section.3.6" rel="Chapter" title="3.6 Parameter Sets">
<link href="#rfc.section.3.6.1" rel="Chapter" title="3.6.1 KAS FFC Parameter Set">
<link href="#rfc.section.3.6.2" rel="Chapter" title="3.6.2 KAS FFC Parameter Set Details">
<link href="#rfc.section.3.7" rel="Chapter" title="3.7 Supported Hash Algorithm Methods">
<link href="#rfc.section.3.8" rel="Chapter" title="3.8 Supported KAS FFC MAC Options">
<link href="#rfc.section.3.9" rel="Chapter" title="3.9 Supported KAS FFC KDF Options">
<link href="#rfc.section.3.9.1" rel="Chapter" title="3.9.1 Other Information Construction">
<link href="#rfc.section.3.10" rel="Chapter" title="3.10 Supported KAS FFC KC Options">
<link href="#rfc.section.3.11" rel="Chapter" title="3.11 Example KAS FFC Capabilities JSON Object">
<link href="#rfc.section.3.12" rel="Chapter" title="3.12 Example KAS FFC Component Capabilities JSON Object">
<link href="#rfc.section.4" rel="Chapter" title="4 Generation requirements per party per scheme">
<link href="#rfc.section.5" rel="Chapter" title="5 Test Vectors">
<link href="#rfc.section.5.1" rel="Chapter" title="5.1 Test Groups JSON Schema">
<link href="#rfc.section.5.2" rel="Chapter" title="5.2 Test Case JSON Schema">
<link href="#rfc.section.5.3" rel="Chapter" title="5.3 Example Test Vectors JSON Object">
<link href="#rfc.section.5.4" rel="Chapter" title="5.4 Example Test Vectors Component JSON Object">
<link href="#rfc.section.6" rel="Chapter" title="6 Test Vector Responses">
<link href="#rfc.section.6.1" rel="Chapter" title="6.1 Example Test Results JSON Object">
<link href="#rfc.section.6.2" rel="Chapter" title="6.2 Example Test Results Component JSON Object">
<link href="#rfc.section.7" rel="Chapter" title="7 Acknowledgements">
<link href="#rfc.section.8" rel="Chapter" title="8 IANA Considerations">
<link href="#rfc.section.9" rel="Chapter" title="9 Security Considerations">
<link href="#rfc.references" rel="Chapter" title="10 Normative References">
<link href="#rfc.authors" rel="Chapter">
<meta name="generator" content="xml2rfc version 2.6.2 - http://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Fussell, B., Ed. and R. Hammett, Ed." />
<meta name="dct.identifier" content="urn:ietf:id:draft-ietf-acvp-subkasffc-0.5" />
<meta name="dct.issued" scheme="ISO8601" content="2018-9" />
<meta name="dct.abstract" content="This document defines the JSON schema for using KAS FFC algorithms with the ACVP specification." />
<meta name="description" content="This document defines the JSON schema for using KAS FFC algorithms with the ACVP specification." />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left">TBD</td>
<td class="right">B. Fussell, Ed.</td>
</tr>
<tr>
<td class="left">Internet-Draft</td>
<td class="right">Cisco Systems, Inc.</td>
</tr>
<tr>
<td class="left">Intended status: Informational</td>
<td class="right">R. Hammett, Ed.</td>
</tr>
<tr>
<td class="left">Expires: March 5, 2019</td>
<td class="right">G2, Inc.</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">September 2018</td>
</tr>
</tbody>
</table>
<p class="title">ACVP KAS FFC JSON Specification<br />
<span class="filename">draft-ietf-acvp-subkasffc-0.5</span></p>
<h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
<p>This document defines the JSON schema for using KAS FFC algorithms with the ACVP specification.</p>
<h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>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 http://datatracker.ietf.org/drafts/current/.</p>
<p>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."</p>
<p>This Internet-Draft will expire on March 5, 2019.</p>
<h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
<p>Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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.</p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a>
</li>
<ul><li>1.1. <a href="#rfc.section.1.1">Requirements Language</a>
</li>
</ul><li>2. <a href="#rfc.section.2">Test Types and Test Coverage</a>
</li>
<ul><li>2.1. <a href="#rfc.section.2.1">Test Coverage</a>
</li>
<ul><li>2.1.1. <a href="#rfc.section.2.1.1">KAS-ECC Requirements Covered</a>
</li>
<li>2.1.2. <a href="#rfc.section.2.1.2">KAS-ECC Requirements Not Covered</a>
</li>
</ul></ul><li>3. <a href="#rfc.section.3">Capabilities Registration</a>
</li>
<ul><li>3.1. <a href="#rfc.section.3.1">Required Prerequisite Algorithms for KAS FFC Validations</a>
</li>
<li>3.2. <a href="#rfc.section.3.2">KAS FFC Algorithm Capabilities JSON Values</a>
</li>
<li>3.3. <a href="#rfc.section.3.3">Supported KAS FFC Functions</a>
</li>
<li>3.4. <a href="#rfc.section.3.4">KAS FFC Schemes</a>
</li>
<ul><li>3.4.1. <a href="#rfc.section.3.4.1">KAS FFC Scheme Capabilities JSON Values</a>
</li>
<li>3.4.2. <a href="#rfc.section.3.4.2">Supported KAS FFC Schemes</a>
</li>
</ul><li>3.5. <a href="#rfc.section.3.5">KAS FFC Modes</a>
</li>
<ul><li>3.5.1. <a href="#rfc.section.3.5.1">KAS FFC noKdfNoKc</a>
</li>
<li>3.5.2. <a href="#rfc.section.3.5.2">KAS FFC kdfNoKc</a>
</li>
<li>3.5.3. <a href="#rfc.section.3.5.3">KAS FFC kdfKc</a>
</li>
</ul><li>3.6. <a href="#rfc.section.3.6">Parameter Sets</a>
</li>
<ul><li>3.6.1. <a href="#rfc.section.3.6.1">KAS FFC Parameter Set</a>
</li>
<li>3.6.2. <a href="#rfc.section.3.6.2">KAS FFC Parameter Set Details</a>
</li>
</ul><li>3.7. <a href="#rfc.section.3.7">Supported Hash Algorithm Methods</a>
</li>
<li>3.8. <a href="#rfc.section.3.8">Supported KAS FFC MAC Options</a>
</li>
<li>3.9. <a href="#rfc.section.3.9">Supported KAS FFC KDF Options</a>
</li>
<ul><li>3.9.1. <a href="#rfc.section.3.9.1">Other Information Construction</a>
</li>
</ul><li>3.10. <a href="#rfc.section.3.10">Supported KAS FFC KC Options</a>
</li>
<li>3.11. <a href="#rfc.section.3.11">Example KAS FFC Capabilities JSON Object</a>
</li>
<li>3.12. <a href="#rfc.section.3.12">Example KAS FFC Component Capabilities JSON Object</a>
</li>
</ul><li>4. <a href="#rfc.section.4">Generation requirements per party per scheme</a>
</li>
<li>5. <a href="#rfc.section.5">Test Vectors</a>
</li>
<ul><li>5.1. <a href="#rfc.section.5.1">Test Groups JSON Schema</a>
</li>
<li>5.2. <a href="#rfc.section.5.2">Test Case JSON Schema</a>
</li>
<li>5.3. <a href="#rfc.section.5.3">Example Test Vectors JSON Object</a>
</li>
<li>5.4. <a href="#rfc.section.5.4">Example Test Vectors Component JSON Object</a>
</li>
</ul><li>6. <a href="#rfc.section.6">Test Vector Responses</a>
</li>
<ul><li>6.1. <a href="#rfc.section.6.1">Example Test Results JSON Object</a>
</li>
<li>6.2. <a href="#rfc.section.6.2">Example Test Results Component JSON Object</a>
</li>
</ul><li>7. <a href="#rfc.section.7">Acknowledgements</a>
</li>
<li>8. <a href="#rfc.section.8">IANA Considerations</a>
</li>
<li>9. <a href="#rfc.section.9">Security Considerations</a>
</li>
<li>10. <a href="#rfc.references">Normative References</a>
</li>
<li><a href="#rfc.authors">Authors' Addresses</a>
</li>
</ul>
<h1 id="rfc.section.1">
<a href="#rfc.section.1">1.</a> Introduction</h1>
<p id="rfc.section.1.p.1">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 KAS FFC algorithms using ACVP.</p>
<h1 id="rfc.section.1.1">
<a href="#rfc.section.1.1">1.1.</a> Requirements Language</h1>
<p id="rfc.section.1.1.p.1">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 <a href="#RFC2119" class="xref">RFC 2119</a>. </p>
<h1 id="rfc.section.2">
<a href="#rfc.section.2">2.</a> <a href="#test_types" id="test_types">Test Types and Test Coverage</a>
</h1>
<p id="rfc.section.2.p.1">The ACVP server performs a set of tests on the KAS protocol in order to assess the correctness and robustness of the implementation. A typical ACVP validation session would require multiple tests to be performed for every supported permutation of KAS capabilities. This section describes the design of the tests used to validate implementations of KAS algorithms. There are two test types for KAS testing: </p>
<ul class="empty">
<li>"AFT" - Algorithm Function Test. In the AFT test mode, the IUT MUST act as a party in the Key Agreement with the ACVP server. The server SHALL generate and provide all necessary information for the IUT to perform a successful key agreement; both the server and IUT MAY act as party U/V, as well as recipient/provider to key confirmation.</li>
<li>"VAL" - Validation test. In the VAL test mode, The ACVP server generates a complete (from both party U and party V's perspectives) key agreement, and REQUIRES the IUT to determine if that agreement is valid. Various types of errors SHALL be introduced in varying portions of the key agreement process (changed DKM, changed key, changed hash, etc), that the IUT MUST be able to detect and report on.</li>
</ul>
<p> </p>
<h1 id="rfc.section.2.1">
<a href="#rfc.section.2.1">2.1.</a> <a href="#test_coverage" id="test_coverage">Test Coverage</a>
</h1>
<p id="rfc.section.2.1.p.1">The tests described in this document have the intention of ensuring an implementation is conformant to <a href="#SP800-56a" class="xref">[SP800-56a]</a>. </p>
<h1 id="rfc.section.2.1.1">
<a href="#rfc.section.2.1.1">2.1.1.</a> <a href="#requirements_covered_kas_ecc" id="requirements_covered_kas_ecc">KAS-ECC Requirements Covered</a>
</h1>
<p></p>
<ul class="empty">
<li>SP 800-56a - 4.1 Key Establishment Preparations. The ACVP server is responsible for generating domain parameters as per the IUT's capability registration.</li>
<li>SP 800-56a - 4.2 Key-Agreement Process. Both the ACVP server and IUT participate in the Key Agreement process. The server and IUT can both take the roles of party U/V, and as such the "performer" of steps depicted in "Figure 2: Key Agreement process" can vary.</li>
<li>SP 800-56a - 5.1 Cryptographic Hash Functions. All modes of performing KAS SHALL make use of a hash function. The hash function MAY be used for confirmation of a successfully generated shared secret Z (noKdfNoKc), or as a primitive within the KDF being tested (kdfNoKc and kdfKc).</li>
<li>SP 800-56a - 5.2 Message Authentication Code (MAC) Algorithm. A MAC is utilized for confirmation of success for kdfNoKc and kdfKc modes of KAS. Note - a MAC prerequisite is REQUIRED only for kdfKc, though is utilized for both kdfNoKc and kdfKc.</li>
<li>SP 800-56a - 5.4 Nonce. Nonces are made use of in various KAS schemes - both the ACVP server and IUT SHALL be expected to generate nonces.</li>
<li>SP 800-56a - 5.6 Domain Parameters. Domain Parameter Generation SHALL be performed solely from the ACVP server, with constraints from the IUTs capabilities registration. The same set of domain parameters SHALL generate all keypairs (party U/V, static/ephemeral) for a single test case.</li>
<li>SP 800-56a - 5.6 Key-Pair Generation. While Key-Pairs are used in each KAS scheme, the generation of said key-pairs is out of scope for KAS testing. Random tests from the VAL groups, MAY inject bad keypairs that the IUT MUST be able detect. These random tests are only present in groups given appropriate assurance functions see: <a href="#supported_functions" class="xref">Section 3.3</a> </li>
<li>SP 800-56a - 4.3 DLC-based Key-Transport Process / 5.7 DLC Primitives. Depending on the scheme used, either Diffie Hellman or MQV SHALL be used to negotiate a shared secret of z. Testing and validation of such key exchanges is covered under their respective schemes.</li>
<li>SP 800-56a - 5.8 Key-Derivation Methods for Key-Agreement Schemes. All schemes/modes save noKdfNoKc (component) MUST make use of a KDF. KDF construction SHALL utilize <a href="#oiPatternConstruction" class="xref">Section 3.9.1</a> for its pattern. </li>
<li>SP 800-56a - 5.9 Key Confirmation. Most KAS schemes allow for a Key Confirmation process, the ACVP server and IUT MAY be Providers or Recipients of said confirmation. Additionally, key confirmation MAY be performed on one or both parties (depending on scheme).</li>
<li>SP 800-56a - 6 Key Agreement Schemes. All schemes specified in referenced document are supported for validation with the ACVP server.</li>
</ul>
<p> </p>
<h1 id="rfc.section.2.1.2">
<a href="#rfc.section.2.1.2">2.1.2.</a> <a href="#requirements_not_covered_kas_ecc" id="requirements_not_covered_kas_ecc">KAS-ECC Requirements Not Covered</a>
</h1>
<p></p>
<ul class="empty">
<li>SP 800-56a - 4.1 Key Establishment Preparations. The ACVP server SHALL NOT make a distinction between IUT generated keys via a trusted third party and the IUT itself.</li>
<li>SP 800-56a - 5.3 Random Number Generation. The IUT MUST perform all random number generation with a validated random number generator. A DRBG is REQUIRED as a prerequisite to KAS, but SHALL NOT be in the scope testing assurances. </li>
<li>SP 800-56a - 5.4 Nonce. Nonce generation is utilized for several schemes. The various methods of generating a nonce described in section 5.5 MUST be used, however their generation SHALL NOT be in scope of KAS testing assurances</li>
<li>SP 800-56a - 5.5.2 Assurances of Domain-Parameter Validity. The ACVP server SHALL generate all domain parameters, IUT validation of such parameters is SHALL NOT be in scope for KAS testing.</li>
<li>SP 800-56a - 5.5.3 Domain Parameter Management. Domain Parameter Management SHALL NOT be in scope for KAS testing.</li>
<li>SP 800-56a - 5.6 Key-Pair Generation. While Key-Pairs MUST be used in each KAS scheme, the generation, assurances, and management of said key-pairs SHALL NOT be in scope of KAS testing.</li>
<li>SP 800-56a - 5.8 Key-Derivation Methods for Key-Agreement Schemes. Two-step Key-Derivation (Extraction-then-Expansion) SHALL NOT be utilized in KAS testing.</li>
<li>SP 800-56a - 5.9 Key Confirmation. KMAC is referenced in 800-56a as being a valid MAC function; it however SHALL NOT (currently) be supported in KAS testing.</li>
<li>SP 800-56a - 5.7 Rationale for Selecting a Specific Scheme. It is expected that the IUT registers all schemes it supports in its capabilities registration. Selecting specific schemes from a KAS testing perspective SHALL NOT be in scope.</li>
<li>SP 800-56a - 8 Key Recovery. Key Recovery SHALL NOT be in scope of KAS testing.</li>
</ul>
<p> </p>
<h1 id="rfc.section.3">
<a href="#rfc.section.3">3.</a> <a href="#caps_reg" id="caps_reg">Capabilities Registration</a>
</h1>
<p id="rfc.section.3.p.1">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 the constructs for advertising support of KAS FFC algorithms to the ACVP server.</p>
<p id="rfc.section.3.p.2">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.</p>
<h1 id="rfc.section.3.1">
<a href="#rfc.section.3.1">3.1.</a> <a href="#prereq_algs" id="prereq_algs">Required Prerequisite Algorithms for KAS FFC Validations</a>
</h1>
<p id="rfc.section.3.1.p.1">Some algorithm implementations rely on other cryptographic primitives. For example, IKEv2 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:</p>
<div id="rfc.table.1"></div>
<div id="rereqs_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>Required Prerequisite Algorithms JSON Values</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
<th class="left">Valid Values</th>
<th class="left">Optional</th>
</tr></thead>
<tbody>
<tr>
<td class="left">algorithm</td>
<td class="left">a prerequisite algorithm</td>
<td class="left">value</td>
<td class="left">CCM, CMAC, DRBG, DSA, HMAC, SHA</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">valValue</td>
<td class="left">algorithm validation number</td>
<td class="left">value</td>
<td class="left">actual number or "same"</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">prereqAlgVal</td>
<td class="left">prerequistie algorithm validation</td>
<td class="left">object with algorithm and valValue properties</td>
<td class="left">see above</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
</tbody>
</table>
<p id="rfc.section.3.1.p.2">KAS has conditional prerequisite algorithms, depending on the capabilities registered:</p>
<div id="rfc.table.2"></div>
<div id="prereqs_requirements_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>Prerequisite requirement conditions</caption>
<thead><tr>
<th class="left">Prerequisite Algorithm</th>
<th class="left">Condition</th>
</tr></thead>
<tbody>
<tr>
<td class="left">DRBG</td>
<td class="left">Always REQUIRED</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">SHA</td>
<td class="left">Always REQUIRED</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">DSA</td>
<td class="left">DSA.PQGGen validation REQUIRED when IUT using assurance function of "dpGen". DSA.PQGVer validation REQUIRED when IUT using assurance function of "dpVal". DSA.KeyPairGen validation REQUIRED when IUT using assurances functions of "keyPairGen", or "keyRegen". </td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">AES-CCM</td>
<td class="left">AES-CCM validation REQUIRED when IUT is performing KeyConfirmation (KC) and utilizing AES-CCM.</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">CMAC</td>
<td class="left">CMAC validation REQUIRED when IUT is performing KeyConfirmation (KC) and utilizing CMAC.</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">HMAC</td>
<td class="left">HMAC validation REQUIRED when IUT is performing KeyConfirmation (KC) and utilizing HMAC.</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.3.2">
<a href="#rfc.section.3.2">3.2.</a> <a href="#cap_ex" id="cap_ex">KAS FFC Algorithm Capabilities JSON Values</a>
</h1>
<p id="rfc.section.3.2.p.1">Each algorithm capability advertised is a self-contained JSON object using the following values.</p>
<div id="rfc.table.3"></div>
<div id="caps_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>KAS FFC Capabilities JSON Values</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
<th class="left">Valid Values</th>
<th class="left">Optional</th>
</tr></thead>
<tbody>
<tr>
<td class="left">algorithm</td>
<td class="left">The algorithm under test</td>
<td class="left">value</td>
<td class="left">KAS-FFC</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">mode</td>
<td class="left">The algorithm mode.</td>
<td class="left">value</td>
<td class="left">Component</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">prereqVals</td>
<td class="left">Prerequisite algorithm validations</td>
<td class="left">array of prereqAlgVal objects</td>
<td class="left">See <a href="#prereq_algs" class="xref">Section 3.1</a> </td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">function</td>
<td class="left">Type of function supported</td>
<td class="left">array</td>
<td class="left">See <a href="#supported_functions" class="xref">Section 3.3</a> </td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">scheme</td>
<td class="left">Array of supported key agreement schemes each having their own capabilities</td>
<td class="left">object</td>
<td class="left">See <a href="#supported_schemes" class="xref">Section 3.4.1</a> </td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
</tbody>
</table>
<p id="rfc.section.3.2.p.2">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.</p>
<h1 id="rfc.section.3.3">
<a href="#rfc.section.3.3">3.3.</a> <a href="#supported_functions" id="supported_functions">Supported KAS FFC Functions</a>
</h1>
<p id="rfc.section.3.3.p.1">The following function types MAY be advertised by the ACVP compliant crypto module:</p>
<p></p>
<ul>
<li>dpGen - IUT can perform domain parameter generation (FFC only)</li>
<li>dpVal - IUT can perform domain parameter validation (FFC only)</li>
<li>keyPairGen - IUT can perform keypair generation.</li>
<li>fullVal - IUT can perform full public key validation ( <a href="#SP800-56a" class="xref">[SP800-56a]</a> section 5.6.2.3.1 / 5.6.2.3.3) </li>
<li>partialVal - IUT can perform partial public key validation ( <a href="#SP800-56a" class="xref">[SP800-56a]</a> section 5.6.2.3.2 / 5.6.2.3.4) </li>
<li>keyRegen - IUT can regenerate keys given a specific seed and domain parameter (pqg for FFC, curve for ECC)</li>
</ul>
<p> </p>
<h1 id="rfc.section.3.4">
<a href="#rfc.section.3.4">3.4.</a> <a href="#schemes" id="schemes">KAS FFC Schemes</a>
</h1>
<h1 id="rfc.section.3.4.1">
<a href="#rfc.section.3.4.1">3.4.1.</a> <a href="#supported_schemes" id="supported_schemes">KAS FFC Scheme Capabilities JSON Values</a>
</h1>
<p id="rfc.section.3.4.1.p.1">All other scheme capabilities are advertised is a self-contained JSON object using the following values. Note that at least one of "noKdfNoKc", "kdfNoKc", or "kdfKc" MUST be supplied with the registration. See <a href="#supported_scheme_values" class="xref">Section 3.4.2</a> for allowed FFC scheme types. </p>
<div id="rfc.table.4"></div>
<div id="scheme_caps_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>KAS FFC Capabilities JSON Values</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
<th class="left">Valid Values</th>
<th class="left">Optional</th>
</tr></thead>
<tbody>
<tr>
<td class="left">kasRole</td>
<td class="left">Roles supported for key agreement</td>
<td class="left">array</td>
<td class="left">initiator and/or responder</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">noKdfNoKc</td>
<td class="left">Indicates no KDF, no KC tests are to be generated. Note this is a COMPONENT mode only test. This property MUST only be used with "KAS-FFC" / "Component"</td>
<td class="left">object</td>
<td class="left">
<a href="#noKdfNoKc" class="xref">Section 3.5.1</a> </td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">kdfNoKc</td>
<td class="left">Indicates KDF, no KC tests are to be generated. Note this is a KAS-FFC only test. This mode MUST only be used for registrations with "KAS-FFC" (no mode)</td>
<td class="left">object</td>
<td class="left">
<a href="#kdfNoKc" class="xref">Section 3.5.2</a> </td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
<tr>
<td class="left">kdfKc</td>
<td class="left">Indicates KDF, KC tests are to be generated. Note this is a KAS-FFC only test. This mode MAY only be used for registrations with "KAS-FFC" (no mode)</td>
<td class="left">object</td>
<td class="left">
<a href="#kdfKc" class="xref">Section 3.5.3</a> </td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.3.4.2">
<a href="#rfc.section.3.4.2">3.4.2.</a> <a href="#supported_scheme_values" id="supported_scheme_values">Supported KAS FFC Schemes</a>
</h1>
<p id="rfc.section.3.4.2.p.1">The following schemes MAY be advertised by the ACVP compliant crypto module:</p>
<p></p>
<ul>
<li>dhHybrid1</li>
<li>MQV2</li>
<li>dhEphem - KeyConfirmation not supported.</li>
<li>dhHybridOneFlow</li>
<li>MQV1</li>
<li>dhOneFlow - Can only provide unilateral key confirmation party V to party U.</li>
<li>dhStatic</li>
</ul>
<p> </p>
<h1 id="rfc.section.3.5">
<a href="#rfc.section.3.5">3.5.</a> <a href="#kasMode" id="kasMode">KAS FFC Modes</a>
</h1>
<h1 id="rfc.section.3.5.1">
<a href="#rfc.section.3.5.1">3.5.1.</a> <a href="#noKdfNoKc" id="noKdfNoKc">KAS FFC noKdfNoKc</a>
</h1>
<p id="rfc.section.3.5.1.p.1">Contains properties REQUIRED for "noKdfNoKc" registration. </p>
<div id="rfc.table.5"></div>
<div id="noKdfNoKc_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>NoKdfNoKc Capabilities</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
<th class="left">Valid Values</th>
<th class="left">Optional</th>
</tr></thead>
<tbody>
<tr>
<td class="left">parameterSet</td>
<td class="left">The parameterSet options for "noKdfNoKc"</td>
<td class="left">object</td>
<td class="left">
<a href="#parameter_set" class="xref">Section 3.6.1</a> </td>
<td class="left">No</td>
</tr>
<tr>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
<td class="left"></td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.3.5.2">
<a href="#rfc.section.3.5.2">3.5.2.</a> <a href="#kdfNoKc" id="kdfNoKc">KAS FFC kdfNoKc</a>
</h1>
<p id="rfc.section.3.5.2.p.1">Contains properties REQUIRED for "kdfNoKc" registration. </p>
<div id="rfc.table.6"></div>
<div id="kdfNoKc_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>kdfNoKc Capabilities</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>