The Vigor 2130 broadband router from Draytek supports IPv6. The WAN-IPv6-connection can be established via Static IPv6, DHCPv6 and TSPC. The price: 119 Euro. Full manual here.

Source: http://ipv6-or-no-ipv6.blogspot.com

DrayTek IPv6 development

DrayTek Vigor series routers (Vigor2130 series) have already received certification of IPv6 Ready logo program (Phase I – IPv6 Ready Silver logo) to honor our efforts to make devices meet requirements not only for today but also for tomorrow. On the other hand, this achievement represents how dedicated DrayTek commits to our customers. Phase I achievement is only the start point for DrayTek and we will keep customers posted about our future progress.

source: http://www.draytek.com

The Canadian ISP TekSavvy has started a limited IPv6 beta service. Customers can request a /64, or if they are using a router an additional /56. TekSavvy doesn’t provide official support for this services as of yet.

First of all, the service is provided over native PPP, there is no tunneling involved or 6to4 like most other providers.
In order to enroll in this limited beta, you will need to ask in the TekSavvy Direct forum. Please make sure that you give us your current contact information so that we can find your account.

Read more about it in their announcement. To sign-up you must use the TekSavvy Direct forum.

The Europeon Commision has started an research project with TNO and GNKS  to find the causes for a slow IPv6deploymentby looking at bottlenecks and the argument that are used when talking about IPv6 deployment.

On www.ipv6monitoring.eu they will publish their project results and collect the feedback and ideas that you, and others who are concerned with IPv6, are willing to share.

Governments, enterprises, ISPs, etc., use a wide variation of arguments for not deploying IPv6 in their ICT environment. Some of these arguments are purely technological in nature, whilst others deal with business or the availability of products. Also, some of the arguments are based on reality, and others are just perceived by people but may be based on, for example, misunderstanding of IPv6 technology.

Here are a few examples of the arguments they cover which you can discuss about:

01: “I dont gain anything”

“I dont gain anything whit implementing IPv6, it only increases costs”

This argument is related to the (lack of a) IPv6 business case. It is assumed that the introduction of IPv6 will require extra investments. This will in most cases be true: at least someone has to determine the impact of the introduction of IPv6. But the costs can often be minimized by doing IPv6 investments concurrently with the introduction of new network devices and service platforms. As far as revenues are concerned: not be able to deliver IPv6 on time, may lead to missed opportunities, missing potential revenues.

04. “They say NAT will solve the problem, so why change?”

“I hear people say that Network Address Translation (NAT, RFC 2663) will do the trick. In that case I can keep my current addresses and network infrastructure.”

Is NAT cascading, or Carrier Grade NAT (CGN), an alternative for IPv6? NAT does prolong the lifetime of current IPv4 networks, but has issues with accessibility (the end-to-end principle) and scalability (the number of concurrent sessions is limited). CGN will provide a short-term solution for ISPs who are not IPv6-ready on time. However their total amount of investments will increase, since they will have to move towards IPv6 anyway later on.

For more bottlenecks and arguments check out http://www.ipv6monitoring.eu/bottlenecks

Google has started to initiate the enabling of their Youtube site over IPv6.
It is currently available to participants in their Google over IPv6
program, http://www.google.com/intl/en/ipv6/ .

The www.youtube.com user interface so far does *not* have any AAAA
published, but the *much* more important (traffic wise) image and video
servers do.

:~$ host s.ytimg.com
s.ytimg.com is an alias for static.cache.l.google.com.
static.cache.l.google.com has address 74.125.13.213
static.cache.l.google.com has IPv6 address 2001:4860:4001:402::15

:~$ host v1.lscache1.c.youtube.com
v1.lscache1.c.youtube.com is an alias for v1.lscache1.l.google.com.
v1.lscache1.l.google.com has address 74.125.97.80
v1.lscache1.l.google.com has IPv6 address 2001:4860:4001:402::10

Read more about it on the Ripe IPv6 Workgroup mailinglist

Maria Häll, Deputy Director for the Ministry of Enterprise, Energy and Communications in Sweden, and Co-chair of the RIPE Cooperation Working Group, talks about the role governments can play in encouraging IPv6 deployment in our latest video interview.

