Middleboxes and the End-to-End Principle

The IP suite was always loosely grounded in the end-to-end principle, defined here (a version of this paper is also apparently available here), is quoted in RFC2775 as:

The function in question can completely and correctly be implemented only with the knowledge and help of the application standing at the endpoints of the communication system. Therefore, providing that questioned function as a feature of the communication system itself is not possible. … This principle has important consequences if we require applications to survive partial network failures. An end-to-end protocol design should not rely on the maintenance of state (i.e. information about the state of the end-to-end communication) inside the network.

How are the Internet and (by extension) IP networks in general doing in regards to the end-to-end principle? Perhaps the first notice in IETF drafts is RFC2101, which argues the IPv4 address was originally a locater and an identifier, and that the locater usage has become the primary usage. This is much of the argument around LISP and many other areas of work—but I think 2101 mistates the case a bit. That the original point of an IP address is to locate a topological location in the network is Continue reading

Worth Reading: So You Want to get Certified

So you want to get certified. Nearly every technology vendor you can think of offers a certification program. You might have a few different reasons for wanting to get certified, and vendors have just as much incentive to get you certified in implementing and supporting their platforms. —Netcraftsmen

The post Worth Reading: So You Want to get Certified appeared first on 'net work.

Worth Reading: Building better ransomware

This is kind of a funny post for me to write, since it ransomwareinvolves speculating about a very destructive type of software — and possibly offering some (very impractical) suggestions on how it might be improved in the future. It goes without saying that there are some real downsides to this kind of speculation. Nonetheless, I’m going ahead on the theory that it’s usually better to talk and think about the bad things that might happen to you — before you meet them on the street and they steal your lunch money. —Cryptography Engineering

The post Worth Reading: Building better ransomware appeared first on 'net work.

Raptor

The post Raptor appeared first on 'net work.

Worth Reading: The Internet’s gilded age

The rise of the Internet has heralded rapid changes in our society. The opportunities presented by a capable and ubiquitous communications system and a global transportation network have taken some corporations from the multinational to the status of truly global mega-corporation. Good examples of these new corporations include Google, Apple, Amazon, Microsoft and Facebook. There are a handful of large scale winners in this space and many losers. But this is not the first time we’ve witnessed a period of rapid technological and social change. —Potaroo

The post Worth Reading: The Internet’s gilded age appeared first on 'net work.

Worth Reading: Three attitudes that lead to maintainable code

When writing code, there are many specific principles that aim to make your code more maintainable: DRY, the single responsibility principle, the Law of Demeter, the open/closed principle, etc. These are great principles to follow, but it can be difficult to keep all of them in your head at once. I’ve found it’s often easier to keep a few broader ideas in mind. —Atomic Object

The post Worth Reading: Three attitudes that lead to maintainable code appeared first on 'net work.

Worth Reading: Web audio API

Web Audio API lets us make sound right in the browser. It makes your sites, apps, and games more fun and engaging. You can even build music-specific applications like drum machines and synthesizers. In this article, we’ll learn about working with the Web Audio API by building some fun and simple projects. —CSS Tricks

The post Worth Reading: Web audio API appeared first on 'net work.

Worth Reading: Digital security assessment quiz

As our reliance on digital devices increases, so does our digital vulnerability. Cyber attacks and hacks are growing both in number and sophistication, making it more important than ever that we take control of our own cybersecurity. But for those of us with limited technical knowledge, anything prefixed with “cyber” seems shrouded in a baffling binary fog. We at CDT wish to clear this intimidating haze by illuminating some effective security strategies. —Center for Democracy and Technology

The post Worth Reading: Digital security assessment quiz appeared first on 'net work.

Worth Reading: Redundancy does not imply fault tolerance

It’s a tough life being the developer of a distributed datastore. Thanks to the wonderful work of Kyle Kingsbury (aka, @aphyr) and his efforts on Jepsen.io, awareness of data loss and related issues in the face of network delays and partitions is way higher than it used to be. Under the Jepsen tests, every single system tested other than ZooKeeper exhibited problems of some kind. But many teams are stepping up, commissioning tests, and generally working hard to fix the issues even if they’re not all there yet. —the morning paper

The post Worth Reading: Redundancy does not imply fault tolerance appeared first on 'net work.

Worth Reading: Fearing Facebook

I used to greatly admire Mark Zuckerberg. Now, I fear him. Here’s why. Facebook is now a supranational company. It spans the globe with about 2 billion subscribers, its 2016 revenue reached $27.6B—54% more than in 2015; it’s immensely profitable (37% of revenue) and cash-rich with $29.56 “in the bank”. Decades ago, European Communists complained about “multinationals”, companies whose spread over multiple countries allowed them to escape full accountability in any one location. —Monday Note

The post Worth Reading: Fearing Facebook appeared first on 'net work.

On the ‘net: PCEP

