[dpdk-dev] [PATCH] [RFC] cryptodev: move AES-GMAC to aead algorithms

[Zhang, Roy Fan]

> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal at intel.com>
> Sent: Wednesday, July 29, 2020 3:22 PM
> To: dev at dpdk.org
> Cc: akhil.goyal at nxp.com; Trahe, Fiona <fiona.trahe at intel.com>;
> anoobj at marvell.com; shallyv at marvell.com; Doherty, Declan
> <declan.doherty at intel.com>; Zhang, Roy Fan <roy.fan.zhang at intel.com>;
> Ananyev, Konstantin <konstantin.ananyev at intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal at intel.com>
> Subject: [PATCH] [RFC] cryptodev: move AES-GMAC to aead algorithms
> 
> This is proposal to move AES-GMAC algorithm to AEAD set
> of algorithms. It is however not 100% conformant GMAC as instead of aad
> pointer
> data to be authenticated is passed normally and  aead.data.length field
> is used to specify length of data to be authenticated.
> Reason behind this move is that GMAC is variant of GCM so it may
> simplify implementations that are using these algorithms (mainly IPsec).
> AES-GMAC therefore needs to be removed from auth algorithms.
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal at intel.com>

Acked-by: Fan Zhang <roy.fan.zhang at intel.com>