forked from usnistgov/ACVP
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathacvp_sub_kas_ffc.xml
4008 lines (4001 loc) · 170 KB
/
acvp_sub_kas_ffc.xml
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
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-ietf-acvp-subkasffc-1.0" ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="Sym Alg JSON">ACVP KAS FFC JSON Specification</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Barry Fussell" initials="B.F." role="editor" surname="Fussell">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>170 West Tasman Dr.</street>
<!-- Reorder these if your country does things differently -->
<city>San Jose</city>
<region>CA</region>
<code>95134</code>
<country>USA</country>
</postal>
<email>[email protected]</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Russell Hammett" initials="R.H." role="editor" surname="Hammett">
<organization>G2, Inc.</organization>
<address>
<postal>
<street>302 Sentinel Dr Suite 300</street>
<!-- Reorder these if your country does things differently -->
<city>Annapolis Junction </city>
<region>MD</region>
<code>20701</code>
<country>USA</country>
</postal>
<email>[email protected]</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<date month="September" year="2018"/>
<!-- If the month and year are both specified and are the current ones, xml2rfc will fill
in the current day for you. If only the current year is specified, xml2rfc will fill
in the current day and month for you. If the year is not the current one, it is
necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally sufficient to
specify just the year. -->
<!-- Meta-data Declarations -->
<area>General</area>
<workgroup>TBD</workgroup>
<!-- WG name at the upperleft corner of the doc,
IETF is fine for individual submissions.
If this element is not present, the default is "Network Working Group",
which is used by the RFC Editor as a nod to the history of the IETF. -->
<keyword>acvp</keyword>
<keyword>crypto</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>This document defines the JSON schema for using KAS FFC algorithms with the ACVP
specification.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>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.</t>
<section title="Requirements Language">
<t>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 <xref target="RFC2119">RFC 2119</xref>. </t>
</section>
</section>
<section anchor="test_types" title="Test Types and Test Coverage">
<t>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: <list
style="testtype">
<t>"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.</t>
<t>"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.</t>
</list>
</t>
<section anchor="test_coverage" title="Test Coverage">
<t>The tests described in this document have the intention of ensuring an
implementation is conformant to <xref target="SP800-56a"/>. </t>
<section anchor="requirements_covered_kas_ecc" title="KAS-ECC Requirements Covered">
<t>
<list>
<t>SP 800-56a - 4.1 Key Establishment Preparations. The ACVP server is
responsible for generating domain parameters as per the IUT's
capability registration.</t>
<t>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.</t>
<t>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).</t>
<t>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.</t>
<t>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.</t>
<t>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.</t>
<t>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:
<xref target="supported_functions"/>
</t>
<t>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.</t>
<t>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 <xref target="oiPatternConstruction"/> for its
pattern. </t>
<t>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).</t>
<t>SP 800-56a - 6 Key Agreement Schemes. All schemes specified in
referenced document are supported for validation with the ACVP
server.</t>
</list>
</t>
</section>
<section anchor="requirements_not_covered_kas_ecc"
title="KAS-ECC Requirements Not Covered">
<t>
<list>
<t>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.</t>
<t>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. </t>
<t>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</t>
<t>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.</t>
<t>SP 800-56a - 5.5.3 Domain Parameter Management. Domain Parameter
Management SHALL NOT be in scope for KAS testing.</t>
<t>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.</t>
<t>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.</t>
<t>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.</t>
<t>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.</t>
<t>SP 800-56a - 8 Key Recovery. Key Recovery SHALL NOT be in scope of KAS
testing.</t>
</list>
</t>
</section>
</section>
</section>
<section anchor="caps_reg" title="Capabilities Registration">
<t>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.</t>
<t>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.</t>
<section anchor="prereq_algs"
title="Required Prerequisite Algorithms for KAS FFC Validations">
<t>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:</t>
<texttable anchor="rereqs_table"
title="Required Prerequisite Algorithms JSON Values">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>algorithm</c>
<c>a prerequisite algorithm</c>
<c>value</c>
<c>CCM, CMAC, DRBG, DSA, HMAC, SHA</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>valValue</c>
<c>algorithm validation number</c>
<c>value</c>
<c>actual number or "same"</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>prereqAlgVal</c>
<c>prerequistie algorithm validation</c>
<c>object with algorithm and valValue properties</c>
<c>see above</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
<t>KAS has conditional prerequisite algorithms, depending on the capabilities
registered:</t>
<texttable anchor="prereqs_requirements_table"
title="Prerequisite requirement conditions">
<ttcol align="left">Prerequisite Algorithm</ttcol>
<ttcol align="left">Condition</ttcol>
<c>DRBG</c>
<c>Always REQUIRED</c>
<c/>
<c/>
<c>SHA</c>
<c>Always REQUIRED</c>
<c/>
<c/>
<c>DSA</c>
<c> 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". </c>
<c/>
<c/>
<c>AES-CCM</c>
<c>AES-CCM validation REQUIRED when IUT is performing KeyConfirmation (KC) and
utilizing AES-CCM.</c>
<c/>
<c/>
<c>CMAC</c>
<c>CMAC validation REQUIRED when IUT is performing KeyConfirmation (KC) and
utilizing CMAC.</c>
<c/>
<c/>
<c>HMAC</c>
<c>HMAC validation REQUIRED when IUT is performing KeyConfirmation (KC) and
utilizing HMAC.</c>
<c/>
<c/>
</texttable>
</section>
<section anchor="cap_ex" title="KAS FFC Algorithm Capabilities JSON Values">
<t>Each algorithm capability advertised is a self-contained JSON object using the
following values.</t>
<texttable anchor="caps_table" title="KAS FFC Capabilities JSON Values">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>algorithm</c>
<c>The algorithm under test</c>
<c>value</c>
<c>KAS-FFC</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>mode</c>
<c>The algorithm mode.</c>
<c>value</c>
<c>Component</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>revision</c>
<c>The algorithm testing revision to use.</c>
<c>value</c>
<c>"1.0"</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>prereqVals</c>
<c>Prerequisite algorithm validations</c>
<c>array of prereqAlgVal objects</c>
<c>See <xref target="prereq_algs"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>function</c>
<c>Type of function supported</c>
<c>array</c>
<c>See <xref target="supported_functions"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>scheme</c>
<c>Array of supported key agreement schemes each having their own
capabilities</c>
<c>object</c>
<c>See <xref target="supported_schemes"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
<t>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.</t>
</section>
<section anchor="supported_functions" title="Supported KAS FFC Functions">
<t>The following function types MAY be advertised by the ACVP compliant crypto
module:</t>
<t>
<list style="symbols">
<t>dpGen - IUT can perform domain parameter generation (FFC only)</t>
<t>dpVal - IUT can perform domain parameter validation (FFC only)</t>
<t>keyPairGen - IUT can perform keypair generation.</t>
<t>fullVal - IUT can perform full public key validation ( <xref
target="SP800-56a"/> section 5.6.2.3.1 / 5.6.2.3.3) </t>
<t>partialVal - IUT can perform partial public key validation ( <xref
target="SP800-56a"/> section 5.6.2.3.2 / 5.6.2.3.4) </t>
<t>keyRegen - IUT can regenerate keys given a specific seed and domain
parameter (pqg for FFC, curve for ECC)</t>
</list>
</t>
</section>
<section anchor="schemes" title="KAS FFC Schemes">
<section anchor="supported_schemes" title="KAS FFC Scheme Capabilities JSON Values">
<t> 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 <xref
target="supported_scheme_values"/> for allowed FFC scheme types. </t>
<texttable anchor="scheme_caps_table" title="KAS FFC Capabilities JSON Values">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>kasRole</c>
<c>Roles supported for key agreement</c>
<c>array</c>
<c>initiator and/or responder</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>noKdfNoKc</c>
<c>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"</c>
<c>object</c>
<c>
<xref target="noKdfNoKc"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>kdfNoKc</c>
<c>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)</c>
<c>object</c>
<c>
<xref target="kdfNoKc"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>kdfKc</c>
<c>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)</c>
<c>object</c>
<c>
<xref target="kdfKc"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="supported_scheme_values" title="Supported KAS FFC Schemes">
<t>The following schemes MAY be advertised by the ACVP compliant crypto
module:</t>
<t>
<list style="symbols">
<t>dhHybrid1</t>
<t>MQV2</t>
<t>dhEphem - KeyConfirmation not supported.</t>
<t>dhHybridOneFlow</t>
<t>MQV1</t>
<t>dhOneFlow - Can only provide unilateral key confirmation party V to
party U.</t>
<t>dhStatic - requires dkmNonceTypes</t>
</list>
</t>
</section>
</section>
<section anchor="kasMode" title="KAS FFC Modes">
<section anchor="noKdfNoKc" title="KAS FFC noKdfNoKc">
<t>Contains properties REQUIRED for "noKdfNoKc" registration. </t>
<texttable anchor="noKdfNoKc_table" title="NoKdfNoKc Capabilities">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>parameterSet</c>
<c>The parameterSet options for "noKdfNoKc"</c>
<c>object</c>
<c>
<xref target="parameter_set"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="kdfNoKc" title="KAS FFC kdfNoKc">
<t>Contains properties REQUIRED for "kdfNoKc" registration. </t>
<texttable anchor="kdfNoKc_table" title="kdfNoKc Capabilities">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>kdfOption</c>
<c>The kdf options for "kdfNoKc"</c>
<c>object</c>
<c>
<xref target="supported_kdfOption"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>parameterSet</c>
<c>The parameterSet options for "kdfNoKc"</c>
<c>object</c>
<c>
<xref target="parameter_set"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>dkmNonceTypes</c>
<c>The nonce type(s) the IUT is to use for deriving keying material. Required for DhStatic scheme.</c>
<c>array</c>
<c>
randomNonce, timestamp, sequence, timestampSequence
</c>
<c>Yes - required for DhStatic scheme</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="kdfKc" title="KAS FFC kdfKc">
<t>Contains properties REQUIRED for "kdfKc" registration. </t>
<texttable anchor="kdfKc_table" title="kdfKc Capabilities">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>kdfOption</c>
<c>The kdf options for "kdfNoKc"</c>
<c>object</c>
<c>
<xref target="supported_kdfOption"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>kcOption</c>
<c>The kc options for "kdfNoKc"</c>
<c>object</c>
<c>
<xref target="supported_kcOption"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>parameterSet</c>
<c>The parameterSet options for "kdfNoKc"</c>
<c>object</c>
<c>
<xref target="parameter_set"/>
</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
</section>
<section anchor="parameterSet" title="Parameter Sets">
<section anchor="parameter_set" title="KAS FFC Parameter Set">
<t>Each parameter set advertised is a self-contained JSON object using the
following values. Note that at least one parameter set ("fb", "fc") MUST be provided.</t>
<texttable anchor="parameter_set_table"
title="KAS FFC Parameter Set Capabilities JSON Values">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>fb</c>
<c>The fb parameter set</c>
<c>object</c>
<c>See <xref target="parameter_set_details"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>fc</c>
<c>The fc parameter set</c>
<c>object</c>
<c>See <xref target="parameter_set_details"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="parameter_set_details" title="KAS FFC Parameter Set Details">
<t>fb/fc changes minimum allowed values on options.</t>
<t>fb: Len p - 2048, Len q - 224, min hash len - 224, min keySize - 112, min
macSize - 64</t>
<t>fc: Len p - 2048, Len q - 256, min hash len - 256, min keySize - 128, min
macSize - 64</t>
<t>"noKdfNoKc" REQUIRES "hashAlg"</t>
<t>"kdfNoKc" REQUIRES "hashAlg" and at least one valid MAC registration</t>
<t>"kdfKc" REQUIRES "hashAlg" and at least one valid MAC registration</t>
<texttable anchor="parameter_set_details_table"
title="KAS FFC Parameter Set Details Capabilities JSON Values">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>hashAlg</c>
<c>The hash algorithms to use for DSA (and noKdfNoKc)</c>
<c>array</c>
<c>See <xref target="supported_hashAlg"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>macOption</c>
<c>The macOption(s) to use with "kdfNoKc" and/or "kdfKc"</c>
<c>object</c>
<c>See <xref target="supported_macOption"/>
</c>
<c>Yes</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
</section>
<section anchor="supported_hashAlg" title="Supported Hash Algorithm Methods">
<t>The following SHA methods MAY be advertised by the ACVP compliant crypto
module:</t>
<t>
<list style="symbols">
<t>SHA2-224</t>
<t>SHA2-256</t>
<t>SHA2-384</t>
<t>SHA2-512</t>
</list>
</t>
</section>
<section anchor="supported_macOption" title="Supported KAS FFC MAC Options">
<t>The following MAC options MAY be advertised for registration under a "kdfNoKc" and
"kdfKc" kasMode:</t>
<t>
<list style="symbols">
<t>AES-CCM</t>
<t>CMAC</t>
<t>HMAC-SHA2-224</t>
<t>HMAC-SHA2-256</t>
<t>HMAC-SHA2-384</t>
<t>HMAC-SHA2-512</t>
</list>
</t>
<texttable anchor="macOption_details_table" title="KAS FFC Mac Option Details">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>keyLen</c>
<c>The supported keyLens for the selected MAC.</c>
<c>Domain</c>
<c> AES based MACs limited to 128, 192, 256. HashAlg based MACs mod 8. All
keySizes minimum MUST conform to parameter set requirements See <xref
target="parameter_set_details"/> . </c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>nonceLen</c>
<c>The nonce len for use with AES-CCM mac</c>
<c>value</c>
<c>Input as bits, 56-104, odd byte values only (7-13). Additionally minimum MUST
conform to parameter set requirements See <xref
target="parameter_set_details"/> . </c>
<c>Yes (REQUIRED for AES-CCM)</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>macLen</c>
<c>The mac len for use with mac</c>
<c>value</c>
<c>Input as bits, mod 8, minimum MUST conform to parameter set requirements See
<xref target="parameter_set_details"/> , maximum MAY NOT exceed block
size.. </c>
<c>Yes (REQUIRED for AES-CCM)</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="supported_kdfOption" title="Supported KAS FFC KDF Options">
<t>The following MAC options are available for registration under a "kdfNoKc" and
"kdfKc" kasMode:</t>
<t>
<list style="symbols">
<t>concatenation</t>
<t>asn1</t>
</list>
</t>
<texttable anchor="kdfOption_details_table" title="KAS FFC KDF Option Details">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>oiPattern</c>
<c>The OI pattern to use for constructing OtherInformation.</c>
<c>value</c>
<c>See <xref target="oiPatternConstruction"/> . </c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
<section anchor="oiPatternConstruction" title="Other Information Construction">
<t> Some IUTs MAY require a specific pattern for the OtherInfo portion of the KDFs
for KAS. An "oiPattern" is specified in the KDF registration to accommodate
such requirements. Regardless of the oiPattern specified, the OI bitlength
MUST be 240 for FFC, and 376 for ECC. The OI will be padded with random bits
(or the most significant bits utilized) when the specified OI pattern does
not meet the bitlength requirement </t>
<t>Pattern candidates:</t>
<t>
<list style="symbols">
<t>literal[123456789ABCDEF] <list style="symbols">
<t>uses the specified hex within "[]". literal[123456789ABCDEF]
substitutes "123456789ABCDEF" in place of the field</t>
</list>
</t>
<t>uPartyInfo <list style="symbols">
<t>uPartyId { || dkmNonce } <list style="symbols">
<t>dkmNonce is provided by party u for static
schemes</t>
</list>
</t>
</list>
</t>
<t>vPartyInfo <list style="symbols">
<t>vPartyId</t>
</list>
</t>
<t>counter <list style="symbols">
<t>32bit counter starting at "1" (0x00000001)</t>
</list>
</t>
</list>
</t>
<t>Example (Note that party U is the server in this case "434156536964", party V
is the IUT "a1b2c3d4e5", using an FFC non-static scheme):</t>
<t>
<list style="symbols">
<t>"concatenation" :
"literal[123456789CAFECAFE]||uPartyInfo||vPartyInfo"</t>
</list>
</t>
<t>Evaluated as:</t>
<t>
<list style="symbols">
<t>"123456789CAFECAFE434156536964a1b2c3d4e5b16c5f78ef56e8c14a561"</t>
<t>"b16c5f78ef56e8c14a561" are random bits applied to meet length
requirements</t>
</list>
</t>
</section>
</section>
<section anchor="supported_kcOption" title="Supported KAS FFC KC Options">
<t>The following KC options are available for registration under a "kdfKc"
kasMode:</t>
<texttable anchor="kcOption_details_table"
title="KAS FFC KC Option Details Capabilities">
<ttcol align="left">JSON Value</ttcol>
<ttcol align="left">Description</ttcol>
<ttcol align="left">JSON type</ttcol>
<ttcol align="left">Valid Values</ttcol>
<ttcol align="left">Optional</ttcol>
<c>kcRole</c>
<c>The role(s) the IUT is to act as for KeyConfirmation.</c>
<c>array</c>
<c>provider/recipient</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>kcType</c>
<c>The type(s) the IUT is to act as for KeyConfirmation.</c>
<c>array</c>
<c>unilateral/bilateral</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
<c>nonceType</c>
<c>The nonce type(s) the IUT is to use for KeyConfirmation.</c>
<c>array</c>
<c>randomNonce, timestamp, sequence, timestampSequence</c>
<c>No</c>
<c/>
<c/>
<c/>
<c/>
<c/>
</texttable>
</section>
<section anchor="app-reg-ex" title="Example KAS FFC Capabilities JSON Object">
<t>The following is a example JSON object advertising support for KAS FFC.</t>
<figure>
<artwork>
<![CDATA[
{
"algorithm": "KAS-FFC",
"revision": "1.0",
"prereqVals": [{
"algorithm": "DSA",
"valValue": "123456"
},
{
"algorithm": "DRBG",
"valValue": "123456"
},
{
"algorithm": "SHA",
"valValue": "123456"
},
{
"algorithm": "CCM",
"valValue": "123456"
},
{
"algorithm": "CMAC",
"valValue": "123456"
},
{
"algorithm": "HMAC",
"valValue": "123456"
}
],
"function": ["keyPairGen", "dpGen"],
"scheme": {
"dhEphem": {
"kasRole": ["initiator", "responder"],
"kdfNoKc": {
"kdfOption": {
"concatenation": "uPartyInfo||vPartyInfo",
"ASN1": "uPartyInfo||vPartyInfo"
},
"parameterSet": {
"fc": {
"hashAlg": ["SHA2-224", "SHA2-256"],
"macOption": {
"AES-CCM": {
"keyLen": [128],
"nonceLen": 56,
"macLen": 64
}
}
}
}
}
},
"mqv1": {
"kasRole": ["initiator", "responder"],
"kdfNoKc": {
"kdfOption": {
"concatenation": "uPartyInfo||vPartyInfo",
"ASN1": "uPartyInfo||vPartyInfo"
},
"parameterSet": {
"fc": {
"hashAlg": ["SHA2-224", "SHA2-256"],
"macOption": {
"AES-CCM": {
"keyLen": [128],
"nonceLen": 56,
"macLen": 64
}
}
}
}
},
"kdfKc": {
"KcOption": {
"KcRole": [
"provider",
"recipient"
],
"KcType": [
"unilateral",
"bilateral"
],
"NonceType": [
"randomNonce"
]
},
"kdfOption": {
"concatenation": "uPartyInfo||vPartyInfo",
"ASN1": "uPartyInfo||vPartyInfo"
},
"parameterSet": {
"fb": {
"hashAlg": ["SHA2-224"],
"macOption": {
"AES-CCM": {
"keyLen": [128],
"nonceLen": 56,
"macLen": 64
}
}
},
"fc": {
"hashAlg": ["SHA2-256"],
"macOption": {
"AES-CCM": {
"keyLen": [128],
"nonceLen": 56,
"macLen": 64
}
}
}