Decisions reached on leadership meetings & calls are reported in the table below:

MtgDateDecision
#50

 

Do not include law enforcement survey cost/time in final report.
#48

 

R5.1 priority level has been updated to high. To be circulated for consensus via email.

#48

 

Alan, Lili, Carlton, Susan, Dmitry, Cathrin support all recommendations

#48

 

In final report, change "no objections" to  "Full Consensus"

#48

 

Priority definitions:

  • Update to High Priority text: "...so the Board may wish to focus on these first"
  • Update to Medium Priority text: "without community input"


#48

 

Report updates:

  • Data Accuracy: Deletion of paragraph N°3

  • Contractual Compliance: updates approved

  • Consumer Trust: Agreement on future changes

  • Objective 2: Updates approved

  • Plan & Annual Reports: update is agreed on p8

#45

 

Workplan new version is accepted but current deadline of 25 Jan 19 to complete action items is still the current target.
#43

 

BY.1: Consensus reached.

#43

 

CM.5: Consensus reached.

#43

 

CM.4: Consensus reached on deleting recommendation.

#43

 

CM.3: Recommendation to be deleted, discussion scheduled on Plenary #44.

#43

 

CM.2: Consensus reached.

#43

 

CM.1: Consensus reached.

#43

 

LE.2: Consensus reached.

#43

 

LE.1: Consensus reached.

#43

 

R15.1 Language mentions 6 months, Jackie to update language as per operational input received in the morning: “ICANN Bylaws, the ICANN Board has six months within receipt of the final report to consider the review team’s recommendations. We would suggest factoring this into implementation details you include in your recommendations (see 1.1 – 1.2 – 1.3 – 15.1 – LE.1 – LE.2)”.

#43

 

R15.1 Consensus reached.

#43

 

R12.1 Consensus reached.

#43

 

R11.2 Consensus reached.

#43

 

R11.1 Consensus reached.
#43

 

R10.1 Discussion deferred to plenary call #44.

#43

 

R4.1 Consensus reached

#43

 

R4.2 Consensus reached

#43

 

R3.2: Consensus reached

#43

 

R3.1  Consensus reached
#43

 

R1.3: Consensus reached on recommendation with the addition of “Board Committee or Working Group” instead of “Board Working Group”
#43

 

R1.1 | R1.2: Consensus reached

#43

 

R5.1: Following several concerns with the present updates, recommendation to be updated and re-discussed on plenary call #44.

#43

 

ICANN Bylaws: Our intent was to replace data safeguards with applicable data protection across border regulations laws and best practices, and we presumed that safeguarding registrant data was implied in that. RT will amend the recommendation to include those explicit words to make clear that RT was not omitting them; RT was just omitting them as a separate action of future review teams. RT will incorporate the term “safeguarding registrant data” into the last half of the recommendation.
#43

 

Update recommendation SG.1 to say “The board should consider whether and to what extent notifications it receives of breaches should be made public.”
#43

 

LE.2: New suggested text: The ICANN Board should consider extending and should consider to extend comparable surveys and/or studies (as described in LE.1) to other RDS (WHOIS) users working with law enforcement on a regular basis. 
#43

 

Consumer Trust: No change in the recommendation We acknowledge and agree with the comment, and RT will make some – probably substantial – change in the text but still resulting in no recommendation.
#43

 

R12.1

  • No changes needed to this recommendation and that Dmitry will address the comments.
  • Recommendation numbering: No changes needed to this recommendation and that Dmitry will address the comments.
#43

 

Single Whois Policy: Jackie to work with Alan to mention the problems of the policy development process regarding a single RDS (WHOIS), to be placed in the Executive Summary.
#43

 

Comments on R10.2:Noted. All comments are supportive.

#43

 

Comments on R10.1: As we are reviewing this document, we will verify that the wording is crystal clear. No other action is necessary.

#43

 

Objective 6: Contractual Compliance Actions: Public comment from Business Constituency on issues following the adoption of ICANN’s Temporary Specification for gTLD registration data are out of review team’s scope.
#43

 

R5.1: Recommendation needs to be reworked, it is conceivable that the recommendation could be removed or replaced with a different one. Consider changing the recommendation to say “ARS” (or some sort of accuracy-reporting system) must continue, even post-GDPR because the then-users of the data will want accuracy of data available to them. (There must be some level of contactability/accuracy of the data and we must consider the resources of Compliance)
#43

 

R3.2: ALAC comment: implementation implies when policy work is done. 
#42

Work Plan is considered approved 

#42

Final Report: Move "Relevant Research" links to appendices

#42

"Milestones" and "Participation" Fact Sheets are considered approved

#42

Final Report: Executive Summary must stand on its own, clarity not length is the major issue.

#42

Final Report: Move "Relevant Research" links to appendices.

#42

NCSG comment: Agreement on acronyms suggestion (definition, acronym list as an appendix)

#40

 

FtoF Meeting #4 objectives are:

  • Consider the results of public comment, determine any corresponding changes, and finalize its recommendations.
  • Mark up the draft report where substantial changes are needed
#40

 

Public Comment Summary Template has been approved.
#39

 

