Voxel dot Net (AS 29791) Settlement-Free Peering Policy
Last Revised: 2008-09-23
Introduction
Voxel maintains a selective peering policy, and will generally entertain peering requests from organizations which adhere to the below requirements and bring some form of value to the table, such as, for example, increased reliability and inter-provider capacity.
The following set of requirements applies to public/exchange peering relationships with Voxel. Private peers are subject to an additional set of requirements, which will be made available privately.
Peering Requirements
- Prospective peers must maintain a PeeringDB record containing up-to-date contacts and technical specifications.
- Prospective peers must maintain a contiguous IP backbone, and advertise to Voxel a consistent set of routes in every peering location, unless otherwise mutually pre-arranged.
- Prospective peers must maintain a professionally staffed Network Operations Center (NOC), with the ability to escalate outages to an engineer 24 hours a day, 7 days a week, 365 days a year.
- Prospective peers must also provide Voxel with a security point of contact, and assist with the mutual troubleshooting of any inter-provider security issues, such as Denial of Service (DoS) attacks, on a 24x7x365 basis.
- Prospective peers must notify Voxel of planned and unplanned network maintenance via e-mail.
- Routing information is exchanged with peers via the Border Gateway Protocol version 4 only. Peers may not, at any time, static route to Voxel, or alter 'next hops' such that they are routing to Voxel for networks which are not being advertised across the peering session. Such activities are monitored for closely, and are considered grounds for immediate disconnection.
- Peers must maintain ample capacity to the exchange point(s) at which they interconnect with Voxel, and proactively upgrade these connections such that they are never saturated.
- Peers must maintain an Internet Routing Registry (IRR) AS-MACRO, providing accurate information on the prefixes which peers and their customers intend to advertise. Voxel may (prefix-list and/or AS-path) filter peers against data published in the IRR, or use the IRR as a tool for detecting any routing-related anomalies.
- Voxel practices 'hot potato' routing to its peers, and will not honor MEDs as a matter of standard practice. Requests for 'cold potato' routing configurations with MEDs may be submitted by networks meeting Voxel in multiple geographic regions, and will be evaluated on an Individual Case Basis (ICB).
- Voxel will not enter into a settlement-free peering relationship with current IP transit customers (or their customers, ...), or organizations that have purchased IP transit services from Voxel in the past six (6) months.
- Peering is a privilege and not a right. Unless otherwise specified per contract, Voxel reserves the right to discontinue any peering arrangement at any time, and for any reason, with or without notice.
- Voxel reserves the right to deny a prospective network for peering for any reason, published or unpublished.
Technical Specifications
Technical specifications for Voxel's peering footprint can be found at:
This site will be continually updated with any changes.
Administrative Contact
To initiate the peering evaluation process, or for policy/administrative requests concerning an existing peering relationship, please send e-mail to peering (at) voxel dot net.