Summary
- Section 8.1 of the Address Council's Operating Procedures hands it the appointment ballot and then states it "shall have no power to remove a Non-Representative Appointee", the class its definitions say includes ASO-appointed ICANN Board members.
- The removal route that does exist sits in a separate instrument: the NRO Executive Council accepts or rejects a petition, and the Address Council may only recommend how that petition should be handled.
- Seat 9 shows the machinery running end to end — selected 15 August 2026, designated by the Empowered Community Administration on 18 August, announced 25 August, serving to the close of ICANN 90 on 4 November 2027.
Three sentences that allocate a power
Section 8.1 of the Operating Procedures does two jobs in one paragraph, and it deserves to be read whole rather than paraphrased: "The Address Council shall vote to appoint members to external bodies using the ballot process in Section 7.2. The Address Council may remove any Representative Appointee by approving a proposal to do so by ballot vote under Section 7.2. The Address Council shall have no power to remove a Non-Representative Appointee." (ASO AC Operating Procedures)
The middle sentence alone reads like a recall power. With the third beside it, it is a boundary line, and the boundary is drawn by a definition rather than by argument. A Non-Representative Appointee is "a person the Address Council has appointed or recommended to serve on an external body who does not serve on that body as a representative of the Address Council" — and then, closing the door politely: "For the avoidance of doubt, ASO-appointed members of the ICANN Board are Non-Representative Appointees."
So the Council may remove a person it sent somewhere as its own delegate, and may not remove a person it sent to the ICANN Board. Both halves were drafted. Neither is a silence a reader has to fill in.
What Section 9 builds, and where it stops
Section 9.1 states the authority without ornament: "Under Sections 7.2 and 9.2 of the ICANN Bylaws, the ASO is responsible for selecting persons to fill seats 9 and 10 of the ICANN Board." The standalone Board Selection Procedures page reproduces that sentence word for word, alongside the same Section 9 numbering (ASO AC ICANN Board Selection Procedures).
The rest of Section 9 assembles a selection and then stops. Section 9.2 puts the beginning of each term in the ICANN Bylaws and prints no term length of its own. Section 9.4.7 requires a selection phase of at least 14 days and gates the announcement on ICANN finishing due diligence without any significant concerns. Section 9.4.8 sends the successful candidate's name and contact information from the Secretariat to the ICANN Secretary. Section 9.4.9 leaves due diligence with ICANN and promotes the next highest vote-getter if the selected candidate fails it.
Section 9.4.10 keeps election results and vote counts with eligible voters and calls them "strictly confidential". Section 10 is titled "Rules of Order" and holds two subsections, parliamentary procedure and special rules of order.
Nothing in Section 9 or Section 10 returns the ballot Section 8.1 withheld. The document is consistent with itself, which is the interesting part: this is an appointing instrument that says out loud it is not a removing instrument.
On the candidate side the paperwork is signed. No candidate is considered who does not sign a Certification Letter attesting to compliance with ICANN's requirements and to conduct and character, and the nominee returns that letter with a questionnaire.
A majority on paper, a tally nobody publishes
The threshold is not decorative. Section 7.2.3 requires first-choice votes from "an absolute majority of the voting members", with eliminated candidates' votes transferred until someone crosses it; Section 7.2.6 keeps an abstention out of the denominator when the majority is counted. What the public receives is narrower than the arithmetic: a name, a region, a term. Under 9.4.10 the distribution of support is not part of the record, so a reader can see who won and not how nearly someone else did.
Seven weeks from vacancy to designation
Seat 9 shows how the machine behaves under time pressure. At its 1 July 2026 teleconference the Address Council voted by majority to use the extraordinary route in Section 9.5.3, "Selection from Address Council Nominations". Electronic voting opened on 8 August 2026. Oscar Robles was selected on 15 August 2026, after due diligence was complete. The Empowered Community Administration designated him on 18 August and notified the ICANN Secretary under Section 7.25 of the ICANN Bylaws. The public announcement followed on 25 August (2026 extraordinary selection to fill the Seat 9 vacancy).
The procedure leaves little room for a public argument. Section 9.5 is chosen by "majority vote of the Address Council (internal matter)", and the person selected serves "for the remainder of the term of the vacated seat". Section 9.5.3 requires AC members to nominate at least two candidates, each of whom completes the Certification Letter and questionnaire within 15 days and is then selected under the Section 9.4.7 procedure. The Council's own announcement records at least two certified candidates, evaluation and interviews, and the submission of the winner's nomination for formal designation by the Empowered Community (ASO AC selects Oscar Robles to fill ICANN Board Seat 9 vacancy).
The term is bounded by a meeting, not by a number of years. Robles serves through the conclusion of the ICANN 90 Annual General Meeting on 4 November 2027, and under Section 7.8(e) of the Bylaws filling a vacancy does not count as a term against the three-consecutive-term limit. Section 9.5's "remainder of the term" is thus a real remainder rather than a fresh clock.
The standing register prints the same seat in coarser grain: Oscar Robles, Seat 9, LACNIC, "August 2026" to "ICANN 90, 4 November 2027"; Christian Kaufmann, Seat 10, RIPE NCC, October 2025 to ICANN 93 on 26 October 2028 (ICANN Board Appointments). Because Kaufmann, the Seat 10 director, is from the European Region, European candidates were ineligible for the Seat 9 vacancy, and the extraordinary process carried no public call for nominations and no public comment period.
Where the removal actually lives
A removal route exists. It belongs to somebody else. The ASO's procedures for Empowered Community powers state that they apply to the Community's exercise of its right to remove one or more ICANN Directors, and they list three routes: the NomCom Director Removal Process, the SO/AC Director Removal Process and the Board Recall Process. On a petition concerning a director the ASO AC nominated, the NRO Secretariat informs the AC and arranges a teleconference; the AC "may make a recommendation to the NRO EC regarding how the petition should be handled". The NRO Executive Council decides whether to accept or reject the petition, and whether to support another Decisional Participant's petition. The ASO EC Administration Representative then communicates that decision to the Empowered Community Administration and ICANN (ASO Procedures for Empowered Community Powers).
The body that selects is a recommender when the question turns to removal. The deciding body is one level up, in the NRO Executive Council, and the formal act runs through the Empowered Community. Read with Section 8.1, the design is coherent: the same body is denied both the removal vote and the removal decision, and the check on its appointment sits outside it.
The instrument that delegated both halves
The ICANN–NRO Memorandum of Understanding executed on 7 November 2019 makes the split visible at the source. The NRO fulfils the role, responsibilities and functions of the ASO under Article 9 of the ICANN Bylaws, and one stated purpose is "defining accessible, open, transparent and documented procedures for the selection of individuals to serve on other ICANN bodies, including selection of Directors of ICANN". The Address Council's responsibilities include "defining procedures for selection, removal, and recommendations for the removal, of individuals to serve on other ICANN bodies, in particular on the ICANN Board", and all such procedures "shall be submitted to the Executive Council of the NRO for approval" (ASO MoU executed 7 November 2019).
The Council was handed selection and removal together. It defined selection as a vote, removal as a recommendation, and the definitional line that separates an ICANN Board seat from an ordinary delegation. That narrowing sits inside an approved procedure, not in an unconsidered silence — which is why the finding belongs to the text and not to anyone's motives.
What this record does not settle
The Operating Procedures page, as read for this article on 19 November 2026, carried no overall version number and no single effective date; its "Overview of Updates" table shows one entry dated only "24 October", with no year, beside entries for 10 February 2020, 19 November 2019 and 1 July 2020, and the page footer was not visible in the text available (ASO AC Operating Procedures). The quotations above come from that page as returned, not from a continuous read of the whole document.
The register and the timeline do not reconcile at the level of a single date, and neither is wrong. "August 2026" does not say whether it means selection, designation or seating; the timeline gives 8 August for the opening of electronic voting, 15 August for the selection and 18 August for the designation. The Empowered Community procedures do not state the internal voting threshold by which the NRO EC reaches its decision. The relationship between the standalone selection procedures page and the consolidated Operating Procedures is not stated in either text.
The MoU's extracted text is word-fragmented, so its punctuation and section numbering are not reliably recoverable and it was not read continuously. And the 25 August announcement is a publication date, not a distinct effective date of appointment.
The narrower question the record raises is legibility rather than legitimacy. The count is confidential, the designation is formal, the removal decision belongs to the NRO EC, and the public trace is a name and an end date. A community that wants to know how firmly its two Board seats are held can find the front door plainly marked. What it cannot find in these seven documents is a procedure under which the selector answers for the appointment it made.
See the ASO Address Council entry for the body itself.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






