Dear review team members,
This is to kindly remind you that
all team members should, no later than this coming Friday (with the exception of Stephanie), review, at the least, the sections that they led and preferably those that they participated in with the aim of:
- ensuring no inconsistencies;
- addressing any issues noted in comments;
- identifying (or fixing) duplications to avoid saying the same thing multiple times.
Many thanks in advance,
Kind regards,
Jean-Baptiste
From: Jean-Baptiste Deroulez <jean-baptiste.deroulez@icann.org>
Date: Monday, January 14, 2019 at 5:36 PM
To: RDS WHOIS2-RT List <rds-whois2-rt@icann.org>
Subject: IMPORTANT: [RDS-WHOIS2-RT] Plenary Call #46 | 14 January 2019 | 15:00 - 16:30 UTC
Dear review team members,
Following up on today’s call decisions reached and action items,
review team members/subject matter experts are invited to
The attached suggested updates were accepted by members in presence, see minor updates, decisions reached and action items below, please share any concerns you may have before
Friday January 2019, 23:59:
Decisions reached: Agreement from members in attendance with rationale for R1.1, R1.2.
Action item: R1.1, R1.2 Implementation section should say "working group" not "Working Group"
Action item:
R1.3: should say "working group" not "Working Group"
Action item: Jackie emphasize the "at minimum" sentence in rationale. Replace the "or" at the end of the 4th line with an "and".
Decisions reached: New text:
R11.2: The ICANN Board should direct the ICANN organization to ensure that the common interface displays all applicable output for each gTLD domain name registration as available
from contracted parties, including multiple versions when the outputs from registry and registrar differs. The common interface should be updated to address any policy or contractual changes to maintain full functionality.
Action item: Under “Possible Impact GDPR and other applicable laws” Alan to add a paragraph on current situation pointing out the paradox of goodwill vs doing it properly.
Add sentence on whether contractual compliance can verify compliance if they can't look at the data.
Plenary call is confirmed next week, updates from each subject matter expert will be presented.
Kind regards,
Jean-Baptiste
From: RDS-WHOIS2-RT <rds-whois2-rt-bounces@icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez@icann.org>
Date: Monday, January 14, 2019 at 2:12 PM
To: RDS WHOIS2-RT List <rds-whois2-rt@icann.org>
Subject: Re: [RDS-WHOIS2-RT] Plenary Call #46 | 14 January 2019 | 15:00 - 16:30 UTC
Dear review team members,
In preparation for today’s plenary call, please find attached the supporting slides.
Kind regards,
Jean-Baptiste
From: RDS-WHOIS2-RT <rds-whois2-rt-bounces@icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez@icann.org>
Date: Friday, January 11, 2019 at 7:05 PM
To: RDS WHOIS2-RT List <rds-whois2-rt@icann.org>
Subject: [RDS-WHOIS2-RT] Plenary Call #46 | 14 January 2019 | 15:00 - 16:30 UTC
Dear review team members,
In preparation for your plenary call #46, scheduled for Monday, 14 January at 15:00-16:30
UTC, please find the below meeting agenda:
1. Welcome, roll-call, SoI
2. Updates review:
·
WHOIS1 Rec #1 - Strategic Priority
·
Subgroup 3 - Law Enforcement Needs
·
Objective 6: ICANN Contractual Compliance Actions, Structure and Processes
·
+ Any other submitted updates
3. A.O.B.
Thank you for reviewing the previously shared action items list and completing any items assigned to you.
As always, let us know if you have any questions or concerns.
Kind regards,
Jean-Baptiste