Summary

  • A policy record should distinguish proposal, discussion, adoption and implementation.
  • Official process pages describe parts of that chain; they do not prove the status of every individual proposal.

A decision is not yet an operating instruction

A reader may find a meeting outcome or a mailing-list notice and reasonably ask a second question: which policy text governs now, and what evidence shows that implementation has begun or become effective? Treating every public decision as an operating instruction collapses stages that official processes keep separate.

APNIC describes proposal discussion, consensus, comment and endorsement steps. ARIN describes public policy records, a documented policy life cycle and staff implementation of adopted number-resource policy. RIPE and the Address Supporting Organization publish their own policy-development entry points. These records support a trace; they do not establish the implementation date of a particular proposal without proposal-specific evidence.

Keep the chain explicit

An adoption-and-implementation ledger can retain: the proposal identifier and text; the relevant public discussion; the consensus, adoption or endorsement record; the authoritative policy text; and a bounded implementation-status record. Each item should have a source, owner and observation date. The ledger is a governance aid, not a substitute for an RIR's official policy publication.

Facts, inference and unknowns

The documented facts are the published processes and records. The inference is that linking their stages reduces ambiguity for operators and researchers. Unknowns include whether a specific proposal was implemented, when it took effect and what downstream systems changed; those questions require direct evidence rather than assumptions.

Sources