January 2022 - Test - lists.nanog.org

Open source mapping of US high voltage electrical grid
by Eric Kuhnke 16 Jan '22

16 Jan '22

Possibly of interest for network operators who have inter-city circuits, where the underlying carrier is something on OPGW fiber in high voltage lines. These people seem to be making an effort at mapping out high voltage lines, hydroelectric dams, substations, etc. https://openinframap.org

3 2

Contact request AS 6453
by Drew Weaver 15 Jan '22

15 Jan '22

Does anyone have a contact for AS 6453 or are there any AS 6453 folks on list? Seeing some routing trouble from their customers to the US. Thanks, -Drew

3 2

Useful ping targets for end-users?
by Adam Thompson 15 Jan '22

15 Jan '22

Before you start reading, yes, I fully understand how silly this question is. But I need to give _something_ to a customer who has the ability to run ping/traceroute but nothing else. (And they have an intermittent latency problem that we haven’t been able to isolate yet.) Does anyone curate a list of “useful” ICMP responders that are at least kinda-sorta reliable/expected to continue responding? For example, all the major anycast DNS cloud providers respond to ICMP, but I don’t really want to tell my customer to ping an anycast IP address because the RTT results will be useless data (for comparative purposes). I’m also not excited about providing random router IP address for what should be obvious reasons. There are some IPs that my routing paths that should be stable, but between routing changes and control-plane policing, those aren’t awesome. I’m looking for IPs I can suggest that are well outside my network. Restatement: yes, there are much better ways to diagnose problems, but my customer can only run ping & traceroute (and pathping, I suppose) and is capable enough to run those tools and self-assess before calling me. It sounds foolish to even ask, but maybe there’s a resource out there I don’t know about… -Adam Adam Thompson Consultant, Infrastructure Services [MERLIN] 100 - 135 Innovation Drive Winnipeg, MB, R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) athompson(a)merlin.mb.ca<mailto:athompson@merlin.mb.ca> www.merlin.mb.ca<http://www.merlin.mb.ca/>

6 8

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 14 Jan '22

