- Test - lists.nanog.org

Outbound Route Filtering (ORF) vendor support
by Humberto Galiza 20 Aug '21

20 Aug '21

Hi, Is anyone aware of any vendor that supports Outbound Route Filtering (ORF) based on anything other than prefix-lists? I found these two old IETF drafts (both expired :-/) which supported the idea of filtering based on community and as-path respectively, but I wasn't able to understand if they were ever discussed at the WG and if there was any outcome of the discussion (I suspect the authors are no longer even working with the mentioned companies in the drafts): - https://datatracker.ietf.org/doc/html/draft-chen-bgp-ext-community-orf-02 - https://datatracker.ietf.org/doc/html/draft-ietf-idr-aspath-orf-13 Any info is very much appreciated. Thanks,

6 11

Weekly Routing Table Report
by cscora＠apnic.net 20 Aug '21

20 Aug '21

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 21 Aug, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 859868 Prefixes after maximum aggregation (per Origin AS): 325752 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 413785 Total ASes present in the Internet Routing Table: 71865 Prefixes per ASN: 11.97 Origin-only ASes present in the Internet Routing Table: 61780 Origin ASes announcing only one prefix: 25515 Transit ASes present in the Internet Routing Table: 10085 Transit-only ASes present in the Internet Routing Table: 338 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 37 Max AS path prepend of ASN (141827) 33 Prefixes from unregistered ASNs in the Routing Table: 1049 Number of instances of unregistered ASNs: 1055 Number of 32-bit ASNs allocated by the RIRs: 36959 Number of 32-bit ASNs visible in the Routing Table: 30762 Prefixes from 32-bit ASNs in the Routing Table: 142783 Number of bogon 32-bit ASNs visible in the Routing Table: 26 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 520 Number of addresses announced to Internet: 3038543744 Equivalent to 181 /8s, 28 /16s and 127 /24s Percentage of available address space announced: 82.1 Percentage of allocated address space announced: 82.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 285499 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 230866 Total APNIC prefixes after maximum aggregation: 66047 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 226383 Unique aggregates announced from the APNIC address blocks: 91138 APNIC Region origin ASes present in the Internet Routing Table: 11871 APNIC Prefixes per ASN: 19.07 APNIC Region origin ASes announcing only one prefix: 3372 APNIC Region transit ASes present in the Internet Routing Table: 1679 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 37 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7035 Number of APNIC addresses announced to Internet: 773573632 Equivalent to 46 /8s, 27 /16s and 204 /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-147769 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: 251610 Total ARIN prefixes after maximum aggregation: 115210 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 251096 Unique aggregates announced from the ARIN address blocks: 119829 ARIN Region origin ASes present in the Internet Routing Table: 18894 ARIN Prefixes per ASN: 13.29 ARIN Region origin ASes announcing only one prefix: 6884 ARIN Region transit ASes present in the Internet Routing Table: 1946 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 28 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4074 Number of ARIN addresses announced to Internet: 1268434432 Equivalent to 75 /8s, 154 /16s and 198 /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-401308 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, 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: 239014 Total RIPE prefixes after maximum aggregation: 111957 RIPE Deaggregation factor: 2.13 Prefixes being announced from the RIPE address blocks: 235603 Unique aggregates announced from the RIPE address blocks: 144381 RIPE Region origin ASes present in the Internet Routing Table: 28037 RIPE Prefixes per ASN: 8.40 RIPE Region origin ASes announcing only one prefix: 12060 RIPE Region transit ASes present in the Internet Routing Table: 3898 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10361 Number of RIPE addresses announced to Internet: 711071360 Equivalent to 42 /8s, 98 /16s and 22 /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-213403 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: 111414 Total LACNIC prefixes after maximum aggregation: 26598 LACNIC Deaggregation factor: 4.19 Prefixes being announced from the LACNIC address blocks: 112417 Unique aggregates announced from the LACNIC address blocks: 47233 LACNIC Region origin ASes present in the Internet Routing Table: 10785 LACNIC Prefixes per ASN: 10.42 LACNIC Region origin ASes announcing only one prefix: 2667 LACNIC Region transit ASes present in the Internet Routing Table: 2088 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8438 Number of LACNIC addresses announced to Internet: 176610048 Equivalent to 10 /8s, 134 /16s and 219 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 25914 Total AfriNIC prefixes after maximum aggregation: 5176 AfriNIC Deaggregation factor: 5.01 Prefixes being announced from the AfriNIC address blocks: 33849 Unique aggregates announced from the AfriNIC address blocks: 10740 AfriNIC Region origin ASes present in the Internet Routing Table: 1521 AfriNIC Prefixes per ASN: 22.25 AfriNIC Region origin ASes announcing only one prefix: 532 AfriNIC Region transit ASes present in the Internet Routing Table: 304 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 32 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 854 Number of AfriNIC addresses announced to Internet: 108511488 Equivalent to 6 /8s, 119 /16s and 193 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 9808 7736 9000 57 CMNET-GD Guangdong Mobile Communication 7545 5821 785 675 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4711 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3547 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3532 1023 56 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2801 1897 56 VNPT-AS-VN VNPT Corp, VN 4766 2489 11121 572 KIXS-AS-KR Korea Telecom, KR 9498 2373 503 248 BBIL-AP BHARTI Airtel Ltd., IN 45090 2129 1198 75 CNNIC-TENCENT-NET-AP Shenzhen Tencent C 4755 2115 437 192 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 16509 5485 9667 2419 AMAZON-02, US 11492 4712 311 759 CABLEONE, US 7155 3981 264 32 VIASAT-SP-BACKBONE, US 22773 3971 3029 277 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3598 1859 2492 AKAMAI-AS, US 6327 3362 1313 62 SHAW, CA 30036 2573 373 228 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2516 5029 454 CENTURYLINK-US-LEGACY-QWEST, US 5972 2287 485 814 DNIC-ASBLK-05800-06055, US 20115 2244 3048 506 CHARTER-20115, US 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 6780 1726 143 UNI2-AS, ES 20940 3766 3348 216 AKAMAI-ASN1, NL 39891 3267 187 22 ALJAWWALSTC-AS, SA 8551 2933 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2914 2283 896 ROSTELECOM-AS, RU 9009 2485 260 1330 M247, GB 34984 2217 357 594 TELLCOM-AS, TR 61317 1773 270 979 ASDETUK www.heficed.com, GB 58224 1627 889 563 TCI, IR 13188 1610 100 27 TRIOLAN, 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 8834 3459 585 Uninet S.A. de C.V., MX 10620 3399 522 671 Telmex Colombia S.A., CO 11830 2501 369 62 Instituto Costarricense de Electricidad 13999 1803 414 476 Mega Cable, S.A. de C.V., MX 6503 1509 359 477 Axtel, S.A.B. de C.V., MX 28573 1451 2307 233 CLARO S.A., BR 3816 1240 652 152 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 26615 1098 2351 134 TIM SA, BR 6147 1088 369 22 Telefonica del Peru S.A.A., PE 11664 979 193 435 Techtel LMDS Comunicaciones Interactiva 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 1640 393 22 LINKdotNET-AS, EG 24835 1464 503 31 RAYA-AS, EG 36992 1310 1489 267 ETISALAT-MISR, EG 36903 1183 537 110 MT-MPLS, MA 29571 758 68 11 ORANGE-COTE-IVOIRE, CI 6713 614 1863 34 IAM-AS, MA 36935 571 522 40 Vodafone-, EG 15399 500 49 28 WANANCHI-, KE 37342 469 32 1 MOVITEL, MZ 2018 337 319 74 TENET-1, ZA 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 8834 3459 585 Uninet S.A. de C.V., MX 9808 7736 9000 57 CMNET-GD Guangdong Mobile Communication 12479 6780 1726 143 UNI2-AS, ES 7545 5821 785 675 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 5485 9667 2419 AMAZON-02, US 11492 4712 311 759 CABLEONE, US 4538 4711 4192 74 ERX-CERNET-BKB China Education and Rese 7155 3981 264 32 VIASAT-SP-BACKBONE, US 22773 3971 3029 277 ASN-CXA-ALL-CCI-22773-RDC, US 20940 3766 3348 216 AKAMAI-ASN1, NL Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 7736 7679 CMNET-GD Guangdong Mobile Communication Co.Ltd. 12479 6780 6637 UNI2-AS, ES 7545 5821 5146 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4711 4637 ERX-CERNET-BKB China Education and Research Net 11492 4712 3953 CABLEONE, US 7155 3981 3949 VIASAT-SP-BACKBONE, US 22773 3971 3694 ASN-CXA-ALL-CCI-22773-RDC, US 20940 3766 3550 AKAMAI-ASN1, NL 7552 3547 3527 VIETEL-AS-AP Viettel Group, VN 7713 3532 3476 TELKOMNET-AS-AP PT Telekomunikasi Indonesia, ID Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 1782 UNALLOCATED 8.42.19.0/24 46887 LIGHTOWER, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 15132 UNALLOCATED 12.9.150.0/24 1239 SPRINTLINK, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.177.96.0/24 Origin: 397300 UNASSIGNED Transit: 33387 NOCIX, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 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:16 /9:13 /10:41 /11:101 /12:303 /13:589 /14:1193 /15:2006 /16:13420 /17:8214 /18:14001 /19:25441 /20:42501 /21:50770 /22:107164 /23:91675 /24:500974 /25:1446 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 5716 6780 UNI2-AS, ES 11492 3671 4712 CABLEONE, US 6327 3173 3362 SHAW, CA 8151 3147 8834 Uninet S.A. de C.V., MX 7155 3069 3981 VIASAT-SP-BACKBONE, US 22773 2973 3971 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2803 3267 ALJAWWALSTC-AS, SA 8551 2399 2933 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2225 2573 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 1934 2501 Instituto Costarricense de Electricidad y Telec Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1906 2:1107 3:142 4:20 5:3580 6:82 7:5 8:1530 9:1 11:164 12:1743 13:384 14:2286 15:100 16:21 17:342 18:108 20:124 21:1 22:188 23:4993 24:2441 25:2 27:2506 29:19 31:2347 32:116 34:1 35:47 36:1699 37:3791 38:2203 39:639 40:164 41:3795 42:971 43:2080 44:274 45:15380 46:3662 47:348 48:7 49:1622 50:1813 51:101 52:1278 54:251 55:641 56:4 57:53 58:1733 59:1202 60:935 61:2300 62:2311 63:1955 64:5374 65:2361 66:4994 67:2877 68:1167 69:4122 70:1366 71:677 72:3150 74:2616 75:1500 76:699 77:2046 78:1654 79:2262 80:1879 81:1544 82:1366 83:1144 84:1285 85:2737 86:718 87:1806 88:962 89:3010 90:517 91:7371 92:1800 93:2541 94:3107 95:3502 96:1297 97:350 98:979 99:961 100:77 101:1028 102:1590 103:26752 104:3891 105:432 106:812 107:2285 108:729 109:3859 110:2033 111:3149 112:1931 113:1425 114:1468 115:1895 116:1887 117:2352 118:2327 119:1899 120:1462 121:1060 122:2515 123:2163 124:1599 125:2066 128:1331 129:1371 130:863 131:2013 132:752 133:363 134:1823 135:299 136:780 137:847 138:2390 139:1186 140:748 141:1210 142:1204 143:1339 144:1263 145:322 146:1495 147:1412 148:2163 149:1498 150:817 151:1080 152:1630 153:424 154:2993 155:1329 156:1700 157:1225 158:970 159:2015 160:2348 161:1239 162:3389 163:1092 164:1546 165:1418 166:595 167:1785 168:3658 169:705 170:4350 171:804 172:2642 173:2949 174:1021 175:1091 176:3213 177:4387 178:2975 179:1879 180:2258 181:2615 182:3221 183:2011 184:2419 185:18717 186:4216 187:3161 188:3310 189:2889 190:8723 191:1369 192:10717 193:8290 194:6746 195:4847 196:2903 197:2108 198:6019 199:6000 200:7381 201:5215 202:10566 203:10063 204:4610 205:3383 206:3713 207:3340 208:4026 209:4707 210:4188 211:2343 212:3744 213:3461 214:1166 215:60 216:6344 217:2578 218:1207 219:682 220:1966 221:953 222:857 223:1996 End of report

