Those who follow my work know I’ve been focused on building live webinars for the last year or two, but I am still creating pre-recorded material for Pearson. The latest is built from several live webinars which I no longer give; I’ve updated the material and turned them into a seven-hour course called How Networks Really Work. Although I begin here with the “four things,” the focus is on a problem/solution view of routed control planes. From the description:
There are many elements to a networking system, including hosts, virtual hosts, routers, virtual routers, routing protocols, discovery protocols, etc. Each protocol and device (whether virtual or physical) is generally studied as an individual “thing.” It is not common to consider all these parts as components of a system that works together to carry traffic through a network. To show how all these components work together to form a complete system, this video course presents a series of walk throughs showing the processing involved in various kinds of network events, and how control planes use those events to build the information needed to carry traffic through a network.
This course is largely complimentary to the course Ethan and I did a couple of years back, Understanding Network Transports. Taking both would give you a good understanding of network fundamentals. This material is also parallel and complimentary to Problems and Solutions in Computer Networks, which Ethan and I published a few years ago.
I am working on one new live webinar; I really need to get my butt in gear on another one I’ve been discussing for a long time (but I somehow dropped the ball).
I’ve started publishing in the Public Discourse on topics of technology and culture; the following is the first article they’ve accepted. Note the contents might be classified as a little controversial.
The recent “takedown” of Parler by Amazon, Apple, and Google has spurred discussion in technological circles. Do the companies’ actions constitute an abuse of free speech? Or were the tech giants well within their rights, simply enforcing their own “terms of service”? Looking back at the history of free speech in the United States, especially the historical moment during which the right to free speech was codified, can offer guidance.
I’ll be joining Jeff Tantsura, Nick Buraglio, and Brooks Westbrook for a roundtable on March 16, 9 am PST (that’s tomorrow if you’re reading this the day it publishes) about the development of wide area networking technologies up until today. This is the first part of a two part series on changes in the wide area network.
I was recently a guest on The Art of Conviction podcast, where we covered a bit of my background, some of the challenges I’ve faced in getting where I am, and then we moved into a discussion around my recently finished dissertation. I’m working to find places to publish more in the area of worldview and culture; I’ll point to those here as I can find a “home” for that side of my life.
Beyond my episode, The Art of Conviction is a fascinating podcast; you should really subscribe and listen in.
I was recently a guest on the IPv6 Buzz podcast. Ed, Scott, Tom, and I talk about IPv6 operational maturity, IPv6 standards, and the IETF process. This was a great episode, you should really listen to it … and listen to IPv6 Buzz in general.
I’m doing a series of three master classes through Juniper on various DC fabric topics—
Join Juniper’s Russ White, a widely published 30-year network engineering veteran, in a three-part masterclass exploring the data center. Choose from classes on data center fabric, physical topologies, or data center security.
From the schedule—
- Class 1: Data Center Fabric, December 2, 12 PM EST
- Class 2: Physical Topologies, January 13, 12 PM EST
- Class 3: Security in the Data Center, February 10, 12 PM EST
The commodification of networks is in full swing and everyone seems to think it is a good thing. You might hear this phrased as treating network devices like cattle, rather than pets. Or maybe you’ve heard that the network should move packets and do nothing more. Even, perhaps, that network bandwidth should be treated just like memory—you just add more when you need it.