November 2020 - Test - lists.nanog.org

Neteng field laptop/tablet
by Brandon Martin 21 Nov '20

21 Nov '20

Sorry if this is perhaps a bit OT... Can anyone recommend a smallish (10-13" display), relatively lightweight tablet or laptop (or convertible) with a native PCIe multi-gig Ethernet port, ideally both 10GBASE-T + 2.5GBASE-T (and 5GBASE-T perhaps). I'm not seeing a lot out there, and it's hard to search for multi-gig in a laptop at this point. Failing that, I'm sure someone has a recommendation for a similar device with native PCIe 1000BASE-T + a thunderbolt or similar port I can hang a dongle off of? Ruggedness is useful but not essential. 6-8 hour practical battery life is important but almost implied these days. Must be able to nicely run Linux (distro is unimportant). -- Brandon Martin

2 1

inspecting RPKI data: console.rpki-client.org
by Job Snijders 20 Nov '20

20 Nov '20

Dear all, I'd like to introduce another tool to inspect RPKI data... the rpki-client console! Comes with an authentic 90s look & feel :-) The Frontpage - http://console.rpki-client.org/ ----------------------------------------------- On the front page you can see stdout + stderr of the most recent rpki-client run. The log shows which publication points were contacted and prints any issues encountered with specific RPKI files. Those of us publishing RPKI data should keep an eye out not to show up in this type of log with warnings or errors. For example: rpki-client: cc.rg.net/rpki/RGnet-cc/1opByAd8x8R2F-SzstgaYzVXK8Q.mft: mft expired on Oct 12 17:58:45 2020 GMT However, the above line might be the result of some kind of experiment someone is conducting :-) The RPKI distributed database currently is more than 120,000 (!) certificate/roa/manifest files, and only a handful of files have some kind of completeness or expiration date issue. Good job everyone! :-) The ASN specific pages - http://console.rpki-client.org/AS2914.html ------------------------------------------------------------------- You can substitute the 'AS2914' portion in the URL for any ASN to see which .roa files reference the given ASN. Another example, here one can see all ROAs which authorize AS 8283 as origin: https://console.rpki-client.org/AS8283.html If you encounter a HTTP 404 error, no ROAs reference the ASN. On the 'per ASN page' you can search click the .roa files on the left side to inspect the ROA. Each object in the RPKI has a unique Subject Key Identifier (SKI). An example of a SKI is this hexadecimal identifier '06:96:B3:F7:CC:AD:55:45:A5:3A:64:32:31:2B:7F:E1:2B:7A:15:22' which maps to a filename like 'rpki.apnic.net/member_repository/A91A4C60/B526FF74D84111E9A4521413C4F9AE02/…' Yeah... compared to DNS names mapping to IPv6 addresses, in the RPKI neither the path name nor the SKI are easy to remember :-) The console can show that .roa file in human readable format, just append .html: http://console.rpki-client.org/rpki.apnic.net/member_repository/A91A4C60/B5… Every object in the RPKI is subordinate to another object (all objects are signed by a parent certificate, except the Trust Anchors). The parent is identified by the Authority Key Identifier (AKI). So one object's AKI is another object's SKI! If you click the AKI, the console brings you to the parent object, from where you can continue to explore other objects related to parent. Certificates point to Manifests, and .mft files contain the 'directory indexes' of the RPKI: http://console.rpki-client.org/rpki.apnic.net/member_repository/A91A4C60/B5… >From the manifest overview you can jump to the parent, click the referenced .roa, .cer or .crl files. All directories on the webserver are 'open', except the root. This allows you to explore this RPKI cache by browsing through the filesystem directly, example: http://console.rpki-client.org/rpki.apnic.net/member_repository/ Final notes ----------- The rpki-client console provides a view on *validated* RPKI data. First rpki-client runs and prunes bad files, then all HTML is generated. The console provides a view on the data as used in production Internet routers. Please note: the console's rendering is delayed by a bit over an hour compared to the real thing. Another entry point, you can use your browser's 'find on page' function to search for anything in all of it on this humongous page: http://console.rpki-client.org/roas.html The RPKI is very intricate collection of references, I hope this console offers another useful perspective on the tree-like structures. Enjoy! Kind regards, Job

3 3

Ingress filtering on transits, peers, and IX ports
by Brian Knight 20 Nov '20

20 Nov '20

We recently received an email notice from a group of security researchers who are looking at the feasibility of attacks using spoofed traffic. Their methodology, in broad strokes, was to send traffic to our DNS servers with a source IP that looked like it came from our network. Their attacks were successful, and they included a summary of what they found. So this message has started an internal conversation on what traffic we should be filtering and how. This security test was not about BCP 38 for ingress traffic from our customers, nor was it about BGP ingress filtering. This tested our ingress filtering from the rest of the Internet. It seems to me like we should be filtering traffic with spoofed IPs on our transit, IX, and peering links. I have done this filtering in the enterprise world extensively, and it's very helpful to keep out bad traffic. BCP 84 also discusses ingress filtering for SP's briefly and seems to advocate for it. We have about 15 IP blocks allocated to us. With a network as small as ours, I chose to go with a static ACL approach to start the conversation. I crafted a static ACL, blocking all ingress traffic sourced from any of our assigned IP ranges. I made sure to include: * Permit entries for P-t-P WAN subnets on peering links * Permit entries for IP assignments to customers running multi-homed BGP * The "permit ipv4 any any" at the end :) The questions I wanted to ask the SP community are: * What traffic filtering do you do on your transits, on IX ports, and your direct peering links? * How is it accomplished? Through static ACL or some flavor of uRPF? * If you use static ACLs, what is the administrative overhead like? What makes it easy or difficult to update? * How did you test your filters when they were implemented? Thanks a lot, -Brian

