[ALAC] Improving Contractual Compliance

[Rinalia Abdul Rahim]

Dear ALAC and Regional Leaders,

FYI below. At-Large views would be extremely valuable for continuous
improvement of ICANN compliance.

Best regards,

Rinalia

Jamie Hedlund's bog that was just posted on improving contractual
compliance:



 https://www.icann.org/news/blog/improving-contractual-compliance



*Improving Contractual Compliance*



About ten days ago, members of the Registry Stakeholder Group (RySG) and
the Intellectual Property Constituency (IPC) submitted a document entitled,
“Joint Recommendations for ICANN Compliance
<https://www.icann.org/en/system/files/correspondence/rysg-ipc-to-compliance-28mar17-en.pdf>.”
A few months into my new role leading Contractual Compliance and Consumer
Safeguards, I appreciated the constructive input from these two
constituencies.



At a session
<https://community.icann.org/pages/viewpage.action?pageId=63144494&preview=/63144494/64069639/transcript_ncphlunch_140217.pdf>
at
the Non-Contracted Parties House Intercessional 2017
<https://community.icann.org/pages/viewpage.action?pageId=63144494> in
Reykjavik, in sessions at the ICANN58 Community Forum with the At-Large
Community
<https://schd.ws/hosted_files/icann58copenhagen2017/9f/I58CPH_Sun12Mar2017-ALAC%20and%20Regional%20Leaders%20Working%20Session%20Part%208-en.pdf>
, the Registry Stakeholder Group
<https://schd.ws/hosted_files/icann58copenhagen2017/03/Transcript%20RySG_Part%20I_14%20March%202017_Transcript%5B1%5D.pdf>
, the Registrar Stakeholder Group
<https://schd.ws/hosted_files/icann58copenhagen2017/2c/Transcript%20RrSG%20meeting%20I%2014%20March%20.pdf>
, the Security and Stability Advisory Committee
<https://schedule.icann.org/event/9nnX/ssac-private-meeting-c>, the
Business Constituency
<https://schd.ws/hosted_files/icann58copenhagen2017/6c/Transcript%20BC%2014%20March%20Copenhagen%5B1%5D.pdf>
, the Intellectual Property Committee
<https://schd.ws/hosted_files/icann58copenhagen2017/90/2017_03March_14%20IPC%20Open%20Meeting%20Transcription.pdf>,
and the Governmental Advisory Committee
<https://participate.icann.org/p3rrfzfm4p9/?launcher=false&fcsContent=true&pbMode=normal>
in
Copenhagen, and during formal and informal calls with community members,
there were lively discussions regarding the need for improvements in
Contractual Compliance.



To help us succeed in making desired changes, I asked for examples of where
we could do better, as well as specific and concrete recommendations that
we could implement. I was specifically asking for more than general
statements such as “ICANN isn’t transparent” or “ICANN is bad at
compliance”. The RySG-IPC Joint submission, which I understand was underway
before these recent discussions, includes recommendations that are clear
and specific and can be assessed for feasibility, cost and effort. And
that’s just what we in Contractual Compliance will do.



There is another effort underway that also recommends improvements to
Contractual Compliance. In the “Competition, Consumer Trust and Consumer
Choice Review Team Draft Report of Recommendations for New gTLDs
<https://www.icann.org/public-comments/cct-rt-draft-report-2017-03-07-en>,”
the Review Team seeks input on recommendations related to Contractual
Compliance. In particular, Recommendation 23 urges ICANN to “Include more
detailed information on the subject matter of complaints in ICANN publicly
available compliance reports.”  The draft recommendations are now out for
public comment. This is an excellent opportunity for community members to
provide input just as RySG and IPC representatives have done. (Full
disclosure – I am a member of the CCT-RT).



If you have examples of where Contractual Compliance could improve,
especially on its commitment to transparency, and specific and concrete
recommendations on how to improve ICANN’s Contractual Compliance function,
please consider submitting them to the CCT-RT Public Comment forum.
Alternatively, please submit them by email to me at jamie.hedlund at
icann.org <jamie.hedlund at icann.org>. Once the public comment period on
the CCT-RT’s closes, we will review all of the input we receive and provide
a report on changes that we will undertake as well as a rationale for not
undertaking others. Please send us your good ideas!

 END
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20170411/1f1a3d9f/attachment.html>