14 Jan '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 15 Jan, 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: 885121 Prefixes after maximum aggregation (per Origin AS): 333219 Deaggregation factor: 2.66 Unique aggregates announced (without unneeded subnets): 425456 Total ASes present in the Internet Routing Table: 72620 Prefixes per ASN: 12.19 Origin-only ASes present in the Internet Routing Table: 62321 Origin ASes announcing only one prefix: 25693 Transit ASes present in the Internet Routing Table: 10299 Transit-only ASes present in the Internet Routing Table: 377 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 53 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 910 Number of instances of unregistered ASNs: 914 Number of 32-bit ASNs allocated by the RIRs: 38307 Number of 32-bit ASNs visible in the Routing Table: 31840 Prefixes from 32-bit ASNs in the Routing Table: 148041 Number of bogon 32-bit ASNs visible in the Routing Table: 23 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 568 Number of addresses announced to Internet: 3074313728 Equivalent to 183 /8s, 62 /16s and 78 /24s Percentage of available address space announced: 83.0 Percentage of allocated address space announced: 83.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: 299471 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 232790 Total APNIC prefixes after maximum aggregation: 65474 APNIC Deaggregation factor: 3.56 Prefixes being announced from the APNIC address blocks: 227581 Unique aggregates announced from the APNIC address blocks: 93678 APNIC Region origin ASes present in the Internet Routing Table: 12263 APNIC Prefixes per ASN: 18.56 APNIC Region origin ASes announcing only one prefix: 3490 APNIC Region transit ASes present in the Internet Routing Table: 1704 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7446 Number of APNIC addresses announced to Internet: 774476672 Equivalent to 46 /8s, 41 /16s and 147 /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: 257494 Total ARIN prefixes after maximum aggregation: 118531 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 257375 Unique aggregates announced from the ARIN address blocks: 122888 ARIN Region origin ASes present in the Internet Routing Table: 18930 ARIN Prefixes per ASN: 13.60 ARIN Region origin ASes announcing only one prefix: 6862 ARIN Region transit ASes present in the Internet Routing Table: 1950 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 34 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4286 Number of ARIN addresses announced to Internet: 1300451328 Equivalent to 77 /8s, 131 /16s and 80 /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: 252847 Total RIPE prefixes after maximum aggregation: 116069 RIPE Deaggregation factor: 2.18 Prefixes being announced from the RIPE address blocks: 249215 Unique aggregates announced from the RIPE address blocks: 148413 RIPE Region origin ASes present in the Internet Routing Table: 28168 RIPE Prefixes per ASN: 8.85 RIPE Region origin ASes announcing only one prefix: 12135 RIPE Region transit ASes present in the Internet Routing Table: 3969 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10598 Number of RIPE addresses announced to Internet: 713844352 Equivalent to 42 /8s, 140 /16s and 102 /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: 113593 Total LACNIC prefixes after maximum aggregation: 27175 LACNIC Deaggregation factor: 4.18 Prefixes being announced from the LACNIC address blocks: 114409 Unique aggregates announced from the LACNIC address blocks: 48485 LACNIC Region origin ASes present in the Internet Routing Table: 10909 LACNIC Prefixes per ASN: 10.49 LACNIC Region origin ASes announcing only one prefix: 2661 LACNIC Region transit ASes present in the Internet Routing Table: 2197 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 53 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8591 Number of LACNIC addresses announced to Internet: 176636672 Equivalent to 10 /8s, 135 /16s and 67 /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: 27487 Total AfriNIC prefixes after maximum aggregation: 5281 AfriNIC Deaggregation factor: 5.20 Prefixes being announced from the AfriNIC address blocks: 35973 Unique aggregates announced from the AfriNIC address blocks: 11486 AfriNIC Region origin ASes present in the Internet Routing Table: 1582 AfriNIC Prefixes per ASN: 22.74 AfriNIC Region origin ASes announcing only one prefix: 545 AfriNIC Region transit ASes present in the Internet Routing Table: 308 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 42 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 919 Number of AfriNIC addresses announced to Internet: 108532480 Equivalent to 6 /8s, 120 /16s and 19 /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 8726 8919 50 CHINAMOBILE-CN China Mobile Communicati 7545 5842 787 680 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4689 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3611 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3492 1038 51 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3426 1880 57 VNPT-AS-VN VNPT Corp, VN 4766 2517 11120 602 KIXS-AS-KR Korea Telecom, KR 9498 2228 474 231 BBIL-AP BHARTI Airtel Ltd., IN 45090 2163 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 4755 2118 429 199 TATACOMM-AS TATA Communications formerl 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 6090 10131 2623 AMAZON-02, US 11492 4597 304 768 CABLEONE, US 22773 4022 3030 376 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3951 264 30 VIASAT-SP-BACKBONE, US 16625 3672 1894 2566 AKAMAI-AS, US 6327 3348 1318 63 SHAW, CA 749 2889 50784 2145 DNIC-AS-00749, US 30036 2608 374 127 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2512 5042 429 CENTURYLINK-US-LEGACY-QWEST, US 20115 2247 3035 507 CHARTER-20115, 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 6829 1730 150 UNI2-AS, ES 9121 6718 1692 17 TTNET, TR 20940 3877 3348 210 AKAMAI-ASN1, NL 8551 3776 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 39891 3271 187 23 ALJAWWALSTC-AS, SA 12389 2951 2286 903 ROSTELECOM-AS, RU 9009 2478 253 1295 M247, GB 34984 2216 357 602 TELLCOM-AS, TR 47331 1963 314 1495 TTNET, TR 58224 1777 925 589 TCI, IR 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 10222 3463 575 Uninet S.A. de C.V., MX 10620 3442 519 715 Telmex Colombia S.A., CO 11830 2464 369 62 Instituto Costarricense de Electricidad 13999 1641 283 463 Mega Cable, S.A. de C.V., MX 6503 1440 354 524 Axtel, S.A.B. de C.V., MX 28573 1393 2326 253 CLARO S.A., BR 3816 1245 658 146 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 26615 1146 2350 138 TIM SA, BR 6147 1092 369 21 Telefonica del Peru S.A.A., PE 11664 994 191 443 Techtel LMDS Comunicaciones Interactiva 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 1640 393 21 LINKdotNET-AS, EG 24835 1547 515 32 RAYA-AS, EG 36992 1299 1518 262 ETISALAT-MISR, EG 36903 1195 543 114 MT-MPLS, MA 29571 871 68 12 ORANGE-COTE-IVOIRE, CI 36935 734 521 39 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 519 50 33 WANANCHI-, KE 37342 468 32 1 MOVITEL, MZ 23889 428 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 10222 3463 575 Uninet S.A. de C.V., MX 9808 8726 8919 50 CHINAMOBILE-CN China Mobile Communicati 12479 6829 1730 150 UNI2-AS, ES 9121 6718 1692 17 TTNET, TR 16509 6090 10131 2623 AMAZON-02, US 7545 5842 787 680 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4689 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4597 304 768 CABLEONE, US 22773 4022 3030 376 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3951 264 30 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 8726 8676 CHINAMOBILE-CN China Mobile Communications Grou 9121 6718 6701 TTNET, TR 12479 6829 6679 UNI2-AS, ES 7545 5842 5162 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4689 4615 ERX-CERNET-BKB China Education and Research Net 7155 3951 3921 VIASAT-SP-BACKBONE, US 11492 4597 3829 CABLEONE, US 8551 3776 3737 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 20940 3877 3667 AKAMAI-ASN1, NL 22773 4022 3646 ASN-CXA-ALL-CCI-22773-RDC, 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 46990 UNALLOCATED 8.5.242.0/23 3356 LEVEL3, 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 32848 UNALLOCATED 8.28.72.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 1782 UNALLOCATED 8.42.19.0/24 46887 LIGHTOWER, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 395056 UNALLOCATED 8.45.133.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.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.252.160.0/24 Origin: 398968 GROUP-IID-01, US 23.252.160.0/24 Transit: 174 COGENT-174, US 23.252.161.0/24 Origin: 398968 GROUP-IID-01, US 23.252.161.0/24 Transit: 174 COGENT-174, US 23.252.162.0/24 Origin: 398968 GROUP-IID-01, US 23.252.162.0/24 Transit: 174 COGENT-174, US 23.252.163.0/24 Origin: 398968 GROUP-IID-01, US 23.252.163.0/24 Transit: 174 COGENT-174, US 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:41 /11:102 /12:305 /13:593 /14:1214 /15:2038 /16:13569 /17:8320 /18:13875 /19:25171 /20:43230 /21:51779 /22:108388 /23:94988 /24:520689 /25:790 /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 5893 6718 TTNET, TR 12479 5777 6829 UNI2-AS, ES 8151 4195 10222 Uninet S.A. de C.V., MX 11492 3532 4597 CABLEONE, US 8551 3241 3776 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3159 3348 SHAW, CA 7155 3041 3951 VIASAT-SP-BACKBONE, US 22773 3002 4022 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2807 3271 ALJAWWALSTC-AS, SA 30036 2263 2608 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1902 2:997 3:153 4:7 5:3701 6:101 7:5 8:1557 9:1 11:172 12:1705 13:407 14:2361 15:145 16:39 17:374 18:129 20:165 21:4 22:188 23:5398 24:2374 25:4 27:2585 29:19 31:2407 32:104 34:1 35:50 36:1733 37:3926 38:2459 39:737 40:149 41:3913 42:1067 43:2100 44:294 45:15969 46:3876 47:302 49:1635 50:1905 51:107 52:1345 54:293 55:733 56:8 57:55 58:1767 59:1138 60:953 61:2255 62:2418 63:1936 64:5366 65:2321 66:4927 67:2930 68:1182 69:4171 70:1346 71:677 72:3068 74:2628 75:1516 76:715 77:2170 78:3800 79:2882 80:1915 81:1654 82:1444 83:1196 84:1324 85:3587 86:708 87:1882 88:2617 89:3142 90:498 91:7528 92:1893 93:2595 94:3266 95:4493 96:1313 97:344 98:991 99:863 100:75 101:1049 102:1865 103:27974 104:4113 105:459 106:841 107:2431 108:747 109:4164 110:2053 111:3179 112:1956 113:1533 114:1531 115:1944 116:1890 117:2499 118:2320 119:1850 120:1661 121:1029 122:2530 123:2114 124:1615 125:2062 128:1362 129:1150 130:916 131:2085 132:758 133:367 134:1927 135:285 136:849 137:862 138:2469 139:1220 140:868 141:1334 142:1247 143:1424 144:1229 145:336 146:1751 147:1466 148:2210 149:1653 150:856 151:1080 152:1785 153:446 154:3678 155:1360 156:1864 157:1209 158:998 159:2002 160:2386 161:1260 162:3420 163:1185 164:1663 165:1530 166:624 167:1678 168:3674 169:687 170:4310 171:824 172:2956 173:3048 174:1015 175:1124 176:3460 177:4574 178:3022 179:2001 180:2286 181:2848 182:3215 183:1926 184:2416 185:19184 186:4267 187:3508 188:3764 189:3101 190:8857 191:1331 192:10990 193:8478 194:6941 195:4978 196:2909 197:2381 198:5971 199:5992 200:7465 201:5655 202:10465 203:10015 204:4521 205:3379 206:3841 207:3377 208:3995 209:4592 210:4229 211:2449 212:3913 213:3375 214:1160 215:64 216:6386 217:2627 218:1226 219:607 220:1958 221:983 222:860 223:2153 End of report