23 48

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

20 Nov '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 21 Nov, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 835774 Prefixes after maximum aggregation (per Origin AS): 319021 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 398314 Total ASes present in the Internet Routing Table: 69979 Prefixes per ASN: 11.94 Origin-only ASes present in the Internet Routing Table: 60139 Origin ASes announcing only one prefix: 24893 Transit ASes present in the Internet Routing Table: 9840 Transit-only ASes present in the Internet Routing Table: 299 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 35 Max AS path prepend of ASN ( 45582) 27 Prefixes from unregistered ASNs in the Routing Table: 935 Number of instances of unregistered ASNs: 936 Number of 32-bit ASNs allocated by the RIRs: 34200 Number of 32-bit ASNs visible in the Routing Table: 28331 Prefixes from 32-bit ASNs in the Routing Table: 129951 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: 462 Number of addresses announced to Internet: 2865990144 Equivalent to 170 /8s, 211 /16s and 138 /24s Percentage of available address space announced: 77.4 Percentage of allocated address space announced: 77.4 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: 284118 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 217658 Total APNIC prefixes after maximum aggregation: 63654 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 213242 Unique aggregates announced from the APNIC address blocks: 87121 APNIC Region origin ASes present in the Internet Routing Table: 11033 APNIC Prefixes per ASN: 19.33 APNIC Region origin ASes announcing only one prefix: 3128 APNIC Region transit ASes present in the Internet Routing Table: 1609 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6156 Number of APNIC addresses announced to Internet: 779023744 Equivalent to 46 /8s, 110 /16s and 245 /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-143673 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: 242531 Total ARIN prefixes after maximum aggregation: 111606 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 240572 Unique aggregates announced from the ARIN address blocks: 115191 ARIN Region origin ASes present in the Internet Routing Table: 18691 ARIN Prefixes per ASN: 12.87 ARIN Region origin ASes announcing only one prefix: 6810 ARIN Region transit ASes present in the Internet Routing Table: 1920 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3557 Number of ARIN addresses announced to Internet: 1093792000 Equivalent to 65 /8s, 49 /16s and 241 /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: 238274 Total RIPE prefixes after maximum aggregation: 112098 RIPE Deaggregation factor: 2.13 Prefixes being announced from the RIPE address blocks: 234322 Unique aggregates announced from the RIPE address blocks: 137329 RIPE Region origin ASes present in the Internet Routing Table: 27535 RIPE Prefixes per ASN: 8.51 RIPE Region origin ASes announcing only one prefix: 11861 RIPE Region transit ASes present in the Internet Routing Table: 3893 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9689 Number of RIPE addresses announced to Internet: 709712512 Equivalent to 42 /8s, 77 /16s and 90 /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: 111924 Total LACNIC prefixes after maximum aggregation: 26173 LACNIC Deaggregation factor: 4.28 Prefixes being announced from the LACNIC address blocks: 113028 Unique aggregates announced from the LACNIC address blocks: 47967 LACNIC Region origin ASes present in the Internet Routing Table: 10604 LACNIC Prefixes per ASN: 10.66 LACNIC Region origin ASes announcing only one prefix: 2606 LACNIC Region transit ASes present in the Internet Routing Table: 1959 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 33 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8196 Number of LACNIC addresses announced to Internet: 174339584 Equivalent to 10 /8s, 100 /16s and 54 /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: 24450 Total AfriNIC prefixes after maximum aggregation: 4752 AfriNIC Deaggregation factor: 5.15 Prefixes being announced from the AfriNIC address blocks: 34148 Unique aggregates announced from the AfriNIC address blocks: 10300 AfriNIC Region origin ASes present in the Internet Routing Table: 1412 AfriNIC Prefixes per ASN: 24.18 AfriNIC Region origin ASes announcing only one prefix: 487 AfriNIC Region transit ASes present in the Internet Routing Table: 289 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 733 Number of AfriNIC addresses announced to Internet: 108683776 Equivalent to 6 /8s, 122 /16s and 98 /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 5748 778 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4748 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3584 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3261 1896 55 VNPT-AS-VN VNPT Corp, VN 7713 3032 913 538 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2502 9044 57 CMNET-GD Guangdong Mobile Communication 4766 2353 11103 553 KIXS-AS-KR Korea Telecom, KR 9498 2293 466 232 BBIL-AP BHARTI Airtel Ltd., IN 4755 2134 441 189 TATACOMM-AS TATA Communications formerl 45090 2055 1045 63 CNNIC-TENCENT-NET-AP Shenzhen Tencent C 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 4717 313 750 CABLEONE, US 16509 4459 9050 2061 AMAZON-02, US 7155 4035 264 32 VIASAT-SP-BACKBONE, US 22773 3734 2995 198 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3347 1323 82 SHAW, CA 16625 3169 1654 2253 AKAMAI-AS, US 209 2495 5061 511 CENTURYLINK-US-LEGACY-QWEST, US 30036 2482 368 98 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2314 2982 1626 FRONTIER-FRTR, US 20115 2164 2895 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 47331 6820 937 3630 TTNET, TR 12479 6207 1667 142 UNI2-AS, ES 39891 3459 195 22 ALJAWWALSTC-AS, SA 8551 3321 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3298 3347 202 AKAMAI-ASN1, EU 12389 2853 2280 885 ROSTELECOM-AS, RU 9009 2188 226 1192 M247, GB 34984 2172 354 576 TELLCOM-AS, TR 13188 1611 100 26 TRIOLAN, UA 58224 1384 852 540 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 8127 3441 596 Uninet S.A. de C.V., MX 10620 3391 528 569 Telmex Colombia S.A., CO 11830 2563 369 63 Instituto Costarricense de Electricidad 13999 1489 426 402 Mega Cable, S.A. de C.V., MX 6503 1470 312 474 Axtel, S.A.B. de C.V., MX 7303 1469 943 268 Telecom Argentina S.A., AR 28573 1355 2257 224 CLARO S.A., BR 3816 1162 576 166 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1148 379 39 Telefonica del Peru S.A.A., PE 11664 1005 213 418 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 1546 393 22 LINKdotNET-AS, EG 24835 1285 470 26 RAYA-AS, EG 36992 1218 1529 131 ETISALAT-MISR, EG 36903 918 480 94 MT-MPLS, MA 29571 711 68 12 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 15399 488 46 16 WANANCHI-, KE 37342 476 32 1 MOVITEL, MZ 36935 456 522 40 Vodafone-, EG 36914 368 82 3 KENET-AS, KE 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 8127 3441 596 Uninet S.A. de C.V., MX 47331 6820 937 3630 TTNET, TR 12479 6207 1667 142 UNI2-AS, ES 7545 5748 778 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4748 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4717 313 750 CABLEONE, US 16509 4459 9050 2061 AMAZON-02, US 7155 4035 264 32 VIASAT-SP-BACKBONE, US 22773 3734 2995 198 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3584 1330 21 VIETEL-AS-AP Viettel Group, VN 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 6207 6065 UNI2-AS, ES 7545 5748 5074 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4748 4675 ERX-CERNET-BKB China Education and Research Net 7155 4035 4003 VIASAT-SP-BACKBONE, US 11492 4717 3967 CABLEONE, US 7552 3584 3563 VIETEL-AS-AP Viettel Group, VN 22773 3734 3536 ASN-CXA-ALL-CCI-22773-RDC, US 39891 3459 3437 ALJAWWALSTC-AS, SA 8551 3321 3276 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3347 3265 SHAW, CA 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 174 COGENT-174, 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 393489 UNALLOCATED 12.7.109.0/24 7018 ATT-INTERNET4, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, 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.142.80.0/24 Origin: 397294 UNASSIGNED Transit: 398559 TUNBROKER, 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:8 /9:13 /10:40 /11:101 /12:292 /13:577 /14:1178 /15:1932 /16:13476 /17:8268 /18:14047 /19:25677 /20:41494 /21:50442 /22:103273 /23:87562 /24:486154 /25:1240 /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 47331 6012 6820 TTNET, TR 12479 5175 6207 UNI2-AS, ES 11492 3813 4717 CABLEONE, US 6327 3143 3347 SHAW, CA 7155 3123 4035 VIASAT-SP-BACKBONE, US 22773 2861 3734 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2839 8127 Uninet S.A. de C.V., MX 39891 2801 3459 ALJAWWALSTC-AS, SA 8551 2781 3321 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2224 2482 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1885 2:1208 3:33 4:19 5:3401 6:53 8:1487 9:1 11:1 12:1761 13:347 14:2391 15:72 16:12 17:306 18:91 20:113 23:4058 24:2361 25:3 27:2345 31:2148 32:111 34:1 35:39 36:1086 37:3464 38:2003 39:444 40:151 41:3813 42:626 43:2136 44:226 45:14969 46:3611 47:321 49:1575 50:1678 51:89 52:1127 54:215 55:761 56:7 57:53 58:1792 59:1139 60:817 61:2327 62:2213 63:2009 64:5270 65:2383 66:5109 67:2926 68:1169 69:4105 70:1406 71:684 72:3005 74:2545 75:1462 76:687 77:2043 78:3313 79:2582 80:2040 81:1696 82:1378 83:1080 84:1265 85:3188 86:618 87:1789 88:2531 89:2878 90:387 91:7139 92:1643 93:2537 94:2881 95:4270 96:1241 97:340 98:956 99:979 100:89 101:1033 102:1150 103:24857 104:3629 105:375 106:899 107:2155 108:691 109:3722 110:1986 111:2333 112:1656 113:1535 114:1524 115:1851 116:1857 117:2097 118:2259 119:1791 120:935 121:1028 122:2295 123:2114 124:1621 125:2145 128:1372 129:1244 130:765 131:1995 132:753 133:312 134:1388 135:329 136:678 137:899 138:2290 139:1156 140:764 141:1144 142:1028 143:1246 144:1209 145:333 146:1356 147:1236 148:2168 149:1242 150:756 151:1193 152:1595 153:442 154:3291 155:1286 156:2483 157:1122 158:906 159:2031 160:2003 161:1068 162:3190 163:911 164:1518 165:1322 166:593 167:1704 168:3591 169:626 170:4291 171:747 172:2006 173:2925 174:957 175:1061 176:2875 177:4354 178:2788 179:1895 180:2274 181:2569 182:3157 183:1502 184:2436 185:17417 186:3952 187:2977 188:3288 189:2700 190:9135 191:1369 192:10580 193:7847 194:6390 195:4552 196:3107 197:2225 198:6056 199:5904 200:7333 201:5264 202:10554 203:10185 204:4648 205:3093 206:3285 207:3304 208:4012 209:4526 210:4201 211:2082 212:3552 213:3176 214:1197 215:60 216:6150 217:2492 218:862 219:631 220:2046 221:926 222:969 223:1681 End of report

