May 2012 - ispcp - lists.icann.org

Meeting Invitation / ISPCP Call / Monday 23 August at 1400 UTC
by Gisella Gruber-White Aug. 3, 2012

Aug. 3, 2012

Dear All, Please note that the next ISPCP call is scheduled for on Monday 23 August 2010 at 1400 UTC. Please find the dial-in details below. Thank you Kind regards Gisella ------------------------------------------------------------- Passcodes: Participant: 1385274 Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0489 AUSTRALIA ADELAIDE: 61-8-8121-4854 1-800-009-646 AUSTRALIA BRISBANE: 61-7-3102-0956 1-800-009-646 AUSTRALIA CANBERRA: 61-2-6100-1956 1-800-009-646 AUSTRALIA MELBOURNE: 61-3-9010-7725 1-800-009-646 AUSTRALIA PERTH: 61-8-9467-5235 1-800-009-646 AUSTRALIA SYDNEY: 61-2-8211-1378 1-800-009-646 AUSTRIA 43-1-92-80-004 0800-677-079 BELGIUM 32-2-401-7012 0800-4-9773 BRAZIL 0800-7610709 CHILE 1230-020-2471 CHINA* 86-400-810-4743 10800-712-1185 10800-120-1185 COLOMBIA 01800-9-156479 CZECH REPUBLIC 420-2-25-98-56-06 800-700-159 DENMARK 45-7014-0229 8088-5346 ESTONIA 800-011-1092 FINLAND Land Line: 106-33-156 0-800-1-12318 FINLAND Mobile: 09-106-33-156 0-800-1-12318 FRANCE LYON: 33-4-26-69-12-67 080-563-9648 FRANCE MARSEILLE: 33-4-86-06-00-67 080-563-9648 FRANCE PARIS: 33-1-70-75-25-91 080-563-9648 GERMANY 49-69-2222-20599 0800-101-2179 GREECE 30-80-1-100-0630 00800-12-5998 HONG KONG 852-2286-5624 800-968-767 HUNGARY 06-800-15230 INDIA 000-800-852-1209 INDONESIA 001-803-011-3492 IRELAND 353-1-431-9674 1800-992-641 ISRAEL 1-80-9214131 ITALY 39-02-3600-0507 800-985-846 JAPAN OSAKA: 81-6-7739-4755 00531-12-1423 JAPAN TOKYO: 81-3-5539-5146 00531-12-1423 LATVIA 8000-2933 LUXEMBOURG 352-27-000-1305 MALAYSIA 1-800-80-8114 MEXICO 001-866-761-6529 NETHERLANDS 31-20-713-3466 0800-020-3473 NEW ZEALAND 64-9-970-4633 0800-445-270 NORWAY 47-21-59-00-05 800-11825 PANAMA 011-001-800-5072096 PERU 0800-53765 PHILIPPINES 63-2-858-3702 POLAND 00-800-1210066 PORTUGAL 8008-12795 RUSSIA 8-10-8002-9763011 SINGAPORE 65-6883-9189 800-120-4141 SLOVAK REPUBLIC 421-2-322-422-07 SOUTH AFRICA 080-09-93386 SOUTH KOREA 82-2-6744-1044 00798-14800-6315 SPAIN 34-91-414-08-12 800-099-807 SWEDEN 46-8-506-92-118 0200-897-066 SWITZERLAND 41-44-580-4209 0800-000-663 TAIWAN 886-2-2795-7338 00801-137-557 THAILAND 001-800-1206-65077 UNITED KINGDOM BIRMINGHAM: 44-121-210-9007 0800-279-9198 UNITED KINGDOM GLASGOW: 44-141-202-3207 0800-279-9198 UNITED KINGDOM LEEDS: 44-113-301-2107 0800-279-9198 UNITED KINGDOM LONDON: 44-20-7098-0710 0800-279-9198 UNITED KINGDOM MANCHESTER: 44-161-601-1407 0800-279-9198 URUGUAY 000-413-598-3427 USA 1-210-795-0464 866-617-1530 VENEZUELA 0800-1-00-3717 Certain dialing restrictions can apply from specific countries. To ensure that your participants have the correct dialing procedures, please include this link in your invitation: https://e-meetings.verizonbusiness.com/audioconferencing/global_access.php

6 30

REMINDER/ ISPCP Call / 15 May 2012 at 1530 UTC
by Gisella Gruber June 10, 2012

June 10, 2012

