Author Archives: Russ
Author Archives: Russ
This post is going to be a little off the beaten path, but it might yet be useful for folks interested in the process of standardization through the IETF.
Last week, at the IETF in Buenos Aires, a proposal was put forward to move the IPv4 specifications to historic status. Geoff Huston, in his ISP column, points out the problem with this sort of thing—
The idea to push IPv4 to historic is, apparently, an attempt to move the market, in a sense. If it’s historic, then the market won’t use it, or will at least move away from it.
Right.
Another, similar, line of thinking came up at the mic during a discussion around whether Continue reading
While the IS-IS book is still useful, it is getting on a little in age, and some people find learning through video to be more helpful. I’ve recorded seven hours of video on IS-IS in the form of a LiveLesson with Cisco Press. They should be available on the 18th of April (just a few days from now), and apparently they’re already available as a sneak peek.
Thanks to Brett (who runs, and has run, all my projects at Cisco Press and Addison-Wesley), Pete (who patiently recorded my many fumbles), and Chris Cleveland, who has been my steadfast editor for all things Cisco Press and Addison-Wesley for some fifteen years now), for making this happen. This is the first, I think, of a number of new video projects I have on tap, so watch this space.
And no, I’m not going to stop writing books (just a gentle reminder).
The post IS-IS LiveLesson Publishing Soon appeared first on 'net work.
So far, in our investigation of the design mindset, we’ve—
We also considered the problem of interaction surfaces in some detail along the way. This week I want to wrap this little series up by considering the final step in design, act. Yes, you finally get to actually buy some stuff, rack it up, cable it, and then get to the fine joys of configuring it all up to see if it works. But before you do… A couple of points to consider.
It’s important, when acting, to do more than just, well, act. It’s right at this point that it’s important to be metacongnitive—to think about what we’re thinking about. Or, perhaps, to consider the process of what we’re doing as much as actually doing it. To give you two specific instances…
First, when you’re out there Continue reading
I will be speaking at NANOG on the road tomorrow—the topic is “An Introduction to Network Complexity.” If you’re in the Raleigh area, this is well worth taking the time off to come to, as the speaker lineup is fantastic.
The post Introduction to Network Complexity at NANOG on the Road appeared first on 'net work.
I’m presenting at two sessions this year at Cisco Live: BRKRST-3014, Policy, Complexity, and Modern Control Planes on Thursday afternoon, and TECCCDE-3005, The Cisco Certified Design Expert, on Sunday afternoon. If you’re attending, feel free to look me up—when I’m not speaking, I’m generally hanging out at Cisco Press, at the Certification Lounge, or just walking around the show floor.
The post Cisco Live 2016 Las Vegas appeared first on 'net work.
Before talking the final point in the network design mindset, ,act, I wanted to answer an excellent question from the comments from the last post in this series: what is surface?
The concept of interaction surfaces is difficult to grasp primarily because it covers such a wide array of ideas. Let me try to clarify by giving a specific example. Assume you have a single function that—
This single function can be considered a subsystem in some larger system. Now assume you break this single function into two functions, one of which does the addition, and the other of which does the multiplication. You’ve created two simpler functions (each one only does one thing), but you’ve created an interaction surface between the two functions—you’ve created two interacting subsystems within the system where there only used to be one. This is a really simple example, I know, but consider a few more that might help.
The post Lawful Hacking and Continuing Vulnerabilities appeared first on 'net work.
Ivan, over at ipspace.net, has an interesting post up on writing books —
Several points in reply…
No, you won’t make a lot of money. Writing books for a living (in fact, writing for a living at all) has been pretty much destroyed by several factors, including the absolute dismal rate at which our culture reads (I’m considered something of a freak with my goal of reading 100 books/year; C.S. Lewis read that many in a few weeks in the hospital, across four or five languages), and the rate at which people try to “climb the author pile” by writing for free on blogs/etc.
There is one comment here that I think is really worth pointing out: To make matters worse, core networking is not exactly a popular topic (compared to Swift Programming or Introduction to IPv6)… I’ve heard this a lot in my time as an author—for instance, my books simply don’t sell as well as just about anything at the CCIE level, Continue reading
I’m forever seeing announcements like this in the software defined networking world—
But you need to note one specific thing about this announcement. How did they achieve these forwarding rates? By using DPDK to offload the actual, well, forwarding to a custom ASIC on a NIC. The reality is that we’ve always done the control plane in software, and we’ve always done the forwarding in hardware. There have been precious few router platforms over the years where the forwarding plane is actually an “embedded system.”
Certainly we’re seeing a world where open source operating systems are learning to interact with commodity ASICs so it’s possible to separate the software from the hardware, and the operating system from the control plane, and this is all too the good. But if this is software defined networking, then we’ve been doing this since sometime in the 1990’s, perhaps even earlier…
Perhaps we’ve become so accustomed to considering the network operating Continue reading
In my last post on securing BGP, I said—
The CAP theorem post referenced above is here.
Before I dive into the technical issues, I want to return to the business issues for a moment. In a call this week on the topic of BGP security, someone pointed out that there is no difference between an advertisement in BGP asserting some piece of information (reachability or connectivity, take your pick), and an advertisements outside BGP asserting this same bit of information. The point of the question is this: if I can’t trust you to advertise the right thing in one setting, then why should I trust you to advertise the right thing in another? More specifically, if you’re using Continue reading
The post Broken Configurations, Broken Windows appeared first on 'net work.
The post Worth Reading: Don’t ask what you can measure appeared first on 'net work.
When I first started in Cisco TAC, as a lowly grade 3 engineer taking hardware RMA calls, I didn’t know anyone. I had just moved to North Carolina, we hadn’t found a church yet, I’m not the most social person on the face of the earth (in fact, if anything, I’m antisocial), and I was sitting in a cubicle surrounded by people who’d been working in serious networking for a lot longer than I had. Not only that, but a lot of them were a lot smarter than I was (and still are). These people were really busy; it was hard to sip from the firehose, and I really needed to find my way around. How could I go about building a network?
What to do… ??
I put a candy jar on my desk, and filled it with interesting candy. How would a candy jar work? Well, it attracted all sorts of interesting people to my desk throughout the day, and as I got to know what different people liked, it gave me an excuse to bring stuff to their desk—along with a question about a case I was working on, of course. In a sense, I learned all I Continue reading