- NANOG - lists.nanog.org

Friday Reminder: Web Site Security
by Ronald F. Guilmette 16 May '20

16 May '20

This is your helpful Friday reminder to always pay close attention to the security settings of all of the web sites under your administration. Otherwise, anonymous skript kiddiez could show up at any moment and deface one or more of your web sites. (It happens a lot.) https://ipv4.plus/

6 5

Rogue BGP Routes
by Gary Godard 15 May '20

15 May '20

Hi, We are having an issue with Charter Communications advertising 2 of our IP ranges. We are in the process of implementing RPKI now, but does anyone have a suggestion on how to get them to stop? We have tried contacting them via email and via and phone through numerous channels with no luck. Thanks Gary Godard *Chief Technical Officer* 308 Pine Street West Monroe, LA 71291 Office: 800-536-7035 x5201 Fax: 888-471-8778 Direct: 318-884-9422 Email: gary(a)skyrider.net Web: www.skyrider.net LinkedIn: https://www.linkedin.com/in/gary-godard-48733920 ---------------------------------------------------- Matt 4:19 And he saith unto them, "Follow me, and I will make you fishers of men." If you are his follower, "A Christian", where are you fishing??? ----------------------------------------------------

4 8

Weekly Routing Table Report
by cscora＠apnic.net 15 May '20

