ARIN-prop-27: RSA Modification Procedure

What changed

Version 1.0 proposed putting changes to ARIN's Registration Services Agreement through public policy discussion, allowing a Board veto on advice of counsel, and announcing changes at least 30 days before they took effect. Owen DeLong circulated the proposal on 18 April 2006; the retained Member Services announcement followed on 20 April. These are proposed procedural changes, not evidence that the agreement or policy was amended.

What the debate was really about

The central issue was whether registrants would have a predictable opportunity to see and challenge changes to the agreement governing their relationship with ARIN. Edward Lewis asked whether the agreement was common to all registrants and how the veto would work; DeLong clarified that he intended a legal-risk exception. Michael Dillon and Scott Leibrand requested clearer terminology. Their wording requests should not be counted as support for every substantive clause.

Arguments that prevailed

• The available decision evidence does not establish which substantive argument prevailed. The Board chair's commitment to consider notice and review shows attention to the issue, not acceptance of the proposed clauses.

Arguments that did not prevail

• No substantive argument can be classified as defeated from this linked April record. The request to replace the abbreviation RSA with RS Agreement received support and a conditional willingness to revise, but no retained revised version proves that the wording changed.

Decision vs debate

The retained record establishes a proposal, discussion and announced procedural consideration. Member Services described receipt and Advisory Council review; John Curran said the Board would consider notice and review arrangements. Neither message establishes adoption. The linked April discussion and retained proposal do not establish a final disposition, and the policy's recorded decision status remains unknown.

Participation concentration

Eight linked messages represent six discussion participants over four days. The proposer wrote three messages, or 37.5% of this observed exchange; the other participants wrote one each. That concentration partly reflects submitting and clarifying a proposal. It does not measure votes, community representation or control of the outcome. No separate formal-actor record is attached to this snapshot, which does not mean institutional actors were absent.

Chokepoint analysis

The proposed procedure would make contract changes visible to resource holders before taking effect and give them a public forum to question those changes. The Board's legal-advice veto would remain a point of discretion. From a registrant's perspective, meaningful accountability would depend on timely notice, a usable opportunity to respond, and reasons that make the scope of a veto understandable. The discussion identifies those design questions but does not show that the proposed safeguards were implemented.

Uncertainties

• The linked April messages are not a complete record of subsequent Advisory Council, Board, petition or community proceedings; the final disposition still requires source-backed reconciliation.
• The proposal's account of existing notice practices is the author's rationale. It does not independently establish the legal effect of every registrant's agreement.
• A service-address announcement is institutional process communication. The enclosed text attributed to Owen DeLong is not evidence of Member Services' own policy preference.
• The observed counts describe retained, linked messages. They do not establish the size or representativeness of the wider community, nor any later operational effect.