- Test - lists.nanog.org

Fwd: IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations)
by Fernando Gont 12 Feb '21

12 Feb '21

Folks, FYI. The intent is to discuss this on the IETF v6ops wg list (https://www.ietf.org/mailman/listinfo/v6ops) But comments will be appreciated, regardless of the specific channel (whether on this list, off-list, etc.) Thanks! Regards, Fernando -------- Forwarded Message -------- Subject: IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations) Date: Fri, 12 Feb 2021 18:50:48 -0300 From: Fernando Gont <fgont(a)si6networks.com> To: IPv6 Operations <v6ops(a)ietf.org> Folks, In the aforementioned document (https://tools.ietf.org/html/draft-gont-v6ops-ipv6-addressing-considerations) we have tried to do at least three things: 1) Look at what we have and try to discuss things from an architectural perspective 2) Analyze the implications of #1 (whether operations, security, privacy, etc.) 3) Find missing gaps that currently prevent us from fully leveraging IPv6 addressing. Part of what we've found as doing #3 above is that: * There are shortcomings associated with the current APIs that prevent better usage of IPv6 addresses * Multi-router/multi-prefix routing seems to be broken. RFC8028 would be a fundamental starting point in the right direction... but I believe there's more to do in this area. In that light, we'd like to hear further comments on our document. And, in particular, we're interested to hear if : * there are any operational implications of IPv6 addressing that we have missed, or, * there's anything related to IPv6 addressing that you consider to be currently broken or problematic, that is missing in our I-D. Thoughts on the current contents of the I-D are, of course, also very welcome! Thanks, -- Fernando Gont SI6 Networks e-mail: fgont(a)si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

1 0

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

12 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 13 Feb, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 845861 Prefixes after maximum aggregation (per Origin AS): 322196 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 402923 Total ASes present in the Internet Routing Table: 70526 Prefixes per ASN: 11.99 Origin-only ASes present in the Internet Routing Table: 60682 Origin ASes announcing only one prefix: 25080 Transit ASes present in the Internet Routing Table: 9844 Transit-only ASes present in the Internet Routing Table: 295 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: 927 Number of instances of unregistered ASNs: 933 Number of 32-bit ASNs allocated by the RIRs: 35042 Number of 32-bit ASNs visible in the Routing Table: 29074 Prefixes from 32-bit ASNs in the Routing Table: 135830 Number of bogon 32-bit ASNs visible in the Routing Table: 18 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 560 Number of addresses announced to Internet: 2910555264 Equivalent to 173 /8s, 123 /16s and 140 /24s Percentage of available address space announced: 78.6 Percentage of allocated address space announced: 78.6 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: 288838 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 221583 Total APNIC prefixes after maximum aggregation: 65428 APNIC Deaggregation factor: 3.39 Prefixes being announced from the APNIC address blocks: 217412 Unique aggregates announced from the APNIC address blocks: 88209 APNIC Region origin ASes present in the Internet Routing Table: 11268 APNIC Prefixes per ASN: 19.29 APNIC Region origin ASes announcing only one prefix: 3225 APNIC Region transit ASes present in the Internet Routing Table: 1595 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 30 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6419 Number of APNIC addresses announced to Internet: 770448384 Equivalent to 45 /8s, 236 /16s and 28 /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: 243710 Total ARIN prefixes after maximum aggregation: 112158 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 244226 Unique aggregates announced from the ARIN address blocks: 116434 ARIN Region origin ASes present in the Internet Routing Table: 18727 ARIN Prefixes per ASN: 13.04 ARIN Region origin ASes announcing only one prefix: 6808 ARIN Region transit ASes present in the Internet Routing Table: 1919 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: 3705 Number of ARIN addresses announced to Internet: 1147787520 Equivalent to 68 /8s, 105 /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: 242051 Total RIPE prefixes after maximum aggregation: 112658 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 238056 Unique aggregates announced from the RIPE address blocks: 139612 RIPE Region origin ASes present in the Internet Routing Table: 27736 RIPE Prefixes per ASN: 8.58 RIPE Region origin ASes announcing only one prefix: 11914 RIPE Region transit ASes present in the Internet Routing Table: 3891 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9927 Number of RIPE addresses announced to Internet: 710304384 Equivalent to 42 /8s, 86 /16s and 98 /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: 112427 Total LACNIC prefixes after maximum aggregation: 26347 LACNIC Deaggregation factor: 4.27 Prefixes being announced from the LACNIC address blocks: 113586 Unique aggregates announced from the LACNIC address blocks: 48143 LACNIC Region origin ASes present in the Internet Routing Table: 10648 LACNIC Prefixes per ASN: 10.67 LACNIC Region origin ASes announcing only one prefix: 2633 LACNIC Region transit ASes present in the Internet Routing Table: 2004 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: 8251 Number of LACNIC addresses announced to Internet: 173827328 Equivalent to 10 /8s, 92 /16s and 101 /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: 25162 Total AfriNIC prefixes after maximum aggregation: 4873 AfriNIC Deaggregation factor: 5.16 Prefixes being announced from the AfriNIC address blocks: 32021 Unique aggregates announced from the AfriNIC address blocks: 10009 AfriNIC Region origin ASes present in the Internet Routing Table: 1448 AfriNIC Prefixes per ASN: 22.11 AfriNIC Region origin ASes announcing only one prefix: 500 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: 31 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 772 Number of AfriNIC addresses announced to Internet: 107762688 Equivalent to 6 /8s, 108 /16s and 84 /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 5727 781 667 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4750 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3548 1330 19 VIETEL-AS-AP Viettel Group, VN 7713 3229 935 528 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 3218 9045 60 CMNET-GD Guangdong Mobile Communication 45899 2887 1896 55 VNPT-AS-VN VNPT Corp, VN 4766 2448 11105 569 KIXS-AS-KR Korea Telecom, KR 9498 2304 482 230 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 4827 9094 2170 AMAZON-02, US 11492 4742 315 738 CABLEONE, US 7155 4038 264 32 VIASAT-SP-BACKBONE, US 22773 3863 2992 247 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3329 1317 72 SHAW, CA 16625 3281 1715 2334 AKAMAI-AS, US 209 2522 5058 503 CENTURYLINK-US-LEGACY-QWEST, US 30036 2505 370 89 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2352 3000 1642 FRONTIER-FRTR, US 5972 2187 437 773 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 8089 1086 3227 TTNET, TR 12479 6301 1700 146 UNI2-AS, ES 39891 3459 195 22 ALJAWWALSTC-AS, SA 20940 3440 3347 207 AKAMAI-ASN1, NL 8551 3247 379 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2877 2282 890 ROSTELECOM-AS, RU 9009 2350 237 1262 M247, GB 34984 2177 354 582 TELLCOM-AS, TR 13188 1611 100 23 TRIOLAN, UA 58224 1512 870 561 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 8238 3405 595 Uninet S.A. de C.V., MX 10620 3400 526 612 Telmex Colombia S.A., CO 11830 2561 369 63 Instituto Costarricense de Electricidad 13999 1629 433 417 Mega Cable, S.A. de C.V., MX 6503 1441 311 475 Axtel, S.A.B. de C.V., MX 7303 1439 913 262 Telecom Argentina S.A., AR 28573 1389 2261 221 CLARO S.A., BR 6147 1162 379 39 Telefonica del Peru S.A.A., PE 3816 1156 574 143 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 987 210 410 Techtel LMDS Comunicaciones Interactiva Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1581 393 22 LINKdotNET-AS, EG 24835 1294 486 27 RAYA-AS, EG 36992 1178 1537 169 ETISALAT-MISR, EG 36903 978 510 101 MT-MPLS, MA 29571 702 68 11 ORANGE-COTE-IVOIRE, CI 6713 532 1863 34 IAM-AS, MA 36935 489 522 41 Vodafone-, EG 37342 486 32 1 MOVITEL, MZ 15399 483 46 18 WANANCHI-, KE 23889 454 232 16 MauritiusTelecom, MU 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 8238 3405 595 Uninet S.A. de C.V., MX 47331 8089 1086 3227 TTNET, TR 12479 6301 1700 146 UNI2-AS, ES 7545 5727 781 667 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 4827 9094 2170 AMAZON-02, US 4538 4750 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4742 315 738 CABLEONE, US 7155 4038 264 32 VIASAT-SP-BACKBONE, US 22773 3863 2992 247 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3548 1330 19 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 6301 6155 UNI2-AS, ES 7545 5727 5060 TPG-INTERNET-AP TPG Telecom Limited, AU 47331 8089 4862 TTNET, TR 4538 4750 4676 ERX-CERNET-BKB China Education and Research Net 7155 4038 4006 VIASAT-SP-BACKBONE, US 11492 4742 4004 CABLEONE, US 22773 3863 3616 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3548 3529 VIETEL-AS-AP Viettel Group, VN 39891 3459 3437 ALJAWWALSTC-AS, SA 6327 3329 3257 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 393489 UNALLOCATED 12.7.109.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:40 /11:102 /12:293 /13:580 /14:1182 /15:1932 /16:13500 /17:8308 /18:13796 /19:25618 /20:41725 /21:50907 /22:105083 /23:89560 /24:491766 /25:1446 /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 7234 8089 TTNET, TR 12479 5268 6301 UNI2-AS, ES 11492 3797 4742 CABLEONE, US 6327 3134 3329 SHAW, CA 7155 3126 4038 VIASAT-SP-BACKBONE, US 22773 2924 3863 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2840 8238 Uninet S.A. de C.V., MX 39891 2801 3459 ALJAWWALSTC-AS, SA 8551 2712 3247 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2237 2505 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:1880 2:1171 3:94 4:19 5:3598 6:65 7:5 8:1487 9:1 11:36 12:1760 13:358 14:2424 15:76 16:15 17:308 18:94 20:117 22:188 23:4344 24:2377 25:2 27:2383 31:2202 32:112 34:2 35:39 36:1141 37:3630 38:2049 39:485 40:150 41:3867 42:896 43:2100 44:233 45:14928 46:3624 47:320 49:1612 50:1708 51:102 52:1205 54:217 55:775 56:6 57:57 58:1692 59:1164 60:824 61:2364 62:2220 63:1983 64:5251 65:2408 66:5175 67:2919 68:1173 69:4075 70:1399 71:687 72:3240 74:2584 75:1476 76:693 77:2025 78:3730 79:2489 80:1806 81:1646 82:1303 83:1120 84:1258 85:3291 86:653 87:1805 88:2836 89:3049 90:402 91:7260 92:1644 93:2531 94:2949 95:4456 96:1224 97:346 98:978 99:978 100:91 101:1054 102:1279 103:25346 104:3657 105:418 106:723 107:2212 108:675 109:3839 110:2001 111:2384 112:1770 113:1681 114:1440 115:1869 116:1890 117:2193 118:2312 119:1934 120:946 121:1084 122:2283 123:2179 124:1633 125:2144 128:1323 129:1164 130:803 131:2019 132:760 133:320 134:1555 135:288 136:721 137:897 138:2289 139:1163 140:743 141:1167 142:1059 143:1239 144:1218 145:326 146:1395 147:1238 148:2210 149:1267 150:749 151:1199 152:1544 153:385 154:2184 155:1316 156:1474 157:1158 158:928 159:2050 160:2065 161:1103 162:3236 163:965 164:1426 165:1302 166:613 167:1770 168:3547 169:651 170:4343 171:755 172:2066 173:2950 174:979 175:1065 176:2965 177:4330 178:2868 179:1886 180:2276 181:2621 182:3191 183:1705 184:2459 185:17890 186:4170 187:3083 188:3314 189:2752 190:9069 191:1470 192:10657 193:7926 194:6490 195:4655 196:2963 197:2343 198:6028 199:5982 200:7396 201:5281 202:10496 203:10113 204:4645 205:3259 206:3428 207:3322 208:3995 209:4615 210:4233 211:2177 212:3626 213:3289 214:1213 215:61 216:6171 217:2518 218:1022 219:682 220:2069 221:944 222:983 223:1743 End of report

1 0

Anyone with experience working the Oracle Cloud and IPSec connections?
by Joseph Jenkins 12 Feb '21

12 Feb '21

We are in the process of setting up connectivity to the Oracle Cloud over ipsec connections. I have it setup with 3 /16 subnets to route back to our on premise network. The tunnel comes up when interesting traffic comes from one of the subnets, however when traffic is generated from another subnet the first subnet stops getting return traffic from OCI. Anyone with any experience that can shed some light on this?

1 0

Re: DoD IP Space
by Willy Manga 12 Feb '21

12 Feb '21

Hi, On 11/02/2021 13:00, nanog-request(a)nanog.org wrote: > Date: Wed, 10 Feb 2021 09:50:56 -0800 > From: Doug Barton <dougb(a)dougbarton.us> >[...] On 2/10/21 5:56 AM, Ca By wrote> >> The 3 cellular networks in the usa, 100m subs each, use ipv6 to uniquely >> address customers. And in the case of ims (telephony on a celluar), it >> is ipv6-only, afaik. > So that answers the question of how to scale networks past what can be > done with 1918 space. Although why the phones would need to talk > directly to each other, I can't imagine. - P2P applications? - (because I'm tethering,) enable customers to share a service to other people without relying to (many) external parties? (actually, that was the purpose of the Internet since the beginning if I'm right) - ... > I also reject the premise that any org, no matter how large, needs to > uniquely number every endpoint. When I was doing IPAM for a living, not > allowing the workstations in Tucson to talk to the printers in Singapore > was considered a feature. I even had one customer who wanted the > printers to all have the same (1918) IP address in every office because > they had a lot of sales people who traveled between offices who couldn't > handle reconfiguring every time they visited a new location. I thought > it was a little too precious personally, but the customer is always > right. :) Here comes the DNS imho if it was accepted by the customer. Same result, better management and flexibility... > Sure, it's easier to give every endpoint a unique address, but it is not > a requirement, and probably isn't even a good idea. Spend a little time > designing your network so that the things that need to talk to each > other can, and the things that don't have to, can't. I did a lot of > large multinational corporations using this type of design and never > even came close to exhausting 1918 space. Here comes your firewall rules and all your ACL ... easier with IPv6 imho -- Willy Manga @ongolaboy https://ongola.blogspot.com/

