- ispcp - lists.icann.org

WG: Draft of Weekend GNSO Council Schedule
by KnobenW＠telekom.de June 7, 2012

June 7, 2012

First draft FYI Best regards Wolf-Ulrich ________________________________ Von: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Im Auftrag von Neuman, Jeff Gesendet: Donnerstag, 7. Juni 2012 07:54 An: GNSO Council List Betreff: [council] Draft of Weekend GNSO Council Schedule All, Attached is a very preliminary draft of the proposed weekend schedule for the GNSO in Prague. I have to tell you that this process has been very frustrating in that I do not have confirmation from certain ICANN staff of their availability for some of these meetings despite repeated attempts to lock them down. Apparently there are other activities scheduled for the ICANN Board during the weekend that also ties up a significant amount of staff. That said, I have included slots for a meeting with the new ICANN CEO (which is a hope and not anything that has been confirmed) as well as a new TLD session where I have asked Kurt, John, Akram and Xavier to attend. This too has not been confirmed. There are still a couple of other things I need to fit in, but I cant do so until certain things are locked in with ICANN staff. We will discuss during the Council meeting later on today. Jeffrey J. Neuman Neustar, Inc. / Vice President, Business Affairs 46000 Center Oak Plaza, Sterling, VA 20166 Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: +1.703.738.7965 / jeff.neuman(a)neustar.biz<mailto:jeff.neuman@neustar.biz> / www.neustar.biz<http://www.neustar.biz/>

1 0

WG: ICANN News Alert -- New gTLD Batching Announcement
by KnobenW＠telekom.de June 7, 2012

June 7, 2012