1 0

Akamai TE Contacts
by Robert Carstens 20 Nov '20

20 Nov '20

Does anyone have a contact for someone at Akamai besides the standard Netsupport and tix emails? Or if anyone from Akamai is on the list, can you please contact me off list? We are in need of assistance with TE for Akamai sourced traffic since standard methods are not doable with their CDN. Their NOG presentations usually say to contact them if you need assistance with adjusting traffic flows, but I cannot get a response. We have been contacting them for over a month now with no acknowledgement. Robert

2 1

ARIN hosted RPKI key rotation
by Ca By 20 Nov '20

20 Nov '20

Hello folks, I use ARIN hosted RPKI to publish ROAs The ROAs have an expire date How do i rotate the cert to push out the expiration date? Does ARIN do this for me? Thanks!

3 3

NANOG 81: Call For Presentations
by Steve Feldman 20 Nov '20

20 Nov '20

NANOG Community, The NANOG Program Committee (PC) would like to remind you they are accepting proposals for all sessions at NANOG 81, February 8-10, 2021. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at https://nanog.org/meetings/nanog-81/nanog-81-call-presentations/. Given by many of the industry’s top minds, presentations at NANOG meetings are meant to spark the imagination, encourage dialog, and drive new solutions to our greatest networking challenges. The PC is currently seeking proposals, and also welcomes suggestions for speakers and topics. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional, or discuss proprietary solutions. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the title and abstract Timeline for submission and proposal review: - Submitter enters abstract (and draft slides if possible) in Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — within 2 weeks. - Submitter develops draft slides of talk if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic. - Draft presentation slides should be submitted prior to the published deadline for slides (Dec. 14, 2020). - PC evaluates submissions to determine presentations for the agenda (posted on Jan. 25, 2021). - Agenda assembled and posted. - Submitters notified. - Final presentation slides must be submitted prior to the published deadline for slides (Jan. 11, 2021). If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nanogpc(a)nanog.org) and a representative will respond to you in a timely manner. Otherwise, submit your talk, keynote, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 81 Calendar of Events Date Event/Deadline Nov 19, 2020 CFP Announced Dec 7, 2020 CFP Reminder Dec 14, 2020 CFP Deadline: Draft Presentation Slides Due Jan 4, 2021 Registration Opens Jan 11, 2021 Topics List + Highlights Posted Jan 11, 2021 Speaker FINAL Presentations Due Jan 22, 2021 Speaker Presentation Recordings Finalized Jan 25, 2021 NANOG 81 Agenda Published Feb 8-10, 2021 NANOG 81 Virtual Conference Final slides must be submitted by Monday, January 11, 2021, and no changes will be accepted between that date and the conference. Materials received after that date may be updated on the website after the completion of the conference. We look forward to “seeing you” in February on our virtual platform! Sincerely, Steve Feldman On behalf of the NANOG PC