1 0

BGP - Traffic Management
by Ryan Hamel 20 Aug '21

20 Aug '21

Hello, Does anyone know of any US carriers that will accept more specific routes other than what's required for the DFZ, like "le 31" or "upto /31" (junos speak) ? I know Zayo supports this internally but would like to know of other carriers for redundancy. I am currently dealing with a network that has per region assigned public IP blocks. I would like to see about moving to announcing aggregates to the carriers across the MPLS network and redistributing more specifics from iBGP to the carriers to get the traffic where it needs to be. In a failover situation these more specifics are also visible on an MPLS backbone where other transit routers will prepend the AS path upstream based on specific communities to prevent anycast routing. Thanks, Ryan

4 3

Zayo BGP filter update contact
by Adam Korab 19 Aug '21

19 Aug '21

Hi, It was requested on July 7 that Zayo build our inbound prefix filter from our as-set object in RADB. As of today, six weeks or so later, after beating them up for updates, all we get back from support is “we have engaged our engineering team on this” Anybody around willing and able to assist getting this done and verified? If so, please drop me a note off list. Thanks! --Adam

1 0

Meet our Scholarship Recipients (VIDEO) + Poll Results + Digital Blast from the Past
by Nanog News 19 Aug '21

19 Aug '21

Meet our 2021-22 Scholarship Recipients *We love supporting our builders of the Internet of tomorrow. * Meet Esu, Charly, Wendy, and Juan. Four incoming undergrad freshman engineering students from all over the United States, that NANOG was able to help support their career dreams. Learn more about how they will invest the funds toward their future. *MEET THE STUDENTS <https://www.nanog.org/stories/meet-our-2021-22-scholarship-recipients/>* Our Next Webinar: Your Voice HeardThe polls are in. We asked you what you wanted to learn about for our next NANOG webinar and this is what you voted for. *Follow us *on LinkedIn <https://www.linkedin.com/company/nanog/mycompany/?viewAsMember=true>to vote on more of NANOG's programming. *TAKE OUR NEXT POLL <https://www.linkedin.com/feed/update/urn:li:activity:6833509193845116929/>* *NANOG's Blast from the Digital Past* *One of the Internet's Earliest "Memes"* Dancing hamsters anyone? Throwback to the late nineties, *when this dated meme would have been the latest in digital entertainment *to roll out of your email.* In fact, you may have been pranked with these critters. *A trending office joke at the time was to set *Hamster Dance*as your colleague's browser homepage. *According to KnowYourMeme <https://knowyourmeme.com/memes/hampster-dance>, *Hampster Dance is "one of the earliest single-serving sites." Set to the annoyingly good, and instantly stuck-in-your-head, sped-up melodies of *Whistle Stop* by Roger Miller, the meme features rows of dancing hamster GIFs. *WATCH ORIGINAL HAMSTER DANCE <https://www.youtube.com/watch?v=Uq5XmNS1M-g>*

