From the very beginning, the walled garden has been the opposite of what those who work on and around the ‘net have wanted. The IETF, and the protocols it has developed over the years, have always been about free and open access to anyone who wants to learn networking, coding, or even just what the latest baseball score for their favorite team. Of course, a number of tech giants (remember Compuserve?) fought to build walled gardens using the tools of the Internet. A user would dial into a modem pool, and access the world through a small portal that would provide a consistent and controlled interface for their entire experience, from email to news to chat to…
The same battle rages in recent times, as well. Phone makers, mobile providers, and even social media networks would desperately like to make your only interface into the global Internet a single O/S or app. From this one app, you’ll be able to talk to your friends, pay your bills, save all your data, and, in general, live your entire life. And for those times when you can’t get to what you want outside the app or social network, they will gladly Continue reading
The post Worth Reading: Software Defined Overload appeared first on 'net work.
The post Worth Reading: New Port Mapper DDoS Attack appeared first on 'net work.
I’m moderating a panel called Cloud Builders at the upcoming Cloud Partners show in Boston! If you’re going to be there, look me up.
The post Come meet me at Cloud Partners appeared first on 'net work.
Furthering the thoughts I’ve put into the forthcoming book on network complexity…
One of the hardest things for designers to wrap their heads around is the concept of unintended consequences. One of the definitional points of complexity in any design is the problem of “push button on right side, weird thing happens over on the left side, and there’s no apparent connection between the two.” This is often just a result of the complexity problem in its base form — the unsolvable triangle (fast/cheap/quality — choose two). The problem is that we often don’t see the third leg of the triangle.
The Liskov substitution principle is one of the mechanisms coders use to manage complexity in object oriented design. The general idea is this: suppose I build an object that describes rectangles. This object can hold the width and the height of the rectangle, and it can return the area of the rectangle. Now, assume I build another object called “square” that overloads the rectangle object, but it forces the width and height to be the same (a square is type of rectangle that has all equal sides, after all). This all seems perfectly normal, right?
Now let’s say Continue reading
The post Worth Reading: Another Salvo in the Crypto War appeared first on 'net work.
The post Worth Reading: Knowledge and Power appeared first on 'net work.
Yes, we really are going to reach a point where the RIRs will run out of IPv4 addresses. As this chart from Geoff’s blog shows —
Why am I thinking about this? Because I ran across a really good article by Geoff Huston over at potaroo about the state of the IPv4 address pool at APNIC. The article is a must read, so stop right here, right click on this link, open it in a new tab, read it, and then come back. I promise this blog isn’t going anyplace while you’re over on Geoff’s site. But my point isn’t to ring the alarm bells on the IPv4 situation. Rather, I’m more interested in how we got here in the first place. Specifically, why has it taken so long for the networking industry to adopt IPv6?
Inertia is a tempting answer, but I’m not certain I buy this as the sole reason for lack of deployment. IPv6 was developed some fifteen years ago; since then we’ve deployed tons of new protocols, tons of new networking gear, and lots of other things. Remember what a cell phone looked like fifteen years ago? In fact, if we’d have started fifteen years ago Continue reading
Matt has a greater starter up on running Cumulus IX on a Vagrant installation — since Vagrant is available on a few widely deployed machines, this is a great tool for learning the environment. As soon as I can get one of my Ubuntu machines local, or figure out how to get enough drive space on one of my laptops to install this, I’ll be getting Vagrant set up to use on a few different things.
The post Worth Reading: Vagrant and Cumulus appeared first on 'net work.
The post Worth Reading: The Crisis of Attention appeared first on 'net work.
Two different articles caught my attention this last week. They may not seem to be interrelated, but given my “pattern making mind,” I always seem to find connections. The first is an article from Network Computing discussing the future of network engineering skill sets.
Patrick Hubbard goes on to talk about the hand grenade John Chambers left in the room 3 that there would be major mergers, failures, and acquisitions in the next twenty years, leaving the IT industry a very different place. The takeaway? That individual engineers need to “up their game,” learning new technologies faster, hitting the books and the labs on a more regular basis. Given the view in the industry of Cisco as a “safe harbor” for IT skills, this is something of a hand grenade in the room, coming from Chambers at Cisco Live.
The second article predicts a hand grenade, as well, though of a Continue reading
The post Worth Reading: SDN Controller Benchmarking appeared first on 'net work.
The Craft of Research, Kindle Location 2392
The post Clear Writing appeared first on 'net work.
The post HL: Navigating Network Complexity appeared first on 'net work.