TR 21.900 v20.0.0 · How standards actually get made
The whole document
97 clauses in the order they appear. The bar shows how much text each part holds. Open one to see what is inside it and which chapter teaches it.
3 General responsibilities of the Support Team 167 words · 2 of 3 clauses taught
4 Handling of Specifications 6,998 words · 22 of 40 clauses taught
- 4.0 Numbering scheme 7. Reading either body's paper trail yourself
- 4.0A Version nomenclature 3. From an idea to an approved version7. Reading either body's paper trail yourself
- 4.0B Releases 4. The change request and the release
- 4.1 Overview 3. From an idea to an approved version
- 4.2 Characteristics of a specification 2. The shape of 3GPP, and where the data stops
- 4.3 Characteristics of a major version of a specification
- 4.4 Characteristics of a version of a specification
- 4.5 (void)
- 4.6 Change Request regime
- 4.7 "Freezing" of specifications 4. The change request and the release
- 4.8 "Closing" of specifications 4. The change request and the release
- 4.9 "Withdrawing" of specifications 4. The change request and the release
- 4.9A "Withdrawing" of functionality
- 4.9B Procedure for withdrawing of specifications and functionality
- 4.10 Release control
5 Availability and distribution of specifications 264 words · 1 of 3 clauses taught
6 Work Items 4,595 words · 5 of 22 clauses taught
- 6.0 Introduction
- 6.1 Creation of a Work Item 1. Why anybody writes a standard down3. From an idea to an approved version
- 6.2 Types of Work Item
- 6.3 Start and continuation of the work and responsibilities
- 6.4 Realization of Work Items
- 6.5 Status tracking of Work Items 3. From an idea to an approved version
- 6.6 Work Item model 2. The shape of 3GPP, and where the data stops
- 6.7 Guidance for Appointed Duties