- Test - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 29 Sep '23

29 Sep '23

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 UKNOF, 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 30 Sep, 2023 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: 930281 Prefixes after maximum aggregation (per Origin AS): 353509 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 453312 Total ASes present in the Internet Routing Table: 74874 Prefixes per ASN: 12.42 Origin-only ASes present in the Internet Routing Table: 64269 Origin ASes announcing only one prefix: 26434 Transit ASes present in the Internet Routing Table: 10605 Transit-only ASes present in the Internet Routing Table: 460 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1003 Number of instances of unregistered ASNs: 1005 Number of 32-bit ASNs allocated by the RIRs: 42726 Number of 32-bit ASNs visible in the Routing Table: 35176 Prefixes from 32-bit ASNs in the Routing Table: 175775 Number of bogon 32-bit ASNs visible in the Routing Table: 54 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 527 Number of addresses announced to Internet: 3053878912 Equivalent to 182 /8s, 6 /16s and 126 /24s Percentage of available address space announced: 82.5 Percentage of allocated address space announced: 82.5 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: 309201 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 247043 Total APNIC prefixes after maximum aggregation: 70962 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 240653 Unique aggregates announced from the APNIC address blocks: 98905 APNIC Region origin ASes present in the Internet Routing Table: 13679 APNIC Prefixes per ASN: 17.59 APNIC Region origin ASes announcing only one prefix: 4094 APNIC Region transit ASes present in the Internet Routing Table: 1821 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9004 Number of APNIC addresses announced to Internet: 772959104 Equivalent to 46 /8s, 18 /16s and 107 /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-153913 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: 272579 Total ARIN prefixes after maximum aggregation: 123726 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 276203 Unique aggregates announced from the ARIN address blocks: 131912 ARIN Region origin ASes present in the Internet Routing Table: 19097 ARIN Prefixes per ASN: 14.46 ARIN Region origin ASes announcing only one prefix: 6956 ARIN Region transit ASes present in the Internet Routing Table: 1960 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4829 Number of ARIN addresses announced to Internet: 1277916160 Equivalent to 76 /8s, 43 /16s and 116 /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: 261556 Total RIPE prefixes after maximum aggregation: 123664 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 256783 Unique aggregates announced from the RIPE address blocks: 160050 RIPE Region origin ASes present in the Internet Routing Table: 28418 RIPE Prefixes per ASN: 9.04 RIPE Region origin ASes announcing only one prefix: 12056 RIPE Region transit ASes present in the Internet Routing Table: 3946 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11354 Number of RIPE addresses announced to Internet: 716413824 Equivalent to 42 /8s, 179 /16s and 155 /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-216475 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: 118194 Total LACNIC prefixes after maximum aggregation: 28513 LACNIC Deaggregation factor: 4.15 Prefixes being announced from the LACNIC address blocks: 117113 Unique aggregates announced from the LACNIC address blocks: 49363 LACNIC Region origin ASes present in the Internet Routing Table: 11037 LACNIC Prefixes per ASN: 10.61 LACNIC Region origin ASes announcing only one prefix: 2705 LACNIC Region transit ASes present in the Internet Routing Table: 2334 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8855 Number of LACNIC addresses announced to Internet: 178491776 Equivalent to 10 /8s, 163 /16s and 145 /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: 29906 Total AfriNIC prefixes after maximum aggregation: 5948 AfriNIC Deaggregation factor: 5.03 Prefixes being announced from the AfriNIC address blocks: 39002 Unique aggregates announced from the AfriNIC address blocks: 12642 AfriNIC Region origin ASes present in the Internet Routing Table: 1790 AfriNIC Prefixes per ASN: 21.79 AfriNIC Region origin ASes announcing only one prefix: 623 AfriNIC Region transit ASes present in the Internet Routing Table: 335 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 28 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1134 Number of AfriNIC addresses announced to Internet: 107671808 Equivalent to 6 /8s, 106 /16s and 241 /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 9495 8730 44 CHINAMOBILE-CN China Mobile Communicati 7545 5735 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4938 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4231 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3592 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3331 1840 96 VNPT-AS-VN VNPT Corp, VN 9498 3188 498 251 BBIL-AP BHARTI Airtel Ltd., IN 7552 2940 1330 20 VIETEL-AS-AP Viettel Group, VN 4766 2540 11270 601 KIXS-AS-KR Korea Telecom, KR 24560 2517 848 383 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 9098 10992 3232 AMAZON-02, US 11492 4535 301 668 CABLEONE, US 7155 4177 288 100 VIASAT-SP-BACKBONE, US 6327 3546 1319 66 SHAW, CA 22773 3529 3055 302 ASN-CXA-ALL-CCI-22773-RDC, US 749 3151 54959 2403 DNIC-AS-00749, US 367 3002 3822 1418 DNIC-ASBLK-00306-00371, US 16625 2987 1409 2288 AKAMAI-AS, US 396982 2698 3597 395 GOOGLE-CLOUD-PLATFORM, US 30036 2498 359 376 MEDIACOM-ENTERPRISE-BUSINESS, 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 7389 1713 145 UNI2-AS, ES 39891 4897 290 61 ALJAWWALSTC-AS, SA 20940 4073 3398 153 AKAMAI-ASN1, NL 8551 3446 368 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2980 2296 915 ROSTELECOM-AS, RU 9009 2897 264 1483 M247, RO 34984 2334 361 596 TELLCOM-AS, TR 58224 1723 923 527 TCI, IR 13188 1606 100 27 TRIOLAN, UA 8452 1488 1852 16 TE-AS TE-AS, EG 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 11801 3382 595 UNINET, MX 10620 3542 506 852 Telmex Colombia S.A., CO 13999 2407 331 621 Mega Cable, S.A. de C.V., MX 11830 1820 369 64 Instituto Costarricense de Electricidad 28573 1327 2324 233 Claro NXT Telecomunicacoes Ltda, BR 6503 1302 344 510 Axtel, S.A.B. de C.V., MX 3816 1296 766 190 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1110 369 22 Telefonica del Peru S.A.A., PE 11664 1106 179 428 Techtel LMDS Comunicaciones Interactiva 26615 1034 2501 49 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 1605 393 19 LINKdotNET-AS, EG 24835 1549 549 28 RAYA-AS, EG 36992 1360 1518 280 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1046 67 45 ORANGE-COTE-IVOIRE, CI 36935 938 521 44 Vodafone-, EG 6713 549 1861 34 IAM-AS, MA 15399 533 55 50 WANANCHI-, KE 37342 489 32 1 MOVITEL, MZ 24757 462 73 5 EthioNet-AS, ET 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 11801 3382 595 UNINET, MX 9808 9495 8730 44 CHINAMOBILE-CN China Mobile Communicati 16509 9098 10992 3232 AMAZON-02, US 12479 7389 1713 145 UNI2-AS, ES 7545 5735 785 698 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4938 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4897 290 61 ALJAWWALSTC-AS, SA 11492 4535 301 668 CABLEONE, US 18403 4231 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4177 288 100 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 9495 9451 CHINAMOBILE-CN China Mobile Communications Grou 12479 7389 7244 UNI2-AS, ES 16509 9098 5866 AMAZON-02, US 7545 5735 5037 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4938 4863 ERX-CERNET-BKB China Education and Research Net 39891 4897 4836 ALJAWWALSTC-AS, SA 18403 4231 4206 FPT-AS-AP FPT Telecom Company, VN 7155 4177 4077 VIASAT-SP-BACKBONE, US 20940 4073 3920 AKAMAI-ASN1, NL 11492 4535 3867 CABLEONE, 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 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 396894 UNALLOCATED 8.28.201.0/24 46887 LIGHTOWER, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, 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.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.176.160.0/24 Origin: 397327 RESERVED, ZZ 23.176.160.0/24 Transit: 19108 SUDDENLINK-COMMUNICATIONS, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, US 36.255.139.0/24 Origin: 56050 NEW-SHINE-INTERNET-TH 134 Yenchit Road, 36.255.139.0/24 Transit: 58913 HCL-TH 4819 Supapong 3 Alley, Srinakarin 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:14 /10:38 /11:101 /12:299 /13:581 /14:1196 /15:2064 /16:13501 /17:8313 /18:13886 /19:25168 /20:44315 /21:51237 /22:110289 /23:99053 /24:559476 /25:734 /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 12479 6476 7389 UNI2-AS, ES 8151 5830 11801 UNINET, MX 39891 3632 4897 ALJAWWALSTC-AS, SA 11492 3447 4535 CABLEONE, US 6327 3356 3546 SHAW, CA 7155 3122 4177 VIASAT-SP-BACKBONE, US 8551 2923 3446 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2578 3529 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2155 2498 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2107 3542 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2237 2:1408 3:265 4:5 5:4436 6:137 7:6 8:1538 9:1 11:172 12:1514 13:369 14:2328 15:304 16:200 17:369 18:659 20:287 21:4 22:188 23:6432 24:2511 25:2 27:2531 29:19 31:2535 32:78 34:25 35:117 36:2007 37:4520 38:5367 39:864 40:143 41:4016 42:2067 43:2295 44:321 45:16644 46:4296 47:369 49:1835 50:1884 51:590 52:1592 54:393 55:960 56:5 57:122 58:1866 59:1180 60:1004 61:2517 62:2690 63:1914 64:5647 65:2361 66:4990 67:3038 68:1340 69:4135 70:1194 71:668 72:2944 74:2626 75:1560 76:626 77:2302 78:1826 79:2985 80:2098 81:1832 82:1503 83:1302 84:1560 85:3075 86:770 87:2004 88:1201 89:3912 90:620 91:7813 92:2062 93:2617 94:3515 95:4020 96:1300 97:315 98:1082 99:730 100:90 101:1047 102:2860 103:32150 104:4739 105:576 106:915 107:2694 108:1132 109:4245 110:2134 111:3200 112:2067 113:1817 114:1693 115:1987 116:1901 117:2460 118:2685 119:1969 120:1803 121:1182 122:2610 123:2215 124:1614 125:2576 128:1450 129:922 130:1044 131:1977 132:820 133:408 134:1784 135:306 136:971 137:970 138:2620 139:1596 140:1286 141:1325 142:1513 143:1549 144:1009 145:353 146:1951 147:1608 148:2480 149:2281 150:877 151:1229 152:1873 153:520 154:5067 155:1389 156:1987 157:1336 158:1055 159:2247 160:2631 161:1594 162:3544 163:1608 164:1701 165:1845 166:1070 167:1734 168:3761 169:885 170:4634 171:914 172:3774 173:2966 174:983 175:1193 176:3788 177:4467 178:3537 179:2163 180:2459 181:3528 182:3409 183:1980 184:2275 185:20579 186:4678 187:4181 188:4165 189:3859 190:9281 191:1371 192:10986 193:8964 194:7308 195:5224 196:3096 197:2477 198:6024 199:6144 200:7861 201:5890 202:10557 203:10031 204:4557 205:3701 206:4381 207:3504 208:4153 209:4913 210:4498 211:2540 212:4258 213:3391 214:1114 215:70 216:6707 217:2781 218:1302 219:577 220:2032 221:982 222:842 223:2179 End of report

