February 2021 - Test - lists.nanog.org

London Interxion Data Centers
by Rod Beck 01 Mar '21

01 Mar '21

Hi Folks, My understanding is that there are three London Interxion data centers (I thought Equinix was the Borg and had assimilated pretty everything at this point). Trying to get the address where the facility where the London Metal Exchange houses its trading engine. No, financial institutions don't like to give this info to transport providers. The trading engine is the heart of electronic trading - it matches buy and sell offers. Regards, Roderick. Roderick Beck Global Network Capacity Procurement United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> https://unitedcablecompany.com/video/ New York City & Budapest rod.beck(a)unitedcablecompany.com Budapest: 36-70-605-5144 NJ: 908-452-8183 [1467221477350_image005.png]

4 5

Re: DoD IP Space
by scott 27 Feb '21

27 Feb '21

--- sabri(a)cluecentral.net wrote: From: Sabri Berisha <sabri(a)cluecentral.net> The true enemy here is mid-level management that refuses to prioritize deployment of IPv6. What we should be discussing is how best to approach that problem. It's where ops and corporate politics overlap. ---------------------------------------------- 100% agreed! Been whining about that here many times. I have been trying to get IPv6 going for a long time, but the above stopped my plans. One thing I mentioned recently, though, is we just got a $BIGCUSTOMER and their requirement was we do IPv6. So keep your IPv6 deployment plans ready. In my case they said a 'we need it right now' kind of thing. That could happen to anyone here. scott

14 23

Newbie Question: Is anyone actually using the Null MX (RFC 7505)?
by Pirawat WATANAPONGSE 26 Feb '21

26 Feb '21

Dear all, I put the “Null MX” Record (RFC 7505) into one of my domains yesterday, then those online mail diagnostic tools out there start getting me worried: It looks like most of those tools do not recognize the Null MX as a special case; they just complain that they cannot find the mail server at “.” [Sarcasm: as if the root servers are going to provide mail service to a mere mortal like me!] Among a few shining exceptions (in a good way) is the good ol’ https://bgp.he.net/ which does not show that domain as having any MX record. [maybe it is also wrong, in the other direction?] I fear that the MTAs are going to behave that same way, treating my Null MX as a “misconfigured mail server name” and that my record will mean unnecessary extra queries to the root servers. [well, minus cache hit] So, here comes the questions: 1. Is there anyone actively using this Null MX? If so, may I please see that actual record line (in BIND zone file format) just to satisfy myself that I wrote mine correctly? 2. Which one makes more sense from the practical point-of-view: having a Null MX Record for the no-mail domain, or having no MX record at all? Thanks in advance for all advices, -- Pirawat.

8 12

Weekly Routing Table Report
by cscora＠apnic.net 26 Feb '21

