We have an open peering policy subject to the following requirements:

Requirements

• A registered, unique ASN allocated within the DN42 registry
• Complete, updated, and accurate DN42 registry records containing:
  • An email address
  • Prefix information for IPv4/IPv6 (we filter peer routes based on valid objects)
• A reasonable latency to one of our endpoints
• Network router capable of running BGP
• No default route or the use static routes that are not authorized

We encourage peering wherever reasonable as it contributes to our experimentation.

Route Policy

We currently support and/or filter the following:

• BGP Graceful Shutdown (RFC8326)
• Blackhole Community (RFC7999)
• DN42 Bogon filtering (addresses not expected on DN42)
• Well-known Communities (RFC1997)
• RPKI invalid route rejection (Valid and Unknown permitted)

See communities for additional information

Peering Requests

You can submit peering requests via Pull Request on our dn42-peers repository.

Alternatively, you can click here to submit a peering request via Google Form.