For the full transcript, as well as other interviews with community figures, see IPv6 Act Now.

Comcast has announced their plans for IPv6 Trials this year:

2Q2010:

Trial #1 will evaluate tunneling IPv6 over IPv4, using “6RD” technology. 6RD is an open Internet standard developed in the IETF’s Softwires working group. This trial enables us to explore how we may be able to provide production level IPv6 service to customers who have only been issued IPv4 addresses by the ISP network.

Trial #2 will evaluate a native Dual-Stack IPv6 deployment. We will test issuing both IPv4 and IPv6 addresses to the customer premise. This trial will attempt to suit a variety of customer premise configurations, and will evolve over time as the customer premise equipment (CPE) support for IPv6 matures. Native, dual-stack is central to our IPv6 strategy and we expect that the native dual-stack solution will be a significant part of the IPv6 transition, enabling IPv6 technology to evolve globally while still being able to provide seamless services to the traditional IPv4 Internet.

3Q2010:

Trial #3 will evaluate tunneling IPv4 over IPv6, using “Dual-Stack Lite” technology (aka DS-Lite). DS-Lite is an open standard defined in the IETF’s Softwires working group. DS-Lite will involve provisioning only an IPv6 address at the customer premise, and creating a IPv4 over IPv6 tunnel between the customer’s home gateway and an Address Family Transition Router (AFTR) in our network. That AFTR enables sharing IPv4 addresses among DS-Lite IPv6 customers. DS-Lite can be seen as the mirror image of 6RD; 6RD enables IPv6 service to IPv4 customers, whereas DS-Lite enables IPv4 service to IPv6 customers. DS-Lite offers the ability to continue an IPv4 service when IPv4 addresses are no longer readily available or are otherwise constrained.

Trial #4 will evaluate how to deploy IPv6 to our Business Class customers, on a native Dual-Stack IPv6 basis.

Its good to see that this big ISP has seen the importance of an IPv6 rollout. Lets  that their trials are successful so we can see Comcast connections with native IPv6 very soon!

You can sign up for the trials right here!

Virbl is a project which gets reports of virusscanning mailservers, and put the IP-addresses that were reported to send viruses on a blacklist.

We’ve changed Virbl today, which makes it the first fully IPv6 enabled dnsbl, as far as we can tell. You could already reach Virbl via IPv6 for years, but no IPv6 hosts were served by the nameserver. rbldnsd, on which we ran Virbl before, does not understand IPv6 in its zones.

This website allows you to check the status from the 3 big Dutch news servers on IPv6

http://www.daveboonstra.nl/ipv6/server-status.php

Every year in the Netherlands we have an event called “the glass house” by radio station 3FM to raise money for a charity.

This year the collected money will go to red cross foundation to help the fight against malaria!

This year the streams are reachable by IPv6. The IPv6 streams have an advantage over the regular stream because they have been upscaled to 3Mbit/s.

The streams are:

http://www.omroep.nl/live/ipv6/3fm_sr2009_main.asx

http://www.omroep.nl/live/ipv6/3fm_sr2009_brievenbus.asx

http://www.omroep.nl/live/ipv6/3fm_sr2009_cam1.asx

http://www.omroep.nl/live/ipv6/3fm_sr2009_djcam.asx

http://www.omroep.nl/live/ipv6/3fm_sr2009_buitenshot.asx

So check the streams out, and make sure you donate a few Euro’s by requesting a good song on  http://seriousrequest.3fm.nl/

The RIPE Labs website features an interview with Alain Durand at the recent IETF 74 meeting. Alain discusses the type of IPv6 measurements he is doing at Comcast, together with the University of Pennsylvania.

Alain: Before we start I would like to stress that this is a long-term study with the aim to see how the amount of IPv6 content is increasing over time. This project is done in collaboration with Roch Guerin of the University of Pennsylvania.

RIPE Labs: How many sites do you see as being accessible through both IPv4 and IPv6?

Alain: For every scan we measured the percentage of sites from the top  one million Alexa ranked web sites that are accessible via both IPv4 and IPv6. There is a link to the raw data on the bottom of each page [seeFigure-1 below].

Read the full interview at RIPE Labs.