- NANOG - lists.nanog.org

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

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

13 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 14 Aug, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 859233 Prefixes after maximum aggregation (per Origin AS): 325419 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 412951 Total ASes present in the Internet Routing Table: 71756 Prefixes per ASN: 11.97 Origin-only ASes present in the Internet Routing Table: 61685 Origin ASes announcing only one prefix: 25422 Transit ASes present in the Internet Routing Table: 10071 Transit-only ASes present in the Internet Routing Table: 328 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: 1073 Number of instances of unregistered ASNs: 1079 Number of 32-bit ASNs allocated by the RIRs: 36882 Number of 32-bit ASNs visible in the Routing Table: 30663 Prefixes from 32-bit ASNs in the Routing Table: 142443 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: 533 Number of addresses announced to Internet: 3039950336 Equivalent to 181 /8s, 49 /16s and 246 /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: 285549 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 230688 Total APNIC prefixes after maximum aggregation: 66041 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 226129 Unique aggregates announced from the APNIC address blocks: 91042 APNIC Region origin ASes present in the Internet Routing Table: 11835 APNIC Prefixes per ASN: 19.11 APNIC Region origin ASes announcing only one prefix: 3356 APNIC Region transit ASes present in the Internet Routing Table: 1676 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: 6999 Number of APNIC addresses announced to Internet: 773842432 Equivalent to 46 /8s, 31 /16s and 230 /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: 251416 Total ARIN prefixes after maximum aggregation: 115126 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 251019 Unique aggregates announced from the ARIN address blocks: 119512 ARIN Region origin ASes present in the Internet Routing Table: 18871 ARIN Prefixes per ASN: 13.30 ARIN Region origin ASes announcing only one prefix: 6860 ARIN Region transit ASes present in the Internet Routing Table: 1945 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: 4054 Number of ARIN addresses announced to Internet: 1269971840 Equivalent to 75 /8s, 178 /16s and 59 /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: 238809 Total RIPE prefixes after maximum aggregation: 111777 RIPE Deaggregation factor: 2.14 Prefixes being announced from the RIPE address blocks: 235343 Unique aggregates announced from the RIPE address blocks: 144080 RIPE Region origin ASes present in the Internet Routing Table: 28017 RIPE Prefixes per ASN: 8.40 RIPE Region origin ASes announcing only one prefix: 12033 RIPE Region transit ASes present in the Internet Routing Table: 3907 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: 10338 Number of RIPE addresses announced to Internet: 711115392 Equivalent to 42 /8s, 98 /16s and 194 /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: 111249 Total LACNIC prefixes after maximum aggregation: 26556 LACNIC Deaggregation factor: 4.19 Prefixes being announced from the LACNIC address blocks: 112292 Unique aggregates announced from the LACNIC address blocks: 47161 LACNIC Region origin ASes present in the Internet Routing Table: 10772 LACNIC Prefixes per ASN: 10.42 LACNIC Region origin ASes announcing only one prefix: 2648 LACNIC Region transit ASes present in the Internet Routing Table: 2079 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8427 Number of LACNIC addresses announced to Internet: 176148480 Equivalent to 10 /8s, 127 /16s and 208 /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: 25997 Total AfriNIC prefixes after maximum aggregation: 5162 AfriNIC Deaggregation factor: 5.04 Prefixes being announced from the AfriNIC address blocks: 33917 Unique aggregates announced from the AfriNIC address blocks: 10685 AfriNIC Region origin ASes present in the Internet Routing Table: 1513 AfriNIC Prefixes per ASN: 22.42 AfriNIC Region origin ASes announcing only one prefix: 525 AfriNIC Region transit ASes present in the Internet Routing Table: 298 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: 845 Number of AfriNIC addresses announced to Internet: 108525312 Equivalent to 6 /8s, 119 /16s and 247 /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 7655 9000 57 CMNET-GD Guangdong Mobile Communication 7545 5821 785 675 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4708 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3604 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3531 1023 56 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2801 1897 55 VNPT-AS-VN VNPT Corp, VN 4766 2487 11121 572 KIXS-AS-KR Korea Telecom, KR 9498 2374 503 249 BBIL-AP BHARTI Airtel Ltd., IN 45090 2129 1198 75 CNNIC-TENCENT-NET-AP Shenzhen Tencent C 4755 2120 437 193 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 5388 9657 2422 AMAZON-02, US 11492 4766 314 740 CABLEONE, US 7155 3981 264 32 VIASAT-SP-BACKBONE, US 22773 3978 3030 277 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3589 1852 2488 AKAMAI-AS, US 6327 3362 1313 62 SHAW, CA 30036 2574 375 226 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2517 5029 455 CENTURYLINK-US-LEGACY-QWEST, US 5972 2265 483 823 DNIC-ASBLK-05800-06055, US 20115 2245 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 6785 1726 145 UNI2-AS, ES 20940 3743 3348 216 AKAMAI-ASN1, NL 39891 3267 187 22 ALJAWWALSTC-AS, SA 8551 2942 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2913 2283 896 ROSTELECOM-AS, RU 9009 2467 256 1322 M247, GB 34984 2218 357 594 TELLCOM-AS, TR 61317 1750 269 965 ASDETUK www.heficed.com, GB 58224 1623 889 561 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 8665 3456 586 Uninet S.A. de C.V., MX 10620 3399 522 671 Telmex Colombia S.A., CO 11830 2507 369 62 Instituto Costarricense de Electricidad 13999 1795 414 474 Mega Cable, S.A. de C.V., MX 6503 1500 359 477 Axtel, S.A.B. de C.V., MX 28573 1448 2306 230 CLARO S.A., BR 3816 1240 652 152 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 26615 1099 2351 134 TIM SA, BR 6147 1090 369 22 Telefonica del Peru S.A.A., PE 11664 983 194 437 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 1649 393 22 LINKdotNET-AS, EG 24835 1425 499 30 RAYA-AS, EG 36992 1309 1489 266 ETISALAT-MISR, EG 36903 1183 537 110 MT-MPLS, MA 29571 739 68 11 ORANGE-COTE-IVOIRE, CI 6713 612 1863 34 IAM-AS, MA 36935 571 522 40 Vodafone-, EG 15399 500 49 28 WANANCHI-, KE 37342 463 32 1 MOVITEL, MZ 2018 329 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 8665 3456 586 Uninet S.A. de C.V., MX 9808 7655 9000 57 CMNET-GD Guangdong Mobile Communication 12479 6785 1726 145 UNI2-AS, ES 7545 5821 785 675 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 5388 9657 2422 AMAZON-02, US 11492 4766 314 740 CABLEONE, US 4538 4708 4192 74 ERX-CERNET-BKB China Education and Rese 7155 3981 264 32 VIASAT-SP-BACKBONE, US 22773 3978 3030 277 ASN-CXA-ALL-CCI-22773-RDC, US 20940 3743 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 7655 7598 CMNET-GD Guangdong Mobile Communication Co.Ltd. 12479 6785 6640 UNI2-AS, ES 7545 5821 5146 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4708 4634 ERX-CERNET-BKB China Education and Research Net 11492 4766 4026 CABLEONE, US 7155 3981 3949 VIASAT-SP-BACKBONE, US 22773 3978 3701 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3604 3584 VIETEL-AS-AP Viettel Group, VN 20940 3743 3527 AKAMAI-ASN1, NL 7713 3531 3475 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:102 /12:305 /13:589 /14:1193 /15:2006 /16:13443 /17:8274 /18:13999 /19:25455 /20:42472 /21:50611 /22:107035 /23:91675 /24:500556 /25:1448 /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 5723 6785 UNI2-AS, ES 11492 3723 4766 CABLEONE, US 6327 3173 3362 SHAW, CA 8151 3168 8665 Uninet S.A. de C.V., MX 7155 3069 3981 VIASAT-SP-BACKBONE, US 22773 2972 3978 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2803 3267 ALJAWWALSTC-AS, SA 8551 2408 2942 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2225 2574 MEDIACOM-ENTERPRISE-BUSINESS, US 11830 1934 2507 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:1908 2:1111 3:141 4:20 5:3595 6:82 7:5 8:1542 9:1 11:164 12:1741 13:372 14:2283 15:99 16:20 17:334 18:105 20:124 21:1 22:188 23:4965 24:2422 25:2 27:2509 29:19 31:2321 32:116 34:1 35:47 36:1600 37:3807 38:2190 39:619 40:186 41:3776 42:969 43:2071 44:271 45:15382 46:3662 47:348 48:7 49:1618 50:1806 51:101 52:1247 54:251 55:624 56:4 57:53 58:1756 59:1202 60:933 61:2339 62:2309 63:1966 64:5372 65:2363 66:5016 67:2873 68:1168 69:4096 70:1366 71:677 72:3143 74:2611 75:1492 76:697 77:2021 78:1662 79:2275 80:1876 81:1547 82:1366 83:1138 84:1287 85:2739 86:711 87:1817 88:969 89:2987 90:511 91:7386 92:1814 93:2534 94:3110 95:3509 96:1290 97:344 98:979 99:963 100:77 101:1029 102:1587 103:26678 104:3940 105:431 106:808 107:2322 108:728 109:3876 110:2032 111:3149 112:1927 113:1424 114:1470 115:1894 116:1885 117:2353 118:2329 119:1907 120:1461 121:1058 122:2518 123:2155 124:1597 125:2069 128:1318 129:1314 130:894 131:2007 132:753 133:364 134:1657 135:301 136:793 137:944 138:2396 139:1204 140:792 141:1204 142:1224 143:1342 144:1258 145:323 146:1501 147:1370 148:2144 149:1491 150:820 151:1069 152:1632 153:423 154:3000 155:1340 156:1701 157:1223 158:967 159:2014 160:2323 161:1215 162:3386 163:1020 164:1546 165:1405 166:608 167:1782 168:3662 169:702 170:4368 171:801 172:2613 173:2961 174:1021 175:1086 176:3211 177:4394 178:2958 179:1864 180:2251 181:2618 182:3216 183:2010 184:2421 185:18686 186:4236 187:3172 188:3330 189:2917 190:8721 191:1363 192:10737 193:8300 194:6725 195:4820 196:2900 197:2139 198:6042 199:5992 200:7380 201:5219 202:10556 203:10061 204:4605 205:3371 206:3716 207:3340 208:4035 209:4704 210:4189 211:2340 212:3726 213:3462 214:1186 215:55 216:6339 217:2578 218:1208 219:681 220:1971 221:953 222:861 223:1967 End of report