26 Feb '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 27 Feb, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 847193 Prefixes after maximum aggregation (per Origin AS): 322664 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 404082 Total ASes present in the Internet Routing Table: 70649 Prefixes per ASN: 11.99 Origin-only ASes present in the Internet Routing Table: 60774 Origin ASes announcing only one prefix: 25076 Transit ASes present in the Internet Routing Table: 9875 Transit-only ASes present in the Internet Routing Table: 299 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 62 Max AS path prepend of ASN (266299) 59 Prefixes from unregistered ASNs in the Routing Table: 978 Number of instances of unregistered ASNs: 982 Number of 32-bit ASNs allocated by the RIRs: 35208 Number of 32-bit ASNs visible in the Routing Table: 29241 Prefixes from 32-bit ASNs in the Routing Table: 136223 Number of bogon 32-bit ASNs visible in the Routing Table: 16 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 562 Number of addresses announced to Internet: 2915817600 Equivalent to 173 /8s, 203 /16s and 216 /24s Percentage of available address space announced: 78.8 Percentage of allocated address space announced: 78.8 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: 289157 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 221800 Total APNIC prefixes after maximum aggregation: 65449 APNIC Deaggregation factor: 3.39 Prefixes being announced from the APNIC address blocks: 217721 Unique aggregates announced from the APNIC address blocks: 88511 APNIC Region origin ASes present in the Internet Routing Table: 11310 APNIC Prefixes per ASN: 19.25 APNIC Region origin ASes announcing only one prefix: 3218 APNIC Region transit ASes present in the Internet Routing Table: 1606 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 30 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6455 Number of APNIC addresses announced to Internet: 770662656 Equivalent to 45 /8s, 239 /16s and 97 /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: 244189 Total ARIN prefixes after maximum aggregation: 112229 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 244750 Unique aggregates announced from the ARIN address blocks: 116755 ARIN Region origin ASes present in the Internet Routing Table: 18747 ARIN Prefixes per ASN: 13.06 ARIN Region origin ASes announcing only one prefix: 6813 ARIN Region transit ASes present in the Internet Routing Table: 1923 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3737 Number of ARIN addresses announced to Internet: 1152112896 Equivalent to 68 /8s, 171 /16s and 217 /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: 242205 Total RIPE prefixes after maximum aggregation: 112911 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 238145 Unique aggregates announced from the RIPE address blocks: 139917 RIPE Region origin ASes present in the Internet Routing Table: 27746 RIPE Prefixes per ASN: 8.58 RIPE Region origin ASes announcing only one prefix: 11903 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: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9971 Number of RIPE addresses announced to Internet: 710165376 Equivalent to 42 /8s, 84 /16s and 67 /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: 112868 Total LACNIC prefixes after maximum aggregation: 26402 LACNIC Deaggregation factor: 4.27 Prefixes being announced from the LACNIC address blocks: 114012 Unique aggregates announced from the LACNIC address blocks: 48296 LACNIC Region origin ASes present in the Internet Routing Table: 10688 LACNIC Prefixes per ASN: 10.67 LACNIC Region origin ASes announcing only one prefix: 2638 LACNIC Region transit ASes present in the Internet Routing Table: 2020 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 62 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8293 Number of LACNIC addresses announced to Internet: 174540032 Equivalent to 10 /8s, 103 /16s and 69 /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: 25152 Total AfriNIC prefixes after maximum aggregation: 4937 AfriNIC Deaggregation factor: 5.09 Prefixes being announced from the AfriNIC address blocks: 32003 Unique aggregates announced from the AfriNIC address blocks: 10099 AfriNIC Region origin ASes present in the Internet Routing Table: 1456 AfriNIC Prefixes per ASN: 21.98 AfriNIC Region origin ASes announcing only one prefix: 504 AfriNIC Region transit ASes present in the Internet Routing Table: 286 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 38 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 785 Number of AfriNIC addresses announced to Internet: 107908352 Equivalent to 6 /8s, 110 /16s and 141 /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 5707 782 668 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4830 4192 74 ERX-CERNET-BKB China Education and Rese 9808 3689 9045 60 CMNET-GD Guangdong Mobile Communication 7552 3554 1330 21 VIETEL-AS-AP Viettel Group, VN 7713 3232 936 533 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2897 1896 55 VNPT-AS-VN VNPT Corp, VN 4766 2444 11105 568 KIXS-AS-KR Korea Telecom, KR 9498 2307 482 229 BBIL-AP BHARTI Airtel Ltd., IN 4755 2144 441 191 TATACOMM-AS TATA Communications formerl 45090 2080 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 16509 4850 9095 2177 AMAZON-02, US 11492 4759 316 718 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 22773 3909 2998 251 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3331 1317 72 SHAW, CA 16625 3305 1722 2352 AKAMAI-AS, US 209 2520 5058 501 CENTURYLINK-US-LEGACY-QWEST, US 30036 2518 371 81 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2352 3000 1642 FRONTIER-FRTR, US 5972 2195 439 776 DNIC-ASBLK-05800-06055, 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 7999 1076 3346 TTNET, TR 12479 6351 1701 147 UNI2-AS, ES 20940 3445 3347 207 AKAMAI-ASN1, NL 39891 3266 187 22 ALJAWWALSTC-AS, SA 8551 3041 379 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2876 2282 889 ROSTELECOM-AS, RU 9009 2422 247 1310 M247, GB 34984 2178 355 583 TELLCOM-AS, TR 13188 1610 100 31 TRIOLAN, UA 58224 1526 873 562 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 8371 3466 583 Uninet S.A. de C.V., MX 10620 3399 526 614 Telmex Colombia S.A., CO 11830 2563 369 63 Instituto Costarricense de Electricidad 13999 1637 436 420 Mega Cable, S.A. de C.V., MX 7303 1447 921 269 Telecom Argentina S.A., AR 6503 1440 311 475 Axtel, S.A.B. de C.V., MX 28573 1404 2263 219 CLARO S.A., BR 3816 1198 609 153 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1127 377 39 Telefonica del Peru S.A.A., PE 11664 991 210 409 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 1577 393 22 LINKdotNET-AS, EG 24835 1289 482 29 RAYA-AS, EG 36992 1188 1537 174 ETISALAT-MISR, EG 36903 970 506 115 MT-MPLS, MA 29571 704 68 11 ORANGE-COTE-IVOIRE, CI 6713 540 1864 35 IAM-AS, MA 36935 487 522 40 Vodafone-, EG 37342 487 32 1 MOVITEL, MZ 23889 454 232 16 MauritiusTelecom, MU 15399 445 46 16 WANANCHI-, 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 8371 3466 583 Uninet S.A. de C.V., MX 47331 7999 1076 3346 TTNET, TR 12479 6351 1701 147 UNI2-AS, ES 7545 5707 782 668 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 4850 9095 2177 AMAZON-02, US 4538 4830 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4759 316 718 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 22773 3909 2998 251 ASN-CXA-ALL-CCI-22773-RDC, US 9808 3689 9045 60 CMNET-GD Guangdong Mobile Communication 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 6351 6204 UNI2-AS, ES 7545 5707 5039 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4830 4756 ERX-CERNET-BKB China Education and Research Net 47331 7999 4653 TTNET, TR 11492 4759 4041 CABLEONE, US 7155 4030 3998 VIASAT-SP-BACKBONE, US 22773 3909 3658 ASN-CXA-ALL-CCI-22773-RDC, US 9808 3689 3629 CMNET-GD Guangdong Mobile Communication Co.Ltd. 7552 3554 3533 VIETEL-AS-AP Viettel Group, VN 6327 3331 3259 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 18604 UNALLOCATED 8.25.204.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 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, 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: 397881 STINGERS, US Transit: 398481 REDMERCURY, US 23.226.240.0/20 Origin: 40430 UNASSIGNED Transit: 174 COGENT-174, 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:11 /9:12 /10:41 /11:102 /12:292 /13:577 /14:1182 /15:1939 /16:13465 /17:8316 /18:13772 /19:25626 /20:41718 /21:50941 /22:105375 /23:89651 /24:492739 /25:1434 /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 7151 7999 TTNET, TR 12479 5309 6351 UNI2-AS, ES 11492 3813 4759 CABLEONE, US 6327 3136 3331 SHAW, CA 7155 3118 4030 VIASAT-SP-BACKBONE, US 8151 2948 8371 Uninet S.A. de C.V., MX 22773 2944 3909 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3266 ALJAWWALSTC-AS, SA 8551 2505 3041 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2238 2518 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:1881 2:1168 3:94 4:18 5:3596 6:64 7:5 8:1498 9:1 11:36 12:1755 13:359 14:2350 15:77 16:15 17:315 18:93 20:126 22:188 23:4382 24:2389 25:2 27:2381 31:2253 32:112 34:3 35:39 36:1146 37:3712 38:2050 39:485 40:148 41:3815 42:904 43:2105 44:237 45:14988 46:3695 47:319 49:1616 50:1708 51:90 52:1204 54:216 55:763 56:6 57:57 58:1703 59:1157 60:884 61:2374 62:2223 63:1969 64:5274 65:2403 66:5164 67:2926 68:1174 69:4107 70:1404 71:688 72:3244 74:2591 75:1478 76:689 77:2005 78:3691 79:2299 80:1832 81:1630 82:1309 83:1107 84:1257 85:3344 86:711 87:1793 88:2795 89:2987 90:428 91:7262 92:1730 93:2532 94:2966 95:4427 96:1228 97:345 98:986 99:971 100:89 101:1065 102:1257 103:25524 104:3673 105:419 106:719 107:2217 108:684 109:3890 110:1998 111:2558 112:1779 113:1638 114:1443 115:1870 116:1885 117:2182 118:2319 119:1916 120:988 121:1085 122:2161 123:2178 124:1586 125:2081 128:1340 129:1200 130:810 131:2015 132:751 133:354 134:1549 135:290 136:724 137:901 138:2298 139:1162 140:745 141:1168 142:1069 143:1263 144:1235 145:327 146:1390 147:1253 148:2206 149:1303 150:769 151:1082 152:1549 153:387 154:2209 155:1346 156:1488 157:1147 158:928 159:2054 160:2070 161:1137 162:3241 163:963 164:1430 165:1338 166:614 167:1778 168:3528 169:653 170:4322 171:759 172:2082 173:2963 174:979 175:1099 176:2970 177:4350 178:2889 179:1933 180:2271 181:2620 182:3195 183:1637 184:2459 185:17942 186:4195 187:3071 188:3291 189:2781 190:9038 191:1451 192:10676 193:7924 194:6525 195:4653 196:2936 197:2327 198:6039 199:6001 200:7388 201:5360 202:10540 203:10090 204:4645 205:3292 206:3472 207:3329 208:3979 209:4624 210:4253 211:2173 212:3657 213:3278 214:1214 215:61 216:6180 217:2530 218:1046 219:687 220:2060 221:946 222:979 223:1759 End of report