1 0

RE:"Tactical" /24 announcements
by Jakob Heitz (jheitz) 19 Aug '21

19 Aug '21

Ytti, We have introduced the scalable as-set into the XR route policy language. as-path-set does not scale well with 1000's of ASNs. Now, you don't need to expand AS-SET into prefix-set, just enter it directly. Example: as-set test 2914, 3356, end-set ! route-policy sample if as-path originates-from test then pass endif end-policy If this does not meet your needs and you need improvements, let me know. Kind Regards, Jakob. ------------------------------------------------------------- Date: Mon, 9 Aug 2021 19:10:23 +0300 From: Saku Ytti <saku(a)ytti.fi> We just recently learned of a IOS-XR prefix-set limit of 300001 when a particular customer AS-SET expanded to a higher number of prefixes. -- ++ytti

8 16

AS20940 Max Prefix and as-path filtering
by Jared Mauch 18 Aug '21

18 Aug '21

Hello, Akamai has been increasing the routes we are advertising in various locations as part of ongoing network changes. If you have a max-prefix set for Akamai can you please increase v4 to 1k and ensure you are accepting our additional ASNs that may live behind the clusters. We are going to be updating PeeringDB to reflect this change as well. An appropriate as-path access-list would look like: 20940_(21342|16625|33905|36183|24319|34164|35204|35994|43639|18680|39836|35993|23454|18717|31108|36183) Feel free to reach out if you have any questions. - Jared

