Add data based on atlas traceroutes

[kroeckx]

This also contains the commit from #397

[lspgn]

Hello,
Could you detail a bit the process with Atlas traceroutes? Does it include the false positives?
I prefer putting only what the network does. Makes it easier to read than "not filtering".
There are also more states with partial filtering which would need to be featured.

This rewrites every line and reviewing it is a considerable amount of work.

[kroeckx]

Could you detail a bit the process with Atlas traceroutes? Does it include the false positives? I prefer putting only what the network does. Makes it easier to read than "_not filtering_". There are also more states with partial filtering which would need to be featured.

All the ones I've added are "not filtering". I've look at the traceroutes that are able to reach it, and then marked each AS on that route as not filtering. I guess there could be that are partially filtering that I now mark as not filtering.

This rewrites every line and reviewing it is a considerable amount of work.

Please only look at the 2nd commit.

[kroeckx]

First let's properly define the terms.
False positive: It looks like their filtering, but they're not
False negative: It looks like their not filtering, but they are

Examples of false positive:

• There was just some network problem at the time
• They're not filtering, but all (or their only) transit provider(s) is filtering
• They're only filtering some peers
• They're only partially filtering, because for whatever reason they can't filter all ranges
• They're actually just filtering some known test ranges

Examples of false negatives:

• They are filtering, but they have a default route to one of their transit providers that doesn't filter

Since it's all results for where it could reach an invalid route, it can not contain false positives, but can contain false negatives. It can mark things that are partially filtering as not filtering, but if that's the case, they can just open a pull request to fix that.