February 2018 - RDS-WHOIS2-RT

Fwd: [RDS-WHOIS2-REC4-Compliance] RDS-WHOIS2 Compliance Management meeting
by Susan Kawaguchi Feb. 4, 2018

Feb. 4, 2018

Hello All, The compliance subgroup met with Maguy Serad and Jamie Hedlund last week to kick off the compliance review. It was a very informative meeting and Maguy provided a written response along with the discussion. The subgroup will use this information to flesh out a plan for the compliance review. I have attached the document as others in the RT may find it interesting. Susan ---------- Forwarded message ---------- From: MSSI Secretariat <mssi-secretariat(a)icann.org> Date: Thu, Feb 1, 2018 at 5:27 PM Subject: [RDS-WHOIS2-REC4-Compliance] RDS-WHOIS2 Compliance Management meeting To: "rds-whois2-rec4-compliance(a)icann.org" < rds-whois2-rec4-compliance(a)icann.org> Hello Rec 4 Compliance Subgroup members, Please see attached document for RDS-WHOIS2 Compliance subgroup meeting with Compliance Management. Thank you. With kind regards, *Brenda Brewer,** Projects & Operations Assistant * Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Skype: brenda.brewer.icann Phone: 1-310-745-1107 <(310)%20745-1107> _______________________________________________ RDS-WHOIS2-REC4-Compliance mailing list RDS-WHOIS2-REC4-Compliance(a)icann.org https://mm.icann.org/mailman/listinfo/rds-whois2-rec4-compliance

1 0

missing cal today - apologies
by Erika Mann Feb. 2, 2018

Feb. 2, 2018

Apologies team for missing the call today. My brain was still connected to European time and I expected to have the call in the afternoon. Silly mistake. Have a good weekend, Erika

1 0

WHOIS Information Must Remain Available
by Carlton Samuels Feb. 2, 2018

Feb. 2, 2018

...never mind the GDPR purists, says our Uncle Sam. https://domainnamewire.com/2018/01/29/u-s-gov-whois-info-must-remain-availa… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

3 3

Agenda - Call # 17 - 2 February @ 13:30 UTC
by Jean-Baptiste Deroulez Feb. 2, 2018

Feb. 2, 2018

Dear Review Team Members, In preparation for your call #17<https://community.icann.org/display/WHO/Meeting+%2317+-+14+February+2018>, scheduled for tomorrow, Friday, 2 February 2018 – 13:30-15:00 UTC, please find below the suggested meeting agenda: 1. Welcome, roll-call, SoI updates 2. Terms of Reference & Work plan Note: Review Alan’s email<http://mm.icann.org/pipermail/rds-whois2-rt/2018-February/000316.html> in preparation for the call 3. Subgroup status update & next steps Note: Rapporteurs (or subgroup member if rapporteur is unable to join call) will be asked to explain how they plan to carry through work, and be prepared for the face-to-face meeting 4. Confirm request for written implementation briefings: http://mm.icann.org/pipermail/rds-whois2-rt/2018-February/000315.html 5. Face-to-Face Meeting #2 6. ICANN62 7. Scheduling calls 8. Confirm decisions reached and action items 9. 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>. As always, let us know if you have any questions or concerns. Kind regards, Jean-Baptiste

3 2

Request for written briefings
by Alan Greenberg Jan. 31, 2018

Jan. 31, 2018

As previously discussed, 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 the amount of staff time/resources that went into the implementation. This is a low priority item and delivery of briefings should not be delayed in order to provide it. We would appreciate these briefings no later than 29 March 2018, but delivery of individual Recommendation briefings should not be delayed awaiting all of them to be completed. The RT notes that to the extent that this information already exists in the oral/presentation briefings already provided to the review team, that material may be used as the basis for these new documents. Alan Greenberg Chair, RDS-WHOIS2-RT

1 0

Addressing the Board caucus Group's concerns
by Alan Greenberg Jan. 31, 2018

Jan. 31, 2018

At our last meeting, Chris shared a concern ofthe Board Causus Group that the RT may wish to defer work on some items that may be appreciably affected by changes in response to the EU GDPR. I have added a paragraph at the end of the section detailing our scope. The draft version (page 4-5) reads: In recognition that the WHOIS landscape will be changing, perhaps radically, over the coming months as ICANN addresses how it will respond to the EU General Data Protection Regulation (GDPR), the RT may choose to defer some or all of its work in relation to the scope items on Law Enforcement Needs, Consumer Trust and Safeguarding Registrant Data until it is more clear what path ICANN will be following. Should any work be deferred, individual timelines may slip. However, it is the intent of the RT that the overall schedule calling for the final report to be delivered by the end of December 2018 not change appreciably. I would like to highlight three points that are included in that statement: 1. I believe that the three area are the only ones that may significantly affected by the GDPR compliance model selected and the associated redaction of certain WHOIS fields. None of the post WHOIS1-RT analysis is affected. Anything New will largely address a number of things that have already or are in the process of changing, and although what Compliance does may be affected, our analysis of how they do it and how transparently they do it should not be. 2. Deferring work may imply that our interim report is less complete, but I do not sense that there is a desire to stretch out this entire review, thus my hope that we will still make our final deliver date (or perhaps slip by a month or so). 3. I have hedged on whether we will indeed slip on all of these. I am optimistic that by the time we meet in April, ICANN's path forward on GDPR will be known, and I also consider that the three scope area are not among our most complex items, so we may well be able to make up for lost time quickly. Moreover, I suspect that we can actually start thinking about these issue, even though we do not fully understand where GDPR is leading us. This will be further discussed on Friday, and hopefully we can come to closure quickly to allow us to send the final ToR to the Board. I have also attached what I think was the latest assignment matrix, updated to reflect the merger of two Compliance groups, with a double line separating the items which may be deferred. It shows that even if they are all fully deferred, no one is left without any work (although a few people may have it a bit easier if we do not make some changes). Alan

1 0