From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] HNCP protocol design RFC and code
Date: Fri, 7 Feb 2014 13:51:42 -0500 [thread overview]
Message-ID: <CAA93jw7agKxrC8Pq8LuHaazpnMFWMzWOcPoXtS0+CaZcE2KSFA@mail.gmail.com> (raw)
HNCP is going to solve a lot of problems with border discovery,
propagating ipv6 prefixes and other problems like that. It looks like
it will break the logjam we've had for 2+ years in homenet with the
incendiary "embed config info in routing protocol" vs "embed config in
a separate protocol" debate.
Some code already exists for openwrt. I haven't had time to read the
draft or code fully, but with the latent integration into opewrt's
ubus system it seems probable we can replace AHCP in the long run.
I love that HNCP uses the trickle protocol underlying.
My only glancing comments were that the crypto architecture needs
work, and it wasn't clear if /128s could be distributed and there is
probably more configuration information that needs to be propagated
across a homenet. Also I'd still like to see some ipv4 concerns (like
local nat discovery) also addressed.
Please make your comments on the homenet mailing list, not here.
This is not slated for the upcoming cero stable release.
See below for links.
---------- Forwarded message ----------
From: Markus Stenberg <markus.stenberg@iki.fi>
Date: Wed, Feb 5, 2014 at 9:52 AM
Subject: [homenet] Two new drafts (and third one 'soon')
To: "homenet@ietf.org Group" <homenet@ietf.org>
Cc: Markus Stenberg <markus.stenberg@iki.fi>
Drafts:
http://tools.ietf.org/html/draft-stenberg-homenet-hncp-00
http://tools.ietf.org/html/draft-stenberg-homenet-dnssd-hybrid-proxy-zeroconf-00
(Generic PA one in the works, but submitted also 'soon')
Experimental partial implementation:
https://github.com/sbyx/hnetd/
Discuss.
Cheers,
-Markus
_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2014-02-07 18:51 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=CAA93jw7agKxrC8Pq8LuHaazpnMFWMzWOcPoXtS0+CaZcE2KSFA@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