Hi ICANN SSR team, Below is a request for information that James submitted on the SSR implications of the .avianca tld https://www.icann.org/uploads/compliance_notice/attachment/957/serad-to-reyes-19sep17.pdf[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_uploads_compliance-5Fnotice_attachment_957_serad-2Dto-2Dreyes-2D19sep17.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=Q_fMdPzWh_dPIFRoT0_RCyUZ-mS0xeE4EeQTxa_ckQI&m=p2Lm8ofa5rNaO0aLWcmV_BrbBLrEviypvPlmzqsq3Q8&s=cJuVslqsC2Mc9J5JfL2DacOYaGfaGtZXfivBKb2e-wc&e=>. Posting to the list so that everyone can see the response. We will also update the tracker accordingly. Question: When and where do the decisions on enforcement of non-compliance get evaluated for SSR impact (in this case where a gTLD is AWOL but for months no actual action is taken) Response: “The question is viewed in 2 parts – the first is the Compliance role and responsibilities which we can address below and the other is the decision to invoke an EBERO event, which should be addressed by the EBERO team. Compliance work is focused on bringing the registry operator into compliance and addressing the issues that led to non-compliance. Once there is a non-compliance issue, ICANN Contractual Compliance enforcement decisions are based on the contractual obligations. The SSR impact of non-compliance for critical registry functions, as defined in the contract, have previously been evaluated in the determination of Specification 10 (Registry Performance Specification) and EBERO requirements. ICANN continues to work with .avianca in an effort to bring the registry operator into compliance. The EBERO team is responsible for the evaluation and decision on whether to invoke an EBERO event for the five critical registry functions.” Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce@icann.org Skype: jennifer.bryce.icann www.icann.org