From Concept to Consensus: Developing Internet Standards

I love the whole Internet standards development process and tend to collect standards development organization (SDO) meeting badges like other people collect Pokémon. (Don’t judge; there are stranger hobbies out there. Granted, none come to mind right now, but I’m sure they exist.) Having been an active part of cross-organization collaborations since around 2001, the process of developing broadly applicable standards is natural to me and deeply mystifying to anyone outside the standards development space.

The creation of an Internet standard is a journey that involves personal autonomy, teamwork, and the voices of countless stakeholders. It requires a mix of individual expertise and collective effort. Arguments, debates, concessions, compromises, and pragmatism are all characteristics of a good standards process.

The Spark of an Idea

How does a standard even get started? Every single one begins with a problem needing to be solved, sparked by a challenge or a gap in the current technology landscape. This is where personal autonomy plays its first crucial role. An individual or a small group identifies a problem and starts brainstorming a solution. This initial phase is all about creativity and innovation, with minimal constraints. It is the part the individual loves most while their management wonders when the problem will actually be _solved_.

But to move from an idea to something actionable, the next step is to find like-minded individuals who share the same problems. While technology is evolving faster than ever, it is rarely entirely new. That means one or more SDOs are almost certainly working in the space. That’s your first stop to finding others who will likely see the value in the idea and are willing to invest time and effort in developing it further.

Building Consensus: The Heart of Internet Standards Development

Of course, finding a home for an idea to turn into an Internet standard is critical; it’s also the point that people new to the idea of standards start to get overwhelmed. Depending on the type of SDO involved—whether it’s a treaty-based, industry-based, or de facto community-based organization—the process towards standardization will vary. So. Much. Process. That said, though, the core principle remains the same: consensus.

Consensus is the lifeblood of standards. It’s the point where autonomy meets teamwork. Each participant brings a unique perspective, whether they are representing a government, a corporation, or their own independent expertise. The goal is to hammer out the technical details in a way that works for everyone—or at least for most stakeholders involved.

At this stage, the process can become incredibly challenging. It’s not just about getting the technical details right; it’s about navigating the complex web of competing interests. For example, treaty-based SDOs often involve nation-state politics, where technical merit might take a backseat to broader geopolitical concerns. Meanwhile, industry-based SDOs have to balance the needs of various commercial entities, each with its own agenda.

For those engineers who want to focus purely on the tech, the non-technical skills required to move an idea forward can be excruciating to develop.

The Role of Stakeholder Engagement

And speaking of non-technical skills, the people who came up with the initial idea cannot be the only people who can offer input into the standard. There are _always_ additional stakeholders that need to be brought in. If people and organizations don’t have a say, they may not adopt the standard. A standard that isn’t adopted is ultimately a waste of time and energy. So, all this means that the process must be open enough to allow for broad participation but structured enough to keep things moving forward.

Sometimes, the standard might be developed within a small, focused community before it’s presented to a broader audience. This is often the case with de facto or community-based SDOs, where the initial work is done by a committed group of experts who are passionate about the topic. It’s my favorite way of doing things. These standards can gain significant influence if they garner widespread adoption, often transitioning into more formalized industry-based standards over time.

Publication and Beyond: The Long Tail of Internet Standards Work

Through dangers untold and hardships unnumbered (how to say you’re Gen X without saying you’re Gen X) or, more to the point, after much discussion, negotiation, and revision, the standard is finally ready for publication. Enter in MORE PROCESS. Each SDO will have a process for its participants or members to indicate support for the proposed standard to be published by that SDO.

If you’ve done your work and engaged a broad swath of stakeholders, then the approval part of the process will go much more smoothly. Standards need to be implemented, which often means dealing with feedback from those putting them into practice in the real world.

This can be frustrating for those not involved in the early stages. It’s not uncommon to hear complaints that a standard doesn’t quite fit the needs of a particular organization or use case. Hearing that at the point the initiating working group thinks it’s all done is, to say the least, wildly frustrating. And I mean frustrating for both the group that worked on the standard and the organizations who are only just hearing about it at the end of the game. Still, even late in the game, having that opportunity to catch any missing bits is important. To paraphrase an old adage: The best time to get involved in standards development was years ago, but the second best time is now.

Why You Should Care

Now, on to why you should care about the standards development process: The standards that come out of these efforts have a direct impact on how you (as vendors, enterprises, humans, etc.) operate in the digital world. For technologists, these standards shape the tools and protocols that we rely on every day. And the more diverse the input into these standards, the better they will be at addressing the needs of the global community.

By engaging in the standards development process, you not only contribute to the betterment of the industry but also ensure that your organization’s needs are met. If you’re not ready to dive in at the deep end, there are many ways to get involved. Start by participating in a community group or contributing to the early thoughts through organizations like IDPro® or conferences like the Internet Identity Workshop (IIW).

Wrap-Up: Your Role in Shaping the Future

The journey from an idea to a published standard is long and complex, but it’s also incredibly rewarding. It’s rewarding personally because while it requires the input of many, each person brings their own autonomy and expertise to the table. And from an organization’s perspective, it’s where you truly demonstrate your thought leadership on how the technology in your field should evolve. And if you’re worried you’re “not technical enough,” I promise you that there’s a role for you to play in shaping the future of Internet standards.

So, if you’ve ever found yourself frustrated by a standard that doesn’t quite meet your needs, consider this: You have the power to change that. Get involved, make your voice heard, and be part of the team that’s building the digital world of tomorrow.

If you’re interested in learning more about navigating this process or need support in engaging with standards development, don’t hesitate to reach out. With my experience across various SDOs, I’m here to help guide you through the complexities of Internet standards development.