School of Specs How standards actually get madeIn depth

TR 21.900 · version 20.0.0 · 97 clauses · In depth · 120 minutes

How standards actually get made

A standard is a promise put in writing before the products exist, and somebody has to run the machinery that turns an idea into that promise. This course is about the machinery rather than about any one technology: who may propose a change, what form the proposal has to take, who agrees it, who approves it, and what a published version number is actually telling you. Half of it is 3GPP, read straight out of that body's own working-methods document, TR 21.900, whose clauses open in the panel beside the text. The other half is the IETF, read out of the documents in which the IETF describes its own process. Where the material on this machine cannot settle a question — who the Organizational Partners are, when a Release was frozen, how a vote is counted — the chapter says so plainly and names where you would look instead. Every number and every quotation here points at the file it was read from.

Start at chapter 1 Sit the final test Look at the document first

This course was written against TR 21.900 version 20.0.0, and built from a source register generated 2026-08-04.

Same subject, different depth: quick start · overview ·

The document, all of it

One block per clause of TR 21.900, in the order they appear, sized by how much text the clause holds. Lit blocks are taught in this course.

Open the whole of TR 21.900 as a page

The chapters

Part 1 Why any of this exists

  1. 1 Why anybody writes a standard down What breaks when separately built products have no written agreement, what each of the two bodies says it is for, and how much paper that has produced. 7 min

Part 2 How 3GPP is put together

  1. 2 The shape of 3GPP, and what the record does not say about it The layers of groups, the permanent staff, who owns a document, and an honest account of the four things the data here cannot settle. 7 min
  2. 3 What a Release is, and what freezing one costs How specifications are grouped into Releases, the four principles a Release has to satisfy, and the difference between frozen, closed and withdrawn. 8 min

Part 3 How a 3GPP document is made

  1. 4 The life of a 3GPP document, from blank page to published version The spine of the course — the stages, the draft versions, the two presentations to the plenary, the moment change control begins, and what happens after it. 8 min
  2. 5 The Change Request, field by field The one form that can alter a 3GPP specification — who may raise it, what it must carry, the six category letters, and the route from a working group to a plenary decision. 10 min
  3. 6 Work Items and Study Items — how the work is authorised The four sizes of work item, what a proposal must carry before a plenary will adopt it, the shortcut code for small changes, and the four states a work item can be in. 9 min
  4. 7 Reading a 3GPP number — the series, the version, the file name What the two halves of a specification number tell you, what each of the three version digits carries, and how both are packed into a file name. 7 min
  5. 8 How a 3GPP meeting decides, and the word it decides in Everything in the room is a numbered document, every document ends with one status word from a fixed list, and between meetings the same decisions are taken by email under a rule where silence means yes. 9 min
  6. 9 Why the documents read the way they do Where the drafting rules live, which verb makes a sentence binding, why clause numbers are left empty rather than reused, and how to read a NOTE. 6 min

Part 4 How the IETF works

  1. 10 The shape of the IETF A body with no members, organised into working groups and areas, steered by the directors of those areas, publishing into a series that started in 1969. 7 min
  2. 11 The life of an RFC, from a draft nobody may cite to a number nobody may edit Internet-Drafts and why they have no status, the working group recommendation, the IETF-wide Last Call, the two maturity levels, and the rule that a published RFC is never changed. 7 min
  3. 12 Rough consensus, and why the room hums The IETF's refusal to vote, what its own documents say rough consensus is and is not, and why a chair asks a room to hum rather than to raise hands. 7 min
  4. 13 MUST, SHOULD and MAY — three words, one short document The IETF's requirement words, quoted exactly, the correction that made only the capitalised spellings count, and what each one costs an implementer. 6 min

Part 5 Reading the record yourself

  1. 14 The two cultures, side by side and on the evidence Where 3GPP and the IETF genuinely differ, where they do the same thing under different names, the one place their rulebooks touch, and the comparisons this course refuses to make. 6 min
  2. 15 Reading either body's paper trail from a cold start A practical route from one sentence in a live document back to the decision that put it there, in 3GPP and in the IETF, and the registers that make it possible. 7 min
  3. 16 What this record cannot tell you Every question a reader would reasonably ask that the material behind this course cannot answer, why each gap exists, and where the answer would have to come from. 7 min

Testing yourself

Every question at once

84 questions, chapter by chapter, on one page — for revision after you have read the course.

Open all the questions

The final test

20 questions drawn across the whole course, marked at the end. 70 per cent to pass, and every miss says which chapter to go back to.

Sit the final test

What this course is built on

Chapters
16
Words written for you
22,502
Clauses covered
93 of 97
Figures from the document
0
Abbreviations
0
Published versions
20
Checked sources
120
Sources this course cites
101

The document · Words · History · Documents around it · Every source