14 What this record cannot tell you

14.1 Why this chapter exists

Every number in this course came out of a file or a database on one machine on 2026-08-04, and every one of them carries a written note saying which question produced it and on what day. That is the strength of the material.

Its weakness is the same thing seen from the other side. A count of documents is a count of documents. It is not a record of what people meant, what they argued about, or what anybody decided in a corridor.

What follows is the whole list of what this record cannot answer. Each item says where the answer actually lives, because a limit without a way round it is half a sentence.

14.2 The thirteen gaps

N1. There are no attendance figures except for two meetings. 172 people at C1-161 ^[1] and 165 at C1-160 ^[2] were counted from the participant list inside those two meeting reports. Only three CT1 meeting folders are mirrored on this machine and only two of them hold a report, so no other meeting has an attendance number and no trend exists. Where to go instead: the participant list in the report of the meeting you care about, in the file area ^[3].

N2. The report of the last meeting is a draft. The C1-161 report is not approved ^[4]; the C1-160 one is ^[5]. Its numbers can still change. Where to go instead: say "the draft report of C1-161" wherever you use it, or use C1-160, which is settled.

N3. There is nothing from C1-162 onwards. Documents are being filed for it — 69 so far ^[6] — but the meeting is planned for 2026-08-24 C1-162 and has not happened. Nothing was decided, agreed or postponed there. Where to go instead: the meeting's own folder after it runs ^[3].

N4. No past office holder is named. The register carries the four with no end date ^[7]; 44 terms exist in the same file ^[8] and their names are not here, so no chapter may name a past chair. Where to go instead: the office holders page, which lists them term by term ^[9].

N5. There are no vote, objection or attendance counts of any kind. 3GPP works by consensus, and this data holds no tallies. Nothing here was "approved by a majority" or "voted through", and nothing may be described that way. Where to go instead: the meeting report's own text, which records outcomes in words rather than numbers.

N6. The register explains no abbreviation. It holds titles and work item names exactly as they are spelled — "Non-Access-Stratum (NAS)", "AmbientIoT-CT", "MINT_Ph2" — and says nothing about what any of them means. Where to go instead: for terms inside TS 24.501, the document's own definitions §3.1 and abbreviations §3.2, which is where every explanation in this course came from. For a work item name, the 3GPP work plan ^[10].

N7. The text of no letter between groups is here. The 108 outgoing and 135 incoming liaison statements of the year ^{[11] [12]} are counted, not read. What any of them said is not in this data. Where to go instead: the letter is itself a document, in the meeting folder ^[3].

N8. There is no agenda, no minutes and no debate. The register knows a document's outcome word — agreed, revised, postponed, noted, merged, withdrawn — and nothing about why. Never write why CT1 postponed something. Where to go instead: the meeting report, and even that records decisions rather than arguments.

N9. No rapporteur, editor or author is named. The specification catalogue here carries the number, type, title, group and active flag, and no person. The change history of TS 24.501 does mention the role — its first row, from 2017-10, reads "Draft skeleton provided by the rapporteur" §Annex F — but never the name. Where to go instead: the work item description, and the meeting report.

N10. There is no reliable count before 2015. 7181 CT1 documents carry no upload date at all ^[13]. Every "in the last twelve months" number in this course is a count of dated rows; every all-time number includes the undated ones. Where to go instead: nowhere — just never compare the two. Use all-time counts for all-time questions and yearly counts for yearly ones, and say which you used.

N11. There is no comparison with any other working group. The register was built for CT1 alone and holds no specification, document or meeting count for CT3, CT4, SA2 or anybody else, so CT1 cannot be called the largest, busiest or fastest of anything The neighbours — and how little the record says about them. Where to go instead: the specification status report, which lists every specification with its owning group ^[14].

N12. There are no dates or version numbers for the specifications. The register carries the number, the title and which Releases a document has a version in — no publication date, no version date, no version number. Where to go instead: for a specification whose text is parsed here, its own change history gives both, one row per version §Annex F. Only 157 of the 229 have their text parsed here ^[15]; for the rest, the status report ^[14].

N13. There is no date on which CT1 began. The meetings database starts at 2005-04-25 ^[16] and the stored document dates run from 2005 to 2026 ^[17], but 2005 is the floor of two stores and nothing more. CT1 grew out of CN1 CT1 — Mobility, call control, session management (WG1_mm-cc-sm_ex-CN1), whose work is not in here, so a reader who takes 2005 for a founding year is wrong by however long CN1 ran. Never write that CT1 started, was formed or first met in 2005. Where to go instead: the group's own file area, whose folders reach further back than this database does ^[3].

14.3 The two limits that catch people most often

Of those thirteen, two produce almost all the wrong statements, and both look harmless.

Subtracting to find a missing count. At C1-161 the six counted outcome words come to fewer than the 617 documents put to the meeting ^[18]. Two more words exist in the data with no counts, so the difference is not the size of anything. The same trap sits in the document kinds Following CT1 yourself and in the specification series counts What CT1 owns — 229 documents and the six that matter.

Reading absence as zero. The liaison tables carry the four busiest partners in each direction and stop Who CT1 writes to, and what the letters count. CT3 not appearing means CT3 is not in the top four, not that no letters passed.

14.4 What is solid

It is worth saying plainly what survives all of the above, because the list of gaps is long enough to look discouraging and the material is genuinely good.

Every count in the register carries its method: the exact question that produced it and the day it was asked. Every specification, meeting, document and office holder cited in this course is an entry a reader can open.

And every statement about the protocol itself comes from a clause of TS 24.501 version 20.0.0, which is a document under change control §Annex F rather than anybody's summary of one.

That is a narrower foundation than a textbook and a firmer one.

14.5 Where to go next

The document. TS 24.501 TS 24.501 is the whole of the protocol side of this course, and the clauses cited throughout open beside the text.

The register. Every source this course cites is listed on the course's own sources page, each with the file or database it was read from.

The live record. CT1's documents ^[19], the meeting calendar ^[20], the file area on the 3GPP server ^[3], the specification status report ^[14] and the work plan ^[10]. The routine that ties them together is Following CT1 yourself.