- RDS-WHOIS2-RT - lists.icann.org

GDPR and WHOIS
by Erika Mann Nov. 21, 2017

Nov. 21, 2017

Just in case you did not notice this: https://www.icann.org/news/blog/data-protection-privacy-activity-recap Sent from my iPhone

1 0

RESEND: Terms of Reference
by Alan Greenberg Nov. 20, 2017

Nov. 20, 2017

[With attachment this time] I have done a detailed review of the terms of reference and offer the following updated version. Note that this includes a number of Questions in the form of Comments inserted into the document. Alan

2 1

ICANN Blog Post Re: GDPR - Dated 17 November 2017
by Cathrin.BAUER-BULST＠ec.europa.eu Nov. 20, 2017

Nov. 20, 2017

https://www.icann.org/news/blog/data-protection-privacy-activity-recap Relevant Extracts: · To be clear, we will defer enforcement on a temporary basis during this period of uncertainty. We also want to clarify that submission of a model does not mean that it will qualify for deferral or that any deferral granted will be permanent. ICANN is currently considering the process for reviewing deferral submissions. The sharing of models is also an important contribution to feed into subsequent iterations of analysis from the Hamilton law firm. · On a related note, we are encouraged to know that various contracted parties are discussing the possibility of aligning models prior to submission. We commend this effort. Fewer models will ease the impact on end-users and operational processes for all of us including the contracted parties themselves.

1 0

Re: [RDS-WHOIS2-RT] AGENDA - Call #12 - 20Nov2017
by Jean-Baptiste Deroulez Nov. 20, 2017

Nov. 20, 2017

Dear Review Team members, In anticipation of today’s plenary call #12<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>, please find attached the updated version of documents that will be projected in Adobe Connect. Plenary Call Agenda: 1. Welcome, roll-call, SoI updates 2 Subgroup kick-off & next steps 3. Scope of review 4. Terms of Reference 5. Work plan 6. Scheduling 7. A.O.B. You should all have received dial-in details to join this call. If not, please contact us off list at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org> and we will make sure to send you a copy. Please feel free to join earlier to confirm your Adobe Connect and audio connections, if you wish. As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste From: RDS-WHOIS2-RT <rds-whois2-rt-bounces(a)icann.org> on behalf of Alice Jansen <alice.jansen(a)icann.org> Date: Tuesday, November 14, 2017 at 10:56 AM To: "rds-whois2-rt(a)icann.org" <rds-whois2-rt(a)icann.org> Subject: [RDS-WHOIS2-RT] AGENDA - Call #12 - 20Nov2017 Dear Review Team Members, On leadership call #10, it was determined – in light of a scheduling tool and based on the list of identified conflicts – that Mondays, 14:30UTC, would be the most convenient time for your weekly plenary calls. You should have received a calendar invite from MSSI-Secretariat. Calls are scheduled for 90 minutes. There is a placeholder on your call #12 agenda, should you have scheduling conflicts you wish to bring to the Review Team’s attention. In preparation for your call #12[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>, Monday, 20 November at 14:30 UTC (timezone converter[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.timeanddate.com_wo…>), please below a proposed meeting agenda. Note: the agenda includes a number of actions needed from you prior to the call. 1. Welcome, roll-call, SoI updates Required action: Please return your duly signed and completed Conflict of Interest policy[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> and Statement of Interests form[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> to rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. Our recommendation is to send us a scanned copy of your forms. You can check status of your documents here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…>. 2 Subgroup kick-off & next steps Required action: As requested<http://mm.icann.org/pipermail/rds-whois2-rt/2017-November/000208.html>, please identify the two subgroup efforts (in order of preference) you would be interested in leading (“rapporteur”) by Monday, 20 November – 11:00 UTC. See matrix[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> of subgroups here. 3. Scope of review See here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…>. 4. Terms of Reference Required action: A number of edits have been made to the Terms of Reference. Read through this clean version of Terms of Reference and flag any concerns/objections you may have. There will be a call for edits on the plenary call. 5. Work plan Required action: Review the work plan and share any concerns you may have. It includes a new submission date to the Board for the ToR/work plan (28 Nov) as a result of adjustments made to the call schedule. It also includes a suggested timeline for the subgroup kick-off activities. The Review Team leadership will be looking for a couple of volunteers to run an in-depth analysis of the work plan. Consider whether you wish to volunteer. 6. Scheduling See above. 7. A.O.B. Thanks Kind regards Alice

1 0

Interesting piece
by Erika Mann Nov. 20, 2017

Nov. 20, 2017

FYI Interesting piece concerning WHOIS and related areas: https://www.farsightsecurity.com/2017/11/17/stsauver-rdap/ Sent from my iPhone

1 0

DRAFT Request for written briefings WHOIS1-RT Recommendations
by Alan Greenberg Nov. 20, 2017

Nov. 20, 2017

During the informal lunch in Abu Dhabi, I suggested that we ask ICANN Org for written statements on the implementation of the first WHOIS RT recommendations. This would augment the published summaries we already have access to plus the Plenary Briefings we received. Following is that draft request. Comments or additions? Do we want to set a deadline? Do we want to ask for an assessment of whether the implementation was an effective use of ICANN Org resources? Alan =================== The RDS-WHOIS2-RT formally requests written detailed implementation reports for the Recommendations of the first WHOIS-RT. Such reports should include: - To what extent the recommendation was implemented as written; - If the implementation was different from that requested, the rationale; - Details of the implementation; - Results of the implementation, and to the extent applicable, metrics/measurements indicating the degree of success or change as a result of the implementation; - To the degree practical, as assessment of whether the implementation met its desired goals.

