Dear Review Team Members, Please find enclosed the pod content of your conference call held on 11 April. A preliminary report will be drafted. Thanks, Kind regards Alice -- WHOIS Policy Review Team Conference call – 11 April - 17:00 UTC AGENDA 1. Roll call & apologies 2. Adopt preliminary report (4 April) 3. Continuing walk through of ICANN Staff comments and queries on Recommendations, starting at Recommendation 12 (Denise) 4. Update from action item penholders https://community.icann.org/display/whoisreview/Action+Items+-+Spring+2012 and ongoing review of proposed new texts https://community.icann.org/display/whoisreviewprivate/Final+Report * Data Accuracy recommendations * Proxy & privacy recommendations * Recommendation 3 & 17 * Deaccreditation * IDN recommendations * Language on timeframes and implementation paths * Compliance recommendations 5. Next steps 6. A.O.B PARTICIPANTS Susan Kawaguchi, Kathy Kleiman, James Bladel, Lynn Goodendorf, Emily Taylor, Michael Yakushev, Seth Reiss, Sarmad Hussain ICANN STAFF Olof Nordling, Alice Jansen, Denise Michel APOLOGIES Peter Nettlefold, Bill Smith, Lutz Donnerhacke, Omar Kaminski, Sharon Lemon NOTES 1. Agenda amendments - A.O.B - WHOIS><ICANN Staff call + data validation (Larry Strickling letter) - Preliminary report adopted 2. Rec 5 - Susan - substantial failure - James avoid undeliverable. Full failure/substantial failure. Need clear language - contactable not clear enough. ET proposal to adopt substantial/full failure terms. James: redefine those terms. Body of report - (SK) + (JB) to insert references into draft footnotes. Proposal to have a references section. (SK) to circulate finding, agreed recommendations, add wordings. 4/3 paragraphs of findings. 3. Staff comments Rec 12: Voluntary discussions with proxy providers that ICANN has no contractual relationships with. Proxy services - big in RAA negotiations. Depending on how negotiations play out and on the Team's recommendations, this may require a GNSO consensus policy. Rec 13 Update on this topic next week. Need to explore various ways this could be implemented Rec 14 RAA negotiations would come into play. Rec 15 Staff is exploring a different range of ways this might be implemented and what the implications are. Rec 16 Currently RAA hold registrant holder responsible. In 2010 a draft - verify terms in RAA. Draft advisory submitted for comments. (KK) negotiations and studies going on: do we want to change our recommendations in light of that or shall we keep a high level approach? (JB) If group to reach out to Staff for RAA negotiations update, could open up to accusations then will need to recuse myself. (SR) should not respon to ongoing negotiations. Proposal to note that ongoing studies and negotiations (JB) advisoy draft not welcomed in Cartagena. (LG) come back to primary purpose: evaluate effectiveness WHOIS. We can certainly acknowledge activities and progress but at this point in time, the issue is there. Make sure that identified anything that hinders WHOIS. (DM) Not endorsing nor encouraging this advisory approach but will provide summary of comments so that Team can get a clearer picture of discussion at time. Rec 17 Feasible recommendation but investigations needed to implement recommendation. Connection to IRD WG. Staff noted issues that need to be explored: capacity planning, technical scaling, legal issues. (ET) enhancing current Internet service so no huge relocation or reassignment of data. Rec 18 - Rec 19 - Rec 20 Not ICANN's remit to determine encoding. That is fully within the role of IETF. addtional resources would be needed Rec 18 (SH) standards have not been adopted yet. Why and suggestions? (DM) serious concerns regarding compatability issue. Happy to provide additional material. Call with Steve Sheng to be scheduled (IDN subteam) Team thanks DM 4 Proxy/Privacy recommendations Progress ongoing. Subteam needs to review KK's comments. (ET) thanks for work. (KK)'s draft fleshes out findings and has references to where material is. Please circulate a final draft by Friday, 13 April. (LG) volunteered to help with drafting. (ET) - Clear difference between privacy and proxy services. Better use of time may be to go back to draft report. 5. Recommendation 3 Waiting for information from compliance team which will influence findings and recommendations. Historic figures from Staffing. Awaiting updated figures incl. on spendings. (DM): Stacy Burnette's slides in London included staffing chart that included full time staff. Discrepancy because of that. (SK) to propose some language. (ET) to integrate (PN), (KK) and (SK)'s comments. 6. Recommendation 17 (DM) highlight areas where unclear + implementation . (KK) to propose new iteration - if substantive edits, this rec will be back on action items list. 7 Deaccreditation Refer to slide from Maguy Serad and Bill's comment. Mention incentives when talking about penalties - holistic approach. (JB) to circulate language by next call 8 IDN recommendations Conversation with Steve Cheng and come up with draft Subteam will have a call with Steve Cheng and are working on clarifying draft recommendations and hope to share language. 9 Language on timeframes No follow-up action is required on this except make it more general. Language adopted and will be a separate recommendation at the end of data accuracy recommendation. 6 months from when Board received final report. List timing from AoC. 10. Compliance recommendations No progress. More work to be done. (AJ) to organize subteam call to discussion findings and recommendations within next week or so. 11. Next steps A.O.B Call with ICANN Staff scheduled for Monday, 16 April - 22:30 UTC Discussion on validation reverted to next call.