- routing-wg - mailman.ripe.net

Routinator 0.1.0 'Godspeed!', RPKI Relying Party Software released
by Alex Band 01 Nov '18

01 Nov '18

Further to our presentation in the routing working group at RIPE 77, we’re happy to tell you Routinator 0.1.0 'Godspeed!’ has now been released. The initial release implements the basic set of functionality: fetching and validating RPKI data and exposing route origin attestations both as output (CSV, JSON, RPSL) and to routers via the RPKI-RTR protocol. Assuming you have rsync and the C toolchain but not yet Rust, here’s how you get the Routinator to run as an RTR server listening on 127.0.0.1 port 3323: curl https://sh.rustup.rs -sSf | sh source ~/.cargo/env cargo install routinator routinator -r -l 127.0.0.1:3323 We’re very much looking forward to your operational feedback, to ensure this package runs well in a wide variety of environments. Going forward, we’ll be focussing on monitoring for the next release. You can find the source code and further details on Github: https://github.com/NLnetLabs/routinator Cheers, Alex Band NLnet Labs

1 0

Weekly Routing Table Report
by cscora＠apnic.net 26 Oct '18

26 Oct '18

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 27 Oct, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 722250 Prefixes after maximum aggregation (per Origin AS): 278090 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 346952 Total ASes present in the Internet Routing Table: 62257 Prefixes per ASN: 11.60 Origin-only ASes present in the Internet Routing Table: 53743 Origin ASes announcing only one prefix: 23346 Transit ASes present in the Internet Routing Table: 8514 Transit-only ASes present in the Internet Routing Table: 263 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 44 Max AS path prepend of ASN ( 19955) 41 Prefixes from unregistered ASNs in the Routing Table: 40 Number of instances of unregistered ASNs: 40 Number of 32-bit ASNs allocated by the RIRs: 24617 Number of 32-bit ASNs visible in the Routing Table: 19895 Prefixes from 32-bit ASNs in the Routing Table: 84143 Number of bogon 32-bit ASNs visible in the Routing Table: 230 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 261 Number of addresses announced to Internet: 2860457139 Equivalent to 170 /8s, 127 /16s and 28 /24s Percentage of available address space announced: 77.3 Percentage of allocated address space announced: 77.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.1 Total number of prefixes smaller than registry allocations: 241318 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 196372 Total APNIC prefixes after maximum aggregation: 56014 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 194079 Unique aggregates announced from the APNIC address blocks: 80222 APNIC Region origin ASes present in the Internet Routing Table: 9197 APNIC Prefixes per ASN: 21.10 APNIC Region origin ASes announcing only one prefix: 2576 APNIC Region transit ASes present in the Internet Routing Table: 1369 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4168 Number of APNIC addresses announced to Internet: 767928322 Equivalent to 45 /8s, 197 /16s and 168 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-139577 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 214886 Total ARIN prefixes after maximum aggregation: 102025 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 214232 Unique aggregates announced from the ARIN address blocks: 102051 ARIN Region origin ASes present in the Internet Routing Table: 18279 ARIN Prefixes per ASN: 11.72 ARIN Region origin ASes announcing only one prefix: 6780 ARIN Region transit ASes present in the Internet Routing Table: 1819 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 44 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2480 Number of ARIN addresses announced to Internet: 1102718992 Equivalent to 65 /8s, 186 /16s and 40 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-399260 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 197293 Total RIPE prefixes after maximum aggregation: 94314 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 193756 Unique aggregates announced from the RIPE address blocks: 114550 RIPE Region origin ASes present in the Internet Routing Table: 25591 RIPE Prefixes per ASN: 7.57 RIPE Region origin ASes announcing only one prefix: 11485 RIPE Region transit ASes present in the Internet Routing Table: 3536 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7526 Number of RIPE addresses announced to Internet: 714749056 Equivalent to 42 /8s, 154 /16s and 52 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-210331 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/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, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 93819 Total LACNIC prefixes after maximum aggregation: 21500 LACNIC Deaggregation factor: 4.36 Prefixes being announced from the LACNIC address blocks: 95259 Unique aggregates announced from the LACNIC address blocks: 41519 LACNIC Region origin ASes present in the Internet Routing Table: 7692 LACNIC Prefixes per ASN: 12.38 LACNIC Region origin ASes announcing only one prefix: 2103 LACNIC Region transit ASes present in the Internet Routing Table: 1448 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5237 Number of LACNIC addresses announced to Internet: 172397600 Equivalent to 10 /8s, 70 /16s and 148 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 19839 Total AfriNIC prefixes after maximum aggregation: 4203 AfriNIC Deaggregation factor: 4.72 Prefixes being announced from the AfriNIC address blocks: 24663 Unique aggregates announced from the AfriNIC address blocks: 8370 AfriNIC Region origin ASes present in the Internet Routing Table: 1210 AfriNIC Prefixes per ASN: 20.38 AfriNIC Region origin ASes announcing only one prefix: 402 AfriNIC Region transit ASes present in the Internet Routing Table: 241 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 26 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 484 Number of AfriNIC addresses announced to Internet: 102236160 Equivalent to 6 /8s, 24 /16s and 0 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 4634 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4522 509 503 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 2950 1153 93 VIETEL-AS-AP Viettel Group, VN 45899 2947 1685 110 VNPT-AS-VN VNPT Corp, VN 4766 2807 11130 763 KIXS-AS-KR Korea Telecom, KR 9829 2746 1496 551 BSNL-NIB National Internet Backbone, IN 9394 2426 4907 30 CTTNET China TieTong Telecommunications 9808 2250 8699 26 CMNET-GD Guangdong Mobile Communication 17974 2246 968 51 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4755 2130 421 171 TATACOMM-AS TATA Communications formerl Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6327 3455 1324 84 SHAW - Shaw Communications Inc., CA 11492 3453 223 640 CABLEONE - CABLE ONE, INC., US 22773 3273 2972 164 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2354 5006 851 AMAZON-02 - Amazon.com, Inc., US 18566 2154 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2145 2737 540 CHARTER-NET-HKY-NC - Charter Communicat 16625 2099 1128 1565 AKAMAI-AS - Akamai Technologies, Inc., 5650 2084 3074 1461 FRONTIER-FRTR - Frontier Communications 30036 2052 346 152 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 2041 5080 596 CENTURYLINK-US-LEGACY-QWEST - CenturyLi Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 4997 1616 132 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3037 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2559 573 1910 AKAMAI-ASN1, US 12389 2144 2125 679 ROSTELECOM-AS, RU 34984 2021 335 532 TELLCOM-AS, TR 9121 1871 1691 17 TTNET, TR 13188 1604 100 45 TRIOLAN, UA 8402 1285 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1241 355 21 UKRTELNET, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5434 3307 599 Uninet S.A. de C.V., MX 10620 3196 489 810 Telmex Colombia S.A., CO 11830 2665 370 80 Instituto Costarricense de Electricidad 6503 1660 449 55 Axtel, S.A.B. de C.V., MX 7303 1436 959 209 Telecom Argentina S.A., AR 28573 1125 2237 181 CLARO S.A., BR 6147 1090 377 29 Telefonica del Peru S.A.A., PE 3816 1027 512 114 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 936 145 71 Alestra, S. de R.L. de C.V., MX 13999 921 537 258 Mega Cable, S.A. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1170 396 48 LINKdotNET-AS, EG 37611 907 107 9 Afrihost, ZA 36903 794 399 146 MT-MPLS, MA 36992 776 1411 41 ETISALAT-MISR, EG 24835 676 758 20 RAYA-AS, EG 8452 636 1728 15 TE-AS TE-AS, EG 37492 467 470 57 ORANGE-, TN 29571 461 70 12 ORANGE-COTE-IVOIRE, CI 23889 396 231 15 MauritiusTelecom, MU 37342 394 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5434 3307 599 Uninet S.A. de C.V., MX 12479 4997 1616 132 UNI2-AS, ES 4538 4634 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4522 509 503 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3455 1324 84 SHAW - Shaw Communications Inc., CA 11492 3453 223 640 CABLEONE - CABLE ONE, INC., US 22773 3273 2972 164 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3196 489 810 Telmex Colombia S.A., CO 8551 3037 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 4997 4865 UNI2-AS, ES 4538 4634 4560 ERX-CERNET-BKB China Education and Research Net 7545 4522 4019 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3455 3371 SHAW - Shaw Communications Inc., CA 22773 3273 3109 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 3037 2994 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7552 2950 2857 VIETEL-AS-AP Viettel Group, VN 45899 2947 2837 VNPT-AS-VN VNPT Corp, VN 11492 3453 2813 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 64500 DOCUMENT 45.43.56.0/24 45474 NEXUSGUARD-AS-AP Suite 2101~02 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64121 UNALLOCATED 98.159.9.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.12.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64140 UNALLOCATED 98.159.14.0/24 64121 UNKNOWN 65551 DOCUMENT 103.112.64.0/23 58889 ZOL-BD Zx Online Ltd, BD 65001 PRIVATE 109.161.56.0/24 13118 ASN-YARTELECOM PJSC Rostelecom 92937 UNALLOCATED 110.49.72.0/24 45458 SBN-AWN-AS-02-AP SBN-ISP/AWN-I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 45.121.32.0/22 134356 UNKNOWN 45.124.164.0/22 38803 GTELECOM-AUSTRALIA Gtelecom-AUSTRALIA, AU 45.252.236.0/22 38803 GTELECOM-AUSTRALIA Gtelecom-AUSTRALIA, AU 64.28.160.0/20 20475 AS20475 - Global Capacity, LLC, US 64.29.240.0/20 27279 -Reserved AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:14 /9:11 /10:36 /11:98 /12:289 /13:567 /14:1122 /15:1888 /16:13319 /17:7885 /18:13837 /19:25410 /20:39613 /21:46014 /22:89730 /23:73619 /24:406579 /25:821 /26:624 /27:639 /28:35 /29:21 /30:22 /31:4 /32:53 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3811 4997 UNI2-AS, ES 6327 3240 3455 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2740 3453 CABLEONE - CABLE ONE, INC., US 22773 2529 3273 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2493 3037 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2048 2154 MEGAPATH5-US - MegaPath Corporation, US 11830 2012 2665 Instituto Costarricense de Electricidad y Telec 30036 1801 2052 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1762 2084 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1615 2:893 4:18 5:2670 6:43 7:1 8:1142 12:1873 13:231 14:1858 15:33 16:3 17:192 18:58 20:50 23:2471 24:2435 25:2 27:2512 31:2025 32:86 35:30 36:553 37:2927 38:1560 39:262 40:122 41:3211 42:717 43:1979 44:125 45:5844 46:3100 47:228 49:1351 50:1069 51:319 52:1098 54:361 55:1 56:12 57:38 58:1623 59:991 60:418 61:2088 62:1891 63:1795 64:5062 65:2198 66:4830 67:2667 68:1155 69:3341 70:1168 71:591 72:2239 74:2728 75:415 76:470 77:1662 78:1742 79:2217 80:1566 81:1414 82:1053 83:789 84:1043 85:2074 86:561 87:1463 88:948 89:2379 90:208 91:6450 92:1275 93:2394 94:2447 95:3020 96:913 97:351 98:945 99:147 100:86 101:1160 102:263 103:18982 104:3586 105:236 106:898 107:1835 108:709 109:3374 110:1667 111:1814 112:1345 113:1312 114:1142 115:1689 116:1647 117:1796 118:2194 119:1673 120:1082 121:1038 122:2320 123:1656 124:1451 125:1940 128:1209 129:672 130:502 131:1610 132:724 133:191 134:1035 135:237 136:526 137:662 138:1976 139:709 140:553 141:753 142:802 143:1021 144:842 145:496 146:1238 147:773 148:1644 149:781 150:762 151:996 152:875 153:325 154:1895 155:950 156:1557 157:820 158:652 159:1856 160:1474 161:871 162:2639 163:740 164:1096 165:1570 166:454 167:1344 168:3150 169:859 170:3989 171:496 172:1054 173:2083 174:993 175:825 176:2121 177:4019 178:2519 179:1279 180:2125 181:2448 182:2578 183:1305 184:1125 185:14273 186:3613 187:2451 188:2923 189:1997 190:8344 191:1388 192:9887 193:6337 194:5169 195:4041 196:2820 197:1620 198:5675 199:5964 200:7446 201:5011 202:10247 203:10147 204:4615 205:3009 206:3224 207:3203 208:3945 209:4149 210:3837 211:1985 212:2997 213:2810 214:1050 215:54 216:6001 217:2186 218:863 219:577 220:1818 221:994 222:971 223:1394 End of report

