Summary

  • Resolution 202106.616 authorised any one of three named representatives of Executive Services Ltd to provide AFRINIC's basic information and beneficial-ownership information when a competent authority requested it under section 190(6)(a) of the Companies Act 2001.
  • The authorisation concerned information about AFRINIC as a company. It did not extend to AFRINIC's member register, WHOIS or RDAP contacts, Internet number-resource records, routing data, customer files, policy-participant records or the beneficial control of an IPv4 holding vehicle.
  • The public resolution proves that the Board created the channel, but it does not establish that a request arrived, that a disclosure occurred, which fields would have been considered, or what private procedures may have surrounded a response.
  • The proportionate safeguard is a privacy-preserving, versioned disclosure receipt that makes the request, authority, scope, acting representative, decision and handling safeguards reviewable without exposing the protected information itself.

The three names and the narrow aperture

On 9 June 2021, the AFRINIC Board reduced a potentially expansive subject to a short chain of authority. Resolution 202106.616 named Mr Christian ANGSEESING, Mr Didier ANGSEESING and Ms Nathalie DESCELLES-POCHÉ, all representatives of Executive Services Ltd. It said any one of them could provide, upon request by a competent authority, all basic information and beneficial-ownership information of the Company pursuant to section 190(6)(a) of the Companies Act 2001. The instrument also allowed execution in counterparts: each executed counterpart would count as an original, and the counterparts together would form one instrument.

Every element of that sentence matters. There were three named people, not an undefined class of employees or advisers. Any one could act, so the authorisation did not demand a joint decision by all three. The trigger was a request, not curiosity, convenience or a self-started inquiry. The requester had to be a competent authority, not simply any member of the public. The information belonged to two stated classes, both concerning AFRINIC as the Company. The legal hook was one cited provision, section 190(6)(a). Read together, these terms describe a narrow aperture in a corporate recordkeeping arrangement.

They do not describe an open publication policy. Nothing in the wording authorises the three representatives to place a corporate ownership dossier online, circulate it routinely, respond to any person who asks, or search through unrelated AFRINIC systems. Nor does the wording say that the Board itself was creating the public power behind the request. The resolution is best understood as an internal corporate designation for answering a request whose lawful force, if any, comes from the competent authority and applicable law.

That distinction makes the resolution more interesting than its brevity suggests. A company can require an identifiable human channel through which a lawful demand is received and answered. Without that channel, responsibility can become diffuse: one office assumes another has verified the requester, an employee cannot tell whether a mandate is current, or a response is delayed while everyone searches for authority to act. A Board resolution can solve that organisational problem. Yet the same resolution can be described too broadly if the trigger and the information class are detached from the sentence.

“Beneficial ownership” sounds capacious when quoted alone. In context, it is tied to the Company and to a request from a competent authority under the cited provision.

The strongest benign reading therefore deserves to be stated first. Executive Services Ltd, as a corporate-services provider, may need a clear Board mandate before one of its representatives answers a lawful request involving company records. Naming three individuals supplies redundancy. Allowing any one to act avoids a single-person bottleneck caused by travel, illness, departure or simple unavailability. Identifying a request trigger, two information classes and one legal hook is more disciplined than leaving the matter to informal discretion after an official letter arrives. A prepared route can be both faster and safer than improvisation.

That benign case is not weakened by insisting on boundaries. It is strengthened. A reliable disclosure channel should permit the right response to the right requester without encouraging a wider release. Speed has institutional value only when the institution can later show what was accelerated. Redundancy has value only when each authorised person is acting under the same current instrument. A concise mandate does its job when it enables action; supporting records do the rest by showing that each action remained faithful to the mandate.

What the public instrument proves

The official AFRINIC Board page establishes the existence and wording of Resolution 202106.616. It supports the date, identifier, three names, any-one-may-act structure, competent-authority trigger, two company-information classes, cited statutory hook and counterparts clause. That is substantial evidence of a corporate act. It is not evidence of a later event merely because the resolution created the capacity for one.

In particular, the published instrument does not identify a competent authority that invoked the channel. It names no request, investigation, file, recipient of information or completed disclosure. It does not say that any of the three named representatives ever acted under it. A standing authorisation is not proof of use, just as a designated signatory is not proof that a particular document was signed. Conflating capacity with exercise would turn a verified governance fact into an invented event.

