Summary

  • The Service Level Agreement for the IANA Numbering Services, dated 29 June 2016, names ICANN as "Operator" and AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC as the RIRs. The NRO is not in the party clause, although it hosts the signature text and registers the current version.
  • Four retrieved full texts print a twelve-month non-renewal notice and a thirty-calendar-day cure period that begins only after a majority arbitrator's decision. ICANN's own overview page prints six months, and it is the page most readers meet first.

Start with the party clause, because most descriptions of this contract get it wrong — including the one I wrote to commission this briefing. The Service Level Agreement for the IANA Numbering Services is dated 29 June 2016, and it is not an agreement between the Number Resource Organization and ICANN. The passage returned from the retrieved texts names "Internet Corporation for Assigned Names and Numbers … (In this agreement ICANN is referred to as 'Operator')" and then AFRINIC Ltd, APNIC Pty Ltd, the American Registry for Internet Numbers, the Latin American and Caribbean Internet Addresses Registry and Réseaux IP Européens Network Coordination Centre, "collectively, 'RIRs'" (ICANN's hosted text of the agreement). The NRO hosts the signature version and its register lists the current version of the instrument; it is not named as a party in that clause (NRO version register).

That correction is not pedantry. It decides who may end the arrangement. The counterparties who must judge a failure and may terminate are the five registries, and the party that must keep the service running is ICANN, styled the Operator. Every lever in this contract sits in one of those two hands, and the interesting part is how differently the two hands are priced.

The term is automatic; the calendar is not printed. Article 10.2 says the term runs five (5) years after the Commencement Date and "shall renew automatically for consecutive five (5) year term unless earlier terminated or not renewed" (NRO-hosted signature-version text). The Commencement Date is not a date in the contract: Article 1.1 defines it as "The date on which the Condition Precedent is satisfied", and the Condition Precedent is defined by reference to the Operator being released from obligations to provide substantially similar services under its NTIA/DOC contract dated on or about July 2012, and to the Operator having accepted responsibility for the IANA Numbering Services. Article 10.1 adds that the agreement has no force or effect unless that condition is satisfied on or before 1 October 2017.

So the start had to be read from two other documents. ICANN's overview page carries the status line "01 October 2016: The SLA is now in effect", and ARIN's transition announcement states that the expiration of the prior contract "established the commencement date of the Service Level Agreement (SLA) entered into between ICANN and the five Regional Internet Registries (RIRs) for the administration of the IANA Numbering Services" (ICANN's stewardship overview; ARIN's transition announcement). Take 1 October 2016 as the start and the arithmetic is dull and unforgiving: five-year terms end on 30 September 2021, 30 September 2026 and 30 September 2031. On 20 November 2026 the agreement is therefore sitting inside a third five-year term that began without any new instrument, on the assumption that no non-renewal notice was served — none was obtained in this review. Nobody signed anything new. The old document simply kept going.

The exit needs nothing but a notice. Article 10.3, headed "Right not to renew": "Either Party may elect not to renew this Agreement by providing a notice of non-renewal to the other Party at least twelve (12) months prior to the expiration of the then-current term" (NRO-hosted signature-version text). No cause, no arbitral finding, no cure period. Twelve months, either side, done.

Now read the description of that clause on the operator's own stewardship overview: the agreement renews every five years "unless either ICANN or the RIRs elect to not renew for any reason (with or without cause) by providing six-months' notice prior to the expiration of the then-current term" (ICANN's stewardship overview). Six months. The overview gets the party structure, the automatic renewal and the absence of a cause requirement right; it halves the notice.

A summary page cannot amend a signed agreement, so the operative window is the one printed in the instrument. And the instrument prints twelve months in every full text retrieved — not once, four times, from four publishers. ICANN's own document page for the 29 June 2016 agreement prints twelve (ICANN's hosted text). The NRO-hosted signature version prints twelve (NRO-hosted signature-version text). ARIN's Vault holds the agreement text as Exhibit H for the Board of Trustees meeting of 20 May 2016, the meeting at which the Board authorised its President to execute the agreement with ICANN in coordination with the other registries, and that text prints twelve months and a thirty-calendar-day cure (ARIN exhibit H). RIPE NCC hosts a full text expressly labelled "Public Draft v5.0 – 15 March 2016" and it too prints twelve months and thirty days, which is corroborative only, since a pre-signature draft is not the executed instrument (RIPE NCC hosted text).

One NRO-hosted text cuts the other way: a version marked v2.6 prints a six-month non-renewal notice and a fifteen-day cure period (NRO-hosted v2.6 text). Its date, its version status and its relationship to the executed agreement were not established from the passages retrieved, so it cannot set the window. It does explain how a six-month sentence can circulate in good faith.

