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
The post Worth Reading: Are we headed to another bust? appeared first on 'net work.
The post Worth Reading: The road to 200g appeared first on 'net work.
The post Worth Reading: The end of Moore’s Law? appeared first on 'net work.
Edge provider networks, supporting DSL, voice, and other services to consumers and small businesses, tend to be more heavily bound by vendor specific equipment and hardware centric standards. These networks are built around the more closed telephone standards, rather than the more open internetworking standards, and hence they tend to be more expensive to operate and manage. As one friend said about a company that supplies this equipment, “they just print money.” The large edge providers, such as AT&T and Verizon, however, are not endless pools of money. These providers are in a squeeze between the content providers, who are taking large shares of revenue, and consumers, who are always looking for a lower price option for communications and new and interesting services.
If this seems like an area that’s ripe for virtualization to you, you’re not alone. AT&T has been working on a project called CORD for a few years in this area; they published a series of papers on the topic that make for interesting reading:
The post Worth Reading: Yellow journalism on encryption appeared first on 'net work.
Over at Packet Pushers, there’s an interesting post asking why we don’t use actual user traffic to detect network failures, and hence to drive routing protocol convergence—or rather, asking why routing doesn’t react to the data place.
This is, indeed, an interesting question—and ones that’s highly relevant in our current software defined/drive world. So why not? Let me give you two lines of thinking that might be used to answer this question.
First, let’s consider the larger problem of fast convergence. Anyone who’s spent time in any of my books, or sat through any of my presentations, should know the four steps to convergence—but just in case, let’s cover them again, using a slide from my forthcoming LiveLesson on IS-IS:
There Continue reading
The post Worth Reading: Trademarking hashtags appeared first on 'net work.
So you’ve spent time asking what, observing the network as a system, and considering what has actually been done in the past. And you’ve spent time asking why, trying to figure out the purpose (or lack of purpose) behind the configuration and design choices made in the past. You’ve followed the design mindset to this point, so now you can jump in and make like a wrecking ball (or a bull in a china shop), changing things so they’re better, and the new requirements you have can fit right in. Right?
Wrong.
As an example, I want to take you back to another part of a story I told here about my early days in the networking world. Before losing the war over Banyan Vines, I actually encountered an obstacle that should have been telling—but I was too much of a noob at the time to recognize it for the warning it really was. At the time, I had written a short paper comparing Vines to Netware; the paper was, perhaps, ten pages long, and I thought it did a pretty good job of comparing the two network operating systems. Heck, I’d even put together a page showing how Vines Continue reading
The post Worth Reading: Building a (human) network, part 2 appeared first on 'net work.
The post Worth Reading: Free market needs some sunshine appeared first on 'net work.
In 2000, Eric Brewer was observing and discussing the various characteristics of database systems. Through this work, he observed that a database generally has three characteristics—
Brewer, in explaining the relationship between the three in a 2012 article, says—
The CAP theorem, therefore, represents a two out of three situation—yet another two out of three “set” we encounter in the real world, probably grounded someplace in the larger space of complexity. We’ll leave the relationship to complexity on the side for the moment, however, and just look at how Continue reading
The post Worth Reading: The IANA transition so far appeared first on 'net work.