1 0

New on RIPE Labs: Routing Security is Hot!
by Mirjam Kuehne 23 Oct '18

23 Oct '18

Dear colleagues, In this new RIPE Labs article Melchior Aelmans explains why routing security is a hot topic and why you should join the RPKI signing party: https://labs.ripe.net/Members/melchior_aelmans/routing-security-is-hot Kind regards, Mirjam Kühne RIPE NCC

1 0

Weekly Routing Table Report
by cscora＠apnic.net 20 Oct '18

20 Oct '18

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 20 Oct, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 720932 Prefixes after maximum aggregation (per Origin AS): 277736 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 346559 Total ASes present in the Internet Routing Table: 62172 Prefixes per ASN: 11.60 Origin-only ASes present in the Internet Routing Table: 53659 Origin ASes announcing only one prefix: 23351 Transit ASes present in the Internet Routing Table: 8513 Transit-only ASes present in the Internet Routing Table: 258 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 36 Max AS path prepend of ASN ( 30873) 34 Prefixes from unregistered ASNs in the Routing Table: 45 Number of instances of unregistered ASNs: 45 Number of 32-bit ASNs allocated by the RIRs: 24512 Number of 32-bit ASNs visible in the Routing Table: 19802 Prefixes from 32-bit ASNs in the Routing Table: 83276 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 265 Number of addresses announced to Internet: 2855841539 Equivalent to 170 /8s, 56 /16s and 175 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.1 Total number of prefixes smaller than registry allocations: 240937 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 196031 Total APNIC prefixes after maximum aggregation: 55976 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 193756 Unique aggregates announced from the APNIC address blocks: 80180 APNIC Region origin ASes present in the Internet Routing Table: 9173 APNIC Prefixes per ASN: 21.12 APNIC Region origin ASes announcing only one prefix: 2566 APNIC Region transit ASes present in the Internet Routing Table: 1366 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4141 Number of APNIC addresses announced to Internet: 767770050 Equivalent to 45 /8s, 195 /16s and 61 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-139577 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 214759 Total ARIN prefixes after maximum aggregation: 101898 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 214148 Unique aggregates announced from the ARIN address blocks: 101956 ARIN Region origin ASes present in the Internet Routing Table: 18276 ARIN Prefixes per ASN: 11.72 ARIN Region origin ASes announcing only one prefix: 6787 ARIN Region transit ASes present in the Internet Routing Table: 1819 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2468 Number of ARIN addresses announced to Internet: 1098652576 Equivalent to 65 /8s, 124 /16s and 27 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-399260 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 197098 Total RIPE prefixes after maximum aggregation: 94122 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 193556 Unique aggregates announced from the RIPE address blocks: 114401 RIPE Region origin ASes present in the Internet Routing Table: 25565 RIPE Prefixes per ASN: 7.57 RIPE Region origin ASes announcing only one prefix: 11475 RIPE Region transit ASes present in the Internet Routing Table: 3540 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7497 Number of RIPE addresses announced to Internet: 714892672 Equivalent to 42 /8s, 156 /16s and 101 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-210331 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/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, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 93394 Total LACNIC prefixes after maximum aggregation: 21481 LACNIC Deaggregation factor: 4.35 Prefixes being announced from the LACNIC address blocks: 94805 Unique aggregates announced from the LACNIC address blocks: 41433 LACNIC Region origin ASes present in the Internet Routing Table: 7667 LACNIC Prefixes per ASN: 12.37 LACNIC Region origin ASes announcing only one prefix: 2118 LACNIC Region transit ASes present in the Internet Routing Table: 1445 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5216 Number of LACNIC addresses announced to Internet: 172298784 Equivalent to 10 /8s, 69 /16s and 18 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 19604 Total AfriNIC prefixes after maximum aggregation: 4219 AfriNIC Deaggregation factor: 4.65 Prefixes being announced from the AfriNIC address blocks: 24402 Unique aggregates announced from the AfriNIC address blocks: 8345 AfriNIC Region origin ASes present in the Internet Routing Table: 1207 AfriNIC Prefixes per ASN: 20.22 AfriNIC Region origin ASes announcing only one prefix: 405 AfriNIC Region transit ASes present in the Internet Routing Table: 243 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 26 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 480 Number of AfriNIC addresses announced to Internet: 101797120 Equivalent to 6 /8s, 17 /16s and 77 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 4638 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4471 496 489 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 2985 1153 93 VIETEL-AS-AP Viettel Group, VN 45899 2839 1674 159 VNPT-AS-VN VNPT Corp, VN 4766 2809 11130 764 KIXS-AS-KR Korea Telecom, KR 9829 2734 1495 548 BSNL-NIB National Internet Backbone, IN 9394 2503 4907 31 CTTNET China TieTong Telecommunications 9808 2252 8699 26 CMNET-GD Guangdong Mobile Communication 17974 2240 968 51 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4755 2133 422 172 TATACOMM-AS TATA Communications formerl Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 11492 3495 226 581 CABLEONE - CABLE ONE, INC., US 6327 3454 1324 84 SHAW - Shaw Communications Inc., CA 22773 3268 2971 161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2325 5005 834 AMAZON-02 - Amazon.com, Inc., US 18566 2156 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2148 2737 515 CHARTER-NET-HKY-NC - Charter Communicat 5650 2085 3074 1461 FRONTIER-FRTR - Frontier Communications 16625 2081 1118 1555 AKAMAI-AS - Akamai Technologies, Inc., 209 2036 5079 594 CENTURYLINK-US-LEGACY-QWEST - CenturyLi 30036 2033 343 228 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 4996 1616 132 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3045 378 50 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2569 578 1913 AKAMAI-ASN1, US 12389 2119 2067 686 ROSTELECOM-AS, RU 34984 2030 336 527 TELLCOM-AS, TR 9121 1862 1691 17 TTNET, TR 13188 1604 100 45 TRIOLAN, UA 8402 1284 544 14 CORBINA-AS OJSC "Vimpelcom", RU 6849 1241 355 21 UKRTELNET, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5424 3305 609 Uninet S.A. de C.V., MX 10620 3199 490 804 Telmex Colombia S.A., CO 11830 2661 370 83 Instituto Costarricense de Electricidad 6503 1651 449 55 Axtel, S.A.B. de C.V., MX 7303 1432 956 206 Telecom Argentina S.A., AR 6147 1092 377 29 Telefonica del Peru S.A.A., PE 28573 1083 2234 192 CLARO S.A., BR 3816 1025 508 115 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 937 145 72 Alestra, S. de R.L. de C.V., MX 18881 919 1114 28 TELEFÔNICA BRASIL S.A, BR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 949 395 41 LINKdotNET-AS, EG 37611 902 107 9 Afrihost, ZA 36903 794 399 146 MT-MPLS, MA 36992 753 1411 41 ETISALAT-MISR, EG 24835 682 758 20 RAYA-AS, EG 8452 612 1728 15 TE-AS TE-AS, EG 29571 462 70 12 ORANGE-COTE-IVOIRE, CI 37492 440 467 62 ORANGE-, TN 23889 394 231 15 MauritiusTelecom, MU 37342 394 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5424 3305 609 Uninet S.A. de C.V., MX 12479 4996 1616 132 UNI2-AS, ES 4538 4638 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4471 496 489 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 11492 3495 226 581 CABLEONE - CABLE ONE, INC., US 6327 3454 1324 84 SHAW - Shaw Communications Inc., CA 22773 3268 2971 161 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3199 490 804 Telmex Colombia S.A., CO 8551 3045 378 50 BEZEQ-INTERNATIONAL-AS Bezeqint Interne Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 4996 4864 UNI2-AS, ES 4538 4638 4564 ERX-CERNET-BKB China Education and Research Net 7545 4471 3982 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3454 3370 SHAW - Shaw Communications Inc., CA 22773 3268 3107 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 3045 2995 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3495 2914 CABLEONE - CABLE ONE, INC., US 7552 2985 2892 VIETEL-AS-AP Viettel Group, VN 45899 2839 2680 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 64500 DOCUMENT 45.43.56.0/24 45474 NEXUSGUARD-AS-AP Suite 2101~02 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64121 UNALLOCATED 98.159.9.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.12.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64140 UNALLOCATED 98.159.14.0/24 64121 UNKNOWN 65551 DOCUMENT 103.112.64.0/23 58889 ZOL-BD Zx Online Ltd, BD 65001 PRIVATE 109.161.56.0/24 13118 ASN-YARTELECOM PJSC Rostelecom 92937 UNALLOCATED 110.49.72.0/24 45458 SBN-AWN-AS-02-AP SBN-ISP/AWN-I Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 45.121.32.0/22 134356 UNKNOWN 45.124.164.0/22 38803 GTELECOM-AUSTRALIA Gtelecom-AUSTRALIA, AU 45.252.236.0/22 38803 GTELECOM-AUSTRALIA Gtelecom-AUSTRALIA, AU 64.28.160.0/20 20475 AS20475 - Global Capacity, LLC, US 64.29.240.0/20 27279 -Reserved AS-, ZZ 64.30.152.0/24 15830 TELECITY-LON, GB Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:14 /9:11 /10:36 /11:98 /12:289 /13:566 /14:1105 /15:1889 /16:13326 /17:7890 /18:13785 /19:25401 /20:39569 /21:45929 /22:89486 /23:73423 /24:405894 /25:822 /26:625 /27:639 /28:36 /29:21 /30:22 /31:4 /32:52 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3779 4996 UNI2-AS, ES 6327 3239 3454 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2764 3495 CABLEONE - CABLE ONE, INC., US 22773 2527 3268 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 2501 3045 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 18566 2050 2156 MEGAPATH5-US - MegaPath Corporation, US 11830 2011 2661 Instituto Costarricense de Electricidad y Telec 30036 1781 2033 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1762 2085 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1612 2:892 4:18 5:2676 6:43 7:1 8:1142 12:1869 13:222 14:1848 15:33 16:3 17:192 18:58 20:50 23:2471 24:2434 25:2 27:2512 31:2013 32:84 35:30 36:546 37:2918 38:1560 39:262 40:122 41:3179 42:717 43:1959 44:126 45:5808 46:3112 47:222 49:1352 50:1062 51:318 52:1089 54:361 55:1 56:12 57:38 58:1608 59:985 60:417 61:2084 62:1954 63:1805 64:5053 65:2204 66:4817 67:2665 68:1156 69:3345 70:1166 71:590 72:2245 74:2730 75:416 76:458 77:1658 78:1746 79:2226 80:1584 81:1422 82:1052 83:787 84:1048 85:2063 86:568 87:1468 88:942 89:2368 90:215 91:6446 92:1272 93:2392 94:2451 95:3026 96:924 97:353 98:944 99:145 100:86 101:1174 102:252 103:18935 104:3569 105:235 106:769 107:1831 108:710 109:3375 110:1658 111:1815 112:1329 113:1306 114:1143 115:1681 116:1660 117:1802 118:2192 119:1666 120:1083 121:1036 122:2319 123:1664 124:1451 125:1939 128:1206 129:689 130:503 131:1616 132:723 133:191 134:1036 135:237 136:527 137:658 138:1961 139:695 140:553 141:752 142:840 143:988 144:851 145:496 146:1249 147:769 148:1665 149:775 150:763 151:991 152:871 153:325 154:1882 155:941 156:1533 157:813 158:660 159:1867 160:1494 161:852 162:2650 163:735 164:1092 165:1565 166:454 167:1288 168:3138 169:859 170:3982 171:495 172:1040 173:2077 174:997 175:817 176:2107 177:3980 178:2507 179:1305 180:2122 181:2430 182:2596 183:1303 184:1135 185:14239 186:3591 187:2449 188:2930 189:2010 190:8269 191:1361 192:9864 193:6304 194:5153 195:4047 196:2838 197:1618 198:5692 199:5954 200:7407 201:5017 202:10249 203:10199 204:4612 205:2982 206:3217 207:3196 208:3931 209:4160 210:3834 211:1985 212:2983 213:2800 214:1041 215:54 216:6022 217:2181 218:866 219:575 220:1812 221:992 222:967 223:1400 End of report

3 2

Re: [routing-wg] some stats for proposal 2018-06
by Alexander Azimov 18 Oct '18

18 Oct '18

Hi all, In the attachment is raw data that was used in https://ripe77.ripe.net/presentations/123-RIPE-NONAUTH.azimov.pdf It shows a list of globally visible prefixes that have route objects ONLY in RIPE-NONAUTH. For these prefixes, the removal of route objects from this database may lead to DoS. *Numbers for IPv4:* Total number of objects - 69178 Address space covered In other IRRs - 43527 Address space covered In other IRRs with same ASN - 33839 Unique Objects in RIPE-NONAUTH - 25651 Globally visible prefixes – 4507 ASNs - 543 *Numbers for IPv6:* Total number of objects - 1991 Address space covered In other IRRs - 1502 Address space covered In other IRRs with same ASN - 1336 Unique Objects - 489 Globally visible prefixes – 303 ASNs - 86 I haven't yet analyzed to which IRRs the route objects from NONAUTH should belong. So, please take it as input, but there is a significant place for improvement. чт, 18 окт. 2018 г. в 12:58, Alexander Azimov <aa(a)qrator.net>: > Hi all, > > In the attachment is raw data that was used in > https://ripe77.ripe.net/presentations/123-RIPE-NONAUTH.azimov.pdf > It shows a list of globally visible prefixes that have route objects ONLY > in RIPE-NONAUTH. For these prefixes, the removal of route objects from this > database may lead to DoS. > > *Numbers for IPv4:* > Total number of objects - 69178 > > Address space covered In other IRRs - 43527 > > Address space covered In other IRRs with same ASN - 33839 > > Unique Objects in RIPE-NONAUTH - 25651 > > Globally visible prefixes – 4507 > > ASNs - 543 > > > > *Numbers for IPv6:* > Total number of objects - 1991 > > Address space covered In other IRRs - 1502 > > Address space covered In other IRRs with same ASN - 1336 > > Unique Objects - 489 > > Globally visible prefixes – 303 > > ASNs - 86 > > I haven't yet analyzed to which IRRs the route objects from NONAUTH should > belong. So, please take it as input, but there is a significant place for > improvement. > > чт, 18 окт. 2018 г. в 12:48, nusenu <nusenu-lists(a)riseup.net>: > >> here is my data for you to scrutinize since >> Alexander Azimov (slides [3]) had some slightly different (lower) >> numbers (maybe that difference is either caused by a difference in >> TALs configured - or just because we didn't produce the data at the very >> same time >> or just a problem on my side) >> >> [1] 69178 route objects - 758 invalids - 55 of them are announced as >> defined in the route object >> [2] 1991 route5 objects - 16 invalids >> >> That said these are just current numbers but they obviously will change >> over time with the increasing creation of ROA outside of the RIPE region. >> >> >> kind regards, >> nusenu >> PS: I've a few more remarks but I'll postpone them. >> >> [1] >> https://gist.githubusercontent.com/nusenu/21687b0902cc64cd61b92ec5ae66bbc1/… >> [2] >> https://gist.githubusercontent.com/nusenu/7d4c7f6ea5cadb47ff49760e5f2e5aa0/… >> >> format: origin,prefix,RPKI validity state >> >> [3] https://ripe77.ripe.net/presentations/123-RIPE-NONAUTH.azimov.pdf >> >> >> >> -- >> https://twitter.com/nusenu_ >> https://mastodon.social/@nusenu >> >> > > -- > | Alexander Azimov | HLL l QRATOR > | tel.: +7 499 241 81 92 > | mob.: +7 915 360 08 86 > | skype: mitradir > | visit: radar.qrator.net > -- | Alexander Azimov | HLL l QRATOR | tel.: +7 499 241 81 92 | mob.: +7 915 360 08 86 | skype: mitradir | visit: radar.qrator.net

