From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2F9FBA04B0; Fri, 7 Aug 2020 23:49:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7C1D11C033; Fri, 7 Aug 2020 23:49:30 +0200 (CEST) Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by dpdk.org (Postfix) with ESMTP id 8EB772C54 for ; Fri, 7 Aug 2020 23:49:28 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id CAD4458019C; Fri, 7 Aug 2020 17:49:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 07 Aug 2020 17:49:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= J/jcgOT5wlbdFKjzsq7Ke3ujPRFPu8EsnzzFe5+qQOk=; b=yCrEb6QylWjpWbG9 iFMx9N6Mu1wKx+Weeda6jnlAS49Q5d38BnoulcRLoWXhz9ukEI5J43BqhJ4Sk2bJ bf+HdOOxSSmHOSM0xkRREUbsTH+i+2/v4jLz2fO+CR03fkgisP5YF8cdDcVEYLT3 wDkoz7q7K12ovEkvo/ogtM71VAZzBwK4nk3eK5gjA5ayCFRmqrh7P5pT7QFUds5Z SSryFKNToQFMnl8RHWT2SaEBmOmfgq4CMuA6neFd5R6Exc8FlWonsKJHhSCw3h0f QU41wIjTCLyyunsyqbeRqWVtzxDk4e/C7KG6ZZ61X/SymorKdmbxmBcpm6Itw83k TDrg+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=J/jcgOT5wlbdFKjzsq7Ke3ujPRFPu8EsnzzFe5+qQ Ok=; b=Cm1VjrzMlNqKVPIDMHATzB3qL4AJApmJt8x9BrVT7H1Dm1rN2pg8PYN9C dxMpFOiKXcW2f+N4EfzDy38xVmi5QGzctvw3X1PMRwck9MJwtbVnbeatYW5fsucB jcGx+zBf4ufNtYDbELyRrMI9v5DvrnlSmiOKdJq5lynCxD56pthrpFl2bAAqwM3M EMGDx+6ysAqZTybz7+fMMNxPAsy6QxF6q8TV/T+DQ2hA+npdJtQrV/+KCBrVrfSU OfiBSsnEPIL5Aag67WAr7/ukms4d1jOrQ+HtkAdrfcH+vJNlyBSF/36IVezq/bsP 2CZKz5GQkzVZtZVDjw3SM2C0zNQcw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrkeefgddtfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucfkphepleefrdeirddugeelrdduudegnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdr nhgvth X-ME-Proxy: Received: from xps.localnet (114.149.6.93.rev.sfr.net [93.6.149.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 2734B328005A; Fri, 7 Aug 2020 17:49:26 -0400 (EDT) From: Thomas Monjalon To: Arek Kusztal Cc: dev@dpdk.org, akhil.goyal@nxp.com, anoobj@marvell.com, declan.doherty@intel.com, fiona.trahe@intel.com, asomalap@amd.com, rnagadheeraj@marvell.com, hemant.agrawal@nxp.com, pablo.de.lara.guarch@intel.com, roy.fan.zhang@intel.com Date: Fri, 07 Aug 2020 23:49:24 +0200 Message-ID: <4171449.91m3rO6bWt@thomas> In-Reply-To: <20200805151514.1180-1-arkadiuszx.kusztal@intel.com> References: <20200805151514.1180-1-arkadiuszx.kusztal@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] doc: announce move of aes gmac algorithm to aead X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 05/08/2020 17:15, Arek Kusztal: > This patch announces removal of RTE_CRYPTO_AUTH_AES_GMAC > from rte_crypto_auth_algorithm and addition of RTE_CRYPTO_AEAD_AES_GMAC > to rte_crypto_aead_algorithm. > AES-GMAC is variation of AES-GCM algorithm with the difference that > it does not perform encryption. As a matter of fact internally > there is no difference between GMAC and GCM except for the way how > data is passed. > Moving GMAC to AEAD can simplify way of implementing this alogrithm > for example in IPsec (RFC4543). > > Signed-off-by: Arek Kusztal > --- > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > +* cryptodev: ``RTE_CRYPTO_AUTH_AES_GMAC`` will no longer be included in > + ``enum rte_crypto_auth_algorithm``. It will be included in > + ``enum rte_crypto_aead_algorithm`` as ``RTE_CRYPTO_AEAD_AES_GMAC``. I wonder whether this move shows a problem in classification of the crypto algorithms. Anyway this proposal didn't meet its audience. Because of the lack of ack (3 required), it cannot be accepted.