From: Steffen Klassert <steffen.klassert@secunet.com>
To: "Skidmore, Donald C" <donald.c.skidmore@intel.com>,
Boris Pismenny <borisp@mellanox.com>,
Florian Westphal <fw@strlen.de>,
Sowmini Varadhan <sowmini.varadhan@oracle.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: <netdev@vger.kernel.org>
Subject: IPsec workshop at netdevconf
Date: Mon, 21 Aug 2017 09:10:49 +0200 [thread overview]
Message-ID: <20170821071049.GE31224@secunet.com> (raw)
Hi all,
we plan for an IPsec workshop at the next netdev conference in November.
Is there anybody interested to present something or is there anybody who
want to discuss something?
So far we have the following tentative topics:
Donald Skidmore:
Presentation: The intel implementation of the IPsec offload support.
Discussion: Virtualization with IPsec offload; IPsec offload with OVS
Boris Pismenny:
Presentation: Describe trailer removal; Describe ESN; show performance
numbers.
Discussion: Full device terminated IPsec offload; software fallback
problems common to TLS and IPsec; auth failure using decrypted packet
vs. plaintext packet
Steffen Klassert:
Presentation: The IPsec status update.
Discussion: Redesigning the IPsec VTI interfaces.
reply other threads:[~2017-08-21 7:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170821071049.GE31224@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=borisp@mellanox.com \
--cc=donald.c.skidmore@intel.com \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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