@inproceedings {Cit2014, title = {On the Quality of BGP Route Collectors for iBGP Policy Inference}, booktitle = {IFIP Networking}, year = {2014}, month = {June 2014}, abstract = {

A significant portion of what is known about Internet routing stems out from\ public BGP datasets. For this reason, numerous research efforts were devoted to\ (i) assessing the (in)completeness of the datasets, (ii) identifying biases\ in the dataset, and (iii) augmenting data quality by optimally placing new\ collectors. However, those studies focused on techniques to extract information\ about the AS-level Internet topology.

In this paper, we show that considering different metrics influences the\ conclusions about biases and collector placement. Namely, we compare AS-level\ topology discovery with \iac inference. We find that the same datasets exhibit\ significantly diverse biases for these two metrics. For example, the sensitivity\ to the number and position of collectors is noticeably different. Moreover, for\ both metrics, the marginal utility of adding a new collector is strongly\ localized with respect to the proximity of the collector. Our results suggest\ that the {\textquoteleft}{\textquoteleft}optimal{\textquoteright}{\textquoteright} position for new collectors can only be defined with\ respect to a specific metric, hence posing a fundamental trade-off for\ maximizing the utility of extensions to the BGP data collection infrastructure.

}, keywords = {bias, iBGP policies, measurement, network topology}, author = {Luca Cittadini and Stefano Vissichio and Benoit Donnet} } @article {Tra2013d, title = {mPlane Architecture Specification}, number = {D1.3}, year = {2013}, month = {11/2013}, institution = {mPlane Consortium}, type = {Public Deliverable}, address = {Torino}, keywords = {architecture, measurement, platform, scenario, use case}, author = {Brian Trammell and Marco Mellia and Alessandro Finamore and Stefano Traverso and Tivadar Szemethy and Balazs Szabo and D Rossi and Benoit Donnet and Fabrizio Invernizzi and Dimitri Papadimitriou} } @article {Tra2013a, title = {Use Case Elaboration and Requirements Specification}, number = {D1.1}, year = {2013}, month = {01/2013}, institution = {mPlane Consortium}, type = {Public Deliverable}, address = {Torino}, abstract = {

The document defines the requirements for the mPlane architecture on the background of a set of scenarios explored by the consortium, a survey of existing comparable measurement systems and platforms and applicable standards therefore, and a set of architectural first principles drawn from the description of work and the consortium{\textquoteright}s experience.\ As mPlane is intended to be a fully flexible measurement platform, freely integrating existing probes and repositories with ones to be developed in the project, this document is primarily concerned with the definition of interfaces among mPlane components. While it does enumerate capabilities to be provided by these components, these are primarily intended to ensure the platform has the flexibility required to meet all the scenarios envisioned; the enumerations of measurements, metrics, data types, and other component capabilities are therefore not to be construed to limit the scope of work on components within the project to just those scenarios treated in this document; nor do the scenarios enumerated here define the capabilities to be demonstrated in the project{\textquoteright}s integrated trial.\ 

}, keywords = {architecture, measurement, platform, scenario, use case}, issn = {D1.1}, author = {Brian Trammell and Stephan Neuhaus and Francesco Matera and Ernst Biersack and Antonio Barbuzzi and Saverio Niccolini and Mohamed Ahmed and Maurizio Dusi and Tivadar Szemethy and Balazs Szabo and P. Casas and A B{\"a}r and Konstantina Papagiannaki and Yan Grunenberger and Ilias Leontiadis and Rolf Winter and Zied Ben-Houidi and Giovanna Carofiglio and Samir Ghamri-Doudane and Diego Perino and D Rossi} }