1 0

BGP Route Monitoring
by Sandoiu Mihai 13 Jan '22

13 Jan '22

Hi I am looking for a route monitoring product that does the following: -checks if a specific bgp route from a specific neighbor is present the BGP table (in some vrf, not necessarily internet routed vrf) of an ASR9K running IOS XR -sends a syslog message or an alarm if the route goes missing The use case is the following: we are receiving same routes over 2 or more bgp peerings, due to best route we cannot really see at the moment if one of the routes ceased to be received over a certain peering. Alternative approach: a product that measures the number of bgp received prefixes from a certain peer. Do you know of such product that is readily available and does not require ssh sessions to the routers and parsing the outputs? I am trying to find a solution that does not require much scripting or customization. Many thanks. Regards Mihai

9 8

RE: home router battery backup
by Shawn L 13 Jan '22

13 Jan '22

In $dayjob I work for a telco that deploys fiber to the home. If we are providing voice services over fiber a battery backup is installed (we maintain) that powers the customer's phone in the event of a power outage. It does not power their router, etc. 99% of the customers do not install a UPS for their router, etc. We try to explain that to customers, but we still get calls that they can't get on the Internet when their power is out. -----Original Message----- From: "Scott T Anderson via NANOG" <nanog(a)nanog.org> Sent: Wednesday, January 12, 2022 12:35pm To: "nanog(a)nanog.org" <nanog(a)nanog.org> Subject: home router battery backup Hi NANOG mailing list, I am a graduate student, currently conducting research on how power outages affect home Internet users. I know that the FCC has a regulation since 2015 (47 CFR Section 9.20) requiring ISPs to provide an option to voice customers to purchase a battery backup for emergency voice services during power outages. As this is only an option and only applies to customers who subscribe to voice services, I was wondering if anyone had any insights on the prevalence of battery backup for home modem/routers? I.e., what percentage of home users actually install a battery backup in their home modem/router or use an external UPS? Thanks. Scott Reference for 47 CFR Section 9.20: [ https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-9/subpart… ]( https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-9/subpart… )

