Content Comparison

Rec 13, 15, 33: Jordyn to consolidate registrant survey recommendations.

Substitution analysis paper:

• • Jordyn to work on additional language based on recent shared figures (attached)
  • ICANN org to filter open TLDs from concatenation spreadsheets and share with subteam
  • Jordyn to confirm whether it should discussed on next subteam or plenay call

Jordyn

ICANN Org

Jordyn

Rec 11, 13, 15 ,33: Jordyn and Laureen to draft consolidated recommendation, and to include it for discussion on next plenary call agenda

Rec 9:

• • Waudo to update recommendation 9 to reflect public comments received. Jordyn to provide input on this.
  • Updated version to be included on next plenary call agenda

Rec 5:

• • Based on Kaili's previous suggestion, Jordyn to cite 0.3% defensive registration and for details link it to section 4.3.
  • Updated version to be included on next plenary call agenda

Waudo to write a text on how defensive registrations were "not useful and a sunk cost" (in reply to INTA's public comment on rec.9), Jordyn to find and add a footnote for one or more statements from the community who raised concern that the "new gtld program would break the internet, and trademark holders."

ICANN org to liaise with Tech Services about generating TLD concatenation spreadsheets. Jordyn to write up analysis of spreadsheet data when complete.

ICANN org to address Jordyn's request on data on competition for generic vs. specific domain names.

Include the Substitution Analysis and Recommendation 5 for discussion on the plenary call.

Rec 11: Megan to review recommendation and update rationale

"frustrate": Jordyn to revise recommendations language based on Waudo's suggestion to replace "frustrate"

Rec 13, 15, 33: Jordyn to consolidate registrant survey recommendations.

Rec 7-8, 9: Consolidation to be submitted on plenary call

Rec 2, 3, 4, 6 : Jordyn to update rationale

Rec 11: Megan to review recommendation and update rationale

Rec 10: Jordyn to update details and success measures

Rec. 12: Dejan to update Details & Success Measures, To: field: change ICANN Org with GNSO 

Changes to findings: Public comment review process to be discussed on leadership meeting.  

Jordyn to provide Waudo with minor edits on his updated recommendation.

Complete the analysis of Rec. 9

Parking paper to be discussed on tomorrow's plenary call

.NET increased prices / Parking paper: Share revised version

Rec 2-3: Review the supporting text in the body of the report to make sure it's consistent with the revised recommendation.

Rec 9: Waudo to review recommendation and submit edits.

Rec. 10 & 40: Jordyn to follow up with David.

Rec. 11: Follow up with ICANN Org on previous plenary call discussion

Rec. 12: Review the supporting text in the body of the report to make sure it's consistent with the revised recommendation.

Rec. 7-8: Dejan to add reference to LAC Study in recommendation 7

Rec 9: Waudo to review recommendation and submit edits.

.NET increased prices / Parking paper: Share revised version

ICANN org to share previous work made on price caps, and confirm whether there was a mechanism for registries to increase price caps that CCTRT didn’t use.

Send follow-up email to obtain perspective on whether language on contractual obligations and policy development needed. 

Send analysis of public comment for assigned recs 

- Rec 1: Jonathan to rewrite the recommendation and circulate with the subgroup before next call.

- Rec 2-3: Jordyn to rewrite the two recommendations based on feedback received from RySG

Jonathan

Jordyn

All to review papers/recommendations and propose revisions (based on ICANN59 ftof meeting action items) before the next competition sub group call:

- Rec 1: Jonathan
- Rec 2, 3, 4, 5: Jordyn
- Rec 6: Megan
- Rec 7: Dejan
- Rec 8: Dejan
- Rec 9: Megan
- Rec 10: Jordyn
- Rec 11: Megan
- Rec 12: Dejan

- Jordyn to reach out to Megan on updating recommendations.

Jordyn, Jonathan,

Stan

Produce a template for new vs legacy gTLDs markets 

Coordinate on getting request to Sedo or GoDaddy on "Compare pricing vs. single-string ROs and multi-string ROs"

Work with staff on defining the policies that should be researched, as well as what TLDs to include in sample

Discuss how to get data from Zooknic. Reach out to NTLD stats and enquire whether feasible and could speak to group on next call

Enquire if analysis of data on what SLDs are registered in what domains is feasible

Use NTLD site to identify trends and make initial hypothesis; use ICANN data sources to confirm / refine data

Send email to Jordyn for any suggested data elements or suggestions on how to structure data or make changes directly in g-doc

Add a question on comparing registry's intended audience with their current customers or business practices

Working model for data analysis - address requests individually