IPv6 in Sixty Seconds – gogoCPE

MONTREAL (February 4, 2011) – gogo6 inc., the leading provider of IPv6 products, community and services, today announced the release of gogoCPE version 1.0 – a small v6 adaptor for the home that can be installed and providing IPv6 within a minute. Designed to work with, rather than replace home networking equipment, the gogoCPE can be used to deploy IPv6 using IPv4 or to deploy IPv4 using IPv6 – both resulting in a dual-stack home network. Early customers of the gogoCPE include SingTel, Comcast and Globe Telecom.

The gogoCPE is plug ‘n’ play simple and designed to be installed by the end user without any support. The gogoCPE uses the same code as the gogoCLIENT which has reliably provided IPv6 to over 150,000 users of the Freenet6 service.

The gogoCPE supports the most popular transition technologies including TSP, DS-Lite, 6RD, DSTM and L2TP. It is compatible with the gogoSERVER and other manufacturer systems. Its wide technology support allows it to work in any IPv4/v6 network scenario, including:
Providing IPv6 to existing and new customers with IPv4 home routers in an IPv4 network.
Providing IPv4 to new customers with IPv4 home routers in an IPv6 network.
Providing IPv6 to new customers without IPv4 home routers in an IPv4 network.

“Hands down the most difficult part of introducing IPv6 into a broadband network is the home. This is where a majority of the IPv6 costs lie and where service providers have the least control. In a vast majority of the cases the home networking equipment is either not upgradable or owned by the end user making IPv6 synonymous with installing new equipment,” said Bruce Sinclair, gogo6 CEO. “The recent depletion of IPv4 addresses from the IANA pool increases the pressure on service providers to find a simple yet effective solution to offer v6 and v4 by way of v6. Service providers can quickly introduce IPv6 into their networks with a single 1U gogoSERVER and one gogoCPE per home.”

Availability and pricing
The gogoCPE is available today after being tested by service providers around the world. In addition to being sold in volume individual gogoCPEs are available on the gogo6 website. These units are preconfigured to work with Freenet6 making them plug ‘n’ play ready out of the box. Individual units cost $99 plus shipping and handling. Volume pricing is lower.

For detailed information on the gogoCPE go to: http://bit.ly/gogoCPEinfo
To purchase individual units of the gogoCPE go to: http://bit.ly/gogoCPEbuy
To request a volume quote contact: [email protected]

Top 10 tasks for IPv6 application developers

Many IT people, who are unfamiliar with IPv6, believe the responsibility for IPv6 deployment falls on the network-teams. However, those who are knowledgeable about IPv6 realize the migration to IPv6 will involve any system that uses an IP address. As the network teams prepare the infrastructure for the addition of IPv6 we should alert our application developers and make sure they are ready for the challenge that awaits. This article contains some of the key issues that application developers will need to know as they make their applications function properly in a multi-protocol world.

More from Network World…

2010 in IP addresses: 225 million down, 496 million to go

As of January 1, 2011, the number of unused IPv4 addresses stands at 495.66 million. Exactly a year earlier, the number of available addresses was 721.06 million. So we collectively used up 225.4 million addresses in 2010. 242 million, really, if we ignore the unusual circumstance that Interop gave back nearly 17 million addresses.

At first glance, this suggests that we have two more years of IPv4 addresses left. But it’s not that simple: Asia is almost certainly going to run out before year end. And that means really running out, as in: sorry, no addresses for you.

More from Ars Technica…

European Commission Researching IPv6 Deployment

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