March 2021 - Test - lists.nanog.org

Best practice for ptp/loopback numbering for "small" enterprise multihome setup
by vom513 26 Mar '21

26 Mar '21

Hello, tl;dr - If I only have a /24 PI - is there any way to use this and not “chop it up / deagg” to use for ptp/loopbacks ? Hopefully I can explain this in a manner that makes sense. Say I have a vanilla dual router/dual upstream setup (think enterprise internet edge). It’s basically an “H” shape: - Two ISPs - Two routers (“crosslink” is the middle of the H - iBGP) - Each router has at least a link downstream into my public “outside” segment. I run an FHRP here. This is where my DMZ firewalls, VPN endpoints etc. have their outside interfaces. Let’s also say I only have a /24 of PI. I need to number the crosslink and the loopbacks. The upstreams will use their own /30 / /31 let’s say for the top of the H. My downstream interfaces will have my /24 (or parts of it) on the bottom of the H. My understanding and instinct is that at least the crosslink should be numbered with public addresses. One scenario where this might matter is if router2 loses his inside interface (ex: switch failure) - he still needs to be able to deliver traffic via crosslink via router1 and onward downstream. When this traffic traverses here, if there is any kind of error (i.e. router is sourcing an ICMP packet of some kind) - this will be sourced from router1’s crosslink yes (assuming router1 is generating the error of course) ? Loopback’s may be negotiable, as only router1/2 are using these to pin up iBGP. Nevertheless, my instinct would be to also use public addresses here. As I said in the tl;dr - my main point of contention here is breaking up my /24 I.e. use the very top /30s / /31s for ptp/loop. I would then have at most the bottom /25 to use contig. on my “lan” - and I would need to use the next /26, /27 and so on in some manner for the space to be useable... Here are some other options, and my understanding of the pros/cons: - Use RFC1918 Makes my eye twitch out of the gate. Not to mention packets sourced from here *should* get blocked by my upstreams by way of uRPF. Likely to be filtered at other points and directions as well… - Get a /29 from one of the ISPs for ptp/loops Better than RFC1918. Kind of weird. If this is from isp1 - should have no issues sourcing toward them. Might have issues (uRPF) toward isp2. Announce this via BGP / no-export to both ISPs ? Now it’s getting even weirder… - Use my own PI space Should have no filtering issues at all. Now I have to deagg my /24 and use the pieces (largest /25). Am I making too big of a deal of this ? If you’ve read this far - I do appreciate it. Anxious to hear feedback on this. PS: I would likely ACL on my upstream interfaces to block direct packets to my routers themselves as well.

6 11

RE: Google IP Geolocation
by Michael K. Spears 26 Mar '21

26 Mar '21

Sweet, that’s massively helpful. I just found the link to request access to the Google ISP portal. Thank you, Michael K. Spears From: Brendan Halley <brendan(a)halley.net.au> Sent: Friday, March 26, 2021 6:18 PM To: Michael K. Spears <michael(a)spears.io> Subject: Re: Google IP Geolocation Hey, Google ISP portal is your best bet. Can do it self service. Another way is to get a few Android devices onto the IP range. Google use them heavily for working out Geo. Brendan On Sat, 27 Mar 2021, 9:14 am Michael K. Spears, <michael(a)spears.io<mailto:michael@spears.io>> wrote: Anyone have a good contact at Google who can help with IP geolocation? I have a /24 where anything related to Google is in the wrong language. Thank you, Michael K. Spears

1 0

FCC seeks information about wireless service provider's disaster prepardness
by Sean Donelan 26 Mar '21

26 Mar '21

The same FCC which keeps outage reports secret from the public (and congress?), is seeking information about wireless service provider's safety measures during disasters. https://docs.fcc.gov/public/attachments/DA-21-362A1.pdf How have mobile wireless service providers addressed and improved network reliability in the face of natural disasters? Overall, what resiliency measures are most effective? How can these measures be improved? How have customers responded to new measures? We specifically seek comment on steps wireless mobile providers have taken to ensure network resiliency, including but not limited to: back up power in areas prone to planned power outages to mitigate wildfires; pre-storm staging processes; roaming agreements that can be activated quickly following a natural disaster; effective coordination with power companies, municipalities, and backhaul providers; diversification of backhaul options in disaster prone areas; availability of deployable network assets; network infrastructure sharing among operators during natural disasters; and communicating disaster-related information with customers, particularly members of vulnerable populations, including individuals who are low-income, members of the disabilities community, or non-English speaking. Are there successful network resiliency policy measures for fixed networks that have been applied to wireless networks, especially given that much of the backhaul for wireline providers is the same as wireless providers? We also seek comment on cost and benefit issues associated with implementing measures to maintain and improve resiliency of mobile wireless networks.