Dear All, Please note that the next ISPCP call is scheduled on Tuesday 15 May 2012 at 1530 UTC. To check your local time: http://tinyurl.com/87a6k8b Please find the dial-in details below: Participant Passcode: Participant: 3429 # Dial-in numbers: http://www.adigo.com/icann/ Thank you. Kind regards, Gisella ----------------- Gisella Gruber GNSO Secretariat Staff Internet Corporation for Assigned Names and Numbers (ICANN) Email: gisella.gruber(a)icann.org<mailto:gisella.gruber@icann.org> Tel: +44 7545 334 360 Skype ID: gisella.gw

3 6

RAP "uniformity of reporting" question before Council
by Mike O'Connor May 30, 2012

May 30, 2012

hi all, one of my actions from the call today was to resend the little writeup i did about the Uniformity of Reporting recommendation that's coming up before Council this Friday. i've attached my (somewhat ragged, apologies). we ask that you speak up soon if you OPPOSE our supporting the recommendation to find a way to move forward with this initiative. here's a sketch of some talking points for Wolf during the Council meeting: -- Proposed next step -- develop ideas on how to move this "meta issue" forward, noting that it may fall outside the PDP process because the issue spans more than just the GNSO -- Proposed action -- add this issue to the Prague agenda and look for community input and ideas during that session -- with an eye to both the substance of the work and the process by which it is done -- Proposed position -- don't kill off a broadly supported recommendation simply because it falls outside familiar processes or is too much work. there are substantial benefits to be gained. here's a list, based on the WG report; Improving the "complaint reporting and notification" process for end-users and registrants and the "tracking and compliance" processes by ICANN will provide the following benefits: • Reduce errors and wasted time for all parties by providing “just in time” education and knowledge to people wanting to report problems • Improve quality by making it easier to submit a valid complaint • Reduce the cost of making (and responding to) erroneous complaints, for all parties • Improving understanding of the limits of ICANN policies and other options to pursue if the issue is not covered by policy • Improving the effectiveness of policy-compliance activities • Improving the data available for GNSO (working-group) and ICANN (advisory-group) policy-making • Improving the data available for compliance activities • Answering the question “which comes first, policy-process or definitive data describing the problem?” along with suggestions as to how data can be gathered when it hasn’t yet been included in the reporting process. - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

2 1

RAP "uniformity of reporting" question before Council - WITH the attachment
by Mike O'Connor May 30, 2012

May 30, 2012

hi all, oops - forgot the attachment... one of my actions from the call today was to resend the little writeup i did about the Uniformity of Reporting recommendation that's coming up before Council this Friday. i've attached my (somewhat ragged, apologies). we ask that you speak up soon if you OPPOSE our supporting the recommendation to find a way to move forward with this initiative. here's a sketch of some talking points for Wolf during the Council meeting: -- Proposed next step -- develop ideas on how to move this "meta issue" forward, noting that it may fall outside the PDP process because the issue spans more than just the GNSO -- Proposed action -- add this issue to the Prague agenda and look for community input and ideas during that session -- with an eye to both the substance of the work and the process by which it is done -- Proposed position -- don't kill off a broadly supported recommendation simply because it falls outside familiar processes or is too much work. there are substantial benefits to be gained. here's a list, based on the WG report; Improving the "complaint reporting and notification" process for end-users and registrants and the "tracking and compliance" processes by ICANN will provide the following benefits: • Reduce errors and wasted time for all parties by providing “just in time” education and knowledge to people wanting to report problems • Improve quality by making it easier to submit a valid complaint • Reduce the cost of making (and responding to) erroneous complaints, for all parties • Improving understanding of the limits of ICANN policies and other options to pursue if the issue is not covered by policy • Improving the effectiveness of policy-compliance activities • Improving the data available for GNSO (working-group) and ICANN (advisory-group) policy-making • Improving the data available for compliance activities • Answering the question “which comes first, policy-process or definitive data describing the problem?” along with suggestions as to how data can be gathered when it hasn’t yet been included in the reporting process. - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

1 0

WG: AW: Outreach -- Topic for GNSO in Prague?
by KnobenW＠telekom.de May 30, 2012

May 30, 2012

Re: AW: Outreach -- Topic for GNSO in Prague? Wolf-Ulrich it is scheduled for 12:00 to 12:30 pm on Saturday the 23rd. Julie

1 0

WG: [council] Fwd: Advance Notice for Prague Sessions
by KnobenW＠telekom.de May 30, 2012

May 30, 2012

