DevStorage Peering Policy
This document sets forth DevStorage’s policy for settlement-free peering.
DevStorage is listed in PeeringDB, the industry database for peering information for network operators. Please review our PeeringDB entry for the most current list of DevStorage’s public and private peering locations. Peering requests must be submitted to DevStorage or rather AS210633 via online form through https://as210633.net/peering. DevStorage reserves the right to accept or reject a peering request in its sole discretion and may but has no obligation to explain the basis for its decision.
DevStorage has an open peering policy, subject to certain requirements. At times, local infrastructure requirements or constraints may make it necessary for us to modify these requirements on a temporary or long-term basis.
DevStorage peers with route servers in Internet Exchange, and we send our routes to them. However, we do have restricted policy on which routes we accept.
General Peering Policy
General requirements for those networks who wish to peer with DevStorage are:
- A fully redundant network with sufficient capacity to exchange traffic without congestion.
- The DevStorage ASN (AS210633) is a full-IPv6 network. We therefore only peer over IPv6.
- Publicly routable ASN
- Publicly routable address space (at least one /48 of IPv6 space)
- 24x7 NOC contact capable of resolving BGP routing issues, denial of service attacks and security issues (or more generically, network issues)
- Maintaining accurate and up-to-date peeringDB information
- Presence at one or more of the Internet Exchanges or private peering interconnection facilities listed for DevStorage in PeeringDB
- Routes being sent should pass ROA validation (valid, instead of unknown)
- MD5 passwords are requested for all BGP sessions
- Minimum traffic requirements as set forth below
- Traffic: We prefer to exchange routes via route servers as we already have session with them. If you wish to have direct BGP session with us, ASNs exhibiting more than 1Gbps of DevStorage traffic at peak, in either direction, can request peering via a bilateral BGP session over an Internet Exchange, please contact email@example.com
- Diversity: A requesting network should have the ability to peer with DevStorage at a reasonable level of diversity (e.g., metro, facility, router) in a location where DevStorage has a peering point of presence
- Traffic: ASNs exhibiting more than 10Gbps of DevStorage traffic at peak, in either direction, can request private peering via a bilateral BGP session over dedicated port(s). We prefer 100GE ports for such private peering but also accept multiple 10GE ports. Please contact firstname.lastname@example.org for detailed information.
- DevStorage prefers private peering, also known as Private Network Interconnect (PNI), for networks with sufficient traffic volume.
- DevStorage may remove a public peering session once a corresponding PNI has been established.
In general, networks that have established peering sessions with DevStorage will receive all DevStorage routes within that area. At times, local infrastructure requirements or constraints may result in a more limited set of routes being advertised from DevStorage. These routes would be relevant to the local peering region.
We suggest peers set a max-prefix of at least 30 (IPv6) routes on peering sessions with DevStorage.
DevStorage reserves the right to grant or refuse peering with a requesting network, whether or not the requesting network meets the criteria set forth in this DevStorage Peering Policy. DevStorage also reserves the right to: (1) terminate peering for any reason upon 30 calendar days prior notice to the other party; and (2) to terminate peering immediately should any event detrimentally affect, or threaten to detrimentally affect, the DevStorage network. Examples of such events include BGP session flaps, route flaps, excessive routes, denial of service attacks or spam.