[council] FW: CCWG-Accountability Independent Review Process Implementation Oversight Team (IRP IOT)

James M. Bladel jbladel at godaddy.com
Thu Mar 2 02:43:07 UTC 2017

Councilors –

See announcement below, regarding the formation of an IRP Implementation Oversight Team as part of the new bylaws associated with the IANA transition.

There’s quite a bit of info here, but at a summary level the GNSO will soon be asked to name (a) panelist(s) to a group that will oversee the implementation of the new IRP.  I recommend that we assign this task to the SSC, once that group is chartered.

Thank you,


From: Bernard Turcotte <turcotte.bernard at gmail.com>
Date: Tuesday, February 28, 2017 at 15:39
Subject: CCWG-Accountability Independent Review Process Implementation Oversight Team (IRP IOT)

Dear Supporting Organizations and Advisory Committees to ICANN:

We write to you in our capacity as members of the CCWG-Accountability Independent Review Process Implementation Oversight Team (IRP IOT<https://community.icann.org/pages/viewpage.action?pageId=59643726>).
As you know, as part of the IANA transition ICANN reconstituted the IRP in the recently enacted Bylaw Article 4, Section 4.3. As the IRP IOT works to develop recommendations to the CCWG-Accountability on implementing the newly constituted IRP, we note that there are a number of provisions within Section 4.3 that anticipate input/activity from SOs and ACs along the way.

This correspondence is intended:

(1)   to bring these matters to your attention; and

(2)   to mention an additional right you have (in conjunction with others) if you are a direct customer of the IANA naming functions.
This correspondence is not about the public comment period (recently closed) regarding the Updated Supplementary Procedures for IRP, which is being managed separately.

As for the first matter, please note that Section 4.3(j)(ii) requires that ICANN in consultation with the SOs and ACs initiate a four-step process to establish a standing panel of not less than seven IRP panelists.  Section 4.3(j)(ii) anticipates the following actions:

A.     ICANN in consultation with the SOs and ACs shall initiate a tender process for an organization to provide admin support to the IRP, beginning by consulting with the IRP IOT on a draft tender document. [The current admin support organization for ICANN IRP’s is the International Centre for Dispute Resolution<https://www.icdr.org/icdr/faces/home?_afrLoop=366877148548956&_afrWindowMode=0&_afrWindowId=157511b7oa_93#%40%3F_afrWindowId%3D157511b7oa_93%26_afrLoop%3D366877148548956%26_afrWindowMode%3D0%26_adf.ctrl-state%3D157511b7oa_125>.]

 B.     ICANN shall issue a call for expressions of interest from potential panelists and work with the SOs and ACs and the Board to identify and solicit well-qualified applications, and to conduct an initial review/vetting of applications.

C.      The SOs and ACs shall nominate a slate of proposed panel members identified in such process.

 D.     Final selection is subject to Board confirmation.

 The qualifications for IRP panelists are set forth in Section 4.3(j).
We expect that in the first part of 2017 you will be called on by ICANN to participate in these endeavors. The sooner these steps are taken, the sooner the newly constituted IRP will be able to function in complete accordance with the new bylaws. We stand ready to help as appropriate.

As for the second matter, to the extent your group (in whole or in part) is a direct customer of the IANA naming function, please note that Section 4.3(n)(ii) is of particular interest to “direct customers” of the IANA naming functions, stating in part:

Specialized Rules of Procedure may be designed for reviews of PTI service complaints that are asserted by direct customers of the IANA naming functions and are not resolved through mediation. The Rules of Procedure shall be published and subject to a period of public comment that complies with the designated practice for public comment periods within ICANN, and take effect upon approval by the Board, such approval not to be unreasonably withheld.

Direct customers of the IANA naming functions should have an opportunity to inform us of your views on the matter.
We urge you to review the provisions of Section 4.3(n) generally on IRP rules of procedure and let the IRP IOT know of any requests along these lines.

Sincerely yours,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20170302/1a981265/attachment.html>

More information about the council mailing list