Summary

  • AFRINIC’s management made three charges against Cloud Innovation on 23 June 2020; Cloud Innovation answered each on 13 July 2020. Its page Did Cloud Innovation break AFRINIC’s rules? sets out the record.
  • For use outside AFRINIC’s region, the letter cited section 6 of the bylaws, which defines membership. The only policy sentence on it, CPM 5.4.6.2, belongs to rationing that began on 31 March 2017, after Cloud Innovation’s blocks were allocated.
  • The courts restrained AFRINIC three times in 2021. No court has found that Cloud Innovation broke an AFRINIC rule.

What did AFRINIC’s letter of 23 June 2020 accuse Cloud Innovation of?

Three things, in a letter of 23 June 2020 from AFRINIC’s management to Cloud Innovation, a Seychelles company and an AFRINIC member since 2013.

First, in the words of AFRINIC’s management, that “some 2026 records pertaining to your company appear to be inconsistent with what is visible in the global routing”. That is a count of 2,026 records, not a year. Cloud Innovation’s reply of 13 July 2020: “there is no reliable or meaningful correlation between the location where an Autonomous System Number (‘ASN’) is registered and the location where IP prefix announcements are originated from that ASN.”

Second, that “most of the utilisation records registered in the AFRINIC WHOIS database show a usage that is not consistent with the ‘needs’ expressed”, and that Cloud Innovation “failed to notify AFRINIC of these changes promptly, accurately and fully”. The reply: “we have very strict policies in place to ensure that the utilization of the IPs we assign to our customers are based on a strict need-basis only”, and “conducting updates through the WHOIS database is a sufficient and reasonable notice to AFRINIC.”

Third, that “the majority of the IP Number Resources allocated to Cloud Innovation Ltd by AFRINIC are not originating services within the AFRINIC service region as required by section (6) of the AFRINIC Bylaws”. The reply: “section 6 of the By-laws has no relevance in supporting your allegation”.

The letter set a deadline of 14 July 2020. Cloud Innovation answered a day early and concluded: “we strongly deny having acted in any way in breach of the Agreement, Policy Manual and/or the By-laws.”

What did the letter cite for each charge?

A policy section and a contract clause, then contract clauses, then a membership clause. For the first charge, AFRINIC’s management cited section 5.3.2 of the Consolidated Policy Manual and clause 4(c)(ii) of the Registration Service Agreement, which, the letter said, Cloud Innovation signed on 23 July 2013. For the second, clauses 2(d), 4(c)(i) and 6(d)(iii) of the same agreement.

For the third, about where addresses are used, it cited no section of the policy manual, only section 6 of the bylaws: “We find it apt to remind you that ‘Membership’ is clearly and unequivocally defined in section 6 of the Bylaws.” It then named the soft-landing policy as the exception: addresses “must originate services within the defined region, except as regards those issued under the ‘SOFT-LANDING Policy’”. The letter knew where the one policy sentence on use outside the region sits. For the charge itself, it reached for a definition of membership.

What does section 6 of AFRINIC’s bylaws say?

Who may be a member, and nothing about where addresses are used. Cloud Innovation’s reply: section 6 “merely defines who is eligible for AFRINIC membership and what are the different types of ‘Members’”; “it does not specify anything in regards to the manner or location of usage for the IP number resources.” Administration of the registry, the reply added, is “controlled by the policies developed through a bottom-up open public policy process”.

A letter can describe a rule; it cannot create one. A section that defines membership is not a rule on where a member’s customers may be. Lu Heng, the internet entrepreneur behind Cloud Innovation, names the move in his Note 61 on heng.lu: “It was converting the absence of permission into a claim of control.” And: “That is not a small difference. It is the difference between applying policy and manufacturing policy.”

Is there any AFRINIC rule on where addresses are used?

One sentence, and it does not cover Cloud Innovation’s addresses. CPM section 5.4.6.2: “AFRINIC resources are for AFRINIC service region and any use outside the region should be solely in support of connectivity back to the AFRINIC region.”

It is a condition for receiving addresses in the “Exhaustion Phase” of the soft-landing policy, whose first phase, by AFRINIC’s own account, began on 31 March 2017. AFRINIC’s own published statistics show Cloud Innovation’s four blocks allocated in July 2013, December 2014, December 2015 and September 2016, all before that rationing began.

The letter called the soft-landing condition the exception to a general rule. The policy manual has no general rule; BTW has set out what AFRINIC’s out-of-region rule says and whose addresses it covers. Lu Heng: “The clause most commonly cited in support of a territorial-use restriction appears inside the Soft Landing framework. It is not framed as a general master rule for all AFRINIC-issued resources.”

How did AFRINIC decide where the addresses were used?

By the country in which a network’s AS number (Autonomous System Number) is registered. Cloud Innovation’s reply: “your reliance on the country registration of the ASN as the sole determining factor to indicate the alleged inconsistencies … is erroneous.” It sent its own spreadsheet with traceroute examples.

On the routing table: “it is not uncommon to advertise a covering aggregate while registering only the component more specific prefixes in WHOIS.” Those more specific prefixes “are the only ones that reflect the actual usage of the IPs”. The 2,026 records the letter flagged measure AFRINIC’s method, not Cloud Innovation’s use.

What does the WHOIS record show?

That Cloud Innovation registered its assignments. AFRINIC’s management built its charges on “an examination of the utilisation records registered in the AFRINIC WHOIS database”: records Cloud Innovation had entered itself.

The reply: “We take great pains to accurately register each assignment”. By Cloud Innovation’s account, its updates alone at one point made up about 80% of all the updates made to AFRINIC’s WHOIS database. Its page: “A member with something to hide does not fill a registry’s database with its own updates.”

What happened after the reply, and what have the courts done?

AFRINIC’s management escalated, and the courts restrained it. In March 2021, on the first day of a national lockdown in Mauritius, “when access to justice was very limited”, as the Supreme Court later put it, AFRINIC’s management gave Cloud Innovation 30 days to answer what the Court called “purported breaches”, or face termination at its “sole discretion”. BTW has explained what AFRINIC’s contract lets it do to a member.

The Judge in Chambers restrained AFRINIC from ending Cloud Innovation’s membership on 29 March, 13 July and 3 December 2021; the last order protects it until the dispute is finally determined. On 19 July 2022 (2022 SCJ 253) the Supreme Court held that Cloud Innovation “cannot be taxed for resorting to an independent court to safeguard its rights”, and recorded that those then running AFRINIC “deliberately flouted” its order of 13 July 2021. BTW tracks every AFRINIC court decision since 2021. No court has found that Cloud Innovation broke any AFRINIC rule.

The most repeated charge against Cloud Innovation rested on a membership clause, and the one policy sentence on the subject belongs to rationing that began after its addresses were allocated. Cloud Innovation’s page Did Cloud Innovation break AFRINIC’s rules? sets out the full record.

Sources