Skip to Content
[CAIDA - Center for Applied Internet Data Analysis logo]
Center for Applied Internet Data Analysis
www.caida.org > publications : papers : 2014 : open_peering_transit_providers
Open Peering by Internet Transit Providers: Peer Preference or Peer Pressure?
A. Lodhi, A. Dhamdhere, and C. Dovrolis, "Open Peering by Internet Transit Providers: Peer Preference or Peer Pressure?", in IEEE Conference on Computer Communications (INFOCOM), Apr 2014.
|   View full paper:    PDF    |  Citation:    BibTeX   |

Open Peering by Internet Transit Providers: Peer Preference or Peer Pressure?

Aemen Lodhi2
Amogh Dhamdhere1
Constantine Dovrolis2
1

CAIDA, San Diego Supercomputer Center, University of California San Diego

2

School of Computer Science, Georgia Institute of Technology

Peering agreements between Autonomous Systems affect not only the flow of interdomain traffic but also the economics of the entire Internet ecosystem. The conventional wisdom is that transit providers are selective in choosing their settlement-free peers because they prefer to offer revenue-generating transit service to others. Surprisingly, however, a large percentage of transit providers use an Open peering strategy. What causes this large-scale adoption of Open peering, especially among transit providers? More importantly, what is the impact of this peering trend on the economic performance of the population of transit providers? We approach these questions through game-theoretic modeling and agent-based simulations, capturing the dynamics of peering strategy adoption, inter-network formation and interdomain traffic flow. We explain why transit providers gravitate towards Open peering even though that move may be detrimental to their economic fitness. Finally, we examine the impact of an Open peering variant that requires some coordination among providers.

Keywords: economics, policy, routing, topology
  Last Modified: Wed Oct-11-2017 17:04:03 PDT
  Page URL: http://www.caida.org/publications/papers/2014/open_peering_transit_providers/index.xml