- Test - lists.nanog.org

jon postel
by Randy Bush 07 Nov '22

07 Nov '22

it's been 24 years, and we still live in his shadow and stand on his shoulders. we try not to stand on his toes. randy

24 36

Offline contact for MS Windows network stack dev? (Win10 IPv6 bug Q.)
by Nathan Anderson 07 Nov '22

07 Nov '22

Not sure this is the best place to ask, but I'm not sure where else to go at this point... I'm trying to find somebody on the Windows development team that might be able & willing to help me track down some info on a bizarre IPv6 bug I've been chasing in Win10 & its related fix. I can confirm the bug in question was silently fixed somewhere in between 10.0.18362.657 and 10.0.18362.693 and that it seems to be within the tcpip.sys component, but the release notes for KB4535996 make zero mention of it. The fix has also seemingly never been backported to LTSC 2019. Essentially the problem is that, in a dual-stack environment, if a DNS lookup returns both an A and an AAAA record, Windows will prefer to make a connection to the target host via v4, claiming that it chose to do so because it is "Prefer[ring] [the] Aoac Interface", as if the given network interface only supports Connected/Modern Standby for IPv4 and not v6. Despite this, with the exact same drivers on the exact same host with the exact same hardware & network interfaces connected to the exact same LAN, the seemingly-fixed tcpip.sys no longer behaves this way. (It actually even works on "buggy" tcpip.sys after a fresh reboot, but only for some undefined amount of time before it reverts to this behavior. My theory is the codepath that is causing this is only *supposed* to be followed while the PC is *actually* asleep & not during normal operation, but some bit in memory is getting flipped when some event occurs, and the logic that is taking this particular bit into account is faulty.) If anybody can put me in touch with somebody who can pull a changelog of tcpip.sys between those two versions, I'd really appreciate it! I'm just trying to better understand the exact nature of the bug & the fix, since a NetTrace would implicate buggy network interface drivers, but that clearly can't be the whole story. And I'd like to figure out if a workaround is available for still-supported Windows versions that do not incorporate the actual fix (e.g., some registry entry that will make Windows ignore the freaking AOAC support reported by the network interface driver...the NetTrace entry implies Windows is following RFC 6724 and that it is considering the IPv6 destination to be "unreachable" [merely because of lack of AOAC support in the driver for IPv6?!], which is clearly not the case). Thanks! -- Nathan Anderson First Step Internet, LLC nathana(a)fsr.com

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 04 Nov '22