1 0

RIPE Atlas probe available on SpaceX Starlink beta terminal
by Eric Kuhnke 12 Feb '21

12 Feb '21

https://atlas.ripe.net/probes/1001821/ I am running what I believe to be the first RIPE Atlas probe on a Starlink beta test terminal. When searching the index of public probes I did not find any other probes with "spacex" or "starlink" in the descriptions. This probe is at present not contained within AS14593 (Starlink). All beta test terminals that I am aware of right now, including my own, are in cgnat IP space and meet the public Internet via AS36492 (Google). This particular terminal is topologically closest to things at major IX points in the metro Seattle area. The absolute lowest ping time I've seen to something at the Westin is 15.85ms, with averages more often between 21-32ms. The site where this is installed will occasionally conduct other, non Atlas related tests which result in full saturation of the upstream or downstream connection, simulating a number of different types of real world use cases. This means that occasionally the RTT ping to things in Seattle may rise as high as 150ms, and artificially-induced packet loss will be introduced into the connection. Please feel free to contact me off-list with any questions.

1 0

2021.02.10 community meeting unofficial notes
by Matthew Petach 11 Feb '21

11 Feb '21

It was mentioned in the chat this morning that there was no link to slides or anything on the agenda for the community meeting that happened this morning, so I offered to share the notes I was jotting down during the meeting, to give an idea of what was covered for those in timelines not as friendly to the meeting time, or to those with conflicts. ^_^; Thanks so much to the staff, Elizabeth, Steve, and Ed for the great presentations this morning! Matt 2021.02.10 NANOG81 community meeting Speaker Edward McNair, NANOG Steve Feldman, ViacomCBS Elizabeth Culley, Comcast NOTES: Michael Voity kicks off the meeting at 0901 hours Pacific time to go over the agenda for the day. special announcements: fill out surveys! The PC reads all of them! And if you're a lucky winner, you'll get a $100 gift card! Looking for presentation proposals for NANOG82! check out sponsors at virtual expo both; sponsors have stepped up to the challenge with interesting offerings. first talk today is hosted by edward mcnair, with Elizabeth Culley and Steve Feldman. Ed Mcnair has been with nanog since 2005, and has been ED since 2018; Steve has been contributing to nanog since its inception since 1994, and has been involved with PC for the last 20 years. Elizabeth Culley is peering coordinator with comcast, and is completing her first year on the PC; this is her first time presenting to NANOG. welcome edward, steve and elizabeth, it's great to have you here. Edward takes a few moments to give some updates on the organization; strategic plan narrowed to 3 areas; education, meeting experience, online collaboration, another piece built out is the strategic timeline; encompasses from NANOG73 to NANOG 85. purpose is to see what we are aiming to achieve and what we will put forward. we always like to hear your comments, there is a feedback button that goes to NANOG staff, and he reads them all. Take a moment to honor the nanog staff; counting himself, there are 6.5 staff members, as Claudia works with them halftime. Claudia, Leigh, Valerie, Shawn, Darrieux (Dee), and Brandi all work very hard to ensure that we can have a quality program. Our 2020 annual report will be coming out soon; to give a linear record of what we've accompished over the course of 2020; we'll do polls at the end of the section; log into the polls at pollEV.com/nanog Over to Steve feldman; at end of every NANOG, there is a Program commitee get together; after SF, decided to have retreat in 2020; planned to do it in Boston or Seattle; but then things changed, and they couldn't get together in person; so they had a virtual retreat, 2 days, dec 16 2020, and jan 13 2021 to go over various items. some of the items covered: PC structure new member onboarding PC handbook update mentorship leadership review roles, responsibliities need to document them better subcommittees are we optiimizing our effort? some don't seem to do much. will add some new ones. diversity of skills and perspectives need to get people who have different industry perspectives. other topics at virutal retreat meeting format how to do hybrid meetings we optimize time for training and tutorial we focus on human interaction; need to accomodate people in different timezones. talk solicitation and selection attracting new speakers expanding the audience standardize voting content review PC's strategic vision. Liz, chairing our data analysis effort; for past 20 years, we've been building a repository of tracks, tutorials, keynote speeches, lightning talks; we have a long history of hosting the voices of those building the internet. what comes up in NANOG is often in the leading edge of technology trends; this effort will be to mine the repository, to help us keep up with the onslaught of demand. cataloging NANOG; we are recording the details of every presentation, tutoria and keynote; tagging each record with relevant metadata provide intuitive web page of popular topics porovide data to potential speakers on history of any topic which topics are asked for most often which videos are most viewed. use surveys and data on view counts to project topics that will be of most interest. looking at last 5 years of NANOG data; how many times this topic 44 topics on DNS 40 requests for automation, but 26 talks on automation Geoff Huston comes up a lot look at how many times talks are viewed on youtube; 27K views of 44 DNS talks on youtube; 26 automation videos got 77K views. A lot of people would say they're experts in a field; how can they talk about their job when it's 100% proprietary, and they can't talk about their day job; take a look at the request counts, how many presentations we get, so even doing a 101 intro class is a great way to get your feet wet. 66% of presentations are on top 20 subjects. 115 categoreis in presentations and requests match the survey requests. if we watched all the talks and presentations, 8 hours a day, it woud take 8 weeks to watch the all 550 prsentations, 357 speakers, 218 organizations. 90% of speakers present 1 or 2 times. looking forward; want to give huge thanks to Jeff Bartig, Anna Valsami, and Valerie Wittkop for doing the work to move it forwrd; and thank you to PC for creating the new data analysis committee, and providing the sunlight and support to make this a reality. we have 1300 recorded and tagged; we expect 2100 items; easy part is done, now we're getting into the hard part. Jeff Bartig wrote scripts to download from youtube; there's a lot of stuff in agendas that have to be gone through one at a time. in midst of the project; would love to hear from you; what else would you like to see? now, for polls--what topic would you like to see? and you can always put feedback in the web feedback form. Seems that Geoff Huston, IPv6, Automation, Cloud, Virtualization are hot topics! are you planning to attend minnapolis nanog82 in person? most are undecided or will attend virtually. most seem to lean to attending virtually. likewise for toronto, nanog83 it looks like most people are waiting for vaccines to be available before they will come. So far, most have not yet taken the vaccine, but also most are planning to take the vaccine once they are able to. Over to you, Michael; Thank you to Edward, Steve and Elizabeth for their time. Network Automation treasure hunt without a map is up next.

