From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8078621F1B1 for ; Mon, 17 Mar 2014 07:55:41 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B7D7D20036; Mon, 17 Mar 2014 12:14:56 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id C7E34647C9; Mon, 17 Mar 2014 10:55:39 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B136E647C8; Mon, 17 Mar 2014 10:55:39 -0400 (EDT) From: Michael Richardson To: Dave Taht In-Reply-To: References: <5162.1395058842@sandelman.ca> X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-9 released 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: Mon, 17 Mar 2014 14:55:41 -0000 Dave Taht wrote: >> Dave Taht wrote: >> > - haven't tried blue-ray >> >> quai? > At least one blueray player we know of isn't working through the > default dhcp/dns/upnp setup. okay, I was imaging you plugging a blue-ray player onto the USB port... and then... ... ? profit. >> > items were procd support >> > for babeld, and bcp38 support. We have issues still with upnp. hnetd, >> >> is bcp38 support something you are expecting to see in the UI scripts or is >> there some other place that you'd expect to see it? > firewall and UI support would be good > I've modeled something that basically should work in my bcp38 repo. >> while we need to drop packets from ULA src at the *WAN* edge, I am wondering >> how we deal with a gentle renumber from the ISP... I'm thinking that we >> should just leave all the prefixes that PD gave us in place for some time. >> Maybe LRU on 16 prefixes... > With source specific routing for ipv6 we have no need for bcp38 for ipv6. well... if all of our tables are source specific, then I guess I agree. If we have no default route for a default source, then we have implemented bcp38. > It's needed for ipv4. That's a different can of worms. The NAT table won't survive a renumber... > That said, surviving an ipv6 renumber is a problem. Many clients probably > don't respect an address assignment lifetime. I have experimental evidence that it's the opposite: clients give up their address and on-linkness way too easily. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [