Peering Policy

We maintain an open peering policy, but we would prefer not to enter into a formal peering contract (Zero-Settlement Peering). We prefer to secure BGP sessions with MD5 passwords. We advertise AS-FREINET on all peering sessions, unless agreed upon otherwise. Peers should advertise only their registered AS macro.

Neither party will send traffic to destinations not announced by the other party, to the other party's network. This also means that neither party will establish a default route directed towards the other. We will keep our AS object updated at all times, and require our peering partners to do the same.

Advertisements with reserved networks and subnets are never permitted. This includes RFC1918, IANA reserved networks, default route, our own subnets and some others. Prefixes longer than /24 are filtered at ingress. Advertisements with reserved AS numbers in the path (ie 64512 - 65535) are not permitted.
Customer ingress communities are never transitive. Route flap-dampening according RIPE-229 is applied.