AI-Driven Wireless Is Key to the Digital Workplace
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.
More on Leaky Abstractions
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.
Getting start with RSVP
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 Still Doesn’t Have a CEO, Reports Q4 Revenue Miss
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’s Cloud Playbook Goes ‘All Out’ for AI
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.
Netskope IDs New Google Cloud Attack, McAfee Finds Ransomware
Threat researchers at Netskope and McAfee this week described new and potentially dangerous networking vulnerabilities.
Linux Foundation Launches LF Edge Group With 5 Projects
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.
Vodafone Loses Its Head of Cloud, Automation Fran Heeran to Nokia
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.
IBM’s Multi-Million Dollar Cloud Wins Keep on Coming
Another day, another multi-million dollar cloud deal for IBM, which signed a $260 million agreement with the Bank of the Philippine Islands.
HTTP/3: From root to tip
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 Becomes First CNCF Graduate of 2019
CoreDNS replaced kube-dns as the default DNS server in the most recent update of Kubernetes. It is the fourth project to graduate CNCF.
EU Trumpets 5G Progress as Number of Trials Hits 138
The most important 5G pilot in the EU to date, according to the report, was carried out by Elisa in Finland because it used at least two cell sites and involved end users.
Thoughts before CLEUR 2019
In just 3 days time I will be leaving for Cisco Live 2019 in Barcelona. Im thinking about what sort of event it will be and what to expect in term of announcements.
Especially one thought keeps reappearing and thats the thought of the transformation of Cisco. It is no longer a company with a future in just selling hardware. It itself has been disrupted by the emergence of “everything software” and merchant silicon.
The issues and consequences of merchant silicon has been discussed in many places, so I won’t mention them in this post, other than saying it has in some way forced Cisco’s hands in going down the route of being a software and services company.
Especially the software component will be huge this year. If you need proof of this, just look at the very large following as well as events from the Cisco DevNet community. But is this transformation smooth sailing from here? — I think not.
Traditionally Cisco’s reputation in the industry when it comes to software has been very flaky, to say the least. Something a lot of engineers hope will change in the coming years.
That being said, I think a lot of Continue reading