- Test - lists.nanog.org

Autoresponses from NANOG subscribers
by William Herrin 17 Sep '22

17 Sep '22

Howdy, Can the nanog list admins do something about whatever list recipient is causing these messages from the Facebook NOC when I post to the list? Thanks, Bill Herrin ---------- Forwarded message --------- From: noc <noc(a)fb.com> Date: Fri, Sep 16, 2022 at 2:02 PM Subject: Re: [External] Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 To: bill(a)herrin.us <bill(a)herrin.us> Dear Partner, Thanks for reaching out to the Facebook NOC support team. After initial review of your query, we do not see any action needed to be taken here. Please feel free to reply back on this email thread for any support required. Thanks, Facebook NOC -- For hire. https://bill.herrin.us/resume/

2 1

China Telecom in Hunan office tower fire
by Sean Donelan 16 Sep '22

16 Sep '22

The China Telecom office tower fire in Hunan is reportedly out, after completely burning the entire 200m tower (42-floors). China Telecom statement: "By around 4:30 pm today, the fire at our No. 2 Communications Tower in Changsha has been extinguished. No casualties have yet been discovered and communications have not been cut off."

3 3

Looking for contact at Fastly
by Mark Spring 16 Sep '22

16 Sep '22

In short, I am having issues with a couple of our subnets not being able to traverse a fastly peer which I don't manage, it is upstream from me. I need to get this resolved as it is causing issues with a good amount of traffic. I emailed their noc several hours ago with no response yet. Mark Spring Information Systems Manager

2 1

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 16 Sep '22