04 Nov '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 05 Nov, 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: 914187 Prefixes after maximum aggregation (per Origin AS): 345210 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 441304 Total ASes present in the Internet Routing Table: 73782 Prefixes per ASN: 12.39 Origin-only ASes present in the Internet Routing Table: 63404 Origin ASes announcing only one prefix: 26064 Transit ASes present in the Internet Routing Table: 10378 Transit-only ASes present in the Internet Routing Table: 408 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: 1006 Number of instances of unregistered ASNs: 1008 Number of 32-bit ASNs allocated by the RIRs: 40572 Number of 32-bit ASNs visible in the Routing Table: 33622 Prefixes from 32-bit ASNs in the Routing Table: 162808 Number of bogon 32-bit ASNs visible in the Routing Table: 12 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 510 Number of addresses announced to Internet: 3064630528 Equivalent to 182 /8s, 170 /16s and 141 /24s Percentage of available address space announced: 82.8 Percentage of allocated address space announced: 82.8 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: 310253 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 238910 Total APNIC prefixes after maximum aggregation: 68007 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 233889 Unique aggregates announced from the APNIC address blocks: 96892 APNIC Region origin ASes present in the Internet Routing Table: 13077 APNIC Prefixes per ASN: 17.89 APNIC Region origin ASes announcing only one prefix: 3778 APNIC Region transit ASes present in the Internet Routing Table: 1756 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 33 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8324 Number of APNIC addresses announced to Internet: 773861504 Equivalent to 46 /8s, 32 /16s and 48 /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: 267032 Total ARIN prefixes after maximum aggregation: 121841 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 268396 Unique aggregates announced from the ARIN address blocks: 129002 ARIN Region origin ASes present in the Internet Routing Table: 19070 ARIN Prefixes per ASN: 14.07 ARIN Region origin ASes announcing only one prefix: 6977 ARIN Region transit ASes present in the Internet Routing Table: 1928 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4667 Number of ARIN addresses announced to Internet: 1290101248 Equivalent to 76 /8s, 229 /16s and 98 /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: 261799 Total RIPE prefixes after maximum aggregation: 120887 RIPE Deaggregation factor: 2.17 Prefixes being announced from the RIPE address blocks: 258585 Unique aggregates announced from the RIPE address blocks: 154650 RIPE Region origin ASes present in the Internet Routing Table: 28150 RIPE Prefixes per ASN: 9.19 RIPE Region origin ASes announcing only one prefix: 12004 RIPE Region transit ASes present in the Internet Routing Table: 3954 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 38 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10852 Number of RIPE addresses announced to Internet: 716490624 Equivalent to 42 /8s, 180 /16s and 199 /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: 116846 Total LACNIC prefixes after maximum aggregation: 28114 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 116298 Unique aggregates announced from the LACNIC address blocks: 48449 LACNIC Region origin ASes present in the Internet Routing Table: 10985 LACNIC Prefixes per ASN: 10.59 LACNIC Region origin ASes announcing only one prefix: 2708 LACNIC Region transit ASes present in the Internet Routing Table: 2229 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8750 Number of LACNIC addresses announced to Internet: 175917056 Equivalent to 10 /8s, 124 /16s and 72 /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: 28594 Total AfriNIC prefixes after maximum aggregation: 5604 AfriNIC Deaggregation factor: 5.10 Prefixes being announced from the AfriNIC address blocks: 36509 Unique aggregates announced from the AfriNIC address blocks: 11890 AfriNIC Region origin ASes present in the Internet Routing Table: 1702 AfriNIC Prefixes per ASN: 21.45 AfriNIC Region origin ASes announcing only one prefix: 597 AfriNIC Region transit ASes present in the Internet Routing Table: 332 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: 1029 Number of AfriNIC addresses announced to Internet: 107975168 Equivalent to 6 /8s, 111 /16s and 146 /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 9092 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5942 786 696 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4879 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3616 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3498 1043 62 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3397 1877 66 VNPT-AS-VN VNPT Corp, VN 4766 2531 11252 600 KIXS-AS-KR Korea Telecom, KR 9498 2498 499 237 BBIL-AP BHARTI Airtel Ltd., IN 24560 2259 850 411 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2180 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 7561 10612 2897 AMAZON-02, US 11492 4585 304 549 CABLEONE, US 7155 3898 265 32 VIASAT-SP-BACKBONE, US 22773 3759 3061 341 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3562 1864 2548 AKAMAI-AS, US 6327 3517 1320 63 SHAW, CA 749 3029 50727 2287 DNIC-AS-00749, US 7018 2609 24057 1569 ATT-INTERNET4, US 30036 2599 371 285 MEDIACOM-ENTERPRISE-BUSINESS, US 396982 2560 3480 351 GOOGLE-CLOUD-PLATFORM, 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 6920 1730 144 UNI2-AS, ES 9121 6841 1692 17 TTNET, TR 20940 4115 3400 183 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA 8551 3981 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2956 2290 913 ROSTELECOM-AS, RU 9009 2628 252 1351 M247, RO 6849 2331 339 20 UKRTELNET, UA 34984 2241 357 615 TELLCOM-AS, TR 47331 2078 323 1581 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 10785 3345 604 Uninet S.A. de C.V., MX 10620 3472 510 839 Telmex Colombia S.A., CO 11830 2300 369 64 Instituto Costarricense de Electricidad 13999 2099 341 544 Mega Cable, S.A. de C.V., MX 28573 1335 2328 261 Claro NXT Telecomunicacoes Ltda, BR 6503 1295 338 521 Axtel, S.A.B. de C.V., MX 3816 1286 722 153 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 1110 182 471 Techtel LMDS Comunicaciones Interactiva 6147 1083 369 22 Telefonica del Peru S.A.A., PE 26615 992 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 1575 393 21 LINKdotNET-AS, EG 24835 1545 521 31 RAYA-AS, EG 36992 1354 1520 270 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 992 68 32 ORANGE-COTE-IVOIRE, CI 36935 831 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 526 53 42 WANANCHI-, KE 37342 490 32 1 MOVITEL, MZ 23889 400 231 14 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 10785 3345 604 Uninet S.A. de C.V., MX 9808 9092 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7561 10612 2897 AMAZON-02, US 12479 6920 1730 144 UNI2-AS, ES 9121 6841 1692 17 TTNET, TR 7545 5942 786 696 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4879 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4585 304 549 CABLEONE, US 20940 4115 3400 183 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 9092 9042 CHINAMOBILE-CN China Mobile Communications Grou 9121 6841 6824 TTNET, TR 12479 6920 6776 UNI2-AS, ES 7545 5942 5246 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4879 4804 ERX-CERNET-BKB China Education and Research Net 16509 7561 4664 AMAZON-02, US 11492 4585 4036 CABLEONE, US 39891 4010 3963 ALJAWWALSTC-AS, SA 8551 3981 3943 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 20940 4115 3932 AKAMAI-ASN1, NL 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 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.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 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.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.181.240.0/24 Origin: 399613 UNASSIGNED 23.181.240.0/24 Transit: 11992 CENTENNIAL-, PR 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:100 /12:295 /13:588 /14:1198 /15:2047 /16:13533 /17:8355 /18:13983 /19:25166 /20:44387 /21:52270 /22:109998 /23:97774 /24:543619 /25:806 /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 5987 6841 TTNET, TR 12479 5925 6920 UNI2-AS, ES 8151 4738 10785 Uninet S.A. de C.V., MX 11492 3492 4585 CABLEONE, US 8551 3445 3981 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3325 3517 SHAW, CA 39891 3193 4010 ALJAWWALSTC-AS, SA 7155 2987 3898 VIASAT-SP-BACKBONE, US 22773 2780 3759 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2255 2599 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1907 2:1017 3:166 4:5 5:4013 6:117 7:5 8:1597 9:1 11:173 12:1619 13:350 14:2382 15:280 16:69 17:360 18:373 20:236 21:4 22:188 23:6002 24:2454 25:6 27:2703 29:19 31:2467 32:93 34:7 35:95 36:1794 37:4498 38:3750 39:770 40:144 41:3931 42:1183 43:2252 44:301 45:16308 46:4201 47:375 49:1720 50:1924 51:244 52:1496 54:398 55:846 56:8 57:78 58:1790 59:1163 60:1002 61:2409 62:2590 63:1958 64:5622 65:2324 66:4831 67:2995 68:1379 69:4146 70:1297 71:679 72:2998 74:2648 75:1474 76:600 77:2226 78:3961 79:3149 80:2047 81:1830 82:1477 83:1216 84:1449 85:3733 86:730 87:1917 88:2842 89:3402 90:550 91:7593 92:2040 93:2555 94:3517 95:4810 96:1349 97:350 98:1172 99:739 100:69 101:1068 102:2378 103:30393 104:4555 105:480 106:894 107:2553 108:911 109:4316 110:2020 111:3319 112:2050 113:1560 114:1530 115:2029 116:1901 117:2474 118:2325 119:1851 120:1707 121:1092 122:2568 123:2115 124:1553 125:2180 128:1261 129:982 130:976 131:2022 132:845 133:378 134:1911 135:291 136:880 137:907 138:2508 139:1516 140:1120 141:1464 142:1398 143:1404 144:1196 145:354 146:1879 147:1533 148:2265 149:1831 150:874 151:1139 152:1831 153:453 154:3829 155:1438 156:1621 157:1297 158:1040 159:2202 160:2566 161:1385 162:3521 163:1436 164:1688 165:1636 166:823 167:1714 168:3855 169:903 170:4546 171:851 172:3479 173:3110 174:1032 175:1161 176:3602 177:4793 178:3514 179:2131 180:2348 181:3361 182:3238 183:1932 184:2361 185:19878 186:4548 187:3986 188:3977 189:3447 190:9052 191:1434 192:11015 193:8760 194:7175 195:5087 196:2983 197:2470 198:6005 199:6068 200:7613 201:5798 202:10557 203:10053 204:4598 205:3493 206:3921 207:3419 208:4092 209:4788 210:4395 211:2441 212:4038 213:3507 214:1100 215:53 216:6536 217:2630 218:1289 219:573 220:2051 221:925 222:839 223:2015 End of report