7 10

"Hackathon" Solves Real-World Tech Issue + Committee Nominations + More
by Nanog News 13 Jan '22

13 Jan '22

*“Hackathon” Solves Real-World Tech Issue* Code Developed during NANOG Hackathon Goes Live Hackathons are an essential part of NANOG conferences. They are designed as a “fail forward” space where mistakes can be made as learning, having fun + building community is the prime objective. And sometimes this perfect cocktail of sophisticated fun leads to solving real-world technical issues. The work done at the NANOG 83 Hackathon improved the PeeringDB Simple Search and resolved a vital search issue. Thus, allowing PeeringDB (a freely available, user-maintained, database of networks, and a go-to location for interconnection data) to provide more relevant search results for the end-user. The developed code during the Hackathon, officially went live early Wednesday morning (Jan. 12). NANOG had the opportunity to catch up with PeeringDB product manager Leo Vegoda to learn more. *READ MORE <https://www.nanog.org/stories/hackathon-solves-real-world-tech-issue/>* *Now Accepting Committee Nominations* The 2022 Committee Nominations are now open and run through Tuesday, Feb. 15, 2022. Reminder, only NANOG members in good standing are allowed to serve on a NANOG committee. We are currently seeking volunteers for the Program Committee. **If you are not a member and wish to participate in the nomination process, your membership must be received by 9:00 p.m. PST on Tuesday, Feb. 15, 2022.** Click here to review the nomination process and volunteer for a committee! *COMMITTEE NOMINATIONS <https://www.nanog.org/members/elections/committee-nomination-process/>* *NANOG 84 Sponsorships Still Available * NANOG is, and always has been, dedicated to the people who make up our community. Our in-person conferences draw up to 1,500 individuals in multiple facets of network engineering, operations, and architecture, who gather with us in major cities across North America. As a sponsor of NANOG, you’ll help us in our mission to continue cultivating and strengthening our community of networking professionals. *SPONSORSHIP NOMINATIONS <https://www.nanog.org/events/sponsorship/sponsorship-opportunities/>*

