netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org
Subject: Re: IPsec workshop/BoF at netdev1.1?
Date: Mon, 7 Dec 2015 07:19:02 -0500	[thread overview]
Message-ID: <20151207121902.GC14535@oracle.com> (raw)
In-Reply-To: <20151207120054.GI14008@secunet.com>

On (12/07/15 13:00), Steffen Klassert wrote:
> Is there any interest in doing an IPsec workshop/BoF at netdev1.1?
> 
> This mail is to probe if we can gather enough discussion topics to run
> such a workshop/BoF. So if someone is interested to attend and/or has a
> related discussion topic, please let me know.

As I've already mentioned, I'm interested. 
BTW, a related topic may be this one:
  http://www.netdevconf.org/1.1/talk-securing-traffic-tunnelled-over-l3-sowmini-varadhan.html

--Sowmini

  reply	other threads:[~2015-12-07 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 12:00 IPsec workshop/BoF at netdev1.1? Steffen Klassert
2015-12-07 12:19 ` Sowmini Varadhan [this message]
2015-12-07 16:20 ` Eric Dumazet
2015-12-08 11:30   ` 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=20151207121902.GC14535@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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).