1 0

Weekly Routing Table Report
by cscora＠apnic.net 26 Mar '21

26 Mar '21

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 27 Mar, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 853765 Prefixes after maximum aggregation (per Origin AS): 323350 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 405865 Total ASes present in the Internet Routing Table: 70923 Prefixes per ASN: 12.04 Origin-only ASes present in the Internet Routing Table: 61009 Origin ASes announcing only one prefix: 25176 Transit ASes present in the Internet Routing Table: 9914 Transit-only ASes present in the Internet Routing Table: 307 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 38 Max AS path prepend of ASN ( 37385) 33 Prefixes from unregistered ASNs in the Routing Table: 971 Number of instances of unregistered ASNs: 975 Number of 32-bit ASNs allocated by the RIRs: 35515 Number of 32-bit ASNs visible in the Routing Table: 29547 Prefixes from 32-bit ASNs in the Routing Table: 137633 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 512 Number of addresses announced to Internet: 2909527424 Equivalent to 173 /8s, 107 /16s and 221 /24s Percentage of available address space announced: 78.6 Percentage of allocated address space announced: 78.6 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 289671 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 226292 Total APNIC prefixes after maximum aggregation: 65353 APNIC Deaggregation factor: 3.46 Prefixes being announced from the APNIC address blocks: 222401 Unique aggregates announced from the APNIC address blocks: 89095 APNIC Region origin ASes present in the Internet Routing Table: 11418 APNIC Prefixes per ASN: 19.48 APNIC Region origin ASes announcing only one prefix: 3248 APNIC Region transit ASes present in the Internet Routing Table: 1619 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6573 Number of APNIC addresses announced to Internet: 772179200 Equivalent to 46 /8s, 6 /16s and 133 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-143673 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 244801 Total ARIN prefixes after maximum aggregation: 112519 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 245330 Unique aggregates announced from the ARIN address blocks: 117363 ARIN Region origin ASes present in the Internet Routing Table: 18764 ARIN Prefixes per ASN: 13.07 ARIN Region origin ASes announcing only one prefix: 6804 ARIN Region transit ASes present in the Internet Routing Table: 1932 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 30 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3780 Number of ARIN addresses announced to Internet: 1144306688 Equivalent to 68 /8s, 52 /16s and 188 /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: 243349 Total RIPE prefixes after maximum aggregation: 113363 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 239232 Unique aggregates announced from the RIPE address blocks: 140771 RIPE Region origin ASes present in the Internet Routing Table: 27822 RIPE Prefixes per ASN: 8.60 RIPE Region origin ASes announcing only one prefix: 11942 RIPE Region transit ASes present in the Internet Routing Table: 3892 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10051 Number of RIPE addresses announced to Internet: 710691456 Equivalent to 42 /8s, 92 /16s and 74 /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: 112916 Total LACNIC prefixes after maximum aggregation: 26496 LACNIC Deaggregation factor: 4.26 Prefixes being announced from the LACNIC address blocks: 114028 Unique aggregates announced from the LACNIC address blocks: 48190 LACNIC Region origin ASes present in the Internet Routing Table: 10742 LACNIC Prefixes per ASN: 10.62 LACNIC Region origin ASes announcing only one prefix: 2674 LACNIC Region transit ASes present in the Internet Routing Table: 2024 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 33 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8346 Number of LACNIC addresses announced to Internet: 174829312 Equivalent to 10 /8s, 107 /16s and 175 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 25435 Total AfriNIC prefixes after maximum aggregation: 4872 AfriNIC Deaggregation factor: 5.22 Prefixes being announced from the AfriNIC address blocks: 32262 Unique aggregates announced from the AfriNIC address blocks: 9978 AfriNIC Region origin ASes present in the Internet Routing Table: 1458 AfriNIC Prefixes per ASN: 22.13 AfriNIC Region origin ASes announcing only one prefix: 508 AfriNIC Region transit ASes present in the Internet Routing Table: 293 Average AfriNIC Region AS path length visible: 5.2 Max AfriNIC Region AS path length visible: 38 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 797 Number of AfriNIC addresses announced to Internet: 107100928 Equivalent to 6 /8s, 98 /16s and 59 /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 6259 9045 61 CMNET-GD Guangdong Mobile Communication 7545 5724 783 673 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4813 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3538 1330 21 VIETEL-AS-AP Viettel Group, VN 7713 3524 1014 58 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2908 1896 55 VNPT-AS-VN VNPT Corp, VN 4766 2436 11104 565 KIXS-AS-KR Korea Telecom, KR 9498 2316 482 231 BBIL-AP BHARTI Airtel Ltd., IN 4755 2147 441 190 TATACOMM-AS TATA Communications formerl 45090 2097 1197 71 CNNIC-TENCENT-NET-AP Shenzhen Tencent C Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 4904 9258 2208 AMAZON-02, US 11492 4747 315 704 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 22773 3910 2998 245 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3393 1760 2409 AKAMAI-AS, US 6327 3360 1317 72 SHAW, CA 30036 2540 372 93 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2527 5054 486 CENTURYLINK-US-LEGACY-QWEST, US 5650 2346 2998 1637 FRONTIER-FRTR, US 5972 2214 448 787 DNIC-ASBLK-05800-06055, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 47331 7740 1041 3484 TTNET, TR 12479 6405 1701 138 UNI2-AS, ES 20940 3557 3347 202 AKAMAI-ASN1, NL 39891 3266 187 22 ALJAWWALSTC-AS, SA 8551 3222 379 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2899 2284 898 ROSTELECOM-AS, RU 9009 2375 246 1277 M247, GB 34984 2183 355 582 TELLCOM-AS, TR 13188 1610 100 31 TRIOLAN, UA 58224 1570 881 572 TCI, IR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8480 3472 570 Uninet S.A. de C.V., MX 10620 3411 527 604 Telmex Colombia S.A., CO 11830 2539 369 63 Instituto Costarricense de Electricidad 7303 1872 1732 296 Telecom Argentina S.A., AR 13999 1651 446 427 Mega Cable, S.A. de C.V., MX 6503 1442 311 475 Axtel, S.A.B. de C.V., MX 28573 1392 2269 222 CLARO S.A., BR 3816 1210 623 154 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1127 377 39 Telefonica del Peru S.A.A., PE 11664 1002 212 401 Techtel LMDS Comunicaciones Interactiva Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1581 393 22 LINKdotNET-AS, EG 24835 1443 486 27 RAYA-AS, EG 36992 1194 1537 174 ETISALAT-MISR, EG 36903 977 510 104 MT-MPLS, MA 29571 710 68 11 ORANGE-COTE-IVOIRE, CI 6713 540 1863 34 IAM-AS, MA 36935 514 522 40 Vodafone-, EG 37342 487 32 1 MOVITEL, MZ 15399 452 47 17 WANANCHI-, KE 23889 447 232 16 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8480 3472 570 Uninet S.A. de C.V., MX 47331 7740 1041 3484 TTNET, TR 12479 6405 1701 138 UNI2-AS, ES 9808 6259 9045 61 CMNET-GD Guangdong Mobile Communication 7545 5724 783 673 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 4904 9258 2208 AMAZON-02, US 4538 4813 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4747 315 704 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 22773 3910 2998 245 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 6405 6267 UNI2-AS, ES 9808 6259 6198 CMNET-GD Guangdong Mobile Communication Co.Ltd. 7545 5724 5051 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4813 4739 ERX-CERNET-BKB China Education and Research Net 47331 7740 4256 TTNET, TR 11492 4747 4043 CABLEONE, US 7155 4030 3998 VIASAT-SP-BACKBONE, US 22773 3910 3665 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3538 3517 VIETEL-AS-AP Viettel Group, VN 7713 3524 3466 TELKOMNET-AS-AP PT Telekomunikasi Indonesia, ID 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 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.142.80.0/24 Origin: 397881 STINGERS, US Transit: 398481 REDMERCURY, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:10 /9:12 /10:40 /11:102 /12:292 /13:576 /14:1183 /15:1946 /16:13515 /17:8328 /18:13797 /19:25791 /20:42402 /21:51347 /22:106418 /23:90554 /24:496041 /25:1411 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 47331 6918 7740 TTNET, TR 12479 5359 6405 UNI2-AS, ES 11492 3801 4747 CABLEONE, US 6327 3165 3360 SHAW, CA 7155 3118 4030 VIASAT-SP-BACKBONE, US 8151 3052 8480 Uninet S.A. de C.V., MX 22773 2952 3910 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3266 ALJAWWALSTC-AS, SA 8551 2686 3222 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2237 2540 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1877 2:1107 3:94 4:20 5:3567 6:64 7:5 8:1503 9:1 11:36 12:1750 13:352 14:2327 15:73 16:15 17:317 18:93 20:129 22:188 23:4596 24:2391 25:2 27:2500 31:2267 32:113 34:3 35:40 36:1282 37:3761 38:2071 39:607 40:153 41:3836 42:924 43:2120 44:239 45:14958 46:3684 47:320 49:1624 50:1754 51:92 52:1203 54:216 55:752 56:7 57:57 58:1736 59:1207 60:890 61:2395 62:2203 63:1973 64:5273 65:2382 66:5122 67:2885 68:1160 69:4047 70:1403 71:686 72:3171 74:2580 75:1482 76:684 77:2006 78:3665 79:2411 80:1841 81:1632 82:1352 83:1110 84:1263 85:3345 86:710 87:1786 88:2706 89:3017 90:423 91:7278 92:1745 93:2555 94:3042 95:4407 96:1257 97:344 98:986 99:970 100:89 101:1049 102:1293 103:25741 104:3696 105:426 106:720 107:2225 108:704 109:3962 110:1993 111:2937 112:1933 113:1622 114:1463 115:1877 116:1891 117:2293 118:2323 119:1894 120:1115 121:1086 122:2295 123:2185 124:1572 125:2101 128:1365 129:948 130:827 131:2026 132:746 133:355 134:1590 135:289 136:743 137:912 138:2301 139:1182 140:738 141:1183 142:1114 143:1274 144:1252 145:333 146:1391 147:1294 148:2203 149:1438 150:793 151:1088 152:1552 153:390 154:2272 155:1337 156:1510 157:1169 158:925 159:2032 160:2078 161:1135 162:3244 163:981 164:1494 165:1336 166:598 167:1778 168:3580 169:662 170:4282 171:763 172:2118 173:2945 174:968 175:1091 176:3067 177:4344 178:2895 179:1961 180:2269 181:2589 182:3208 183:1809 184:2411 185:18100 186:4197 187:3123 188:3304 189:2846 190:8891 191:1490 192:10611 193:7970 194:6539 195:4697 196:2908 197:2331 198:6038 199:6029 200:7408 201:5351 202:10597 203:10128 204:4652 205:3319 206:3527 207:3324 208:3999 209:4650 210:4258 211:2207 212:3675 213:3283 214:1214 215:61 216:6186 217:2521 218:1146 219:703 220:2073 221:974 222:968 223:1860 End of report