1 0

home router battery backup
by james.cutler＠consultant.com 13 Jan '22

13 Jan '22

> On Jan 12, 2022, at 5:11 PM, Scott T Anderson via NANOG <nanog(a)nanog.org <mailto:nanog@nanog.org>> wrote: > > For those individuals with backup battery power for their modem/router, do they maintain Internet access throughout a power outage (as long as their backup power solution works)? I.e., does the rest of the ISP network maintain service throughout a power outage? The answer is, “It depends.” Plymouth in Michigan recently had a substation fire that took out a large fraction of the city. Restoration of the substation was a lengthy process as mobile transformers and the like were required. My Comcast connection was only down for a short time until some generators were dispatched to some pole-mounted equipment within the city. Since my local power comes from a different substation, the brief Comcast outage was the only noticeable event. I frequently hear the UPS beep for short interruptions, confirming that the battery is still strong. My original UPS was installed to ride through momentary outages and to inhibit spikes since spikes and arbitrary power shutdowns can cause damage to both data and equipment. My cable modem, router, network hub, several computers and monitors, and task lighting are all protected from outages for a decent interval followed by a spike-free shutdown. The latter is important, especially as compared to the transients occurring as trees fall on power lines. The 2003 midwest blackout was days long. I helped a friend wire his well pump to a portable generator so one could “flush”. I then grabbed my laptop and took refuge up north outside the outage area. At that time, WFH had long been part of my vocabulary.

1 0

DNS-OARC 37 Call for Presentations
by John Todd 12 Jan '22

12 Jan '22

OARC 37 will be a online/hybrid meeting on February 17th and 18th, 2022 starting at 16:00 UTC (10:00 CST). The onsite part of the meeting will be held in Austin, Texas. 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: - Operations: Any operational gotchas, lessons learned from an outage, details/reasons for a recent outage (how to improve TTR, tooling). - Deployment: Managing DNS changes and propagation, release process, change management. - Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. - Scaling: Managing service capacity, failovers, disaster recovery. As it is an online/hybrid workshop, we'd like to encourage brevity; presentations should not be longer than 20 minutes (with additional time for questions). **Workshop Milestones:** * 27 December 2021 - Submissions open via Indico * 10 January 2022 - Deadline for submission (23:59 UTC) * 11 January 2022 - Initial Contribution list published * 18 January 2022 - Full agenda published * 3 February 2022 - Deadline for slideset submission and Rehearsal * 17 & 18 February 2022 - OARC 37 Workshop The Registration page and details for presentation submission are published at: https://www.dns-oarc.net/oarc37 DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented 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 37: * 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 3rd February 2022. 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> John Todd, 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.) -- John Todd - jtodd(a)quad9.net General Manager - Quad9 Recursive Resolver