1 0

Sprint contact - Mobile network block DNS
by Andrew Imeson 19 Nov '20

19 Nov '20

I'm looking for a contact at Sprint (or T-Mobile?) mobile networking, if someone could please contact me off-list. I help run a service that relies on being able to make DNS queries via standard UDP directly to particular servers, and recently we've been seeing all the packets silently dropped on Sprint with both iOS and Android devices. -- Thanks, Andrew Imeson

1 0

Mozilla solicits comments on rolling DoH wide
by Jay R. Ashworth 19 Nov '20

19 Nov '20

If, like me, you think it's a solution in search of a problem -- excuse me, a *problem* in search of a problem -- here's your chance: https://www.zdnet.com/article/fearing-drama-mozilla-opens-public-consultati… -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

Spectrum (AS33363) Clue?
by Bryan Fields 19 Nov '20

19 Nov '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Is there anyone at Spectrum business with clue who can contact me off list regarding some peering issues in your network? I have several customers seeing 150ms of latency due to traffic bouncing between east and west coasts to go across the room. This is between routers both in TAMSFLDE. Support has said this is "normal" and refused to escalate it. Some quick testing with RIPE Atlas probes shows it's the same across 33363. Thanks, - -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEaESdNosUjpjcN/JhYTmgYVLGkUAFAl+0N20ACgkQYTmgYVLG kUAsBQ/8Cu5i3rH98K/pEwawV391d++V8dQWrFosYEz6Yp99OTJg3K2NcgI5wYGj +cfTYbw2sGTQUB57bIxZbpAYIV1KIeEwHckQ2P/2coud9y8yeuFjSY2kEYl5HpoV T9Q8bIw8XTvZgPZYvQ9VPry4zWscV+2OoHEZQpQSN4MOyjN1Oj+w36/nM3La+Dp3 RaQkbKKW44LcAgqn4wUqdZgmZcYpsgz+RyA9hbbvT3tl7693LdD4XcenULo0t4kS cu0YcoDA7+2yoTdF7yzabl0qPwhqfhTPEYczWxHEqfEXN0NebV5Nqj4pMAQfQFZ2 mEyckAx84+hL2op0XVXYPnbU6Kd3i5JZxcHOwXIp5Kk0LvZVSfMypseAAPRzS/M+ PXbnlqFYf350VOjV7rQn23UWo5kduxzvOyc+bYGAvsqJWYumpIGYqe05EHQqYiBO RTuJoOLmEYfg52OML/ih0M9UPGtluIZvvMPv+jLmbyVt2COjaJnVGiWWfrIjkQqr 2kjIRrja3RTvHZHVUHHyZZMdfjufjb2fIhboHDhhEueEMSPBdzCb+j241IrG4IHb sDWkhkcdXyN82htvEocZDJqGGMQqzCP86TWoefjN3YOjKMLl8kL9HgRV7eZGZJc9 6cbQrh50mWHQtYgki9a0+3Sk9Eu7cJIWSAA4p6l3WaOa80VGbEw= =BfB0 -----END PGP SIGNATURE-----

3 3