Anycast Latency: How Many Sites Are Enough?. Schmidt, R. d. O., Heidemann, J., & Kuipers, J. H. In Proceedings of the Passive and Active Measurement Workshop, pages to appear, Sydney, Australia, March, 2017. Springer. Awarded Best Paper![Anycast Latency: How Many Sites Are Enough? [link]](https://bibbase.org/img/filetypes/link.svg "link")
Paper abstract bibtex Anycast is widely used today to provide important services such as DNS and Content Delivery Networks (CDNs). An anycast service uses multiple \emphsites to provide high availability, capacity and redundancy. BGP routing associates users to sites, defining the \emphcatchment that each site serves. Although prior work has studied how users associate with anycast services informally, in this paper we examine the key question \emphhow many anycast sites are needed to provide good latency, and the worst case latencies that specific deployments see. To answer this question, we first define the \emphoptimal performance that is possible, then explore how routing, specific anycast policies, and site location affect performance. We develop a new method capable of determining optimal performance and use it to study four real-world anycast services operated by different organizations: C-, F-, K-, and L-Root, each part of the Root DNS service. We measure their performance from more than 7,900 vantage points (VPs) worldwide using RIPE Atlas. (Given the VPs uneven geographic distribution, we evaluate and control for potential bias.) Our key results show that a few sites can provide performance nearly as good as many, and that geographic location and good connectivity have a far stronger effect on latency than having many sites. We show how often users see the closest anycast site, and how strongly routing policy affects site selection.
@InProceedings{Schmidt17a,
author = "Schmidt, Ricardo de O. and John Heidemann and Jan Harm Kuipers",
title = "Anycast Latency: How Many Sites Are Enough?",
booktitle = "Proceedings of the " # " Passive and Active Measurement Workshop",
year = 2017,
pages = "to appear",
month = mar,
note = "Awarded Best Paper",
address = "Sydney, Australia",
publisher = "Springer",
jlocation = "johnh: pafile",
project = "ant, lacrend, lander, retrofuture, researchroot, pinest, nipet",
jsubject = "network_security",
sortdate = "2017-03-30",
jlocation = "johnh: pafile",
keywords = "anycast, dns, design, latency",
url = "https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.html",
pdfurl = "https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.pdf",
blog = "https://ant.isi.edu/blog/?p=930",
copyrightholder = "Springer",
copyrightterms = "An author may self-archive an author-created version of his/her article on his/her own website and or in his/her institutional repository. He/she may also deposit this version on his/her funder's or funder's designated repository at the funder's request or as a result of a legal obligation, provided it is not made publicly available until 12 months after official publication. He/she may not use the publisher's PDF version, which is posted on \url{www.springerlink.com}, for the purpose of self-archiving or deposit. Furthermore, the author may only post his/her version provided acknowledgement is given to the original source of publication and a link is inserted to the published article on Springer's website. The link must be accompanied by the following text: ``The final publication is available at www.springerlink.com''. " ,
xxxdoi = "xxx",
abstract = "
Anycast is widely used today to provide important services such as DNS
and Content Delivery Networks (CDNs). An anycast service uses
multiple \emph{sites} to provide high availability, capacity and
redundancy. BGP routing associates users to sites, defining
the \emph{catchment} that each site serves. Although prior work has
studied how users associate with anycast services informally, in this
paper we examine the key
question \emph{how many anycast sites are needed}
to provide good latency, and the worst case latencies that
specific deployments see. To answer this question, we first define
the \emph{optimal performance} that is possible, then explore how
routing, specific anycast policies, and site location affect
performance. We develop a new method capable of determining optimal
performance and use it to study four real-world anycast services
operated by different organizations: C-, F-, K-, and L-Root, each part
of the Root DNS service. We measure their performance from more
than 7,900 vantage points (VPs) worldwide using RIPE Atlas. (Given the
VPs uneven geographic distribution, we evaluate and control for
potential bias.) Our key results show that a few sites can provide
performance nearly as good as many, and that geographic location and
good connectivity have a far stronger effect on latency than having
many sites. We show how often users see the closest anycast site, and
how strongly routing policy affects site selection.
",
}
Downloads: 0
{"_id":"CcKLHTtv6PzDY42hS","bibbaseid":"schmidt-heidemann-kuipers-anycastlatencyhowmanysitesareenough-2017","author_short":["Schmidt, R. d. O.","Heidemann, J.","Kuipers, J. H."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"propositions":[],"lastnames":["Schmidt"],"firstnames":["Ricardo","de","O."],"suffixes":[]},{"firstnames":["John"],"propositions":[],"lastnames":["Heidemann"],"suffixes":[]},{"firstnames":["Jan","Harm"],"propositions":[],"lastnames":["Kuipers"],"suffixes":[]}],"title":"Anycast Latency: How Many Sites Are Enough?","booktitle":"Proceedings of the Passive and Active Measurement Workshop","year":"2017","pages":"to appear","month":"March","note":"Awarded Best Paper","address":"Sydney, Australia","publisher":"Springer","jlocation":"johnh: pafile","project":"ant, lacrend, lander, retrofuture, researchroot, pinest, nipet","jsubject":"network_security","sortdate":"2017-03-30","keywords":"anycast, dns, design, latency","url":"https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.html","pdfurl":"https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.pdf","blog":"https://ant.isi.edu/blog/?p=930","copyrightholder":"Springer","copyrightterms":"An author may self-archive an author-created version of his/her article on his/her own website and or in his/her institutional repository. He/she may also deposit this version on his/her funder's or funder's designated repository at the funder's request or as a result of a legal obligation, provided it is not made publicly available until 12 months after official publication. He/she may not use the publisher's PDF version, which is posted on ˘rlwww.springerlink.com, for the purpose of self-archiving or deposit. Furthermore, the author may only post his/her version provided acknowledgement is given to the original source of publication and a link is inserted to the published article on Springer's website. The link must be accompanied by the following text: ``The final publication is available at www.springerlink.com''. ","xxxdoi":"xxx","abstract":"Anycast is widely used today to provide important services such as DNS and Content Delivery Networks (CDNs). An anycast service uses multiple \\emphsites to provide high availability, capacity and redundancy. BGP routing associates users to sites, defining the \\emphcatchment that each site serves. Although prior work has studied how users associate with anycast services informally, in this paper we examine the key question \\emphhow many anycast sites are needed to provide good latency, and the worst case latencies that specific deployments see. To answer this question, we first define the \\emphoptimal performance that is possible, then explore how routing, specific anycast policies, and site location affect performance. We develop a new method capable of determining optimal performance and use it to study four real-world anycast services operated by different organizations: C-, F-, K-, and L-Root, each part of the Root DNS service. We measure their performance from more than 7,900 vantage points (VPs) worldwide using RIPE Atlas. (Given the VPs uneven geographic distribution, we evaluate and control for potential bias.) Our key results show that a few sites can provide performance nearly as good as many, and that geographic location and good connectivity have a far stronger effect on latency than having many sites. We show how often users see the closest anycast site, and how strongly routing policy affects site selection. ","bibtex":"@InProceedings{Schmidt17a,\n\tauthor = \t\"Schmidt, Ricardo de O. and John Heidemann and Jan Harm Kuipers\",\n\ttitle = \t\"Anycast Latency: How Many Sites Are Enough?\",\n\tbooktitle = \t\"Proceedings of the \" # \" Passive and Active Measurement Workshop\",\n\tyear = \t\t2017,\n\tpages = \t\"to appear\",\n\tmonth = \tmar,\n\tnote = \"Awarded Best Paper\",\n\taddress = \t\"Sydney, Australia\",\n\tpublisher = \t\"Springer\",\n\tjlocation = \t\"johnh: pafile\",\n\tproject = \"ant, lacrend, lander, retrofuture, researchroot, pinest, nipet\",\n\tjsubject = \"network_security\",\n\tsortdate = \"2017-03-30\",\n\tjlocation = \t\"johnh: pafile\",\n\tkeywords = \t\"anycast, dns, design, latency\",\n\turl =\t\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.html\",\n\tpdfurl =\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.pdf\",\n\tblog = \"https://ant.isi.edu/blog/?p=930\",\n\t copyrightholder = \"Springer\",\n\t copyrightterms = \"An author may self-archive an author-created version of his/her article on his/her own website and or in his/her institutional repository. He/she may also deposit this version on his/her funder's or funder's designated repository at the funder's request or as a result of a legal obligation, provided it is not made publicly available until 12 months after official publication. He/she may not use the publisher's PDF version, which is posted on \\url{www.springerlink.com}, for the purpose of self-archiving or deposit. Furthermore, the author may only post his/her version provided acknowledgement is given to the original source of publication and a link is inserted to the published article on Springer's website. The link must be accompanied by the following text: ``The final publication is available at www.springerlink.com''. \" ,\n\txxxdoi = \t\"xxx\",\n\tabstract = \"\nAnycast is widely used today to provide important services such as DNS\nand Content Delivery Networks (CDNs). An anycast service uses\nmultiple \\emph{sites} to provide high availability, capacity and\nredundancy. BGP routing associates users to sites, defining \nthe \\emph{catchment} that each site serves. Although prior work has\nstudied how users associate with anycast services informally, in this\npaper we examine the key \nquestion \\emph{how many anycast sites are needed} \nto provide good latency, and the worst case latencies that\nspecific deployments see. To answer this question, we first define\nthe \\emph{optimal performance} that is possible, then explore how\nrouting, specific anycast policies, and site location affect\nperformance. We develop a new method capable of determining optimal\nperformance and use it to study four real-world anycast services\noperated by different organizations: C-, F-, K-, and L-Root, each part\nof the Root DNS service. We measure their performance from more\nthan 7,900 vantage points (VPs) worldwide using RIPE Atlas. (Given the\nVPs uneven geographic distribution, we evaluate and control for\npotential bias.) Our key results show that a few sites can provide\nperformance nearly as good as many, and that geographic location and\ngood connectivity have a far stronger effect on latency than having\nmany sites. We show how often users see the closest anycast site, and\nhow strongly routing policy affects site selection.\n\",\n}\n\n","author_short":["Schmidt, R. d. O.","Heidemann, J.","Kuipers, J. H."],"bibbaseid":"schmidt-heidemann-kuipers-anycastlatencyhowmanysitesareenough-2017","role":"author","urls":{"Paper":"https://ant.isi.edu/%7ejohnh/PAPERS/Schmidt17a.html"},"keyword":["anycast","dns","design","latency"],"metadata":{"authorlinks":{}}},"bibtype":"inproceedings","biburl":"https://bibbase.org/f/dHevizJoWEhWowz8q/johnh-2023-2.bib","dataSources":["YLyu3mj3xsBeoqiHK","fLZcDgNSoSuatv6aX","fxEParwu2ZfurScPY","7nuQvtHTqKrLmgu99"],"keywords":["anycast","dns","design","latency"],"search_terms":["anycast","latency","many","sites","enough","schmidt","heidemann","kuipers"],"title":"Anycast Latency: How Many Sites Are Enough?","year":2017}