1 0

Does anybody here have a problem
by C. A. Fillekes 12 Aug '21

12 Aug '21

telling the difference between their NANOG and SCA mail? since I stopped getting both in digest form, maybe it's easier to mix the two up by mistake.

6 5

Opt-in national WEA test in the United States on Aug 11 at 2:20pm EDT
by Sean Donelan 11 Aug '21

11 Aug '21

Tommorrow, Wednesday, August 11, 2021 at 2:20 p.m. EDT the Federal Emergency Management Agency (FEMA) will be testing the national emergency alert system and wireless emergency alert system. Most of the news reporting has tried to simplify things. The Wireless Emergency Alert (WEA) test on mobile devices is "opt-in." By default, consumer devices are NOT enabled for WEA tests. A consumer must manually enable test messages. Other emergency alerts are enabled by default. Instructions to enable/disable WEA test messages on iPhone and Android https://www.fcc.gov/sites/default/files/weatest_opt-in_instructions.pdf Additionally, only mobile devices with 1. WEA version 2.0 or later (roughly iPhone 6 and later) 2. Use a participating wireless service provider, the six major cellular carriers covering 97% of subscribers participate in WEA 3. In range, and receiving a radio signal from a participating carrier cell tower (not in a cave, basement, outback -- no signal) 4. Powered on, and not in airplane mode You can provide feedback, if you opted-in, about how well the test worked. FEMA-National-Test [@] fema.dhs.gov https://www.fema.gov/fact-sheet/frequently-asked-questions-2021-ipaws-natio…

