Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.

I ran into an article over at the Register this week which painted the entire networking industry, from vendors to standards bodies, with a rather broad brush. While there are true bits and pieces in the piece, some balance seems to be in order. The article recaps a presentation by Peyton Koran at Electronic Arts (I suspect the Register spiced things up a little for effect); the line of argument seems to run something like this —

Vendors are only paying attention to larger customers, and/or a large group of customers asking for the same thing; if you are not in either group, then you get no service from any vendor

Vendors further bake secret sauce into their hardware, making it impossible to get what you want from your network without buying from them

Standards bodies are too slow, and hence useless

People are working around this, and getting to the inter-operable networks they really want, by moving to the cloud

There is another way: just treat your networking gear like servers, and write your own protocols--after all you probably already have programmers on staff who know how to do this

Let's think about these a little more deeply.

Vendors only pay attention to big customers and/or big markets. – Ummm… Yes. I do not know of any company that does anything different here, including the Register itself. If you can find a company that actually seeks the smallest market, please tell me about them, so I can avoid their products, as they are very likely to go out of business in the near future. So this is true, but it is just a part of the real world.

Vendors bake secret sauce into their hardware to increase their profits. – Well, again… Yes. And how is any game vendor any different, for instance? Or what about an online shop that sells content? Okay, next.

Standards bodies are too slow, and hence useless. – Whenever I hear this complaint, I wonder if the person making the complaint has actually ever built a real live running system, or a real live deployed standard that provides interoperability across a lot of different vendors, open source projects, etc. Yes, it often seems silly how long it takes for the IETF to ratify something as a standard. But have you ever considered how many times things are widely implemented and deployed before there is a standard? Have you ever really looked at the way standards bodies work to understand that there are many different kinds of standards, each of which with a different meaning, and that not everything needs to be the absolute tip top rung on the standards ladder to be useful? Have you ever asked how long it takes to build anything large and complicated? I guess we could say the entire open source community is slow and useless because it took many years for even the Linux operating system to be widely deployed, and to solve a lot of problems.

Look, I know the IETF is slow. And I know the IETF has a lot more politics than it should. I live both of those things. But I also know the fastest answer is not always the right answer, and throwing away decades of experience in designing protocols that actually work is a pretty dumb idea — unless you really just want to reinvent the wheel every time you need to build a car.

In the next couple of sentences, we suddenly find that someone needs to call out the contradiction police, replete in their bright yellow suits and funny hats. Because now it seems people want inter-operable networks without standards bodies! Let make a simple point here many people just do not seem to realize:

You cannot have interoperability across multiple vendors and multiple open source projects, without some forum where they can all discuss the best way to do something, and find enough common ground to make their various products inter-operate.

I hate to break the news to you, but that forum is called a standards body.

In the end, if you truly want every network to be a unique snowflake, groaning under the technical debt of poor decisions made by a bunch of folks who know how to code up a UI, but do not understand the intimate details of how a network actually converges in the real world, feel free to abandon the standards, and just throw the problem to any old group of coders you have handy.

Let me know how it turns out — but remember, I am not the one who has to answer the phone at 2AM when your network falls over, killing your entire business.

People are working around this by moving to the cloud. Yep — this is what every company I've talked to who is moving to the cloud has said to me: "We're doing it to get to inter-operable networks." 'nuff said.

There is a better way. On this I can agree entirely. But the better way is not to build each network into a unique snowflake, nor to abandon standards. There is a real path forward, but as always it will not be the apparently easy path of getting mad at vendors and the IETF, and making the bald statement you can build it all on your own. The real path forward looks something like this —

Learn to be, and build, real engineers, rather than CLI slingers

Rationally assess the problems that need to be solved to build the network your organization needs

