Philip Smith's Internet Development Site

User Tools

Site Tools

Trace:
peering-toolbox:where-to-peer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
peering-toolbox:where-to-peer [2023/03/27 11:35] – [Physical Connection] philippeering-toolbox:where-to-peer [2023/03/27 18:57] – [Public Peering / Internet Exchange Point] philip
Line 19: Line 19:
   * [[where-to-peer#when_to_consider|When to consider]]   * [[where-to-peer#when_to_consider|When to consider]]
   * [[where-to-peer#location|Location]]   * [[where-to-peer#location|Location]]
 +  * [[where-to-peer#sizing|Sizing]]
   * [[where-to-peer#physical_connection|Physical Connection]]   * [[where-to-peer#physical_connection|Physical Connection]]
   * [[where-to-peer#configuration|Configuration]]   * [[where-to-peer#configuration|Configuration]]
Line 36: Line 37:
  
 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). 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 ==== ==== Physical Connection ====
Line 47: Line 60:
   * 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.    * 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).   * 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 ==== ==== 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). 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).
Line 71: Line 91:
 ===== Public Peering / Internet Exchange Point ===== ===== 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 **Internet Exchange Point**. The following topics cover the aspects needed in any Public Peering setup.+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#meaning1|Meaning]]
   * [[where-to-peer#when_to_consider1|When to consider]]   * [[where-to-peer#when_to_consider1|When to consider]]
   * [[where-to-peer#location1|Location]]   * [[where-to-peer#location1|Location]]
 +  * [[where-to-peer#sizing1|Sizing]]
   * [[where-to-peer#physical_connection1|Physical Connection]]   * [[where-to-peer#physical_connection1|Physical Connection]]
   * [[where-to-peer#configuration1|Configuration]]   * [[where-to-peer#configuration1|Configuration]]
Line 97: Line 118:
  
 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. 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 ==== ==== Physical Connection ====
  
Line 109: Line 143:
  
 ==== Configuration ==== ==== 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). 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).
peering-toolbox/where-to-peer.txt · Last modified: 2023/04/30 14:39 by philip