Currently: 1. The aggrieved registry operator may or may not have a cause of action for IRP or litigation, depends a lot on the circumstances 2. No direct resolution path that I am aware of for ccTLDs. With gTLDs, it depends on circumstances but contractual arbitration provision could kick in 3. SLEs in IANA Functions Contract are between ICANN and NTIA, not sure what recourse any affected registry operator would have. J. Beckwith Burr Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer 1775 Pennsylvania Avenue NW, Washington D.C. 20006 Office: +1.202.533.2932 Mobile: +1.202.352.6367 / neustar.biz<http://www.neustar.biz> From: Seun Ojedeji <seun.ojedeji@gmail.com<mailto:seun.ojedeji@gmail.com>> Date: Monday, January 25, 2016 at 9:19 AM To: Chuck Gomes <cgomes@verisign.com<mailto:cgomes@verisign.com>> Cc: "cwg-stewardship@icann.org<mailto:cwg-stewardship@icann.org>" <cwg-stewardship@icann.org<mailto:cwg-stewardship@icann.org>> Subject: Re: [CWG-Stewardship] CCWG-ACCT Request for Guidance on PTI - IRP - Please respond by 23h59 UTC Monday 25 January 2016 Thanks for the examples Chuck. If I may ask, considering that the examples you stated may have happened under the current arrangement, do you or any other person knows how such is resolved presently? secondly, is NTIA involved in any of the resolution process? Regards On Mon, Jan 25, 2016 at 2:49 PM, Gomes, Chuck <cgomes@verisign.com<mailto:cgomes@verisign.com>> wrote: Let me give a few examples where I think that the IRP would be applicable: 1. A gTLD is not delegated as requested by a registry operator without appropriate justification. 2. Modification to a zone file record for a gTLD is not made without proper justification. 3. SLEs are not met after applicable procedures are followed. I think that we have recommended processes that would hopefully solve problems like the above well before an IRP would be needed, but it those processes do not work in a timely manner, then an IRP would provide an objective and well-defined option for an appeal. I think the affected registry operator, the RySG or the GNSO should all have standing to use the IRP in cases like the above if needed. The RySG in its comments over the history of the CWG Stewardship has repeatedly emphasized the need for registry operators to be able to appeal IANA decisions that they believe are contrary to policy. I suspect that others could come up with other examples. Chuck From:cwg-stewardship-bounces@icann.org<mailto:cwg-stewardship-bounces@icann.org> [mailto:cwg-stewardship-bounces@icann.org<mailto:cwg-stewardship-bounces@icann.org>] On Behalf Of Matthew Shears Sent: Monday, January 25, 2016 8:14 AM To: jrobinson@afilias.info<mailto:jrobinson@afilias.info>; cwg-stewardship@icann.org<mailto:cwg-stewardship@icann.org> Subject: Re: [CWG-Stewardship] CCWG-ACCT Request for Guidance on PTI - IRP - Please respond by 23h59 UTC Monday 25 January 2016 Would it be useful to try and list the possible situations where recourse to an appeals mechanism would be used? This might give us a better sense of what type of mechanism would be suited and whether or not the IRP would be appropriate/adequate? Matthew On 22/01/2016 12:33, Jonathan Robinson wrote: All, We have received a direct request (see below) from the CCWG Accountability Co-Chairs for further guidance with respect to the application of the IRP to the actions (or inactions) of PTI. Moreover, we have had input from Sidley via the Client Committee as follows: “Sidley spoke with Becky Burr from CCWG today regarding the CWG dependency for an IRP process. Based on the call, it appears that the open question for CWG is whether the CWG dependency is adequately met with an ICANN bylaw provision that allows for an IRP if ICANN fails to enforce the contract with PTI (for example, due to a material performance breach by PTI that is not cured) – or whether in addition to such an ICANN bylaw, a separate process is also required that would give direct customers a right to mediation or arbitration to address SLAs or other service issues. If the latter is required, then in order for CCWG to create such a process, it would need input from CWG on what the standard of review should be for those types of proceedings and what the type of process would be – for example, would non-binding mediation be sufficient to address a direct customer issue or would binding arbitration be required? By clarifying this point, CCWG will be better positioned to ensure that the CWG dependency is being met in the CCWG proposal.” So the essential question is: A. Is an ICANN bylaw provision that allows for an IRP if ICANN fails to enforce the contract with PTI (for example, due to a material performance breach by PTI that is not cured) sufficient? OR B. In addition to such an ICANN bylaw, is a separate process also required that would give direct customers a right to mediation or arbitration to address SLAs or other service issues? If B above, what type of process is necessary? As discussed in our CWG meeting yesterday, it will be particularly helpful if when responding to the above, you provide a rationale for your response. In addition, if possible, please make reference to (and be consistent with) the prior work of this CWG Stewardship (such as our proposal in response to the RFP from the ICG). Given that the request from the CCWG Co-Chairs indicates their need to close this item by 28 January, we need to discuss this soon. Accordingly, we request that you provide input ASAP and, in any event, by 23h59 UTC Monday 25 January 2016. Thank-you, Jonathan & Lise Co-chairs, CWG Stewardship From: Alice Jansen [mailto:alice.jansen@icann.org] Sent: 21 January 2016 17:05 To: Lise Fuhr <Fuhr@etno.eu><mailto:Fuhr@etno.eu>; Jonathan Robinson <jrobinson@afilias.info><mailto:jrobinson@afilias.info> Cc: Mathieu Weill <mathieu.weill@afnic.fr><mailto:mathieu.weill@afnic.fr>; Thomas Rickert <thomas@rickert.net><mailto:thomas@rickert.net>; León Felipe Sánchez Ambía <leonfelipe@sanchez.mx><mailto:leonfelipe@sanchez.mx>; Grace Abuhamad <grace.abuhamad@icann.org><mailto:grace.abuhamad@icann.org>; acct-staff@icann.org<mailto:acct-staff@icann.org> Subject: CCWG-ACCT Request for Guidance on PTI - IRP Sent on behalf of CCWG-Accountability Co-Chairs Dear Lise, Dear Jonathan, This is to inform you that further to our call #79, the CCWG-ACCT seeks the CWG-Stewardship’s guidance on the two proposed approaches that were suggested to address the dependency that relates to PTI compliance through the Independent Review Process (IRP) i.e.: 1. Provide direct access to IRP for PTI action or inaction; 2. Oblige ICANN in Bylaws to ensure PTI compliance, in which case failure to do is covered by IRP. We are currently in the final stages of discussion to issue our supplemental report and would need to close this item by 28 January. Any prompt feedback you could send us would be much appreciated. We look forward to your guidance. Thank you Best regards Mathieu, Thomas, León _______________________________________________ CWG-Stewardship mailing list CWG-Stewardship@icann.org<mailto:CWG-Stewardship@icann.org> https://mm.icann.org/mailman/listinfo/cwg-stewardship<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NnG6eny0oQaGz3iCqBwwlgeeC46xQbGu0Dp3_V8C35s&s=OR603kQHhn40RkVrYwPohLtx7A5rmwYr8TIhhVb6_vA&e=> -- Matthew Shears | Director, Global Internet Policy & Human Rights Project Center for Democracy & Technology | cdt.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__cdt.org&d=CwMFaQ&c=MOptN...> E: mshears@cdt.org<mailto:mshears@cdt.org> | T: +44.771.247.2987<tel:%2B44.771.247.2987> CDT's Annual Dinner, Tech Prom, is April 6, 2016. Don't miss out - register at cdt.org/annual-dinner<https://urldefense.proofpoint.com/v2/url?u=http-3A__cdt.org_annual-2Ddinner&...>. [https://ipmcdn.avast.com/images/logo-avast-v1.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_sig-2Demail-3Futm-5Fmedium-3Demail-26utm-5Fsource-3Dlink-26utm-5Fcampaign-3Dsig-2Demail-26utm-5Fcontent-3Demailclient&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NnG6eny0oQaGz3iCqBwwlgeeC46xQbGu0Dp3_V8C35s&s=sZu9jN2OHyRtZtumWCg0zdJ4LnX2Acy_NnypKeAoRUM&e=> This email has been sent from a virus-free computer protected by Avast. www.avast.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.avast.com_sig-2Dema...> _______________________________________________ CWG-Stewardship mailing list CWG-Stewardship@icann.org<mailto:CWG-Stewardship@icann.org> https://mm.icann.org/mailman/listinfo/cwg-stewardship<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NnG6eny0oQaGz3iCqBwwlgeeC46xQbGu0Dp3_V8C35s&s=OR603kQHhn40RkVrYwPohLtx7A5rmwYr8TIhhVb6_vA&e=> -- ------------------------------------------------------------------------ Seun Ojedeji, Federal University Oye-Ekiti web: http://www.fuoye.edu.ng<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fuoye.edu.ng&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NnG6eny0oQaGz3iCqBwwlgeeC46xQbGu0Dp3_V8C35s&s=KR7KFpFVoBq6KL0t3KxtuszRynyZDL72MeEUBlPzrvk&e=> Mobile: +2348035233535 alt email:<https://urldefense.proofpoint.com/v2/url?u=http-3A__goog-5F1872880453&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NnG6eny0oQaGz3iCqBwwlgeeC46xQbGu0Dp3_V8C35s&s=8bjRiYRNGoYs8dxi79lnRkDFNVhRYCbaIdA3E-ovU4Y&e=>seun.ojedeji@fuoye.edu.ng<mailto:seun.ojedeji@fuoye.edu.ng> Bringing another down does not take you up - think about your action!