Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@reed.com>
To: Dave Taht <dave.taht@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] make-wifi-fast videoconference?
Date: Sat, 28 Feb 2015 19:39:30 -0500	[thread overview]
Message-ID: <ec23f35a-a5f2-4711-863c-d1bcbeccfb19@reed.com> (raw)
In-Reply-To: <CAA93jw5m8WR3eCvi8WWpLpDB-maFMBY8A6m+MsPtNxKLgGMt+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

I am booked solid on Monday and Tuesday - speaking at the F2C conference in NYC about the big issues in evolving the wireless Internet to be less centralized and more scalable. I will briefly mention Cerowrt  as a good model for making a difference and mention the WiFi challenge. It won't be technically deep, but will frame why leaving it to the cellular companies as offload is far worse than improving the architecture to scale and interoperate well.

On Feb 28, 2015, Dave Taht <dave.taht@gmail.com> wrote:
>in trying to get make-wifi-fast off the ground, I am certainly finding
>email to be a release (for ranting & venting!) but not very productive
>for planning and figuring out various bits and pieces of what else is
>needed to be done.
>
>There is an awful lot to be done, and I am thinking that maybe pulling
>together a videoconference of everyone interested would be useful.
>These days I mostly use appear.in. I am (presently) in PDT, and
>typically awake between 8AM and 1AM.
>
>So does anyone have time next week (say, monday afternoon or evening)
>to chat more interactively?
>
>I could try to go back to operating over irc, also.
>
>--
>Dave Täht
>Let's make wifi fast, less jittery and reliable again!
>
>https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- Sent with K-@ Mail - the evolution of emailing.

[-- Attachment #2: Type: text/html, Size: 1865 bytes --]

      reply	other threads:[~2015-03-01  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 21:52 Dave Taht
2015-03-01  0:39 ` David P. Reed [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ec23f35a-a5f2-4711-863c-d1bcbeccfb19@reed.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-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