1 0

bet365 contact
by Rafael Ganascim 04 Nov '22

04 Nov '22

Anyone from bet365 on here or have contact details for them? We got access denied from an entire ASN, and whois contacts and support doesn't help. -- Rafael

1 0

RE: Understanding impact of RPKI and ROA on existing advertisements
by Jakob Heitz (jheitz) 04 Nov '22

04 Nov '22

There are a lot of ROAs out there that make it EASIER to hijack a route rather than harder. If you register an ROA for a route and also advertise that route in BGP, then an attacker who prepends your ASN has to at least compete with your route with an AS_PATH length and will lose in most of the Internet (but not all of it). However, if you don't advertise the route, then the attacker has nothing to compete with and his prepended route will be accepted as RPKI valid everywhere. Remember max_length in a ROA. All routes covered by that max_length will be considered valid by RPKI if the origin ASN matches. If you don't advertise them all, then you are just making it EASIER for an attacker to hijack them. For example if you have an ROA for 10.1.0.0/16, max_length 17, that includes the routes: 10.1.0.0/16 10.1.0.0/17 10.1.128.0/17 If you don't advertise all those routes in BGP, they are open to being hijacked and considered RPKI valid. OTOH, if you register the ROA as 10.1.0.0/16 max_length 16, then anyone who tries to advertise 10.1.0.0/17 will have their advertisement rejected as RPKI invalid. I'm aware that people create ROAs for more specifics in case they need to advertise them to break a hijack. But then the hijacker could just advertise the longest prefix allowed by the ROA. You can't break that with a yet more specific. Unless the user of the route is not validating with RPKI. It's a conundrum. Regards, Jakob.