16 Sep '22

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 17 Sep, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 909144 Prefixes after maximum aggregation (per Origin AS): 342561 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 439421 Total ASes present in the Internet Routing Table: 73660 Prefixes per ASN: 12.34 Origin-only ASes present in the Internet Routing Table: 63260 Origin ASes announcing only one prefix: 26007 Transit ASes present in the Internet Routing Table: 10400 Transit-only ASes present in the Internet Routing Table: 404 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1126 Number of instances of unregistered ASNs: 1127 Number of 32-bit ASNs allocated by the RIRs: 40160 Number of 32-bit ASNs visible in the Routing Table: 33360 Prefixes from 32-bit ASNs in the Routing Table: 160068 Number of bogon 32-bit ASNs visible in the Routing Table: 10 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 616 Number of addresses announced to Internet: 3068824192 Equivalent to 182 /8s, 234 /16s and 138 /24s Percentage of available address space announced: 82.9 Percentage of allocated address space announced: 82.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 308727 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 237144 Total APNIC prefixes after maximum aggregation: 67475 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 232071 Unique aggregates announced from the APNIC address blocks: 96334 APNIC Region origin ASes present in the Internet Routing Table: 12962 APNIC Prefixes per ASN: 17.90 APNIC Region origin ASes announcing only one prefix: 3743 APNIC Region transit ASes present in the Internet Routing Table: 1754 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8200 Number of APNIC addresses announced to Internet: 773418240 Equivalent to 46 /8s, 25 /16s and 109 /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-151865 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: 265063 Total ARIN prefixes after maximum aggregation: 121004 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 265804 Unique aggregates announced from the ARIN address blocks: 128101 ARIN Region origin ASes present in the Internet Routing Table: 19054 ARIN Prefixes per ASN: 13.95 ARIN Region origin ASes announcing only one prefix: 6934 ARIN Region transit ASes present in the Internet Routing Table: 1916 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 33 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4618 Number of ARIN addresses announced to Internet: 1292487936 Equivalent to 77 /8s, 9 /16s and 205 /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: 260848 Total RIPE prefixes after maximum aggregation: 119782 RIPE Deaggregation factor: 2.18 Prefixes being announced from the RIPE address blocks: 258088 Unique aggregates announced from the RIPE address blocks: 153669 RIPE Region origin ASes present in the Internet Routing Table: 28175 RIPE Prefixes per ASN: 9.16 RIPE Region origin ASes announcing only one prefix: 12049 RIPE Region transit ASes present in the Internet Routing Table: 3985 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10801 Number of RIPE addresses announced to Internet: 718336128 Equivalent to 42 /8s, 208 /16s and 240 /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: 116632 Total LACNIC prefixes after maximum aggregation: 27906 LACNIC Deaggregation factor: 4.18 Prefixes being announced from the LACNIC address blocks: 116231 Unique aggregates announced from the LACNIC address blocks: 48971 LACNIC Region origin ASes present in the Internet Routing Table: 10965 LACNIC Prefixes per ASN: 10.60 LACNIC Region origin ASes announcing only one prefix: 2691 LACNIC Region transit ASes present in the Internet Routing Table: 2230 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8725 Number of LACNIC addresses announced to Internet: 176454912 Equivalent to 10 /8s, 132 /16s and 125 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 28331 Total AfriNIC prefixes after maximum aggregation: 5587 AfriNIC Deaggregation factor: 5.07 Prefixes being announced from the AfriNIC address blocks: 36334 Unique aggregates announced from the AfriNIC address blocks: 11838 AfriNIC Region origin ASes present in the Internet Routing Table: 1687 AfriNIC Prefixes per ASN: 21.54 AfriNIC Region origin ASes announcing only one prefix: 590 AfriNIC Region transit ASes present in the Internet Routing Table: 325 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 37 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1016 Number of AfriNIC addresses announced to Internet: 107810560 Equivalent to 6 /8s, 109 /16s and 15 /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 9063 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5914 786 696 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4720 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3575 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3499 1042 61 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3361 1870 59 VNPT-AS-VN VNPT Corp, VN 4766 2471 11124 603 KIXS-AS-KR Korea Telecom, KR 9498 2445 499 238 BBIL-AP BHARTI Airtel Ltd., IN 24560 2206 852 413 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2173 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 7167 10498 2836 AMAZON-02, US 11492 4542 301 591 CABLEONE, US 7155 3898 265 32 VIASAT-SP-BACKBONE, US 22773 3795 3064 355 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3530 1826 2532 AKAMAI-AS, US 6327 3464 1319 63 SHAW, CA 749 3033 50728 2291 DNIC-AS-00749, US 30036 2616 370 231 MEDIACOM-ENTERPRISE-BUSINESS, US 396982 2533 3387 365 GOOGLE-CLOUD-PLATFORM, US 209 2348 4935 394 CENTURYLINK-US-LEGACY-QWEST, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6913 1730 144 UNI2-AS, ES 9121 6854 1692 17 TTNET, TR 20940 4062 3348 217 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA 8551 3986 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2943 2290 910 ROSTELECOM-AS, RU 6849 2702 355 21 UKRTELNET, UA 9009 2604 251 1344 M247, GB 34984 2257 358 633 TELLCOM-AS, TR 47331 1985 312 1500 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10950 3394 557 Uninet S.A. de C.V., MX 10620 3501 515 787 Telmex Colombia S.A., CO 11830 2322 369 65 Instituto Costarricense de Electricidad 13999 1995 325 510 Mega Cable, S.A. de C.V., MX 28573 1360 2328 264 Claro NXT Telecomunicacoes Ltda, BR 6503 1289 338 520 Axtel, S.A.B. de C.V., MX 3816 1279 708 148 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1134 369 21 Telefonica del Peru S.A.A., PE 11664 1058 179 467 Techtel LMDS Comunicaciones Interactiva 26615 985 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1556 393 21 LINKdotNET-AS, EG 24835 1520 521 31 RAYA-AS, EG 36992 1346 1519 268 ETISALAT-MISR, EG 36903 1268 550 99 MT-MPLS, MA 29571 989 68 32 ORANGE-COTE-IVOIRE, CI 36935 810 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 522 52 40 WANANCHI-, KE 37342 481 32 1 MOVITEL, MZ 23889 402 232 16 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10950 3394 557 Uninet S.A. de C.V., MX 9808 9063 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7167 10498 2836 AMAZON-02, US 12479 6913 1730 144 UNI2-AS, ES 9121 6854 1692 17 TTNET, TR 7545 5914 786 696 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4720 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4542 301 591 CABLEONE, US 20940 4062 3348 217 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9063 9013 CHINAMOBILE-CN China Mobile Communications Grou 9121 6854 6837 TTNET, TR 12479 6913 6769 UNI2-AS, ES 7545 5914 5218 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4720 4645 ERX-CERNET-BKB China Education and Research Net 16509 7167 4331 AMAZON-02, US 39891 4010 3963 ALJAWWALSTC-AS, SA 11492 4542 3951 CABLEONE, US 8551 3986 3948 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3898 3866 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 25674 UNALLOCATED 8.19.146.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 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 Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.128.80.0/24 Origin: 397372 UNASSIGNED 23.128.80.0/24 Transit: 577 BACOM, CA 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 24.152.20.0/23 Origin: 270472 UNASSIGNED 24.152.20.0/23 Transit: 28186 ITS TELECOMUNICACOES LTDA, BR 24.152.22.0/23 Origin: 270472 UNASSIGNED 24.152.22.0/23 Transit: 28186 ITS TELECOMUNICACOES LTDA, BR 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet Complete listing at https://thyme.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:39 /11:101 /12:297 /13:591 /14:1208 /15:2059 /16:13514 /17:8339 /18:13955 /19:25148 /20:44502 /21:52362 /22:109317 /23:97324 /24:539556 /25:803 /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 9121 6000 6854 TTNET, TR 12479 5911 6913 UNI2-AS, ES 8151 4688 10950 Uninet S.A. de C.V., MX 11492 3462 4542 CABLEONE, US 8551 3450 3986 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3274 3464 SHAW, CA 39891 3193 4010 ALJAWWALSTC-AS, SA 7155 2987 3898 VIASAT-SP-BACKBONE, US 22773 2811 3795 ASN-CXA-ALL-CCI-22773-RDC, US 6849 2558 2702 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1911 2:1020 3:163 4:5 5:3884 6:116 7:6 8:1600 9:1 11:173 12:1634 13:340 14:2367 15:262 16:51 17:361 18:308 20:244 21:4 22:188 23:5947 24:2445 25:6 27:2663 29:19 31:2413 32:94 34:7 35:88 36:1857 37:4474 38:3557 39:740 40:155 41:3916 42:1149 43:2243 44:289 45:16127 46:4188 47:308 48:1 49:1695 50:1932 51:241 52:1493 54:385 55:833 56:8 57:64 58:1786 59:1163 60:983 61:2309 62:2547 63:1916 64:5600 65:2306 66:4879 67:2968 68:1209 69:4156 70:1312 71:686 72:2999 74:2645 75:1455 76:593 77:2266 78:3995 79:3131 80:2058 81:1810 82:1506 83:1200 84:1394 85:3721 86:729 87:1913 88:2826 89:3422 90:557 91:7594 92:2057 93:2543 94:3537 95:4798 96:1309 97:348 98:1031 99:721 100:75 101:1067 102:2319 103:29985 104:4555 105:472 106:889 107:2542 108:892 109:4319 110:1997 111:3324 112:2040 113:1539 114:1500 115:2007 116:1914 117:2480 118:2321 119:1827 120:1736 121:1078 122:2532 123:2093 124:1554 125:2149 128:1224 129:1029 130:1004 131:2029 132:821 133:377 134:1945 135:296 136:860 137:876 138:2522 139:1512 140:950 141:1455 142:1333 143:1395 144:1197 145:343 146:1851 147:1520 148:2215 149:1806 150:868 151:1102 152:1822 153:467 154:3771 155:1424 156:1692 157:1278 158:1041 159:2189 160:2532 161:1343 162:3500 163:1401 164:1674 165:1658 166:794 167:1724 168:3820 169:870 170:4509 171:845 172:3352 173:3118 174:1022 175:1150 176:3606 177:4687 178:3579 179:2144 180:2330 181:3292 182:3232 183:1931 184:2359 185:19710 186:4617 187:3929 188:4008 189:3470 190:8990 191:1490 192:10992 193:8702 194:7130 195:5064 196:2970 197:2459 198:5981 199:6029 200:7697 201:5797 202:10530 203:10028 204:4508 205:3457 206:3841 207:3434 208:4053 209:4719 210:4333 211:2397 212:4077 213:3480 214:1117 215:54 216:6402 217:2630 218:1286 219:567 220:2010 221:922 222:827 223:2004 End of report

