Versions Compared

Old Version 83

changes.mady.by.user Jean-Baptiste Deroulez

Saved on

compared with

New Version 84

changes.mady.by.user Jean-Baptiste Deroulez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

MtgDateActionAction OwnerDue DateAction CompleteStatus
538/25

Review Drew's paper on DNS Abuse and send questions, edits.

CCTRTAug 31
IN PROGRESS
538/25Rec. 1: review the recommendation and use of "to justify policy initiatives" JonathanAug 31
IN PROGRESS
538/25Parking Paper: revise text based on Waudo's inputJonathanAug 31
IN PROGRESS
528/2

Rec 1 - Incorporate comments received on call #52 

JonathanAug 23, 2017
IN PROGRESS
528/2Rec. 10-40: Discuss possible consolidation of both recommendationsDavid/JordynAug 23, 2017
IN PROGRESS
528/2Rec. 11-49: Insert a cross-reference
Nov 2017
IN PROGRESS
528/2Rec 9: Change priority level to low. Use in consultation with instead of in association with.ICANN org

IN PROGRESS
528/2

During editing process, proof readers should make sure that the references to the surveys (consuner end-user and registrant) are consistent throughout both the Report and the Recommendations. 

ICANN org

IN PROGRESS
528/2

Parking - Clarify language on renewal rate and Jonathan to work on hypotheses. Jordyn to refine language.

Laureen

IN PROGRESS
528/2Rec 50.: Add line on appeals mechanismsJonathan

IN PROGRESS
516/24-25Check on whether the rate of abusive domains using Privacy/Proxy registrations is increasingSIDN/TU Delft

IN PROGRESS
516/24-25Include more detail on abuse in p/p registrationsSIDN/TU Delft

IN PROGRESS
516/24-25Public Comment follow-up
  • SubGroups to review recommendations and consolidate related recommendations and eliminate duplicative ones.
  • SubGroup to review wording to ensure that it's expressed in a manner so that the Board can adopt our recommendations Verbatim.
  • SubGroups to review recommendations to harmonize terms such as "should" "shall" "must" (refer to https://www.ietf.org/rfc/rfc2119.txt) and consider that as the SubGroups work to standardize terms throughout the report.
  • Clarify which group will implement the recommendations if Board approves (who is best to take this on during the implementation process)
  • SubGroups to review assigned recommendations and add details on rationale and success measures(and especially regarding data we recommend collecting).
SubGroups

IN PROGRESS
516/24-25Review slides from INTA survey and share follow up questions to relay back to Nielsen who commissioned that study.CCTRT

IN PROGRESS
516/24-25

Rec.1: Redefine the recommendation and its rationale and success measures. 

Jonathan

IN PROGRESS
516/24-25

Add more clarity on terms such as "Global South, Underserved Regions", align with terms used by other groups e.g. Subsequent Procedures Working Group.

Jonathan

IN PROGRESS
516/24-25

Parking Paper: Review the parking paper and look into the DNS Abuse Correlation with Parking.

Jordyn/Drew

IN PROGRESS
516/24-25

Schedule subgroups call as from the week after ICANN59 for a period of 4-5 weeks (Deadline August 1)  to review the public comments received and incorporate edits. Subgroup calls should last one hour and be extended if necessary.

CCTRT

OVERDUE
516/24-25

Review Team to publish for public comment only new sections to the draft report (DNS Abuse Study, INTA Survey...), edits following the first period of public comment will be incorporated in the final report before it is sent out the Board.

CCTRTSeptember 2017
IN PROGRESS

...