On Cycles in AS Relationships Xenofontas Dimitropoulos IBM Research, Zurich ¨ M. Angeles Serrano IFISC (CSIC-UIB) Dmitri Krioukov CAIDA xed@zurich.ibm.com marian.serrano@i sc.uibcsic.es dima@caida.org This article is an editorial note submitted to CCR. It has NOT been peer reviewed. Authors take full responsibility for this article s technical content. Comments can be posted through CCR Online. Categories and Subject Descriptors C.2.5 [Local and Wide-Area Networks]: Internet; C.2.1 [Network Architecture and Design]: Network topology General Terms Measurement, Design, Veri cation Keywords AS relationships, cycles everal users of our AS relationship inference data [1], released with [2], asked us why it contained AS relationship cycles, e.g., cases where AS A is a provider of AS B, B is a provider of C, and C is a provider of A, or other cycle types. Having been answering these questions in private communications, we have eventually decided to write down our answers here for future reference. Formally, the heuristics in [2] do not produce acyclic relationships because neither do the techniques that [2] is based on [3, 4, 5], and because we did not try to impose any no-cycle constraints that can certainly be enforced [6]. Below we explain why we did not
/lp/association-for-computing-machinery/on-cycles-in-as-relationships-BAJsrFixY6