[council] ICANN Contractual Compliance Response Re:BulkRegistrations

[Theo Geurts]

I agree Mark, nothing surprising in the response from Compliance. 

However, it also reads that there is no pressing issue. 
The time that there was a pressing issue was with Conficker (2008) and Avalanche (2016). These threats were neutralized with efforts from LEA's, CP's and ICANN ORG. 

Best, 
Theo 

On Thu, Feb 23, 2023, at 9:37 AM, Mark W. Datysgeld via council wrote:
> Thank you for the heads-up, Steve.
> 
> While there is nothing surprising in their response, it consolidates in writing that bulk registrations are not being looked into by ICANN and that we definitely need more information from CPs to be able to gauge how this resource is currently being used.
> 
> Best,
> ---
> Mark W. Datysgeld
> Director at Governance Primer
> ICANN GNSO Councilor
> 
> 
> *From:* Steve Chan via council <council at gnso.icann.org>
> *Sent:* Wednesday, February 22, 2023 18:12
> *To:* council at gnso.icann.org
> *Subject:* [council] ICANN Contractual Compliance Response Re: Bulk Registrations
> 
>> Dear Councilors,
>>  
>> You will likely recall that as a result of the Council’s adoption of the recommendations from its small team on DNS Abuse that a letter <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/ducos-to-heineman-et-al-06jan23-en.pdf> was sent to a number of parties seeking information about bulk registrations, including ICANN Contractual Compliance as one of the recipients. Attached, please find the response from Jamie Hedlund, SVP, Contractual Compliance & U.S. Government Engagement.
>>  
>> This response will be added to the GNSO’s correspondence page. If you have any questions, please let us know.
>>  
>> Best,
>> Steve
>>  
>>  
>>  
>> *Steven Chan**
*
>> Senior Director, Policy Development Support & GNSO Relations
>>  
>> Internet Corporation for Assigned Names and Numbers (ICANN) 
>> 12025 Waterfront Drive, Suite 300
>> Los Angeles, CA 90094-2536

>>                                                                   
>> Email: steve.chan at icann.org
>> Skype: steve.chan55
>> Mobile: +1.310.339.4410
>>  
>> Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
>> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
>> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar  <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
> 
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230223/eba06ecb/attachment-0001.html>