1 0

RE: "Tactical" /24 announcements
by Jakob Heitz (jheitz) 17 Aug '21

17 Aug '21

> RPKI validity cover is incomplete. One way: add your own RTR records. They don't all have to come from the RPKI. Another way: Add route-policy to validate the origin-as. That requires a prefix-set. However, these prefix-sets are much smaller and the sum of them is smaller than the sum of prefix-sets you would use on your neighbor sessions. Regards, Jakob. -----Original Message----- Date: Tue, 17 Aug 2021 09:22:01 +0300 From: Saku Ytti <saku(a)ytti.fi> I share your confusion Randy. It seems like perhaps Jakob answered a slightly different question and his answer is roughly. a) Use this as-set feature to ensure valid set of ASNs from given peer b) Validate prefix using RPKI (I'm assuming with rejecting unknowns and invalids) c) Don't punch in prefix-lists anywhere Which in theory works, but in practice it does not, as RPKI validity cover is incomplete. Somewhat related, when JNPR implemented RTR the architecture was planned so that the RTR implementation itself isn't tightly coupled to RPKI validity. It was planned day1 that customers could have multiple RTR setups feeding prefixes and the NOS side could use these for other purposes too. So technically JNPR is mostly missing CLI work to allow you to feed prefix-lists dynamically over RTR, instead of punching them in vendor-specific way in config. I really hope JNPR does that work, I really like the appeal of doing things off-box and using the same protocol to talk to on-box. Also, give me gRPC/protobuf route policy API, so I can write my route-policy in a real programming language once for all my NOS. On Mon, 16 Aug 2021 at 20:32, Randy Bush <randy(a)psg.com> wrote: > > hi jakob, > > i am confused between > > > There is no expansion to prefix-set. > > and your earlier > > >> We have introduced the scalable as-set into the XR route policy language. > >> as-path-set does not scale well with 1000's of ASNs. > >> Now, you don't need to expand AS-SET into prefix-set, just enter it directly. > > expanding AS-SET into prefix filters is exactly what we do. > > ``` > % peval -s RIPE AS-RG-SEA > ({198.180.153.0/24, 198.180.151.0/24, 147.28.8.0/24, 147.28.9.0/24, 147.28.10.0/24, 147.28.11.0/24, 147.28.12.0/24, 147.28.13.0/24, 147.28.14.0/24, 147.28.15.0/24, 147.28.4.0/24, 147.28.5.0/24, 147.28.6.0/24, 147.28.7.0/24, 147.28.2.0/24, 147.28.3.0/24, 147.28.0.0/23, 45.132.188.0/24, 45.132.189.0/24, 45.132.190.0/24, 45.132.191.0/24}) > ``` > > i do not see how to get around this. clue bat please > > randy -- ++ytti