1 1

Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN73 Community Forum
by Jacques Latour 12 Jan '22

12 Jan '22

Hi all, Happy new year! 8 weeks left before the next virtual ICANN DNSSEC & Security workshop. Let us know if you are interested to present. Jacques Call for Participation -- ICANN DNSSEC and Security Workshop for ICANN73 Community Forum In cooperation with the ICANN Security and Stability Advisory Committee (SSAC), we are planning a DNSSEC and Security Workshop for the ICANN73 Community Forum being held virtually from 05-10 March 2022 in the Atlantic Standard Time Zone (UTC -4). This workshop date will be determined once ICANN creates a block schedule for us to follow; then we will be able to request a day and time. The DNSSEC and Security Workshop has been a part of ICANN meetings for several years and has provided a forum for both experienced and new people to meet, present and discuss current and future DNSSEC deployments. For reference, the most recent session was held at the ICANN72 Annual General Meeting on Wednesday 27 October 2021. The presentations and transcripts are available at https://72.schedule.icann.org/meetings/M24SJN375N2rcupnS, https://72.schedule.icann.org/meetings/NQMcvSwdLbpdGPaz6, and https://72.schedule.icann.org/meetings/9g4P3ceRA8FGS34Ei. The DNSSEC Workshop Program Committee is developing a program. Proposals will be considered for the following topic areas and included if space permits. In addition, we welcome suggestions for additional topics either for inclusion in the ICANN72 workshop, or for consideration for future workshops. 1. Global DNSSEC Activities Panel For this panel, we are seeking participation from those who have been involved in DNSSEC deployment as well as from those who have not deployed DNSSEC but who have a keen interest in the challenges and benefits of deployment, including Root Key Signing Key (KSK) Rollover activities and plans. 2. DNSSEC Best Practice Now that DNSSEC has become an operational norm for many registries, registrars, and ISPs, what have we learned about how we manage DNSSEC? * Do you still submit/accept DS records with Digest Type 1? * What is the best practice around key roll-overs? * What about Algorithm roll-overs? * Do you use and support DNSKEY Algorithms 13-16? * How often do you review your disaster recovery procedures? * Is there operational familiarity within your customer support teams? * What operational statistics have we gathered about DNSSEC? * Are there experiences being documented in the form of best practices, or something similar, for transfer of signed zones? Activities and issues related to DNSSEC in the DNS Root Zone are also desired. 3. DNSSEC Deployment Challenges The program committee is seeking input from those that are interested in implementation of DNSSEC but have general or particular concerns with DNSSEC. In particular, we are seeking input from individuals that would be willing to participate in a panel that would discuss questions of the following nature: * Are there any policies directly or indirectly impeding your DNSSEC deployment? (RRR model, CDS/CDNSKEY automation) * What are your most significant concerns with DNSSEC, e.g., complexity, training, implementation, operation or something else? * What do you expect DNSSEC to do for you and what doesn't it do? * What do you see as the most important trade-offs with respect to doing or not doing DNSSEC? 4. Security Panel The program committee is looking for presentations on DNS, DNSSEC and Routing topics that could impact the security and/or stability of the internet. We are looking for presentations that cover implementation issues, challenges, opportunities and best practices for: * Emerging threats that could impact the security and/or stability of the internet * DoH and DoT * RPKI (Resource Public Key Infrastructure) * BGP routing & secure implementations * MANRS ( Mutually Agreed Norms for Routing Security) * Browser security – DNS, DNSSEC, DoH * EMAIL & DNS related security – DMARC, DKIM, TLSA, etc… If you are interested in participating, please send a brief (1-2 sentence) description of your proposed presentation to dnssec-security-workshop(a)icann.org<mailto:dnssec-security-workshop@icann.org> by COB Friday, January 21 2022 Thank you, Kathy and Andrew On behalf of the DNSSEC Workshop Program Committee: Steve Crocker, Shinkuro Mark Elkins, DNS/ZACR Jacques Latour, .CA Russ Mundy, Parsons Ondrej Filip, CZ.NIC Yoshiro Yoneya, JPRS Fred Baker, ISC Dan York, Internet Society

1 0