NATIONAL CAPITAL INTERNET EXCHANGE

O/A OTTAWA-GATINEAU INTERNET EXCHANGE (“OGIX”)

CONNECTION AND PEERING POLICY

 

Purpose of the policy

The purpose of this policy is to articulate the rules that apply for connection to, and peering at, the Internet Exchange Point (“IXP”) locations operated by OGIX.

The Organisation

OGIX is a not-for-profit corporation incorporated on March 29, 2018, as National Capital Internet Exchange under the Canada Not-for-profit Corporations Act, S.C. 2009, c.23. One of the stated purposes of the Corporation is: “To provide an infrastructure that facilitates the exchange of communications network traffic among Internet service providers, network service providers, content service providers and other entities that need to exchange communications network traffic within Canada”.

OGIX mandate

In order to fulfil its mandate, OGIX is in the process of establishing IXP peering infrastructure in the Ottawa-Gatineau region. Initially, the IXP is operational at the PureColo Inc. data centre located at 390 March Road in the City of Ottawa. Additional locations will be added as practicable.

 

Interconnection with the OGIX infrastructure at the IXP locations

Any organization that operates a communication network and satisfies the following conditions may connect at the OGIX peering infrastructure for the purpose of exchanging traffic with other peers connected to that infrastructure, thereby becoming a participant in the exchange

1.) The organization has delivered a complete and signed service order to OGIX specifying the peering services that it wishes to obtain from OGIX and the location(s) at which it intends to interconnect, based on the options that OGIX makes available to peers from time-to-time;

2.) The organization has paid the necessary installation charge so as to be in good financial standing with OGIX;

3.) The organization has provided the technical information that OGIX requires to connect the participant’s network to the OGIX exchange and interconnection is being requested to be accomplished in a manner that is compatible with the peering equipment operated by, and technical requirements of, OGIX;

4.) The organization commits to complying with the terms and conditions of service and policies of OGIX, as amended from time-to-time;

5.) The organization has made the necessary arrangements, including providing the necessary authorizations, to obtain meet-me-room cross-connect(s) to reach the OGIX peering infrastructure at its own expense in each IXP location at which it seeks interconnection; and

6.) The organization adheres to all required technical interconnection and peering rules of OGIX, as amended from time-to-time.

 

Technical requirements for interconnection and peering at OGIX

An organization that wants to peer at OGIX must also meet the following technical requirements:

1.) he organization has a unique 16- or 32- bit long global autonomous system number.

2.) The organization is interconnecting using either multi-mode or single-mode fibre associated to either short- or long-reach optics media only at port speeds offered by OGIX, which are currently: (1) 10 Gbps port; (2) 40Gbps port or (3) 100Gbps port, but note that sub-rated speeds are independent from the chosen media type.

3.) The organization is in charge of providing its own transceiver for the equipment connecting to OGIX peering fabric as well as arranging for the cross connect to the OGIX switch, whereas the transceiver on the OGIX switch is provided by OGIX. As a result, the demarcation for the NNI connection is on the OGIX side of the cross connect side.

4.) The ethernet link supporting the connection between the organization and the OGIX supports a 1500-byte IP MTU. There is no planned support for jumbo frames.

5.) The organization either provides its own Internet Protocol (“IP”) IPv4/IPv6 address space or a written authorization from the holder of the IP address space that the organization intends to advertise indicating that the organization is entitled to advertise that IP space.

6.) The organization does not advertise IPv4 IP address prefix sizes longer than a /24 of IPv4 space or a /48 of IPv6 space, since longer prefixes are typically filtered by peers.

7.)The organization maintains entries in the ARIN (https://www.arin.net/resources/routing/) or RADb (https://www.radb.net/) Internet Routing Registry.

8.) The organization has up-to-date entries in the database of networks that peer, called PeeringDB (https://www.peeringdb.com/) for all prefixes it wishes to announce. In accordance with MANRS for IXP recommendation, the OGIX route-server filtering policy is based on the combination of ARIN/RADb and PeeringDB entries. Any inconsistent entry will be filtered automatically.

9.)The authentication to the OGIX peering manager interface is done through PeeringDB OAuth which requires the organization to have valid user entries for the team in charge of maintaining the connection between the organization and the OGIX.