Peering Policy

Introduction

The Peering Policy of Free Pro has been established to define the minimum requirements to establish a peering relation with Free Pro. We are currently running one AS for our network. (AS30781) Minimum Requirements :

Minimum Requirements

• Peering partner must operate a NOC which is reachable 24/7/365 by Email,Phone and Fax.
• Peering partner should run it's own AS to peer with Free Pro 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 exchange with Free Pro a minimum of 100Mb.
• Peering partner should cooperate in case of network abuse.
• Peering partner will run a non software router to peer with Free Pro.
• Peering partner should get a router located in the Peering Exchange Point (No MPLS pipe).
• Free Pro reserve the right to evaluate the peering for a non determinated period.
• Free Pro is sending MED to any peers so we expect you to do the same.

IPv4/IPv6 Routing Configuration

The route exchange will be done over BGPv4. We will announce the routes that are registered for each AS we are announcing under the as-macro AS-FREEPRO for IPv4 or AS-FREEPRO-V6 for IPv6. We will reannounce customers routes as we receive them. Peering partner will not send traffic to destinations not announced by the other party through the other party's network. This mean that the Peering partner will not establish a default route directed to Free Pro network or use static routes to pass trafic through Free Pro. The peering is based on good will and best effort. Peering partner can't be liable on Free Pro in case of loss or damage during interruption of peering for any period of time.

Peering Locations