Peering Policy

Introduction
This Peering Policy describes and defines the minimum criteria that LambdaNet Communications (LambdaNet) has established for engaging in peering relationships between the LambdaNet Internet network and other Internet networks in the various regions of the world. This global network is represented by a single AS number: 13237.

This peering policy applies to all requests for peering with AS13237. It is effective on 1st August 2006 and is being reviewed periodically. LambdaNet reserves the right to apply the criteria set forth in this document to all existing peering relationships at any time.

Final qualification for Peering is determined through business analysis. Apart from the criteria below - the cost/benefit analysis must show the Peering as being beneficial for all LambdaNet organisations.

Operational and Backbone Requirements

1. Peer must operate a fully redundant network capable of handling a single-node outage in each network without significantly affecting the traffic being exchanged.
2. Peer must operate a Network Operations Centre (NOC) which is staffed 24 x 7 x 365.
3. Peer must cooperate in case of network abuse. On occurrence of Denial of Service attacks Peer shall implement filters on request.

1. Each Internet Network will announce consistent customer routes from a single AS at all interconnection points.
2. Each Internet Network will implement closest-exit routing, if not otherwise agreed.
3. All traffic exchanged between LambdaNet and Peer shall be carried over the peering connections established between both networks.
4. Routes should be aggregated as much as possible. LambdaNet will not accept any announcement smaller than /24.
5. Routes must be registered with a recognized route registry: ARIN, RIPE or APNIC. Peers must enforce routing integrity by means of filters to their customers.
6. No route of last resort (default route) will be directed at LambdaNet.
7. Existing transit customers cannot be peers in the same region.

1. Public Peerings shall be established on multiple locations.
2. Aggregated average traffic between LambdaNet and Peer shall be at least 20 mbps.
3. LambdaNet reserves the right to set up public peerings on a test basis.
4. A network may submit a peering request once every three months.

1. LambdaNet requires 50 mbps of aggregated average traffic to justify a private peering relationship.
2. Private Interconnects shall be done on one of the following interface types: GbE, 10GbE, STM-4, STM-16.
3. Private Interconnects shall be backed by private or public interconnects in other physical locations.
4. Upon request Peer shall execute a LambdaNet Non-Disclosure Agreement (NDA).
5. Upon request Peer shall provide LambdaNet with a readable hard or soft copy network map. This map shall show network topology details and active IP capacity between backbone nodes.
6. Private Peering shall be backed by a contract.

7. Each Party will bear its network cost. Expenditures for interconnection are shared between Lambdanet and Peer.

Please send all questions/inquiries about peering in English to:
peering@lambdanet.net