1 1

Re: "Tactical" /24 announcements
by Jason Pope 16 Aug '21

16 Aug '21

>On Thu, Aug 12, 2021 at 9:41 AM Hank Nussbacher <hank(a)interall.co.il> wrote: >> On 12/08/2021 17:59, William Herrin wrote: >> > If you prune the routes from the Routing Information Base instead, for >> > any widely accepted size (i.e. /24 or shorter netmask) you break the >> > Internet. >> >> How does this break the Internet? I would think it would just result in >> sub-optimal routing (provided there is a covering larger prefix) but >> everything should continue to work. Clue me in, please. > >A originates 10.0.0.0/16 to paid transit C >B originates 10.0.1.0/24 also to paid transit C >C offers both routes to D. D discards 10.0.1.0/24 from the RIB based >on same-next-hop >You peer with A and D. You receive only 10.0.0.0/16 since A doesn't >originate 10.0.1.0/24 and D has discarded it. >You send packets for 10.0.1.0/24 to A (the shortest path for >10.0.0.0/16), stealing A's paid transit to C to get to B. >Unless A filters C-bound packets purportedly from 10.0.1.0/24. B >doesn't currently transit for A so from B's perspective that's not an >allowed path. In which case, your path to 10.0.1.0/24 is black holed. > >D broke the Internet. If packets from you reach A at all, they do so >through an unpermitted path. > >Regards, >Bill Herrin Ok, I apologize, but I have some dumb questions (because I don't BGP anymore): 1) I assume in the scenario that A "owns" (ARIN assignment) 10.0.0.0/16 and if B has a /24 assignment out of the block that A "owns", shouldn't that mean that B has a business relationship with A and some kind of direct connectivity to A? 2) If "no", then why is B using a /24 out of A's block? If A sold or gave the block to B without a connectivity agreement, then A should break up their announcements appropriately to carve the /24 out of their announcement, right? 3) If "yes", then the connectivity wouldn't be broken, right? TIA for the tutoring and bearing with me. Regards, Jason K Pope

3 2

"Tactical" /24 announcements
by Billy Croan 15 Aug '21

15 Aug '21

How does the community feel about using /24 originations in BGP as a tactical advantage against potential bgp hijackers? All of our allocations are larger and those prefixes we announce for clients as well usually are. But we had a request recently to originate everything as distinct /24 prefixes, to reduce the effect of a potential bgp hijack. It seemed a little bit like a tragedy of the commons situation. Is this seen as route table pollution, or a necessary evil in today's world? How many routers out there today would be affected if everyone did this? Are there any big networks that drop or penalize announcements like this?

22 57