September 2020 - Test - lists.nanog.org

IP addresses on subnet edge (/24)
by Andrey Khomyakov 15 Sep '20

15 Sep '20

TL;DR I suspect there are middle boxes that don't like IPs ending in .255. Anyone seen that? Folks, We are troubleshooting a strange issue where some of our customers cannot establish a successful connection with our HTTP front end. In addition to checking the usual things like routing and interface errors and security policy configurations, hopening support tickets with the load balancer vendor so far all to no avail, we did packet captures. Based on the packet captures we receive a SYN, we reply with SYN-ACK, but the client never actually receives that SYN-ACK. In a different instance the 3-way completes, followed by TLS client hello to us, we reply with TLS Server Hello and that server hello never makes it to the client. And again, this is only affecting a small subset of customers thus suggesting it's not the load balancer or the edge routing configuration (in fact we can traceroute fine to the customer's IP). So far the only remaining theory that remains is that there are middle boxes out there that do not like IPs ending in .255. The service that the clients can't get to is hosted on two IPs ending in .255 Let's just say they are x.x.121.255 and x.x.125.255. We even stood up a basic "hello world" web server on x.x.124.255 with the same result. Standing up the very same basic webserver on x.x.124.250 allows the client to succeed. So far we have a friendly customer who has been working with us on troubleshooting the issue and we have some pcaps from the client's side somewhat confirming that it's not the customer's system either. This friendly customer is in a small 5 people office with Spectrum business internet (that's the SYN-ACK case). The same customer tried hopping on his LTE hotspot which came up as Cellco Partnership DBA Verizon Wireless with the same result (that's the TLS server hello case). That same customer with the same workstation drives a town over and he can get to the application fine (we are still waiting for the customer to let us know what that source IP is when it does work). Before you suggest that those .255 addresses are broadcasts on some VLAN, they are not. They are injected as /32s using a routing protocol, while the VLAN addressing is all RFC1918 addressing. --Andrey

9 8

curious spam...
by William Herrin 15 Sep '20

15 Sep '20

Howdy, I've noticed something odd. When I lived in Virginia, I started receiving email directly to my gmail box from my U.S. Representative. Unsolicited spam from Congressmen is nothing new but it was a little odd that they found my gmail box (which I don't give out) and not one of the hundreds of aliases at herrin.us or dirtside.com which I do give out. The gmail box exists only in mail headers; "From" is always a different address. I moved to Seattle. Today I found my grmail box subscribed to a congressman's list from a nearby Washington jurisdiction. Not some random congressman. And not any of the addresses I give out; my gmail box's address which I don't. Anyone else have a similar experience? Any idea how a hidden address is making it on to relevant congressmens' lists but not any others? That's weird right? Regards, Bill Herrin -- William Herrin bill(a)herrin.us https://bill.herrin.us/

7 7

how would draft-ymbk-opsawg-finding-geofeeds work in noam
by Randy Bush 14 Sep '20

14 Sep '20

would folk familiar with the north american RIR and IRR registries be kind enough to suggest how this might adapt? thanks. A new version of I-D, draft-ymbk-opsawg-finding-geofeeds-02.txt has been successfully submitted by Randy Bush and posted to the IETF repository. Name: draft-ymbk-opsawg-finding-geofeeds Revision: 02 Title: Finding and Using Geofeed Data Document date: 2020-09-11 Group: Individual Submission Pages: 16 URL: https://www.ietf.org/id/draft-ymbk-opsawg-finding-geofeeds-02.txt Status: https://datatracker.ietf.org/doc/draft-ymbk-opsawg-finding-geofeeds/ Htmlized: https://datatracker.ietf.org/doc/html/draft-ymbk-opsawg-finding-geofeeds Htmlized: https://tools.ietf.org/html/draft-ymbk-opsawg-finding-geofeeds-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-ymbk-opsawg-finding-geofeeds-02 Abstract: This document describes how to find and authenticate geofeed data.

3 16

why not use dns for draft-ymbk-opsawg-finding-geofeeds?
by Randy Bush 14 Sep '20

14 Sep '20

