From: Steffen Klassert <steffen.klassert@secunet.com>
To: <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Eyal Birger <eyal.birger@gmail.com>,
Antony Antony <antony@phenome.org>,
Benedict Wong <benedictwong@google.com>,
Lorenzo Colitti <lorenzo@google.com>,
"Shannon Nelson" <shannon.nelson@oracle.com>
Subject: [PATCH RFC ipsec-next 0/3] Virtual xfrm interfaces
Date: Mon, 4 Jun 2018 08:09:07 +0200 [thread overview]
Message-ID: <20180604060910.13896-1-steffen.klassert@secunet.com> (raw)
This patchset introduces new virtual xfrm interfaces.
The design of virtual xfrm interfaces interfaces was
discussed at the Linux IPsec workshop 2018. This patchset
implements these interfaces as the IPsec userspace and
kernel developers agreed. The purpose of these interfaces
is to overcome the design limitations that the existing
VTI devices have.
We had two presentations about xfrm interfaces at
the workshop. Slides with further informations
can be found at the workshop homepage:
https://workshop.linux-ipsec.org/2018/
next reply other threads:[~2018-06-04 6:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 6:09 Steffen Klassert [this message]
2018-06-04 6:09 ` [PATCH RFC ipsec-next 1/3] flow: Extend flow informations with xfrm interface id Steffen Klassert
2018-06-04 6:09 ` [PATCH RFC ipsec-next 2/3] xfrm: Add a new lookup key to match xfrm interfaces Steffen Klassert
2018-06-04 6:09 ` [PATCH RFC ipsec-next 3/3] xfrm: Add virtual " Steffen Klassert
2018-06-04 12:58 ` [PATCH RFC ipsec-next 0/3] Virtual " David Miller
2018-06-05 9:07 ` Steffen Klassert
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=20180604060910.13896-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=antony@phenome.org \
--cc=benedictwong@google.com \
--cc=eyal.birger@gmail.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@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;
as well as URLs for NNTP newsgroup(s).