Policies and Procedures

Updated by Reed Disney

Foreword on Policies and Procedures

All CoreSite and Any2Exchange® policies are subject to change without notice. In the event a market trend, technology shift or other event should signal a possible revision to an Any2Exchange policy, CoreSite® will evaluate proposed changes and will determine what course of action will be the most beneficial for the entire community. CoreSite reserves the right to alter any / all final decisions as deemed necessary by management. Participants agree to comply with any amendment(s) within 30 days of implementation unless events mandate a specific time frame for compliance. Notwithstanding anything to the contrary, your continued use of the service thirty (30) days after any amendment to the policies means that you are deemed to have accepted the policies, as amended.

Should any participating network have a grievance or concern with the conduct of another participating organization, please notify CoreSite immediately via the CoreSite Customer portal or by email: Any2@CoreSite.com.

Policies and Procedures

CoreSite endeavors to manage and offer an open environment that encourages networks to interconnect and establish working relationships. The following is a set of CoreSite policies for using Any2Exchange to accomplish this. All participants are required to comply with the Any2Exchange “Operational” and “Technical Requirements” as set forth below.

Use of Any2Exchange for Purposes of Publicity

Any2Exchange participants are encouraged to use the Any2Exchange or other terms relating to CoreSite’s peering offering for instances of publicity. Please email Marketing@CoreSite.com with information on utilization and your request will be reviewed in a timely manner. Prior approval must be obtained before any utilization of trademarked or frequently used CoreSite terms as our goal is to prevent negative imaging that may affect the community.

Participant’s Operational Requirements

1.        Participant’s business shall include the transmission of internet protocols, content, VoIP transmission, or other IP protocol services.

2.       The Any2Exchange is an Internet Exchange Point designed for peering traffic only. Customers should not depend on the Any2Exchange as their sole source of upstream network connectivity.

3.       Participants will provide their contact information for operational matters, including the person or persons to whom requests for peering should be sent. This information may be viewable by other Any2Exchange members on the MyCoreSite customer service delivery platform. General information such as company name, AS number, IP Address(es), data center location and exchange may be posted on the public CoreSite website.

4.        Participants must comply with applicable law and are prohibited from using the Any2Exchange while engaging in / to facilitate illegal activities of any kind. While CoreSite aggressively protects the privacy and operational integrity of every customer, we are obligated under US law to comply with warrants and subpoenas as presented by qualified law enforcement agencies.

Technical Requirements General

1.        Participants must ensure that their usage of the Any2Exchange is not detrimental to any other participating Any2Exchange organization or CoreSite in any way.

2.       Participants must ensure that their usage is in compliance with applicable internet standards and Internet exchange standards as published by the IETF.

3.       Participants are not permitted to use the Any2Exchange for carrying traffic between their own routers (i.e., from a CoreSite facility in Reston to a CoreSite facility in New York). Any participant found to be peering between their own routers will be given a 72-hour notice to comply before their ports will be removed from the Any2Exchange.

4.      Traffic may only be forwarded from one Any2Exchange participant to another if permission has been given by the recipient.

5.       Customers will not statically route traffic to another Any2Exchange participant without their expressed written permission.

Connectivity

1.        The Any2Exchange provides connectivity to its infrastructure using switched, shared Ethernet LANs. The following requirements apply:

  • Prior to connecting to the Any2Exchange IX switch fabric, all new and upgraded ports will be placed in a hairpin VLAN.  One participant at a time will be placed in the hairpin VLAN.  To add your new or upgraded port into the peering VLAN, you will need to submit a case via MyCoreSite service delivery platform to schedule a turn up.  Have an authorized person access the MyCoreSite service delivery platform and go to 'Order Services & Support' (left pane menu), select 'Support , Access, & Shipping'.  Click on the 'NEW' button next to 'Trouble Ticket’ then fill out the form. 

Any2 Turn ups can be scheduled Monday to Friday, between 7:00 AM to 7:00 PM local time.  Make sure to include the following:

         i. CoreSite order number (usually begins with 'CAS').

         ii. MAC address (see next bullet for more details).

         iii. Point of contact (POC) from your team (name, email, phone number) that the CoreSite OSC will work with to perform the turn up.

2.       Named ACLs will be explicitly configured on all Any2Exchange interfaces by CoreSite with a maximum of one MAC address per connection (single port or multi-port LAG):

  • In some rare cases, for technical reasons, a participant may require additional MAC addresses configured on their connection. This will be reviewed and approved by the CoreSite Network Engineering team on a case-by-case basis.
  • Physical interfaces of the same speed on the same physical Any2Exchange switch may be aggregated together using IEEE 802.3ad link aggregation control protocol (LACP), by prior agreement with the Any2Exchange. However, for multiple connections, CoreSite reserves the right to charge fees as needed to ensure fair access to all participants.
  •   CoreSite reserves the right to disconnect any port that violates any of the requirements without notice.

3.       Each unique connection will receive a matching set of IPv4 and IPv6 addresses. For example:

  •   206.72.210.50/2001:504:13:0:0:0:210.50;
  • 206.51.41.100/2001:504:13:3:0:0:0:100.

4.      MD5 authentication is currently not supported

Routing

1.        Each participant must have their own Autonomous System Number and register the routing policy for their ASN in the ARIN routing registry or another public routing registry (such as RIPE).

2.       Unicast peering between participants’ routers across the Any2Exchange will be via BGP (Version 4 or subsequent).

3.       Participants may not advertise routes with a next-hop other than that of their own routers without the prior written permission of the advertised party, the recipient, and the Any2Exchange.

4.      Any2Easy® router servers cannot be used as a default router address of any kind.

Physical

1.        Participants have a duty of confidentiality to the Any2Exchange and other Any2Exchange participants. In particular, participants must not install packet sniffers to monitor traffic passing through the Any2Exchange.

2.       Participants may not connect equipment to or otherwise provide connectivity to the Any2Exchange switch infrastructure on behalf of non-participants.

How did we do?