[db-wg] FW: IRR Report for RIPE managed space
- Previous message (by thread): [db-wg] db-wg Digest, Vol 39, Issue 12
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Fri Nov 28 12:22:43 CET 2014
Hi db-wg, I think this is might interest some of you as well. I am researching impact of ignoring route objects in non-RIPE IRRs which cover RIPE managed space when generating filters. I encourage discussion in on the routing-wg list. Kind regards, Job ----- Forwarded message from Job Snijders <job at instituut.net> ----- Date: Fri, 28 Nov 2014 11:32:06 +0100 From: Job Snijders <job at instituut.net> To: routing-wg at ripe.net Subject: IRR Report for RIPE managed space Hi routing-wg, I am assessing the state of IRR. I took yesterday's IRR dumps which we use to generate filters, and correlated that with a RIB dump from the NLNOG RING Looking Glass. Keep in mind that prefixes can overlap, duplicate route objects can exist, etc when looking at this data. Consider all values carefully. Blocks IANA handed down to RIPE: 2/8 5/8 31/8 37/8 46/8 62/8 77/8 78/8 79/8 80/8 81/8 82/8 83/8 84/8 85/8 86/8 87/8 88/8 89/8 90/8 91/8 92/8 93/8 94/8 95/8 109/8 176/8 178/8 185/8 193/8 194/8 195/8 212/8 213/8 217/8 (any holes in these blocks are dealt with). BGP Snapshot taken on 27 November 2014 around 18:00 UTC. TOTALS: - total IPv4 route objects present in the specific IRR. - total of prefixes observed in DFZ which length-wise match with a route object in the IRR. (the closer this number is to the previous value, the better) - total of prefixes with a exact matching prefix-length AND origin AS as observed in the BGP table snapshot. (higher is better) - total of prefixes which fall within RIPE IP space for which a route object was detected AND a exact match in the BGP snapshot. note: this includes non-ripe-managed-space (lower is better) - total of prefixes which fall within RIPE IP space for which a route object was detected AND a exact match in the BGP snapshot AND where the origin AS as listed in the foreign object matches with the BGP table. note: this includes non-ripe-managed-space (lower is better) DUPLICATE: a route object that exists both in a foreign IRR and the RIPE IRR with same prefix-length and origin AS number. Because this data is duplicated such these foreign objects can safely be ignored when generating filters. ERROR_ROAMING: a route object that covers RIPE IP space, but for which no route object in the RIPE IRR database exists. Such objects should be moved to the RIPE IRR. Possible operational impact. Lower value is better. MORE_SPECIFIC_ROAMING: a route object in a foreign IRR which covers part of a route object which is present in the RIPE IRR. Origin AS is the same in both objects. NON_RIPE_MANAGED: IANA handed /8 blocks down to RIPE, but there are holes in these /8 blocks. For informative purposes the number is listed. The filter implementation would not give these blocks special protection like it would protect "RIPE proper" IP space. RIPE lists these blocks as 'NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK' in inetnums in RIPE IRR. ORIGIN_MISMATCH - IRR: both a route object exist in the RIPE IRR as well as in a foreign IRR, for the exact same prefix + prefix-length. The origin AS does not match between the RIPE version and the foreign version. Lower is better, but operational impact depends on the next two values. ORIGIN_MISMATCH - BGP: both a route object exist in the RIPE IRR as well as in a foreign IRR, for the exact same prefix + prefix-length. The origin AS does not match between the RIPE version and the foreign version. The lower this number is, the better. ORIGIN_MISMATCH - RIPE's version in BGP: both a route object exist in the RIPE IRR as well as in a foreign IRR, for the exact same prefix + prefix-length. The origin AS does not match between the RIPE version and the foreign version. The closer this number is to the previous value, the better. afrinic.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 315 119 in DFZ w/ matching origin: 119 RIPE pfx in DFZ : 54 RIPE pfx in DFZ w/ origin: 54 DUPLICATE : 0 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 0 0 NON_RIPE_MANAGED : 131 54 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 altdb.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 13998 7940 in DFZ w/ matching origin: 5032 RIPE pfx in DFZ : 235 RIPE pfx in DFZ w/ origin: 149 DUPLICATE : 71 ERROR_ROAMING : 155 79 MORE_SPECIFIC_ROAMING : 96 42 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 76 55 RIPE's version in DFZ : 42 apnic.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 90224 30804 in DFZ w/ matching origin: 27875 RIPE pfx in DFZ : 0 RIPE pfx in DFZ w/ origin: 0 DUPLICATE : 0 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 8 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 arin.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 24032 10416 in DFZ w/ matching origin: 6925 RIPE pfx in DFZ : 240 RIPE pfx in DFZ w/ origin: 79 DUPLICATE : 56 ERROR_ROAMING : 92 39 MORE_SPECIFIC_ROAMING : 361 45 NON_RIPE_MANAGED : 53 16 ORIGIN_MISMATCH : 118 96 RIPE's version in DFZ : 91 bboi.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 1326 857 in DFZ w/ matching origin: 764 RIPE pfx in DFZ : 4 RIPE pfx in DFZ w/ origin: 2 DUPLICATE : 5 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 0 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 1 1 RIPE's version in DFZ : 1 bell.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 29531 1710 in DFZ w/ matching origin: 655 RIPE pfx in DFZ : 2 RIPE pfx in DFZ w/ origin: 2 DUPLICATE : 2 ERROR_ROAMING : 2 0 MORE_SPECIFIC_ROAMING : 6 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 gt.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 2479 1196 in DFZ w/ matching origin: 754 RIPE pfx in DFZ : 0 RIPE pfx in DFZ w/ origin: 0 DUPLICATE : 0 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 1 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 jpirr.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 7685 6019 in DFZ w/ matching origin: 5821 RIPE pfx in DFZ : 11 RIPE pfx in DFZ w/ origin: 11 DUPLICATE : 4 ERROR_ROAMING : 9 5 MORE_SPECIFIC_ROAMING : 5 2 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 level3.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 87609 44874 in DFZ w/ matching origin: 23408 RIPE pfx in DFZ : 1155 RIPE pfx in DFZ w/ origin: 678 DUPLICATE : 384 ERROR_ROAMING : 316 102 MORE_SPECIFIC_ROAMING : 1526 233 NON_RIPE_MANAGED : 208 69 ORIGIN_MISMATCH : 591 460 RIPE's version in DFZ : 367 nttcom.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 208425 60603 in DFZ w/ matching origin: 42122 RIPE pfx in DFZ : 1135 RIPE pfx in DFZ w/ origin: 875 DUPLICATE : 623 ERROR_ROAMING : 229 92 MORE_SPECIFIC_ROAMING : 5020 510 NON_RIPE_MANAGED : 77 40 ORIGIN_MISMATCH : 144 100 RIPE's version in DFZ : 85 radb.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 677083 205492 in DFZ w/ matching origin: 136172 RIPE pfx in DFZ : 7051 RIPE pfx in DFZ w/ origin: 4550 DUPLICATE : 4647 ERROR_ROAMING : 1932 789 MORE_SPECIFIC_ROAMING : 8958 1271 NON_RIPE_MANAGED : 519 151 ORIGIN_MISMATCH : 2602 1764 RIPE's version in DFZ : 1680 rgnet.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 311 77 in DFZ w/ matching origin: 45 RIPE pfx in DFZ : 0 RIPE pfx in DFZ w/ origin: 0 DUPLICATE : 0 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 0 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 savvis.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 92031 33113 in DFZ w/ matching origin: 18417 RIPE pfx in DFZ : 4417 RIPE pfx in DFZ w/ origin: 3076 DUPLICATE : 3626 ERROR_ROAMING : 674 367 MORE_SPECIFIC_ROAMING : 4052 927 NON_RIPE_MANAGED : 512 157 ORIGIN_MISMATCH : 1329 784 RIPE's version in DFZ : 725 tc.db-result-parsed IRR BGP TOTAL ROUTE OBJECTS : 3070 1462 in DFZ w/ matching origin: 1432 RIPE pfx in DFZ : 0 RIPE pfx in DFZ w/ origin: 0 DUPLICATE : 0 ERROR_ROAMING : 0 0 MORE_SPECIFIC_ROAMING : 0 0 NON_RIPE_MANAGED : 0 0 ORIGIN_MISMATCH : 0 0 RIPE's version in DFZ : 0 Total number of prefixes for which a route object ONLY exists in a foreign IRR AND which were observed in the DFZ: 1004 prefixes (aggregated 522), spread over 280 ASNs. List "ERROR_ROAMING.txt" is attached. Total number of prefixes for which a route object exists in both RIPE IRR and a foreign IRR (with mismatching origins), AND where the foreign version is observered in the DFZ: 269 prefixes spread over 119 ASNs. List is attached as "ORIGIN_MISMATCH.txt". Kind regards, Job
- Previous message (by thread): [db-wg] db-wg Digest, Vol 39, Issue 12
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]