The Review of all Rights Protection Mechanisms (RPMs) Sub Team for Sunrise Data Review call is scheduled on Wednesday, 08 May 2019 at 18:00 UTC for 90 minutes. 

11:00 PDT, 14:00 EDT, 20:00 Paris CEST, 23:00 Karachi PKT, (Thursday) 03:00 Tokyo JST, (Thursday) 04:00 Melbourne AEST

For other times: https://tinyurl.com/y2v7uv66 

PROPOSED AGENDA

Proposed Agenda for Next Meeting

Here is a proposed agenda for the meeting on Wednesday, 8 May at 18:00 UTC:

  1. Review agenda/updates to Statements of Interest (SOIs)
  2. Development of Preliminary Recommendations:
    1. Discuss agreed Sunrise Charter Question 8
    2. Discuss agreed Sunrise Charter Question 9, in conjunction with Proposal #13
    3. (If time permits) Discuss agreed Sunrise Charter Question 10
  3. AOB

Resource

Summary Table (as of 16 April 2019) contains draft answers, preliminary recommendations, and links to the relevant individual proposals in relation to the Agreed Charter Questions:https://community.icann.org/download/attachments/102138618/%5BSunrise%20Summary%20Table%5D%20%2816%20April%202019%29.pdf?version=1&modificationDate=1555515624235&api=v2

  • Q1: pp.8-12
  • Q3: pp.15-20
  • Q4: pp.20-24
  • Q5(a): pp.24-26
  • Q6: pp.29-32
  • Q8: pp.34-36
  • Q9: pp.36-40
  • Q10: pp.40-42

Relevant to the Agreed Sunrise Charter Questions, multiple individual proposals were submitted. Staff analysis concluded the following Individual Proposals are more relevant to the Agreed Sunrise Charter Questions being reviewed by the Sub Team in the homework assignment:

 

Documents Wiki

Access the Documents wiki page and find the opening messages of all discussion threads, all versions of the summary table, and other working documents of the Sub Team:https://community.icann.org/x/_oIWBg  

BACKGROUND DOCUMENTS


RECORDINGS

Mp3

Zoom Recording

GNSO transcripts are located on the GNSO Calendar

PARTICIPATION

Attendance & Chat

Apologies: Maxim Alzoba, Petter Rindforth, Zak Muscovitch, Kristine Dorrain

Notes/ Action Items

Action Items:


  1. Sub Team members will review discussion threads on:
    1. Q1 (including Proposal #9): https://mm.icann.org/pipermail/gnso-rpm-sunrise/2019-April/000278.html
    2. Q3 (including Proposals #10 & #11): https://mm.icann.org/pipermail/gnso-rpm-sunrise/2019-April/000270.html
    3. Q4: https://mm.icann.org/pipermail/gnso-rpm-sunrise/2019-April/000271.html
    4. Q5(a): https://mm.icann.org/pipermail/gnso-rpm-sunrise/2019-April/000279.html
    5. Q6: http://mm.icann.org/pipermail/gnso-rpm-sunrise/2019-May/000286.html
  2. Question #8: Staff will revise the summary table.  Distinguish among the three elements: LRP, ALP, QLP to make sure they are not conflated.
  3. Staff will update the summary table based on the transcript/recording from the meeting.


Brief Notes:


  1. Updates to Statements of Interest (SOIs): No updates provided.


2. Development of Preliminary Recommendations:


a. Discuss agreed Sunrise Charter Question 8


-- There were some limited comments in the data, but don’t think they relate to the LRP.  Some issues around launch programs generally. 

-- Limited uptake of ALP.

-- People need to be clear what they are talking about.  Make sure this is clear in the discussion thread.

-- The responses said that some registries noted issues with the improved launch program, which is completely different.  

-- Staff will revise the summary table by reviewing the source material.


b. Discuss agreed Sunrise Charter Question 9, in conjunction with Proposal #13


-- Support for keeping the current rules.

-- Let mark holders decide where to register the mark in Sunrise.

-- Anecdote suggest problems -- scenarios where people gamed the system.

-- Solution penalizes the vast majority of genuine brand owners.

-- Don’t develop a system that goes further than it should.

-- Not every TLD is category-specific.


Proposal #13, Michael Karanicolas:

-- Where a top level domain is suggestive of a category of service, then the TM holder would have to prove use in that category of service.

-- The proposal doesn’t go far enough.

-- Could look at how SDRP could address the problem or some variant

  • No labels