FW: Data Accuracy Findings and recommendations [SEC=UNCLASSIFIED]
Hi Susan and all, Thanks again Susan for all your work on these recommendations. I have a couple of question and comments on recommendation 20. The recommendation currently reads: ICANN should also provide at least annual status reports on its progress towards achieving the goals set out by this WHOIS Review Team, published by the time the next WHOIS Review Team starts. This report should include tangible, reliable figures needed. My first question is on timing - and I've highlighted the relevant sequence of comments in yellow. I agree that the reports should be at least annual, but I'm interested in how this fits with the start of the next review team? Do we mean that at least one report should be published by then? I assume that that is feasible, timing wise (I apologise, but is it clear when the next WHOIS RT will start?) An alternative to tying report timing to the start of the next RT would be to give a start date - e.g. 'with the first report published one year, at the latest, after ICANN tables the implementation plan mentioned in rec 21?' I don't have a strong preference, but my thinking is that it may be useful to have a timeframe that it achievable and predictable, rather than something that isn't (or is less so). I'm also wonder if we could clarify the reference to 'tangible, reliable figures needed'. It may be that this was initially tied to the accuracy recommendations, and so it was clearer that we recommending the collection of reliable accuracy data - but given the broader focus of the recommendation now, we may need to revisit how we word this reference. So those are broad my questions/concerns. If others agree that these are worth exploring, I've had a first go at redrafting this recommendation below, to start the conversation: ICANN should provide at least annual written status reports on its progress towards implementing the recommendations of this WHOIS Review Team. The first of these reports should be published one year, at the latest, after ICANN tables the implementation plan mentioned in recommendation 21. Each of these reports should contain all relevant information, including all underlying facts, figures and analyses. Thanks again for your work on this, and I hope this helps. Cheers, Peter From: Susan Kawaguchi [mailto:susank@fb.com] Sent: Friday, 20 April 2012 4:56 AM To: Nettlefold, Peter; rt4-whois@icann.org Subject: Re: [Rt4-whois] Data Accuracy Findings and recommendations Hi Peter, Thanks for the thoughtful comments. I think I have incorporated all the changes in this document. I still need to update the draft report with the revised language. Let me know if you have any revisions or if I have missed anything. Susan Kawaguchi Domain Name Manager Facebook Legal Dept. Phone - 650 485-6064 From: "Nettlefold, Peter" <Peter.Nettlefold@dbcde.gov.au<mailto:Peter.Nettlefold@dbcde.gov.au>> Date: Thu, 19 Apr 2012 14:15:26 +1000 To: Susan Kawaguchi <susank@fb.com<mailto:susank@fb.com>>, "rt4-whois@icann.org<mailto:rt4-whois@icann.org>" <rt4-whois@icann.org<mailto:rt4-whois@icann.org>> Subject: RE: [Rt4-whois] Data Accuracy Findings and recommendations [SEC=UNCLASSIFIED] Hello again all, Thanks Susan for all your work on these recommendations and findings. Following today's teleconference, I thought it may be useful to circulate some comments on the draft. These reflect my comments made on the call, and I think summarise some of the positions we agreed. I hope this helps. Cheers, Peter From: rt4-whois-bounces@icann.org<mailto:rt4-whois-bounces@icann.org> [mailto:rt4-whois-bounces@icann.org] On Behalf Of Susan Kawaguchi Sent: Thursday, 19 April 2012 8:37 AM To: rt4-whois@icann.org<mailto:rt4-whois@icann.org> Subject: [Rt4-whois] Data Accuracy Findings and recommendations For review on our phone call. Susan Kawaguchi Domain Name Manager Facebook Legal Dept. Phone - 650 485-6064 ------------------------------------------------------------------------------- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Axway MailGate. MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit www.axway.com. ------------------------------------------------------------------------------- ________________________________ ------------------------------------------------------------------------------- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Axway MailGate. MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit www.axway.com. -------------------------------------------------------------------------------
participants (1)
-
Nettlefold, Peter