Technology Status
This table gives an overview of the various technologies used and sub-projects that run in the SixXS project.
For a historical overview of the SixXS PoP code see the SixXS History page.
We of course accept new wishlist items, thus if you have any, don't hesitate to submit them to the forum or through our feedback channels.
| Technology Name | Status | Description |
| Website | Production | The Web User Interface |
| AICCU | Production | Tool to automatically configure IPv6 connectivity |
| Heartbeat | Production | Protocol for getting the a tunnel to be pointed to your current location |
| TIC | Production | Protocol for retrieving Tunnel information and optionally controlling it |
| TSP | Alpha; Internal testing of AICCU and server-side implementation | Tunnel Setup Protocol: like TIC, but XML based and can't be used to control tunnels and per default misses functionality in the client to be completely useable by SixXS PoPs |
| AYIYA | Production | Anything in Anything - used mainly for IPv6 in IPv4 UDP and thus NAT-crossable tunnels |
| Multicast | Beta; requires ecmh to have MBGP support to properly connect to Renater and thus m6bone. | Allows one to setup Multicast connectivity to others on the Internet.
Multicast is available on some PoPs but isn't global on most due to this.
|
| GRH | Production | Ghost Router Hunter - used for debugging IPv6 routing issues |
| Forum | Production | Your friendly forum |
| Ticket Tracker | Production | Got a problem? Report it in the Ticket tracker |
| Traffic Statistics | Production | How much traffic are the PoPs doing? |
| Latency Service | Production | Check up on your latency and latency around the world as seen by the PoPs |
| IPv6 Only Bittorrent Tracker | Beta; Public Testing stage | Large file transfers from fast seeds |
| BGP on the PoPs | Wishlist | Allows one to use multiple tunnels for a single /48, even announcing seperate /64s from that block.
These announcements will only be used internally on the PoP though and won't appear on global BGP.
The downstream client will only get a 'default' route, not a full feed as with the amount of clients it would become very heavy to update everyone when there is a route change in the DMZ.
Next to that fact that the PoPs themselves don't have BGP connectivity upstream.
|
| Community Edition | Wishlist | Allow the community to rate and approve requests |
|