Welcome

ANYCAST-1

Investigate anycast routing. Various interesting issues:

Understanding routing impact of adding/removing instances CDNs do a lot of things to make their anycast work well --prepending, communities, selective advertising, regional anycast addresses. How should you decide how to configure your anycast? Use PEERING to Influence how remote ASes reach your AS. Do informed AS path prepending, rather than tweak and pray :-). Use online feedback to selectively filter announcements to peers, etc.

Use BGPStream (e.g., pybgpstream or bgpreader) to observe changes. Option to coordinate with the challenge on live BGPlay to feed BGPlay, or with challenge [V2] or use other viz. Data plane measurements could generate time series that can be visualized in Charthouse.

Three??? anycast nodes using Peering.usc.edu

Traceroutes using atlas Visualization through d3 framework (Circular view: http://bl.ocks.org/mbostock/4063550) Map/Circular ASN view

What happens when you add or remove instances can you predict where the traffic goes.

Prefix

184.164.240.0/24(everywhere)

184.164.241.0/24

61574 amsterdam01 tap5 up 100.126.4.3

61575 cornell01 tap3 down

61576 gatech01 tap6 up 100.126.5.4

263842 isi01 tap2 up 100.126.1.2

263844 seattle01 tap1 up 100.126.0.4

263843 ufmg01 tap7 up 100.126.6.2

47065 phoenix01 tap4 up 100.126.3.2

61574, 61575, 61576, 263842, 263843, 263844