1 0

RE: iCloud/Apple Mail contact.
by Nathan Anderson 15 Sep '22

15 Sep '22

Did you ever manage to find out who at Apple to speak to about getting things added to or changed in this database? Quite irritating how there is zero public-facing information about this. Also, an Apple employee authored RFC 6186, yet they don't implement it?? -- Nathan From: NANOG [mailto:nanog-bounces+nathana=fsr.com@nanog.org] On Behalf Of Matt Hohman Sent: Wednesday, July 20, 2022 10:28 AM To: nanog(a)nanog.org Cc: Jonathan Dukes Subject: iCloud/Apple Mail contact. Hello, Looking for an iCloud/Apple admin contact me off list. I’ve exhausted all the usual support channels on this one and some of the responses have been quite comical. Background: Every time you setup an email account in Apple Mail it will check the domain entered against a database of email server settings and conveniently autofill those settings. 10 or so years ago we reached out to our business contact at Apple to setup email server auto discovery for our domain, over the last decade our contact has left and any attempts to reach Apple to get this info updated have been fruitless. The autofilled info now points to a long dead email server. Thanks, Matt Hohman Technical Director New Heights Foundation

2 1

Ziply Fiber contact
by Jay Hennigan 15 Sep '22

15 Sep '22

Is there someone from Ziply Fiber in the PNW here who can contact me offlist? Thanks! -- Jay Hennigan - jay(a)west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV

1 0

Call for Working Group Participation: MANRS+
by Andrei Robachevsky 13 Sep '22

13 Sep '22

