NavigationSearchUser loginRecent blog posts
|
President's Strategy Committee meeting2007-03-19 13:00 2007-03-19 16:00 Etc/GMT
The third meeting of the President's Strategy Committee will take place online on Monday 19 March for three hours between 1pm and 4pm UTC (6-9am PST). The session will be held online, split into panels, and followed at the end by an half-hour moderated session where questions posted to this site will be raised. The Committee itself is charged with "making observations and recommendations concerning strategic issues facing ICANN" and to this end held a similar online "town hall" meeting on 20 July 2006. The results from that meeting were compiled into a draft report [pdf] on 29 November 2006, and then discussed at an open session at the ICANN Sao Paulo meeting on 4 December 2006. Feedback by those sessions will be carried over to this third meeting of the Committee. The hope is that the session will outline any possible additions needed plus highlight any new and emerging themes. In particular:
This session will then feed into a final report to be presented to the Board and ICANN community on Wednesday 28 March at the ICANN Lisbon meeting. The consultation will be carried out over a conference call due to the geographical diversity of the panellists.
We have also set up a chatroom, and a forum for the committee meeting (see above) in order to provide people with as many ways as interacting as possible.
Agenda
RegisterFlyDanny Thanks for this. The Committee will not be speaking to the RegisterFly issue this afternoon. But there will be a workshop on this particular issue at the ICANN Lisbon meeting. Further, I will be making a statement prior to the meeting outlining areas which need consideration by the ICANN meeting. Thank you for your input here - indeed some of your list overlap with my own. May I suggest that you make further response concerning the Registrar issues after my statement comes out during the week. Paul Twomey Registrar Accreditation AgreementPaul, Thanks for the feedback. I'm aware that discussions started on revisions to the RAA about two years ago; could you perhaps provide us with an update regarding the current progress of those discussions? Place your questions hereThis is where you can ask questions of the Strategy Committee at the end half-hour session |
Recent comments
ICANN newsNet coverage |
Contract Enforcement
In its Draft Committee Report the PSC referenced
Responsibility #10 cited in the Joint Project
Agreement that in part called for "devoting
adequate resources to contract enforcement".
Unfortunately, the PSC did not choose to treat the
issue of contract compliance as a strategic
initiative.
While this clear failure to put registrant security
and stability concerns at the top of a strategic
priority list may have been occasioned by the top-down
nature of the Committee itself, it cannot be said that
the Committee was unaware of these concerns as the PSC
was in receipt of written comments on compliance
issues from both the INTA and Network Solutions:
INTA: "The safety and reliability of the DNS is
threatened when ICANN does not enforce the contracts
on which its business is based."
Network Solutions: "Take a proactive role in
compliance efforts to limit abuses, particularly in
light of the budgetary resources allocated in this
area and ICANN's claim that with a larger budget it
could address these abuses."
By now, the PSC should have become aware of the
registerfly.com debacle and the need to deal with
these matters on a more proactive basis.
I ask the Committee to advise the President to:
(1) examine the potential need for contractual
arrangements that impose reasonable requirements on
the domain reseller community
(2) implement a schedule, terms, and format for the
registrant data escrow arrangement
(3) hire additional compliance staff
(4) consider increasing the frequency of compliance
reviews (currently invoked only during the
accreditation renewal process)
(5) publicly post a RAA Violations Form that
enumerates all registrar contractual obligations and
allows the public to notify ICANN of any RAA-specific
violations
(6) formulate a gTLD Registrar Code of Conduct (see
RAA 3.7.1 -- perhaps using the Eurid model as a guide)
(7) inform the public whenever any registrar fails to
make a scheduled payment to ICANN
(8) inform the public whenever any registrar is not in
a status of full RAA compliance