My Spanish is a little rusty, but I got the gist, this is really serious. -------------------------------------------------- From: "Eduardo Diaz" <eduardodiazrivera@gmail.com> Sent: Friday, July 15, 2011 4:44 PM To: "Beau Brendler" <beaubrendler@earthlink.net> Cc: <na-discuss@atlarge-lists.icann.org> Subject: Re: [NA-Discuss] interesting story
The .pr ccTLD situation has more ramifications.
As the article says the University of Puerto Rico is suing the current operator for taking public money (aprox. $2 million) and University equipment out of its facilities. I am attaching the original sue document.
The document tells the story of the things that the operator did to move money around the University system in preparation to move it out. It also mentions how he fooled IANA in authorizing the re-delegation outside the University.
Good read! (The document is in Spanish and I do not know if there are any translators for pdf type documents).
-ed
On Fri, Jul 15, 2011 at 4:22 PM, Beau Brendler <beaubrendler@earthlink.net>wrote:
...passed on by Eduardo, regards shenanigans at Puerto Rico's ccTLD:
http://www.vocero.com/puerto-rico-es/se-llevan-dominio-www-gobierno-pr-sin-a...
-----Original Message-----
From: Beau Brendler <beaubrendler@earthlink.net> Sent: Jul 15, 2011 4:13 PM To: "na-discuss@atlarge-lists.icann.org" < na-discuss@atlarge-lists.icann.org> Subject: [NA-Discuss] agenda item for Monday's call
Danny Younger will not be able to join Monday's call. He asked that we consider the following (quoting from his e-mail with a couple of edits). I will put this item on Monday's agenda.
Beau ----------------------------------- "The [draft applicant] Guidebook (section 3.3.2] calls upon the ALAC to develop a new gTLD objection vetting process. Kurt Pritz, in his comments to Congress, has stipulated that he expects this to be a "robust" process established on behalf of the public interest. My concern is that ... It took eleven and a half months just to set up the process to select an at-large director ... and there was a fair amount of confusion within some of the regions as to process considerations. Making matters worse is that we now have only around nine months within which to have the project completed.
The Guidebook states: At a minimum, the process for objecting to a gTLD application will require: bottom-up development of potential objections, discussion and approval of objections at the Regional At-Large Organization (RALO) level, and a process for consideration and approval of the objection by the At-Large Advisory Committee.
... The NARALO has always taken the lead on major initiatives. Perhaps this is the time to once more take the lead to defend the public interest."
-----Original Message-----
From: Marilyn Vernon <staff@atlarge.icann.org> Sent: Jul 13, 2011 9:44 PM To: "na-discuss@atlarge-lists.icann.org" < na-discuss@atlarge-lists.icann.org> Cc: ICANN At-Large Staff <staff@atlarge.icann.org> Subject: [NA-Discuss] REMINDER: NARALO TELECONFERENCE - Monday, 18 July 19:00 UTC
Dear All,
The next NARALO teleconference is scheduled for Monday, 18 July 2011 at 19:00 UTC.
The agenda (to be updated) and call details can be found at: https://community.icann.org/x/HIAUAQ
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org<mailto:staff@atlarge.icann.org>.
-- Regards,
Heidi Ullrich, Gisella Gruber-White, Seth Greene, Marilyn Vernon, Matt Ashtiani ICANN At-Large Staff
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
-- NOTICE: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If you have received this communication by error, please notify us immediately by e-mail, and delete the original message.