Hi, MANRS is looking for volunteers to join a new working group to explore the idea of creating a second, elevated tier of MANRS participation for organizations that comply with more stringent requirements and auditing. We’re calling this MANRS+ at the moment, though that’s only a working title. MANRS has traditionally been focused on peer-to-peer relationships, but we believe generating customer demand could be a powerful driving force for better routing security. If we can enhance the business case, customers will demand better routing security of their network connectivity providers and providers will ensure they’re following best practices and staying in compliance with the MANRS actions that stop routing security incidents. Read more at https://www.manrs.org/2022/09/improving-manrs-call-for-working-group-partic…, and email us at contact(a)manrs.org<mailto:contact@manrs.org> by 23 September to join the MANRS+ working group. We look forward to hearing from you. Regards, Andrei On Behalf of the MANRS Team

1 0

Router ID on IPv6-Only
by Crist Clark 13 Sep '22

13 Sep '22

During some IPv6 numbering discussions at work today, someone had a question that I hadn't really considered before. How to choose 32-bit router IDs for IPv6-only routers. Quick background. We have a requirement to convert a significant portion of our network to IPv6-only over the next few years. Previously, I, and everyone else on the team, have only ever set up routers in dual-stack environments. Choosing a router ID for use in routing protocols just followed whatever rules you used for your IPv4 networking. You used the same router ID in IPv4 and IPv6. Well, now there is no IPv4. But BGP, OSPFv3, and other routing protocols still use 32-bit router IDs for IPv6. On the one hand, there are plenty of 32-bit numbers to use. Generally speaking, router IDs just need to be unique inside of an AS to do their job, but (a) for humans or automation to generate them and (b) to easily recognize them, it's convenient to have some algorithm or methodology for assigning them. Has anyone thought about this or have a good way to do it? We had ideas like use bits 32-63 from an interface. Seems like it could work, but also could totally break down if we're using >64-bit prefixes for things like router-to-router links or pulling router loopbacks out of a common /64. Also, various network OS implementations will typically automatically choose a router ID from the IPv4 addresses on the router by some algorithm (e.g. numerically lowest) if not explicitly configured. Was curious what IPv6-only routers do. Haven't had the chance to get on some lab gear or GNS3 to just try it and see.

11 21

Re: Rogers Outage: What do we Know After Two Months?
by Clayton Zekelman 12 Sep '22

12 Sep '22

It was mentioned: It shouldnt take a parliamentary inquiry or pointed attention from Canadas telecoms regulator, or the <https://www.cbc.ca/news/business/rogers-outage-relevant-to-shaw-deal-1.6565…>fear of having its corporate merger with another enormous IP network backbone blocked, to bring those technical lessons into the light. But not by name. At 07:21 PM 12/09/2022, Eric Kuhnke wrote: >I did a ctrl-f for "Shaw" in that article and there's zero mention of it. > >I realize that the Internet Society is meant to >remain neutral and not comment subjectively on >matters of market competition and conglomeration of telecoms. > >It's very concerning to me that the Rogers/Shaw >acquisition-merger will likely be allowed to >proceed, even further reducing competition, and >increasing centralization (the opposite of the >decentralization mentioned in the article). From >the point of view of a Canadian who works >primarily for US-based ISPs these days, at least >in the US there's seven or eight gargantuan >multi-billion-dollar sized last mile cable >operators. In many parts of Canada it's just >Rogers or Shaw. It's not a good situation at all for the consumer. > > > > > >On Mon, 12 Sept 2022 at 07:42, Sean Donelan ><<mailto:sean@donelan.com>sean(a)donelan.com> wrote: >Article by Internet Society's Resident Advisor Jim Cowie. > > >Rogers Outage: What do we Know After Two Months? > ><https://pulse.internetsociety.org/blog/rogers-outage-what-do-we-know-after-…>https://pulse.internetsociety.org/blog/rogers-outage-what-do-we-know-after-… > >September 9, 2022 > >Itâs now been a full two months since Rogers Telecom suffered a nationwide >Internet outage, leaving tens of millions of Canadians without >telecommunications services. -- Clayton Zekelman Managed Network Systems Inc. (MNSi) 3363 Tecumseh Rd. E Windsor, Ontario N8W 1H4 tel. 519-985-8410 fax. 519-985-8409

1 0

Rogers Outage: What do we Know After Two Months?
by Sean Donelan 12 Sep '22

12 Sep '22

Article by Internet Society's Resident Advisor Jim Cowie. Rogers Outage: What do we Know After Two Months? https://pulse.internetsociety.org/blog/rogers-outage-what-do-we-know-after-… September 9, 2022 It’s now been a full two months since Rogers Telecom suffered a nationwide Internet outage, leaving tens of millions of Canadians without telecommunications services.

2 1