That's going to make fun. I've heard from 6-digit offers ensuring applicants to get to the 1st batch... Best regards Wolf-Ulrich ________________________________ Von: ICANN News Alert [mailto:communications@icann.org] Gesendet: Donnerstag, 7. Juni 2012 04:36 An: Knoben, Wolf-Ulrich Betreff: ICANN News Alert -- New gTLD Batching Announcement [http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-06jun12-en.htm ________________________________ New gTLD Batching Announcement 6 June 2012 Given the large number of new generic top-level domain (gTLD) applications, we will divide and evaluate them in batches. The batching system is targeted to open at 00:01 UTC on 8 June 2012, and will close at 23:59 UTC on 28 June 2012. The target date for posting the batching order is 11 July 2012. The batching process will be used to determine which applications will be processed in the first batch, the second batch and so on. It will be done by: assignment of a timestamp, and the formation of batches. Timestamp assignments will be done using the TLD Application System (TAS). All applicants must use their TAS credentials to log in, read and accept the batching rules, indicate their batching preference, and select their target date and time. Once these steps are completed applicants should log back into TAS to hit the target time and generate a secondary timestamp. Users will have access to a testing feature to gauge the secondary timestamp system's response time. Batching formation considers an applicant's: (1) batching preference, (2) geographic region and secondary timestamp; and (3) contention among identical and "similar" applications. (1) Applicants stating a preference for "opting-out" will be placed last. (2) Geographic diversity is important in bringing more competition and choice into the domain name market. Applicants who opted in will be ranked within their geographic region (Africa, Asia-Pacific, Europe, Latin America/Caribbean and North America) by their secondary timestamp score. Then applications will be selected from each ICANN region using a "round robin" approach. This approach selects the best timestamp score from each region, one region at a time, on a rotating basis. If a region runs out of opted-in applications, the "round robin" continues across the remaining regions. This process continues until the batch is formed, with the opted-out applications last. (3) ICANN will then make preliminary determinations of contention sets based upon exact match. All applications in a single contention set are placed into the batch where the earliest application in the contention set is placed. Once the string similarity panel establishes complete contention sets, "similar" strings might be reassigned to an earlier batch. No applications will be demoted as a result of the promotion of others. This could result in a batch larger than 500. ICANN has taken care to provide a secure and stable platform for the batching system. Users will connect to the Citrix XenApp high-availability cluster and will then log into the batching system. Applicants will be required to agree to a set of Batching Rules, including an agreement that "ICANN reserves the right to delay an application to the last batch or to reject an application entirely if ICANN reasonably determines that the applicant abused the batching system or intentionally interfered with the performance of the system or any other applicant's use of the system." Along with this announcement ICANN is posting several additional resources to inform applicants about the batching process. These include a: set of frequently asked questions (FAQs), video demonstration, user guide, batching details and rules, and a batching basics fact sheet, which all can be found on the Batching information webpage at http://newgtlds.icann.org/en/applicants/tas/batching/. Information on security, infrastructure, and operations is also available in these materials. This message was sent to knobenw(a)telekom.de from: ICANN | 4676 Admiralty Way Suite 330 | Marina del Rey, CA 90292-6601 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=11118977&l=6333&s=WW8E&m=88…>

1 0

WG: Reminder: Pre-Prague ICANN Policy Update Webinar Invitation
by KnobenW＠telekom.de June 7, 2012

June 7, 2012

FYI Best regards Wolf-Ulrich ________________________________ Von: owner-liaison6c(a)gnso.icann.org [mailto:owner-liaison6c@gnso.icann.org] Im Auftrag von Glen de Saint Géry Gesendet: Mittwoch, 6. Juni 2012 14:45 An: liaison6c(a)gnso.icann.org Betreff: [liaison6c] Reminder: Pre-Prague ICANN Policy Update Webinar Invitation http://www.icann.org/en/news/announcements/announcement-2-16may12-en.htm REMINDER: Pre-Prague ICANN Policy Update Webinar Invitation In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org>) to receive the call details. Whether you plan to participate in the upcoming ICANN meeting in Prague remotely or in person, you're invited to an update on the background and current status of each major policy issue currently under discussion in ICANN. The ICANN Policy Staff will provide a briefing on: Thursday 14 June at 12.00 UTC (For other places see: http://tinyurl.com/cbj6eow) and Thursday 14 June at 19.00 UTC, (For other places see: http://tinyurl.com/cwx3mkt) summarizing policy issues across the different ICANN Supporting Organizations, namely the Generic Names Supporting Organization (GNSO), Country Code Names Supporting Organization (ccNSO) and Address Supporting Organization (ASO). Amongst other topics, updates will be provided on: · Inter-Registrar Transfer Policy · WHOIS · RAA Improvements · Consumer Choice, Competition and Innovation · Study Group on Use of Names for Countries and Territories · Framework of Interpretation Working Group for the delegation and re-delegation of ccTLDs · Joint DNS Security and Stability Analysis Working Group · Participation and Engagement activities in Prague In addition, staff will provide a briefing on the ALAC's activities related to current policy development issues of the Supporting Organizations. The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 90 minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to policy-staff(a)icann.org<mailto:policy-staff@icann.org>. In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org>) to receive the call details. Please indicate which call you would like to join, Thursday at 12.00 UTC (For other places see: http://tinyurl.com/cbj6eow) or Thursday at 19.00 UTC (For other places see: http://tinyurl.com/cwx3mkt) We will send you an e-mail reminder before the event with log-in and dial-in details. Please DO NOT RSVP to any other ICANN staff members e-mail address. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Fwd: ICANN News Alert -- Universal Acceptance of All TLDs - Prague Meeting
by Mike O'Connor June 7, 2012

June 7, 2012

i'm *way* behind on email, having pounded my hands to a pulp playing rock n'roll for the last 4 days, so apologies if this is a duplicate. but i was thinking we might want to take these people up on their offer to meet -- since we're going to be getting the customer-service calls when the new domains don't work. what do the rest of you think? mikey Begin forwarded message: > From: "ICANN News Alert" <communications(a)icann.org> > Date: May 31, 2012 11:19:49 PM CDT > To: <mike(a)haven2.com> > Subject: ICANN News Alert -- Universal Acceptance of All TLDs - Prague Meeting > > > News Alert > > http://www.icann.org/en/news/announcements/announcement-31may12-en.htm > > Universal Acceptance of All TLDs – Prague Meeting > 31 May 2012 > Universal acceptance of all top-level domains is an on-going initiative within ICANN. Our goal is to raise awareness among all Internet users about the diversity of domains on the Internet. In the 1980s and 1990s the number of top-level domains (TLDs) was small and they all shared the same basic format – two-character ASCII country code TLDs (ccTLDs) or a handful of three-character ASCII generic TLDs (gTLDs). This standard format led software vendors and web site developers to build their programs making specific assumptions about what was considered a valid TLD. As long as the software recognized the TLDs, people were able to use them. In the past decade newer ASCII gTLDs longer than three characters were introduced, plus new domains written in various non-Latin scripts — known as Internationalized domain names (IDNs) – were added. In the not so distant future we will be seeing even more TLDs, including IDN TLDs, thanks to the new gTLD program and IDN ccTLD Fast Track Process. This is why ICANN is committed to raising awareness among Internet software developers so they can build their software to ensure compatibility with all domains, rather than relying on outdated assumptions. > > During the ICANN meeting in Costa Rica we held a roundtable discussion on TLD Acceptance. A panel of experts shared their experiences with the issue. We heard many suggestions on how to better guide our efforts in raising awareness of this initiative from the experts as well as from the community. > > At the upcoming ICANN meeting in Prague we will not have a session specific to this topic. Instead we are reaching out to groups such as The At-Large Advisory Committee (ALAC), Country Code Names Supporting Organization (ccNSO) and others in order to schedule times to talk with them about the initiative and how they can help raise awareness. > > If you have any questions about this effort or would like to schedule a time during the Prague meeting to learn more about the initiative and how you can help raise awareness, please contact ICANN staff at tld-acceptance(a)icann.org. > > > > This message was sent to mike(a)haven2.com from: > ICANN | 4676 Admiralty Way Suite 330 | Marina del Rey, CA 90292-6601 > Email Marketing by > > Manage Your Subscription > - - - - - - - - - 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

CSG call with Bill Graham
by tony holmes June 6, 2012

June 6, 2012

All Just a quick note for your diaries, a conference call is being scheduled with Bill Graham our GNSO Board member on 13th June at 14.00 UTC. Details for the call will follow later. Tony

1 0

heads up -- the Hilton is double-booked
by Mike O'Connor June 5, 2012

June 5, 2012

hi all, the ICANN social group is buzzing this weekend. many (maybe all) of us who were booked into the venue Hilton in Prague have received notifications that we have been relocated to a different hotel for our stay in Prague. details (except for the emails that we received) are a little thin right now. my suggestion is to remain calm and wait to see what develops. but at the same time i would suggest you check your spam folder if you're booked at the Hilton and you have *not* seen the notification. it seems like many if not all attendees are being relocated. 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 5

IRTP -- can i get a little slot on our agenda in Prague?
by Mike O'Connor June 5, 2012

June 5, 2012

hi all, i'm on an IRTP call and wanted to see if i could get a little slot on our agenda to talk you through it. 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

Info on the Hilton
by tony holmes June 5, 2012

June 5, 2012

Following my message below please let me know by return email if you have been affected by the situation at the Hilton. The CSG are compiling a combined spread sheet to help ascertain the number of people impacted. Thanks Tony -----Original Message----- From: tony holmes [mailto:tonyarholmes@btinternet.com] Sent: 05 June 2012 08:14 To: 'Mike O'Connor'; 'ispcp(a)icann.org' Subject: RE: [ispcp] heads up -- the Hilton is double-booked Mikey Thanks for flagging this to the Constituency. I'm also one of those impacted but agree with your advice. Tony -----Original Message----- From: owner-ispcp(a)gnso.icann.org [mailto:owner-ispcp@gnso.icann.org] On Behalf Of Mike O'Connor Sent: 04 June 2012 13:09 To: ispcp(a)icann.org Subject: [ispcp] heads up -- the Hilton is double-booked hi all, the ICANN social group is buzzing this weekend. many (maybe all) of us who were booked into the venue Hilton in Prague have received notifications that we have been relocated to a different hotel for our stay in Prague. details (except for the emails that we received) are a little thin right now. my suggestion is to remain calm and wait to see what develops. but at the same time i would suggest you check your spam folder if you're booked at the Hilton and you have *not* seen the notification. it seems like many if not all attendees are being relocated. 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

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