Re: [dpdk-dev] [PATCH v2 1/9] cryptodev: clarify API for AES-CCM

2017-10-09 Thread Trahe, Fiona
> -Original Message- > From: De Lara Guarch, Pablo > Sent: Thursday, September 21, 2017 2:11 PM > To: Doherty, Declan ; Trahe, Fiona > ; Jain, Deepak K > ; Griffin, John > Cc: dev@dpdk.org; De Lara Guarch, Pablo > Subject: [PATCH v2 1/9] cryptodev: clarify API for AES-CCM > > AES-CCM

[dpdk-dev] [PATCH v2 1/9] cryptodev: clarify API for AES-CCM

2017-09-21 Thread Pablo de Lara
AES-CCM algorithm has some restrictions when handling nonce (IV) and AAD information. As the API stated, the nonce needs to be place 1 byte after the start of the IV field. This field needs to be 16 bytes long, regardless the length of the nonce, but it is important to clarify that the first byte