Closed SichangHe closed 1 year ago
The small amounts of Peering Sets and Filter Sets appeared are surprising to me, but the number of ASes appeared seems right, so I am positive that I did not just collect stats from a subset of all AutNums by mistake.
I think thees ratios make sense. My impression was always that operators use AS-sets instead of route-sets. I don't think I have ever seen a filter-set or peering-set. Can you post some?
While looking for fltr-bogons-v6
, which appears in policies, I found something interesting.
fltr-bogons-v6
does not exist in the IRR, but AS39904:fltr-bogons-v6
does, and ASes presumably mean to do a shorthand.
AS3344:PRNG-LIPEX
does not exist in RIPE despite being referred there.
By any chance, is fltr-bogons-v6
reffered to by AS39904? Maybe they forgot the name they used for their own filter-set
?
No. fltr-bogons-v6
(without the prefix) is referred to by AS15562, AS208391, AS212123, AS209718, AS211398, AS199839.
(Useful side note: rg -C40
)
Well, I couldn't find where the value of this fltr-bogons-v6
is coming from... so I guess we just flag it as unrecorded.
Type | ASes | AS Sets | Route Sets | Peering Sets | Filter Sets |
---|---|---|---|---|---|
Total | 78951 | 59724 | 24652 | 342 | 202 |
Appeared | 58976 | 22110 | 1892 | 80 | 64 |
% | 74.70 | 37.02 | 7.68 | 23.39 | 31.68 |
Lists of them are as below:
as_sets_appeared_in_rules.csv aut_nums_appeared_in_rules.csv filter_sets_appeared_in_rules.csv peering_sets_appeared_in_rules.csv route_sets_appeared_in_rules.csv
Findings of https://github.com/SichangHe/internet_route_verification/commit/f5e73fe7d30cc71c5f93322574dd7d6212c17927.