[RDS-WHOIS2-REC4-Compliance] [Ext] Re: RDS-WHOIS2 Rec 4: Compliance Meeting #2 | 22 January | 14:30 UTC

Carlton Samuels carlton.samuels at gmail.com
Sun Jan 28 01:00:43 UTC 2018


Hi Susan:
I have added a few lines of questioning that might be useful.

Best,
-Carlton


==============================
*Carlton A Samuels*

*Mobile: 876-818-1799Strategy, Planning, Governance, Assessment &
Turnaround*
=============================

On Fri, Jan 26, 2018 at 2:35 PM, Susan Kawaguchi <susankpolicy at gmail.com>
wrote:

> Hello All,
>
> Resending the list of questions for ICANN compliance team kick off
> meeting.  Please send edits/comments by COB on Monday so that we can
> provide this to the compliance team management for the short meeting
> scheduled next week.
>
> Best regards,
>
> Susan
>
> On Tue, Jan 23, 2018 at 12:35 AM, Jean-Baptiste Deroulez <
> jean-baptiste.deroulez at icann.org> wrote:
>
>> Hi Susan,
>>
>>
>>
>> I don’t see any attachment in your email. Could you please resend it to
>> the group?
>>
>>
>>
>> Many thanks.
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Jean-Baptiste
>>
>>
>>
>> *From: *Susan Kawaguchi <susankpolicy at gmail.com>
>> *Date: *Tuesday, January 23, 2018 at 12:46 AM
>> *To: *Jean-Baptiste Deroulez <jean-baptiste.deroulez at icann.org>
>> *Cc: *"rds-whois2-rec4-compliance at icann.org" <
>> rds-whois2-rec4-compliance at icann.org>
>> *Subject: *[Ext] Re: [RDS-WHOIS2-REC4-Compliance] RDS-WHOIS2 Rec 4:
>> Compliance Meeting #2 | 22 January | 14:30 UTC
>>
>>
>>
>> Hello All,
>>
>>
>>
>> Thank you Jean-Baptiste for the excellent review of the meeting this
>> morning.  As we discussed several of the subgroup will be in the ICANN
>> offices next week for other meetings so thought we should take advantage of
>> that time and start an initial discussion with the Compliance team
>> management  I have attached a document in which  I have included all the
>> questions we discussed this morning and included a few more.
>>
>>
>>
>> Please review and edit.  We would like to provide this to the compliance
>> team Wednesday morning so please have your comments and edits by COB on
>> Tuesday.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> Susan
>>
>>
>>
>> On Mon, Jan 22, 2018 at 10:57 AM, Jean-Baptiste Deroulez <
>> jean-baptiste.deroulez at icann.org> wrote:
>>
>> Dear subgroup members,
>>
>>
>>
>> Following today’s compliance subgroup meeting, please find below the
>> identified action items and useful links:
>>
>>
>>
>> *ACTION ITEMS:*
>>
>>
>>
>> *Subgroup 2-day face-to-face meeting*
>>
>> - Alan and Susan requested to hold a two days subgroup face-to-face
>> meeting with Compliance Department at ICANN org office in Los Angeles, only
>> a small conference room would be needed. This would happen before the next
>> plenary face-to-face meeting. ICANN org to liaise with meetings team to
>> confirm notification time needed with meetings teamto prepare such meeting
>> to identify a possible date (also taking into consideration compliance
>> department staff would be available).
>>
>>
>>
>> *Next Week’s Kick-Off Meeting with ICANN org Compliance Team (exact date
>> to be confirmed)*:
>>
>> *Initial 1hour kickoff meeting between subgroup members who are in LA
>> next week and members of the compliance Department*
>>
>> - Questions raised on today's call to be shared with the subgroup (see
>> below), subgroup members not attending the call to share input/edits by
>> Wednesday COB.
>>
>> - Subgroup members to review attached first pass planning document and
>> raise any questions, edits, *by tomorrow COB.*
>>
>> - ICANN org to look into the possibility to add remote participation
>> during the meeting with compliance for remote subgroup members.
>>
>>
>>
>> *Questions for Compliance Team:*
>>
>> - Understand the structure of Compliance and how it deals with WHOIS
>>
>> For example:
>>
>> How many employees?
>>
>> How many management?
>>
>> Are there separate teams?
>>
>> Do people who work on WHOIS inaccuracy work on other things?
>>
>> How are WHOIS issues brought to attention of others on team?
>>
>> - What tools do you use?
>>
>> - What are the sources of data they are capturing?
>>
>> - How does compliance assemble individual issues into a bigger picture?
>>
>> - Do they have a roadmap for future changes to WHOIS already
>>  and how that affects the compliance? How will complianc
>> e work flows change when WHOIS enforcement changes?
>>
>>
>>
>> *USEFUL LINKS*:
>>
>> Risk Committee link: https://www.icann.org/re
>> sources/pages/risk-committee-2014-03-21-en[icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_risk-2Dcommittee-2D2014-2D03-2D21-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=98XHtiH63htfS1RcxAa37AUHIa-ulO39TgjeiRxSnHk&s=JbDwWp5Y0ubO7srzHw-ubTV93g2GZ4ft4s1D_q8TBDk&e=>
>>
>> Risk Commitee's Charter: https://www.icann.org/resource
>> s/pages/charter-brc-2017-11-10-en[icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_charter-2Dbrc-2D2017-2D11-2D10-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=98XHtiH63htfS1RcxAa37AUHIa-ulO39TgjeiRxSnHk&s=f2hx50kIoTUgBkeDPQwa6UlgF9x-BkXyfW-BOIu8ngg&e=>
>>
>> Compliance page : https://www.icann.org/resource
>> s/pages/compliance-2012-02-25-en[icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_compliance-2D2012-2D02-2D25-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=98XHtiH63htfS1RcxAa37AUHIa-ulO39TgjeiRxSnHk&s=AYehP8tg31r7gXZnypvv3lzAuFr2wY_Ri6rP31iQNG8&e=>
>>
>> Contractual Compliance Staff: https://www.icann.org/resource
>> s/pages/about-2014-10-10-en[icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_about-2D2014-2D10-2D10-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=98XHtiH63htfS1RcxAa37AUHIa-ulO39TgjeiRxSnHk&s=2k2onrdz89csqNqfT944pUZTJO49HLXtjCeiYVFIDvk&e=>
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Jean-Baptiste
>>
>>
>> _______________________________________________
>> RDS-WHOIS2-REC4-Compliance mailing list
>> RDS-WHOIS2-REC4-Compliance at icann.org
>> https://mm.icann.org/mailman/listinfo/rds-whois2-rec4-compliance
>>
>>
>>
>
>
> _______________________________________________
> RDS-WHOIS2-REC4-Compliance mailing list
> RDS-WHOIS2-REC4-Compliance at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rec4-compliance
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/attachments/20180127/46f24785/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Understand?the?structure?of?Compliance?and?how?it?deals?with?WHOIS - with edits from Carlton Jan 27.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 15277 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/attachments/20180127/46f24785/UnderstandthestructureofComplianceandhowitdealswithWHOIS-witheditsfromCarltonJan27-0001.docx>


More information about the RDS-WHOIS2-REC4-Compliance mailing list