Calculating best path can be a complex process in many typologies. In this Network Collective Short Take, Russ shares how routers process BGP updates and the intricacies of how those routes are shared with peers.
The post Short Take – Duplicate BGP Updates appeared first on Network Collective.


At Cloudflare, we aim to make the Internet faster and safer for everyone. One way we do this is through caching: we keep a copy of our customer content in our 165 data centers around the world. This brings content closer to users and reduces traffic back to origin servers.
Today, we’re excited to announce a huge change in our how cache works. Cloudflare Workers now integrates the Cache API, giving you programmatic control over our caches around the world.
Figuring out what to cache and how can get complicated. Consider an e-commerce site with a shopping cart, a Content Management System (CMS) with many templates and hundreds of articles, or a GraphQL API. Each contains a mix of elements that are dynamic for some users, but might stay unchanged for the vast majority of requests.
Over the last 8 years, we’ve added more features to give our customers flexibility and control over what goes in the cache. However, we’ve learned that we need to offer more than just adding settings in our dashboard. Our customers have told us clearly that they want to be able to express their ideas in code, to build Continue reading

The IPNSIG (InterPlanetary Networking Special Interest Group) has been a Chapter of the Internet Society since February 2014. We are pleased to announce that we recently created a blog dedicated to everyone interested in IPN and DTN, and computer networking in general. It is a first step in providing nonspecialists with easy-to-understand explanations of what IPN is and how it works. Each week, we will post news about the exciting world of IPN, summaries of academic research, or links to IPN in the mainstream media. We’ll also be announcing upcoming IPNSIG events and activities.
Our mission
We aim to realize a functional and scalable system of interplanetary data communications before the year 2020. We will accomplish this objective by engaging the public’s interest in funding and executing the research and technology development necessary to make InterPlanetary Networking (IPN) a reality. We will educate them about the critical need for a reliable, scalable space data network to enable cost-effective exploration and eventual commercial use of the inner solar system. We will excite them about the potential role these same network systems technologies can play in solving communication problems here on earth.
What is IPN?
It is a solution to the constrained Continue reading
The vision of a mobile-first workplace is one where people communicate, interact, and transact in an intuitive and frictionless manner. AI-driven wireless networks are key to making that vision a reality.
When I was writing the Back to Basics blog post I reread the Law of Leaky Abstractions masterpiece. You’ll love it – the first example Joel uses is TCP.
However, what really caught my eye was this bit:
The law of leaky abstractions means that whenever somebody comes up with a wizzy new code-generation tool that is supposed to make us all ever-so-efficient, you hear a lot of people saying “learn how to do it manually first, then use the wizzy tool to save time.”
You should apply the same wisdom to shiny new gizmos launched by network virtualization vendors… oh wait, you can’t, they are mostly undocumented black boxes. Good luck ;)
Sadly, the Law of Leaky Abstractions blog post was written in 2002… and nothing changed in the meantime, at least not for the better.
We’ve spent a great deal of time in the last few posts talking about MPLS both with LDP and with static LSP configurations. While these approaches certainly work, they aren’t the only options to use for label distribution and LSP creation. If we take static LSPs off the table (since they’re the equivalent of static routes and not scalable) we really have two main choices for label distribution – LDP and RSVP. LDP is typically considered to be the easiest of the two options but also offers a limited set of functionality. RSVP offers many more features but also requires more configuration. When you’re designing an MPLS network you’ll have to decide which protocol to use based on your requirements. In many cases a network may leverage both in different areas. In this post the aim is just to get RSVP up and running – we’ll dig into the specifics in a later post.
So let’s get right into a simple lab where we leverage RSVP instead of LDP. Like the previous post, we’ll leverage the same lab environment…

Let’s assume as before that the base configuration of the lab includes all the routers interfaces configured, OSPF enabled on all Continue reading
Intel has been on the hunt for a new CEO for more than seven months. Pundits expected the chipmaker to announce a new chief executive before or on its earnings call today.
Baidu, China’s search and ad giant, has aggressively re-focused its business on artificial intelligence and connected vehicles as the U.S.-China trade war heats up and online advertising becomes less profitable.
Threat researchers at Netskope and McAfee this week described new and potentially dangerous networking vulnerabilities.
The new group’s list of founding members reads like a who’s who of chipmakers, telecommunications companies, cloud providers, edge infrastructure vendors, and others.
This is the latest in a series of major changes at Vodafone, which just said goodbye to a number of executives and announced large real estate changes in the U.K.
Another day, another multi-million dollar cloud deal for IBM, which signed a $260 million agreement with the Bank of the Philippine Islands.

HTTP is the application protocol that powers the Web. It began life as the so-called HTTP/0.9 protocol in 1991, and by 1999 had evolved to HTTP/1.1, which was standardised within the IETF (Internet Engineering Task Force). HTTP/1.1 was good enough for a long time but the ever changing needs of the Web called for a better suited protocol, and HTTP/2 emerged in 2015. More recently it was announced that the IETF is intending to deliver a new version - HTTP/3. To some people this is a surprise and has caused a bit of confusion. If you don't track IETF work closely it might seem that HTTP/3 has come out of the blue. However, we can trace its origins through a lineage of experiments and evolution of Web protocols; specifically the QUIC transport protocol.
If you're not familiar with QUIC, my colleagues have done a great job of tackling different angles. John's blog describes some of the real-world annoyances of today's HTTP, Alessandro's blog tackles the nitty-gritty transport layer details, and Nick's blog covers how to get hands on with some testing. We've collected these and more at https://cloudflare-quic.com. And if that tickles your fancy, be sure Continue reading
CoreDNS replaced kube-dns as the default DNS server in the most recent update of Kubernetes. It is the fourth project to graduate CNCF.