1 0

OARC 35 Workshop, May 6th & 7th, Registration and Call for Contributions now open
by Jake Zack 26 Feb '21

26 Feb '21

OARC 35 will be an online meeting on May 6th & 7th starting at 01:00 UTC. The Programme Committee is seeking contributions from the community. All DNS-related subjects and suggestions for discussion topics are welcome. For inspiration, we provide a non-exhaustive list of ideas: - Stories of DNS Migrations: Reasoning for DNS software migration. Tooling used to ensure a smooth and correct process. - DNS Intricacies: Chasing down problems and surprising behavior. - Garbage Traffic: Analysis on unexpected traffic seen by authoritative and recursive servers. - DITL: Day In The Life of various roles and teams in DNS. As it is an online workshop, we'd like to encourage brevity; presentations should not be longer than 20 minutes (with additional time for questions). **Workshop Milestones:** * 04 Feb 2021 - Submissions open via Indico * 18 Mar 2021 - Deadline for submission (23:59 UTC) * 25 Mar 2021 - Initial Contribution list published * 08 Apr 2021 - Full agenda published * 22 Apr 2021 - Deadline for slideset submission and Rehearsal * 06 May 2021 - OARC 35 Workshop The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc35> DNS-OARC provides registration fee waivers for the workshop to support those who are part of under-represented groups at DNS-OARC. See the registration page for details. To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft slides are acceptable on submission. Additional information for speakers of OARC 35: * your talk will be broadcast live and recorded for future reference * your presentation slides will be available for delegates and others to download and refer to, before, during and after the meeting * you will be expected to attend a rehearsal on April 22nd. It would be very useful to have your slides (even if draft) ready for this. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> Jacob Zack for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- Jacob Zack DNS Architect – CIRA (.CA TLD)

