Recent Russian Routing Leak was Largely Preventable
Last week, the IP address space belonging to several high-profile companies, including Google, Facebook and Apple, was briefly announced out of Russia, as was first reported by BGPmon.
Following the incident, Job Snijders of NTT wrote in a post entitled, “What to do about BGP hijacks”. He stated that, given the inherent security weaknesses in BGP, things will only improve “the moment it becomes socially unacceptable to operate an Internet network without adequate protections in place” and thus customers would stop buying transit from providers that operate without proper route filtering.
Since Job has presented at NANOG about the various filtering methods employed by NTT, I decided to look into how well NTT (AS2914) did in this particular incident. While a handful of the 80 misdirected routes were ultimately carried on by AS2914 to the greater internet, NTT didn’t contribute to the leaking of any of the major internet companies, such as Facebook, Google, Apple, etc. In fact, when one analyzes the propagation of every one of these leaked routes, a pattern begins to emerge.
Route Leaks by AS39523
On 12 December 2017, AS39523 announced 80 prefixes (only one of which was theirs) for two different 3-4 Continue reading
The project brings together data scientists and software engineers.
Dell EMC continues to lead the HCI vendor market, according to IDC.
Qualcomm rejects Broadcom board nominees; Ericsson, Vodafone complete pre-standard 5G test; CENX signs Open API Manifesto.
Schmidt joined the company in 2001 when it only had a few hundred employees.
This is Microsoft's second price cut this year.
The software provider is offering RMM and Helpdesk services to its customers.
We need more SD-WAN vendors to write about (and also new socks).