The ACVP JSON spec for symmetric block ciphers omits a few details needed to carry out CCM-ECMA algorithm validation. It required experimentation to deduce and to be confident in the following:
1: Table 7 could be updated to offer a row dedicated to CCM-ECMA, and that can be used to indicate that ivLen is always 0 for CCM-ECMA (unlike CCM, where ivLen=0 is invalid).
2: A sentence could be added (perhaps after Table 7) indicating that for CCM-ECMA, the IV attribute is used to convey a pre-formatted "B_0 block" containing 16 bytes as defined by Fig 113 in ECMA-368 Sec 18.5.
The ACVP JSON spec already contains a reference to ECMA-368, so it shouldn't take many words to add these details.
The ACVP JSON spec for symmetric block ciphers omits a few details needed to carry out CCM-ECMA algorithm validation. It required experimentation to deduce and to be confident in the following:
1: Table 7 could be updated to offer a row dedicated to CCM-ECMA, and that can be used to indicate that ivLen is always 0 for CCM-ECMA (unlike CCM, where ivLen=0 is invalid).
2: A sentence could be added (perhaps after Table 7) indicating that for CCM-ECMA, the IV attribute is used to convey a pre-formatted "B_0 block" containing 16 bytes as defined by Fig 113 in ECMA-368 Sec 18.5.
The ACVP JSON spec already contains a reference to ECMA-368, so it shouldn't take many words to add these details.