RE: [gnso-metrep-wg] GNSO MetRep - Charter - Draft Final
I share Tony's concern and have taken the liberty of marking up the latest version of the draft Charter for your review and consideration. As I previously commented during one of our calls, the 2013 RAA and the new gTLD Registry Agreement require contracted parties to collect abuse data and provide such data to ICANN upon request (see excerpts below). I hope my suggested edits make sense in light of these new (and onerous) obligations on contracted parties and the new (and powerful) compliance tools that were not previously available to ICANN. Kind regards, Pam ~~~ 2013 RAA 3.18 Registrar's Abuse Contact and Duty to Investigate Reports of Abuse. 3.18.1 Registrar shall maintain an abuse contact to receive reports of abuse involving Registered Names sponsored by Registrar, including reports of Illegal Activity. Registrar shall publish an email address to receive such reports on the home page of Registrar's website (or in another standardized place that may be designated by ICANN from time to time). Registrar shall take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse. 3.18.2 Registrar shall establish and maintain a dedicated abuse point of contact, including a dedicated email address and telephone number that is monitored 24 hours a day, seven days a week, to receive reports of Illegal Activity by law enforcement, consumer protection, quasi-governmental or other similar authorities designated from time to time by the national or territorial government of the jurisdiction in which the Registrar is established or maintains a physical office. Well-founded reports of Illegal Activity submitted to these contacts must be reviewed within 24 hours by an individual who is empowered by Registrar to take necessary and appropriate actions in response to the report. In responding to any such reports, Registrar will not be required to take any action in contravention of applicable law. 3.18.3 Registrar shall publish on its website a description of its procedures for the receipt, handling, and tracking of abuse reports. Registrar shall document its receipt of and response to all such reports. Registrar shall maintain the records related to such reports for the shorter of two (2) years or the longest period permitted by applicable law, and during such period, shall provide such records to ICANN upon reasonable notice. New gTLD Registry Agreement, Specification 11 (PUBLIC INTEREST COMMITMENTS) b. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. From: owner-gnso-metrep-wg@xxxxxxxxx [mailto:owner-gnso-metrep-wg@xxxxxxxxx] On Behalf Of Onorato, Tony Sent: Thursday, January 09, 2014 7:20 AM To: Mike O'Connor; Berry Cobb Cc: GNSO Metrics and Reporting Subject: RE: [gnso-metrep-wg] GNSO MetRep - Charter - Draft Final Mikey - I read over the draft again last night and a question occurred to me: we identify as Out of Scope "Problem-report tracking - transparent processes to collect, analyze and publish summaries of valid policy-violation reports, the root-causes of the problems and their final disposition". My concern is whether this suggests to the WG that aggregate numbers of UDRPs or URSs or other means by which abuse trends might be captured, are meant to be excluded from the universe of desirable metrics. If you/the team share this concern, perhaps it could be re-worded as "Problem-report tracking - transparent processes to collect, analyze and publish summaries of valid policy-violation reports and/or analyses of the root-causes of the problems and their final disposition, in contrast with underlying data concerning, e.g., the reported frequency of an abuse" Thanks very much for all your hard work on this. Best, Tony From: owner-gnso-metrep-wg@xxxxxxxxx [mailto:owner-gnso-metrep-wg@xxxxxxxxx] On Behalf Of Mike O'Connor Sent: Monday, January 06, 2014 3:44 PM To: Berry Cobb Cc: GNSO Metrics and Reporting Subject: Re: [gnso-metrep-wg] GNSO MetRep - Charter - Draft Final thanks Berry, sounds like a good plan to me. m On Jan 6, 2014, at 2:35 PM, Berry Cobb <mail@xxxxxxxxxxxxx> wrote: Mikey beat me to the New Year announcement! Welcome to 2014, all! I agree that by the close of this week and if no one objects, we forward the Charter and Draft Motion to the Council by the 13 Jan 2014, 23:59 UTC deadline. Because this is a motion for the Council to consider, Mikey you should submit it as the maker of the motion and ask for a second. I will send Mikey final versions of the report and motion on Friday morning. Please let me know if anyone has any questions. Thank you. B Berry Cobb Internet Corporation for Assigned Names & Numbers (ICANN) 720.839.5735 mail@xxxxxxxxxxxxx @berrycobb From: owner-gnso-metrep-wg@xxxxxxxxx [mailto:owner-gnso-metrep-wg@xxxxxxxxx] On Behalf Of Mike O'Connor Sent: Monday, January 06, 2014 13:17 To: GNSO Metrics and Reporting Subject: Fwd: [gnso-metrep-wg] GNSO MetRep - Charter - Draft Final hi all, welcome back from the holidays. just in time to take a last look at the draft charter. let's say that if we get to the end of the week without anybody raising an issue, we've got us a final draft - and that Berry can push the draft and the resolution along to Council? sound OK? Berry, i snuck my revised version of the motion into this pile... mikey Begin forwarded message: From: "Berry Cobb" <mail@xxxxxxxxxxxxx> Subject: [gnso-metrep-wg] GNSO MetRep - Charter - Draft Final Date: December 18, 2013 at 11:10:40 PM CST To: <gnso-metrep-wg@xxxxxxxxx> WG Members, Please find attached version v0.7 of our draft charter. I also included a clean version for easier review. Pending any other suggested changes, this version is what will be sent to the GNSO Council the week prior to the GNSO Documents and Motions deadline of 13 Jan 2014. Basically, we have until 8 Jan 2014 should we need to deliberate any changes. Please consider the work tasked to the future WG over the holidays and respond back to the list if you think we missed something. I also included a draft of the motion for the GNSO Council to approve the charter after they discuss it on the 23 Jan 2014 GNSO Council meeting. Should the Council approve the charter, we will conduct a call for volunteers for the Working Group. I suspect most members here intend to participate on the WG, but for those that may choose not participate, please let me know and I can have you removed from the mailing list. Lastly, I attached the high-level, proposed work plan once the call for volunteers concludes and the WG would tentatively begin. This is not a set schedule, but it should give you an idea of the WG's schedule over the coming months leading up to Singapore and subsequently London. I wish everyone a great holiday. Should you have any questions, please reach out to me. Thank you. B Berry Cobb Internet Corporation for Assigned Names & Numbers (ICANN) 720.839.5735 mail@xxxxxxxxxxxxx @berrycobb PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) Attachment:
GNSO_MetRep_WG_Charter_v0 7_clean+PL_9Jan2014.doc
|