Hi Noah

Without getting into the content of your mail and without endorsing the 
specific language chosen by Owen: The RIRs are independent and ICANN does not 
in any way direct or control the RIRs.

The RIRs chose to operate within the ICANN framework, however can move the NRO 
/ ASO out of ICANN at any time (including moving the contract out of PTI as 
well).

So I would not characterise ICANN as “puppet” of the NRO - but rather a 
framework within which an independent NRO choses to operate. That may be a 
distinction without a difference - so I am not offended by Owen’s choice of 
words.

Mike

> On 2 Aug 2021, at 10:23, Noah <n...@neo.co.tz> wrote:
> 
> Owen,
> 
> I have some questions for you...
> 
> On Sun, 1 Aug 2021, 20:43 Owen DeLong via Community-Discuss, 
> <community-discuss@afrinic.net <mailto:community-discuss@afrinic.net>> wrote:
> 
> While people often mistake ICANN for some form of authority, the reality is 
> that for number
> resources, ICANN is a puppet at the end of the strings pulled by the NRO 
> (which acts in the
> role of ICANN ASO).
> 
> Your association with LARUS has really got you off the rails.
> 
> No wonder Larus has created the so called purported organization called the 
> *Number Resource Alliance* aka NRA  whose website is  https://www.nra.help/ 
> <https://www.nra.help/>
> 
> Since you claim that ICANN is a puppet of the NRO, and not an authority, is 
> that why your LARUS which is linked to Cloud Innovation Ltd created this so 
> called *NRA* organisation.
> 
> Are IPv4 brokers now forming their own system?  Against ICANN and the NRO? 
> 
> I ask because your sentiments that ICANN is a puppet are really wanting.
> 
> Cheers,
> Noah
> 
>  
> _______________________________________________
> Community-Discuss mailing list
> Community-Discuss@afrinic.net
> https://lists.afrinic.net/mailman/listinfo/community-discuss

_______________________________________________
Community-Discuss mailing list
Community-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/community-discuss

Reply via email to