ICANN ICANN Email List Archives

[alac-bylaw-comments]


<<< Chronological Index >>>    <<< Thread Index >>>

ALS - compliance monitoring

  • To: alac-bylaw-comments@xxxxxxxxx
  • Subject: ALS - compliance monitoring
  • From: Adam Peake <ajp@xxxxxxxxxxxx>
  • Date: Thu, 8 Nov 2007 17:55:48 +0900

There are clear and simple criteria for becoming an at large structure <http://alac.icann.org/correspondence/structures-app.htm> (see, Minimum criteria for an At-Large Structure, 1-5), they mainly concern ensuring mechanisms are in place for the ALS to have the potential to represent the interests of users in the ICANN through the RALO and ALAC structure. If ALS actually meet the criteria, and remained in compliance with the criteria, then the criteria seem adequate.

Acknowledgement as an ALS brings benefits, there should also be responsibilities and simple among those should be are the criteria of becoming and ALS being maintained (does the ALS distribute information, does it have a means of taking input from users in policy development, discussions and decisions, etc.) ICANN has mechanisms for compliance monitoring, these should be used to check for compliance with these simple criteria, perhaps on an annual basis. Non-compliance should result in decertification or suspension as an ALS.

Asking ALAC members, most are selected by ALS (currently 10 via the RALOs, 5 via NomCom), to be responsible for decertification does not seem appropriate. An independent and rules based mechanism would be preferable.

Thanks,

Adam Peake
GLOCOM Tokyo


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy