I'm curious as to what actually is the CPU <-> NPU bandwidth in these whitebox OLTs? Traditionally that has been sized for small amounts of punted control plane packets, then programming a fast path into the NPU for revenue traffic.
This doesn't look like anything malicious, 8048 is just prepending these announcements to 52320.. If anything, it looks like 269832(MDS) had a couple hits to their tier 1 peers which caused these prepended announcements to become more visible to collectors.
Interesting take, but generally large, incumbent eyeball networks have refrained from open peering at IX's for decades at this point. They maintained presences, but usually just to grab a few specific peers they wanted, not to peer broadly with everyone across the exchange, and the bulk of traffic from large providers into eyeball networks comes across PNIs or on-net CDN nodes, not IX.
If anything, this move to centralized PNIaaS platforms makes interconnecting with the eyeball networks even easier for smaller providers. The portals allow for straightforward visibility on what they want to charge for paid peering, and instant automated EVCs and turnup, shortcutting the long and windy process of negotiating terms and establishing individual XCs in DCs that you agree to peer in.
My son and I listen to DMR and P25 all the time, and we listened to a bunch of the samples of Codec2 vs AMBE. And while it might be a slight improvement, it doesn't move the needle enough to really excite. Perhaps a longer QSO would be more exciting to hear the difference on. Wouldn't hardware be a constratint just like it is with M17?
At least the good guys found this one first, and it is in Windows Defender, and the definitions should automatically update in 24hrs or less silently without a reboot.
reply