The CORD Architecture

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:

• A set of slides covering the concept can be found here
• A recording of a talk on this topic can be found here
• A shorter white paper on the topic can Continue reading

Worth Reading: Yellow journalism on encryption

That’s not how encryption works. Instead, if “encryption” were the one thing the terrorists were using to hide, then you’d certainly find encrypted emails and encrypted messages — ones you couldn’t read without knowing the key. The lack of emails/messages instead hints that the terrorists were meeting in person, passing paper notes to each other, or using telepathy. All of these, even telepathy, are more likely explanation for the lack of evidence than “encryption”. It’s a typical example of yellow journalism. The public isn’t familiar with “encryption”, so it’s easy to sensationalize it, to make it seem like something sinister is going on. -via Errata Security

The post Worth Reading: Yellow journalism on encryption appeared first on 'net work.

Worth Reading: Construction zones on the Ethernet road map

There is never enough bandwidth in a datacenter that is the size of a football field and that is expected to work more or less like a single computer. While 10 Gb/sec Ethernet on the server and 40 Gb/sec Ethernet on the backbone is fine for many enterprises today, hyperscalers, cloud builders, and service providers are pushing up against these limits and crave more bandwidth. -via The Next Platform

The post Worth Reading: Construction zones on the Ethernet road map appeared first on 'net work.

Reaction: Should routing react to the data plane?

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.

I have been looking at convergence from a user perspective, in that the real aim of convergence is to provide a stable network for the users traversing the network, or more specifically the user traffic traversing the network. As such, I found myself asking this question: “What is the minimum diameter (or radius) of a network so that the ‘loss’ of traffic from a TCP/UDP ‘stream’ seen locally would indicate a network outage FASTER than a routing update?”

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

Worth Reading: Microservices

In this post, I’ll talk about how and why a microservices architecture can help with application development and lifecycle tasks, and describe the capabilities that platforms can provide to support those architectures. Then I’ll list some of the platforms commonly used by developers as the foundation for their microservice based applications. . . -via Azure

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

Worth Reading: Trademarking hashtags

Now companies are trademarking hashtags in the same way they trademark logos, catchphrases and other designs, to keep other entities from using them to market or sell certain goods or services. In 2010, four years after Twitter first launched, just seven companies applied to trademark specific hashtags, according to a report from Thomson Reuters CompuMark. Five of the seven trademarks were granted. -via MarketWatch

The post Worth Reading: Trademarking hashtags appeared first on 'net work.

The Design Mindset (3)

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

Worth Reading: Building a (human) network, part 2

There are endless ways of building a network and the ways I describe here are based on my personal experience. That said, I do believe that there are some common factors regardless of what approach you take. -via Lost in Transit

The post Worth Reading: Building a (human) network, part 2 appeared first on 'net work.

Worth Reading: Free market needs some sunshine

This week is Sunshine Week, and lots of people are writing about government transparency, which is very important. From federal agencies stiff-arming Freedom of Information Act requests, to government agencies punishing whistleblowers, to the Obama Administration’s new record in withholding public information, there’s a lot to talk about. But it’s not just the government that matters. Plenty of private companies that deal with the public could do better with transparency than they do, and they’d be a lot more trusted if they did. The question is whether they care more about being trusted, or about what they can get away with. At the moment, it’s looking as if they’re more concerned with the latter. -via USA Today

The post Worth Reading: Free market needs some sunshine appeared first on 'net work.

CAP Theorem and Routing

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—

• Consistency, which means the database will produce the same result for any two readers who happen to read a value at the same moment in time.
• Availability, which means the database can be read by any reader at any moment in time.
• Partionability, which means the database can be partitioned.

Brewer, in explaining the relationship between the three in a 2012 article, says—

The easiest way to understand CAP is to think of two nodes on opposite sides of a partition. Allowing at least one node to update state will cause the nodes to become inconsistent, thus forfeiting C (consistency). Likewise, if the choice is to preserve consistency, one side of the partition must act as if it is unavailable, thus forfeiting A (availability).

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

