April 2012 - Rt4-whois - lists.icann.org

Action items list - updated
by Alice Jansen April 20, 2012

April 20, 2012

Dear Review Team Members, Please find enclosed an updated version of your action items list. Note that this is also available at: https://community.icann.org/display/whoisreview/Action+Items+-+Spring+2012 Thanks, Kind regards Alice Action Items - Spring 2012 * Revive call schedule (calls to take place on Wednesdays once a week; first call to take place on Wed, 28 March) – Alice [https://community.icann.org/images/icons/emoticons/check.gif] * Review and submit language of recs 5-9 (Data Accuracy) - Susan [https://community.icann.org/images/icons/emoticons/check.gif] * Susan to circulate findings (3/4 paragraphs), agreed recommendations and add wordings (+ define the substantial/full failure terms) [https://community.icann.org/images/icons/emoticons/check.gif] * Susan and James to add footnotes references * Susan to delete recommendation 7 and to move it to overarching recommendation 21 (20 with renumbering), to circulate draft to Team for comments - by 25 April * Note: timeline discussion now component of this discussion * Review comments submitted to the Team and Denise's recommendation tracking document [https://community.icann.org/images/icons/emoticons/check.gif] * Propose alternative language for Proxy and Privacy recommendations - James + Susan + Peter + Seth + Lynn ; [https://community.icann.org/images/icons/emoticons/check.gif] * Subteam to review comments submitted and to circulate a draft - by 25 April * Peter to submit comments in writing - by 19 April [https://community.icann.org/images/icons/emoticons/check.gif] * Kathy to circulate language to transcribe discussion held during call - by 19 April * Subteam to comment and finalize - by 24 April * Subteam to work on language of last paragraph (findings) - by 25 April * Subteam to go back to transcripts (Dakar) regarding rights/responsibilities discussions * Hold the pen on rec. 3 strategic priority -- Emily ; [https://community.icann.org/images/icons/emoticons/check.gif] * Emily to integrate comments received by next call (note: overlap with Compliance Subteam) * Susan to put forward some language on senior position - by 25 April * Denise to circulate draft advisory 2010 and material (recording, notes etc) of Cartagena discussion on this subject matter [https://community.icann.org/images/icons/emoticons/check.gif] * Find text on accreditation-- Kathy ; + Hierarchy of enforcement - James [https://community.icann.org/images/icons/emoticons/check.gif] * James to circulate language by 25 April (incentives><penalties) * Kathy to finalize and circulate * Work on language of rec. 17 Emily; [https://community.icann.org/images/icons/emoticons/check.gif] AGREEMENT REACHED * [https://community.icann.org/images/icons/emoticons/warning.gif] Kathy to circulate iterations - if substantive, back on action items list by 25 April * Review language of recs. on IDNs -- Sarmad + Kathy + Wilfried + Michael * IDN subteam to hold a call with Steve Sheng (Staff to schedule it [https://community.icann.org/images/icons/emoticons/check.gif] ) * Subteam to share language by 25 April * Review your chapters and send redline to Seth + Omar + Alice - by 25 April * Review body of text in light of comments and integrate changes suggested/required by Members-- Seth + Omar * Draft some language on timeframes and implementation paths in light of the AoC - Susan + Lynn [https://community.icann.org/images/icons/emoticons/check.gif] AGREEMENT * Susan to add agreed language to to data accuracy recommendation * Respond to Staff's comments for Community's information - All * Strengthen compliance recommendations and add justification to proposal - Peter + Emily + Bill * Team to take on discussion about recommendation 3 - Strategic priority * Alice to organize a subteam call in progress * All Members should submit their views and comments by next call * Data Validation: James and Peter to draft language by next call + to determine where this fits in the report * Emily to make a decision on timeline of final report [https://community.icann.org/images/icons/emoticons/check.gif] -- Alice Jansen Assistant, Organizational Reviews 6 Rond Point Schuman, Bt.5 B-1040 Brussels Belgium Direct dial: +32 2 234 78 64 Mobile: +32 4 73 31 76 56 Skype: alice_jansen_icann