4 4

DNSSEC question
by Randy Carpenter 10 Feb '21

10 Feb '21

Any DNSSEC experts that could help with a question about a specific domain? Off-list please. thanks, -Randy

1 0

cogent issues in texas?
by aaron1＠gvtc.com 09 Feb '21

09 Feb '21

Anyone else having cogent internet issues in south central Texas or the region? I called Cogent and they mentioned a few spans down between el paso, fort worth, san Antonio and Houston My 100 gig link to them took a lot of loss. I had to bring down bgp for preferring other sp Aaron aaron1(a)gvtc.com

2 1

Problems with newish IP block assignment issues from ARIN
by Justin Wilson (Lists) 09 Feb '21

09 Feb '21

Folks, Have a gremlin we have been chasing around for several months now and it’s becoming a major issue as we are getting tighter on IPV4 and needing to give some provider assigned space back. In June we received a /22 from ARIN. As is my workflow I started announcing it but waited a month while I checked out the geolocation databases for correct info, did testing ,etc. All this time our test accounts could browse web-sites, etc. We put one of the pools into production and things ran good for awhile. Then we started getting the occasional web-site was not working. After several of these we started assigning the customer an IP out of one of our other ARIN blocks and the web-site would be fine and reachable. The issue seems to reside just on this /22. We have other blocks from ARIN and they are just fine. We can assign an IP out of this new block and can’t reach certain web-sites. We turn around and assign out of another block and web-site works just fine. We have two upstreams and an IX on this network. We have tried withdrawing the route on this particular /22 and isolating to one upstream alone and the problems still persist. Many of the web-sites in question are government (both state and local), online universities, and the occasional local news station. They are diverse enough to not be traced down to a common point, except the IP block. We announce the IP block via BGP the same exact way we announce the other blocks. Traceroutes show the path going the same way no matter what IP block the customer has. It acts like the IP block was blacklisted at some point and got on some bad lists but I don’t want ti limit myself to that theory. I have opened up a ticket with ARIN asking for any guidance. Has anyone ran into this with new space assigned? Any tools, sites, etc. I can use to do further troubleshooting. The IP block does not appear to have any blacklisted IPs according to MX toolbox, and some others. The block in question is 134.195.44.0/22. It has been RPKI certified and has IRR entries. Thanks in advance Justin Wilson j2sw(a)mtin.net — https://j2sw.com - All things jsw (AS209109) https://blog.j2sw.com - Podcast and Blog

8 9

Retalitory DDoS
by Mike Hammett 09 Feb '21

09 Feb '21

Is there a club for people that have been DDoSed? If so, count me in. This one was directed at me (as opposed to one of my customers) because I got an e-mail explaining why I was getting DDoSed. Is that aspect common? There were also some racial and sexual accusations that were made that clearly aren't true and just speak to the intelligence of people like this. Is it safe to assume that they completely anonymized the email they sent to me? Is there anyone I should be reporting this to? I thought my site was running in Cloudflare, but my individual server was still attacked, so I gotta figure out where I screwed that up. https://www.dropbox.com/s/rrrx90jvy09h26s/ICS%20DDoS.png?dl=0 ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

5 10