Philip Smith's Internet Development Site

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{peering-toolbox/peeringtoolbox.png?400|}}

====== Where to Peer ======

This section of the Toolbox describes the where a network operator would seek peering. 

There are two paths available:
  * [[where-to-peer#private_peering|Private Peering]]
  * [[where-to-peer#public_peeringinternet_exchange_point|Public Peering/Internet Exchange Point]]





===== Private Peering =====

Private peering is where there is a private connection between the two network operators for the purpose of exchanging traffic. The following topics cover the aspects needed in any Private Peering setup.
  * [[where-to-peer#meaning|Meaning]]
  * [[where-to-peer#when_to_consider|When to consider]]
  * [[where-to-peer#location|Location]]
  * [[where-to-peer#sizing|Sizing]]
  * [[where-to-peer#physical_connection|Physical Connection]]
  * [[where-to-peer#configuration|Configuration]]
  * [[where-to-peer#private_peering_agreement|Private Peering Agreement]]
==== Meaning ====

**Private** means that the physical link between the two network operators is organised by them (by one operator or by both), is only for their use, and is usually jointly owned (costs are shared) by both operators.

==== When to Consider ====

Private Peering is considered when there is mutual benefit for two organisations to interconnect (see the [[why-peer| Why peer]] section):

  * For a network operator, this may be to connect to another operator for mutually beneficial traffic exchange between their respective customers.
  * For an enterprise, this may primarily be to interconnect with content and cloud providers for more optimum (bandwidth, latency, service quality) connectivity.
==== Location ====

It is up to the two operators who wish to peer privately to agree the location that would suit them best. If they are in the same physical datacentre, a link between their equipment cabinets may be enough. If parts of their respective networks are in the same metropolitan area, perhaps local capacity can be leased from an infrastructure operator. But if they are far apart, or in different countries, a wide area network link will need to be used, chosen according to what makes most economic sense (usually leasing fibre or specific circuits or using a L2 infrastructure provider).

==== Sizing ====

(NEW)

Sizing of capacity from one operator to another for a private peering is critically important to ensure that money is not wasted either over-provisioning or under-provisioning.

**Over-provisioning** is usually preferred but comes at a cost, usually for physical infrastructure and any port charges. Advice from experienced operators is usually to provision enough capacity to allow for growth over at least the next 2 years - longer is better if there isn't a cost implication.

**Under-provisioning** is incredibly risky and is usually a very expensive mistake by any network operator, especially if the infrastructure has been difficult to procure and implement in the first place. It is strongly recommended to be avoided. It is not a good cost saving strategy!

As a general guideline, private peering link capacity is usually measured in multiples of the physical infrastructure available. For example, today, links in many parts of the Internet are counted in multiples of 10Gbps. The physical link may be 10Gbps even if the peering traffic may only be 1Gbps to 2Gbps. Indeed, provisioning two 1Gbps links for a private peering might well be considerably more expensive than provisioning a single 10Gbps link, even when port and optical transceiver cost is taken into account.

==== Physical Connection ====

(UPDATED)

The physical link can take many forms, including:
  * copper ethernet or fibre optic cable patching between each operators routers in different equipment racks in the same datacentre
  * dark fibre or "lambdas" (specific wavelengths) leased from an infrastructure provider between the two operators datacentres
  * wireless media (the various 802.11 standards) connecting over the air across distances up to 10km (usually where fibre interconnect is not possible)
  * satellite infrastructure (whether low earth orbit, medium earth orbit, geosynchronous or geostationary) connecting over large distances where neither fibre nor wireless can service the need. 
  * layer-2 infrastructure provided by a layer-2 infrastructure operator (today this is typically using L2VPN services over MPLS; in the past, ATM, SMDS, Frame Relay and X.25 were used).




==== Configuration ====

(UPDATED)

The Border Gateway Protocol (BGP) is used by the operators to share routes with each other and knowledge of BGP is required to implement a peering relationship.

At a high level, the configuration applied to each network operator's router ensures that each operator only sends the routes (public IP address space) they and their customers use for Internet access, and only accept the routes that their peer (and their customers) use for Internet access. All other routing information is blocked on this private link (a very important requirement for routing security).

The routes that a network operator learns from a private peer must not be passed on to any other autonomous network **unless** and **only** if there is agreement with the private peer that this is desirable.

Detailed configuration examples are covered elsewhere in the Toolbox. 

==== Private Peering Agreement ====

Operators who enter into a Private Peering arrangement will usually exchange documentation detailing the peering agreement between them. This agreement usually contains information such as:
  * which routes will be exchanged
  * the process by which changes to the routes being exchanged will be informed to the peer
  * an undertaking to upgrade the interconnect capacity (bandwidth) in a timely manner (timely will be defined at what percentage of capacity is used before an upgrade is needed)
  * contact details of the Peering Coordinator (the administrative contact) in each operator
  * contact details of the Network Operations Centre at each operator (not customer helpdesk!)
  * escalation process in case of faults on the interconnect
  * any other relevant information relating to the interconnect to ensure its continuous and reliable operation

Not all operators enter into such an agreement although it is recommended simply so there is a documentation trail and that each operator knows what to do if any issues need to be resolved.

===== Public Peering / Internet Exchange Point =====

Public peering is where there is a public interconnect location where network operators can interconnect for the purpose of exchanging traffic. This public interconnect is known as an [[:peering-toolbox/what-is-peering/what_is_an_internet_exchange_point|Internet Exchange Point]]. The following topics cover the aspects needed in any Public Peering setup.
  * [[where-to-peer#meaning1|Meaning]]
  * [[where-to-peer#when_to_consider1|When to consider]]
  * [[where-to-peer#location1|Location]]
  * [[where-to-peer#sizing1|Sizing]]
  * [[where-to-peer#physical_connection1|Physical Connection]]
  * [[where-to-peer#configuration1|Configuration]]
  * [[where-to-peer#agreements|Agreements]]
==== Meaning ====
**Public** means that the physical infrastructure provided for interconnecting to other networks is open to all and any network operator to participate in, as they wish. Each network operator is responsible for providing their own connectivity to the public interconnect location.

==== When to Consider ====

Peering at an IXP is considered when there benefit for the entity (see the [[why-peer| Why peer]] section) to connect to the infrastructure to access other members present there:

  * For a network operator, this may be to connect to other members (network operators, content and cloud providers, enterprises, R&E networks etc) for mutually beneficial traffic exchange between their respective customers.
  * For an enterprise, this may be to ensure higher quality access to services they host for the population served by the network operators connected to the IXP. Another strong motivator for an enterprise to join an IXP is to interconnect with content and cloud providers for more optimum (bandwidth, latency, service quality) connectivity.

Even if the IXP is small, there is still benefit in connecting, as the more members present, the greater value the IXP gives to all members, and the more attractive it is for other entities to join it. The largest IXPs all started with just a few members, and their value grew as more entities joined to exchange traffic.

==== Location ====
Public interconnects are located where it is most convenient for the largest number of network operators to access and participate at the most optimum cost to the network operators. (Bearing in mind that peering is designed to minimise the cost of operation for network operators.)

Ideal locations for public interconnects include datacentres and/or locations of concentrations of fibre provided by several infrastructure operators. These locations all have good physical and network access, 24 hour coverage, independent power grid supplies with on-site backup, sufficient cooling, and are well protected from natural disasters (earthquake, tsunami, wildfire, floods, volcanoes, cyclones). 

Given the large concentration of network operators present, these public interconnects are often considered critical infrastructure, and their reliable operation is often considered of national importance.

==== Sizing ====

(NEW)

Sizing of capacity from an operator to an IXP is critically important to ensure that money is not wasted either over-provisioning or under-provisioning.

**Over-provisioning** is usually preferred but comes at a cost, usually for physical infrastructure and any port charges. Advice from experienced operators is usually to provision enough capacity to allow for growth over at least the next 2 years - longer is better if there isn't a cost implication.

**Under-provisioning** is incredibly risky and is usually a very expensive mistake by any network operator, especially if the infrastructure has been difficult to procure and implement in the first place. It is strongly recommended to be avoided. It is not a good cost saving strategy!

As a general guideline, peering link capacity is usually measured in multiples of the physical infrastructure available. For example, today, links in many parts of the Internet are counted in multiples of 10Gbps. The physical link may be 10Gbps even if the IXP traffic may only be 1Gbps to 2Gbps. Indeed, provisioning two 1Gbps links to an IXP might well be considerably more expensive (and harder to implement BGP and routing policies to get equal link utilisation) than provisioning a single 10Gbps link, even when port and optical transceiver cost is taken into account.

==== Physical Connection ====

(UPDATED)

The physical link each operator has to provide to the public interconnect can take many forms, including:
  * copper ethernet or fibre optic cable patching between the operator's routers and the IXP switch in the same datacentre
  * dark fibre or "lambdas" (specific wavelengths) leased from an infrastructure provider between the operator's datacentre and the IXP location
  * wireless media (the various 802.11 standards) connecting over the air across distances up to 10km (usually where fibre interconnect is not possible)
  * satellite infrastructure (whether low earth orbit, medium earth orbit, geosynchronous or geostationary) connecting over large distances where neither fibre nor wireless can service the need. 
  * via a layer-2 infrastructure provider, which means the operator does not need to physically connect to the IXP by any of the above options (this is known as Remote Peering).

==== Configuration ====

(UPDATED)

The Border Gateway Protocol (BGP) is used by the operators to share routes with each other and knowledge of BGP is required to implement a peering relationship. 

At a high level, the configuration applied to the network operator's router ensures that the operator only sends the routes (public IP address space) they and their customers use for Internet access, and only accept the routes that their peers (and their customers) use for Internet access. All other routing information is blocked on the public peering links (a very important requirement for routing security).

The routes that a network operator learns from a public peer must not be passed on to any other autonomous network unless and only if there is agreement with the public peer that this is desirable.

Detailed configuration examples are covered elsewhere in the Toolbox.

==== Agreements ====

Operators who participate at an IXP usually will sign an agreement with the IXP itself. This agreement usually contains information such as:

  * contact details of the Peering Coordinator (the administrative contact) at the operator
  * contact details of the Network Operations Centre at the operator (not customer helpdesk!) and the IXP
  * escalation process in case of faults on the interconnect
  * rules/behaviour at the IXP
  * how to use IXP infrastructure to aid with setting up connections with other operators
  * any other relevant information relating to the connection at the IXP to ensure its continuous and reliable operation

Not all IXPs require such an agreement although it is recommended simply so there is a documentation trail and that the operator knows what to do if any issues need to be resolved. 




[[:peering-toolbox/start#beginner| Back to Home page]]