Worth Reading: The IANA transition so far

Since the creation of ICANN in 1998, the community has fervently supported this transition. For more than 10 years, APNIC and the RIR communities have actively advocated for the end of a special role by a single government. Here are some historical highlights of the last 10 years of the IANA stewardship transition from an APNIC and number community perspective. -via APNIC

The post Worth Reading: The IANA transition so far appeared first on 'net work.

Worth Reading: Scrutinizing the Cisco-Arista legal battles

The legal battle between Cisco and Arista has heated up in a big way. Earlier this month, Judge David Shaw of the International Trade Commission (ITC) released the public version of the findings in the case. The findings reveal curious aspects of this case that raise questions about Cisco’s intentions and put a spotlight on Silicon Valley work culture. -via Network Computing

The post Worth Reading: Scrutinizing the Cisco-Arista legal battles appeared first on 'net work.

Yokohama

The post Yokohama appeared first on 'net work.

Book Winners!

Lots of good suggestions in my inbox—thanks to all who gave me some great design ideas to blog about. I eventually chose two winners, as I uncovered another copy of the book to give away! The two winners are Patrick Watson and Matthew Sabin. I’m going to try and run something like this every three or four months, so look for another one in the future.

The post Book Winners! appeared first on 'net work.

Rethinking BGP path validation (part 2)

This is the second post in the two part series on BGP path validation over on the LinkedIn Engineering blog.

We left off last time after having described the eight operational requirements that must be met for any system that reduces our reliance on transitive trust in relation to the AS Path. As a reminder, AS, or Autonomous Systems, is a set of routers which all follow a standard set of policies. A typical AS is run by a single organization, such as a company or an ISP. Now, let’s see how this kind of system might work in practice.

The post Rethinking BGP path validation (part 2) appeared first on 'net work.

Worth Reading: The Databerg Report

Veritas has released their US Databerg Report, which looks at the effects of today’s exploding data volumes and how they have been overlooked by most business leaders who were did not anticipate the exponential growth of data. In fact, an independent research study demonstrates how organizations around the world are on track to waste more than $3.3tn by 2020. Previously, Veritas released their study results on data management, which touches on this subject. -via Storage Review

The post Worth Reading: The Databerg Report appeared first on 'net work.

Worth Reading: OCP recap

Last week’s Open Compute Project Summit was kinda crazy with all the announcements of new members (the big one being Google), partnerships (the big one being Mellanox and Cumulus Networks) and contributions to OCP for both hardware and software. -via Packet Pushers

The post Worth Reading: OCP recap appeared first on 'net work.

Worth Reading: Building a Network

Building a strong network of people is very important in creating a successful career in IT. In these posts we will start first look at why building a network is important and in the other posts we will look at how to actually build the network and how to make sure that you are also contributing to the network and not only exploiting it. -via Lost in Transit

The post Worth Reading: Building a Network appeared first on 'net work.

Worth Reading: The FCC’s subtractive privacy rules

Less is not more. That’s real “common sense.” When one’s actions demonstrably create a worse rather than better outcome net-net, like the FCC’s new Title II ISP privacy policy does, others would justifiably consider it a mistake. While the FCC obviously complied with President Obama’s call for regulating broadband as a Title II utility, the FCC obviously ignored President Obama’s 2011 call for a 21st century regulatory system, where he said we are “making it our mission to root out regulations that conflict, that are not worth the cost, or are just plain dumb.” -via Somewhat Reasonable

The post Worth Reading: The FCC’s subtractive privacy rules appeared first on 'net work.

Worth Reading: iSDX

Today, we are excited to announce, in partnership with the Open Networking Foundation and Open Source SDN, the official launch of iSDX — open-source controller software for an industrial-scale Software-Defined Internet exchange point. iSDX allows independently operated networks to interconnect and exchange traffic in completely new ways. This software, which we’ve been developing for nearly three years, now finally operates at the scale of the world’s largest IXPs and interoperates with SDN-capable hardware switches, opening up new possibilities for interdomain business relationships and traffic exchange. -via Circle ID

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