RE: [gnso-rap-dt] revised RAPWG Final Report draft
- To: <gnso-rap-dt@xxxxxxxxx>
- Subject: RE: [gnso-rap-dt] revised RAPWG Final Report draft
- From: "Greg Aaron" <gaaron@xxxxxxxxxxxx>
- Date: Thu, 20 May 2010 09:38:40 -0400
Please confirm. I think this is the latest version and should be included in
the report:"The RAPWG recommends the GNSO monitor for Cross-TLD Registration
Scam abuse in the gTLD space and co-ordinate research with the community to
determine the nature and extent of the problem. The WG believes this issue
warrants review but notes there is not enough data at this time to warrant
an Issues Report or PDP." I think I pulled the wrong version from my notes
last night. Thanks to Marika for bringing this up.
From: Greg Aaron [mailto:gaaron@xxxxxxxxxxxx]
Sent: Thursday, May 20, 2010 12:59 AM
Subject: [gnso-rap-dt] revised RAPWG Final Report draft
This revised draft (attached) features:
. the revision of the cybersquatting definition
. the addition of the gripe site and reverse hijacking material to
the cybersquatting background section
. the tweaked Fake Renewal Notice recommendation as per Berry
. the Cross-TLD Registration Scam section.
. 9.11: Conclusions, Recommendations, & Next Steps section. I have
drafted as no other drafts were posted.
. Removed references to the Interim Report, fixed typos, added notes
about WIPO's comments, etc., all red-lined for your reference.
Please let us know as soon as possible if anything is incorrect. The hard
deadline for edits to the paper is this Friday, May 21st, at 20:00 UTC.
Marika: Section 11 is the "Conclusions, Recommendations, & Next Steps"
section. Should the WG's Recommendations go here, or should they remain in
section 2.9? (It does not make sense to list them in both places.) In
Section 11 should we include the Recommendations in order of level of
support received? All thoughts appreciated.
Marika: last page needs a link to the attendance sheet.
Thanks. I am going to bed now.
Director, Key Account Management and Domain Security
The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify
us immediately by replying to the message and deleting it from your