1 0

FW: Data Accuracy Findings and recommendations [SEC=UNCLASSIFIED]
by Nettlefold, Peter April 20, 2012

April 20, 2012

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(a)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(a)dbcde.gov.au<mailto:Peter.Nettlefold@dbcde.gov.au>> Date: Thu, 19 Apr 2012 14:15:26 +1000 To: Susan Kawaguchi <susank(a)fb.com<mailto:susank@fb.com>>, "rt4-whois(a)icann.org<mailto:rt4-whois@icann.org>" <rt4-whois(a)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(a)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(a)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. -------------------------------------------------------------------------------

1 0

FYI - FW: REVISED motion to delay the 'thick' Whois Policy Development Process
by Denise Michel April 19, 2012

April 19, 2012

Dear Team, FYI - please see Liz Gasster's note below regarding the GNSO Council's vote to delay the thick Whois PDP until the end of the year. Regards, Denise Denise Michel ICANN Advisor to the President & CEO denise.michel(a)icann.org +1.408.429.3072 mobile +1.310.578.8632 direct ---------- Forwarded message ---------- From: Liz Gasster <liz.gasster(a)icann.org> Date: Thu, Apr 19, 2012 at 2:34 PM Subject: FW: REVISED motion to delay the 'thick' Whois Policy Development Process To: Denise Michel <denise.michel(a)icann.org> Hi Denise,**** ** ** The WHOIS Review Team may be interested in the following resolution that the GNSO Council passed at its meeting last Thursday. The GNSO Council voted to delay the start of a PDP on the issue of “thick” WHOIS until the first meeting following 30 November, 2012. Note the following “Whereas” clause which speaks to the delay: “taking into account the current workload of the GNSO community, the GNSO Council voiced support for a delay in the start of the PDP until both ICANN staff and GNSO resources are available to deal with this”.**** ** ** To be clear, the transcript will reflect that ICANN staff resources would have been made available had the Council opted to proceed.**** ** ** Best regards, Liz**** ** ** *From:* owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] *On Behalf Of *Glen de Saint Géry *Sent:* Thursday, April 12, 2012 10:51 AM *To:* council(a)gnso.icann.org *Subject:* [council] REVISED motion to delay the 'thick' Whois Policy Development Process **** ** ** ** ** Dear All,**** ** ** Apologies, below is the correct amended motion to delay the ‘thick’ Whois Policy Development Process that the Council voted on and which carried unanimously by voice vote.**** ** ** *Motion to delay the ‘thick’ Whois Policy Development Process * ** ** Whereas the GNSO Council requested an Issue Report on ‘thick’ Whois at its meeting on 22 September 2011 (see http://gnso.icann.org/resolutions/#201109);**** ** ** Whereas a Preliminary Issue Report on ‘thick’ Whois was prepared by staff and posted on 21 November 2011 for public comment (see http://www.icann.org/en/announcements/announcement-2-21nov11-en.htm);**** ** ** Whereas a Final Issue Report on ‘thick’ Whois was published on 2 February 2012 (see http://gnso.icann.org/issues/whois/final-report-thick-whois-02feb12-en.pdf)… ** ** Whereas the Final Issue Report recommends that the GNSO Council proceed with a Policy Development Process limited to consideration of the issues discussed in this report, and the General Counsel of ICANN has indicated the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO;**** ** ** Whereas the GNSO Council initiated a Policy Development Process at its meeting of 14 March 2012 (see http://gnso.icann.org/resolutions/#20120314-1);**** ** ** Whereas at its wrap up session on 15 March, taking into account the current workload of the GNSO community, the GNSO Council voiced support for a delay in the start of the PDP until both ICANN staff and GNSO resources are available to deal with this. **** ** ** THEREFORE BE IT:**** Resolved, the next step (creating a drafting team to develop a charter) of the ‘thick’ Whois PDP will be delayed until the first GNSO Council meeting after 30 November 2012.**** ** ** A recording of the meeting is available at:**** http://audio.icann.org/gnso/gnso-council-20120412-en.mp3 Apologies for the confusion.**** ** ** Thank you. **** ** ** Kind regards,**** ** ** Glen**** ** ** ** ** Glen de Saint Géry**** GNSO Secretariat**** gnso.secretariat(a)gnso.icann.org**** http://gnso.icann.org**** ** **

1 0

Data Accuracy Findings and recommendations
by Susan Kawaguchi April 19, 2012

April 19, 2012

For review on our phone call. Susan Kawaguchi Domain Name Manager Facebook Legal Dept. Phone - 650 485-6064

2 2

No extension to deadline
by Emily Taylor April 19, 2012

April 19, 2012

Hi all Thank you for a tremendous amount of work on the drafts. I have looked through the various documents, and read the note pod, and I think we are on track with progress. Noticed an aside at the end of the note pod, speculating whether we would have to go into May, and saying 'Emily to decide'. I thought it would help all if I let you know as soon as possible that I dont think we will need to extend our work, or that we should hope to do so. We have nearly 2 full weeks left, and are well on with the bits of text. There is a small editing job on the whole report, but I think this only needs a quick read through for sense, and to take in an textual comments received in the public comment. We need to work out the readability of our new findings -> recommendations structure, but this should not take long. So, let's keep our foot on the pedal for another couple of weeks, and then deliver our report when we said we would. One caveat is that there is still outstanding information from ICANN but so long as we receive that with a day or two to spare, we will be fine to incorporate it. If not, we just mention that we asked and didnt get the information. Kind regards Emily -- * * 76 Temple Road, Oxford OX4 2EZ UK t: +44 (0)1865 582 811 • m: +44 (0)7540 049 322 emily(a)emilytaylor.eu *www.etlaw.co.uk* Emily Taylor Consultancy Limited is a company registered in England and Wales No. 7630471. VAT No. 114487713.

1 0

Note Pod Content - 18 April call
by Alice Jansen April 19, 2012

April 19, 2012

Dear Review Team Members, Please find enclosed the note pod content of your conference call held on 18 April. Staff will draft a preliminary report for your consideration. Thanks, Kind regards Alice From: Alice Jansen <alice.jansen(a)icann.org<mailto:alice.jansen@icann.org>> Reply-To: Alice Jansen <alice.jansen(a)icann.org<mailto:alice.jansen@icann.org>> To: Alice Jansen <alice.jansen(a)icann.org<mailto:alice.jansen@icann.org>> Subject: Adobe Connect - Note Pod Content from WHOIS-Review WHOIS Policy Review Team - I8 April - 23:00 UTC AGENDA 1. Roll call & apologies 2. Agenda & Preliminary report (11 April) 3. Data validation: should this topic be added to our findings/preamble 4. Review proposed language & action items penholders report * Compliance * Proxy/Privacy * Data Accuracy * Recommendation 3 * Deaccreditation * IDNs 5. Discuss general revisions to chapters and final report timeline 6. A.O.B (scheduling issues) PARTICIPANTS Lutz Donnerhacke, Lynn Goodendorf, Kathy Kleiman, James Bladel, Peter Nettlefold, Omar Kaminski, Susan Kawaguchi, Seth Reiss ICANN STAFF Alice Jansen, Denise Michel APOLOGIES Sarmad Hussain, Emily Taylor, Wilfried Woeber, Michael Yakushev, Bill Smith, Olof Nordling NOTES 1. Prel report adopted 2. Data validation - (JB) this subject was discussed in London. Would have to rebuild amount of work ongoing in Community (PDP, RAA) need to be cautious (LG) appropriate to consider having a couple of lines to encourage data validation techniques as a way to achieve accuracy goals. (JB) as ongoing, think we had agreed to leave a roadmap to next RT. (PN) Not sure where this would fit in Data accuracy. Would be useful to acknowledge that things going on in the Community. (KK) state that numerous mechanisms but went for low-hanging fruit? (JB) might confuse community. Be consistent, restate definitions. (LG) How would validation/authentication techniques be used rather than getting involved in implementation details. (JB) emphasize accuracy goal not mention the path taken to get there. PENHOLDERS - (JB) - (PN) Would should this additional piece go? Exec. summary? Body of text? Recs? (KK) make sure it can be found in different parts of the report. Up to subteam to put proposal forward 3) Compliance recommendations (PN) Mostly prepared by (ET). Public discussion about compliance in Costa Rica + enquired about Compliance figures. Compliance clearly related to WHOIS landscape. Strategic priority also included in the compliance recommendations. How much do we pull them apart to make them clear? Each issue to be given an identity. (KK) Liaison with IETF? (PN) still need to discuss points. Please send in your views. Team should review Compliance recommendations and submit comments to subteam. 4) Strategic priority - Compliance subteam to take this on. SK position: CEO or Board committee - Team went back to Costa Rica discussion. (JB) Board-level Committee tasked with implementing whatever comes out of this group. Starting-point ATRT. This group would overseen WHOIS. (SK) Should be for all WHOIS issue not only compliance recommendations. If the Board issues the mandate, there would be more movement within ICANN Staff. (PN) - Idea of CEO and Board Committee good situation - to keep issues disentangled, call for independent report to advise Board on benchmarking, best practivces etc. More of an organizational question. (SK) volunteered to draft some language. 5) Proxy/Privacy Recommendations (JB) Reference to 3.7.7.3 - important component not contained in paragraph. Wrongful use. Collision with something that is currently in the RAA. (SK) this was not caught on in the comments (JB) The way written in our report - it preserves liability. (PN) Done to deal with uncertainty created by RAA. Comments in response to discussion paper brought our attention to this question of who is responsible. Discussion in Dakar responsibility with Registry Name Holder. Go back to Dakar transcripts. (KK) to send out a version on Thurs, 19 April to reflect that. discussion. Subteam o work on the language of last paragraph. (PN) comments on findings - dot points are repetitive. Positive and negative should be together followed by a conclusion. (PN) to submit comments in writing Privacy discussion:. (PN) Is there a right to privacy (LG) In Europe, privacy is a human right. Word right has connotations which could mean different things and cause unecessary disagreement with recommendations. Would prefer if could avoid using that word. (JB) ICANN not governement - cannot support, establish, disminish right that people don't have under jurisdiction they live in. E.G. domain name transfer. Number of contexts where word right starts to confuse proces rather clarify it. Reference to Registrants' rights and responsibilities document published by ICANN. Need to find a way to establish expectations for privacy. (LG) Data protection aspects of people who believe they have been harmed by fraudulent Domain names. Rights of people using the internet. In violent agreement James - just need to find wording to present the problem. (PN) to draft on Tursday, 19 April for subteam comments to get ball moving. 5) Data Accuracy Recommendations (SK) not created language per say but shortened things. Findings are for revision. On rec 7, initially recommended that add language on timeline, should we lose rec 7 as is under accuracy and add to recommendation 21? (PN) thanks for work. Middle paragraph of findings bits where go directly to scope. In terms of readability, might be worth drawing points out. Regulator term - not sure if better wording? Might want to focus on that. (SK) in the report (PN) discussed this with GAC. Something we might want to be mindful of. (SK) Oversight? (PN) which ICANN regulates and oversees? (JB) alternatives: administer/manage/coordinate... (PN) findings: heard in public sessions. make it clear that widely communicated to the RT. Rec 6 - language of unreachable WHOIS - update? Annual status on all goals. Rec 7? (SK) Rec 7 - WHOIS overall. If renumber recommendation - moving it to a different section. No pointing toward data accuracy or whois in general. (KK) merge 6+7 into one rec? (PN) getting rid of rec 7 and create an overarching 21 rec. (SK) Separate rec about plan at the end. All related recs. at the end to work on this and to send it to the group. 6) Deaccreditation (JB) and (KK) to reiterate that. 7) IDNs Meeting tomorrow with Steve Sheng and Francisco Arias. Michael has circulated revisions to subteam and this has been emailed to Staff to see if that fixes issues. 8) Chapters & Timeline (PN) No revision to chapters (KK) Add agenda item to next call. Do you think can get all language ready by next week? No objection. Emily to decide. Looks like might be going into May. Amendments to chapters and recs by next call. 9) A.O.B

