= Сообщение: 2173 из 7440 ============================================= IPV6 = От : Andrew Leary 1:320/219 17 Feb 16 18:46:18 Кому : Michiel van der Vlist 17 Feb 16 18:46:18 Тема : Bill not answering on IPv6 for several weeks now? FGHI : area://IPV6?msgid=1:320/219@fidonet+56c51102 На : area://IPV6?msgid=2:280/5555+56c34902 = Кодировка сообщения определена как: CP437 ================================== Ответ: area://IPV6?msgid=1:14/5@fidonet+56c573c4 ============================================================================== Hello Michiel!
16 Feb 16 17:00, you wrote to me:
MV> Hello Andrew,
MV> On Tuesday February 16 2016 04:04, you wrote to Bill McGarrity:
AL>> I've noticed that Comcast tends to change their IPv6 assignments AL>> occasionally for no apparent reason.
MV> Why not just ask them?
Based on past experience, it takes nearly an hour on the phone before you get to someone in their support department that has any clue what they are talking about, and that is with IPv4 issues. Most of their staff seems to have no clue whatsoever what IPv6 is.
AL>> [..] It wouldn't surprise me if this was done by Comcast to AL>> discourage the use of server applications on their residential AL>> service.
MV> That, or they are resetting their systems for maintenance or taking MV> care of child diseases. Maybe the IPv6 part of their network is still MV> a bit unstable.
This is possible. The assignments don't change very often, but I haven't been able to nail down the exact time frame.
MV> If it is indeed to discourage running servers, I predict it will not MV> be effective. People have found work arounds for dynamic IPv4 MV> adresses. Similar methods will emerge for IPv6 if ISPs are making a MV> habit of it.
Agreed. A FidoNet node, even one carrying the full backbone and filebone, doesn't put nearly the load on the network that streaming services such as NetFlix and the like do.