1 1

A crazy idea
by Stephen Satchell 10 Aug '21

10 Aug '21

First, I know this isn't the right place to propose this; need a pointer to where to propose an outlandish idea. PROBLEM: IPv6 support is still in its birthing pangs. I see a problem that limits deployment of IPv6 fully: reverse PTR records in the ".in6.arpa." zones. (Now that I think about it, this may very well be a network operator issue. Who maintains the ".in.arpa." zones delegated by IANA now?) I've been going 'round and 'round with AT&T about "static" IPv6 addresses. In particular, I can't get a PTR record in the ip6.arpa. zone to save my life. Now, the problem is not really ripe yet, because the big reason for PTR records is for mail servers -- best practice calls for AAAA/PTR agreement, just like for IPv4 the best practice is for A/PTR agreement. The existing DNS providers can support delegation domains, so that I don't have to have DNS servers of my own if I don't want to. It could be that one would need to "buy" the delegation domain, but that's a front-office consideration. Personally, I use register.com for my domain DNS zones. I believe strongly that other registrars that offer customer zone editing, plus DNS service providers, can support reverse delegation zones with a minimum of hassle, and without charging an arm and a leg for the service. From the customers' viewpoint, a GUI would make the maintenance relatively painless. (Keying the information below took a long time. Any rational DNS admin and DNS service provider would have automation in place to take out the painful work.) What would the domain names look like? Let's take my current IP/IPv6 assignments from AT&T: 2600:1700:79b0:ddc0::/64 99.65.194.96/29 The IPv6 delegation would be easy: > 0.c.d.d.0.b.9.7.0.0.7.1.0.0.6.2.ip6.arpa. NS my-DNS-server-1. > 0.c.d.d.0.b.9.7.0.0.7.1.0.0.6.2.ip6.arpa. NS my-DNS-server-2. because the delegation would always be on a /64 boundary. The customer assignments would be straightforward. In my BIND9 zone file, it would look something like this: > $ORIGIN 0.c.d.d.0.b.9.7.0.0.7.1.0.0.6.2.ip6.arpa. > @ IN SOA ... > @ NS my-DNS-server-1. > @ NS my-DNS-server-2. > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR server1.example.com. > 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR server2.example.com. Delegations for the IP range, not being on an octet boundary, would be a little more problematic: > 96-103.194.65.99.in-addr.arpa. NS my-DNS-server-1 > 96-103.194.65.99.in-addr.arpa. NS my-DNS-server-2> $GENERATE 96-102 $ IN CNAME $.96-103.194.65.99.in-addr.arpa. In my BIND9 zone file, it would look something like this: > $ORIGIN 96-103.194.65.99.in-addr.arpa. > @ SOA ... > @ NS my-dns-server-1. > @ NS my-dns-server-2. > 96 IN PTR server1.example.com. > 97 IN PTR server2.example.com. The advantage to this system to the number providers is they would have one administrative record per customer, instead of having to deal with each PTR record individually. The advantage to customers is they don't have to beg and snivel to get PTR records, just beg and snivel once to get the delegation. The advantage to DNS server providers is they have something else to sell. Want to encourage IPv6 adoption? This would help.