1 0

Seattle-area centurylink (residential fiber) on the list?
by William Herrin 29 Sep '23

29 Sep '23

Howdy, Is anyone from Centurylink in the Seattle area on the list? Would you mind contacting me offlist? My residential fiber has been bouncing for a few hours. I figured it was something physical and scheduled a technician, but on closer examination I'm seeing something weird with the PPPoE. It chugs along happily for a while (dc:38:e1:cd:4f:7a is you, 44:1e:a1:44:70:3f is me) and then I lose *my* connectivity for 10-20 seconds but during that window there's a big spew of packets that aren't addressed to me. The following is just the PPPoE LCP messages captured by tcpdump, but the misdirected traffic also appears to include TCP/IP user data for customers who are not me. 20:15:13.278955 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 73, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:15:13.280651 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 73, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 20:15:20.712278 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 97, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 20:15:20.712418 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 97, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:15:33.291480 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 74, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:15:53.293020 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 75, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:15:58.165578 dc:38:e1:cd:4f:7a > 0c:83:cc:e2:46:82, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x175] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x1b3bc70b 20:15:58.312737 dc:38:e1:cd:4f:7a > 0c:83:cc:fb:9c:60, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x35d] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 56, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x10318647 20:16:00.517865 dc:38:e1:cd:4f:7a > 88:6a:e3:64:fe:1a, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x17a] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x74677bcb 20:16:01.215725 dc:38:e1:cd:4f:7a > 4c:c5:3e:9e:16:e7, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x1f9] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 57, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x2a507cd9 20:16:02.162884 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d7:bd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x18f] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 57, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x53806fa0 20:16:02.911642 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d6:fd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x287] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 57, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x363109e1 20:16:03.315970 dc:38:e1:cd:4f:7a > 0c:83:cc:fe:dc:10, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x7f] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x1916d95f 20:16:05.713807 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 100, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 20:16:05.713968 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 100, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:16:08.257543 dc:38:e1:cd:4f:7a > d8:ec:e5:02:1c:b5, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x23a] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x37a24174 20:16:08.858581 dc:38:e1:cd:4f:7a > 0c:83:cc:dd:7b:3c, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0xdd] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x79cb769d 20:16:11.912788 dc:38:e1:cd:4f:7a > 4c:c5:3e:75:b2:f4, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x227] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x58cab7de 20:16:12.070053 dc:38:e1:cd:4f:7a > 4c:c5:3e:75:b2:f4, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x227] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 10, length 6 encoded length 4 (=Option(s) length 0) 20:16:13.300753 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 76, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:16:13.302748 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 76, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 20:16:13.312884 dc:38:e1:cd:4f:7a > 0c:83:cc:fb:9c:60, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x35d] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 57, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x10318647 20:16:13.469980 dc:38:e1:cd:4f:7a > 0c:83:cc:fb:9c:60, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x35d] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 243, length 6 encoded length 4 (=Option(s) length 0) 20:16:15.517997 dc:38:e1:cd:4f:7a > 88:6a:e3:64:fe:1a, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x17a] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 59, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x74677bcb 20:16:15.670053 dc:38:e1:cd:4f:7a > 88:6a:e3:64:fe:1a, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x17a] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 2, length 6 encoded length 4 (=Option(s) length 0) 20:16:16.215984 dc:38:e1:cd:4f:7a > 4c:c5:3e:9e:16:e7, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x1f9] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x2a507cd9 20:16:16.370130 dc:38:e1:cd:4f:7a > 4c:c5:3e:9e:16:e7, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x1f9] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 149, length 6 encoded length 4 (=Option(s) length 0) 20:16:17.162973 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d7:bd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x18f] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x53806fa0 20:16:17.320374 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d7:bd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x18f] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 243, length 6 encoded length 4 (=Option(s) length 0) 20:16:17.911948 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d6:fd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x287] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 58, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x363109e1 20:16:18.070000 dc:38:e1:cd:4f:7a > d8:ec:e5:04:d6:fd, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x287] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 86, length 6 encoded length 4 (=Option(s) length 0) 20:16:18.316035 dc:38:e1:cd:4f:7a > 0c:83:cc:fe:dc:10, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x7f] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 59, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x1916d95f 20:16:18.469998 dc:38:e1:cd:4f:7a > 0c:83:cc:fe:dc:10, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x7f] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 31, length 6 encoded length 4 (=Option(s) length 0) 20:16:20.712679 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 101, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 20:16:20.712830 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 101, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:16:23.257678 dc:38:e1:cd:4f:7a > d8:ec:e5:02:1c:b5, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x23a] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 59, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x37a24174 20:16:23.420171 dc:38:e1:cd:4f:7a > d8:ec:e5:02:1c:b5, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x23a] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 198, length 6 encoded length 4 (=Option(s) length 0) 20:16:23.858727 dc:38:e1:cd:4f:7a > 0c:83:cc:dd:7b:3c, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0xdd] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 59, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x79cb769d 20:16:24.020200 dc:38:e1:cd:4f:7a > 0c:83:cc:dd:7b:3c, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0xdd] LCP (0xc021), length 6: LCP, Term-Request (0x05), id 223, length 6 encoded length 4 (=Option(s) length 0) 20:16:33.311230 44:1e:a1:44:70:3f > dc:38:e1:cd:4f:7a, ethertype PPPoE S (0x8864), length 30: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Request (0x09), id 77, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0xd9ab6924 20:16:33.313248 dc:38:e1:cd:4f:7a > 44:1e:a1:44:70:3f, ethertype PPPoE S (0x8864), length 56: PPPoE [ses 0x4e6] LCP (0xc021), length 10: LCP, Echo-Reply (0x0a), id 77, length 10 encoded length 8 (=Option(s) length 4) Magic-Num 0x24a0da14 -- William Herrin bill(a)herrin.us https://bill.herrin.us/