1 0

Cox Outage - a little humor for the day
by Chris Moody 25 Mar '21

25 Mar '21

Apologies in advance for the random message to the board, but it IS provider-related and gave me a good chuckle. Sometimes the timing of events just presents it's own humor in beautiful ways. My wife's office just lost all connectivity and they received a status notification from Cox Communications. While checking the company's twitter for any status announcements, Cox had posted the following webinar just an hour ago. Cheers, -Chris -- Node-Nine, Inc. chris(a)node-nine.com 619.354.6463

4 4

Re: ASE - 100 Gig Wave
by Tom Beecher 25 Mar '21

25 Mar '21

CC back to the mailing list for visibility, since I ate the CC list. On Thu, Mar 18, 2021 at 1:31 PM Tom Beecher <beecher(a)beecher.cc> wrote: > Rod- > > Please refer to the usage guidelines found here. > https://nanog.org/resources/usage-guidelines/ > > 14. Posts that encourage or facilitate an agreement about the following >> subjects are inappropriate: prices, discounts, or terms or conditions of >> sale; salaries; benefits, profits, profit margins, or cost data; market >> shares, sales territories, or markets; allocation of customers or >> territories; or selection, rejection, or termination of customers or >> suppliers. > > > I would tend to agree that while most of your posts to the list are > within the guidelines, there have been occasions where a reasonable person > could think you might be skirting the line a bit. In this case : > > - Your company works as a broker to procure capacity for others. > - You sent an email to the list that wording wise would be exactly the > same as many of us might send to someone they were looking for capacity > from. > > I think most would agree this is pretty clearly against both the usage > guidelines and the spirit of what this mailing list is about. > > I would also like to remind you that this list is administered by the > NANOG organization. You have no authority to tell others to 'cease and > desist', and insult someone as 'underemployed' is also not well tolerated > here. > > I have looped in the list admins here. It would probably be a good idea to > refrain from future messages that are clearly commercial in nature, or that > contain unnecessary insults. > > On Thu, Mar 18, 2021 at 11:28 AM Rod Beck <rod.beck(a)unitedcablecompany.com> > wrote: > >> Actually, that language was intended to prohibit soliciting business and >> not asking for help. I have some hard words to describe like Shane Ronan, >> but I will forbear. >> >> I suggest you cease and desist before this gets ugly. Obviously you are >> underemployed. >> >> Get some work to do. >> >> Best, >> >> -R. >> >> >> >> ------------------------------ >> *From:* sronan(a)ronan-online.com <sronan(a)ronan-online.com> >> *Sent:* Thursday, March 18, 2021 4:24 PM >> *To:* Rod Beck <rod.beck(a)unitedcablecompany.com>; NANOG Operators' Group >> <nanog(a)nanog.org> >> *Cc:* Shane Ronan <shane(a)ronan-online.com> >> *Subject:* Re: ASE - 100 Gig Wave >> >> Please review the Mailing List policies which specifically prohibit >> commercial discussions on the list. I would ask the list moderators to >> chime in here please >> >> Shane >> >> On Mar 18, 2021, at 11:14 AM, Rod Beck <rod.beck(a)unitedcablecompany.com> >> wrote: >> >> >> People post requests all the time. You are free to block me. And I know >> the majority of uses disagree with you. >> >> ------------------------------ >> *From:* Shane Ronan <shane(a)ronan-online.com> >> *Sent:* Thursday, March 18, 2021 4:11 PM >> *To:* Rod Beck <rod.beck(a)unitedcablecompany.com> >> *Cc:* nanog(a)nanog.org <nanog(a)nanog.org> >> *Subject:* Re: ASE - 100 Gig Wave >> >> NANOG is not a service for receiving details on cable paths for >> commercial purposes. Please find somewhere else to collect this information. >> >> On Thu, Mar 18, 2021 at 10:54 AM Rod Beck < >> rod.beck(a)unitedcablecompany.com> wrote: >> >> This cable is tapped out and I need a 100 gig wave from Hong Kong to >> Singapore. 3 year term. >> >> Roderick Beck >> Global Network Capacity Procurement >> >> United Cable Company >> www.unitedcablecompany.com >> https://unitedcablecompany.com/video/ >> New York City & Budapest >> >> rod.beck(a)unitedcablecompany.com >> >> Budapest: 36-70-605-5144 >> >> NJ: 908-452-8183 >> >> >> >> [image: 1467221477350_image005.png] >> >>

