Linode Forum

[TeddyR42]

I understand that this may take a while to implement if possible and probably only once all datacenters are IPV6 native capable. This may be very useful once ipv4 addresses are scarce or just to be able to say that "Linode encourages IPV6 deployments". One of the issues for IPV6 deployments is that most users do not yet see a real benifit from it. This would break that wall down a little..

In order to encourage IPV6 deployments, implementing a weighted formula for calcuating the bandwidth charged would be a step towards getting linode users to implement ipv6. The weighted method could be implemented in such a way that existing ipv4 traffic does not get penalized while using ipv6 gets a "discount". Examples:

IPV4 traffic weighted at 1.0
IPV6 traffic weighted at 0.8
examples for Linode 512 with a 200GB month transfer.

scenario A:
ipv4 traffic usage at 80 GB
ipv6 traffic usage at 200 GB

Combined allowable with weighted score: ((80*1.0)+((200*0.8))= 240 Weighted billable, or only 40 over vs 80 over.

scenario B:
ipv4 traffic at 160GB
ipv6 traffic at 50GB
Combined allowable with weighted score: ((160*1.0)+((50*0.8))= 200 Weighted billable, or no overage vs 10 over.


This would encourge linode users to configure ipv6 on their vps and encourage the linode user to encourage their users/customers to also connect via ipv6, hopefully further encouraging the end users to ask "what is ipv6 and how do I get it".

[glg]

TeddyR42 wrote: In order to encourage IPV6 deployments, implementing a weighted formula for calcuating the bandwidth charged would be a step towards getting linode users to implement ipv6. The weighted method could be implemented in such a way that existing ipv4 traffic does not get penalized while using ipv6 gets a "discount". Examples:

IPV4 traffic weighted at 1.0
IPV6 traffic weighted at 0.8
examples for Linode 512 with a 200GB month transfer.

scenario A:
ipv4 traffic usage at 80 GB
ipv6 traffic usage at 200 GB

Combined allowable with weighted score: ((80*1.0)+((200*0.8))= 240 Weighted billable, or only 40 over vs 80 over.

scenario B:
ipv4 traffic at 160GB
ipv6 traffic at 50GB
Combined allowable with weighted score: ((160*1.0)+((50*0.8))= 200 Weighted billable, or no overage vs 10 over.


This would encourge linode users to configure ipv6 on their vps and encourage the linode user to encourage their users/customers to also connect via ipv6, hopefully further encouraging the end users to ask "what is ipv6 and how do I get it".

I like your idea because it's a carrot not a stick. No idea how realistic it is though. I implemented once it was native in my datacenter, but with almost no end users having it available, it doesn't do a whole lot at this point.

[obs]

One problem with IPv6 is the support from domestic ISPs is minimal where I live (UK) it's practically non-existant, until this changes then there's little point for enabling IPv6 for websites and other public services, however it's very handy for inter-linode communication.

[TeddyR42]

[quote="obs"]One problem with IPv6 is the support from domestic ISPs is minimal where I live (UK) it's practically non-existant, until this changes then there's little point for enabling IPv6 for websites and other public services, however it's very handy for inter-linode communication.[/quote]

That is part of the problem. Its the chicken or egg. "if you build it, they will come"... The more sites that are enabled for ipv6 now the better it would be when someone later goes to their ISP as asks about ipv6 availibility and are able to say "several sites I use are ipv6 capable already"

[hybinet]

glg wrote: I like your idea because it's a carrot not a stick. No idea how realistic it is though. I implemented once it was native in my datacenter, but with almost no end users having it available, it doesn't do a whole lot at this point.
Yeah, the suggestion looks good on paper, but for most people it won't save any more than a few cents per month because virtually all traffic goes over IPv4.

But specialized high-traffic applications might benefit from cheaper IPv6 bandwidth. For example, many Debian repositories are now available over IPv6.