Reading the record yourself · chapter 16 of 16 · 7 minutes
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.
16.1 Why a chapter about holes
A course built from files can only say what the files say. The temptation, every time a reader would obviously want a fact, is to supply it from somewhere else — and a fact supplied from somewhere else looks exactly like a fact that was checked.
So this chapter collects the gaps in one place. Each one names what is missing, why, and where the answer would have to come from.
16.2 About 3GPP's constitution
Who the Organizational Partners are. TR 21.900 speaks of them twice — when explaining who signs for a registered code point §3.2, and when explaining that they publish approved specifications as their own standards §5.1. The meeting calendar records 3GPP OP. No file read here names one. The answer is in the 3GPP Working Procedures [1].
How a decision is actually carried. Whether there is a vote, who may cast one, and with what weight, is not in the working methods at all. The one appearance of "consensus" in TR 21.900 is as the authority for an exception to a frozen Release, not as a general rule §4.6.2. The voting rules are in the Working Procedures, one level above [1].
Who anybody is. Nothing read here says how many delegates attend, how many companies are members, what membership costs, or who chairs anything. The working methods mention a membership database §7.4, but the database itself is not here.
16.3 About names and codes
The short group codes are never spelled out. The specification catalogue counts documents under codes such as S5, with 685 [2], R4, with 458 [3], and C1, with 237 [4]. The meeting calendar names bodies such as "3GPP SA 5" 3GPP SA 5. No local file states that the two refer to the same group, so this course never says it. The mapping is on the 3GPP website [5].
Most group names here come from a calendar, not a specification. TR 21.900 names SA1, SA2 and SA3 in passing while setting out the work item model, and mentions the TSGs CT and RAN in the same clause §6.6. Every other group name in this course was read out of the meeting calendar, which lists 27 3GPP bodies with a series of their own [6]. A calendar records who met; it does not define who exists.
16.4 About time
No Release freeze dates. The document is clear about where they live.
The 3GPP work plan was not among the files read for this course, so no chapter here gives a freeze date for any Release What a Release is, and what freezing one costs.
Some recorded meetings have not happened yet. All 4,371 entries are counted alike, and the calendar runs to 2028 because it holds scheduled meetings alongside held ones [7]. The last date in a series is a plan, not a record.
The calendar does not reach back equally far. SA and RAN start in 1998, CT in 2005, GERAN in 2014 3GPP SA, 3GPP CT. Those groups are older than their entries; a first recorded date is where the record begins.
Meeting document dates only start in 2015. The record holds 1,629,581 documents [8], and 1,543,057 of them carry an upload date [9]. Those dates run from 2015 to 2026, even though the meetings go back to 1998, so the remaining documents can be placed by meeting but not by day.
16.5 About the IETF material
The archive is RFCs and nothing else. No working group charters, no meeting minutes, no mailing list archives, no Internet-Drafts. Anything about a particular IETF working group — who chairs it, what it decided, what it is arguing about — is out of reach from here. The website is the place to go [10].
The plain-text range has gaps. The 8,457 plain-text files are numbered 1 to 8649 [11], so numbers are missing along the way. Some were never issued and some are held only among the 1,278 XML files [12], and the data does not say which is which.
Two named documents are not quoted. RFC 8729 and RFC 9280 describe what the RFC series is and who runs it, and both are in the archive only as XML. This course names them and takes no sentence out of either RFC 8729, RFC 9280.
No current IETF numbers. RFC 2418 spoke of more than 100 working groups and 8 areas, in 1998 RFC 2418. No local file gives today's figures, so the document is quoted here as history and never as a current fact.
16.6 About the parsed documents themselves
One parsed title is stale. The local copy of TR 21.919 carries the title of an earlier Release. The catalogue title is the right one, and the register records both so that neither is silently preferred TR 21.919 v19.0.0.
The 6G study is a draft. TR 21.802, the study on modernising the specification format and procedures, sits at version 1.2.1 TR 21.802 v1.2.1. By the version rules of Reading a 3GPP number — the series, the version, the file name, a leading 1 means presented to the plenary for information and not approved §4.0A. Nothing in it may be stated here as how 3GPP works.
The 21-series is not all process. TS 21.111 is in the same number range and is a requirements document about the USIM card TS 21.111 v19.0.0. Saying "the 21-series holds the working methods" overstates it.
16.7 About judgement
No comparison of quality or speed. Nothing in this material supports a sentence saying one body is faster, better or more open than the other. The counts here measure output volume, and output volume is not a virtue. That is why The two cultures, side by side and on the evidence compares procedures and refuses to compare performance.
16.8 The gaps in one table
| What is missing | Where it would come from |
|---|---|
| The Organizational Partners by name | the 3GPP Working Procedures [1] |
| Voting rules and weights | the same document |
| Delegates, members, costs, chairs | not in any file read here |
| What S5, R4, C1 stand for | the 3GPP website [5] |
| Release freeze dates | the 3GPP work plan §4.10.3.4 |
| Which recorded meetings actually happened | the 3GPP website [5] |
| Dates for documents before 2015 | not in the meeting-document database |
| IETF working groups, areas, charters, minutes | the IETF website [10] |
| The text of RFC 8729 and RFC 9280 | the IETF datatracker RFC 8729 |
16.9 Where this leaves you
You now know how work is authorised, written, changed, decided and published in both bodies, and which questions this record cannot answer.
The final test covers the whole course. If you want the primary material rather than the teaching, TR 21.900 can be read clause by clause on this machine's own viewer [13] — all 97 of its clauses [14] — the RFCs are all in the register, and every number on these pages carries the query that produced it.
Where the numbers in this chapter come from
- The 3GPP Working Procedures the address as written in the reference list of TR 21.900, reference [8]
- 685 specifications carry the group code S5 rows in table `spec` where wg='S5', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04
- 458 specifications carry the group code R4 rows in table `spec` where wg='R4', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04
- 237 specifications carry the group code C1 rows in table `spec` where wg='C1', read from /var/www/whatthespec.net/data/database/api/spec_catalog.sqlite on 2026-08-04
- The 3GPP website the address as written in TR 21.900 clause 7.6
- 27 3GPP bodies hold a meeting series of their own distinct body names starting '3GPP' in table `meetings`; the list is every one of them, smallest included, because only the larger ones get an entry of their own in this register, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04
- 4,371 of them are 3GPP meetings, from 1998-12-07 to 2028-06-13 rows in table `meetings` whose body name starts '3GPP'; the span is the earliest and latest start date among them, read from /var/www/whatthespec.net/data/database/api/portal_meetings.sqlite on 2026-08-04. The latest dates are meetings already scheduled, not meetings held
- 1,629,581 meeting documents recorded rows in table `tdoc` of the pygppe meeting-document database, read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04
- 1,543,057 of them carry an upload date, running from 2015 to 2026 rows in table `tdoc` whose `uploaded` field starts with a year; the span is the first and last year holding more than 100 rows, which leaves out two stray rows dated before 1910, read from /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-04
- The IETF website the address as written in RFC 2418 section 1, where it is written http://www.ietf.org
- 8,457 of them are plain text, numbered 1 to 8649 files named rfc<number>.txt, counted in /var/www/whatthespec.net/data/data/rfcs on 2026-08-04
- 1,278 of them are XML, numbered 8650 to 9953 files named rfc<number>.xml, counted in /var/www/whatthespec.net/data/data/rfcs on 2026-08-04
- TR 21.900 as a readable web page the address as written in the FriendlySpec viewer on this machine
- 97 clauses in TR 21.900, the working-methods document parsed clause files of 3GPP TR 21.900 v20.0.0, counted in /var/www/whatthespec.net/data/friendlyspec/json/21900/20.0.0/sections on 2026-08-04
Check yourself
Answers appear when you pick one, with where they come from.
Q16.1 Why does this course name no Organizational Partner?
TR 21.900 refers to the Organizational Partners in clauses 3.2 and 5.1 and the calendar records that they meet, but nothing read here says who they are. The 3GPP Working Procedures is where to look. §3.2
Q16.2 Where would a Release freeze date come from?
Clause 4.10.3.4 says the work plan shall indicate the estimated freeze date of forthcoming Releases and the functional content of each. No chapter here gives a date, because the work plan was not read. §4.10.3.4
Q16.3 The meeting calendar's latest entries are in 2028. What does that mean?
The calendar carries future meetings, so the last date in a series is not the most recent meeting. It is also why a first recorded date is not a founding date. 4,371 of them are 3GPP meetings, from 1998-12-07 to 2028-06-13
Q16.4 Which working groups does TR 21.900 itself name?
Clause 6.6 uses TSG SA as its illustration and names those groups. Every other group name in this course comes from the meeting calendar, not from a specification. §6.6
Q16.5 Why does this course quote no sentence from RFC 8729 or RFC 9280?
The archive holds 8,457 RFCs as plain text and 1,278 as XML. Those two are in the XML half, so the register records them without a quotation. 1,278 of them are XML, numbered 8650 to 9953
This chapter was written against TR 21.900 version 20.0.0, and built from a source register generated 2026-08-04. A newer version of the document may say something else.