November 2019 - Bc-gnso - lists.icann.org

Business Constituency (BC) Comment on Draft FY21 PTI and IANA Budgets
by Steve DelBianco Nov. 27, 2019

Nov. 27, 2019

Attached is the comment of ICANN’s Business Constituency (BC) regarding the Draft FY21 PTI and IANA Budgets. This comment was drafted by Jimson Olufuye and Tim Smith. It was approved in accord with our Charter. -- Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency (BC)

1 0

ICANN Policy Development Process (PDP) 3.0 Implementation Webinar Invitation | Wednesday, 27 November 2019 at 21:00 UTC
by Steve DelBianco Nov. 15, 2019

Nov. 15, 2019

BC members – I think this webinar will be valuable for those who are presently or potentially participating in ICANN Working Groups. The GNSO Council is hosting a public Policy Development Process (PDP) 3.0 Implementation Webinar. Intended first for GNSO Councilors, SO, AC, SC and C community members are welcome to participate. Please see webinar details below. Wednesday, 27 November 2019 at 21:00 UTC for 90 minutes. For other times: https://tinyurl.com/yj7edybk [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yj7edybk&d…> Webinar content: * Details for the proposed implementation of the PDP 3.0 improvements, including potential changes to how the ICANN community participate in GNSO working groups * Opportunity for audience to ask questions and provide feedback to the GNSO Council small team who developed the implementation documents Preparation materials: Proposed PDP 3.0 implementation documents delivered to the GNSO Council https://community.icann.org/x/v4rkBg<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Please join the Zoom room: https://icann.zoom.us/my/gnso1 [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_my_gnso1…> You will have VoIP and telecom bridge audio options available to you upon logging in. If you are joining via audio only, please see below. One tap mobile +19294362866,,7441796513# US (New York) +16699006833,,7441796513# US (San Jose) Meeting ID: 744 179 6513 Find your local number: https://zoom.us/u/aRxRoDRS<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_u_aRxRoDRS&d=D…>

1 0

ICANN enforcement of Registrar obligations against Abuse
by Steve DelBianco Nov. 7, 2019

Nov. 7, 2019

This week in Montreal, we met with ICANN Compliance chief Jamie Hedlund (copied here). On Tuesday, Jamie shared the 2 breach notices issued for violations of Public Interest Commitments in Spec 11 in the Registry Agreement, pertaining to the transparency requirement in 3c. Yesterday, I asked Jamie to share breach notices based on 3.18.1 of the Registrar Accreditation Agreement (RAA): 3.18 Registrar's Abuse Contact and Duty to Investigate Reports of Abuse. 3.18.1 Registrar shall maintain an abuse contact to receive reports of abuse involving Registered Names sponsored by Registrar, including reports of Illegal Activity. Registrar shall publish an email address to receive such reports on the home page of Registrar's website (or in another standardized place that may be designated by ICANN from time to time). Registrar shall take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse. Below is Jamie’s quick response (Thanks, Jamie). ICANN Compliance issued a notice of breach<https://www.icann.org/uploads/compliance_notice/attachment/891/serad-to-han…> and was subsequently escalated to termination<https://www.icann.org/uploads/compliance_notice/attachment/895/serad-to-han…> of the registrar’s accreditation for failure to demonstrate compliance in response to a notice involving the registrar’s handling of an abuse report. There was a second breach based on Section 3.18 for failure to investigate and respond to abuse reports: https://www.icann.org/en/system/files/correspondence/serad-to-golding-22jan… ICANN Compliance has issued several notices that included violations of the obligation to display abuse contact information under Section 3.18 of the RAA; a few examples below (their status, including whether they were cured, or escalated to suspension or termination is listed in the Compliance enforcement page at https://www.icann.org/compliance/notices) https://www.icann.org/uploads/compliance_notice/attachment/981/serad-to-677… https://www.icann.org/uploads/compliance_notice/attachment/923/serad-to-nic… https://www.icann.org/uploads/compliance_notice/attachment/901/serad-to-orz… https://www.icann.org/uploads/compliance_notice/attachment/1125/hedlund-to-… https://www.icann.org/uploads/compliance_notice/attachment/1033/serad-to-lo… https://www.icann.org/uploads/compliance_notice/attachment/1107/serad-to-zh… https://www.icann.org/uploads/compliance_notice/attachment/1055/serad-to-pe… https://www.icann.org/uploads/compliance_notice/attachment/1047/serad-to-wa… https://www.icann.org/uploads/compliance_notice/attachment/1037/serad-to-zh… https://www.icann.org/uploads/compliance_notice/attachment/1035/serad-to-de… https://www.icann.org/uploads/compliance_notice/attachment/1021/serad-to-ka… https://www.icann.org/uploads/compliance_notice/attachment/979/serad-to-240… https://www.icann.org/uploads/compliance_notice/attachment/953/serad-to-lop… https://www.icann.org/uploads/compliance_notice/attachment/945/serad-to-boo… https://www.icann.org/uploads/compliance_notice/attachment/931/serad-to-ven… https://www.icann.org/uploads/compliance_notice/attachment/923/serad-to-nic… https://www.icann.org/uploads/compliance_notice/attachment/913/serad-to-wes… https://www.icann.org/uploads/compliance_notice/attachment/907/serad-to-vil… https://www.icann.org/uploads/compliance_notice/attachment/903/serad-to-gra… The above does not reflect the number of abuse complaints processed by ICANN Compliance that did not result in breaches (the vast majority across all complaint types). In these cases, the registrar demonstrated having taken reasonable and prompt steps to investigate and respond appropriately to the abuse report in accordance with the registrar’s own abuse policies by, for example, suspending the domain name; contacting the registrant of the domain name(s) subject to the abuse report and asking for and obtaining evidence (e.g. licenses for pharmaceutical-related abuse reports); providing web-hosting information about the subject domain name(s) to the complainant for reporting the abusive content to the entity hosting the allegedly abusive content or terminating the agreement between the registrar and registrant by allowing the transfer to a different registrar. Hope this is helpful. Thanks. Best, Jamie

2 1

FW: Spec 11 breaches
by Steve DelBianco Nov. 5, 2019

Nov. 5, 2019

ICANN’s Compliance chief Jamie Hedlund followed-up on our request today. (below) Note that these 2 breach notices pertain not to the abuse provisions in 3a of the PIC, but to 3c, which reads: 1. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies. On 11/5/19, 5:56 PM, "Jamie Hedlund" <jamie.hedlund(a)icann.org<mailto:jamie.hedlund@icann.org>> wrote: Steve, Thanks again for inviting Compliance to meet with the BC. Following up on the Spec.11 discussion, wanted to let you know that ICANN Compliance has issued two notices of breach under Section 3.c. of Specification 11 of the Registry Agreement: * On 16 March 2017, direct link to the notice of breach https://www.icann.org/uploads/compliance_notice/attachment/911/serad-to-wes… * On 12 July 2018, direct link to the notice of breach https://www.icann.org/uploads/compliance_notice/attachment/1049/serad-to-al… Hope that’s helpful. Thanks. Best, Jamie Jamie Hedlund Senior Vice President, Contractual Compliance and Consumer Safeguards Managing Director, Washington, DC Office Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +1 202 570 7125 Mobile: +1 202 374 3969 www.icann.org<http://www.icann.org>

1 0