43 86

Reinventing the wheel on a path to deeper learning
by NANOG News 24 Mar '21

24 Mar '21

We’d be hard pressed to name many teenagers as thoughtful, curious, and open to new experiences as Nate Sales. Now in his junior year at the Catlin Gabel School in Portland, Oregon, he has already built, designed, and engineered more than most people twice his age. Nate not only manages his school’s robotics team, he also developed an app to track on-campus movement during COVID 19, coordinates radio communications for the Amateur Radio Emergency Service, is a Reliability Engineer at Fosshost, and sits on the advisory board of the Emerald Onion — a Seattle nonprofit and encrypted transit ISP. We spoke with Nate recently about his path into tech, and his experience presenting at a NANOG conference, where he was — to our collective knowledge — the youngest to ever do so. What struck us most was his curiosity and willingness to build, dismantle, and rebuild again in the name of new discoveries and greater insights; an ethos all of us could stand to learn from. Read the Feature - Read the Feature <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…>

7 6

Re: Perhaps it's time to think about enhancements to the NANOG list...?
by J. Hellenthal 24 Mar '21

24 Mar '21

Nail -> Head <- Hammer Well put ! I don’t know if it could have been put better than that. -- J. Hellenthal The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume. > On Mar 23, 2021, at 10:57, Emil Pfeffer <emu(a)emuadmin.com> wrote: > > On Tue, Mar 23, 2021 at 09:20:14AM -0500, Mike Hammett wrote: >> "But why it should or shouldn't be clicked..." >> Sorta like most man pages. > > They both need prior knowledge to use. > We tend to simplify things in order to save time but then the new generation comes > in and thinks the simple things it's all there is and have no willingness to go > back in time and accumulate "useless" knowledge. It is useless because the problems > it fixes were already fixed but it is paramount in understanding whats behind the > simple things. Knowledge can only be simplified so much and there's no shortcut to > accumulating it. (hence why most people will prefer to just use the tools) > > The generational gap is not an issue it is how things need to be. The network > engineering the younger generation deals with is not the same networking the old > generation deals with but built upon this old networks. This two generations do > not need the same knowledge and it is in each others best interest that they stay > separated. Although we would gladly help someone that is obviously putting in the > effort and is looking to learn we have not volunteered to be teachers and some people > need to understand that we prefer to keep it simple because we have no time to waste. > > It is easy to believe that the method you are using is the one but eventually > the good ones will have to pass the test of time which mailling lists and a plethora > of the old tools successfully did. > --