15 May '20

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 16 May, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 809430 Prefixes after maximum aggregation (per Origin AS): 307947 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 395544 Total ASes present in the Internet Routing Table: 68052 Prefixes per ASN: 11.89 Origin-only ASes present in the Internet Routing Table: 58439 Origin ASes announcing only one prefix: 24374 Transit ASes present in the Internet Routing Table: 9613 Transit-only ASes present in the Internet Routing Table: 315 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 50 Max AS path prepend of ASN ( 22394) 38 Prefixes from unregistered ASNs in the Routing Table: 1159 Number of instances of unregistered ASNs: 1161 Number of 32-bit ASNs allocated by the RIRs: 31652 Number of 32-bit ASNs visible in the Routing Table: 26151 Prefixes from 32-bit ASNs in the Routing Table: 120583 Number of bogon 32-bit ASNs visible in the Routing Table: 22 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 0 Number of addresses announced to Internet: 2841447936 Equivalent to 169 /8s, 93 /16s and 14 /24s Percentage of available address space announced: 76.7 Percentage of allocated address space announced: 76.7 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: 601773 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 212514 Total APNIC prefixes after maximum aggregation: 62442 APNIC Deaggregation factor: 3.40 Prefixes being announced from the APNIC address blocks: 0 Unique aggregates announced from the APNIC address blocks: 0 APNIC Region origin ASes present in the Internet Routing Table: 10555 APNIC Prefixes per ASN: 0.00 APNIC Region origin ASes announcing only one prefix: 2939 APNIC Region transit ASes present in the Internet Routing Table: 1583 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5638 Number of APNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /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-141625 APNIC Address Blocks ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 237015 Total ARIN prefixes after maximum aggregation: 109071 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 0 Unique aggregates announced from the ARIN address blocks: 0 ARIN Region origin ASes present in the Internet Routing Table: 18487 ARIN Prefixes per ASN: 0.00 ARIN Region origin ASes announcing only one prefix: 6749 ARIN Region transit ASes present in the Internet Routing Table: 1922 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3236 Number of ARIN addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /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-399260 ARIN Address Blocks RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 229794 Total RIPE prefixes after maximum aggregation: 106388 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 0 Unique aggregates announced from the RIPE address blocks: 0 RIPE Region origin ASes present in the Internet Routing Table: 27066 RIPE Prefixes per ASN: 0.00 RIPE Region origin ASes announcing only one prefix: 11736 RIPE Region transit ASes present in the Internet Routing Table: 3820 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9166 Number of RIPE addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /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 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 106330 Total LACNIC prefixes after maximum aggregation: 24623 LACNIC Deaggregation factor: 4.32 Prefixes being announced from the LACNIC address blocks: 0 Unique aggregates announced from the LACNIC address blocks: 0 LACNIC Region origin ASes present in the Internet Routing Table: 9851 LACNIC Prefixes per ASN: 0.00 LACNIC Region origin ASes announcing only one prefix: 2459 LACNIC Region transit ASes present in the Internet Routing Table: 1851 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 50 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7424 Number of LACNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + ERX transfers LACNIC Address Blocks AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 22617 Total AfriNIC prefixes after maximum aggregation: 4670 AfriNIC Deaggregation factor: 4.84 Prefixes being announced from the AfriNIC address blocks: 0 Unique aggregates announced from the AfriNIC address blocks: 0 AfriNIC Region origin ASes present in the Internet Routing Table: 1398 AfriNIC Prefixes per ASN: 0.00 AfriNIC Region origin ASes announcing only one prefix: 491 AfriNIC Region transit ASes present in the Internet Routing Table: 275 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 687 Number of AfriNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7545 5448 684 623 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4740 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3431 1330 22 VIETEL-AS-AP Viettel Group, VN 45899 3153 1806 101 VNPT-AS-VN VNPT Corp, VN 7713 2711 830 509 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2589 9043 61 CMNET-GD Guangdong Mobile Communication 9498 2269 434 223 BBIL-AP BHARTI Airtel Ltd., IN 4766 2267 11102 559 KIXS-AS-KR Korea Telecom, KR 4755 2128 441 194 TATACOMM-AS TATA Communications formerl 9394 2037 4914 20 CTTNET China TieTong Telecommunications 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 11492 4405 296 648 CABLEONE, US 7155 4033 264 27 VIASAT-SP-BACKBONE, US 16509 3992 8102 1802 AMAZON-02, US 22773 3544 2969 153 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3367 1324 91 SHAW, CA 16625 3096 1624 2206 AKAMAI-AS, US 30036 2422 367 90 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2405 5076 537 CENTURYLINK-US-LEGACY-QWEST, US 5650 2305 2981 1621 FRONTIER-FRTR, US 26484 2193 137 196 IKGUL-26484, 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 12479 5754 1603 138 UNI2-AS, ES 31334 4828 484 13 KABELDEUTSCHLAND-AS, DE 39891 3651 203 20 ALJAWWALSTC-AS, SA 8551 3181 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2973 444 2035 AKAMAI-ASN1, EU 12389 2491 2251 725 ROSTELECOM-AS, RU 9009 2156 226 1187 M247, GB 34984 2129 353 563 TELLCOM-AS, TR 13188 1607 100 35 TRIOLAN, UA 25019 1183 987 110 SAUDINETSTC-AS, SA 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 6586 3314 605 Uninet S.A. de C.V., MX 10620 3360 530 506 Telmex Colombia S.A., CO 11830 2665 369 63 Instituto Costarricense de Electricidad 6503 1686 327 388 Axtel, S.A.B. de C.V., MX 7303 1554 1033 253 Telecom Argentina S.A., AR 13999 1398 510 332 Mega Cable, S.A. de C.V., MX 28573 1373 2242 205 CLARO S.A., BR 6147 1154 379 39 Telefonica del Peru S.A.A., PE 3816 1098 569 150 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 957 112 70 Alestra, S. de R.L. de C.V., MX 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 1392 393 22 LINKdotNET-AS, EG 24835 1114 574 25 RAYA-AS, EG 36992 1090 1539 76 ETISALAT-MISR, EG 36903 890 467 88 MT-MPLS, MA 29571 600 68 12 ORANGE-COTE-IVOIRE, CI 6713 561 1863 34 IAM-AS, MA 37342 479 32 1 MOVITEL, MZ 36935 409 522 42 Vodafone-, EG 23889 365 231 15 MauritiusTelecom, MU 15399 351 45 11 WANANCHI-, KE 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 6586 3314 605 Uninet S.A. de C.V., MX 12479 5754 1603 138 UNI2-AS, ES 7545 5448 684 623 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 4828 484 13 KABELDEUTSCHLAND-AS, DE 4538 4740 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4405 296 648 CABLEONE, US 7155 4033 264 27 VIASAT-SP-BACKBONE, US 16509 3992 8102 1802 AMAZON-02, US 39891 3651 203 20 ALJAWWALSTC-AS, SA 22773 3544 2969 153 ASN-CXA-ALL-CCI-22773-RDC, US 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 5754 5616 UNI2-AS, ES 7545 5448 4825 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 4828 4815 KABELDEUTSCHLAND-AS, DE 4538 4740 4667 ERX-CERNET-BKB China Education and Research Net 7155 4033 4006 VIASAT-SP-BACKBONE, US 11492 4405 3757 CABLEONE, US 39891 3651 3631 ALJAWWALSTC-AS, SA 7552 3431 3409 VIETEL-AS-AP Viettel Group, VN 22773 3544 3391 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3367 3276 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 62485 UNALLOCATED 8.23.229.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 26584 UNALLOCATED 8.42.62.0/23 209 CENTURYLINK-US-LEGACY-QWEST, 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 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 Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:9 /9:11 /10:38 /11:99 /12:286 /13:578 /14:1169 /15:1916 /16:13347 /17:8231 /18:13931 /19:25811 /20:40825 /21:48116 /22:100262 /23:83058 /24:470462 /25:1281 /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 5595 5754 UNI2-AS, ES 8151 5189 6586 Uninet S.A. de C.V., MX 31334 4817 4828 KABELDEUTSCHLAND-AS, DE 11492 4124 4405 CABLEONE, US 7155 3900 4033 VIASAT-SP-BACKBONE, US 16509 3863 3992 AMAZON-02, US 39891 3651 3651 ALJAWWALSTC-AS, SA 7545 3445 5448 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3435 3544 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3321 3431 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1553 2:1180 3:30 4:19 5:3383 6:51 8:1419 9:1 11:1 12:1773 13:507 14:2290 15:74 16:8 17:294 18:81 20:100 23:3575 24:2272 25:2 27:2506 31:3109 32:105 34:3 35:42 36:929 37:3275 38:1970 39:405 40:124 41:3607 42:650 43:2117 44:206 45:14264 46:3696 47:293 49:1449 50:1426 51:92 52:1063 54:261 55:674 56:6 57:52 58:1760 59:1171 60:736 61:2264 62:2201 63:1980 64:5156 65:2294 66:4947 67:2855 68:1193 69:3904 70:1415 71:679 72:2875 74:2608 75:1439 76:675 77:2849 78:1651 79:2418 80:1906 81:1625 82:1303 83:1164 84:1236 85:2507 86:544 87:1721 88:994 89:2760 90:310 91:7951 92:1514 93:2496 94:2677 95:3903 96:1207 97:335 98:937 99:977 100:87 101:976 102:953 103:23667 104:3429 105:397 106:869 107:1966 108:713 109:3635 110:1816 111:2043 112:1611 113:1355 114:1522 115:1835 116:1787 117:2122 118:2059 119:1717 120:815 121:1038 122:2438 123:1990 124:1557 125:2037 128:1368 129:1199 130:633 131:1837 132:758 133:300 134:1307 135:287 136:611 137:862 138:2159 139:1000 140:657 141:959 142:929 143:1222 144:981 145:303 146:1502 147:1029 148:2107 149:1170 150:864 151:1299 152:1488 153:385 154:4652 155:1044 156:3165 157:1104 158:833 159:1977 160:1898 161:1042 162:3065 163:812 164:1472 165:1291 166:535 167:1612 168:3489 169:564 170:4203 171:779 172:1928 173:2552 174:996 175:1033 176:2668 177:4214 178:3040 179:1533 180:2275 181:2559 182:3089 183:1122 184:2421 185:16452 186:3767 187:2702 188:4085 189:2269 190:8651 191:1417 192:10353 193:7499 194:6149 195:4382 196:3234 197:1929 198:6089 199:5941 200:7220 201:5247 202:10544 203:10298 204:4571 205:3092 206:3199 207:3290 208:4052 209:4406 210:3983 211:1979 212:3354 213:3081 214:1176 215:61 216:6010 217:2409 218:847 219:613 220:2037 221:920 222:997 223:1466 End of report

