ALAC discussed what it could and would do on this and any other similar compliance matters at our last meeting (and please note the Board Liaison was part of this discussion so our direct mandated method of communication of our concerns to the Board is involved) and we are proceeding in the agreed direction (I'm sure Danny you will have listened to the recording and/or read the minutes and action items arising to confirm what action we are taking... The Action item specific to this is still pending but is being done by Alan at the moment so I'm sure he will brief you further as soon as possible... Further to these actions however it should also be noted that the matter of Registrar Compliance is being focused on as part of our Mexico meeting and in fact each RALO General Assembly will have the following item listed at staggered times to allow for the presence of appropriate ICANN staff in each of the GA's that run concurrently on the Tue ... Other ICANN Matters: a. Registrar/registry RAA non-compliance (with ICANN services) b. Outreach under new GNSO structure So Danny, thank you for the link I found it very interesting as we always need anecdotal evidence and specific cases to quite in our work, plus further information and compliance issues do need to be continually looked for and reported; and you seem well equiped to do that... but *please desist* from making claims and statements intended to show off your lack of trust, faith or belief in ICANN generally and the ALAC / At-Large structure we are working with specificalyy, that is based on incorrect, inaccurate or misleading statements; such as trying to indicate below that we are either ignoring this important issue or are doing nothing... That is FAR from the truth... CLO Cheryl Langdon-Orr ALAC Chair 2009/1/30 Danny Younger <dannyyounger@yahoo.com>
http://www.oxadox.com/article/healthfood/2009-01-29/51115.html
The issue of GoDaddy's ongoing violation of Inter-Registrar Transfer Consensus Policy has been brought to the attention of the ICANN Compliance Department -- but what action has been taken?
ICANN Senior Management is aware of the issue -- but what action has been taken?
The ALAC has been notified of the issue -- but what action have they taken?
Question: What's the point in working hard to come up with appropriate consensus-based policies if ICANN routinely turns a blind eye to policy violations? ... and what's the point in working with the ALAC if they fail to bring these oft-repeated user concerns to the attention of the Board?
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org
http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ica...
Visit the NARALO online at http://www.naralo.org ------
-- Cheryl Langdon-Orr (CLO)