----- Original Message -----
From: "Scott Schmit" <i.grok(a)comcast.net>
To: devel(a)lists.fedoraproject.org
Sent: Friday, October 30, 2015 2:10:41 AM
Subject: Re: Fedora IPv6 testing and improvements - request for ideas
On Thu, Oct 29, 2015 at 11:15:10AM -0400, Pavel Simerda wrote:
> I am writing to Fedora development mailing lists to get opinions
> and ideas regarding our project on improving IPv6 support in
> Fedora across its components.
>
>
https://fedoraproject.org/wiki/QA/Networking
>
> Most prominent subpages:
>
> *
https://fedoraproject.org/wiki/QA/Networking/Test_environment
It may make sense to have a IPv6 case between global & local that has
all 4 categories of address (I see this as loosely analogous to the IPv4
masqueraded case).
Hi Scott,
thanks for your feedback.
You can of course have combinations. We can add that once we have
specific test cases that would show importance of a standalone category
for such a setup. Otherwise one would usually view IPv6 global and IPv6
local communication as two isolated things.
Another case would be multi-homed IPv6, where you have global IPv6
addresses from multiple sources (could be two ISPs, two tunnel
providers, or one ISP and one tunnel provider).
Interesting. Any specific test cases for that?
IPv6 is designed to be inherently more dynamic than IPv4
(particularly
with RAs) -- we should test transitions between connectivity states
(simulating an ISP connection dropping and coming back up or a router
going down and coming back up).
While IPv6 is designed to be inherently dynamic, operators seem to be
avoiding it as much as possible and use it in a way more similar to
IPv4. Specific test cases and common usage are welcome, though.
Speed differences between IPv6 & IPv4 could be a factor as well
(happy
eyeballs) -- though reportedly IPv6 has tended to be faster than IPv4
rather than the previously-expected inverse.
Checking support for DHCPv6-PD would also be valuable.
We're not really focusing on a Fedora based router use case. As always,
that doesn't mean someone cannot join and extend the effort. If you're
interested in the classic connection sharing feature, it may be better
to contact NetworkManager developers directly.
Cheers,
Pavel