Points of Presence

The SixXS system provisions multiple PoPs. A PoP (Point of Presence) is a router/machine serving IPv6 in IPv4 tunnels. In RFC3053 IPv6 Tunnel Broker terminology a PoP would be called a Tunnel Server, while SixXS is the Tunnel Broker. Each one of these PoPs is under complete control of the owner and using its own DFP for serving out addresses to its clients under the policies defined by PoP's owners. SixXS manages the day to day aspects of these PoPs and provides the software and knowledge to run them properly. To keep the quality high we've defined a couple of requirements for an ISP to become a SixXS PoP. Additional PoPs are welcome from all around the world.

Which PoP should I use?
What can SixXS do for an ISP?
What can SixXS do for endusers?

The status of the PoPs can be checked on the PoP Status/Overview page. Trouble Tickets can be found in the Tickets Tracker. PoP Up/Down status updates are available through RSS and also on the IRC channel.

New PoP's

New PoP's are always welcome to join, which is completely free, the PoP is not required to be public and control & usage depend on the policy of the owner. Contact us and ask for more information when needed. You will at one point have to fill in the requirements form, though one can submit that at once to get the short process jumpstarted.

Reasons for an ISP to setup a PoP

Current PoPs

The following maps show the physical locations of the 38 PoPs spread over 20 countries that the SixXS Tunnel Broker system currently manages worldwide. See the list of PoP prefixes for an overview of the prefixeses being used by these PoPs.

The PoP status can be Up, Down or Planned.

	Belgium
	Brussels		bebru01	Easynet
	Brussels		bebru02	BELNET, The Belgian Research and Education Network
	Brazil
	Uberlandia		brudi01	Companhia de Telecomunicações do Brasil Central
	Denmark
	Copenhagen		dkcph01	Phonera
	Copenhagen		dkcph02	Fullrate A/S
	Estonia
	Tallinn		eetll01	Linxtelecom Estonia
	Finland
	Helsinki		fihel01	DNA Oy
	France
	Marseille		frmrs01	Jaguar Network SARL
	Germany
	Cologne / Koln		decgn01	NetCologne Gesellschaft fur Telekommunikation mbH
	Duesseldorf		dedus01	SpeedPartner GmbH
	Hamburg		deham01	Easynet
	Hamburg		deham02	Easynet
	Muenchen		demuc02	M-net Telekommunikations GmbH
	Ireland
	Dublin		iedub01	HEAnet
	Galway		iegwy01	Airwire
	Italy
	Torino		ittrn01	ITgate
	Netherlands, The
	Amsterdam		nlams04	Scarlet Internet B.V.
	Amsterdam		nlams05	SURFnet
	Breda		nlams01	Concepts ICT BV
	Ede		nlede01	BIT BV
	Haarlem		nlhaa01	Leaseweb B.V.
	New Zealand
	Wellington		nzwlg01	Advanced Computer Solutions (ACSData)
	Norway
	Oslo		noosl01	Phonera
	Poland
	Poznan		plpoz01	Poznan Supercomputing and Networking Center
	Warsaw		plwaw01	ICM
	Portugal
	Lisboa		ptlis01	NFSi Telecom, Lda.
	Slovenia
	Maribor		simbx01	Amis
	Sweden
	Stockholm		sesto01	Phonera
	Switzerland
	Zurich		chzrh01	IP-Man
	Zurich		chzrh02	Init Seven AG
	United Kingdom (Great Britain)
	London		gblon02	Goscomb Technologies
	United States
	Ashburn, Virginia		usqas01	OCCAID Inc.
	Boston, Massachusetts		usbos01	OCCAID Inc.
	Chicago, Illinois		uschi02	Your.Org, Inc.
	Dallas, Texas		usdal01	Highwinds Network Group Inc
	Los Angeles, California		uslax01	Highwinds Network Group Inc
	Newark, New Jersey		usewr01	OCCAID Inc.
	Phoenix, Arizona		usphx01	Highwinds Network Group Inc

nlams01 was relocated to Breda, though it still uses Concepts's Amsterdam address space.
deham01 was formerly demuc01, when it was still located in Muenchen.

Former PoPs

Following PoP's where previously also available but where shutdown due to the shutdown of the 6bone.

	Germany
	Muenchen	demun01	PSINet Europe
	Netherlands, The
	Amsterdam	nlams02	IPng (Intouch)
	Amsterdam	nlams03	AMS-IX (Amsterdam Internet Exchange)
	United States
	Atlanta, Georgia	usatl01	OCCAID Inc.
	Chicago, Illinois	uschi01	OCCAID Inc.

PoP Naming Scheme

PoPs are named according to UN/LOCODE in the format of a two letter country code followed by a three letter city code and a two digit sequence number.

Tunnel Naming Scheme

Tunnel endpoints will have two DNS forward and reverse entries:
gw-tunnelnumber.city-sequencenumber.tld.sixxs.net
cl-tunnelnumber.city-sequencenumber.tld.sixxs.net
The gw stands for Gateway and is on the side of the PoP, ::1 in the /64. That address should only appear in traceroutes. cl stands for client and it is the endpoint of the client, ::2 in the /64.

Examples:

• gw-20.ams-02.nl.sixxs.net - Gateway endpoint of tunnel 20 on PoP nlams02.
• cl-42.dub-01.ie.sixxs.net - Client endpoint of tunnel 42 on PoP iedub01.
• cl-13.pub-poz-01.pl.sixxs.net - Client endpoint of tunnel 13 on public part of PoP plpoz01.