From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: RFC - IPsec Sample App Date: Wed, 16 Sep 2015 10:35:54 +0200 Message-ID: <2390869.VPa9rt1CFQ@xps13> References: <55F92863.2040902@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Gonzalez Monroy, Sergio" Return-path: Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by dpdk.org (Postfix) with ESMTP id C937F377E for ; Wed, 16 Sep 2015 10:37:02 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so61842134wic.1 for ; Wed, 16 Sep 2015 01:37:02 -0700 (PDT) In-Reply-To: <55F92863.2040902@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-09-16 09:29, Gonzalez Monroy, Sergio: > We are looking for feedback on the proposal to create a new sample > application [...] > A set of generic APIs for the configuration of IPsec security policies and > associations will be provided, which will be independent of the How can you have some API in a sample application? It looks like an IPsec library, not an application. Are we going to add a library for each protocol in DPDK like it is done in the Linux kernel stack (including OVS)? Probably no.