From: Nick Feamster <feamster@cc.gatech.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] incorporating openflow
Date: Wed, 4 May 2011 12:16:18 -0400 [thread overview]
Message-ID: <398DDA0C-771B-4769-A643-E3CBFC3863D8@cc.gatech.edu> (raw)
In-Reply-To: <BANLkTi=XJVjP=NT_Up8UtVOc4haBq21u2A@mail.gmail.com>
As Srikanth said, not needed for capetown.
Some possibilities we've been thinking about using it for:
* enforcing per-user or per-device usage caps (in capped settings)
* rate-limiting and QoS functionality
* remote management, troubleshooting, or security services. See this, for example:
http://www.gtnoise.net/papers/2010/feamster:homenets2010.pdf
I'd love to get this into the build sometime soon-ish, so I could encourage people to use it in my class this coming fall. :-)
-Nick
On May 4, 2011, at 11:33 AM, Dave Taht wrote:
> 3) What is the need for openflow? I am meeting with the folk at stanford at 2PM PDT and although I get what openflow is for, I'm not sure of the intended use. Is it needed for capetown?
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
next prev parent reply other threads:[~2011-05-04 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 15:33 Dave Taht
2011-05-04 15:36 ` Srikanth Sundaresan
2011-05-04 16:16 ` Nick Feamster [this message]
2011-05-04 16:38 ` Dave Taht
2011-05-04 16:46 ` Dave Taht
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=398DDA0C-771B-4769-A643-E3CBFC3863D8@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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