Skip to content

Commit

Permalink
uPartyInfo and vPartyInfo are not required for KTS
Browse files Browse the repository at this point in the history
  • Loading branch information
jvdsn authored Aug 9, 2024
1 parent 3fee827 commit f4fe722
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/kas/sp800-56br2/sections/05-capabilities.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -238,7 +238,7 @@ Note that this method is *REQUIRED* when testing KTS schemes.
[[fixedinfopatcon]]
===== FixedInfoPatternConstruction

IUTs *MUST* be capable of specifying how the FixedInfo is constructed for the KAS/KTS negotiation. Note that for the purposes of testing against the ACVP system, both uPartyInfo and vPartyInfo are *REQUIRED* to be registered within the fixed info pattern.
IUTs *MUST* be capable of specifying how the FixedInfo is constructed for the KAS/KTS negotiation. Note that for the purposes of testing a KAS against the ACVP system, both uPartyInfo and vPartyInfo are *REQUIRED* to be registered within the fixed info pattern.

Pattern candidates:

Expand All @@ -250,7 +250,7 @@ substitutes "0123456789ABCDEF" in place of the field
* uPartyInfo
** uPartyId { || ephemeralKey } { || ephemeralNonce } { || dkmNonce }
*** "optional" items such as ephemeralKey *MUST* be included when available for ACVP testing.
*** For the purposes of the testing defined in this specification, the uPartyInfo value
*** For the purposes of the testing a KAS defined in this specification, the uPartyInfo value
used to create the fixedInfo that is input to the key derivation function *SHALL* take the form of "uPartyId { || ephemeralKey }
{ || ephemeralNonce } { || dkmNonce }".
*** Whether or not an "optional" item, e.g., ephemeralKey, will be included as part of the uPartyInfo
Expand All @@ -259,7 +259,7 @@ substitutes "0123456789ABCDEF" in place of the field
* vPartyInfo
** vPartyId { || ephemeralKey } { || ephemeralNonce } { || dkmNonce }
*** "optional" items such as ephemeralKey *MUST* be included when available for ACVP testing.
*** For the purposes of the testing defined in this specification, the vPartyInfo value
*** For the purposes of the testing a KAS defined in this specification, the vPartyInfo value
used to create the fixedInfo that is input to the key derivation function *SHALL* take the form of "vPartyId { || ephemeralKey }
{ || ephemeralNonce } { || dkmNonce }".
*** Whether or not an "optional" item, e.g., ephemeralKey, will be included as part of the vPartyInfo
Expand Down

0 comments on commit f4fe722

Please sign in to comment.