2 1

WATCH NOW | NANOG 86 Talks, NANOG U + "Internet Innovators"
by Nanog News 03 Nov '22

03 Nov '22

*NANOG 86 Talks are LIVE! * Have you subscribed to our Youtube channel? Subscribe now <https://www.youtube.com/channel/UCIvcN8QNgRGNW9osYLGsjQQ> and be the first to know when new videos are uploaded. The full webcast is available in the "NANOG 86" playlist. *WATCH NOW * <https://www.youtube.com/playlist?list=PLO8DR5ZGla8jtquZaIDizi3q-GnoUgrQQ> *VIDEO: NANOG U Provides Incredible Opportunities for NexGen Tech* *City of Montgomery hosted the two-day event * >From networking opportunities with top-tier tech reps to educational info + career tips from industry leaders — NANOG U is the ultimate foot in the door for anyone interested in pursuing the technical field! Recently, the City of Montgomery hosted our two-day NANOG U Fall 2022 Tour. ARIN, ICANN, Amazon Web Services, Microsoft, + more were in attendance. *WATCH NOW * <https://www.nanog.org/news-stories/nanog-tv/nanog-u/nanog-u-fall-2022-tour-…> *New Episode of "Internet Innovators"* *"Father of the African Internet" Nii Quaynor talks to NANOG* If you watch "Internet Innovators" in Africa, you have Nii Quaynor to thank. Quaynor has pioneered internet development and expansion throughout Africa and is responsible for the first Internet connectivity throughout the continent. *WATCH NOW to learn:* - His story - The current status of the Internet in Africa (post-pandemic) - "Building the Blockchain" + why he thinks Africa should be a cashless society - How to introduce innovation to a new culture - His next five years - + More *WATCH NOW * <https://www.nanog.org/news-stories/nanog-tv/internet-innovators/internet-in…> *2022 NANOG Elections Results* The 2022 NANOG election results are in! Board of Directors Candidates Proposed Bylaw Changes Key Dates Election Results For a full overview and final results click below. *VIEW NOW * <https://www.nanog.org/members/elections/past-elections/2022-nanog-elections…>