The official Mauritius government endpoint for the Companies Act 2001 confirms the legal instrument cited by the Board. For this analysis, the relevant statutory reference stops at section 190(6)(a) and at the operative scope expressed in the resolution. The Board's wording does not support a tour of company law, a catalogue of official powers, or a claim to have reconstructed the provision's entire amendment history. Nor does it justify an opinion about how the provision would apply to a hypothetical request.

The point is institutional: the resolution attached its authorisation to a specified statutory hook rather than presenting the Board's discretion as self-sufficient.

The counterparts clause belongs in the same careful reading. It tells us how the Board document could be executed: separate executed copies would each be treated as originals and together as one instrument. It does not multiply the underlying authority, create three separate mandates, or expand the information classes. Its likely practical significance is documentary continuity, not substantive enlargement. A later reviewer would still need to know which version was operative, whether all relevant counterparts were assembled, and whether any later correction, revocation or successor instrument changed the list of authorised representatives.

The evidentiary posture is therefore asymmetric but clear. The public page gives strong support for what the Board authorised. It gives no support for asserting that the authorised sequence progressed to a request or a release. This is not a semantic caution inserted to make the account bloodless. It is the difference between explaining a control and alleging conduct. In governance reporting, that difference protects both accuracy and accountability: accuracy because it keeps claims within the evidence, and accountability because it identifies which additional records would be needed to understand an actual disclosure.

The missing middle is a question, not a verdict

Between a standing Board authorisation and a defensible disclosure lies a series of practical decisions. Who received the request? How was the requester authenticated? On what basis was it accepted as a competent authority? Which version of the Board instrument governed that day? What did the requester seek? Which requested fields were within the Company's basic information or beneficial-ownership information? Which were outside those classes? Was privilege, confidentiality or security implicated? Who approved, withheld or escalated each part? How was the response transmitted, retained and corrected?

Resolution 202106.616 does not publish answers to those questions. It does not state an identity-validation method, a field-by-field release test, a minimum-necessary rule, a privilege or security review, a decision log, a retention period, a notice rule, an aggregate reporting method, a correction path, or an expiry and revocation procedure. Those omissions define the limits of what can be learned from the public instrument alone.

They do not prove that no private process existed. A short Board resolution may sit above internal instructions, professional obligations, later decisions or case-specific correspondence that is not reproduced on the public Board page. The available record does not establish whether such material existed, how good it was, or whether it was ever used. It would be as unwarranted to declare the channel procedurally empty as it would be to assume that every safeguard was present and effective.

The correct conclusion is narrower: the public resolution leaves the operational middle unshown. That gap matters because the difference between a lawful, scoped response and an overbroad release is usually expressed in those middle steps. A title and statutory citation do not authenticate a requester. The phrase “beneficial ownership information” does not, on its own, enumerate fields. Naming an authorised person does not record what that person released or withheld. If public understanding is to remain precise, the supporting record should make these transitions testable without disclosing the sensitive contents.

A channel, not an event

The resolution can be pictured as a sequence of gates. First, the Board passes and preserves an identifiable corporate authorisation. Second, the instrument designates three individuals. Third, any one of those three may act. Fourth, a request arrives from an entity whose status as a competent authority must be established. Fifth, the requested material is mapped against the two authorised company-information classes. Sixth, only a bounded response is prepared after relevant legal, confidentiality, privilege and security questions are considered. Seventh, a record preserves the decision and its handling.

Only the first three gates are directly visible in the published instrument, together with the stated conditions governing later ones. The resolution does not establish that the fourth gate was ever reached. It consequently cannot prove that anyone passed through the fifth, sixth or seventh. Keeping those states separate prevents the commonplace error of treating an enabling instrument as a historical account of an enabled act.

It also shows why the identity of the actor is less important than the integrity of the chain. Any one of three people may act, but the same request and scope tests should govern all three. Redundancy should not create three standards. A versioned instrument, consistent intake record and common decision format would allow a successor to reconstruct the result even if the individual representative were no longer available. The Board's choice of named people creates personal traceability; the supporting system must turn that traceability into institutional continuity.

This is the resolution's real governance problem. It is neither a scandal waiting to be inferred nor a trivial piece of stationery. It is a bounded delegation whose quality depends on whether the boundaries remain visible at the moment of use. The public text gives a clear outer frame. A proportionate record can make the inner sequence legible while preserving confidentiality. That is how corporate transparency and privacy can reinforce each other rather than compete.