Front Matter
Foreword
This book is the result of a series of informal training sessions I ran with a small group of attorneys at Microsoft. We called them "Coffee & Standards" — an hour every week or two, walking through the IP, governance, and negotiation dynamics of technical standards. No slides. No formal curriculum. Just a screen share of actual agreements, actual policies, and whatever was top of mind that week.
The goal was simple: get people to the point where they could pick up a standards agreement, read it, and figure out whether something was outside the range of reasonable.
That range, it turns out, is pretty wide. Standards work has matured enough that you don't see much truly crazy stuff anymore. But it still shows up — in disclosure obligations, governance structures, voting mechanics, patent commitments. And when it does, you need to be able to spot it.
I've been doing this work for over two decades. Long enough to have seen most of the patterns more than once. The benefit of that tenure is pattern recognition. I can look at a particular clause and tell you it exists because of a negotiation between IBM and Microsoft fifteen years ago, and that the language percolated from one organization to another until nobody remembered why it was there. These organizations are deeply interconnected that way. Terms travel. Context doesn't.
That's the gap this book tries to fill. Not just the legal analysis — you can get that from a careful read of the agreements themselves. What you can't get from the text is the judgment layer: why a provision exists, what problem it was solving, what happens when you push on it, and what the person across the table is actually worried about.
A few things I've learned that shape everything in this book.
First, the skills that make you effective in litigation or bilateral contract negotiation will actively hurt you in standards. There's no judge. You'll never convince someone to take a position against their own interests through clever argument alone. If you go for the jugular in the morning session, you'll be sitting across from that same person at lunch and again next quarter. These are repeat players in a long game.
What works instead is something closer to diplomacy. Back-channeling. Subtlety. Empathy — genuinely understanding what every participant in the room needs, what they can give on, and what they can't. If you do this well, you'll find other people taking your positions for you. You can sit back and watch it happen.
Second, a lot of what we do is theater. Most standards-related patent commitments will never be litigated. The releases, the pledges, the non-asserts (promises not to enforce patents) — they exist to land properly and manage perception. Sometimes the legally optimal approach isn't the best approach. Sometimes a vehicle that is technically weaker but broadly trusted will accomplish more than a bespoke agreement that's technically airtight but nobody recognizes. The MIT license isn't perfect. Neither is the W3C patent policy. But people know them, and that matters.
Third, process is substance. In standards, how you get to a decision matters as much as what you decide. Due process, right to appeal, consensus — these aren't just governance niceties. They're what gives a standard legitimacy and, not incidentally, antitrust protection. When process breaks down, everything downstream is at risk.
This book is organized to build from the ground up. Part I covers the foundations — what standards are, the organizational landscape, how intellectual property maps onto them, the due process and antitrust framework that makes the whole system legitimate, and the increasingly blurry line between standards and open source. Part II goes deep on patent policies, which is where most of the complexity and risk lives: necessary claims, RAND and royalty-free regimes, exclusions, non-asserts, and the practical pitfalls that recur across policies. Part III covers governance, decision-making, and the mechanics of getting a specification from first draft to publication. Part IV turns to practice and reflection: multi-party negotiation, practical advice for counsel, lessons from two decades of this work, a look at where the field is heading, and some closing thoughts.
Three appendices follow the main text. A glossary of standards terminology. A standards-engagement checklist for counsel. And a case study — the HD DVD vs. Blu-ray format war — that shows how the concepts in the earlier parts play out when the stakes are real.
This is a book for practitioners — people who are starting, advising, or participating in standards engagements. It covers the lifecycle from forming an organization and selecting an IPR policy through developing and finalizing a specification. It is not a book about what happens after implementation, when disputes over royalty rates and licensing terms move into litigation. There is surprisingly little case law on the patent policy terms themselves. Most standards disputes that reach courts are about rates and licensing mechanics — important topics, but beyond the scope of what we're doing here.
I've tried to write it the way I would explain it over coffee. Lead with the point. Give you the tradeoffs. Use real examples. Skip the parts that don't earn their place.
If you're an attorney advising a client on a standards engagement for the first time, start at the beginning. If you've been doing this work and need to sharpen a particular area — exclusion mechanics, RAND rate dynamics, voting structures — jump to the relevant chapter. Most chapters are designed to stand largely on their own, though Part II builds on concepts introduced in Part I, and the case study in Appendix C draws on the full arc.
One last note. The agreements and policies discussed in this book are real, drawn from organizations like the Joint Development Foundation, W3C, OASIS, ISO, and others. Where I've included my own analysis or interpretation, that's what it is — one practitioner's view based on long experience. Reasonable people will disagree on some of this. That's fine. The goal isn't to give you the answer. It's to give you the framework to find your own.
Let's get to work.
David Rudin