1 0

DNS OARC 40 - Call for Contribitions
by John Todd 03 Nov '22

03 Nov '22

OARC 40 will be a two-day hybrid meeting held on 16 & 17 February in Atlanta (GA), USA at 10:00 AM (Local time - EST (UTC-05:00)). The onsite part of the meeting will be colocated with NANOG 87. 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: DNS config management and release process. - Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. - Scaling: DNS performance management and metrics. Increasing DNS Server Efficiency - Security/Privacy: DNSSEC signing and validation, key storage, rollovers, qname minimization, DoH/DoT The presentations can be either a full-length presentation - 20 mins (+5 mins Q/A) or a lightning presentation - 10 mins (+5 mins for Q/A) Workshop Milestones: 2022-10-22 Submissions open via Indico 2022-12-20 Deadline for submission (23:59 UTC) 2023-01-10 Preliminary list of contributions published 2023-01-17 Full agenda published 2023-01-30 Deadline for slideset submission and Rehearsal 2023-02-16 OARC 40 Workshop - Day1 2023-02-17 OARC 40 Workshop - Day2 The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc40> 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. Guidelines for presentation > slides: https://www.grammarly.com/blog/presentation-tips/ Additional information for speakers of OARC 40 - 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 - Remote speakers have mandatory rehearsal on 2023-01-31 at 14:00 UTC. It would be very useful to have your slides (even if draft) ready for this. Note: DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented groups to speak at and/or attend DNS-OARC. More details will be provided when registration opens. 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 0

Understanding impact of RPKI and ROA on existing advertisements
by Samuel Jackson 02 Nov '22

02 Nov '22

Hello, I am new to RPKI/ROA and still learning about RPKI. From all my reading on ARIN's documents I am not able to answer some of my questions. We have a public ARIN block and advertise smaller subnets from that to our ISP's. We do not have any RPKI configs. We need to setup ROA's to take another subnet from the ARIN block to AWS. Reading ARIN's docs, it seems I need to get setup on their Hosted RPKI service after which I can configure ROA's for the networks I am taking to AWS. My question is, will this impact my existing advertisements to my ISP's. The current advertisements do not have ROA's. Will having RPKI for my ARIN network, without ROA's for the existing advertisements impact me? Thanks for your help. Ref: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-byoip.html https://www.arin.net/resources/manage/rpki/roa_request/ https://www.arin.net/resources/manage/rpki/hosted/

10 12

ARIN RPA updated (again) to address TAL distribution (Re: ARIN RPKI services terms/conditions - Change to Management of the Trust Anchor Locator for ARIN’s RPKI Service)
by Christopher S. Yoo 02 Nov '22

02 Nov '22