1 0

Fwd: RADb will migrate to IRRdv4 on October 30, 2023
by Job Snijders 28 Sep '23

28 Sep '23

Dear all, Please see the below announcement, I think this is really good news! RPKI-based filtering at large databases and mirror services like RADB really helps take the sting out of potentially harmful RPKI-invalid IRR route objects. This will positively impact operators who use bgpq3, irrpt, or irrtoolset/peval to generate filters, because those tools use whois.radb.net by default. Kind regards, Job ---------- Forwarded message --------- From: Merit RADb <radb(a)merit.edu> Date: Thu, 28 Sep 2023 at 21:00 Subject: RADb will migrate to IRRdv4 on October 30, 2023 To: <job(a)fastly.com> RADB will switch to IRRdv4 on October 30 [image: RADb blue logo-tagline] <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> Dear RADb Community, As originally announced in March 2023, RADb is transitioning to IRRd (Internet Routing Registry daemon) version 4. On October 30th, 2023, we will migrate RADb over from IRRdv3, which you are currently using, to IRRDv4. Below are links to demo servers that will allow you to interact with the new service prior to the migration. As you start planning for the transition, here are some key things to note: - We will import the current database into IRRDv4 on October 30th. - We will work to maintain the current serial numbers for NRTM. If we are unable to you will need to update your mirror before NRTM can continue. - We will enable RPKI. - The rpki-ov-state RPSL field notes the RPKI status (valid, invalid, or not-found) - whois will hide RPKI invalid objects unless you use !fno-rpki-filters - IRRDv4 is more strict, but we are starting with most of this strictness disabled initially. - IRRDv4 may output RPSL objects differently. - The RADb API is the same, but may return different error messages, or similar error messages with different wording. For example, it will now report RPKI errors. - Existing mntner objects will be imported even with invalid admin-c/tech-c handler. Any updates will require at least one person or role object associated with it. We will be updating our registration process to create these objects for you. - New mntner objects must also have at least one person or role object associated with it. We will initially handle this for you the the customer portal, but you should check the created person or role for correctness. - New mntner objects will use bcrypt for passwords. This will happen automatically for you through the customer portal The following demo environments are available for your testing (please use your existing credentials): - whois2.radb.net <#m_-1278871392211290094_m_-2351897707799796429_> - IRRdv4 with current RADb objects and live mirroring of other RIRs - whois2demo.radb.net <#m_-1278871392211290094_m_-2351897707799796429_> - IRRdv4 with sample data (v4 version of whoisdemo.radb.net <#m_-1278871392211290094_m_-2351897707799796429_>) - wwwdemo.radb.net <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> - demo web portal backed by whois2.radb.net <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> - apidemo2.radb.net <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> - demo API (available October 1st) This move to IRRDv4 will bring many benefits to you, including: - Improved RADb data quality - Prevention of RPKI-invalid objects from being created in RADb - Prevention of object creation for invalid prefixes (such as RFC 1918 space) - as-set and route-set object creation will be limited to the account that maintains the aut-num object extending and protecting the ASN of the resource holder from misrepresentation (requires use of hierarchical naming conventions) - Improved extensibility and maintainability We thank you for subscribing to Merit’s RADb service - the contributions of this community make the internet a better place to learn, work and share data. *Questions? *Please contact us at support(a)radb.net *We also welcome your feedback - please take our brief customer satisfaction survey: **https://radb.net/survey* <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> Our sincerest thanks, The RADb Team [image: merit_network1] [image: Facebook] <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> [image: Twitter] <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> [image: LinkedIn] <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…> [image: YouTube] <https://d2tTpN04.na1.hubspotlinks.com/Ctc/2N+113/d2tTpN04/VVpYl230vYh0W6PgX…>