Webinar: 

  • Share final slides prior to the presentation
  • Alan, Cathrin, Susan to present the webinar, rapporteurs in attendance to answer questions
#38

 

Webinar: Leadership to present slides, rapporteurs to be invited to answer any questions on their subgroup's outputs.
#38

 

Schedule of calls:
  • Cancel plenary call next week. Next call should be scheduled for 1 October. 

  • Keep leadership calls scheduled but revisit as necessary depending on agenda

#36

 

Approved updated work plan for posting on wiki and sharing with review team as "FYI" 
#35

 

Leadership meeting to be scheduled at 08:00 AM (Brussels Time) on Face-to-Face meeting Day1

#35

 

Face to Face meeting Day2 start time will be decided on the day before and breakfast can be served whenever it comes.

#34

 

Use draft report to build Brussels meeting agenda
#32

 

Leadership team will meet and finalize slides in Panama prior to deadline and to finalize speakers for each section
#32

 

Final Deadline to submit slides is Wednesday 27 June 12:00 UTC
#31

 

ICANN62 slide deck structure is approved

#31

 

Face-to-Face Meeting #3: 

  • Use a pre-populated draft subgroup report to drive discussions and reach agreement. 

  • Report in slides background of submitted recommendations.

#30

 

Rapporteurs are to include in subgroup reports all recommendations including those without full support, and to flag those where objections have been raised so that the full RT can consider them.
#29

 

ICANN62 engagement session is approved.
#29

 

Review team to send letter (accepting Theresa Swinehart's offer and request that the RDS-WHOIS2 Review be removed from the Public Comment on Short-Term Options to Adjust the Timeline for Specific Reviews) after the plenary meeting #30 next Monday (Support team to let Theresa know beforehand).
#28

 

Face-to-Face Meeting #3: Confirmed on 19-20 July 2018

#27

 

ICANN62 - RDS-WHOIS2-RT Engagement Session: Agenda to focus on findings & recommendations (if any), less time should be spent on review team objectives and methodology.
#27

 

Plenary Calls are to be held on 21 and 28 May, 2018

#26

 

Leadership call on 9 May is cancelled
#25

 

Plenary Call #27: All rapporteurs will be invited to provide an update on their subgroups' status.
#24 Draft Report template to be presented at face-to-face meeting
#24 No plenary call scheduled on 23 April
#24

 

Reading list and agenda for face-to-face meeting #2 in Brussels are approved
#23

 

Draft agenda for Brussels meeting is pre-approved at leadership level (subject to changes based on subgroup output)

#23

 

Timeline proposed to populate findings slides is approved:

  • 9 April COB – Draft slides sent to Rapporteurs
  • 12 April COB – Rapporteurs send final updates to slides
  • 13 April COB – Support team circulates final slide-deck
#22

 

Subgroups deadlines preparing for face-to-face meeting:

April 5th subgroup report deadline

April 6th RDS Call to discuss reports - give extension to April 10th for subgroups who haven’t delivered

April 11th Leadership><staff call to reshuffle agenda accordingly.

#19

 

Schedule for Face-to-Face meeting #2 will be: 09:00 - 17:30

#16

 

Outreach plan is approved

#16

 

Fact Sheet Milestones were approved, only change is 95% instead of 90% for the milestone “Adopt and Publish Terms of Reference”

#14

 

Topics labeled "Ready"/"In Progress" should be up for RT discussion on next plenary. All rapporteurs will be asked for a status update on their subgroup's work.

#14

 

GDPR Briefing on hold at the moment

#14

 

Include outreach paper on next plenary call's agenda

#14

 

Susan will partner on fact sheet discussions. Alan wishes to remain included on email related discussions.

#11

Plenary Call: Cathrin to chair the plenary call.

#11

Plenary Call agenda can be shared with the Review Team.

#10

Monday 1430UTC - 90 min - New time for plenary call

#10

Thursday 1630UTC – 60 min – New time for leadership call
#10

Dec 5th is the envisioned completion date for the subgroups to complete the planning document.

#7

Leaders & ICANN org to have preparatory meetings at 8:00 AM on both days at face-to-face meeting.

#7

CoChairs give greenlight to share Brussels face-to-face meeting agenda with RT in preparation for Thursday plenary call.

#6

FtoF meeting agenda: Goal is to Identify tasks to be performed by subgroups and allocate responsibilities to subgroups, and also to fully understand and agree upon workplan and Terms of Reference and to complete planned implementation briefings.

#6

Plenary agenda is approved and can be circulated with the review team.
#5

Proposed plenary call agenda: Approved

#3

Leadership should put themselves in speakers' queue when speaking in their role as advocate for respective community. 

#3

Leadership to take on budget related questions. 2 sign-offs needed. 

#3

Sign-off on admin related questions should be Chair's responsibility. In absence of Chair, Vice-Chair can step in.

#3

Brussels: 1 formal dinner (Oct 2) - 2 informal dinners (Oct 1, 3). 

#3

FtoF Meeting schedule: 09:00 - 17:30 with 45 min break (lunch provided at meeting location). Meeting can start at 8:30 on day 2 if needed.

  • No labels