The final test

E1 You are handed 3GPP TR 24.801 v2.1.0 and asked whether a change to it needs a change request. What is the answer?

• Yes, every 3GPP document changes only by change request
• No — the first digit is below 3, so it is still a draft under the responsible group
• Only if the change is technical rather than editorial

E2 A correction is agreed for a feature that exists in Release 17, 18 and 19, and none of those releases is closed. How many change requests is that?

• One, written against the newest release
• One per affected release, independently numbered and decided together
• One, plus an exception sheet

E3 Which sequence describes a 3GPP document correctly?

• Draft by the rapporteur, 1.0.0 for approval, work item, then the release version
• Work item, 0.0.0, publication by the Organizational Partners, then change control
• Work item approved by the TSG, draft by the rapporteur, 1.0.0 for information, 2.0.0 for approval, then the release version

E4 Which pair of statements is true of the IETF and false of 3GPP as described in these documents?

• A document has a rapporteur and a responsible group
• There is no formal membership, and people take part as individuals
• Work is done in groups that report upwards, and decisions are recorded per document

E5 Somebody says a proposal was carried in an IETF working group because most of the room was in favour. What is wrong with that account?

• Only the IESG may declare consensus
• Nothing, a simple majority carries
• Rough consensus is the chair's judgement that objections were answered, not a count of the room

E6 You need to know how many votes a given 3GPP member has. Where do you look?

• The meeting report of the last plenary
• The working-methods document, clause 9
• The 3GPP Working Procedures

E7 Which of these documents is NOT a standard in the sense the process defines?

• A specification at Internet Standard
• An RFC marked Informational
• A specification at Proposed Standard

E8 Both bodies decide things by email between meetings. What is the difference that matters?

• 3GPP's email decisions are informal, the IETF's are binding
• There is no difference; both require an explicit reply
• 3GPP's silence counts as agreement against a plenary deadline; the IETF's Last Call invites objections from anyone

E9 What reason does 3GPP's working-methods document give for needing strict and fast procedures?

• Regulators set a deadline for each release
• Industry implements the specifications almost in parallel with the writing of them
• Meetings are expensive and have to be kept short

E10 What is a Working Group, in the document's own definition?

• The permanent staff of 3GPP
• Any gathering of delegates from four or more companies
• An official subgroup of a TSG, reporting to that TSG

E11 What has to happen before substantial work starts in a working group?

• A draft has to reach version 1.0.0
• Four member organizations have to publish a press release
• The responsible TSG has to take a decision

E12 Who may raise a change request?

• Any individual member, who brings it to the responsible group
• Only the rapporteur of the specification
• Only the Support Team

E13 What is an Internet-Draft?

• A published standard awaiting a number
• The IETF's equivalent of a change request
• A working document with no formal status, which may change or vanish at any time

E14 What are the two steps of a 3GPP decision on a change request?

• The plenary votes, then the working group confirms
• The working group agrees it, the parent TSG approves it
• The rapporteur accepts it, the Support Team publishes it

E15 What does the first pair of digits in a 3GPP specification number tell you?

• The subject area it covers
• The working group that owns it
• The release it belongs to