From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from chi.subsignal.org (cxd-2-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:ed::2]) by huchra.bufferbloat.net (Postfix) with ESMTP id 3E56A21F176 for ; Wed, 12 Dec 2012 01:47:46 -0800 (PST) Received: from [192.168.178.21] (unknown [212.255.230.88]) by chi.subsignal.org (Postfix) with ESMTPSA id 8DD281260DF; Wed, 12 Dec 2012 10:48:08 +0100 (CET) Message-ID: <50C852C0.1060100@openwrt.org> Date: Wed, 12 Dec 2012 10:47:44 +0100 From: Steven Barth User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ole_Tr=F8an?= References: <8F973FF7-B39D-4E21-B889-14F6105A29F4@employees.org> <50C84C38.7040207@openwrt.org> <7E37A46B-7F40-40D1-9A59-B176F5219DB4@employees.org> In-Reply-To: <7E37A46B-7F40-40D1-9A59-B176F5219DB4@employees.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Current state of ipv6 in openwrt barrier breaker X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2012 09:47:46 -0000 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. 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? 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.