1 0

Anyone from Charter or Spectrum?
by Joseph Jenkins 25 Feb '21

25 Feb '21

Seeing some issues with packet loss from my users on Charter and Spectrum in California when trying to access my network on Level3/Lumen. Trying to figure out if there are any issues on the Charter or Spectrum side and how to help out my users.

1 0

Comcast Burp in Mass/Boston Area
by Jason Kuehl 25 Feb '21

25 Feb '21

Anyone else with Comcast have a small outage? About 5-7 minutes? -- Sincerely, Jason W Kuehl Cell 920-419-8983 jason.w.kuehl(a)gmail.com

2 3

Historic IRR/RADB snapshots?
by Lars Prehn 24 Feb '21

24 Feb '21

Does anybody have (somewhat frequent, e.g., monthly) snapshots of the various IRR databases lying around? Any snapshot since 2010 would be helpful! Best regards, Lars

3 2

Why are FCC outage reports treated as confidential?
by Sean Donelan 24 Feb '21

24 Feb '21

FCC is proposing a change to who can have access to FCC outage reports. But first a little history.... After the 1990 AT&T Long Distance switching network collapse, there were lots of investigations. The January 15th outage was the biggest, there were a few more smaller crashes in 1990 and 1991. The Network Reliability Council at was first organized by the FCC in January of 1992 following a series of major service outages in various local exchange and interexchange wireline telephone networks. In 1992, the FCC established mandatory network outage reporting requirements for telephone carriers. Originally, outage reports were public documents, although you needed to visit the FCC offices in Washington DC to view them in person. Eventually, the FCC posted the outage reports online during the early days of the Internet. Originally, outage reports were presumed public, unless specifically determined to be confidential. I recall an outage report about a circuit serving Area 51 which disappared after it was filed. In 2004, the FCC decided “[t]he disclosure of outage reporting information to the public could present an unacceptable risk of more effective terrorist activity". Actually what happened, one carrier started using FCC outage reports in its advertising claims that it was "more reliable" than other carriers because it reported fewer outages to the FCC. The other carriers got upset and complained to the FCC. Instead of telling the one carrier to stop using the outage reports in its advertisements, the FCC made all the outage reports confidential. After the decision to make outage reports presumptively confidential, in addition to the public, other state, local and federal agencies no longer had access to them. Although FCC still won't make the outage reports public, its creating a complicated process for selective parties to have access to the outage reports. Amendments to Part 4 of the Commission’s Rules Concerning Disruptions to Communications: Second Report and Order - PS Docket No. 15-80 https://docs.fcc.gov/public/attachments/DOC-370262A1.pdf

1 0

FCC March meeting: Notice of Inquiry: EAS alerts through the Internet
by Sean Donelan 24 Feb '21

24 Feb '21

In response to the recently passed READI Act, the Federal Communications Commission agenda for its March meeting includes the following notice of inquiry: https://www.fcc.gov/document/fcc-announces-tentative-agenda-march-open-meet… The NDAA21 directs the Commission, within 180 days, to adopt rules to implement Section 9201 (a)-(d) and to complete an inquiry under Section 9201(e). The FCC is required to report to Congress on the findings of the inquiry within 90 days after its completion. What the Notice of Inquiry Would Do: • Seek comment on whether it is technically feasible to deliver EAS alerts through the Internet, including through streaming services. • Seek comment on whether and how to leverage the capabilities of the Internet to enhance the alerting capabilities of the radio and television broadcasters, cable systems, satellite radio and television providers, and wireline video providers that currently participate in EAS.

1 0