1 0

p/p
by Kathy Kleiman April 18, 2012

April 18, 2012

for discussion on the call taking place now.... --

1 0

adobe room
by Alice Jansen April 18, 2012

April 18, 2012

Please join the Adobe room: http://icann.adobeconnect.com/whois-review/ -- Alice Jansen Assistant, Organizational Reviews 6 Rond Point Schuman, Bt.5 B-1040 Brussels Belgium Direct dial: +32 2 234 78 64 Mobile: +32 4 73 31 76 56 Skype: alice_jansen_icann

1 0

Please review - compliance language
by Alice Jansen April 18, 2012

April 18, 2012

Dear Review Team Members, Please review the attached document in anticipation of today's call. This is language on Compliance. Note that this material is also available at: https://community.icann.org/display/whoisreviewprivate/Final+Report Thanks, Kind regards Alice

2 2

REMINDER - Call today @ 23:00 UTC
by Alice Jansen April 18, 2012

April 18, 2012

Dear Review Team Members, Your next conference call is scheduled for: **Wednesday, 18 April 2012** 23:00 UTC Please check your local time at: http://timeanddate.com/worldclock/fixedtime.html?msg=WHOIS+Weekly+calls+-+W… PASSWORD: 27318 followed by # Agenda: https://community.icann.org/display/whoisreview/Call+28+-+18+April+2012 Adobe room: http://icann.adobeconnect.com/whois-review/ Audio-cast (silent observers): http://stream.icann.org:8000/whois.m3u Dial-in numbers: Please find below a table which encapsulates dial-in numbers for your countries of residence. Should you be traveling, please refer to the full list which is available at: http://www.adigo.com/icann/ Australia 1 800 009 820 1 800 036 775 Sydney T +61 290372962 Melbourne T +61 399996500 Brisbane T +61 731777546 Austria L - 0 800 295 858 M - 0 800 295 138 T - +43 720 882 638 Belgium L - 0800 79210 M – 0800 79218 T - +32 78 480 286 Brazil L - 0800 891 1597 M - 0800 891 1598 T - +55 613 717 2040 Canada 1 800 550 6865 T - +1 213 233 3193 France 0800 90 25 56 T - +33 170618347 Germany L - 0800 1016 120 G - M 0800 1016 124 Russia 8 10 8002 535 3011 T - +7 499 650 7835 United Kingdom 0800 032 6646 T - +44 207 099 0867 United States 1 800 550 6865 T - +1 213 233 3193 T – local toll number ; M – mobile preferred number ; L – landline preferred number Please do not hesitate to contact me should you require a dial-out for this call. Thank you, Very best regards Alice Alice E. Jansen -------------------------- ICANN Assistant, Organizational & Affirmation Reviews alice.jansen(a)icann.org<mailto:alice.jansen@icann.org> Direct Dial: +32.2.234.78.64 Mobile: +32.4.73.31.76.56 Office Fax: +32.2.234.78.48 Skype: alice_jansen_icann -------------------------- 6, Rond Point Schuman B-1040 Brussels, Belgium -- Alice Jansen Assistant, Organizational Reviews 6 Rond Point Schuman, Bt.5 B-1040 Brussels Belgium Direct dial: +32 2 234 78 64 Mobile: +32 4 73 31 76 56 Skype: alice_jansen_icann

1 0