<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
if this is the case, the conflict is clear and Mr Silber must
resign from the ICANN's new gTLD Program Committee. <br>
Is there an ICANN rule to avoid this kind of situation?<br>
Regards<br>
<br>
Le 13/10/2012 16:53, Lerato a écrit :<br>
</div>
<blockquote
cite="mid:1350143638.25525.YahooMailNeo@web184901.mail.gq1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff; font-family:tahoma,
new york, times, serif;font-size:10pt">
<div><br>
</div>
<div style="color: rgb(0, 0, 0); font-size:
13.600000381469727px; font-family: tahoma, 'new york', times,
serif; background-color: transparent; font-style: normal; ">You
do not seem to understand what you are talking about. The fact
that ZADNA has endorsed UniForum's new gTLD application, and
Mike Silber, an ICANN Board Member from South Africa who is
also a serving director of South Africa's Domain Names
Authority - the ZADNA; and also a member of the new gTLD
Program Committee of ICANN is a clear Conflict of Interest
situation for him since he would be expected to participate in
the decision-making over a new gTLD that the ZADNA has
endorsed, and by implication, which he has also endorsed by
the mere fact that he is a ZADNA director.</div>
<div style="color: rgb(0, 0, 0); font-size:
13.600000381469727px; font-family: tahoma, 'new york', times,
serif; background-color: transparent; font-style: normal; "><br>
</div>
<div style="color: rgb(0, 0, 0); font-size:
13.600000381469727px; font-family: tahoma, 'new york', times,
serif; background-color: transparent; font-style: normal; ">--Lerato
Ma</div>
<div>
<blockquote style="border-left: 2px solid rgb(16, 16, 255);
margin-left: 5px; margin-top: 5px; padding-left: 5px;">
<div style="font-family: tahoma, 'new york', times, serif;
font-size: 10pt; ">
<div style="font-family: 'times new roman', 'new york',
times, serif; font-size: 12pt; ">
<div dir="ltr"> <font face="Arial" size="2">
<hr size="1"> <b><span style="font-weight:bold;">From:</span></b>
<a class="moz-txt-link-rfc2396E" href="mailto:ngabo@pop.co.za">"ngabo@pop.co.za"</a> <a class="moz-txt-link-rfc2396E" href="mailto:ngabo@pop.co.za"><ngabo@pop.co.za></a><br>
<b><span style="font-weight: bold;">To:</span></b>
<a class="moz-txt-link-abbreviated" href="mailto:africann@afrinic.net">africann@afrinic.net</a> <br>
<b><span style="font-weight: bold;">Sent:</span></b>
Saturday, October 13, 2012 2:19 AM<br>
<b><span style="font-weight: bold;">Subject:</span></b>
Re: [AfrICANN-discuss] It’s like that in life, there
are always bad players and bad losers!<br>
</font> </div>
<br>
On Fri, 2012-10-12 at 18:19 -0700, Lerato wrote:<br>
<br>
"I'm sure the ICANN Board will check the allegations...<br>
> If the ICANN Board checks the
allegations and accepts that they are true why should
you favour UniForum? Irrespective of the fact that you
think that the letters are so cloak and dagger, and
desperate, why should you condone the fact that ICANN
Board members that have conflicting interests are going
to sit down in the new gTLD Program Committee to preside
over new gTLD decision-making?<br>
> <br>
You assume that the conflict allegations are actual
truth.<br>
<br>
Someone told me that the Internet never forgets, now
there appears to be a lot of truth in that.<br>
<br>
Mr. Mike Silber, "former director of UniForum SA" - I
have been unable to find any evidence to support this
claim.<br>
In my research, it looks to me that ZADNA and UniForum
are completely separate organisations.<br>
It seems ZADNA is a creation of the South African
government via their Electronic Communications and
Transactions Act of 2002. "In 18 May 2007, the Minister
of Communications published a public notice officially
giving .za DNA the full assumption of management of .za
in terms of section 59 of the ECT Act)."<br>
Uniforum seems to have been around much longer. I found
"UniForum SA (originally /usr/group/) in 1988. During
1995 UniForum SA were delegated the responsibility of
administrating the co.za domain registry"<br>
<br>
ZADNA's mandate:<br>
"65.(1) The Authority must (a) administer and manage
the .za domain name space;"<br>
It seems ZADNA wants a Central Registry and that is why
Mr. Chris Disspain company was consulted... nothing to
do with the new gTLD process.<br>
<br>
Since then, two things appear to be happening at
Uniforum, they have applied for the "africa" gTLD and
perhaps due to their size, are becoming the "South
Africa Central Registry (ZACR)". There is no suggestion
that one event is dependant on the other. It also looks
like the gTLD "africa" race started before the ZACR
change.<br>
<br>
ZADNA (the government rule maker) seems to be on the
outside of this ZACR (the actor) change - which make
governance sense.<br>
<br>
This didn't take long to research.<br>
<br>
---------------------<br>
<br>
When I see two parties running for the same goal and one
party starts throwing mud at the other - I tend to
support the other. Go read the subject line...<br>
<br>
----------------------------------------------------------------<br>
This message was sent using IMP, the Internet Messaging
Program.<br>
<br>
_______________________________________________<br>
AfrICANN mailing list<br>
<a moz-do-not-send="true"
ymailto="mailto:AfrICANN@afrinic.net"
href="mailto:AfrICANN@afrinic.net">AfrICANN@afrinic.net</a><br>
<a moz-do-not-send="true"
href="https://lists.afrinic.net/mailman/listinfo.cgi/africann"
target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/africann</a><br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AfrICANN mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AfrICANN@afrinic.net">AfrICANN@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo.cgi/africann">https://lists.afrinic.net/mailman/listinfo.cgi/africann</a>
</pre>
</blockquote>
<br>
</body>
</html>