17 25

Where to get IPv4 block these day
by james jones 09 Aug '21

09 Aug '21

hey everyone, Been a while since I had to deal with NetOps stuff. Was wondering, where do you go these days to get IPv4 blocks? It seems like getting assignments is hard due to exhaustion. I have found some "Auction" sites but it all feels very scammy. Any info would be appreciated. -James

19 28

Cogent x RPKI
by Rubens Kuhl 09 Aug '21

09 Aug '21

>From a Cogent support ticket: "Hello, Please see the attached LOA. Regarding the RPKI ROA, for now, we don't create ROA for our prefixes nor for prefixes that we assign to our customers and we don't plan to do it. Unfortunately, this is not an option." Someone that poses as a Tier-1 and doesn't even plan to sign their announcements ? How much more depeering will make them reconsider ? Rubens

3 3

Fort 1.5.1 Released..
by Mark Tinka 08 Aug '21

08 Aug '21

Hi all. Fort 1.5.1 has just been released: https://github.com/NICMx/FORT-validator/releases/tag/v1.5.1 Along with a number of improvements, the key ones that I've been testing for some time are: * Improved scaling for environments that have 500 routers or more. This necessitated a major rewrite of the RTR code, and how Fort utilizes its thread pools. The defaults have gone up from 40 routes to 100 routers. * I/O errors that affected FreeBSD. Mark.

2 1