Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

The Fake Renewal Notices Drafting Team teleconference meeting for Thursday 22 December 2011 at 19.30 UTC. (11:30 PDT, 14:30 EDT,  19:30 London, 20:30 CET  for other places see: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Fake+Renewal+Notices+Drafting+Team&iso=20111222T1930).
 
Adobe Connect URL: http://icann.adobeconnect.com/frndt/

For those of you using Adobe Connect for the first time, please find a short introduction video here: https://admin.adobe.acrobat.com/_a227210/participatemeeting/

Proposed Agenda:

  1. Roll Call / Statements of Interest
  2. Review approach and discussion of last week's meeting
  3. Continue development of Registrar Survey
  4. Confirm next steps and next meeting

For review:

What is the source of complaints you receive?
    Customers?
    Other Registrars?
Do you view the number of complaints as a significant burden/cost or a rather minor issue?
    Not very significant
    Significant burden
    Extremely burdensome
Is there a trend (up, down, steady)?
Are you seeing the same players or are there new ones entering -- is this proliferating?
Where are they coming from?
    An entity connected to ICANN?  How?
        Registrar
        Reseller
        Other
    What country are they coming from?
        Canada
        US
        UK
        Other
What is the mechanism you use to govern your resellers to prevent FRNs?
    By contract?
    By limiting capability through the API?
    Other?
    Combination of the above?
Representative examples of notices
Impact on your operation or customers?
    Cost
    Lost customers
    Other
What "holes" do you see in the new RAA?  Do you think it provides sufficient mechanisms to address FRNs?
What do feel is an appropriate role for ICANN in addressing this issue?