As the coauthors of the 2019 NSF-supported report that contributed to the current momentum toward overcoming the barriers RPKI adoption, a prior posting asked for our assessment of the changes. Our apologies that we won't be able to join you at this NANOG. We hope to put together some type of program in Atlanta in February. We would say that intent of ARIN's Sept. 26 and 29 updates ((link<https://www.arin.net/announcements/2022/documents/rpa_092622_redline.pdf> and link<https://www.arin.net/announcements/2022/documents/rpa_092922_redline.pdf>) to the RPA-to permit distribution of the TAL without signing the RPA-represent positive steps to address the most significant concern that we raised. In particular, the language in Section 5 added by the Sept. 29 update explicitly stating, "Notwithstanding the foregoing, You are specifically allowed to publicly distribute the ARIN TAL, including by embedding the ARIN TAL in relying party software," appears to authorize including ARIN's TAL in all distributions of validator software, and RPKI adopters would no longer need to download ARIN's TAL from its website. If effective, this is would remove the single most important legal obstacle to broader use of RPKI. The continuing wrinkle is that Section 5 authorizes distribution of ORCP services (including the ARIN TAL) only as permitted by the ORCP service terms. Section 9 requires third parties receiving this information either to have agreed to the RPA or to have entered into an agreement with the distributing party that includes the key terms of the RPA. That would suggest that anyone distributing validator software with ARIN's TAL must ensure that the recipient has agreed to the RPA in order to avoid violating the ORCP service terms. Although open source typically relies on licenses that are good against all users regardless of knowledge or assent (because they sound in property instead of contract), assent to the terms of the RPA could be incorporated into the distribution process, perhaps in the same manner used for other certificate authorities, which typically have terms of use. Another comment on this thread asked if ARIN has now addressed the other issues raised by our report. It is our assessment that ARIN has adequately addressed three of our other concerns, has announced its intention to address two others, and partially addressed one. The three issues that ARIN has adequately addressed include: * Dropping provision of the RSA requiring legacy address holders to acknowledge ARIN's property rights in IP addresses: dropped in update to LRSA dated Sept. 12, 2022 (link<https://www.arin.net/about/corporate/agreements/rsav13_changes.pdf>). * Drop provision of RPA prohibiting sharing of RPKI-derived data in a machine-readable format: authorized for informational purposes by update to RPA dated Oct. 21, 2019 (link<https://www.arin.net/vault/announcements/2019/20191021.html>); authorized for routing purposes by update to RPA dated Sept. 26, 2022 (link<https://www.arin.net/announcements/2022/documents/rpa_092622_redline.pdf>). * Better dissemination of best practices to the community: addressed by expansion of RPKI training at FISPA, WISPA, CaribNOG, and NANOG. ARIN has its intention to address two of our other concerns in the near future: * Better disclosure to government agencies of ARIN's willingness to waive insemination and choice of law clauses when barred by law: likely to be addressed by ARIN's announced plans to create webpage specifically for governments. * Better disclosure of operational practices, such as uptime, update frequency, and response expectations: likely to be addressed further by planned update to certificate practices statement. It partially addressed one concern that we raised. * Dropping blanket indemnification clause in favor of disclaimer of warranties and liability: revised RPA to exclude indemnification for ARIN's gross negligence by update to RPA dated Oct. 21, 2019 (link<https://www.arin.net/vault/announcements/2019/20191021.html>). We hope these comments are helpful and look forward to continuing to work with the community on removing the remaining legal barriers to RPKI adoption. Christopher Yoo (on behalf of myself and David Wishnick)

2 2

Equinix: Still looking for routeserver community info
by Elmar K. Bins 02 Nov '22

02 Nov '22

Hi folks, my inquiry kind of dead-ended here; I still have trouble in Warsaw (could be the name of a movie). Whether I send my prefix with NO_EXPORT, or with the secretly documented 24115:65281 (or 2 or 3) (from https://ix.equinix.com/portal/resources/mlpe-information) the routeserver just eats my prefix and doesn't forward... Does anybody have experience with getting the MLPE system to do what would be required (i.e., take the prefix, attach a NO_EXPORT, and forward)? Thanks! Elmar. PS: Anybody from Equinix wanting to shed some light on this, please...

1 0