1 0

OAuth for RIRs - There is already any Idea like that?
by Douglas Fischer 24 Mar '21

24 Mar '21

For me, every day it becomes more evident the need to validate information managed by the RIRs / NIRs / LIRs on separate information platforms. A very simple example is PeeringDB itself, which requires confirmation of correlation between the ASN whois contact and the account that is registering the organization. P.S.1: At least for me, this is more evident when it comes to numerical resources, but without going much deeper into the analysis, I believe that this is also applicable to name resources. I was wondering how complex it would be for RIRs / NIRs to implement some mechanism similar to the OAuth of NIC-Handler accounts to, through a delimitation protocol, allow accounts between information platforms to be correlated, information to be confirmed and maybe even inserted and updated. Still dreaming a little bit about the possibilities, I imagined that in a federation context, IANA or NRO could correlate NIC-Handlers from the same organization in different RIRs. In addition to the PeeringDB example, other uses (non-exhaustive list) of this solution could be: - Linking between Maintainers of IRR bases and owners of resources in RIRs. - Linking between accounts on the basis of IXPs, and ASN owners. - Authentication and integration of RPKI CA Delegate services. I believe that we are already at a point where we can go beyond just using email confirmation. OAuth and similar protocols include benefits such as: - Simplified use of cryptographic protections - Specific definition of the duration of the authorization. - Forced expiration of authorization. - Granular definition of which attributes will have read-only or read and write access. I know that for a person with little experience everything seems possible, and for more hardened people things do not seem that simple. I also know that not everything in this world depends only on technological feasibility. For although there may be protocols and techniques to solve a problem, many questions depend on the layer 9 definitions of the OSI model. P.S.2: To be honest, I don't know if there are already initiatives in this direction from the point of view of making this a standard resource. But unless I am mistaken, https://www.denic.de/ already has something similar in place. -- Douglas Fernando Fischer Engº de Controle e Automação

2 1

Peering and Caching for Epic Games, Fortnite, et al
by Jose Luis Rodriguez 23 Mar '21

23 Mar '21

We run a healthy-sized ISP (say, 2.5M households, plus enterprise, etc ) and we really, REALLY want to make sure our users have an amazing experience when downloading the neverending Fortnite/Spacequest/Blizzard/DigDug updates that run down our pipes. Would love to hear from others about how they're peering and caching -- not having the level of success I'd want with the typical "aggregators" (they know who they are ) and would really like to link to the source even if it means trenching through the core of the Earth... Would love pointers, names, or any leads, on or off list. Thanks Jose L. Rodriguez CTO, Totalplay

9 8