The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
Using peeringDB to understand the peering ecosystem
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
In this study we mine one of the few sources of public data available about the interdomain peering ecosytem: PeeringDB [1], an online database where participating networks contribute information about their peering policies, traffic volumes and presence at various geographic locations. Although established to support the practical needs of operators, this data also provides a valuable source of information to researchers. Using BGP data to cross-validate three years of PeeringDB snapshots, we find that PeeringDB membership is reasonably representative of the Internet's transit, content, and access providers in terms of business types and geography of participants, and PeeringDB data is generally up-to-date. We find strong correlations among different measures of network size -- BGP-advertised address space, PeeringDB-reported traffic volume and presence at peering facilities, and between these size measures and advertised peering policies.
@article{lodhi2014using,
title = {Using peeringDB to understand the peering ecosystem},
author = {Aemen Lodhi and Natalie Larson and Amogh D. Dhamdhere and Constantine Dovrolis and kc claffy},
year = {2014},
journal = {ACM SIGCOMM Computer Communication Review},
publisher = {Association for Computing Machinery},
volume = {44},
number = {2},
pages = {20--27},
doi = {10.1145/2602204.2602208},
}