What the wrong number costs. Here is the arithmetic, plainly labelled as arithmetic on the two texts and not as a quotation from either. If the current term ends on 30 September 2031, a twelve-month notice had to arrive by 30 September 2030. A reader who planned around the summary's six months would instead diarise 30 March 2031 — and would be six months late, with the next term already renewed and the next exit five years away. Notice periods are the one contract term where being approximately right is the same as being wrong.

The remedy is expensive in a way the exit is not. Article 9.2 lets the RIRs invoke dispute resolution under Article 13 where they determine that the Operator has materially failed to perform or materially breached the agreement, "with possible termination under Article 10". Article 10.4 supplies the sequence: "the Operator shall have thirty (30) calendar days from the date of the decision of a majority of the arbitrators as described in Article 13.2.8 to remedy any such failure to perform (referred to as 'Cure Period')", and if the RIRs judge in their sole judgment that it was not remedied, "the RIRs may, in their sole discretion, immediately terminate this Agreement" (NRO-hosted signature-version text).

Read those two routes side by side. Leaving needs a letter. Enforcing needs a majority arbitral decision, and the cure clock does not even start until that decision exists. The document is fully equipped to measure the service and deliberately slow to punish it: the operational clocks that do run are the ones that get a request moving, not the ones that end a contract. Acknowledge an RIR request within two Business Days, and where information is needed, ask for it specifically and completely within four Business Days; update the registry within four Business Days of acknowledgement or of the additional information, whichever is later; if the request cannot be met in ten Business Days, file a written status report (NRO-hosted signature-version text). After thirty Business Days an unsatisfied valid request may be asserted as a failure to perform, if Article 9 is satisfied. Then the arbitration, then the cure period, then the sole judgment of five registries.

The measurement runs on a different clock again. Article 6.2.1 requires Performance Standards Metric Reports published monthly and no later than fifteen calendar days after month-end, starting no later than six months after the Commencement Date; Article 6.2.2 requires an annual Numbering Service Survey; Article 6.2.3 an annual security and systems audit with a report to the RIRs (ICANN's hosted text). Monthly reporting on a fifteen-day tail is a tight cycle. The consequence attached to a bad month is not.

The grader sits one document away. Article 8, "Review of IANA Numbering Services", says that the RIRs may periodically review the services, namely the deliverables and reports articulated in Article 6.2, and that during any such review the Operator must cooperate with and facilitate it. That is the whole of the Article 8 text returned — no committee, no verdict, no obligation attaching to a finding. Yet the NRO's own page, dated 4 October 2016, describes "the establishment of a Review Committee to ensure that the IANA Numbering Services Operator maintains the service level defined in the SLA" and tells readers that "Further description of the Review of IANA Numbering services is described in Article 8 of the SLA" (NRO on Review Committee composition). The description points at a clause whose returned text does not contain it. That is a bounded finding, not a verdict on the agreement: the full text was not read page by page here, and the committee may be named elsewhere. But a reader who follows the pointer lands on two sentences about review and cooperation.

The register, and one annex that will not stay put. The NRO register lists the current version as "SLA: IANA Numbering Services 29 June 2016" with "Amendment No1.:Incorporation of Reverse Resolution Services" dated 12 November 2024, on a page last modified 15 April 2025 (NRO version register). The executed amendment text was not obtained in this review, so the current reverse-resolution service levels cannot be quoted here. There is a smaller wrinkle worth knowing: an NRO announcement of 31 May 2016 records that the parties had agreed two days earlier "to remove any references to an Annex as the description in Article 4.3 is sufficient for the purposes of the SLA", while the signature-version text still carries Article 4.1 pointing to Annex A (NRO announcement, 31 May 2016). A reader looking for the metrics annex should expect to find the operative requirements in Articles 4.3 and 6.2 instead.

What this review did not obtain. The complete Annex A; the executed Amendment No. 1 of 12 November 2024; any renewal or non-renewal notice for 2021 or 2026; any arbitration record under Article 13; the execution and signature pages; and any text making a review-committee verdict binding on the parties. Each quotation above is a passage reported back from the retrieved text of the linked document. The PDFs were not rendered or paginated independently, and no annex, signature page or amendment text was opened.

So hold the operator to which clock? The one in the document. Twelve months before the end of the current term is the window that ends the arrangement without a reason; if the complaint is about the service rather than the relationship, the contract makes you build a record — monthly metric reports, a survey, an audit, an unsatisfied request that survives thirty Business Days — and then win a majority arbitration before a thirty-day cure period even begins. That is the structure, in its own words. Anyone planning around the six-month sentence on the overview page is planning around a description, and getting the date wrong at the only moment the date matters. The registry itself is the IANA entry in our directory.