1 0

Canadian Tire/AS396367 netops contact
by Eric Dugas 15 May '20

15 May '20

Hello, Canadian Tire has a routing loop in their network. We tried the public contact in their ARIN and none of them are reachable externally. The loop is inside 205.210.17.0/24, (205.210.17.0/24) announced by AS396367 Thanks Eric Dugas

1 0

Akamai/CDN rate limiting
by John Von Essen 15 May '20

15 May '20

Can someone from Akamai reach out off-list? I work for a major search engine (not google or bing) and we’re rolling out a new region. One of our upstream API partners is using Akamai CDN on the front end. When we tried an initial rollout of the region we started to get alot of connection timeouts from the Akamai powered CDN, presumably due to some kind of rate limiting. It was also very bursty in nature. It would be great if we could confirm this, and figure out a way to mitigate. Thanks John

1 0

Don't email clients have a kill file?
by Bjørn Mork 15 May '20

15 May '20

At the risk of starting an off topic discussion here, but am I the only one who'd like to see more plonks and less troll feeding? I miss Usenet. Bjørn

7 7

Re: RIPE NCC Executive Board election
by Terrence Koeman 15 May '20

15 May '20

Yes... and? If you cannot answer the questions posed, why reply at all? I wrote a 100% serious reply to your argument, but you simply fail to engage and write something cryptic that has no bearing on the subject (I guess to mask that you simply don't understand it). This is the third time you're doing this (to me at least) and I'm forced to conclude that you're not just willfully ignorant, but purposefully malicious. Basically a paranoid concern troll with a persecution complex to boot. I'll route your emails to /dev/null from now on. Apologies to the rest on the list for not doing this earlier. -- Regards, Terrence Koeman, PhD/MTh/BPsy Darkness Reigns (Holding) B.V. Please quote relevant replies. Spelling errors courtesy of my 'smart'phone. ________________________________ From: Elad Cohen <elad(a)netstyle.io> Sent: Thursday, 14 May 2020 20:19 To: Terrence Koeman; Owen DeLong Cc: Shane Ronan; North American Network Operators' Group Subject: [SPAM-MS] Re: RIPE NCC Executive Board election > "damages caused to whom and amount to be spent by whom" - You are really good. > > > ________________________________ > From: Terrence Koeman > Sent: Thursday, May 14, 2020 8:55 PM > To: Elad Cohen; Owen DeLong > Cc: Shane Ronan; North American Network Operators' Group > Subject: Re: RIPE NCC Executive Board election > > > "A degree in economics is not needed to know that if the damages of something is causing x2 the amount that can be spent to avoid the damages - then half of the amount should be spent." > > > The questions are: damages caused to whom and amount to be spent by whom (& who is going to make them)? If it were a simple case of weighing the aggregate costs of attacks against the aggregate costs of implementation of mitigation, then we would have seen universal implementation of BCP38[1] two decades ago. > > > Unfortunately, we don't live in a child's mind where things are simple. In reality the parties incurring the costs of attacks are not the same as those that aren't implementing the solutions to prevent them from occurring. > > > If your neighbor has a credit card debt of $20k on which he's paying 18% interest, and you have savings of $20k on which you are receiving 2% interest, then with your logic you should immediately pay off your neighbors' debt, because that'd be cheaper for you both, collectively. > > > But of obviously you wouldn't do this, because you're NOT a collective (your neighbors' wallet/bank account and yours are not the same) and thus you both need to be considered separately. You don't need a degree in economics to realise this, just a shred of common sense suffices. > > > If every network configured their own equipment as well as they wish others would, there wouldn't be a problem in the first place. Fact is, they won't. And getting someone that has already spent time and/or money on configuring their own equipment correctly to pay for the privilege of not getting attacked by the equipment of someone else that is either too lazy or cheap to do so is going to be a tall order. > > > [1] https://tools.ietf.org/html/bcp38 > > -- > Regards, > Terrence Koeman, PhD/MTh/BPsy > Darkness Reigns (Holding) B.V. > > Please quote relevant replies. > Spelling errors courtesy of my 'smart'phone. > ________________________________ > From: Elad Cohen <elad(a)netstyle.io> > Sent: Thursday, 14 May 2020 18:12 > To: Owen DeLong > Cc: Shane Ronan; North American Network Operators' Group > Subject: [SPAM-MS] Re: RIPE NCC Executive Board election > > > Me: > "A degree in economics is not needed to know that if the damages of something is causing x2 the amount that can be spent to avoid the damages - then half of the amount should be spent." > > Toma: > > A degree in economics is not needed [..] > "Which is the common thing to say by the ones who don't have it." > > You: > "simply wrong on legitimate technical grounds" > > > You are not a bigotry or hatred, you are just an imbecile. > ________________________________ > From: Owen DeLong <owen(a)delong.com> > Sent: Thursday, May 14, 2020 7:04 PM > To: Elad Cohen <elad(a)netstyle.io> > Cc: Töma Gavrichenkov <ximaera(a)gmail.com>; Shane Ronan <shane(a)ronan-online.com>; North American Network Operators' Group <nanog(a)nanog.org> > Subject: Re: RIPE NCC Executive Board election > > I don’t see hate. I see legitimate technical disagreement with your hair-brained schemes. > > Perhaps, when a large collection of people with actual engineering experience and deep knowledge tell you that you are simply wrong on legitimate technical grounds, it would be wiser to rethink your position than to accuse them of bigotry and hatred. > > Just a thought. > > Owen > > On May 13, 2020, at 16:48, Elad Cohen <elad(a)netstyle.io> wrote: > > > You start your posts with Peace but your posts are full of hate. > ________________________________ > From: Töma Gavrichenkov <ximaera(a)gmail.com> > Sent: Thursday, May 14, 2020 2:17 AM > To: Elad Cohen <elad(a)netstyle.io> > Cc: Shane Ronan <shane(a)ronan-online.com>; North American Network Operators' Group <nanog(a)nanog.org> > Subject: Re: RIPE NCC Executive Board election > > Peace, > > On Thu, May 14, 2020 at 2:14 AM Elad Cohen <elad(a)netstyle.io> wrote: > > A degree in economics is not needed [..] > > Which is the common thing to say by the ones who don't have it. > > I think, dixi. > > -- > Töma

1 0

Where to send your concerns and how to keep our community welcoming
by Edward McNair 14 May '20

14 May '20

NANOG strives to create a welcoming environment for all. If you are concerned that someone has violated our usage guidelines or code of conduct, please contact admins(a)nanog.org <mailto:admins@nanog.org>. We recently updated our guidance for consistency (there are a few we are still working on). Members of this list know more about what other engineers want to read than our staff, so please support our community approach to moderation by using common sense before posting. Complaints about previous code of conduct violations were addressed in reports from other community members. Those individuals who sent reports were given confirmation that their concerns were reviewed, and that action was taken per NANOG guidelines (warning, moderation, bans). Similar measures were taken this week. Airing grievances on the mailing list is not productive. The NANOG staff cannot discuss individual community members on a mailing list with tens of thousands of members. So you will not receive any confirmation for such reports. Also, it's not appropriate content per the mailing-list usage guidelines: "The Mailing List is not an appropriate platform to resolve personal issues, engage in disputes, or file complaints." Please think before you type and contact us to identify off-topic posts early so warnings can be sent to those who violate NANOG's policies. Please contact admins(a)nanog.org <mailto:admins@nanog.org>, if you believe that a specific post should be removed from the archives. Offensive, illegal, or copyright content can be removed, but there is a higher bar to clear as we strive to maintain a historical record of our community's discussions. Congratulations to RIPE <https://www.ripe.net/> for an impressive online RIPE 80 meeting <https://ripe80.ripe.net/archives/>! NANOG prides itself on welcoming everyone, so it encourages discussions of global issues. Still, I sincerely hope that our open discussion list does not distract from the impressive work of their program committee, staff, and working groups who put on such an incredible event. If you haven't yet, please take a look at the content from the RIPE meeting <https://ripe80.ripe.net/archives/> and perhaps send your highlights to the nanog mailing list <mailto:nanog@nanog.org>. Edward McNair Executive Director