Choose a set of solutions that seem right to solve that set of problems (and I don't mean appliances here!)

Look around for implementations of those things (open source and commercial), take in lessons others have learned, and refine the solution set; in other words, don't abandon years of experience, but rather leverage it

If the solution set doesn't exist, decide how you can break the solution set into reasonable pieces

Figure out which pieces you should outsource, which you should not, and what the API looks like between these two

Build it

Oh, and along the way — rather than complaining about standards bodies, get involved in them. There are far too few people who even make an attempt at changing what is there, and far too many who just whine about it. You don't need to be involved in every IETF or W3C mailing list to be "involved;" you can pick a narrow realm to be useful in and make a real difference. Far too many people see these bodies as large monoliths; either you must be involved in everything, or nothing. This is simply not true.

If you are pressed for time ...

... this is for you. More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Vinton Cerf, Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Share your comments

Related

Software-Defined Networking (SDN) and Network Functions Virtualization (NFV) are finally starting to pick up momentum. In the process, it is becoming clear that they are not the silver bullet originally advertised to be. While great for some use cases, emerging technologies like SDN and NFV have been primarily designed for virtual greenfield environments. Yet large service providers continue to run tons of physical network devices that are still managed manually. more

The Silicon Flatirons Conference on Regulating Computing and Code is taking place in Boulder. The annual conference addresses a range of issues at the intersection of technology and policy and provides an excellent look ahead to the tech policy issues on the horizon, particularly in telecommunications. I was looking forward to yesterday's panel on "The Triumph of Software and Software-Defined Networks", which had some good discussion on the ongoing problem surrounding security and privacy of the Internet of Things (IoT)... more

To put it bluntly, the proposal cited in Axios story on "Trump team considers nationalizing 5G network" doesn't make sense on a number of levels. The real danger comes if this indeed represents the NSC's failure to understand Internet style connectivity. The proposal may just be the work of an NSC staffer who accepted all the 5G hype as if it were real. I credit the Axios article for having some skepticism... more

This seemed to be the reaction this morning worldwide to the leaked alleged PowerPoint slides detailing the White House strategic options for a U.S. national 5G infrastructure. The gist of the slides has apparently been confirmed to Reuters by unnamed "Trump security team members." The options apparently range between creating a U.S. Ministry of 5G resembling the old world of government Post, Telegraph and Telecommunication (PTT) agencies of bygone years, and sawing off the U.S. ICT infrastructures and services from the rest of the world. more

There is no doubt that the Internet continues to grow. While the sales volumes of the more traditional forms of personal computers has peaked at some 430 million units per year and sales of handheld smart devices has also peaked at some 1.9 billion units per year, the world of the Internet of Things continues to spiral upward. The installed base of these "things" is now at an astonishing 8.4 billion at the end of 2017. more

Black's Law Dictionary defines it as "the extraterritorial operation of laws; that is, their operation upon persons, rights or jural relations, existing beyond the limits of the enacting state, but still amenable to its laws. The term is used to indicate jurisdiction exercised by a nation in other countries, by treaty..." Extraterritoriality is also the most significant emerging development today in the law shaping virtual network architectures and services that includes OTT and NFV-SDN. more

In simple terms, Meltdown and Spectre are simple vulnerabilities to understand. Imagine a gang of thieves waiting for a stage coach carrying a month's worth of payroll. There are two roads the coach could take, and a fork, or a branch, where the driver decides which one to take. The driver could take either one. What is the solution? Station robbers along both sides of the branch, and wait to see which one the driver chooses. more

The telecommunication industry is continuing to resist structural changes, but the reality is that if they don't transform, technology will do it for them. We have seen the fixed telecom operators slowly being pushed back into the infrastructure utility market. Mobile networks are moving in that same direction - that is, the largest part of their network will be a utility, with currently two, three or four mobile infrastructure providers per country... the industry is facing serious problems. more

How was the state of the Internet's routing system in 2017? Let's take a look back using data from BGPStream. Some highlights: 13,935 total incidents (either outages or attacks like route leaks and hijacks); Over 10% of all Autonomous Systems on the Internet were affected; 3,106 Autonomous Systems were a victim of at least one routing incident; 1,546 networks caused at least one incident. more

It is now out -- all 539 pages entitled "Declaratory Ruling, Report and Order, and Order" (Reversal Order). As someone who has dealt with this subject matter at a working level over the past 40+ years, it seems clear that the FCC will readily prevail here and the protagonists need to move on. (Admittedly that is wishful thinking given the appellate revenue to be made and press blather opportunities.) The document from a Federal Administrative Law perspective is very thorough and well-crafted. more

From time to time, I run across (yet another) article about why Border Gateway Protocol (BGP) is so bad, and how it needs to be replaced. This one, for instance, is a recent example. It seems the easiest way to solve this problem is finding new people - ones who don't make mistakes - to work on BGP configuration, building IRR databases, and deciding what should be included in BGP? more

The largest and most important global information infrastructure today by any measure is clearly the global mobile network and all of its gateways, services, and connected devices. That network is standardized, managed, and energized by a combination of the 3GPP and GSMA. The level of 3GPP industry involvement and collaboration today probably exceeds all other telecom, internet, and assorted other bodies put together... and then some. more

Struggles with the firmware update process are well known by Network Administrators in the cable industry. The copious tasks required to complete an end-to-end firmware update are painstaking and error-prone, often making the investment not worth the time it takes to complete the work... imagine doing these manual tasks over and over for hundreds to thousands of devices, many from different vendors, each with its own unique device update path! Clearly, this complex challenge needs a solution. more

In an earlier post, I described Havana's community network, SNET, and wondered what it could become if the government and ETECSA were willing to legitimatize and support it. Spain's Guifi.net provides a possible answer to that question. Guifi.net is said to be the largest community network in the world. It began in 2004 and has grown to have 34,165 nodes online with 16,758 planned, 407 building, 612 testing and 4,043 inactive. more

I've written several posts on Cuba's user-deployed street networks (SNET), the largest of which is SNET in Havana. (SNET was originally built by the gaming community, but the range of services has grown substantially). My posts and journalist's accounts like this one describe SNET, but a new paper presents SNET measurement data as well as descriptive material. more

Promoted Post

Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.

Avenue4 LLCRead4522

A World-Renowned Source for Internet Developments. Serving Since 2002.