From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] example/ipsec-secgw: ipsec security gateway
Date: Fri, 11 Mar 2016 10:01:18 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8C8A17@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1457662360-108929-1-git-send-email-sergio.gonzalez.monroy@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Friday, March 11, 2016 2:13 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v3] example/ipsec-secgw: ipsec security gateway
>
> Sample app implementing an IPsec Security Geteway.
> The main goal of this app is to show the use of cryptodev framework
> in a "real world" application.
>
> Currently only supported static IPv4 ESP IPsec tunnels for the following
> algorithms:
> - Cipher: AES-CBC, NULL
> - Authentication: HMAC-SHA1, NULL
>
> Not supported:
> - SA auto negotiation (No IKE implementation)
> - chained mbufs
>
> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2016-03-11 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 20:29 [dpdk-dev] [PATCH] " Sergio Gonzalez Monroy
2016-01-31 14:39 ` Jerin Jacob
2016-02-01 11:09 ` Sergio Gonzalez Monroy
2016-02-01 11:26 ` Jerin Jacob
2016-02-01 14:09 ` Thomas Monjalon
2016-03-09 23:54 ` Sergio Gonzalez Monroy
2016-03-10 3:41 ` Jerin Jacob
2016-02-24 13:32 ` Thomas Monjalon
2016-02-24 14:49 ` Sergio Gonzalez Monroy
2016-03-11 1:38 ` [dpdk-dev] [PATCH v2] " Sergio Gonzalez Monroy
2016-03-11 2:12 ` De Lara Guarch, Pablo
2016-03-11 2:12 ` [dpdk-dev] [PATCH v3] " Sergio Gonzalez Monroy
2016-03-11 10:01 ` De Lara Guarch, Pablo [this message]
2016-03-11 10:07 ` Thomas Monjalon
2016-03-11 10:02 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E115CCD9D858EF4F90C690B0DCB4D8973C8C8A17@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).