1 0

The NANOG 2019 Annual Report Is Now LIVE
by NANOG Marketing 14 May '20

14 May '20

*The Future of the Internet Is in Our Hands * We made significant progress in 2019 in service of supporting our community as they continue to build the Internet of tomorrow. Through our first-ever annual report, we hope to provide even greater insight and transparency into our achievements and operations over the past year. “With the support of our generous volunteers and the tireless work of our staff, NANOG enjoyed one of its most productive years ever,” says Edward McNair, NANOG Executive Director. “In 2019, we launched our new website, modernized our visual identity and brand voice, introduced a new badging system to improve the user experience at conferences, and expanded the program by securing keynote speakers well in advance of each meeting.” Many thanks to everyone who helped us along the way! *Read the Report <https://www.nanog.org/resources/annual-report/>*

1 0

RIPE NCC Executive Board election
by Ronald F. Guilmette 14 May '20

14 May '20

Many of you here may be dues-paying members of both ARIN and RIPE. Those of you who are may wish to be aware of the fact that there will be an election held on (I believe) May 14th, just a day or two from now, for three open RIPE NCC Executive Board seats. I have it on good authority that one of the candidates running for the open RIPE NCC board seats in this election has hired legal counsel in South Africa, and that said legal counsel has then proceeded to threaten various officials of the City of Cape Town, South Africa with possible legal action if they do not relinquish to him their rights in and title to the 165.25.0.0/16 block, a block that all historical records, including even ARIN "WhoWas" historical records show, clearly and unambiguously, has been legally registered to the City of Cape Town for over twenty years. (I am assured that at no time did the City of Cape Town ever sell, trade, or barter away their rights to this valuable IPv4 block, and that they are defending themselves, as best as they can, against this attempt to extort them out of their rightful prooperty.) Where I come from, this kind of thing is called barratry, but you be the judge. In any case, prior to the RIPE election, I wanted to let you all know these facts about the candidate in question, as well as a number of additional startling facts relating to the people who nominated this candidate for a RIPE NCC Executive board seat, as documented by my friend, South African journalist Jan Vermeulen: https://mybroadband.co.za/news/internet/350973-man-connected-to-african-ip-… I could go into more detail about many of the nominators mentioned in the above article, but I don't want to make this email too long, so I'll await some explict request for that additional info. For now it should suffice to make at least some of the basic facts more widely available, a task which is accomplished just by sharing the above link, IMHO. Regards, rfg P.S. I have been specifically and explicitly enjoined and constrained from posting here anything at all that might smack of being either partisan or of an even vaguely "political" nature, and thus, I will refrain from doing so. I would be remiss hoever if I did not at least note in passing that history records that in times such as these, when people of good character and good intent are, as they rightly should be, focused on the health and safety of themselves, their loved ones, and their professional collegues, and when the gaze of the world is elsewhere, persons of less than honorable intent reach for power and, with unfortunate regularity, obtain it. I cannot and do not ask that those of you who have been saddled with personal or local crises during this sad time turn away from those responsibilities to give attention to matters of Internet governance, however urgent those may appear at the moment. For all of us, our first- order duty lies nearby, with family, friends, and collegues. But for those of you who still have a few cycles to spare, I do ask that you consider carefully the newfound and critical importance of this tool, this Internet, in the lives of so many millions, all around the world, and the self-evident risks of its governance being handed over, by default or otherwise, to persons with an interest only in what is best for them personally, to the exclusion of all else. P.P.S. I would be posting this info and the above link also to the very relevant RIPE members-discuss mailing list, but as I am not a due-paying member of RIPE, I have no ability to do so. Separately, due in no small part to the candidate's own recent and manifest on-list transgressions on that very list, that list has recently been switched to a heavy-handed moderation, under which, it seems, even discussion of the pros and cons of candidates in the upcoming RIPE NCC Executive Board election are now categorized as "too controversial" and thus, themselves, are now entirely off-limits. I cannot help but be reminded of a catch-phrase that I saw somewhere, not too long ago: "Democracy dies in darkness." -- anon

26 67