IEEE 802's WRC-27 statement needs an expiry record

Summary

IEEE 802 LMSC filed its response to the EC Radio Spectrum Policy Group's Draft Opinion on WRC-27 on 21 August 2026 after a 10-day ballot. Among 13 eligible voting roles, 10 approved, none disapproved, one abstained and two did not vote.
The final document says it solely represents IEEE 802 LMSC, not necessarily IEEE or IEEE Standards Association. The current LMSC Operations Manual says statements of this kind expire five years after issue.
Expiry should end the claim that the document is a current institutional view. It should not destroy the statement, the approval denominator, the submitted revision, the represented-body boundary or later correction and supersession evidence.

A statement has two lives

On 21 August 2031, if the current rule remains applicable, IEEE 802 LMSC's WRC-27 comment will cross a line that most public positions never show so plainly. The PDF may still exist. Its arguments may still be quoted. Its subject may still matter. But it should no longer be presented as IEEE 802 LMSC's current view merely because an archival link still works.

That is the first life of the document: representative authority. It begins with a valid institutional act and ends under the institution's own five-year rule.

The second life is evidentiary. It records what one named body approved, who was authorised to issue it, which version was actually sent, whom it addressed and how its scope was limited. That life should survive the authority clock. Otherwise expiry becomes a method for erasing the history needed to test later accounts of the decision.

The distinction matters because the same public page can serve two audiences. Policymakers and implementers want to know whether a statement is still operative. Researchers, members and future officeholders need to know what the institution said at a particular time. A date alone does not reliably answer both questions.

IEEE 802 already supplies the foundation for a better distinction. Its public-statements page states that, under Section 7.2.1 of the Operations Manual, all IEEE 802 LMSC public statements to government bodies expire five years after issue. The same page retains links to submissions from 2020, 2019 and 2018. Their continued visibility is compatible with an archive. It is not evidence that they remain current positions, and it does not show that every status has been labelled correctly.

The design problem is therefore not whether an old file may remain online. It is whether a reader can distinguish an expired record from a standing mandate without reverse-engineering the rule and calculating the date.

What the LMSC actually approved

The WRC-27 response travelled through a visible internal chain.

IEEE 802.18 approved a draft on 6 August with 12 yes votes, no votes against and one abstention. On 10 August, a 10-day IEEE 802 LMSC electronic ballot opened. The motion identified revision 07 of document 18-26-0068, authorised submission to the EC Radio Spectrum Policy Group before the deadline and granted the LMSC chair or delegate editorial licence.

The result notice closed the ballot on 21 August. It listed 13 eligible voting roles. Ten approved, none disapproved, one abstained and two did not vote. The return rate was 84.6%. The notice said the motion passed under Section 7.2.1 and the applicable voting rules.

The file linked from the public-statements page is revision 08. It carries an electronic filing date of 21 August and the signature of James Gilb, the IEEE 802 LMSC chair. The movement from the balloted revision 07 to the filed revision 08 may be consistent with the editorial licence. The checked record does not justify assuming that every change was merely editorial without a revision comparison. That is precisely why the submitted revision and its exact bytes belong in the public receipt.

The document addresses the RSPG's draft opinion and discusses WRC-27 agenda items affecting Earth-observation measurements, ultra-wideband systems, inter-satellite service, Wi-Fi 6E and Wi-Fi 7, and possible IMT identification. Those details establish that the submission was subject-specific, not a generic declaration. This article does not decide whether its spectrum recommendations are correct.

The ballot proves an internal act within a defined body. It does not show that every eligible role voted, that an external institution accepted the argument or that the decision carries authority beyond the represented body.

The authority was narrow from the start

Current Operations Manual v27 gives the statement a precise institutional perimeter. Section 7.2.1 says an IEEE 802 LMSC public statement to a government body requires prior approval by two-thirds of the LMSC. It must be issued by the LMSC chair as the view of IEEE 802 LMSC, copied to the LMSC and the IEEE-SA Standards Board Secretary, and posted on the LMSC website. The website must state that such statements expire five years after issue.

The filed PDF narrows the perimeter again. A footnote says the document solely represents IEEE 802 LMSC and does not necessarily represent IEEE or IEEE Standards Association. The body also acknowledges that other IEEE organisational units may hold perspectives that differ from or compete with its own.

These are not decorative disclaimers. They identify the principal that authorised the speech. The vote does not turn one committee's position into a position of all IEEE. The chair's signature does not enlarge the body represented. Publication on an IEEE domain does not erase the limitation.

The receiver has a separate role. RSPG invited identifiable stakeholders to comment on its draft opinion between 18 June and 24 August. It says responses are normally published unless a respondent asks otherwise, and that neither RSPG nor the European Commission is liable for their content. Publication by the consultation host, if and when it occurs for this response, would document receipt or public availability. It would not be adoption.

