Changes

===2007 Announcement of Compliance Audit Processes===

===2007 Announcement of Compliance Audit Processes===

ICANN's earliest post report of registrar compliance dates from October 2006.<ref name="06update">[https://www.icann.org/resources/newsletter/registrar-update-2006-10-01-en ICANN.org - Registrar Compliance Update], October 1, 2010</ref> That report indicated that ICANN intended to introduce audit processes for registrars, "similar to the registry audit program already in place."<ref name="06update" /> In March 2007, Contractual Compliance announced its intention to begin auditing the contractual and operational compliance of both registries and registrars.<ref>[https://www.icann.org/en/blogs/details/updated-contractual-compliance-program-24-3-2007-en ICANN.org Blog - Updated Contractual Compliance Program], March 24, 2007</ref> Three days earlier, ICANN's CEO at the time, [[Paul Twomey]], announced that review and revision of ICANN's Registrar Accreditation process was necessary to ensure consumer protection and enforcement goals.<ref>[https://www.icann.org/en/announcements/details/registrar-accreditation-policy-and-process-must-be-reviewed-21-3-2007-en ICANN.org - Registrar Accreditation Policy and Process must be reviewed], March 21, 2007</ref> The announcement was prompted in part by the termination of [[RegisterFly]] due to a large volume of customer complaints. Some commentators criticized ICANN at the time for failing to act sooner.<ref>[https://domainnamewire.com/2007/03/27/icann-lets-learn-from-registerfly/ Domain Name Wire - ICANN: Let's Learn from RegisterFly], March 27, 2007</ref> ICANN executives at the time identified the lack of enforcement mechanisms apart for revocation of accreditation hampered ICANN's capacity to respond.<ref>[https://www.cbc.ca/news/science/icann-to-review-domain-name-regulations-1.671879 CBC News - ICANN to Review Domain Name Regulations], March 27, 2007</ref>

ICANN's earliest posted report of registrar compliance dates from October 2006.<ref name="06update">[https://www.icann.org/resources/newsletter/registrar-update-2006-10-01-en ICANN.org - Registrar Compliance Update], October 1, 2010</ref> That report indicated that ICANN intended to introduce audit processes for registrars, "similar to the registry audit program already in place."<ref name="06update" /> In March 2007, Contractual Compliance announced its intention to begin auditing the contractual and operational compliance of both registries and registrars.<ref>[https://www.icann.org/en/blogs/details/updated-contractual-compliance-program-24-3-2007-en ICANN.org Blog - Updated Contractual Compliance Program], March 24, 2007</ref> Three days earlier, ICANN's CEO at the time, [[Paul Twomey]], announced that review and revision of ICANN's Registrar Accreditation process was necessary to ensure consumer protection and enforcement goals.<ref>[https://www.icann.org/en/announcements/details/registrar-accreditation-policy-and-process-must-be-reviewed-21-3-2007-en ICANN.org - Registrar Accreditation Policy and Process must be reviewed], March 21, 2007</ref> The announcement was prompted in part by the termination of [[RegisterFly]] due to a large volume of customer complaints. Some commentators criticized ICANN at the time for failing to act sooner.<ref>[https://domainnamewire.com/2007/03/27/icann-lets-learn-from-registerfly/ Domain Name Wire - ICANN: Let's Learn from RegisterFly], March 27, 2007</ref> ICANN executives at the time identified the lack of enforcement mechanisms apart for revocation of accreditation hampered ICANN's capacity to respond.<ref>[https://www.cbc.ca/news/science/icann-to-review-domain-name-regulations-1.671879 CBC News - ICANN to Review Domain Name Regulations], March 27, 2007</ref>

