HEAnet Public Peering Policy
HEAnet (AS 1213) maintains an open public peering policy and will generally entertain peering requests from any organisation at public exchanges points where we have a presence.
We currently support IPv4 unicast & multicast and IPv6 unicast. We are more than happy to work with IPv6 newcomers and provide any assistance we can.
Private peering requests are also considered, however we operate a more selective private peering policy and in all cases prefer public peering at an open peering exchange.
Peering Requirements and Acceptable Usage
The following requirements apply to public peering relationships with HEAnet and complement the requirements of the IXPs at specific peering points.
Private peers are subject to additional requirement, to be agreed by both parties.
Prospective peers should:
- Both HEAnet and a prospective peer agree to allow their members and customers to exchange traffic via the public exchange point.
- There will be no charge ("zero settlement") for either traffic exchanged or traffic content.
- Each peer will undertake the cost of connecting its own network to the public exchange point.
- Routing information is exchanged with peers via the Border Gateway Protocol version 4 only. Peers may not, without prior explicit
written (email) permission, statically route to HEAnet, or alter 'next hops' such that they are routing to HEAnet for networks which are not
being advertised across the peering session
- Traffic exchange is not permitted for networks that are not customers of either peer, except with the explicit written (email) agreement between parties.
- Peers should monitor common traffic and must maintain sufficient bandwidth to the exchange points.
- Each network will, to the best of their ability, ensure that users and user networks behave in a manner that does not adversely affect the operations
of other networks and users, and will do so within generally accepted security guidelines. Each network has the right to protect its
technical resources by following generally accepted operational practises.
- HEAnet reserves the right to discontinue any peering agreement at any time, and for any reason, with or without notice. However HEAnet will endeavour to provide written notice (email) in advance of any such action. Further, HEAnet reserves the right to deny a prospective network for peering for any reason.
- Maintain a PeeringDB record with up-to-date information.
- Maintain a RIPE (or similar) IRR entry with up-to-date information.
- Maintain a staffed NOC, available to escalate any routing/peering issues to.
- Notify HEAnet (via email) of any planned or unplanned maintenance.
HEAnet maintains up-to-date RIPE IRR objects for AS1213. Our announcements are available as AS-HEANET.
HEAnet also maintains a PeeringDB entry which can be found at:
HEAnet have a peering presence in the following locations:
- Telecity, Citywest (LAN1).
- InterXion DUB1, ParkWest (LAN2).
Private Peering at:
- BT Application Hosting (EsatX), Citywest, Dublin.
- InterXion DUB1, Park West, Dublin.
- ServeCentric, Blanchardstown, Dublin.
Please send all peering requests and peering information requests to email@example.com.
Revision: 0.3. Revision Date: 2011-05-19.
Original Publish Date: 2010-01-13