|
Thank you for your interest in establishing peering with OCCAID (AS30071). Below you will find the relevant contact information and guidelines used to qualify peering applications.
For your information, OCCAID uses IRR AS-SET object AS-OCCAID6 for its IPv6 routes and AS-OCCAID for its IPv4 routes. Additionally, OCCAID advertises approximately 180 IPv6 unicast routes, 1 IPv6 multicast routes, 65 IPv4 unicast routes and 0 IPv4 multicast routes at this time.
New: Information about IPv6 Quarantine Peering Mode
Peering Contacts | Public Peering Presence | Private Peering Presence
IPv4 Peering Policy | IPv6 Peering Policy
OCCAID Peering Contact Information |
Role |
Name |
Telephone |
Email |
General Peering Account |
Peering Committee |
|
peering [at] occaid.org |
Maintenance & Outages |
IP NOC |
+1 (617) 459-4051 x 500 |
noc [at] occaid.org |
Negotiators |
Lee Valentine James Jun Randy Epstein |
|
lee [at] occaid.org james [at] towardex.com repstein [at] occaid.org |
OCCAID Public Peering Participation |
North American Exchange Points |
ASN |
Announcing |
IP Address |
Status |
Port Speed |
NOTA (Miami) |
30071 |
AS-OCCAID6 |
2001:478:124::138 |
UP |
100M |
TIE (Atlanta) |
30071 |
AS-OCCAID6 |
2001:478:132::40 |
UP |
1G |
BostonIX (Boston) |
30071 |
AS-OCCAID6 |
2001:504:24:1::7577:1 |
UP |
1G |
Equinix (Ashburn) |
30071 |
AS-OCCAID6 |
2001:504:0:2::3:71:1 |
UP |
1G |
Equinix (San Jose) |
30071 |
AS-OCCAID6 |
2001:504:0:1::3:71:1 |
UP |
1G |
SIX (Seattle) |
30071 |
AS-OCCAID6 |
2001:504:16::7577 |
UP |
1G |
Any2 (Los Angeles) |
30071 |
AS-OCCAID6 |
2001:504:13::8 |
UP |
1G |
Any2 (Boston) |
30071 |
AS-OCCAID6 |
2001:504:13:7::8 |
UP |
1G |
Any2 (DC) |
30071 |
AS-OCCAID6 |
2001:504:13:1::22 |
UP |
1G |
European Exchange Points |
ASN |
Announcing |
IP Address |
Status |
Port Speed |
LINX (London UK) |
30071 |
AS-OCCAID6 |
2001:7f8:4:0::7577:1 2001:7f8:4:1::7577:2 |
UP |
2x100M |
Equinix (Paris FR) |
30071 |
AS-OCCAID6 |
2001:7f8:43::3:71:1 |
UP |
1G |
STHIX (Stockholm SE) |
30071 |
AS-OCCAID6 |
2001:7f8:3e::a500:3:71:1 2001:7f8:3e::a500:3:71:2 |
UP |
2x1G |
FIXO (Oslo NO) |
30071 |
AS-OCCAID6 |
2001:7f8:41:4658::30:071 |
UP |
1G |
COPHIX (Copenhagen DK) |
30071 |
AS-OCCAID6 |
2001:7f8:5C::A500:3:71:1 |
UP |
1G |
Asia-Pacific Exchange Points |
ASN |
Announcing |
IP Address |
Status |
Port Speed |
Equinix (Sydney) |
30071 |
AS-OCCAID6 |
2001:de8:6::3:71:1 |
UP |
100M |
OCCAID Private Peering Locations |
North America Facilities |
ASN |
Announcing |
Status |
Accepted Media |
Equinix Ashburn (Bldg. F) 21715 Filigree Ct Ashburn VA, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
Equinix San Jose 11 Great Oaks Blvd San Jose CA, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Equinix Chicago 350 E Cermak Rd Chicago IL, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Equinix Dallas 1950 N Stemmons Fwy Dallas TX, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
Equinix Newark 165 Halsey St Newark NJ, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
4th Floor, Host.net 56 Marietta St Atlanta GA, US |
30071 |
AS-OCCAID6 AS-OCCAID |
UP |
FastE, GigE, 802.1Q |
Host.net 3500 NW Boca Raton FL, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
Nap of The Americas 50 NE 9th St Miami FL, US |
30071 |
AS-OCCAID6 AS-OCCAID |
UP |
FastE, 802.1Q |
Miami Data Vault 100 NE 80th. Terrace Miami FL, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
JMA NAX 530 West 6th St Los Angeles CA, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
One Wilshire 1 Wilshire Blvd Los Angeles CA, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Market Post Tower 55 S. Market St San Jose CA, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
exchangeColo 200 Paul Ave San Francisco CA, US |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
Switch & Data Boston 74 West St Waltham MA, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
TowardEX 800 Boylston St Boston MA, US |
30071 |
AS-OCCAID6 |
UP |
10GbE, GigE, FastE, 802.1Q |
TowardEX 150 Federal St Boston MA, US |
30071 |
AS-OCCAID6 |
UP |
10GbE, GigE, FastE, 802.1Q |
Markley Group (4th Floor) 1 Summer St Boston MA, US |
30071 |
AS-OCCAID6 |
UP |
10GbE, GigE, FastE, 802.1Q |
230 Congress St Boston MA, US |
30071 |
AS-OCCAID6 |
UP |
ATM, GigE, FastE, 802.1Q |
Level3 300 Bent St Cambridge MA, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Bryant Building 1102 Grand Ave Kansas City MO, US |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
NYC Connect 111 8th Ave New York NY, US |
30071 |
AS-OCCAID6 |
PENDING |
GigE, FastE, 802.1Q |
151 Front St W Toronto ON, CA |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Europe Facilities |
ASN |
Announcing |
Status |
Accepted Media |
Redbus Sovereign House (Burstfire/Kewlio) 227 Marsh Wall London, UK |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Telecity2 Amsterdam Kuiperberweg 13 Amsterdam, NL |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Telvent Carrierhouse Lisbon (Prior Velho) Av. Severiano Falcao 14 Sacavem, PT |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Port80 (Fl. 4) Fabriksvag 21 A Stockholm, SE |
30071 |
AS-OCCAID6 |
UP |
FastE, 802.1Q |
Netscalibur Milan Via Caldera 21 Bldg E, Milan, IT |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Dial Telecom/6COM Kovoprojekt Bratislava a.s., Ružová dolina 6, Bratislava, SK |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
Asia-Pacific Facilities |
ASN |
Announcing |
Status |
Accepted Media |
Equinix Tokyo
TRC-C Building B Block, 4F 5-1 Heiwajima 6-Chome, Oota-Ku JP |
30071 |
AS-OCCAID6 |
UP |
GigE, FastE, 802.1Q |
OCCAID IPv4 Peering Policy |
The guidelines for establishing IPv4 peering with OCCAID are as follows: |
1. Intro: Peering IPv4 with OCCAID gives your customers quicker access to IPv6 tunneling service points throughout the US, including some of SixXS POPs in the United States.
|
2. OCCAID will only peer IPv4 with (a) networks with existing IPv6 peering arrangement; (b) OCCAID2 site connectors; and/or (c) IPv4 networks that provide transit path for end-user IPv6 tunnels.
|
OCCAID IPv6 Peering Policy |
The guidelines for establishing IPv6 peering with OCCAID are as follows: |
1. OCCAID grants open peering policy to any one of the following:
- Members of certain exchange points we're present at (contact us for details).
- National Research & Education Networks (NRENs)
- Defense and Governmental Institutions
|
2. Peering is bilateral. There is no MLPA or third-party regulation on bilateral interconnections. |
3.
For all interconnect types (Public and Private), interconnection must occur at minimum of two (2) diverse locations that are not in the same metropolitan region.
For networks with international/global footprint, interconnection must occur at all continents where both networks maintain presence. Specific exemptions may be made, at OCCAID's discretion, for International networks who operate solely in continental regions where OCCAID currently has limited presence, or does not interconnect with other networks.
|
4. The applicant's network must be able to reach all of its OCCAID interconnection points under a single continuant Autonomous System Number (ASN), and must not be a set of disconnected networks.
|
5. Must maintain minimum backbone capacity of OC-12/STM-4 (622 Mbps) links or greator between geographically dispersed metropolitan locations. |
6. Peers who are exchanging 50Mbit/sec (in 95th percentile) in aggregate or more of IPv6 traffic with OCCAID will be asked to either: (a) exchange MEDs; or (b) balance traffic exchange rate to not exceed bidirectional ratio of 2:1.
|
7. Each interconnection (regardless of whether public or private) shall have no less than 100Mbit/s of capacity. |
6. Must not be a member/participant of OCCAID which is receiving transit or commodity peering service. |
8. MD5 password is not supported at all locations.
|
9. Operation of a 24x7x365 network operations center (NOC) that proactively monitors all interconnections and provides an escalation path to quickly identify and resolve network problems. |
10. Must be able and willing to quickly trace and mitigate ongoing denial of service attacks and malicious network activities. Must be able to provide a qualified engineer within a reasonable timeframe and be willing to take reasonable steps to mitigate attacks which are crossing over the interconnection--this includes reasonable placement of packet filters or blackhole routes upon request, and OCCAID will do the same. |
11. Consistent route announcements at all peering locations.
|
12. Hot-potato is implied. We will not accept or send MEDs.
|
13. Neither party shall announce to the other the more specific routes of prefixes learned via a third party transit customer.
|
14. Must not establish a static route, a route of last resort (i.e. default route), or otherwise send traffic over the interconnection for a route not advertised over BGP. Neither party shall alter, sell, or give next-hop to a third party. Neither party shall restrict nor otherwise temper with traffic bound to the other party. These activities are considered malicious and theft of service.
|
15. Must not readvertise OCCAID's prefixes to any parties which are not customers. Tunneled BGP 'peerings' without a business or sponsorship relationship to provide upstream service constitute NON-CUSTOMERS. Peers and upstream transit providers also constitute NON-CUSTOMERS. Likewise, must only advertise customer and self-originated routes to OCCAID and vice versa.
|
16. Both parties should be willing to register route6 and related objects to IRR and update them consistently for the purpose of filtering. Also both parties should encourage their customers to do the same.
|
17. Peers who are unable to maintain these requirements are given 30 days written notice over email to rectify the situation. OCCAID reserves the right to depeer if situation is not cured within 30 days or within a reasonable extension which may be granted upon constant communication between both parties.
|
18. OCCAID reserves the right to temporarily suspend any or all interconnections without prior notice in the event that peer's network is causing material damages and/or operational harm to OCCAID. Such suspended interconnections can be restored back into service as soon as both parties are assured that all operational issues are cured and cleared.
|
19. Meeting the guidelines above is not a guarantee that peering will be established. OCCAID reserves the right to not grant peering to an applicant based on business or operational reasons.
|
20. OCCAID reserves the right to make exceptions at its discretion to any particular peer or applicant. OCCAID further reserves the right to update its peering policies without notice at its discretion, as overall customer demand and network traffic conditions change.
|
Last updated: October 13, 2008
|
|