← Back to Posts

Software is setting the standards: Mark Collier on open source and policy

Sean Roberts•December 18, 2020•4 min read

I opened my second conversation with Mark Collier, chief operating officer of the OpenStack Foundation, with a problem I have run into for years. People in open source call themselves a community. People who make policy, mostly in Washington, call themselves a community too. We do not speak the same language. The same words mean different things, most open source people come from engineering, most policy people come from law or politics, and we have been trained to think in fundamentally different ways. So how do the two build better products together, given that we all have to live with what gets made?

Mark began with standards, which he thinks are vital to growing markets and are where policy rightly comes in. Then he described what has changed in the decade since OpenStack started.

I think what you've seen over the past several years, the last decade since OpenStack started, you see that software in a lot of ways kind of is creating standards. It's not through kind of a standards body per se, but through kind of the practical, you might call it an industry standard.

The engineering mindset, as he put it, starts with the problem: what are we trying to solve? Then you experiment and try things, and open source is one of the great enablers of that, because anyone can download the code and try it. Nobody at OpenStack expected the telecom carriers to adopt it, as he told me in our first conversation. The carriers looked at it, decided it seemed to solve a problem they had, and tried it. A level playing field where many participants can compete and experiment accelerates innovation.

His example of policy that works with that mindset rather than against it was CBRS, the Citizens Broadband Radio Service. The government took a slice of spectrum and built a liquid marketplace for sharing it, with a database deciding who may transmit where. That combines naturally with open source software for running networks, because you cannot build a network without spectrum. You do not have to be one of the five or ten wealthiest companies in the world to have spectrum anymore. You can be a small company, an innovator, a startup. When the first CBRS licenses were auctioned in August, more than two hundred bidders won some, many of them well outside the usual carriers.

The rallying cry in our part of open source has long been standards through implementation. The older model is standards first and innovation last: the committee agrees on the specification, and the builders implement it afterward. The internet itself came from the other model. In the 1970s and 1980s, while international standards bodies worked on an official networking suite, the engineers behind TCP/IP built theirs, ran it, and the world followed. The IETF still sums up its approach as rough consensus and running code.

That is the translation I was looking for between the two communities. Policy people tend to see a standard as the thing you write before anyone builds. Open source people see a standard as the thing that survives after many people have built. CBRS works because it was written to leave room for the second kind: it set the rules for sharing and then let small companies try things nobody had specified. The more of our rules work that way, the less the two communities need a translator.

The rest of our conversation was about what people are building on CBRS right now, starting with factories, and I have written it up separately: spectrum by the factory.

From Lincoln Shorts, the interview series I hosted for Lincoln Network, recorded 18 December 2020.

Share this post