The wider EU process makes that boundary important. The Commission opened a separate call for evidence from 14 July to 11 September. It expected a final RSPG opinion by the end of 2026 and planned a proposal for a Council decision in the first quarter of 2027. WRC-27 itself is an ITU conference scheduled for 18 October to 12 November 2027 in Shanghai. An IEEE 802 submission is an input into that chain, not the EU position or the conference outcome.

Expiry is not retraction

A single label—old—cannot describe every later state of a public position.

An expired statement reached the end of its authorised period. A superseded statement has a newer position taking its place. A corrected statement contains an identified defect repaired by a later record. A withdrawn statement was affirmatively removed from institutional reliance. A retracted statement would carry a stronger repudiation. None of those states can be inferred merely from the passage of five years.

The distinction protects both the institution and its critics. IEEE 802 should not be held indefinitely to a view that its manual has caused to expire. Equally, the expiry date should not allow anyone to claim that the statement never existed, lacked approval or was repudiated. An archive proves a historical act; it does not renew that act.

The rule also prevents a subtle form of mandate inflation. A PDF can outlive the people, market conditions and technical studies that produced it. Search results strip away dates. Quotations travel without footnotes. A functioning link may be treated as present endorsement. Automatic expiry places the burden on anyone claiming continuing authority to obtain a fresh institutional act.

But expiry without state metadata creates the opposite risk. A reader sees the old file and cannot tell whether it is expired, superseded or corrected. Another reader assumes its disappearance means it was rejected. Both errors are avoidable.

An archive is evidence, not standing authority

The public-statements page demonstrates that authority and retention need not have the same duration. It presents the five-year rule and also carries older documents. The cautious reading is that a historical index can remain useful after a statement's current status ends.

That design should be made explicit. The archive should preserve the original submitted artifact rather than silently replacing it with a newer file. A correction should link forward and back. A superseding position should identify what it supersedes. If a receiver publishes a response set or disposition, that record should be connected without suggesting endorsement where none exists.

The archived ballot matters too. “Approved” without the denominator conceals participation. In this case the exact record—13 eligible roles, 10 approvals, no disapprovals, one abstention and two non-votes—shows both the required approval and the limits of the act. The result is stronger evidence than a generic reference to consensus, but it remains evidence of IEEE 802 LMSC's internal authority only.

An archive therefore performs a thin but important function. It preserves attribution, provenance and sequence. It should not decide spectrum policy, extend representation or convert a historical committee act into permanent institutional law.

The smallest useful statement-state record

IEEE 802 need not build a new bureaucracy to make the distinction auditable. One compact record per statement would be enough.

The identity block should contain the document number, the exact submitted revision, a stable URL and a file digest. It should preserve revision 07 as the balloted input and revision 08 as the filed artifact, with the editorial-authority link between them.

The authority block should name the approving body, the governing rule, the full ballot denominator and result, the authorised issuer and the body represented. It should repeat the exclusions: not necessarily IEEE, not necessarily IEEE Standards Association.

The proceeding block should name the receiver, draft or docket, consultation window, filing date and deadline. If the receiver later publishes the response or a disposition, the record can link it with a neutral status such as received, published, acknowledged, considered or not documented. Those words should reflect evidence, not conjecture.

The state block should carry the issue date, computed expiry date and one current status: current, expired, superseded, corrected or withdrawn. Corrections and superseding statements should be bidirectional links. The original bytes, approval record and historical URL should remain available in every state.

That is a modest record of institutional action. It does not demand that every statement remain policy forever. It makes the opposite promise: the mandate can end without the evidence ending with it.

What the record does not establish

No checked source shows that RSPG has published or substantively disposed of this specific submission. No correction, withdrawal or superseding IEEE 802 statement was located. The public page's older entries may be deliberate archive practice; their presence alone does not prove faulty enforcement of the expiry rule.

The date 21 August 2031 follows from applying the published five-year rule to the issue date. It is not a separate expiry notice located for this document. A later rule, correction, withdrawal or superseding statement could change the practical status before then.

Most importantly, procedural clarity does not validate the technical recommendations. A complete authority receipt can show exactly who spoke and under what rule. It cannot prove that the proposed spectrum outcome is wise, compatible or adopted.

IEEE 802's WRC-27 Comment Expires in Five Years. Its Public Record Should Not

Why it matters

Summary

A statement has two lives

What the LMSC actually approved

The authority was narrow from the start

Expiry is not retraction

An archive is evidence, not standing authority

The smallest useful statement-state record

What the record does not establish

Sources

Deeper Profile Context

Strategic Circle

Leadership Alliance

Strategic Circle Briefing

Leadership Alliance Briefing