The original Path Control Element Protocol (PCEP) work dates from the early 2000’s, with the first IETF RFC (4655) being made informational in 2006—which means PCEP predates the time when SDNs were “cool.” PCEP was originally, because of the increasingly complex nature of computing Traffic Engineering (TE) paths through (primarily), Service Provider (SP) networks. Three specific developments drove the design, standardization, and deployment of PCEP —ECI Blog

The post On the ‘net: PCEP appeared first on 'net work.

Worth Reading: Fat Finger Folly

You see, many newly created production systems, when they first come online, focus more on functionality and less on supportability. They are built to provide a specific capability. Of course, the services must be maintained, but maintaining these services often involve manual tasks by operations individuals, tasks such as logging on to servers and rebooting them, or terminating processes, or updating a configuration file. For many production systems, this is how they are maintained. Individuals login to the production servers and high privileged or “superusers” and manually perform necessary actions. This is, unfortunately, a very common process in the industry. —The New Stack

The post Worth Reading: Fat Finger Folly appeared first on 'net work.

History!

The audio is a bit low on this video; it actually recorded a bit lower than this, and the process of amplifying made it poor quality. I’ve already separated the audio recorder from the camera; now I’m upgrading the mic, and playing with the settings on the recorder to make the audio better quality. I’m also playing with putting text and drawings on the side of the video, a concept I intend to use more often in the future.

So this is a bit of a play video, but with a somewhat serious topic: the importance of learning the history of network engineering. Some resources are included below.

A bit history of the Internet
Net Heads versus Bell Heads
On the History of the Shortest Path Problem
The Elements of Networking Style
Software Defined Networks has a great introductory section with a good bit of history

The post History! appeared first on 'net work.

Worth Reading: Comments on the Wikileaks CIA Vault #7

The CIA didn’t remotely hack a TV. The docs are clear that they can update the software running on the TV using a USB drive. There’s no evidence of them doing so remotely over the Internet. If you aren’t afraid of the CIA breaking in an installing a listening device, then you should’t be afraid of the CIA installing listening software. —Errata Security

The post Worth Reading: Comments on the Wikileaks CIA Vault #7 appeared first on 'net work.

Worth Reading: Web Scale Networking

In this episode of The New Stack Makers, we spoke to Josh Leslie, Chief Executive Officer, and JR Rivers, Chief Technology Officer and co-founder of Web-scale networking software provider Cumulus Networks. We discussed how to best define web-scale networking, and how Cumulus Linux is different from traditional networking solutions. They spoke to the need for inter-system communication for new workloads, and how that factors into building a software-defined data center. They told us about their company’s recent product release Cumulus Express, as well as its announcement around Facebook’s Backpack, an open network chassis. Our conversation included points about hyper-converged infrastructure, customer roadblocks, and the roadmap for Cumulus Networks. —The New Stack

The post Worth Reading: Web Scale Networking appeared first on 'net work.

Worth Reading: When your code has to work

Douglas Crockford famously declared browsers to be “the most hostile software engineering environment imaginable,” and that wasn’t hyperbole. Ensuring that our websites work across a myriad of different devices, screen sizes and browsers our users depend on to access the web is a tall order, but it’s necessary. If our websites don’t enable users to accomplish the key tasks they come to do, we’ve failed them. —Smashing Magazine

The post Worth Reading: When your code has to work appeared first on 'net work.

Tan Gate

The post Tan Gate appeared first on 'net work.

Worth Reading: The nuanced future of 5G

5G sounds like the successor to 4G cellular telephony, and indeed that is the intent. While the progression from 2G to 3G, to 4G and now 5G seems simple, the story is more nuanced. At CES last month I had a chance to learn more about 5G (not to be confused with the 5Ghz WiFi) as well as another standard, ATSC 3.0 which is supposed to be the next standard for broadcast TV. —CircleID

The post Worth Reading: The nuanced future of 5G appeared first on 'net work.

Worth Reading: Keys to solving wicked problems

The incredible pace of change of the Internet — from research laboratory inception to global telecommunication necessity — is due to the continuing pursuit, development and deployment of technology and practices adopted to make the Internet better. This has required continuous attention to a wide variety of problems ranging from “simple” to so-called “wicked problems”. Problems in the latter category have been addressed through collaboration. This post outlines key characteristics of successful collaboration activities. —CircleID

The post Worth Reading: Keys to solving wicked problems appeared first on 'net work.

Worth Reading: Bouncing back to private clouds

There is an adage, not quite yet old, suggesting that compute is free but storage is not. Perhaps a more accurate and, as far as public clouds are concerned, apt adaptation of this saying might be that computing and storage are free, and so are inbound networking within a region, but moving data across regions in a public cloud is brutally expensive, and it is even more costly spanning regions. —The Next Platform

The post Worth Reading: Bouncing back to private clouds appeared first on 'net work.