[ am i going to regret cross-posting? ] a friend raised in private the question of whether the dns could be used instead of rpsl. essentially, dns does not search down-tree for you. it only answers exact specific queries. for some reason lost in time, well at least lost in my mind, rpsl servers give you the nearest enclosing object. e.g., if i query for the ip address of psg.com, 147.28.0.62, i get the encompassing inetnum: object. ryuu.rg.net:/Users/randy> whois -h whois.ripe.net 147.28.0.62 inetnum: 147.28.0.0 - 147.28.31.255 netname: RGNET-RSCH-147-0 country: EE org: ORG-RO47-RIPE admin-c: RB45695-RIPE tech-c: RB45695-RIPE abuse-c: AR52766-RIPE status: LEGACY mnt-by: MAINT-RGNET remarks: Geofeed https://rg.net/geofeed created: 2020-09-03T22:23:37Z last-modified: 2020-09-13T20:16:05Z source: RIPE # Filtered and now i know not to query further in the range 147.28.0.0/19. note the geofeed pointer is not at the exact ip, or at the /24, or at the /16. and have fun getting the magic of knowing it is the /19 into the dns. one does not want to query the dns for an RR 62.0.28.147.in-addr.arpa because, for this to be useful, either o you need the geoloc data with every PTR record (think ipv6 and slaac) o you need some non-existent magic to get you the geoloc data for some unspecified less specific granularity if netflix wants to collect the geofeeds once a month. do we propose they dns query all ipv4 and ipv6 host addresses? i suspect there are also cultural issues. in most isps of scale, dns is close to customer service, a different 'silo' from provisioning. rpsl not so much. i am sure massimo is learning more about the silos in ntt than he would care to. but he was able to deploy this hack in a week. i would bet that he could never get a dns hack deployed. possibly amusing tangential note: we once tried to do rpki in the dns, see https://tools.ietf.org/html/draft-bates-bgp4-nlri-orig-verif-00 aside from other issues, dns only allows a single delegation, which would preclude two owners in a make before break transition. randy

1 0

sr - spring - what's the deal with 2 names
by aaron1＠gvtc.com 14 Sep '20

14 Sep '20

Please forgive if this has already been spoken to. if so, you can simply send the link to old mail list entries and that will suffice. otherwise. Does anyone know the scope on why we have 2 names for this ? Seriously, was it one of those things where a vendor started doing it first (pre-standard) as sr, and then ietf started standardizing it as spring ? .or was it always being standardized pre-vendor implementation and there was a disagreement within ietf or elsewhere ? or. was there a conscious decision amongst the inventors to actually call it both sr and spring ? or is their actually something different about each one and I'm wrong in thinking they are 2 names for the same technology. I'm taking stabs at this and presenting multiple choice just as I sit back and wonder why the 2 names I mean there must be a reason why someone thought that we should call this 2 different names. I would think within this NANOG maillist, someone will have the answer or at least some pretty good insights into why the 2 names. Aaron aaron1(a)gvtc.com

6 13

Softbank Contact
by Evan M. Gillman 13 Sep '20

13 Sep '20

Hello, Can someone from Sofbank sales contact me off list? Thanks, Evan Evan M. Gillman | transitbroker.com | P. 212.420.1222 | M. 917.664.0707

2 1

Wildfires: Reminder smart devices don't include emergency warnings while streaming
by Sean Donelan 12 Sep '20

12 Sep '20

As some of the largest wildfires burn along the West Coast, and over 500,000 people evacuate, a reminder that streaming devices do not include local emergency alerts. Cord-cutters using Alphabet Android TV, Amazon Fire TV, Apple TV "smart" devices should remember they don't have emergency alerts while streaming. FCC requires cellular phones support Wireless Emergency Alerts, including when using streaming Apps. But not in-home "smart" devices like smart TVs and smart speakers. You should also have an traditional AM/FM or weather radio at home. And your DTV may still have a connection for an over-the-air antenna. Nevertheless, while you are watching Netflix or listening to Spotify on a non-cell phone smart device, you won't get emergency alerts on those streaming devices. Amazon Fire TV, Apple TV and Alphabet Android TV executives don't see a need to support emergency alerts on their products.

8 9

Wildfires: Clear fuel from hilltop and remote area communications towers
by Eric Kuhnke 12 Sep '20

12 Sep '20