FYI Best regards Wolf-Ulrich ________________________________ Von: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Im Auftrag von Stéphane Van Gelder Gesendet: Mittwoch, 30. Mai 2012 12:44 An: GNSO Council List Betreff: [council] Fwd: Advance Notice for Prague Sessions Councillors, As a heads-up, please see the message from Kurt below. Thanks. Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT Début du message réexpédié : De : Kurt Pritz <kurt.pritz(a)icann.org<mailto:kurt.pritz@icann.org>> Objet : Advance Notice for Prague Sessions Date : 30 mai 2012 03:25:35 HAEC As the time for the Prague meeting approaches, we continue to work on three initiatives that have been important to the community. These are: strategic planning, budgeting, and outreach. ICANN will soon be requesting your participation in community brainstorming and working sessions on these topics in Prague. Since you will be receiving these notices separately, and realizing there are so many sessions to attend, I wanted to give you some advance notice that they were coming so you could plan for them all. The Meeting Schedule is to be posted by 4 June, but the current draft schedule shows these community sessions as follows: (1) Strategic Planning Working Sessions on Tuesday and Wednesday from 9:00-11:00; (2) Outreach Initiative Working Session on Thursday morning at 8:00; and (3) Finance Working Session on Budget Process on Sunday from 16:30-18:00. We hope that through this advance notification, you will be able to work with your community to find opportunities for participation in each session listed above. Individual invitations to each of the sessions listed above will be sent shortly to this mailing list, providing more detailed information and agendas. Your participation is appreciated and we look forward to the interaction in these sessions. Best Regards, Kurt J. Pritz

1 0

WhoIs
by KnobenW＠telekom.de May 30, 2012

May 30, 2012

All, As we discussed some weeks ago, I'd like to introduce a "motion to address WhoIs access" to the council meeting on June 07 (see attached). I'll send it to the list after our call today. Mit freundlichen Grüßen Best regards Wolf-Ulrich

1 0

RAP Uniformity of Reporting recommendation is coming back to the Council
by Mike O'Connor May 29, 2012

May 29, 2012

hi all, i'd like to slip one more item in front of you, since the topic is likely to come up at the next Council meeting. word on the street is that now that the Council has the report back from Compliance, they're likely to tube the whole project with the standard hand-wringing over how there's such a workload problem. so here's a little rant that i just dashed off that tries to make the case on the other side. i would point out that this was a unanimous-consensus recommendation of the working-group, so at a minimum i'd like to see a darn nifty rationale back from the Council if they decide to kill it. here's my rant: could we stick a brief discussion of this topic on the agenda for the Wednesday call? thanks, mikey - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

2 1

review materials for our comment on the WHOIS review-team recommendations
by Mike O'Connor May 28, 2012

May 28, 2012

hi all, as i was starting to think about comments on the WHOIS Review Team, i realized that it would be really helpful to have a redline version that compared the reports before and after the first round of comments. i bugged Emily Taylor ((the Chair of the review team) and she made that happen (thanks Emily!!). a link to the redline is here: http://www.icann.org/en/about/aoc-review/whois/final-report-redline-11may12… here are links to the public comment box http://www.icann.org/en/news/public-comment/whois-rt-final-report-11may12-e… and announcement http://www.icann.org/en/news/announcements/announcement-11may12-en.htm Emily also shared some pointers with me as to what to pay attention to (thanks for these too, Emily): Focus on: - The executive summary. If you read that, you've pretty much got the lot. The first part is mostly unchanged, until we start to get to the Findings and Recommendations. The format of the findings and recommendations has been reworked, so that each recommendation is introduced by the relevant findings. The text of the findings is mostly new minted, but takes the same approach as the previous draft. The recommendations are mostly the same idea, with bits of clarification when it was clear that we'd confused people (!). - The substantively changed recommendations are: 1. strategic priority is fuller, and is now split out from compliance, which also has a fuller, standalone set of recommendations. 2. Privacy/proxy are now handled together, and we're no longer suggesting voluntary best practices for proxies. Instead we're asking for an accreditation process to be developed (it will need a PDP to be sure). 3. The look-up - the old recommendation 17 which had two alternatives - has been changed. I hope, simplified. We're now proposing operational amendments to Internic, which should be possible without policy development. In a nutshell, it's "make this less horrible for users". - Chapter 4 (Compliance) is completely rewritten - Appendix B (which is completely new) is my correspondence with staff about compliance staff numbers, spend etc... maybe we can take this up on our call this Wednesday. mikey - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

1 0

ICANN role and remit in security, stability and resiliency -- out for comment -- comments due by 16-June
by Mike O'Connor May 27, 2012

May 27, 2012

hi all, Patrick Jones just reminded me about this comment period. we may want to weigh in, no? http://www.icann.org/en/news/public-comment/draft-ssr-role-remit-17may12-en… i'd be interested in joining the gang of comment-drafters on this one. anybody else interested? mikey - - - - - - - - - phone 651-647-6109 fax 866-280-2356 web http://www.haven2.com handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)

3 3