From: Josh Hunt <johunt@akamai.com>
To: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
"Bohman, Pete" <pbohman@akamai.com>,
kaber@trash.net, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: [ANNOUNCE] netdev0.1 netfilter BoF
Date: Wed, 04 Feb 2015 18:17:54 -0600 [thread overview]
Message-ID: <54D2B6B2.8070004@akamai.com> (raw)
We will be leading a BoF discussing netfilter development and issues in
iptables, ipset, and nftables at netdev0.1 in Ottawa coming up in a few
weeks.
Our timeslot is currently scheduled for Sunday, Feb 15 @ 9am, but please
refer to https://www.netdev01.org/schedule in case there are any
schedule changes.
The topics we intend to cover will be based around Akamai's usage,
deployment, and the issues we've come across.
Some examples of those topics are:
* The need for supported interfaces from netfilter components.
* The handling of large (1 million to 25 million entry) sets, both
with ipsets and nft sets.
* Limitations in existing iptables functionality.
* For ex, issues with hashlimit implementation and proposals to
extend it.
We'll also look at the current standing of nftables and discuss some
basic performance as it pertains to our environment, as well as,
backwards compatibility, and possible new features in nftables.
We hope to bring together interested stakeholders and interested parties
to discuss the above along with any other related netfilter topics you
would like to discuss. The BoF is scheduled for two hours.
If you have items you'd like to add to the agenda and/or present, please
contact me.
Thanks
Josh & Pete
next reply other threads:[~2015-02-05 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 0:17 Josh Hunt [this message]
2015-02-05 20:20 ` [ANNOUNCE] netdev0.1 netfilter BoF Patrick McHardy
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=54D2B6B2.8070004@akamai.com \
--to=johunt@akamai.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pbohman@akamai.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).