1 0

Test Lab Best Practices
by Kenneth Vedder 28 Sep '23

28 Sep '23

Hello NANOG, We have been struggling with firmware bugs from a specific router vendor. I am looking to set up a test lab of our core network and a few remote site routers. Protocols would include SR-MPLS, ISIS, EVPN MPLS and L3VPN with a little OSPF sprinkled in. I'd be grateful for any tips or resources anyone has that might cover testing strategies and/or best practices. Thanks, Ken

8 7

Contact for Hulu
by Brad Bendy 28 Sep '23

28 Sep '23

Can anyone at Hulu contact me off list? Have issues with some new subnets we have and our end users cannot access the Hulu service with various error messages. Thanks

2 1

Re: Contact for Hulu
by Kenneth Vedder 28 Sep '23

28 Sep '23

I would also be thankful for a contact at Hulu, we've been having similar issues to what Brad described. Ken V Amplex Internet On Thu, Sep 28, 2023 at 8:00 AM <nanog-request(a)nanog.org> wrote: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. RE: SMTP-friendly VPS provider where I can also get a BGP > feed (Tim Burke) > 2. OARC 42 - Call for Contributions (co-located with NANOG 90) > (John Todd) > 3. Re: SMTP-friendly VPS provider where I can also get a BGP > feed (Christopher Munz-Michielin) > 4. Contact for Hulu (Brad Bendy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 27 Sep 2023 13:58:11 +0000 > From: Tim Burke <tim(a)mid.net> > To: Tony Wicks <tony(a)wicks.co.nz>, 'Daniel Corbe' <daniel(a)corbe.net>, > "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: RE: SMTP-friendly VPS provider where I can also get a BGP > feed > Message-ID: > < > PH7P221MB09647C6E57CBE701CF45B6A3BBC2A(a)PH7P221MB0964.NAMP221.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="us-ascii" > > Unfortunately, Racknerd provides a majority of their services using a > dedicated server hosting company (Colo Crossing) that is known for > harboring spam and other malicious activity, so their IP space is generally > either blacklisted, of very poor reputation, or in many cases, completely > dropped at firewalls. Case in point, your message that originated from one > of these IPs tripped up my workstation's local spam filtering plugin from > ESET. > > V/r > Tim > > -----Original Message----- > From: NANOG <nanog-bounces+tim=mid.net(a)nanog.org> On Behalf Of Tony Wicks > Sent: Tuesday, September 26, 2023 1:39 PM > To: 'Daniel Corbe' <daniel(a)corbe.net>; nanog(a)nanog.org > Subject: [SPAM] RE: SMTP-friendly VPS provider where I can also get a BGP > feed > > I can't speak to the bgp feed as this seems like unnecessary complication > to me, but I use https://www.racknerd.com/ for personal email/web hosting > KVM VM's and have found them to be excellent. They have yearly black Friday > specials (last years - https://www.racknerd.com/BlackFriday/ ) that are > very attractive. They don't block any ports on their US/Europe VM's. I use > a primary pair in one city and rsync everything to a backup pair in another > city (as well as home just to make sure). Not all cities can get V6 but > most do. > > > > -----Original Message----- > From: NANOG <nanog-bounces+tony=wicks.co.nz(a)nanog.org> On Behalf Of > Daniel Corbe > Sent: Tuesday, September 26, 2023 11:09 PM > To: nanog(a)nanog.org > Subject: SMTP-friendly VPS provider where I can also get a BGP feed > > Hey all, > > I apologize if this isn't the right place to post this; however, I thought > maybe the NANOG community would be able to point me in the right direction. > > I'm looking for a place that I can host a mailer. My primary use case is > a Mailman-style technical discussion list; much like NANOG but software > related instead of network related: READ: non-commercial in nature. > > I'm currently a vultr customer, but they're refusing to unblock port 25 on > my account. I've tried explaining my use case but no matter who I talk to > over there they just keep pointing me to their spam policy. > > Thanks! > -Daniel > > > > ------------------------------ > > Message: 2 > Date: Wed, 27 Sep 2023 07:51:01 -0700 > From: John Todd <jtodd(a)quad9.net> > To: list <nanog(a)nanog.org> > Subject: OARC 42 - Call for Contributions (co-located with NANOG 90) > Message-ID: <176AEAE1-D6DA-46A9-9EAB-CF0E250550CC(a)quad9.net> > Content-Type: text/plain; charset="us-ascii"; Format="flowed" > > OARC 42 will be a two-day hybrid meeting and the dates are 8th and 9th > February to be co-located with NANOG 90 in Charlotte, North Carolina, > USA. > > 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 10 or 20 minutes in length (plus 5 > minutes for Q&A). Proposals for in-person lightning presentations will > be opened closer to the Workshop dates. > > Workshop Milestones: > > 2023-09-07 Submissions open via Indico > 2023-11-22 Deadline for submission (23:59 UTC) > 2023-11-29 Preliminary list of contributions published > 2023-12-13 Full agenda published > 2024-01-10 Deadline for slideset submission and Rehearsal > 2024-02-08 OARC 42 Workshop - Day1 > 2024-02-09 OARC 42 Workshop - Day2 > > The Registration page and details for presentation submission are > published at: > <https://www.dns-oarc.net/oarc42> > > 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. > Example guidelines for presentation slides: > https://www.grammarly.com/blog/presentation-tips/ > > Additional information for speakers of OARC 42 > - 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 (Date and Time TBD). 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 > > 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, for the DNS-OARC Programme Committee > > -- > John Todd - jtodd(a)quad9.net > General Manager - Quad9 Recursive Resolver > >

1 0

SMTP-friendly VPS provider where I can also get a BGP feed
by Daniel Corbe 27 Sep '23

27 Sep '23

Hey all, I apologize if this isn't the right place to post this; however, I thought maybe the NANOG community would be able to point me in the right direction. I'm looking for a place that I can host a mailer. My primary use case is a Mailman-style technical discussion list; much like NANOG but software related instead of network related: READ: non-commercial in nature. I'm currently a vultr customer, but they're refusing to unblock port 25 on my account. I've tried explaining my use case but no matter who I talk to over there they just keep pointing me to their spam policy. Thanks! -Daniel

17 21

OARC 42 - Call for Contributions (co-located with NANOG 90)
by John Todd 27 Sep '23

27 Sep '23

OARC 42 will be a two-day hybrid meeting and the dates are 8th and 9th February to be co-located with NANOG 90 in Charlotte, North Carolina, USA. 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 10 or 20 minutes in length (plus 5 minutes for Q&A). Proposals for in-person lightning presentations will be opened closer to the Workshop dates. Workshop Milestones: 2023-09-07 Submissions open via Indico 2023-11-22 Deadline for submission (23:59 UTC) 2023-11-29 Preliminary list of contributions published 2023-12-13 Full agenda published 2024-01-10 Deadline for slideset submission and Rehearsal 2024-02-08 OARC 42 Workshop - Day1 2024-02-09 OARC 42 Workshop - Day2 The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc42> 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. Example guidelines for presentation slides: https://www.grammarly.com/blog/presentation-tips/ Additional information for speakers of OARC 42 - 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 (Date and Time TBD). 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 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, for the DNS-OARC Programme Committee -- John Todd - jtodd(a)quad9.net General Manager - Quad9 Recursive Resolver

1 0

Paramount+ anyone here? Please contact off list
by Norman Jester 27 Sep '23

27 Sep '23

Looking for some connectivity help with routing, a unique problem. Please contact me off-list. Norman Jester 619-319-7055 (I prefer WhatsApp or Text if you do too.)

1 0

NANOG 89 Agenda is LIVE! + "Network Automation Could Save Your Life" + More
by Nanog News 26 Sep '23

26 Sep '23

*NANOG 89 Agenda is LIVE! * *Sync Your Calendars Now + Never Miss a Talk! * *Have you registered yet for NANOG 89?* Check out the full agenda with talk date/time, abstract, + speaker info to create your personal NANOG 89 schedule. *VIEW AGENDA * <https://nanog.org/events/nanog-89/nanog-89-agenda/> *Guest Columnist: Scott Robohn* *"Network Automation Could Save Your Life — Maybe Not Your Life, but Probably Your Career"* *Network Automation* is receiving a much-needed boost in attention, partly due to the efforts of NANOG, the Network Automation Forum (NAF), and other organizations. Why this boost? Network Automation is moving slower than we thought it should and perhaps slower than we need it to move. *READ MORE <https://nanog.org/stories/articles/network-automation-could-save-your-life/>* *Video of the Week* *NANOG 87 Recap * NANOG 89 is less than three short weeks away! Get into the NANOG spirit + take a trip down memory lane. Watch the NANOG 87 recap video now — meeting location: Atlanta. *WATCH NOW <https://www.youtube.com/watch?v=fejIBHzKU14&t=53s>* *Attend NANOG Virtually!* *Can't make it to our next meeting in San Diego? Join us virtually!* Stream live presentations, participate in real-time chat forums, enjoy 360 views of General Session + more. *REGISTER NOW! * <https://nanog.org/events/nanog-89/>

1 0