Peering.as49028

POLICIES

Introduction:

D-Lake has a selective peering policy. The Peers are selected based on, the AS path between Peer ASN and D-Lake ASN, capability and mutual benefit for both networks, in particular, D-Lake prioritizes content providers from the following sectors :

• content provider (CDN, hosting, SaaS)
• media.
• video games company.
• movie / animation company.

Peering is based on good will and will be treated on best effort only. Peering Partner must use it in accord with these principles and undertakes not to hold D-lake responsible in case of loss or damage during interruption of peering for any period of time

Peering Policies :

Requirements :

• Peering partner must have a PeeringDB page with up to date information
• Peering partner must operate a NOC which is reachable 24/7/365 by Email or Phone.
• Peering partner should run it's own AS to peer with D-LAKE and announce at least a /24 For IPv4 or a /48 for IPv6.
• Peering partner should announce route aggregated as much as possible.
• Peering partner should not send RFC 1918 prefixes (IPv4) or default route.
• Peering partner should cooperate in case of network abuse.
• D-Lake reserves the right to evaluate the peering for a non determinated period.
• In the event of abuse, obvious incident, abnormal traffic, or any other reason which may lead D-Lake to believe that the peer represents a danger to its own infrastructure, D-Lake reserves the right to cut off sessions. for an indefinite period.

Traffic Requirements for public peering

• there is no traffic requirements for peering with D-Lake, but the benefit must be clear (the first criteria beeing the reduction of AS path lenght).

Traffic Requirements for private peering

• supported connexion : 10Gbit/s and 100Gbit/s.
• Interconnection must be 10 Gigabits Ethernet (10GbE LR) or 100 Gigabits Ethernet (100GbE LR).
• for 10 Gbit/s connectivity, D-Lake invites you to contact us to build together the terms of our agreement.
• The PNI is free of charge up to 100Gbit/s of capacity. Above this value please, contact us for more details.
• For Symmetric or unbalance traffic (between ingress and egress) up to a ratio of 2 to 1 the peering is free regardless of the amount of traffic.

Traffic Requirements for Locally hosted Cache

• > 10Gbit/s, D-Lake give you the possibilities to deploy caching servers on its network.
• Deployment of theses caching servers would respect D-Lake constraint.

Configuration :

Route exchange are done using BGP only. We will announce the routes registered for each AS we are announcing under the as-set described in our peering DB page. Maximum prefix for IPv4 and IPv6 sessions must follow the value indicated in our peering DB page. These value can change at any moment without any warning. We recommend that our peering partner use an automatic tool to check these values and modify the parameters of the BGP session dynamically. Peering partner must never send traffic to destinations not announced by D-Lake, and so must never configure a static default route directed to D-Lake.

Routing Policies :

Partners and customers

D-Lake announces only it’s own routes summarized and expect the same from its customers and partners. Customers IPv4 routes are announced as received, and we do not implement route aggregation for customers prefixes. IPv6 routes must be aggregated, and non-aggregated routes are dropped. We only accept routes originated by our customer AS in conformity with IRR allocations and records. We reserve the right to implement filtering based on RPKI at any time, and we expect our partners and customers to sign their route announcements now.

Global rules

Filtered routes we do not accept (routes are dropped) :

• Subnets in our own IP blocks
• IANA reserved IP blocks
• Bogon Networks (Our reference source is https://team-cymru.org/Services/Bogons/fullbogons-ipv4.txt )
• Prefixes longer than /24 for IPv4 or /48 for IPv6
• Subnets with private ASes in the AS Path

RIPE/ARIN/APNIC/AFRINIC objects must be created and up to date for the routes to be accepted on our network.

BGP Policies

The following communities can be used by peers and customers Note: These communities are evaluated on a "first match wins" basis

Change local Pref

Blackhole

D-Lake support the Blackhole well know community as defined in the RFC7999 65535:666 - Blackhole prefix up to /32 (IPv4) and /128 (IPv6)

AS Path Preprend

AS-Path prepending is allowed to use preferenced routes on the network

Peering Request :

Peering Partner must have an account on PeeringDB and an up-to-date page. Our contact for a peering request are registered under the “Contact Information” session on our ⎋ PeeringDB page.