<div dir="ltr">If it helps, Sixxs (<a href="https://www.sixxs.net/main/">https://www.sixxs.net/main/</a>) is a very highly recommended tunnel broker. I have not tried it and am not affiliated. I do have ipv6 capability from my isp, so could help with testing. </div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 29, 2015 at 3:35 PM, Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Oct 29, 2015 at 3:15 PM, Pavel Simerda <<a href="mailto:psimerda@redhat.com">psimerda@redhat.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I am writing to Fedora development mailing lists to get opinions<br>
> and ideas regarding our project on improving IPv6 support in<br>
> Fedora across its components.<br>
><br>
> <a href="https://fedoraproject.org/wiki/QA/Networking" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/QA/Networking</a><br>
<br>
</span>In the above page:<br>
* Network configuration: I see NetworkManager in there but nothing<br>
about systemd-networkd<br>
* Other: firewalld including zones and other such configurations (you<br>
mention iptables)<br>
<span class=""><br>
> Most prominent subpages:<br>
><br>
> * <a href="https://fedoraproject.org/wiki/QA/Networking/Test_environment" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/QA/Networking/Test_environment</a><br>
<br>
</span>In this section I see "IPv6 node" but nothing that covers a IPv6 only<br>
routed network with IPv6 to IPv4 gateway ie it runs v6 only internally<br>
but uses 6 to 4 services for legacy services.<br>
<br>
> * <a href="https://fedoraproject.org/wiki/QA/Networking/Client_software" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/QA/Networking/Client_software</a><br>
<br>
Again nothing about a native IPv6 only network with a gateway that<br>
supports 6to4 for legacy services outside the network.<br>
<br>
What about a iOS9 style preferring of IPv6 over IPv4 in the general<br>
desktop. In the iOS9 case they do network measurements and favour IPv6<br>
bydefault, and if it's going to be faster but fail back quickly if<br>
it's not, how would we deal with this?<br>
<br>
> * <a href="https://fedoraproject.org/wiki/QA/Networking/Server_software" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/QA/Networking/Server_software</a><br>
<br>
Nothing in here about:<br>
* IPv6 services RA, dhcp6, 6 to 4 proxies, 4 to 6 proxies and other<br>
such transition servers<br>
* what about VPN services like a IPv6 only network connecting to a<br>
dual stack VPN, or a IPv4 only VPN or a number of combinations there<br>
of IE interfaces that are v6 only and ones that are v4 only. What<br>
happens with routing then if there's other 6 to 4 services in play?<br>
* Load balancers ie like facebook uses to bridge external dual stack<br>
to IPv6 only internal services, or providing IPv6 externally to<br>
present internal v4 services externally to v6<br>
<br>
There's also nothing I can see from a quick read about offload<br>
engines. A lot of 10Gb+ network interfaces have offloads for generic<br>
IP, TCP, other acceleration to enable to do line speed 10+gb on IPv4,<br>
we obviously want acceleration because IPv6 headers are larger and<br>
hence take up more memory. There's toolkits like dpgk (<br>
<a href="http://dpdk.org" rel="noreferrer" target="_blank">http://dpdk.org</a> ) for acceleration of packets across large bandwidth<br>
interfaces but I don't see any mention of that or network IO<br>
virtualisation/offload.<br>
<br>
Facebook and others have been testing these sorts of things:<br>
<br>
<a href="https://code.facebook.com/posts/1123882380960538/linux-ipv6-improvement-routing-cache-on-demand/" rel="noreferrer" target="_blank">https://code.facebook.com/posts/1123882380960538/linux-ipv6-improvement-routing-cache-on-demand/</a><br>
<a href="https://code.facebook.com/posts/938078729581886/improving-the-linux-kernel-with-upstream-contributions/" rel="noreferrer" target="_blank">https://code.facebook.com/posts/938078729581886/improving-the-linux-kernel-with-upstream-contributions/</a><br>
<br>
Along these lines also I see nothing about Open vSwitch and SND<br>
encapsulation protocols testing such as vxlan, GRE, GENEVE etc<br>
<span class=""><br>
> During the first phase we are interested in getting feedback on<br>
> testing methods and test cases. Any other ideas are of course<br>
> welcome. Even contacts for future collaboration would be great.<br>
<br>
</span>A future development would be around 6LoWPAN and the routing protocols<br>
etc for that so we can communicate with IoT devices.<br>
<br>
The way I read a lot of the pages above is a "this is how we did it on<br>
IPv4 lets test it on IPv6" rather than a review of how things are<br>
going to change with IPv6, how would I get to a IPv4 site if I'm on a<br>
IPv6 network, visa versa and the whole sets of new use cases that are<br>
appearing as a result of it.<br>
<span class="HOEnZb"><font color="#888888"><br>
Peter<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a></div></div></blockquote></div><br></div>