IPv6 support on Virgin media
Does anyone know whether (and if so when) Virgin plan to implement IPv6 on its network?
Forum Discussion
@artiomchi: I agree that IPv4 is likely to get very messy and painful, but to some extent it already is. Just ask the gamer community about their never-ending fight against NAT idiosyncracies.
IPv6 offers the opportunity to leave that mess behind, and also to improve networking performance compared to what IPv4 has given us. I'm not dismissing that there will be pain on IPv4 ahead, but this is unavoidable pain because limiting IPv6 delegations to the number of public IPv4 addresses makes no sense. IPv4 address exhaustion necessarily implies that Dual Stack is only a transitional mechanism, otherwise the Internet could never grow beyond the limits of IPv4 availability.
The best way to overcome the problems of IPv4 is to encourage migration of the services we love to IPv6.
Oh absolutely! That's absolutely true.
What I'm baffled by is something else. VM already has a large customer base, which are all currently sitting on IPv4. I'm assuming the majority (if not all) of them are on dedicated IPs, assuming VM didn't exhaust their pool.
Running IPv6 and IPv4 side by side shouldn't change anything at all. It's (simplifying a bit) basically just giving the users access to IPv6 with dedicated addresses for each user, and leaving IPv4 in place as it is. Sure, once you get more users, and you run out of available addresses, new users will be put on DS Lite - it's unavoidable. But until then, I see no point in changing the infrastructure and forcing most existing users on DS Lite, and giving them a considerably worse service than before. (I'm hoping they won't do the latter.. I'm just concerned about it, based on what i read so far)
This would just turn people against IPv6. Remember - most users are not technical, so when support will tell them:
> Oh, we turned on this fancy new feature IPv6 on your internet, that's why you're now having issues on your XBox and Skype. What does it do? Oh, nothing much, same as before - gives you access to the whole internet.
The users will just go back and say that IPv6 ruined their internet, roll it back NOW..
What I'm baffled by is something else. VM already has a large customer base, which are all currently sitting on IPv4. I'm assuming the majority (if not all) of them are on dedicated IPs, assuming VM didn't exhaust their pool.
Running IPv6 and IPv4 side by side shouldn't change anything at all. It's (simplifying a bit) basically just giving the users access to IPv6 with dedicated addresses for each user, and leaving IPv4 in place as it is. Sure, once you get more users, and you run out of available addresses, new users will be put on DS Lite - it's unavoidable. But until then, I see no point in changing the infrastructure and forcing most existing users on DS Lite, and giving them a considerably worse service than before. (I'm hoping they won't do the latter.. I'm just concerned about it, based on what i read so far)
This would just turn people against IPv6. Remember - most users are not technical, so when support will tell them:
> Oh, we turned on this fancy new feature IPv6 on your internet, that's why you're now having issues on your XBox and Skype. What does it do? Oh, nothing much, same as before - gives you access to the whole internet.
The users will just go back and say that IPv6 ruined their internet, roll it back NOW..
artiomchi wrote:
Remember - most users are not technical, so when support will tell them:
> Oh, we turned on this fancy new feature IPv6 on your internet, that's why you're now having issues on your XBox and Skype. What does it do? Oh, nothing much, same as before - gives you access to the whole internet.
The users will just go back and say that IPv6 ruined their internet, roll it back NOW..Virgin never tell you what has changed with their network, so IF they roll out DS-Lite in the future it will most likely be done silently. The potential fall-out would be similar to what has happened in Ireland:
http://www.boards.ie/ttfthread/2057598420
I too hope they don't decide to use DS-Lite. I help run an IRC network (which has supported IPv6 for years now) and CGN is a cause of a number of headaches when it comes to abuse. For service providers, there's really not a lot you can do to prevent this sort of abuse in a clean way. If you ban the IP (which would normally just represent one user), you end up with huge collateral damage. For services that do support v6, I guess forcing users to connect using it is a possibility.
I worry about the sites and services that don't support v6, though. Suddenly the actions of a ton of other customers are tied to the same v4 address I have to use - and you can forget hosting any services or forwarding ports (sadly necessary because v6 support in the UK is still awful, especially amongst mobile providers).
The whole transition is going to be painful for some time, I think. Virgin Media would do good to allow us existing customers to continue using the existing v4 addresses as normal whilst it is still possible.
I can't fault your argument there
In fact Virgin Media customers have already been impacted by CGN's in a different way.
Virgin has an outbound spam filtering on it's SMTP relays that relies in some part on the reputation of the IP the user is connecting from. This means that in some situations, users sending emails when connected for example to a mobile network, have been penalised because the public mobile IP is blacklisted. While Virgin doesn't block the mail itself, it does mean that mail from such IP's is more likely to be rejected by the destination.
Ravenstar68
Note that even if they move IPv4 over to DS-Lite, there is no reason why Virgin cannot implement "permanent" stickiness of the IPv4 address assigned to each user at the remote CGN port, at least until the day that they finally run out of them. Until that day arrives, the assignment doesn't have to be stateless.
For a long time, Virgin has been using the daft argument of "We've got plenty of IPv4 addresses" as their excuse for brushing IPv6 deployment under the carpet. Well if that was so, then this is the time to prove it by doing the right thing and using per-account stateful IP assignment.
Anyone want to bet on the chances of VM doing the right thing for a change? :P