Over the past week I think I've seen about 20 to 30 photos of burnt out communications sites in Oregon and California. Due to the often remote and unstaffed nature of many of these sites, there's a natural tendency for brush, shrubs, grass and small trees to grow close to the tower compounds on many hilltop sites. Many of these sites also support emergency communications services. In the subject line I'm using "fuel" as defined by firefighters, not literally meaning petroleum fuels, but anything flammable. In some places there are ecological or political concerns with maintaining a cleared perimeter around telecom tower sites. This might be a time to re-visit the logical purpose of some of these policies, if allowing fuel to grow right up to the tower and telecom equipment shelters greatly increases the likelihood of the whole thing going up in flames.

3 2

Weekly Routing Table Report
by cscora＠apnic.net 11 Sep '20

11 Sep '20

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 12 Sep, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 821585 Prefixes after maximum aggregation (per Origin AS): 312847 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 392371 Total ASes present in the Internet Routing Table: 69335 Prefixes per ASN: 11.85 Origin-only ASes present in the Internet Routing Table: 59579 Origin ASes announcing only one prefix: 24748 Transit ASes present in the Internet Routing Table: 9756 Transit-only ASes present in the Internet Routing Table: 305 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 47 Max AS path prepend of ASN ( 37385) 44 Prefixes from unregistered ASNs in the Routing Table: 842 Number of instances of unregistered ASNs: 843 Number of 32-bit ASNs allocated by the RIRs: 33414 Number of 32-bit ASNs visible in the Routing Table: 27577 Prefixes from 32-bit ASNs in the Routing Table: 128046 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: 452 Number of addresses announced to Internet: 2851880192 Equivalent to 169 /8s, 252 /16s and 61 /24s Percentage of available address space announced: 77.0 Percentage of allocated address space announced: 77.0 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: 275573 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 216134 Total APNIC prefixes after maximum aggregation: 63434 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 209910 Unique aggregates announced from the APNIC address blocks: 86558 APNIC Region origin ASes present in the Internet Routing Table: 10854 APNIC Prefixes per ASN: 19.34 APNIC Region origin ASes announcing only one prefix: 3052 APNIC Region transit ASes present in the Internet Routing Table: 1595 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 28 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5946 Number of APNIC addresses announced to Internet: 770547072 Equivalent to 45 /8s, 237 /16s and 157 /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-141625 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: 240717 Total ARIN prefixes after maximum aggregation: 110220 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 238416 Unique aggregates announced from the ARIN address blocks: 112601 ARIN Region origin ASes present in the Internet Routing Table: 18561 ARIN Prefixes per ASN: 12.84 ARIN Region origin ASes announcing only one prefix: 6773 ARIN Region transit ASes present in the Internet Routing Table: 1903 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3397 Number of ARIN addresses announced to Internet: 1087692288 Equivalent to 64 /8s, 212 /16s and 222 /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, 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: 228762 Total RIPE prefixes after maximum aggregation: 107967 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 225074 Unique aggregates announced from the RIPE address blocks: 135576 RIPE Region origin ASes present in the Internet Routing Table: 27363 RIPE Prefixes per ASN: 8.23 RIPE Region origin ASes announcing only one prefix: 11824 RIPE Region transit ASes present in the Internet Routing Table: 3858 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9478 Number of RIPE addresses announced to Internet: 709144704 Equivalent to 42 /8s, 68 /16s and 176 /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: 111437 Total LACNIC prefixes after maximum aggregation: 25692 LACNIC Deaggregation factor: 4.34 Prefixes being announced from the LACNIC address blocks: 112580 Unique aggregates announced from the LACNIC address blocks: 47556 LACNIC Region origin ASes present in the Internet Routing Table: 10456 LACNIC Prefixes per ASN: 10.77 LACNIC Region origin ASes announcing only one prefix: 2602 LACNIC Region transit ASes present in the Internet Routing Table: 1956 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 28 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8042 Number of LACNIC addresses announced to Internet: 174493952 Equivalent to 10 /8s, 102 /16s and 145 /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: 23692 Total AfriNIC prefixes after maximum aggregation: 4869 AfriNIC Deaggregation factor: 4.87 Prefixes being announced from the AfriNIC address blocks: 35153 Unique aggregates announced from the AfriNIC address blocks: 9710 AfriNIC Region origin ASes present in the Internet Routing Table: 1413 AfriNIC Prefixes per ASN: 24.88 AfriNIC Region origin ASes announcing only one prefix: 497 AfriNIC Region transit ASes present in the Internet Routing Table: 286 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 47 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 714 Number of AfriNIC addresses announced to Internet: 109565184 Equivalent to 6 /8s, 135 /16s and 213 /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 7545 5671 766 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4501 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3530 1330 22 VIETEL-AS-AP Viettel Group, VN 45899 3220 1896 52 VNPT-AS-VN VNPT Corp, VN 7713 2713 828 622 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2518 9043 60 CMNET-GD Guangdong Mobile Communication 4766 2349 11103 555 KIXS-AS-KR Korea Telecom, KR 9498 2289 450 227 BBIL-AP BHARTI Airtel Ltd., IN 4755 2147 441 193 TATACOMM-AS TATA Communications formerl 9394 2039 4914 18 CTTNET China TieTong Telecommunications 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 4621 329 153 CABLEONE, US 16509 4247 8250 1949 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 22773 3631 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3352 1323 82 SHAW, CA 16625 3138 1660 2250 AKAMAI-AS, US 209 2489 5060 526 CENTURYLINK-US-LEGACY-QWEST, US 30036 2457 367 116 MEDIACOM-ENTERPRISE-BUSINESS, US 26484 2449 153 333 IKGUL-26484, US 5650 2310 2981 1625 FRONTIER-FRTR, 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 6053 1652 135 UNI2-AS, ES 20940 3203 2218 1028 AKAMAI-ASN1, EU 8551 3179 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 39891 3073 179 21 ALJAWWALSTC-AS, SA 12389 2749 2275 859 ROSTELECOM-AS, RU 34984 2200 355 572 TELLCOM-AS, TR 9009 2153 226 1172 M247, GB 13188 1609 100 35 TRIOLAN, UA 61317 1353 154 577 ASDETUK http://www.heficed.com, GB 58224 1279 834 519 TCI, IR 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 7945 3339 613 Uninet S.A. de C.V., MX 10620 3375 529 522 Telmex Colombia S.A., CO 11830 2565 369 63 Instituto Costarricense de Electricidad 6503 1632 323 414 Axtel, S.A.B. de C.V., MX 7303 1477 950 286 Telecom Argentina S.A., AR 13999 1423 469 381 Mega Cable, S.A. de C.V., MX 28573 1363 2247 225 CLARO S.A., BR 3816 1136 575 155 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1124 379 39 Telefonica del Peru S.A.A., PE 11664 958 209 410 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 1427 393 22 LINKdotNET-AS, EG 36992 1131 1539 75 ETISALAT-MISR, EG 24835 1105 462 27 RAYA-AS, EG 36903 917 480 93 MT-MPLS, MA 29571 681 68 12 ORANGE-COTE-IVOIRE, CI 6713 553 1863 34 IAM-AS, MA 15399 494 46 15 WANANCHI-, KE 37342 481 32 1 MOVITEL, MZ 36935 448 519 37 Vodafone-, EG 37148 403 43 95 globacom-as, NG 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 7945 3339 613 Uninet S.A. de C.V., MX 12479 6053 1652 135 UNI2-AS, ES 7545 5671 766 674 TPG-INTERNET-AP TPG Telecom Limited, AU 11492 4621 329 153 CABLEONE, US 4538 4501 4192 73 ERX-CERNET-BKB China Education and Rese 16509 4247 8250 1949 AMAZON-02, US 7155 4034 264 32 VIASAT-SP-BACKBONE, US 22773 3631 2984 173 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3530 1330 22 VIETEL-AS-AP Viettel Group, VN 10620 3375 529 522 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 6053 5918 UNI2-AS, ES 7545 5671 4997 TPG-INTERNET-AP TPG Telecom Limited, AU 11492 4621 4468 CABLEONE, US 4538 4501 4428 ERX-CERNET-BKB China Education and Research Net 7155 4034 4002 VIASAT-SP-BACKBONE, US 7552 3530 3508 VIETEL-AS-AP Viettel Group, VN 22773 3631 3458 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3352 3270 SHAW, CA 45899 3220 3168 VNPT-AS-VN VNPT Corp, VN 8551 3179 3134 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 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 22357 UNALLOCATED 8.7.108.0/24 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 36270 UNALLOCATED 8.24.66.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, 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.142.80.0/24 Origin: 10753 LVLT-10753, US Transit: 3356 LEVEL3, US 23.157.0.0/24 Origin: 395101 UNASSIGNED Transit: 33657 CMCS, US 23.164.80.0/24 Origin: 31998 KDSNET, US Transit: 209 CENTURYLINK-US-LEGACY-QWEST, 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 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:9 /9:11 /10:39 /11:100 /12:286 /13:576 /14:1175 /15:1937 /16:13486 /17:8295 /18:14036 /19:25605 /20:41040 /21:49501 /22:102262 /23:85380 /24:476574 /25:1273 /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 5039 6053 UNI2-AS, ES 11492 3666 4621 CABLEONE, US 6327 3149 3352 SHAW, CA 7155 3122 4034 VIASAT-SP-BACKBONE, US 22773 2810 3631 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2767 7945 Uninet S.A. de C.V., MX 8551 2638 3179 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 39891 2609 3073 ALJAWWALSTC-AS, SA 30036 2200 2457 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 1994 2310 FRONTIER-FRTR, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1628 2:1122 3:33 4:19 5:3601 6:54 8:1469 9:1 11:1 12:1770 13:346 14:2328 15:72 16:8 17:295 18:85 20:111 23:3994 24:2348 25:3 27:2324 31:2153 32:121 34:1 35:43 36:982 37:3445 38:1873 39:458 40:144 41:3690 42:635 43:2155 44:215 45:14926 46:3512 47:320 49:1510 50:1636 51:90 52:1114 54:226 55:651 56:6 57:52 58:1630 59:1155 60:790 61:2310 62:2151 63:2012 64:5275 65:2346 66:5082 67:2895 68:1170 69:4075 70:1401 71:677 72:2979 74:2573 75:1457 76:671 77:1951 78:1668 79:2403 80:2069 81:1601 82:1325 83:1264 84:1237 85:2681 86:557 87:1764 88:933 89:2814 90:379 91:7127 92:1561 93:2505 94:2788 95:3272 96:1256 97:340 98:920 99:980 100:88 101:1021 102:1085 103:24337 104:3560 105:395 106:900 107:2098 108:734 109:3722 110:1975 111:2051 112:1651 113:1387 114:1529 115:1841 116:1802 117:2091 118:2156 119:1719 120:845 121:1052 122:2533 123:2034 124:1647 125:2107 128:1414 129:1233 130:724 131:1915 132:754 133:306 134:1366 135:313 136:617 137:875 138:2269 139:1027 140:716 141:1095 142:970 143:1244 144:1168 145:366 146:1386 147:1039 148:2133 149:1190 150:768 151:1073 152:1563 153:427 154:4507 155:1223 156:3013 157:1127 158:869 159:1977 160:1970 161:1075 162:3159 163:914 164:1524 165:1321 166:587 167:1668 168:3522 169:592 170:4327 171:778 172:1989 173:2700 174:978 175:1045 176:2725 177:4809 178:2690 179:1814 180:2281 181:2556 182:3113 183:1178 184:2435 185:16947 186:3900 187:3027 188:3335 189:2670 190:8969 191:1419 192:10397 193:7674 194:6287 195:4529 196:3116 197:2051 198:6098 199:5923 200:7270 201:5246 202:10564 203:10205 204:4628 205:3108 206:3176 207:3261 208:4019 209:4526 210:4177 211:2032 212:3477 213:3262 214:1177 215:60 216:6109 217:2446 218:853 219:612 220:2059 221:910 222:986 223:1678 End of report

1 0

FCC: rulemaking on STIR/SHAKEN and Caller ID Authentication
by Sean Donelan 10 Sep '20

10 Sep '20

At this month's FCC rulemaking meeting, it will consider https://www.fcc.gov/document/fcc-announces-tentative-agenda-september-open-… Promoting Caller ID Authentication to Combat Spoofed Robocalls – The Commission will consider a Report and Order that would continue its work to implement the TRACED Act and promote the deployment of caller ID authentication technology to combat spoofed robocalls. (WC Docket No. 17-97)

6 6