Russ

Author Archives: Russ

What should IETF “standard track” actually mean?

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—

As one commenter in the Working Group session pointed out, declaring IPv4 “Historic” would likely backfire and serve no better purpose other than exposing the IETF to ridicule. And certainly there is some merit in wondering why a standards body would take a protocol specification used by over 3 billion people, and by some estimated 10 billion devices each and every day and declare it to be “Historic”. In any other context such adoption figures for a technology would conventionally be called “outstandingly successful”!

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.

reaction-02Another, similar, line of thinking came up at the mic during a discussion around whether Continue reading

IS-IS LiveLesson Publishing Soon

is-is-livelessonWhile 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).

LinkedInTwitterGoogle+FacebookPinterest

The post IS-IS LiveLesson Publishing Soon appeared first on 'net work.

The Design Mindset (5)

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…

ooda-complexityFirst, when you’re out there Continue reading

Cisco Live 2016 Las Vegas

logoI’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.

LinkedInTwitterGoogle+FacebookPinterest

The post Cisco Live 2016 Las Vegas appeared first on 'net work.

The Design Mindset (4)—Interaction Surfaces

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—

  • Accepts two numbers as input
  • Adds them
  • Multiplies the resulting sum by 100
  • Returns the result

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 routing information carried in OSPF is split up into external routes being carried in BGP, and internal rotues being carried in OSPF. You’ve gone from one system with more Continue reading

Writing books still matters—reading them does, too

Ivan, over at ipspace.net, has an interesting post up on writing books —

Why would you want to write a book? If you think you’ll earn a lot of money, think twice… unless you plan to write a science fiction bestseller, Swift-for-Dummies, or 50 Shades of Something.

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