2 1

Terms of Reference
by Alan Greenberg Nov. 20, 2017

Nov. 20, 2017

I have done a detailed review of the terms of reference and offer the following updated version. Note that this includes a number of Questions in the form of Comments inserted into the document. Alan

1 0

For your information - Confidential Disclosure Framework
by Alice Jansen Nov. 16, 2017

Nov. 16, 2017

Dear Review Team Members, As you prepare for your data analysis phase, we wanted to provide you with a copy of the Confidential Disclosure Framework (CDF) and the associated Non-Disclosure Agreement. Please note that this is for your information only; no need for a signed NDA has been identified yet. We wish to provide you with all the information available for reference, in the event a signed NDA is required later in process. The CDF is in alignment with ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en> Article 4, Section 4.6 (a)(iv)(A): To facilitate transparency and openness regarding ICANN's deliberations and operations, the review teams, or a subset thereof, shall have access to ICANN internal information and documents pursuant to the Confidential Disclosure Framework set forth in the Operating Standards (the "Confidential Disclosure Framework"). Note the following guidelines: (1) ICANN must provide a justification for any refusal to reveal requested information. ICANN's refusal can be appealed to the Ombudsman and/or the ICANN Board for a ruling on the disclosure request. (2) ICANN may designate certain documents and information as "for review team members only" or for a subset of the review team members based on conflict of interest. ICANN's designation of documents may also be appealed to the Ombudsman and/or the ICANN Board. (3) ICANN may require review team members to sign a non-disclosure agreement before accessing documents. As indicated in the Draft Operating Standards<https://www.icann.org/en/system/files/files/draft-operating-standards-speci…>, Review team members that do not wish to adhere to the conditions set forth in the CDF to access confidential information, may continue to participate in the review. Yet, as detailed in the CDF, they may face restriction when accessing documents and when participating in discussions pertaining to those documents. We are happy to answer any questions you may have. Thanks Best regards Alice

1 0

AGENDA - Call #12 - 20Nov2017
by Alice Jansen Nov. 14, 2017

Nov. 14, 2017

Dear Review Team Members, On leadership call #10, it was determined – in light of a scheduling tool and based on the list of identified conflicts – that Mondays, 14:30UTC, would be the most convenient time for your weekly plenary calls. You should have received a calendar invite from MSSI-Secretariat. Calls are scheduled for 90 minutes. There is a placeholder on your call #12 agenda, should you have scheduling conflicts you wish to bring to the Review Team’s attention. In preparation for your call #12<https://community.icann.org/display/WHO/Meeting+%2312+-+20+November+2017>, Monday, 20 November at 14:30 UTC (timezone converter<https://www.timeanddate.com/worldclock/fixedtime.html?msg=RDS-WHOIS2+Review…>), please below a proposed meeting agenda. Note: the agenda includes a number of actions needed from you prior to the call. 1. Welcome, roll-call, SoI updates Required action: Please return your duly signed and completed Conflict of Interest policy<https://community.icann.org/download/attachments/71600710/RDS-COI-Sept%2020…> and Statement of Interests form<https://community.icann.org/download/attachments/71600710/RDS-SOI-Sept%2020…> to rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org>. Our recommendation is to send us a scanned copy of your forms. You can check status of your documents here<https://community.icann.org/display/WHO/Legal+Documents>. 2 Subgroup kick-off & next steps Required action: As requested<http://mm.icann.org/pipermail/rds-whois2-rt/2017-November/000208.html>, please identify the two subgroup efforts (in order of preference) you would be interested in leading (“rapporteur”) by Monday, 20 November – 11:00 UTC. See matrix<https://community.icann.org/download/attachments/71601054/RDSWHOIS2-Subgrou…> of subgroups here. 3. Scope of review See here<https://community.icann.org/download/attachments/64084100/Scope-and-Objecti…>. 4. Terms of Reference Required action: A number of edits have been made to the Terms of Reference. Read through this clean version of Terms of Reference<https://community.icann.org/download/attachments/64084100/Draft%20ToR%20RDS…> and flag any concerns/objections you may have. There will be a call for edits on the plenary call. 5. Work plan Required action: Review the work plan<https://community.icann.org/download/attachments/64084086/RDS-WHOIS2-RT%20W…> and share any concerns you may have. It includes a new submission date to the Board for the ToR/work plan (28 Nov) as a result of adjustments made to the call schedule. It also includes a suggested timeline for the subgroup kick-off activities. The Review Team leadership will be looking for a couple of volunteers to run an in-depth analysis of the work plan. Consider whether you wish to volunteer. 6. Scheduling See above. 7. A.O.B. Thanks Kind regards Alice

4 3

A Patent For WHOIS Privacy?
by Carlton Samuels Nov. 14, 2017

Nov. 14, 2017

...from the folks of web.com; a proprietary(?) of Network Solutions. https://domainnamewire.com/2017/11/14/web-com-gets-whois-privacy-patent/#co… -Carlton Disclosure: Many years ago, in the days when it was a registered SDBE federal contractor with partners McHenry, Denault, Grigsby et.al, I was a low-number employee of Network Solutions. ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

1 0