Peering Policy

To view our peering policy in PDF format download http://www.mojohost.com/peering_policy.pdf
To download our peering request form download http://www.mojohost.com/peering_form.pdf

This document serves as a guideline for Internet Service Providers seeking an open peering relationship with MojoHost (AS:27589), Inc. All questions regarding this document, or requests for Peering, should be directed to peering@mojohost.com .

Public Network Exchange Points:

MojoHost (AS:27589) is currently accepting applications for public peering interconnections at the following public network exchange points:

Exchange

Location

Topologies Supported

Terremark (NAP of the Americas)

Miami , FL. USA

100/1000Base-T (TX/FX)

Eligibility Requirements:

In order to establish a public peering interconnection (PPI) to MojoHost (AS:27589), the candidate’s network should meet the following criteria:

§ The candidate's network must exchange a significant amount of traffic with AS27589 either originated from its own network (peer-as) or from the networks taking transit from it (origin-as). Generally speaking, at least 20Mb/s of aggregate traffic in either direction, measured using 95th Percentile, should be exchanged on an ongoing basis in order for MojoHost to consider establishment of a peering relationship. However, the minimum acceptable amount of traffic remains at the discretion of MojoHost, and all requests for public peering interconnection will be evaluated on a case-by-case basis.

Operational Requirements:

§ Both MojoHost and the candidate must exchange accurate contact information for their Network Operations Center (NOC) or other appropriate technical operations personnel that must be reachable either by e-mail or phone on a 24/7/365 basis.

§ Both Mojohost and the candidate shall provide an appropriate escalation path for resolution of network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours.

§ Both Mojohost and the candidate will make a good faith effort to facillitate communication regarding any network maintenance that will affect traffic exchange across the peering connection(s).

§ Both MojoHost and the candidate must be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time.

Technical Requirements:

§ Both MojoHost and the candidate must register their announced routes and routing policies in a public Internet Routing Registry (IRR) database, for the purposes of establishing and maintaining appropriate filters. Both parties shall make good faith efforts to keep this information up to date.

§ Both MojoHost and the candidate must accept announcements for all authorized prefixes that are properly documented in the IRR database that are announced by the other party. Both parties must make every reasonable effort to ensure that appropriate outbound route filtering is implemented and maintained to prevent any unauthorized prefixes from being announced across the peering session(s).

§ Both MojoHost and the candidate shall announce only their own routes and the routes of their transit customers to the other party. No other routes are permitted, and may be filtered if detected.

§ Both MojoHost and the candidate will implement MD5 authentication on all BGP peering sessions established between the two entities.

§ Both MojoHost and the candidate must make every effort to aggregate prefix announcements across the peering connection(s) wherever possible when specific announcements are not required for legitimate traffic engineering purposes.

§ Both MojoHost and the candidate must make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network.

§ Neither MojoHost or the candidate shall ever establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not intentionally announced to them via BGP. Neither party shall alter, sell, or give next-hops to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law.

General Notes:

§ Either MojoHost or the candidate may, at their discretion, temporarily suspend the peering relationship without prior notice should any violation of this policy occur.

§ Either MojoHost or the candidate may terminate an existing peering relationship for any reason with 30 days of notice.

§ MojoHost reserves the right to accept or decline any request for peering for any reason.

§ MojoHost reserves the right to modify this policy at any time.

Application Procedure:

To view our peering policy in PDF format download http://www.mojohost.com/peering_policy.pdf
To download our peering request form download http://www.mojohost.com/peering_form.pdf

If your agency agrees with all the terms of this policy and would like to pursue a peering relationship with MojoHost, please complete the peering request form and email it to: peering@mojohost.com.

If you have questions, comments or would like to follow up on a peering request please feel free to call our corporate office.