From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [RFC PATCH 1/4] rte_security: API definitions Date: Fri, 18 Aug 2017 11:16:39 +0200 Message-ID: <4861108.dgZJ5lNHcd@xps> References: <20170725112153.29699-1-akhil.goyal@nxp.com> <4cee6900-f886-6997-6911-6c9ca1735e65@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Akhil Goyal , Radu Nicolau , dev@dpdk.org, declan.doherty@intel.com, aviadye@mellanox.com, borisp@mellanox.com, pablo.de.lara.guarch@intel.com, sergio.gonzalez.monroy@intel.com, Sandeep Malik , techboard@dpdk.org To: Hemant Agrawal Return-path: In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, 16/08/2017 17:40, Hemant Agrawal: > Hi Thomas, > Can we get a next-security tree to do development around this proposal? > > Also, we can discuss about this proposal in general in next techboard meeting. First question to ask: Why not create a repository elsewhere for your trials? The benefit of creating a dpdk.org repo is to show it as an official feature. So the idea behind this new library must be accepted by the technical board first. The other use of official repos is prepare pull request for subsequent releases. Do we want to have a -next tree for IPsec development and keep it for next releases? I think it makes sense to have a -next tree for IPsec offloading in general. Before the techboard approves it, we need to define the name (and the scope) of the tree, and who will be the maintainer of the tree.