Proceedings of the ACM Internet Measurement Conference 2020
DOI: 10.1145/3419394.3423646
|View full text |Cite
|
Sign up to set email alerts
|

MAnycast2

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 13 publications
(2 citation statements)
references
References 11 publications
0
2
0
Order By: Relevance
“…We chose to measure IP anycast use ourselves rather than use on publicly available data. While a public anycast census exists [22], it lacks IPv6 information. Regarding geolocation, the iGreedy measurement mechanics offer the means to determine this for anycast IP addresses.…”
Section: B Measurementsmentioning
confidence: 99%
“…We chose to measure IP anycast use ourselves rather than use on publicly available data. While a public anycast census exists [22], it lacks IPv6 information. Regarding geolocation, the iGreedy measurement mechanics offer the means to determine this for anycast IP addresses.…”
Section: B Measurementsmentioning
confidence: 99%
“…Anycasting is supported by both versions 4 and 6 of the Internet Protocol (IP) as documented in RFCs 1546 and 4291, and the Border Gateway Protocol (BGP-4, RFC 4271). It plays a vital role for DNS and CDN and services, but different issues have been noted, including the detection latency of IP anycast prefixes [20], AS-level anycast path inflation [21], and client-server mapping limitations that arise in CDN routing [2]. Several enhancements have been discussed focusing on either performance, see, e.g., [22,23], or security, e.g., to mitigate distributed denial-of-service (DDoS) attacks [5].…”
Section: Related Workmentioning
confidence: 99%