Stop Using the OSI Model

2 September 2019 |

We all use the OSI model to describe the way networks work. I have, in fact, included it in just about every presentation, and every book I have written, someplace in the fundamentals of networking. But if you have every looked at the OSI model and had to scratch your head trying to figure out how it really fits with the networks we operate today, or what the OSI model is telling you in terms of troubleshooting, design, or operation—you are not alone. Lots of people have scratched their heads about the OSI model, trying to understand how it fits with modern networking. There is a reason this is so difficult to figure out.

The OSI Model does not accurately describe networks.

What set me off in this particular direction this week is an article over at Errata Security:

The OSI Model was created by international standards organization for an alternative internet that was too complicated to ever work, and which never worked, and which never came to pass. Sure, when they created the OSI Model, the Internet layered model already existed, so they made sure to include today’s Internet as part of their model. But the focus and intent of the OSI’s efforts was on dumb networking concepts that worked differently from the Internet.

DNS Query Minimization and Data Leaks

26 August 2019 |

When a recursive resolver receives a query from a host, it will first consult any local cache to discover if it has the information required to resolve the query. If it does not, it will begin with the rightmost section of the domain name, the Top Level Domain (TLD), moving left through each section of the Fully Qualified Domain Name (FQDN), in order to find an IP address to return to the host, as shown in the diagram below.

This is pretty simple at its most basic level, of course—virtually every network engineer in the world understands this process (and if you don’t, you should enroll in my How the Internet Really Works webinar the next time it is offered!). The question almost no-one ever asks, however, is: what, precisely, is the recursive server sending to the root, TLD, and authoritative servers?

History of YANG with Phil Shafer

20 August 2019 | Comments Off on History of YANG with Phil Shafer

YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols, described in RFC7950. The origins of YANG are rooted in work Phil Shafer did in building an interface system for JUNOS. Phil joins us on this episode of the History of Networking to discuss the history of YANG.

History of SNMP with Craig Partridge

6 August 2019 |

The Simple Network Management Protocol, or SNMP, was originally specified in RFC1067, and most recently in RFC1157. The original intent was to make “all IP and TCP implementations be network manageable”—an early form of providing a machine-readable interface so operators could “automate all the things.” Craig Partridge played a key role in the early development and standardization of SNMP; he joins us on the History of Networking to discuss the origins and challenges involved in developing SNMP.

The Hedge Episode 2: Jeff Tantsura and Intent Based Networking

30 July 2019 |

Jeff Tantsura recently co-authored a draft in the IRTF defining some of the concepts and parameters for intent based networking. Jeff joins Tom Ammon and Russ White to dig into this new area, and what it means for networks.

https://www.ietf.org/id/draft-clemm-nmrg-dist-intent-02.txt

Dave Piscatello: IP and CLNS in the Early Interenet

23 July 2019 | Comments Off on Dave Piscatello: IP and CLNS in the Early Interenet

Early in the history of the Internet, there were serious discussions about whether IP or CLNS should be adopted. Dave Piscatello joins this episode of the History of Networking to discuss how and why the decision to standardize on IP was made.

The Floating Point Fix

15 July 2019 | Comments Off on The Floating Point Fix

Floating point is not something many network engineers think about. In fact, when I first started digging into routing protocol implementations in the mid-1990’s, I discovered one of the tricks you needed to remember when trying to replicate the router’s metric calculation was always round down. When EIGRP was first written, like most of the rest of Cisco’s IOS, was written for processors that did not perform floating point operations. The silicon and processing time costs were just too high.

What brings all this to mind is a recent article on the problems with floating point performance over at The Next Platform by Michael Feldman. According to the article:

While most programmers use floating point indiscriminately anytime they want to do math with real numbers, because of certain limitations in how these numbers are represented, performance and accuracy often leave something to be desired.

History of ATM

25 June 2019 | Comments Off on History of ATM

In these two episodes of the History of Networking, Dan Grossman joins Donald and I to discuss the history of Asynchronous Transfer Mode (ATM). While this is a technology that is no longer widely used, it had a major influence on the networking world.

https://historyofnetworking.s3.amazonaws.com/Dan+Grossman+-+ATM+01.mp3

https://historyofnetworking.s3.amazonaws.com/Dan+Grossman+-+ATM+02.mp3

For future History of Networking episodes, please subscribe to https://rule11.tech/category/hon/feed/ in your podcast application or RSS reader.

The next episode, OSI and IP with Dave Piscatello, will be released on the 9th of July.

These recordings are non-commercial and can be syndicated so long as they are not modified or advertising added—if you would like to distribute these recordings on your podcast channel, please get in touch with me.

It’s not a CLOS, it’s a Clos

17 June 2019 | Comments Off on It’s not a CLOS, it’s a Clos

Way back in the day, when telephone lines were first being installed, running the physical infrastructure was quite expensive. The first attempt to maximize the infrastructure was the party line. In modern terms, the party line is just an Ethernet segment for the telephone. Anyone can pick up and talk to anyone else who happens to be listening. In order to schedule things, a user could contact an operator, who could then “ring” the appropriate phone to signal another user to “pick up.” CSMA/CA, in essence, with a human scheduler.

This proved to be somewhat unacceptable to everyone other than various intelligence agencies, so the operator’s position was “upgraded.” A line was run to each structure (house or business) and terminated at a switchboard. Each line terminated into a jack, and patch cables were supplied to the operator, who could then connect two telephone lines by inserting a jumper cable between the appropriate jacks.

An important concept: this kind of operator driven system is nonblocking. If Joe calls Susan, then Joe and Susan cannot also talk to someone other than one another for the duration of their call. If Joe’s line is tied up, when someone tries to call him, they will receive a busy signal. The network is not blocking in this case, the edge is—because the node the caller is trying to reach is already using 100% of its available bandwidth for an existing call. Blocking networks did exist in the form of trunk connections, or connections between these switch panels. Trunk connections not only consume ports on the switchboard, they are expensive to build, and they require a lot of power to run. Hence, making a “long distance call” costs money because it consumes a blocking resource. It is only when we get to packet switched digital networks that the cost of a “long distance call” drops to the rough equivalent of a “normal” call, and we see “long distance” charges fade into memory (many of my younger readers have never been charged for “long distance calls,” in fact, and may not even know what I’m talking about).

Service Fabrics

28 May 2019 | Comments Off on Service Fabrics