Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] The definitive homenet talk
Date: Fri, 6 Jun 2014 08:21:03 -0700	[thread overview]
Message-ID: <CAA93jw7mJ2NxmTUbZMubRkJ_55GBQEGLCyZ7duUp9o-ncLDmUg@mail.gmail.com> (raw)

Sometimes I lose sight of all the problems we're trying to solve here.
Bufferbloat, solved, for ethernet, at least. Security, improved. IPv6,
made to work pretty darn good. Routing, looking good, even with
multiple gateways.

The last pieces of all that is improving DNS and service discovery,
and making it all just work for grandma.

I've run low on motivation and cash of late. Mark Townsley here does
the vision thing on why it is important to make routing and service
discover "just work" in the home, with all the new devices in the IoT
in particular:

https://plus.google.com/u/0/+MarcLuethi/posts/7GWKu1sFMw8

He gets rolling at about 4:20. Watching it this morning cheered me up a bit.

The talk predates the HNCP work. We agreed to standardize on hncp (if
it could be made to work) to propagate addresses and subnets in the
home at the last homenet wg meeting. And babel, is (at least for now)
the default protocol,
replacing ospf.

-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

                 reply	other threads:[~2014-06-06 15:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw7mJ2NxmTUbZMubRkJ_55GBQEGLCyZ7duUp9o-ncLDmUg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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