Peering Policy

This policy provides only guidelines and is not self-contained. Nonattached Network maintains an open peering policy and does not require a signed peering agreement.

Infrastructure

• At the moment our only peering point is KleyReX located in Frankfurt (Main), Germany.

Connectivity

• Peering networks should be able to handle 100 Mbit/s without congestion. For traffic peaks only, usually we are way below that limit.
• We do not accept new legacy IP peers. However, IPv4 is still available through the IX's route server.

Routing

• We do not accept IPv6 private prefixes (RFC4193).
• We neither accept nor announce IPv6 prefixes more specific than /48.
• We do not accept private or reserved ASN (RFC5398) from regular peers.
• Peers must not establish a default or static route to us.
• We blackhole fullbogons.

Traffic Balance

• The amount of traffic to be sent and received between Nonattached Network and the peering network should be in approximate parity, but as long as our equipment can handle it, we take this rule easy.

Contact Information

• Peers must provide a 24/7 contact point for abuse or security issues.
• Peers are expected to keep and maintain a record at the Peering Database.

Fulfillment

• Peers are expected to fulfill this peering policy for the duration of the peering.
• If a peer no longer meets the requirements stated by this peering policy then we may remove the peering without prior notice.

Beering

• Whenever two peering contacts meet in person they are encouraged to raise glases in a toast to their successful peering.