At the time of the announcement, there were no contractual provisions for such audits, except to the extent that individual registry agreements might grant a right to audit technical records of registry operators. However, review of the RAA was discussed at [[ICANN 28]] in Lisbon at the end of March.<ref>[https://www.icann.org/resources/board-material/resolutions-2007-03-30-en#_Toc36876525 ICANN Board Meeting Minutes], June 30, 2007</ref> In June 2007, the ICANN Board initiated its Consultation on Registrar Accreditation Agreements.<ref>[https://www.icann.org/resources/board-material/resolutions-2007-06-29-en#k Resolutions 07.50-07.52 of the Board], June 29, 2007</ref> This process resulted in the 2009 amendments to the RAA.

At the time of the announcement, there were no contractual provisions for such audits, except to the extent that individual registry agreements might grant a right to audit technical records of registry operators. However, review of the RAA was discussed at [[ICANN 28]] in Lisbon at the end of March.<ref>[https://www.icann.org/resources/board-material/resolutions-2007-03-30-en#_Toc36876525 ICANN Board Meeting Minutes], June 30, 2007</ref> In June 2007, the ICANN Board initiated its Consultation on Registrar Accreditation Agreements.<ref>[https://www.icann.org/resources/board-material/resolutions-2007-06-29-en#k Resolutions 07.50-07.52 of the Board], June 29, 2007</ref> This process resulted in the 2009 amendments to the RAA.

|}

|}

In total, only 15 registrars passed the audit process without any notice of deficiency.<ref name="21audit" /> Of the remaining 111 registrars, 92 cured all reported deficiencies before the end of the audit's remediation phase. 19 registrars were unable to cure all deficiencies within the audit timeframe, and negotiated due dates with Contractual Compliance for completion of their work to cure.<ref name="21audit" />

In total, only 15 registrars passed the audit process without any notice of deficiency.<ref name="21audit" /> Of the remaining 111 registrars, 92 cured all reported deficiencies before the end of the audit's remediation phase. Nineteen registrars were unable to cure all deficiencies within the audit timeframe and negotiated due dates with Contractual Compliance for completion of their work to cure.<ref name="21audit" />

 

==Outreach==

==Outreach==

Contractual Compliance presents frequently at [[ICANN Meetings|ICANN meetings]], and conducts seminars and other educational programs throughout the ICANN regions.<ref>[https://www.icann.org/resources/compliance/outreach ICANN.org - Contractual Compliance Outreach Activities]</ref>  

Contractual Compliance presents frequently at [[ICANN Meetings|ICANN meetings]], and conducts seminars and other educational programs throughout the ICANN regions.<ref>[https://www.icann.org/resources/compliance/outreach ICANN.org - Contractual Compliance Outreach Activities]</ref>  

==Roles at ICANN==

==ICANN CC Staffers==

* Senior Manager, Contractual Compliance Risk and Audit

* [[Leticia Castillo Sojo]], [[Jonathan Denison]], [[Roger Lim]]: Directors, Contractual Compliance

* SVP, Contractual Compliance & U.S. Government Engagement

* [[Yan Agranonik]]: Senior Manager, Contractual Compliance Risk and Audit

* Contractual Compliance Risk and Audit Senior Specialist

* [[Jamie Hedlund]]: SVP, Contractual Compliance & Consumer Safeguards, Managing Director

* Contractual Compliance Lead

* [[Joseph Restuccia]]: Contractual Compliance Risk and Audit Senior Specialist

* Sr. Manager, Contractual Compliance

* [[Amanda Rose]]: Contractual Compliance Lead

* Contractual Compliance Analyst

* [[Zuhra Salijanova]]: Sr. Manager, Contractual Compliance

* Contractual Compliance Specialist

* [[Mehdi Kurdmisto]], [[Genie Chou]], [[Mariana Solano]], [[Dickson Chew]], [[HuiYing Lim]], [[Leah Symekher]], [[Laine Tan]], [[Amanda Weddle]]: Contractual Compliance Analysts

* Contractual Compliance Senior Specialist

* [[Nicholas Axelrod-McLeod]], [[Charmaine Lim]], [[Bryan Tan]]: Contractual Compliance Specialists

* [[May Kim]], [[Holida Yanik]], [[Selim Manzak]], [[Jinzaemon Kimoto]]: Contractual Compliance Senior Specialists

==References==

==References==

{{reflist}}

{{reflist}}

 

[[Category:ICANN Organization]]

[[Category:ICANN Organization]]