List of IPv6 tunnel brokers
| IPv6 transition mechanisms |
|---|
| Standards Track |
| Experimental |
| Informational |
| Drafts |
| Deprecated |
The following is a list of IPv6 tunnel brokers[1] that conform to the principles of RFC 3053 which describes a system with which users can request creation of an IPv6 tunnel on a host called a point of presence (PoP) which, using the tunnel, then provides the user with IPv6 connectivity.
Contents |
List of IPv6 tunnel brokers [edit]
| Name | PoPs | Locations | Subnet | Tunnelling protocols | Features | Registration | Configuration | Language | Prefix | Server implementation | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6in4 | 4in6 | TSP | AYIYA | heartbeat | RDNS | BGP | Multicast | Anonymous | Signup | Script | Manual | TSP | TIC | URL | |||||||
| 6fei | 1 | China | Unknown | Yes | Yes | No | No | No | No | No | No | No | Yes | Yes | Yes | No | No | Yes | Chinese | 2001:e88::/32 | Unknown |
| Aarnet | 1 | Australia | /56 | Yes | No | Yes | No | No | No | No | No | Yes | Yes | No | No | Yes | No | No | English | 2001:388::/32 | gogoSERVER |
| CITC | 1 | Saudi Arabia | /64 | No | No | Yes | No | No | No | No | No | No | Yes | No | No | Yes | No | No | English, Arabic | 2001:67c:130::/48 | ddtb[2] |
| gogo6/Freenet6 | 3[3] | Canada, Netherlands, Taiwan | /56 on request | Yes | Yes | Yes | No | No | No | No | No | Yes | Yes[4] | No | No | Yes | No | No | English | 2001:5c0::/32 | gogoSERVER |
| Hurricane Electric[5] | 31[6] | Canada, Europe (8 Countries), Hong Kong, Japan, Singapore, United States (9 States) | /64 default /48 on request |
Yes | No | No | No | No | Yes | Yes | No | No | Yes | Yes | Yes | No | No | Yes[7] | English | 2001:470::/32 | Unknown |
| Indonesian IPv6 | 1 | Indonesia | /64 or /48 on request | Yes | No | No | No | No | Yes | Yes | No | No | Yes | Yes | Yes | No | No | Yes | English | 2001:d68::/32 | Unknown |
| IPv6Now | 1 | Australia | /64 or /48 on request | Yes | No | Yes | No | No | No | No | No | No | Yes | No | No | Yes | No | No | English | 2406:a000::/32 | gogoSERVER |
| NetAssist | 1 | Ukraine | /64 /48 |
Yes | No | No | No | No | Yes | No | No | No | Yes | Yes | Yes | No | No | Yes[8] | English, Russian | 2a01:d0:8000::/33 | Unknown |
| NetNam | 1 | VietNam | Unknown | Yes | No | No | No | No | No | No | No | No | Yes | Yes | Yes | No | No | Yes | English, Vietnamese | 2401:e800::/32 | Unknown |
| SixXS | 52[9] | Brazil, Europe (21 countries), New Zealand, New Caledonia, Russia, United States (8 States), Vietnam | /64 default /48 on request |
Yes | No | No | Yes | Yes | Yes | No | Yes | No | Yes | Yes | Yes | No | Yes | Yes | English | Various[10] | sixxsd[11] |
| So-Net | 1 | Taiwan | Unknown | Yes | No | Yes | No | No | No | No | No | No | Yes | No | No | Yes | No | No | Chinese | 2404:80::/32 | gogoSERVER |
The columns in the table provide the following details:
| Name | The name of the organisation providing the tunnel broker, this generally maps directly to an Internet service provider. | |
|---|---|---|
| PoPs | Number of PoPs deployed | |
| Locations | Locations where the tunnel broker has a point of presence / the number of endpoints where termination can occur. | |
| Subnet | What subnet allocation the tunnel broker provides next to the /127 or /64 for the tunnel. | |
| Tunnelling protocols | ||
| Which tunnelling protocols are provided by the tunnel broker. This has impact on whether one can use a tunnel behind NAT or in cases where the IPv4 address of the user changes often. Check the relevant protocol descriptions for more details, or see this tunneling comparison. | ||
| 6in4 | Tunnelling of IPv6 packets directly in IPv4, also called 'proto-41' due to the protocol number it uses. | |
| 4in6 | Tunnelling of IPv4 directly inside IPv6 packets | |
| TSP | The Tunnel Setup Protocol. It uses a UDP-based tunnel. | |
| AYIYA | AYIYA allows users behind a NAT and/or a dynamic address to maintain connectivity even when roaming between networks. It uses a UDP-based tunnel. | |
| heartbeat[12] | Heartbeat tunnels are 6in4 based but allow for dynamic addresses to be updated automatically without user intervention | |
| Features | RDNS | Whether the tunnel broker provides reverse DNS delegations. |
| BGP | Whether the tunnel broker optionally accepts a BGP peering allowing one to announce one's own address space. | |
| Multicast | Whether the tunnel broker optionally provides IPv6 Multicast over a tunnel. | |
| Registration | ||
| The available registration methods. | ||
| Anonymous | One can use the service without registration | |
| Signup | One is required to sign up and provide details (at minimum an email address) | |
| Configuration | ||
| What methods are available for configuring tunnels and subnets provided by the tunnel broker | ||
| Script | Indicates that the broker provides a script through the website. | |
| Manual | That one can set up the tunnel manually if wanted | |
| TSP | Uses the Tunnel Setup Protocol (TSP), thus requires gogoclient | |
| TIC | Uses the Tunnel Information and Control (TIC)[13] protocol as implemented by AICCU, AVM FRITZ!Box, Draytek, Motorola and others | |
| URL | URL indicates that changes to the tunnel parameters can be made on the website (e.g. enable/disable or change the endpoint) | |
| Language | Which languages are supported by the providers web interface and other communication channels. | |
| Prefix | Which IPv6 prefix(es) are used for the tunnel broker. If a /32 is indicated, generally only a portion is used for tunnels/subnets for the tunnel broker or the name of the tunnel broker service that is providing the address space. | |
| Server implementation | The implementation used by the tunnel broker | |
Implementations [edit]
There are a variety of tunnel brokers that provide their own implementations based on different business goals. Listed here are the common implementations as used by the listed IPv6 tunnel brokers.
Gogo6 gogoSERVER [edit]
gogoSERVER (formerly Gateway6) is used by the Freenet6 service, which is the first IPv6 tunnel broker service, going into production in 1999. It was started as a project of Viagenie and then Hexago was spun off as a commercial company selling Gateway6, which powered Freenet6, as their flagship product. In June 2009 Hexago became gogo6 through a management buyout and the Freenet6 service became part of gogoNET, a social network for IPv6 professionals.[14]
SixXS sixxsd [edit]
SixXS's sixxsd is what powers all the SixXS PoPs. It is a purpose built software for the purpose of tunneling at high performance and low latency. Development started in 2002[15] and has evolved into the current v4 version of the software.
CITC ddtb [edit]
CITC Tunnel Broker, run by the Saudi Arabia IPv6 Task Force, uses their own implementation of the TSP RFC named 'ddtb'.
References [edit]
- ^ AICCU - Tunnelbroker Support, lists tunnel brokers that are supported and unsupported by AICCU
- ^ CITC Tunnel Broker
- ^ gogo6 Service Status
- ^ gogoNET signup for Freenet6
- ^ tunnelbroker.net
- ^ HE Tunnel Server Status
- ^ HE Endpoint update
- ^ NetAssist URL Update instruction
- ^ SixXS Points of Presence
- ^ SixXS Prefixes
- ^ sixxsd
- ^ heartbeat
- ^ TIC
- ^ What is gogoNET?
- ^ SixXS History
|
||||||||||||||