forked from usnistgov/ACVP
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathacvp_sub_ecdsa.html
1671 lines (1607 loc) · 58 KB
/
acvp_sub_ecdsa.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 ECDSA Algorithm 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 Supported ECDSA Algorithms">
<link href="#rfc.section.3" rel="Chapter" title="3 Test Types and Test Coverage">
<link href="#rfc.section.3.1" rel="Chapter" title="3.1 Test Coverage">
<link href="#rfc.section.3.1.1" rel="Chapter" title="3.1.1 Requirements Covered">
<link href="#rfc.section.3.1.2" rel="Chapter" title="3.1.2 Requirements Not Covered">
<link href="#rfc.section.4" rel="Chapter" title="4 Capabilities Registration">
<link href="#rfc.section.4.1" rel="Chapter" title="4.1 Required Prerequisite Algorithms for ECDSA Validations">
<link href="#rfc.section.4.2" rel="Chapter" title="4.2 ECDSA Algorithm Capabilities Registration">
<link href="#rfc.section.4.3" rel="Chapter" title="4.3 Supported ECDSA Modes Capabilities">
<link href="#rfc.section.4.3.1" rel="Chapter" title="4.3.1 The keyGen Mode Capabilities">
<link href="#rfc.section.4.3.1.1" rel="Chapter" title="4.3.1.1 keyGen Full Set of Capabilities">
<link href="#rfc.section.4.3.2" rel="Chapter" title="4.3.2 The keyVer Mode Capabilities">
<link href="#rfc.section.4.3.2.1" rel="Chapter" title="4.3.2.1 keyVer Full Set of Capabilities">
<link href="#rfc.section.4.3.3" rel="Chapter" title="4.3.3 The sigGen Mode Capabilities">
<link href="#rfc.section.4.3.3.1" rel="Chapter" title="4.3.3.1 sigGen Full Set of Capabilities">
<link href="#rfc.section.4.3.4" rel="Chapter" title="4.3.4 The sigVer Mode Capabilities">
<link href="#rfc.section.4.3.4.1" rel="Chapter" title="4.3.4.1 sigVer Full Set of Capabilities">
<link href="#rfc.section.5" rel="Chapter" title="5 Supported DSA Conformances">
<link href="#rfc.section.6" rel="Chapter" title="6 Test Vectors">
<link href="#rfc.section.6.1" rel="Chapter" title="6.1 Test Groups JSON Schema">
<link href="#rfc.section.6.2" rel="Chapter" title="6.2 Test Case JSON Schema">
<link href="#rfc.section.7" rel="Chapter" title="7 Test Vector Responses">
<link href="#rfc.section.8" rel="Chapter" title="8 Acknowledgements">
<link href="#rfc.section.9" rel="Chapter" title="9 IANA Considerations">
<link href="#rfc.section.10" rel="Chapter" title="10 Security Considerations">
<link href="#rfc.references" rel="Chapter" title="11 Normative References">
<link href="#rfc.appendix.A" rel="Chapter" title="A Example Capabilities JSON Object">
<link href="#rfc.appendix.B" rel="Chapter" title="B Example Vector Set Request/Responses JSON Object">
<link href="#rfc.appendix.B.1" rel="Chapter" title="B.1 Example Test ECDSA KeyGen JSON Object">
<link href="#rfc.appendix.B.2" rel="Chapter" title="B.2 Example Test ECDSA KeyVer JSON Object">
<link href="#rfc.appendix.B.3" rel="Chapter" title="B.3 Example Test ECDSA Signature Generation JSON Object">
<link href="#rfc.appendix.B.4" rel="Chapter" title="B.4 Example Test ECDSA SigVer JSON Object">
<link href="#rfc.authors" rel="Chapter">
<meta name="generator" content="xml2rfc version 2.21.1 - https://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Fussell, B., Ed." />
<meta name="dct.identifier" content="urn:ietf:id:draft-ietf-acvp-subecdsa-1.0" />
<meta name="dct.issued" scheme="ISO8601" content="2016-06-01" />
<meta name="dct.abstract" content="This document defines the JSON schema for using ECDSA algorithms with the ACVP specification." />
<meta name="description" content="This document defines the JSON schema for using ECDSA 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">June 1, 2016</td>
</tr>
<tr>
<td class="left">Expires: December 3, 2016</td>
<td class="right"></td>
</tr>
</tbody>
</table>
<p class="title">ACVP ECDSA Algorithm JSON Specification<br />
<span class="filename">draft-ietf-acvp-subecdsa-1.0</span></p>
<h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
<p>This document defines the JSON schema for using ECDSA 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 December 3, 2016.</p>
<h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
<p>Copyright (c) 2016 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">Supported ECDSA Algorithms</a>
</li>
<li>3. <a href="#rfc.section.3">Test Types and Test Coverage</a>
</li>
<ul><li>3.1. <a href="#rfc.section.3.1">Test Coverage</a>
</li>
<ul><li>3.1.1. <a href="#rfc.section.3.1.1">Requirements Covered</a>
</li>
<li>3.1.2. <a href="#rfc.section.3.1.2">Requirements Not Covered</a>
</li>
</ul></ul><li>4. <a href="#rfc.section.4">Capabilities Registration</a>
</li>
<ul><li>4.1. <a href="#rfc.section.4.1">Required Prerequisite Algorithms for ECDSA Validations</a>
</li>
<li>4.2. <a href="#rfc.section.4.2">ECDSA Algorithm Capabilities Registration</a>
</li>
<li>4.3. <a href="#rfc.section.4.3">Supported ECDSA Modes Capabilities</a>
</li>
<ul><li>4.3.1. <a href="#rfc.section.4.3.1">The keyGen Mode Capabilities</a>
</li>
<ul><li>4.3.1.1. <a href="#rfc.section.4.3.1.1">keyGen Full Set of Capabilities</a>
</li>
</ul><li>4.3.2. <a href="#rfc.section.4.3.2">The keyVer Mode Capabilities</a>
</li>
<ul><li>4.3.2.1. <a href="#rfc.section.4.3.2.1">keyVer Full Set of Capabilities</a>
</li>
</ul><li>4.3.3. <a href="#rfc.section.4.3.3">The sigGen Mode Capabilities</a>
</li>
<ul><li>4.3.3.1. <a href="#rfc.section.4.3.3.1">sigGen Full Set of Capabilities</a>
</li>
</ul><li>4.3.4. <a href="#rfc.section.4.3.4">The sigVer Mode Capabilities</a>
</li>
<ul><li>4.3.4.1. <a href="#rfc.section.4.3.4.1">sigVer Full Set of Capabilities</a>
</li>
</ul></ul></ul><li>5. <a href="#rfc.section.5">Supported DSA Conformances</a>
</li>
<li>6. <a href="#rfc.section.6">Test Vectors</a>
</li>
<ul><li>6.1. <a href="#rfc.section.6.1">Test Groups JSON Schema</a>
</li>
<li>6.2. <a href="#rfc.section.6.2">Test Case JSON Schema</a>
</li>
</ul><li>7. <a href="#rfc.section.7">Test Vector Responses</a>
</li>
<li>8. <a href="#rfc.section.8">Acknowledgements</a>
</li>
<li>9. <a href="#rfc.section.9">IANA Considerations</a>
</li>
<li>10. <a href="#rfc.section.10">Security Considerations</a>
</li>
<li>11. <a href="#rfc.references">Normative References</a>
</li>
<li>Appendix A. <a href="#rfc.appendix.A">Example Capabilities JSON Object</a>
</li>
<li>Appendix B. <a href="#rfc.appendix.B">Example Vector Set Request/Responses JSON Object</a>
</li>
<ul><li>B.1. <a href="#rfc.appendix.B.1">Example Test ECDSA KeyGen JSON Object</a>
</li>
<li>B.2. <a href="#rfc.appendix.B.2">Example Test ECDSA KeyVer JSON Object</a>
</li>
<li>B.3. <a href="#rfc.appendix.B.3">Example Test ECDSA Signature Generation JSON Object</a>
</li>
<li>B.4. <a href="#rfc.appendix.B.4">Example Test ECDSA SigVer JSON Object</a>
</li>
</ul><li><a href="#rfc.authors">Author's Address</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 ECDSA 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="#supported_algs" id="supported_algs">Supported ECDSA Algorithms</a>
</h1>
<p id="rfc.section.2.p.1">The following ECDSA algorithms MAY be advertised by the ACVP compliant cryptographic module:</p>
<p></p>
<ul>
<li>ECDSA / keyGen</li>
<li>ECDSA / keyVer</li>
<li>ECDSA / sigGen</li>
<li>ECDSA / sigVer</li>
</ul>
<p> </p>
<h1 id="rfc.section.3">
<a href="#rfc.section.3">3.</a> <a href="#test_types" id="test_types">Test Types and Test Coverage</a>
</h1>
<p id="rfc.section.3.p.1">The ACVP server performs a set of tests on the specified ECDSA algorithm in order to assess the correctness and robustness of the implementation. A typical ACVP validation session SHALL require multiple tests to be performed for every supported permutation of ECDSA capabilities. This section describes the design of the tests used to validate implementations of the ECDSA algorithms. </p>
<ul class="empty">
<li>ECDSA / keyGen "AFT" - Algorithm Functional Test. The IUT is REQUIRED for each test case provided, to generate a key pair based on an approved curve. This information is then communicated to the ACVP server and validated. </li>
<li>ECDSA / keyVer "AFT" - Algorithm Functional Test. The ACVP server is REQUIRED to generate a series of keys based on the IUT provided NIST curve(s). The keys generated by the server MAY or MAY NOT be valid, the IUT is REQUIRED to determine if the keys provided in the test cases are valid or invalid keys as they relate to the curve. </li>
<li>ECDSA / sigGen "AFT" - Algorithm Functional Test. This testing mode expects the IUT to generate valid signatures based on the ACVP provided message. The signature is then validated with the ACVP server given the IUT's communicated curve, public key, and signature. </li>
<li>ECDSA / sigVer "AFT" - Algorithm Functional Test. The ACVP server generates a series of signatures to communicate to the IUT. The IUT is REQUIRED to determine the validity of the signature given the curve, key, and message. </li>
</ul>
<p> </p>
<h1 id="rfc.section.3.1">
<a href="#rfc.section.3.1">3.1.</a> <a href="#test_coverage" id="test_coverage">Test Coverage</a>
</h1>
<p id="rfc.section.3.1.p.1">The tests described in this document have the intention of ensuring an implementation is conformant to <a href="#FIPS.186-4" class="xref">[FIPS.186-4]</a> and <a href="#SP.800-89" class="xref">[SP.800-89]</a>. </p>
<h1 id="rfc.section.3.1.1">
<a href="#rfc.section.3.1.1">3.1.1.</a> <a href="#requirements_covered" id="requirements_covered">Requirements Covered</a>
</h1>
<p></p>
<ul class="empty">
<li>FIPS.186-4 - 3 General Discussion. Domain parameter generation, key generation, signature generation, and signature validation are all within scope of ACVP server testing. </li>
<li>FIPS.186-4 - 6 The Eliliptic Curve Digital Signature Algorithm (ECDSA). The ACVP server SHALL allow testing with the recommended NIST curves. The ACVP server SHALL support a variety of curves/hash function for creation and delivery to/from the IUT. Key pair generation/verification testing SHALL be provided by the ACVP server. Both Signature Generation and Validation testing mechanmisms SHALL be provided by the ACVP server. </li>
<li>SP800-106 - (3) Randomized Hashing and (4) Digital Signatures Using Randomized Hashing. The IUT SHALL be provided or provide a random value that should be used to "randomize" a message prior to signing and/or verifying an original message. </li>
</ul>
<p> </p>
<h1 id="rfc.section.3.1.2">
<a href="#rfc.section.3.1.2">3.1.2.</a> <a href="#requirements_not_covered" id="requirements_not_covered">Requirements Not Covered</a>
</h1>
<p></p>
<ul class="empty">
<li>FIPS.186-4 - 3 General Discussion. Assurances of private key secrecy and ownership SHALL NOT be within scope of ACVP testing. </li>
<li>FIPS.186-4 - 6 The Eliliptic Curve Digital Signature Algorithm (ECDSA). Though the ACVP server SHALL support a variety of parameter sizes/hash functions, the IUT's selection of these is out of scope of testing. The ACVP server SHALL NOT provide testing for the validity of domain parameters as testing is (currently) limited to approved NIST curves. Testing SHALL NOT provide assurances the IUT has validated a set of domain parameters prior to their use. Domain parameter and key pair management SHALL NOT be within scope of ACVP testing. </li>
<li>SP800-106 - 3.3 The Random Value. DSA, ECDSA, and RSA have random values generated as per their signing process, this random value can be used as the input to the message randomization function, doing so however is out of scope of this testing. </li>
</ul>
<p> </p>
<h1 id="rfc.section.4">
<a href="#rfc.section.4">4.</a> <a href="#caps_reg" id="caps_reg">Capabilities Registration</a>
</h1>
<p id="rfc.section.4.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 ECDSA algorithms to the ACVP server.</p>
<p id="rfc.section.4.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.</p>
<h1 id="rfc.section.4.1">
<a href="#rfc.section.4.1">4.1.</a> <a href="#prereq_algs" id="prereq_algs">Required Prerequisite Algorithms for ECDSA Validations</a>
</h1>
<p id="rfc.section.4.1.p.1">Each ECDSA implementation relies on other cryptographic primitives. For example, ECDSA 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 ECDSA 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">DRBG, DRBG_OPT2, SHA, SHA_OPT2, SHA_OPT3</td>
<td class="left">No</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">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">No</td>
</tr>
<tr>
<td class="left">prereqVals</td>
<td class="left">prerequistie algorithm validations</td>
<td class="left">array of prereqAlgVal objects</td>
<td class="left">see above</td>
<td class="left">No</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.4.2">
<a href="#rfc.section.4.2">4.2.</a> <a href="#ecdsa_caps_reg" id="ecdsa_caps_reg">ECDSA Algorithm Capabilities Registration</a>
</h1>
<p id="rfc.section.4.2.p.1">Each algorithm capability advertised is a self-contained JSON object using the following values</p>
<div id="rfc.table.2"></div>
<div id="caps_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>ECDSA Algorithm 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">"ECDSA"</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">mode</td>
<td class="left">The ECDSA mode to be validated</td>
<td class="left">value</td>
<td class="left">"keyGen", "keyVer", "sigGen", or "sigVer"</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">revision</td>
<td class="left">The algorithm testing revision to use.</td>
<td class="left">value</td>
<td class="left">"1.0"</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">prereqVals</td>
<td class="left">prerequistie algorithm validations</td>
<td class="left">array of prereqAlgVal objects</td>
<td class="left">See <a href="#prereq_algs" class="xref">Section 4.1</a> </td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">capabilities</td>
<td class="left">array of JSON objects, each with fields pertaining to the global ECDSA mode indicated above and identified uniquely by the combination of the ECDSA "mode" and indicated properties</td>
<td class="left">Array of JSON objects</td>
<td class="left">See <a href="#supported_modes" class="xref">Section 4.3</a> </td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">conformances</td>
<td class="left">Used to denote the conformances that can apply to specific modes of DSA.</td>
<td class="left">Array of strings</td>
<td class="left">See <a href="#supported_conformances" class="xref">Section 5</a> </td>
<td class="left">Yes</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.4.3">
<a href="#rfc.section.4.3">4.3.</a> <a href="#supported_modes" id="supported_modes">Supported ECDSA Modes Capabilities</a>
</h1>
<p id="rfc.section.4.3.p.1">The ECDSA mode capabilities are advertised as JSON objects within the 'capabilities' value of the ACVP registration message - see <a href="#caps_table" class="xref">Table 2</a> . The 'capabilities' value is an array, where each array element is a JSON object corresponding to a particular ECDSA mode defined in this section. The 'capabilities' value is part of the 'capability_exchange' element of the ACVP JSON registration message. See the ACVP specification for details on the registration message. </p>
<p id="rfc.section.4.3.p.2">Each ECDSA mode's capabilities are advertised as JSON objects.</p>
<h1 id="rfc.section.4.3.1">
<a href="#rfc.section.4.3.1">4.3.1.</a> <a href="#mode_keyGen" id="mode_keyGen">The keyGen Mode Capabilities</a>
</h1>
<p id="rfc.section.4.3.1.p.1">The ECDSA keyGen mode capabilities are advertised as JSON objects, which are elements of the 'capabilities' array in the ACVP registration message. See the ACVP specification for details on the registration message.</p>
<p id="rfc.section.4.3.1.p.2">Each ECDSA keyGen mode capability set is advertised as a self-contained JSON object.</p>
<h1 id="rfc.section.4.3.1.1">
<a href="#rfc.section.4.3.1.1">4.3.1.1.</a> <a href="#mode_keyGenFullSet" id="mode_keyGenFullSet">keyGen Full Set of Capabilities</a>
</h1>
<p id="rfc.section.4.3.1.1.p.1">The complete list of ECDSA key generation capabilities may be advertised by the ACVP compliant crypto module:</p>
<div id="rfc.table.3"></div>
<div id="keyGen_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>ECDSA keyGen 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">curve</td>
<td class="left">The curve names supported for the IUT in keyGen.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"P-224", "P-256", "P-384", "P-521", "B-233", "B-283", "B-409", "B-571", "K-233", "K-283", "K-409", "K-571"}</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">secretGenerationMode</td>
<td class="left">The method used to generate the randomness incoporated in the key.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"extra bits", "testing candidates"}</td>
<td class="left">No</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.4.3.2">
<a href="#rfc.section.4.3.2">4.3.2.</a> <a href="#mode_keyVer" id="mode_keyVer">The keyVer Mode Capabilities</a>
</h1>
<p id="rfc.section.4.3.2.p.1">The ECDSA keyVer mode capabilities are advertised as JSON objects, which are elements of the 'capabilities' array in the ACVP registration message. See the ACVP specification for details on the registration message.</p>
<p id="rfc.section.4.3.2.p.2">Each ECDSA keyVer mode capability set is advertised as a self-contained JSON object.</p>
<h1 id="rfc.section.4.3.2.1">
<a href="#rfc.section.4.3.2.1">4.3.2.1.</a> <a href="#mode_keyVerFullSet" id="mode_keyVerFullSet">keyVer Full Set of Capabilities</a>
</h1>
<p id="rfc.section.4.3.2.1.p.1">The complete list of ECDSA key verification capabilities may be advertised by the ACVP compliant crypto module:</p>
<div id="rfc.table.4"></div>
<div id="keyVer_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>ECDSA keyVer 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">curve</td>
<td class="left">The curve names supported for the IUT in keyVer.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"P-192", "P-224", "P-256", "P-384", "P-521", "B-163", "B-233", "B-283", "B-409", "B-571", "K-163", "K-233", "K-283", "K-409", "K-571"}</td>
<td class="left">No</td>
</tr></tbody>
</table>
<h1 id="rfc.section.4.3.3">
<a href="#rfc.section.4.3.3">4.3.3.</a> <a href="#mode_sigGen" id="mode_sigGen">The sigGen Mode Capabilities</a>
</h1>
<p id="rfc.section.4.3.3.p.1">The ECDSA sigGen mode capabilities are advertised as JSON objects, which are elements of the 'capabilities' array in the ACVP registration message. See the ACVP specification for details on the registration message.</p>
<p id="rfc.section.4.3.3.p.2">Each ECDSA sigGen mode capability set is advertised as a self-contained JSON object.</p>
<h1 id="rfc.section.4.3.3.1">
<a href="#rfc.section.4.3.3.1">4.3.3.1.</a> <a href="#mode_sigGenFullSet" id="mode_sigGenFullSet">sigGen Full Set of Capabilities</a>
</h1>
<p id="rfc.section.4.3.3.1.p.1">The complete list of ECDSA signature generation capabilities may be advertised by the ACVP compliant crypto module:</p>
<div id="rfc.table.5"></div>
<div id="sigGen_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>ECDSA sigGen 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">capabilities</td>
<td class="left">An array containing capability objects defined as an array of 'curve' and an array of 'hashAlg' as listed below.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of capability objects</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">curve</td>
<td class="left">The curves supported with a particular set of hash algorithms.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"P-224", "P-256", "P-384", "P-521", "B-233", "B-283", "B-409", "B-571", "K-233", "K-283", "K-409", "K-571"}</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">hashAlg</td>
<td class="left">The hash functions supported when signing a message for a particular set of curves.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"SHA2-224", "SHA2-256", "SHA2-384", "SHA2-512", "SHA2-512/224", "SHA2-512/256"}.</td>
<td class="left">No</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.4.3.4">
<a href="#rfc.section.4.3.4">4.3.4.</a> <a href="#mode_sigVer" id="mode_sigVer">The sigVer Mode Capabilities</a>
</h1>
<p id="rfc.section.4.3.4.p.1">The ECDSA sigVer mode capabilities are advertised as JSON objects, which are elements of the 'capabilities' array in the ACVP registration message. See the ACVP specification for details on the registration message.</p>
<p id="rfc.section.4.3.4.p.2">Each ECDSA sigVer mode capability set is advertised as a self-contained JSON object.</p>
<h1 id="rfc.section.4.3.4.1">
<a href="#rfc.section.4.3.4.1">4.3.4.1.</a> <a href="#mode_sigVerFullSet" id="mode_sigVerFullSet">sigVer Full Set of Capabilities</a>
</h1>
<p id="rfc.section.4.3.4.1.p.1">The complete list of ECDSA signature verification capabilities may be advertised by the ACVP compliant crypto module:</p>
<div id="rfc.table.6"></div>
<div id="sigVer_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>ECDSA sigVer 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">capabilities</td>
<td class="left">An array containing capability objects defined as an array of 'curve' and an array of 'hashAlg' as listed below.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of capability objects</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">curve</td>
<td class="left">The curves supported with a particular set of hash algorithms.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"P-192", "P-224", "P-256", "P-384", "P-521", "B-163", "B-233", "B-283", "B-409", "B-571", "K-163", "K-233", "K-283", "K-409", "K-571"}</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">hashAlg</td>
<td class="left">The hash functions supported when signing a message for a particular set of curves.</td>
<td class="left">array</td>
<td class="left">Any non-empty subset of {"SHA-1", "SHA2-224", "SHA2-256", "SHA2-384", "SHA2-512", "SHA2-512/224", "SHA2-512/256"}.</td>
<td class="left">No</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.5">
<a href="#rfc.section.5">5.</a> <a href="#supported_conformances" id="supported_conformances">Supported DSA Conformances</a>
</h1>
<p id="rfc.section.5.p.1">Conformances MAY be used to test additional features of certain algorithms.</p>
<div id="rfc.table.7"></div>
<div id="conformances_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>DSA Conformances</caption>
<thead><tr>
<th class="left">String Value</th>
<th class="left">Description</th>
<th class="left">Valid algorithm modes</th>
<th class="left">Optional</th>
</tr></thead>
<tbody><tr>
<td class="left">SP800-106</td>
<td class="left">This conformance signifies the SigGen and/or SigVer modes support randomized message hashing as described in <a href="#SP.800-106" class="xref">[SP.800-106]</a>. Utilizing this conformance SHALL generate additional test groups, denoted with a group level property of `"conformance": "SP800-106"`.</td>
<td class="left">SigGen, SigVer</td>
<td class="left">Yes</td>
</tr></tbody>
</table>
<h1 id="rfc.section.6">
<a href="#rfc.section.6">6.</a> <a href="#test_vectors" id="test_vectors">Test Vectors</a>
</h1>
<p id="rfc.section.6.p.1">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 ECDSA function. This section describes the JSON schema for a test vector set used with ECDSA algorithms.</p>
<p id="rfc.section.6.p.2">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.</p>
<div id="rfc.table.8"></div>
<div id="vs_top_table"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>Vector Set JSON Object</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
</tr></thead>
<tbody>
<tr>
<td class="left">acvVersion</td>
<td class="left">Protocol version identifier</td>
<td class="left">value</td>
</tr>
<tr>
<td class="left">vsId</td>
<td class="left">Unique numeric identifier for the vector set</td>
<td class="left">value</td>
</tr>
<tr>
<td class="left">algorithm</td>
<td class="left">ECDSA</td>
<td class="left">value</td>
</tr>
<tr>
<td class="left">mode</td>
<td class="left">The ECDSA mode used for the test vectors</td>
<td class="left">value</td>
</tr>
<tr>
<td class="left">revision</td>
<td class="left">The algorithm testing revision to use.</td>
<td class="left">value</td>
</tr>
<tr>
<td class="left">testGroups</td>
<td class="left">Array of test group JSON objects, which are defined in <a href="#tgjs" class="xref">Section 6.1</a> </td>
<td class="left">array</td>
</tr>
</tbody>
</table>
<h1 id="rfc.section.6.1">
<a href="#rfc.section.6.1">6.1.</a> <a href="#tgjs" id="tgjs">Test Groups JSON Schema</a>
</h1>
<p id="rfc.section.6.1.p.1">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.</p>
<p id="rfc.section.6.1.p.2">The test group for ECDSA is as follows:</p>
<div id="rfc.table.9"></div>
<div id="vs_tg_table5"></div>
<table cellpadding="3" cellspacing="0" class="tt full center">
<caption>Vector Group JSON Object</caption>
<thead><tr>
<th class="left">JSON Value</th>
<th class="left">Description</th>
<th class="left">JSON type</th>
<th class="left">Optional</th>
</tr></thead>
<tbody>
<tr>
<td class="left">curve</td>
<td class="left">The curve type used for the test vectors.</td>
<td class="left">value</td>
<td class="left">No</td>
</tr>
<tr>
<td class="left">secretGenerationMode</td>
<td class="left">The method of generating a secret used for key generation in the test vectors.</td>
<td class="left">value</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">hashAlg</td>
<td class="left">SHA version used</td>
<td class="left">value</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">qx</td>
<td class="left">The public key curve point x</td>
<td class="left">value</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">qy</td>
<td class="left">The public key curve point y</td>
<td class="left">value</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">conformance</td>
<td class="left">Signifies all test cases within the group should utilize random message hashing as described in <a href="#SP.800-106" class="xref">[SP.800-106]</a>.</td>
<td class="left">"SP800-106"</td>
<td class="left">Yes</td>
</tr>
<tr>
<td class="left">tests</td>
<td class="left">Array of individual test vector JSON objects, which are defined in <a href="#tvjs" class="xref">Section 6.2</a> </td>
<td class="left">array</td>
<td class="left">No</td>
</tr>
</tbody>