PeeringPolicy/peering_policy.html

23 lines
1.6 KiB
HTML
Raw Permalink Normal View History

2016-01-10 13:58:04 +01:00
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>AS49009 - Freifunk Hamburg - Peering Policy</title>
</head>
<body>
<h1>Freifunk Hamburg</h1>
<p><a href="https://hamburg.freifunk.net">Freifunk Hamburg</a> is a non commercial open initiative to establish a free radio network (WLAN) in the city of Hamburg. It is part of the international movement for free and wireless radio networks.</p>
<h2>Peering Policy AS49009</h2>
<p>We have an open peering policy and we do not require a written contract. As we are a voluntary project, we prefer to peer with route servers to keep workload low. Please check if you recieve our prefixes through them already. However, we would really appreciate receiving additional routes via a private peering if possible. If it is possible for you to support us with transit, this would also help us a lot.</p>
<p>For more information please check our <a href="https://as49009.peeringdb.com">peeringdb record</a>.</p>
<h3>BGP readable communities</h3>
<ul>
2017-01-16 11:56:24 +01:00
<li><b>49009:10x</b>: Learnt @<a href="https://www.iphh.net">IPHH</a>/Hamburg</li>
<li><b>49009:20x</b>: Learnt @<a href="https://www.work.de/">n@work</a>/Incolocate/Hamburg</li>
<li><b>49009:30x</b>: Learnt @<a href="https://www.artfiles.de/">artfiles</a>/Level(3)/Hamburg</li>
2016-01-10 13:58:04 +01:00
</ul>
<h3>Pico Peering Agreement v1.0</h3>
<p>Within our mesh network, we adhere to the <a href="http://www.picopeer.net/">Pico Peering Agreement</a>. In addition, we try to implement its fundamental idea also in our backbone infrastructure.</p>
</body>
</html>