From: Brandon Lo <blo@iol.unh.edu>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>, dev <dev@dpdk.org>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] Question Regarding FIPS Validation in DPDK
Date: Fri, 3 Dec 2021 13:44:59 -0500 [thread overview]
Message-ID: <CAOeXdvZ8PopYN=w-C5ZW8dMQoz7jHLAKwK+6Sp0sLRZLHL2VnQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB32272A72FB1250EF6C3BAABAFC699@DM6PR11MB3227.namprd11.prod.outlook.com>
On Thu, Dec 2, 2021 at 9:45 AM Mcnamara, John <john.mcnamara@intel.com> wrote:
> > At the time the dpdk-fips_validation tool was written the test vectors
> > weren't available in JSON format, and, to the best of my knowledge, there
> > was a format specification (which is why there is different parsing for
> > different algorithms). We (the community) should probably move to the JSON
> > format. Adding Fan Zhang since I think this was discussion in the
> > community previously.
>
> Sorry I meant to say " to the best of my knowledge, there *wasn't* a format specification" available.
>
> John
Should we plan to move away from the old format to only use the new
JSON format going forward? I believe the file format "CAVS 21.0" is
fully deprecated and NIST does not produce any new files in that
format.
Thanks,
Brandon
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu
next prev parent reply other threads:[~2021-12-03 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 17:44 Brandon Lo
2021-12-02 8:44 ` Mcnamara, John
2021-12-02 14:45 ` Mcnamara, John
2021-12-03 18:44 ` Brandon Lo [this message]
2021-12-06 8:49 ` Mcnamara, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOeXdvZ8PopYN=w-C5ZW8dMQoz7jHLAKwK+6Sp0sLRZLHL2VnQ@mail.gmail.com' \
--to=blo@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=roy.fan.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).