Versions Compared

Key

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

...

MtgDateActionAction OwnerDue DateAction CompleteStatus
#74

 

Review team to review latest version of the final report, and submit edits/comment/objections/concerns by 28 August – 23:59 UTC

Review Team

IN PROGRESS
#74

 

Rec. 12: Jordyn/Laureen to add in rationale/related findings reference to “safety & security of users’ personal and sensitive information”, and circulate final version on Monday 27 August at the latest, for inclusion in the final report.

Jordyn/Laureen

IN PROGRESS
#74

 

Updated rec. 15 to be sent out to the review team on Monday 27 August, for discussion on plenary call #75.Drew/David/Jordyn

IN PROGRESS
#74

 

Rec. 15, 17: Drew/David to combine recommendations, assess whether priority of recommendation should be changed to Prerequisite, add language on DADRP in details section of recommendation, and submit updated version to Jordyn for his review before Friday 23:59 UTC. Laureen to submit an “objective” updated version to Jordyn.

Drew/David/Jordyn

IN PROGRESS
#73

 

Recommendation 13,14:
Add language about removing disincentives in addition to creating incentives
Jordyn

IN PROGRESS
#73

 

Consolidated Recommendation 11 13 15 33:
Find and update other sections of the report referring to the registrant  survey
Jordyn

IN PROGRESS
#73

 

Substitution analysis
- remove "are" in "these new strings are represent competition"
- replace word "cannibalizing"
- Complement (vs compliment)
Jonathan

IN PROGRESS
#72

 

Board letter: Once recommendations are finalized, Jonathan will scrub the timing related information (priority of recommendations) and prescriptive tone in recommendations.

Jonathan

IN PROGRESS
#62

 

Rec. 14 (assigned to David Taylor): Rewriting it to include removal of barriers to diversity (i.e. more niche TLDs or other business models?) to incentivize it rather than encouraging a particular business model.

David/Jordyn

IN PROGRESS
#62

 

  • Updates to Final Report:
    • Executive Summary to include a section on conclusions about the program (Jonathan)
    • Final numbering of recommendations: Restart with clear numbering and digestible way of reporting recommendations. Add a paragraph under the public comment section in the appendix “review process” describing which recommendations were consolidated based on the input received from comments.
    • Recommendation summary: add a column with level of consensus.
    • Finish consolidation exercise, circle back to staff for a cost analysis of the new/consolidated recommendations, CCTRT to determine whether each recommendation is worth/not the cost, and if it’s not then delete.
    • Review Team to identify any sections in the draft report that need to be updated based on public comments received, and all to compare public comment sheet to apply changes.
CCTRT

IN PROGRESS
#52

 

Final Report: 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

...