From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "ams-iport-4.cisco.com", Issuer "Cisco SSCA2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2D73A21F17D for ; Wed, 12 Dec 2012 01:28:35 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApIIAJ5NyFCQ/khN/2dsb2JhbABFg0i7WhZzgh4BAQQBeQULCw44VwaIHgYMvEyQLWEDlyOPLIJ0 X-IronPort-AV: E=Sophos;i="4.84,265,1355097600"; d="scan'208";a="10364221" Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 12 Dec 2012 09:28:33 +0000 Received: from dhcp-lys02-vla252-10-147-117-91.cisco.com (dhcp-lys02-vla252-10-147-117-91.cisco.com [10.147.117.91]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qBC9SWQG015465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 12 Dec 2012 09:28:32 GMT Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: =?iso-8859-1?Q?Ole_Tr=F8an?= In-Reply-To: <50C84C38.7040207@openwrt.org> Date: Wed, 12 Dec 2012 10:28:32 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7E37A46B-7F40-40D1-9A59-B176F5219DB4@employees.org> References: <8F973FF7-B39D-4E21-B889-14F6105A29F4@employees.org> <50C84C38.7040207@openwrt.org> To: Steven Barth X-Mailer: Apple Mail (2.1499) 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:28:36 -0000 Steven, >> the worst you can expect is a /64 on the link-net and no PD. I = suggest you don't support that case. > The problem is that (some) people are expecting to be able to just = plug other routers behind their main uplink router for whatever reasons = (e.g. additional WiFi-network etc.) like they have with IPv4 or e.g. = make a router just connect to a non-WDS WiFi in client mode and extend = their network. that only works in IPv4 if you have a good tail wind and your fingers = crossed. > As the home router shouldn't do PD to further distribute the = ISP-prefix it is hard to support this with IPv6 except with detecting = the case and doing NDP-Proxying then as bridging might not always be = possible or desired in this case. 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. > And supporting all of this above would have the side-effect that such = ISP without PD would be supported as well so I'm not really sure. ND proxy fails in any topology with a loop. 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? cheers, Ole