From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Current state of ipv6 in openwrt barrier breaker
Date: Wed, 12 Dec 2012 11:11:07 +0100 [thread overview]
Message-ID: <CAA93jw5O1QqhCtaCZgF8n3u598zC4OnH2-kAOZM19hMjXe1c5A@mail.gmail.com> (raw)
In-Reply-To: <50C852C0.1060100@openwrt.org>
On Wed, Dec 12, 2012 at 10:47 AM, Steven Barth <cyrus@openwrt.org> wrote:
> Hi Ole,
>
>> you could use hierarchical PD, just that it doesn't work well with:
>> - networks with loops
>> - multi-homed networks
>>
>> and it is quite wasteful with regards to subnet space.
>> ND proxy fails in any topology with a loop.
>
> Yes but I expect loops not to happen in practice or people that build loops
> to know how to take care of them.
I expect loops to happen a lot in practice, and people to not be able
to take care of them.
Babel, however, is loop free.
http://www.pps.univ-paris-diderot.fr/~jch/software/babel/
>
> Nevertheless taking into account the issues I mention below hierarchical PD
> still sounds to me like a better thing in SOHO environments regarding
> interoperability with other devices in that environment however as I still
> need the NDP-Proxying fallback in case the upstream router (be it a
> SOHO-router) doesn't support further distribution of the ISP-Prefix.
>
>
>
>> we do have an implementation on github that implements
>> http://datatracker.ietf.org/doc/draft-arkko-homenet-prefix-assignment/
>> that supports prefix assignment with an arbitrary topology in the network.
>> why not use that?
I would like to implement portions of that algorithm in something far
more lightweight than OSPF. Extending AHCP is my current first choice.
> From a technical point of view I like your approach and using OSPF.
>
> However the stuff is >1 MB in size including all of its dependencies and
> includes some strange dependencies like libreadline?, some otherwise
> unrelated Lua extensions and so on.
>
> Sorry, that is not an option for the majority of OpenWrt users, just for
> having a more versatile Prefix Delegation feature which will only be (?)
> interoperable with a small amount of routers.
>
> We could integrate it for more powerful routers though (and I wouldn't
> object) but I don't see any hope to get it to mainstream before we can get
> it down to a few 100 KB (including dependencies).
> Also at least I don't have any time or resources to take care of either of
> that in the near future.
Neither do I.
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-12-12 10:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 19:56 Ole Trøan
2012-12-11 20:25 ` Dave Taht
2012-12-11 21:31 ` Ole Trøan
2012-12-12 8:19 ` Dave Taht
2012-12-12 9:08 ` Ole Trøan
2012-12-12 9:19 ` Steven Barth
2012-12-12 9:28 ` Ole Trøan
2012-12-12 9:47 ` Steven Barth
2012-12-12 10:11 ` Dave Taht [this message]
2012-12-12 18:56 ` Michael Richardson
2012-12-12 9:05 ` Török Edwin
2012-12-11 20:46 ` Steven Barth
2012-12-11 21:02 ` Ole Trøan
2012-12-12 8:23 ` Steven Barth
2012-12-12 8:43 ` Ole Trøan
-- strict thread matches above, loose matches on Subject: below --
2012-12-10 8:41 Dave Taht
2012-12-10 9:15 ` Dave Taht
2012-12-10 11:27 ` Steven Barth
2012-12-10 11:40 ` Dave Taht
2012-12-10 11:53 ` Steven Barth
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=CAA93jw5O1QqhCtaCZgF8n3u598zC4OnH2-kAOZM19hMjXe1c5A@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cyrus@openwrt.org \
/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