Summary

  • The NRO Executive Council has provided the proposed RIR governance document to ICANN for consideration, ARIN said at its 22 October meeting.
  • ARIN named four milestones ahead: last call, public comment, adoption by RIR and ICANN boards, and implementation procedures.

The draft has reached another desk. In ARIN’s meeting slides, chief legal officer Michael Abejuela says the NRO Executive Council has provided the RIR governance document to ICANN for consideration. The ARIN Day 1 account adds that RIR and ICANN teams met during ICANN 87 and describes their discussions as productive. Neither source supplies a board vote or a final adoption date.

The handoff matters because it replaces a vague promise to keep talking with a visible sequence. ARIN lists a last call on the final draft, a public comment process, adoption by the RIR and ICANN boards, and development of implementation procedures by the RIRs and ICANN. Those are different acts by different people. A last call tests a text; public comment builds a record; boards decide whether to adopt; implementers turn clauses into procedures that registries can actually run.

The slides give no calendar for the four steps. Abejuela says updates on the next round of community engagement will follow ICANN 87. The public record therefore offers a useful starting line and a list of checkpoints, rather than a finish time. Readers can ask for the final draft, the comment window, each board’s decision and the operating procedures as separate records.

For network operators, the last of those records may be the one that arrives at the desk. Governance language becomes concrete when a registry must document compliance, handle an interruption or explain a decision affecting a number-resource record. The document has crossed an institutional boundary. The practical boundary will be crossed when adopted language has an accountable way to work.