Asiera Public Peering Policy

Introduction

Asiera publishes IPv4 and IPv6 routes to both its infrastructure and its clients via a single BGP Autonomous System - AS 1213. We maintain an open public peering policy : we will generally entertain peering requests from any organisation at public exchange points where we have a presence.

We currently support both IPv4 & IPv6 unicast.

While Asiera is open to PNIs - Private Network Interconnects - we operate a more selective private peering policy. In all cases Asiera prefers public peering at an open peering exchange.

Peering Requirements and Acceptable Usage

The following requirements apply to public peering relationships with Asiera - and complement the requirements of the IXPs at specific peering points. Private peers are subject to additional requirements - to be agreed by both parties.

• Both Asiera 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 Asiera, or alter 'next hops' such that they are routing to Asiera 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 practices
• Asiera reserves the right to discontinue any peering agreement at any time, and for any reason, with or without notice. However Asiera will endeavour to provide written notice (email) in advance of any such action. Further, Asiera reserves the right to deny a prospective network for peering for any reason.

Prospective peers should:

• 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, to which Asiera can escalate any routing/peering issues
• Notify Asiera (via email) of any planned or unplanned maintenance

Peering Details

Asiera maintains up-to-date RIPE IRR objects :

• AS1213
• AS-HEANET lists all ASNs used by both Asiera and our clients

Asiera also maintains a Peering DB entry - which lists all Data Centres in which we maintain a presence.

Please send all peering requests and peering information requests to peering@heanet.ie.