2 1

Re: [routing-wg] some stats for proposal 2018-06
by nusenu 18 Oct '18

18 Oct '18

Hi Alexander, Alexander Azimov wrote: > In the attachment is raw data are you also planing to publish the RPKI validity state of your results per prefix so we can investigate the delta in the results? your attached files (global.non-auth.ipv[46].txt) don't contain RPKI data currently. kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

some stats for proposal 2018-06
by nusenu 18 Oct '18

18 Oct '18

Hi, I support the proposal and I'd like to add a **quick'n dirty** "impact analysis". 1) I took the 69178 [1] RIPE-NONAUTH route objects and run them through RPKI validator* 3. Which gives me 758 RPKI INVALID (669 ASN mismatch + 89 ML mismatch) objects. These objects would be the once that get removed as per the proposal. distribution by RPKI validity state: 67904 UNKNOWN 669 INVALID_ASN 516 VALID 89 INVALID_LENGTH 2) to estimate the impact of the route object deletion I then further categorize these 758 prefixes by asking: - Are they currently announced? (visible in RIS) - Are they currently announced by the origin in the route object? I only looked at exact matches - not less specifics. (RIPEstat prefix-routing-consistency data call was used to answer these questions) If one of these two questions is answered with "no", then I expect the potential impact of the deletion to be smaller than the other once (where both questions are answered with "yes"). Only 55 [3] objects (28 unique ASNs) are currently announced and match the origin in the route object. We can analyze these 55 further by asking "Are there IRR entries for them outside of RIPE-NONAUTH already?" (didn't do that yet) route6 stats ------------- total route6 objects found in RIPE-NONAUTH: 1991 [2] affected prefixes: 18 (12 ASN mismatch + 6 ML mismatch) break down by RPKI validity state* (including INVALID reason): 1879 UNKNOWN 94 VALID 12 INVALID_ASN 6 INVALID_LENGTH kind regards, nusenu [1] https://ftp.ripe.net/ripe/dbase/split/ripe-nonauth.db.route.gz [2] https://ftp.ripe.net/ripe/dbase/split/ripe-nonauth.db.route6.gz (fetched on 2018-10-17) *) ARIN TAL was enabled. [3] AS28885,206.49.101.0/24 AS3741,196.209.251.0/24 AS24218,124.158.224.0/22 AS1680,206.49.94.0/24 AS1680,209.88.155.0/24 AS1680,209.88.156.0/23 AS1680,209.88.158.0/24 AS1680,209.88.172.0/22 AS1680,209.88.176.0/20 AS1680,209.88.192.0/21 AS1680,216.72.32.0/21 AS1680,216.72.40.0/22 AS37403,41.79.150.0/24 AS37403,41.79.149.0/24 AS37403,41.79.151.0/24 AS37403,41.79.148.0/24 AS58396,103.225.172.0/24 AS58396,103.225.173.0/24 AS6908,118.91.174.0/24 AS43578,191.96.102.0/24 AS37403,41.242.40.0/24 AS37403,41.242.41.0/24 AS37403,41.242.42.0/24 AS37403,41.242.43.0/24 AS37403,41.242.44.0/24 AS37403,41.242.46.0/24 AS37403,41.242.45.0/24 AS37403,41.242.47.0/24 AS62000,191.101.23.0/24 AS57944,181.215.247.0/24 AS64484,191.96.249.0/24 AS203098,103.74.176.0/22 AS61317,191.101.96.0/20 AS200651,181.215.43.0/24 AS43818,191.96.113.0/24 AS203061,43.242.0.0/22 AS133537,191.96.38.0/24 AS60945,181.214.57.0/24 AS60458,181.41.199.0/24 AS60458,181.41.218.0/24 AS62240,191.101.22.0/24 AS20860,23.139.0.0/24 AS43818,191.96.60.0/23 AS205158,181.214.155.0/24 AS42962,103.81.184.0/24 AS42962,103.81.185.0/24 AS42962,103.81.186.0/24 AS42962,103.81.184.0/23 AS42962,103.81.186.0/23 AS197226,181.215.195.0/24 AS49835,138.255.89.0/24 AS44812,191.101.42.0/24 AS201942,191.96.124.0/22 AS2856,181.214.148.0/24 AS2856,181.214.231.0/24 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 1

source: RIPE may also contain invalid ROUTEs
by denis walker 18 Oct '18

18 Oct '18

Hi guys There is a corner case where invalid ROUTE(6) objects may occur in the source: RIPE database. Before NWI-5 a ROUTE(6) object could be created either by the address space holder or the ASN holder. Both had to authorise the creation, but whoever created the object would maintain it. Suppose the ASN holder created an object and maintains it, then the address space holder chooses another ASN to announce the address space. The address space holder can delete the ROUTE(6) object using the Force Delete mechanism(1), if they know about it. But many resource holders still don't know such mechanisms exist. They may instead just create an RPKI ROA for the new announcement and leave the old ROUTE(6) object in the database. AFAIK there isn't yet any alignment mechanism, but it has been talked about recently, and the cleanup proposal under discussion only applies to source: RIPE-NONAUTH (but I'm not suggesting you extend it). Although this is a corner case, it means you can't guarantee all the data in source: RIPE is still authoritative. (1) https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-data… cheersdenisco-chair DB-WG

3 4

New on RIPE Labs: The RPKI Observatory
by Mirjam Kuehne 17 Oct '18

17 Oct '18

Dear colleagues, In this RIPE Labs article nusenu talks about why it is important to take care of RPKI misconfigurations, what the impact of ignoring them is, how network operators can easily determine whether they are affected by a specific RPKI misconfiguration and how significantly the amount of RPKI unreachable IP space changed over the course of just a few weeks. https://labs.ripe.net/Members/nusenu_nusenu/the-rpki-observatory Kind regards, Mirjam Kühne RIPE NCC

1 0

Fw: [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects
by denis walker 16 Oct '18

16 Oct '18

Sorry I forgot to include routing-wg on my reply... ----- Forwarded Message ----- From: denis walker via db-wg <db-wg(a)ripe.net> To: Job Snijders <job(a)instituut.net>; Nick Hilliard <nick(a)foobar.org> Cc: Marco Schmidt <mschmidt(a)ripe.net>; "db-wg(a)ripe.net" <db-wg(a)ripe.net> Sent: Tuesday, 16 October 2018, 3:57 Subject: Re: [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects Hi Job Just a couple of points. First is a technical issue with your proposal. In your Rationale you mention ¨creating out of region inetnums¨. It wasn't possible to create such objects. Only out of region aut-nums and route(6)s. You talk about cleaning up garbage in the RIPE-NONAUTH IRR. The principle of cleaning up garbage is always good. But doesn't this still leave a lot of potential garbage in all the commercial IRRs where ROUTE objects can still be created without authorisation by, consent from and knowledge of the address space holder? So should we also be promoting the RIRs authoritative IRRs over commercial IRRs so that ROUTE objects can all be created with proper authorisation? cheersdenisco-chair DB-WG From: Job Snijders via db-wg <db-wg(a)ripe.net> To: Nick Hilliard <nick(a)foobar.org> Cc: Marco Schmidt <mschmidt(a)ripe.net>; db-wg(a)ripe.net Sent: Sunday, 14 October 2018, 8:49 Subject: Re: [db-wg] RIPE Policy Proposal 2018-06 Aims to Delete Conflicting Non-authorative IRR Objects Dear Nick, On Sat, Oct 13, 2018 at 10:38:12PM +0100, Nick Hilliard via db-wg wrote: > Marco Schmidt via db-wg wrote on 11/10/2018 14:18: > > We just published the RIPE Policy proposal, 2018-06, "RIPE NCC IRR > > Database Non-Authoritative Route Object Clean-up", to the Routing > > Working Group mailing list. > > > > The goal of the proposal is to delete an non-authoritative object > > stored in the RIPE IRR, if it conflicts with an RPKI ROA. > > There are some corner cases where this could cause permanent and > unwarranted pain. > > 1. what's the procedure for backing out the deletion if the ROA holder > in the other RIR makes a mistake and, for example, forgets to create a > roa for a specific ASN and then they find their RIPE-NONAUTH route > object deleted by accident. When an operator makes a mistake, they've made a mistake. The same already applies today when the operator changes the ASN in the route/route6 object to the wrong origin ASN. The proposal does not have a 'back out' procedure; once a route/route6 object in RIPE-NONAUTH becomes in conflict with a RPKI ROA it should no longer exist. A different way of looking at things: What the policy proposal in a nutshell does is apply the RFC 6811 BGP origin validation process to IRR data. You could view the IRR data as if they are BGP announcements in context of 6811. Example: An IRR route object in RIPE-NONAUTH states that for prefix 206.48.168.0/22 a possible origin is AS4663 - but a set of PKI ROAs exists: 206.48.0.0/16 AS5511 maxlength 24 206.48.0.0/16 AS6505 maxlength 24 206.48.0.0/16 AS51964 maxlength 24 Obviously "206.48.168.0/22 AS4663" conflicts with the above set of ROAs and would be marked with origin validation state 'invalid'. This means that any network applying RPKI based BGP Origin Validation will reject the BGP announcement "206.48.168.0/22 AS4663", even though someone documented in the RIPE-NONAUTH IRR that that announcement perhaps could exist. The RIPE-NONAUTH IRR route object describes a state of the network that is to be discarded anyway - so deletion is warranted as it closes holes in prefix-list based filters in networks not doing OV. Also note that in the above scenario the owner of the ARIN-managed 206.48.0.0/16 prefix never was consulted or consented to the creation of the 206.48.168.0/22 route-object in the RIPE IRR. Leaving such objects laying around is a disservice to the global community - when there is clear and unambigious data that shows the IRR route object describes a route announcement that is to be rejected anyway. > 2. what happens when someone is busy creating ROAs in, for example, > Magastan and the RIPE NCC runs a deletion process mid-way through that > process When someone needs to create multiple ROAs, but only publishes one - it is an operator error. When one misconfigures things... they are misconfigured, no big deal. This is why for example the RIPE RPKI portal allows you to queue up RPKI ROA modifications and publish the batch in one go. By the way, What is "magastan" and what does it have to do with the topic at hand? To me "quality data" means that the routing information was created with the explicit consent of the owner of the resource - this is something the RPKI offers us. If the owner chooses to publish incorrect routing information (for example: wrong origin ASN) that is entirely up to them. > 3. the above situations are complicated by RFC6382. Why? Section 6 of RFC 6382 explicitly states: "Additionally, this technique sets the stage to employ RPKI-enabled machinery and more secure and explicit routing policies, which all network operators should be considering." What is your concern, how does RFC 6832 change anything? Perhaps you can provide us with a tangible example scenario? > It might be a good idea to send some warnings to the holders of the > route/route6 objects before nuking their objects + build in a timeout > period. "their objects"?! We can not assume that the owner of a resource ever asked for the objects in the first place. There are objects in the RIPE-NONAUTH IRR that cover NTT Communications' resources where we've never consented to their creation - since we are not the maintainer and perhaps dont even have any relation with the creator of such objects, we have no recourse to delete such objects. When we create RPKI ROAs covering such route objects it is a clear public statement about which ASNs are authorised to originate those prefixes. Any IRR information that is in conflict with such information should be considered rogue and a risk to our business. It'll take time before we see a great many networks deploy BGP Origin Validation based on RPKI data, so an incremental beneficial step forward is to apply the same origin validation procedure to unvalidated IRR data, this closes loopholes. To me keaving the rogue IRR objects in place and telling the industry to just deploy Origin Validation to mitigate the effects of RIPE-NONAUTH objects would be unreasonable. RIPE-NONAUTH is a pile of garbage, we need to offer folks an easy way to delete the portions of it affecting their resources (knownig that these resource owners probably never have been aware those route/route6 objects existed in the first place!). Kind regards, Job

2 1