June 2011 - 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

WG: [council] GNSO Council resolutions - Singapore 22 June 2011
by KnobenW＠telekom.de June 23, 2011

June 23, 2011

FYI Kind regards Wolf-Ulrich ________________________________ Von: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] Im Auftrag von Glen de Saint Géry Gesendet: Mittwoch, 22. Juni 2011 13:25 An: Council GNSO Betreff: [council] GNSO Council resolutions - Singapore 22 June 2011 Dear All, Ahead of the official Council minutes, please find the resolutions passed by the GNSO Council today, 22 June 2011 in Singapore: Motion 1 on the Adoption of the IRTP Part B Final Report and Recommendations WHEREAS on 24 June 2009, the GNSO Council launched a Policy Development Process (PDP) on IRTP Part B addressing the following five charter questions: a. Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report (http://www.icann.org/announcements/hijacking-report-12jul05.pdf <http://www.icann.org/announcements/hijacking-report-12jul05.pdf> ); see also (http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm <http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm> ); b. Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact (AC). The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar; c. Whether special provisions are needed for a change of registrant when it occurs near the time of a change of registrar. The policy does not currently deal with change of registrant, which often figures in hijacking cases; d. Whether standards or best practices should be implemented regarding use of a Registrar Lock status (e.g. when it may/may not, should/should not be applied); e. Whether, and if so, how best to clarify denial reason #7: A domain name was already in 'lock status' provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status. WHEREAS this PDP has followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 30 May 2011; WHEREAS the IRTP Part B WG has reached full consensus on the recommendations in relation to each of the five issues outlined above; WHEREAS the GNSO Council has reviewed and discussed these recommendations. Resolved RESOLVED (A), the GNSO Council recommends to the ICANN Board of Directors: 1. Requiring Registrars to provide a Transfer Emergency Action Contact (TEAC). To this end the language of section 4 (Registrar Coordination) and Section 6 (Registry Requirements of the Inter-Registrar Transfer Policy should be updated as follows: Transfer Emergency Action Contact (Append to Section 4) Registrars will establish a Transfer Emergency Action Contact (TEAC) for urgent communications relating to transfers. The goal of the TEAC is to quickly establish a real-time conversation between registrars (in a language that both parties can understand) in an emergency. Further actions can then be taken towards a resolution, including initiating existing (or future) transfer dispute or undo processes. Communications to TEACs will be reserved for use by ICANN-Accredited Registrars, gTLD Registry Operators and ICANN Staff. The TEAC point of contact may be designated as a telephone number or some other real-time communication channel and will be recorded in, and protected by, the ICANN RADAR system. Communications to a TEAC must be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized loss of a domain. Messages sent via the TEAC communication channel must generate a non-automated response by a human representative of the gaining Registrar. The person or team responding must be capable and authorized to investigate and address urgent transfer issues. Responses are required within 4 hours of the initial request, although final resolution of the incident may take longer. The losing registrar will report failures to respond to a TEAC communication to ICANN Compliance and the registry operator. Failure to respond to a TEAC communication may result in a transfer-undo in accordance with Section 6 of this policy and may also result in further action by ICANN, up to and including non-renewal or termination of accreditation. Both parties will retain correspondence in written or electronic form of any TEAC communication and responses, and share copies of this documentation with ICANN and the registry operator upon request. This documentation will be retained in accordance with Section 3.4 of the Registrar Accreditation Agreement (RAA). Users of the TEAC communication channel should report non-responsive Registrars to ICANN. Additionally, ICANN may conduct periodic tests of the Registrar TEAC communication channel in situations and a manner deemed appropriate to ensure that registrars are indeed responding to TEAC messages. (Append to Section 6) 6 iv. Documentation provided by the Registrar of Record prior to transfer that the Gaining Registrar has not responded to a message via the TEAC within the timeframe specified in Section 4. In addition, update section 6 to reflect that the registry, in case of a transfer undo, will reverse the transfer and reset the registrar of record filed to its original state ('In such case, the transfer will be reversed and the Registrar of Record field reset to its original state'). (IRTP Part B Recommendation #1) 2. Modifying section 3 of the IRTP to require that the Registrar of Record/Losing Registrar be required to notify the Registered Name Holder/Registrant of the transfer out. The Registrar of Record has access to the contact information for the Registrant and could modify their systems to automatically send out the Standardized Form for Losing Registrars ("Confirmation FOA") to the Registrant. (IRTP Part B Recommendation #5) 3. Modifying Reason for Denial #6 as follows: Express objection to the transfer by the authorized Transfer Contact. Objection could take the form of specific request (either by paper or electronic means) by the authorized Transfer Contact to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the authorized Transfer Contact on an opt-in basis and upon request by the authorized Transfer Contact, the Registrar must remove the lock or provide a reasonably accessible method for the authorized Transfer Contact to remove the lock within five (5) calendar days. (IRTP Part B Recommendation #6) 4. Deleting denial reason #7 as a valid reason for denial under section 3 of the IRTP as it is technically not possible to initiate a transfer for a domain name that is locked, and hence cannot be denied, making this denial reason obsolete. (IRTP Part B Recommendation #9 - part 1) RESOLVED (B), the GNSO Council recommends the promotion by ALAC and other ICANN structures of the measures outlined in the recent report of the Security and Stability Advisory Committee on A Registrant's Guide to Protecting Domain Name Registration Accounts (SAC 044). In particular, the GNSO Council recommends that registrants consider the measures to protect domain registrar accounts against compromise and misuse described in SAC044, Section 5. These include practical measures that registrants can implement "in house", such as ways to protect account credentials and how to incorporate domain name registrations into employee or resource management programs typically found in medium and large businesses. It suggests ways that registrants can use renewal and change notifications from registrars as part of an early warning or alerting system for possible account compromise. The GNSO Council Chair will reach out to the ALAC and other ICANN structures to inform them of this recommendation and discuss how the GNSO may contribute to this promotion. (IRTP Part B Recommendation #2) Resolved (C), the GNSO Council acknowledges receipt of IRTP Part B Recommendation #7 and will consider this recommendation when it considers the Final Issue Report on the Current State of the UDRP. RESOLVED (D), prior to the consideration of approval of the recommendation which states: "denial reason #7 should be replaced by adding a new provision in a different section of the IRTP on when and how domains may be locked or unlocked", the GNSO Council requests ICANN Staff to provide a proposal for such a new provision, taking into account the IRTP Part B WG deliberations in relation to this issue (see IRTP Part B Final Report - (Recommendation #9 - part 2). Upon review of the proposal, the GNSO Council will consider whether to approve the recommendation. RESOLVED (E), prior to the consideration of approval of the recommendation regarding the standardizing and clarifying WHOIS status messages regarding Registrar Lock status, the GNSO Council requests ICANN staff to provide a proposal designed to ensure a technically feasible approach can be developed to meet this recommendation. Staff should take into account the IRTP Part B WG deliberations in relation to this issue (see IRTP Part B Final Report). (IRTP Part B Recommendation #8). The goal of these changes is to clarify why the Lock has been applied and how it can be changed. Upon review of the proposed plan, the GNSO Council will consider whether to approve the recommendation. Resolved (F), the GNSO Council will consider IRTP Part B Recommendation #3 concerning the request of an Issue Report on the requirement of 'thick' WHOIS for all incumbent gTLDs at its next meeting on 21 July. RESOLVED (G), the GNSO Council requests an Issue Report on IRTP Part C, which should include: - "Change of Control" function, including an investigation of how this function is currently achieved, if there are any applicable models in the country-code name space that can be used as a best practice for the gTLD space, and any associated security concerns. It should also include a review of locking procedures, as described in Reasons for Denial #8 and #9, with an aim to balance legitimate transfer activity and security. (IRTP Part B Recommendation #4) - Whether provisions on time-limiting Form Of Authentification (FOA)s should be implemented to avoid fraudulent transfers out. For example, if a Gaining Registrar sends and receives an FOA back from a transfer contact, but the name is locked, the registrar may hold the FOA pending adjustment to the domain name status, during which time the registrant or other registration information may have changed. - Whether the process could be streamlined by a requirement that registries use IANA IDs for registrars rather than proprietary IDs. MOTION 2. RE. REVISION OF THE GNSO COUNCIL OPERATING PROCEDURES RELATING TO PROXY VOTING Made by: Wolf-Ulrich Knoben Seconded by: Stéphane van Gelder WHEREAS, the GNSO Council recently identified areas for improvement in the GNSO Council Operating Procedures that would simplify and clarify the procedures relating to proxy voting; WHEREAS, the GNSO Council tasked the Operations Steering Committee (OSC) with completing a revision to improve the procedures relating to proxy voting; WHEREAS, the OSC submitted to the GNSO Council on 14 June 2011 recommended revisions http://gnso.icann.org/drafts/osc-recommended-revisions-proxy-voting-14jun11… <http://gnso.icann.org/drafts/osc-recommended-revisions-proxy-voting-14jun11…> to the GNSO Council Operating Procedures to simplify and clarify the procedures relating to proxy voting; NOW THEREFORE, BE IT: RESOLVED, that the GNSO Council acknowledges receipt of the recommended revisions submitted by the OSC and directs Staff produce a redlined revision of the GNSO Council Operating Procedures incorporating the recommended revisions and to post this document for twenty-one (21) days in the ICANN Public Comment Forum. RESOLVED FURTHER, that the GNSO Council shall take formal action on these recommendations, including potential modification, as soon as possible after the conclusion of the public comment period. Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

ASO Review
by alain.bidron＠orange-ftgroup.com June 22, 2011

June 22, 2011

As indicated yesterday during our ISPCP meeting, the ASO review is underway with an analysis made by an external consulting company. The initial report will be produced before the next meeting in Dakar. As a consequence if ISPCP wants to express its views on the ASO, it should be better done before our next physical meeting in Dakar. Herve Rannou from ITEMS international will be conducting the first part of the review. For those who are present here in Simgapore you can contact Herve at herve.rannou(a)items.fr Or Thomas Mackenzie at tmackenzie(a)items-int.eu and organize individual interviews with them. Regards Alain ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ********************************************************************************

1 0

FW: Commercial Stakeholder Group meeeting with the BOARD Tuesday, 21 June 2011 - 11:00-12:00
by Tony Holmes June 20, 2011

June 20, 2011

FYI -----Original Message----- From: Glen de Saint Géry [mailto:Glen@icann.org] Sent: 20 June 2011 11:51 To: Marilyn Cade ; Rosette, Kristina; Tony Holmes; J. Scott Evans; steve metalitz; 'Jaime Wagner - PowerSelf'; KnobenW(a)telekom.de; Benedetta BC Secretariat Cc: Gisella Gruber-White; Diane Schroeder; Glen de Saint Gery Subject: Commercial Stakeholder Group meeeting with the BOARD Tuesday, 21 June 2011 - 11:00-12:00 Dear Marilyn, Kristina, Tony, J.Scott, Steve, Jaime, Wolf-Ulrich, Please find the dial-in details for the Board /CSG meeting on Tuesday, 21 June from to 11:00am to 12:00 to be sent to your members who cannot attend the meeting physically. Please check the main schedule for the Adobe connect details: http://singapore41.icann.org/full-schedule Thank you very much. Kind regards, Glen Participant passcode: BCSG For security reasons, the passcode will be required to join the call. ____________________________________________________________________________ Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND Land Line: 106-33-203 0-800-9-14610 FINLAND Mobile: 09-106-33-203 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA 000-800-852-1268 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Restrictions may exist when accessing freephone/toll free numbers using a mobile telephone. ---------------------------- Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

CSG breakfast with the Alac
by Tony Holmes June 20, 2011

June 20, 2011

Dear ISPCP members If you plan to attend the CSG/ALAC breakfast meeting in Singapore on Tuesday morning, please confirm by replying to this email. Thanks Tony

5 4

Cocktail tomorrow
by Tony Holmes June 19, 2011

June 19, 2011

To all ISPCP members in Singapore Please note: The cocktails on Monday at 6:00pm with the Board is the Stamford Ballroom Foyer.

1 0

ISPCP sessions - Singapore
by Tony Holmes June 19, 2011

June 19, 2011

ISPCP members Please note the following schedule for ISPCP members in Singapore. Monday: 20 June 18.00 - 19.15 Cocktails with the BC and the ICANN Board (Venue to be announced). Tuesday: 21 June 08.00 - 09.30 Breakfast with the ALAC - SB Foyer 09.45 - 10.50 Commercial Stakeholder Group meeting - Padang Room 11.00 - 12.00 CSG/Board meeting - Board meeting Room 12.10 -13.00 Commercial Stakeholder Group meeting -Padang Room 14.00 - 15.00 CSG- WHOIS WG - Moor Room 15.00 - 17.00 ISPCP Constituency meeting - Bras Basah Room

1 0

WG: SINGAPORE Saturday 18 June remote participation & dial-in details
by KnobenW＠telekom.de June 17, 2011

June 17, 2011

FYI ________________________________ Von: owner-ntfy-gnso-council(a)icann.org [mailto:owner-ntfy-gnso-council@icann.org] Im Auftrag von Glen de Saint Géry Gesendet: Freitag, 17. Juni 2011 08:16 An: mail=ntfy-gnso-council(a)icann.org Betreff: SINGAPORE Saturday 18 June remote participation & dial-in details Dear All, Please find the dial - in and remote participation information for the GNSO Council working sessions on Saturday, 18 June 2011 in Singapore which starts at 09:00 Singapore time (01:00 UTC) 01:00 UTC : (for other places see: http://www.timeanddate.com/worldclock/fixedform.html <http://www.timeanddate.com/worldclock/fixedform.html> Remote participation : http://singapore41.icann.org/node/24435 <http://singapore41.icann.org/node/24435> Remote Participation - Low Bandwidth Audiocast: English <http://stream.icann.org/sophia-16-en.m3u> Chat Room: http://singapore41.icann.org/chat/sophia <http://singapore41.icann.org/chat/sophia> Remote Participation - High Bandwidth Audiocast: English <http://stream.icann.org/sophia-64-en.m3u> Virtual Meeting Room http://icann.adobeconnect.com/sin41-sophia <http://icann.adobeconnect.com/sin41-sophia> Dial-in information: Please note that the dial-in numbers below remain the same for all the GNSO related meetings in Singapore The pass code for each meeting changes as noted below: Saturday Draft AGENDA: 01:00 UTC / 09:00 - 10:00 - Pass code SCIA 02:00 UTC -10:00 - 10:30 - Pass code SCIB 02:30 UTC--10:30 - 11:15 - Pass code RAP 03:15 UTC -11:15 - 12:00 - Pass code BP 04:00 UTC- 12:00 - 13 :00 -Pass code MOTIONS 06:00 UTC- 14:00 - 14:45 - Pass code PEDNR 06:45 UTC- 14:45 - 15:15 - Pass code DSSA 07:15 UTC -15:15 - 16:15 - Pass code IRD 08 :15 UTC -16 :15- 17 :30- Pass code UDRP 09 :30 UTC- 17 :30- 19 :00 - Pass code BOARD Meeting Transcriptions will be available within approximately 48 hours after the meeting and will be posted on the GNSO Calendar page: http://gnso.icann.org/calendar/#jun Please find the draft Singapore GNSO related meeting schedule, http://icann.box.net/shared/0lhvskg216bm5oqixeyp <http://icann.box.net/shared/0lhvskg216bm5oqixeyp> also posted on pages: http://gnso.icann.org/ http://gnso.icann.org/calendar/#jun which should be read together with the main Singapore schedule http://singapore41.icann.org/full-schedule Please let me know if you require further information. Thank you. Kind regards Glen +33 6 21 79 24 54 ____________________________________________________________________________ Participant passcode: see above For security reasons, the passcode will be required to join the call. ____________________________________________________________________________ Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND Land Line: 106-33-203 0-800-9-14610 FINLAND Mobile: 09-106-33-203 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 06-800-12755 INDIA 000-800-852-1268 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY 39-02-3600-6007 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 MALAYSIA 1-800-81-3065 MEXICO 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 POLAND 00-800-1212572 PORTUGAL 8008-14052 RUSSIA 8-10-8002-0144011 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Restrictions may exist when accessing freephone/toll free numbers using a mobile telephone. ---------------------------- Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org <http://gnso.icann.org>

1 0

WG: [gnso-ppsc-pdp] Public comment period on PDP-WT Final Report
by KnobenW＠telekom.de June 10, 2011

June 10, 2011

________________________________ Von: owner-gnso-ppsc-pdp(a)icann.org [mailto:owner-gnso-ppsc-pdp@icann.org] Im Auftrag von Marika Konings Gesendet: Freitag, 10. Juni 2011 09:24 An: Gnso-ppsc-pdp(a)icann.org Betreff: [gnso-ppsc-pdp] Public comment period on PDP-WT Final Report Dear All, For your information, the GNSO Council resolved at its meeting yesterday in relation to the PDP-WT Final Report to 'commence a thirty (30) day public comment period'. The public comment forum is now open (see http://www.icann.org/en/announcements/announcement-2-09jun11-en.htm) and comments can be submitted until 9 July. As a reminder, the presentation of the PDP-WT Final Report to the GNSO Council is scheduled for Sunday 19 June from 14.45 - 15.30 (local time) in room Sophia. With best regards, Marika

1 0

GNSO Council meeting 09 June
by KnobenW＠telekom.de June 9, 2011

June 9, 2011

All: The following motions passed at the council meeting today: Motion 1. WHOIS Registrant Identification Study Motion May 2011: Made by Jonathan Robinson Seconded by: John Berard Whereas: In October 2007, the GNSO Council concluded that a comprehensive and objective understanding of key factual issues regarding the gTLD Whois system would benefit future GNSO policy development efforts (http://gnso.icann.org/resolutions/) On 4 March 2009, the GNSO Council requested Staff to conduct research on feasibility and cost estimates for selected Whois studies and report its findings to Council. (See Motion 3, http://gnso.icann.org/resolutions/#200903 <http://gnso.icann.org/resolutions/> ). On 23-Mar-2010, Staff presented a report on the feasibility and cost estimates for a Whois "Registrant Identification" Study, finding that the study would cost approximately $150,000 (USD) and take approximately one year to complete (http://gnso.icann.org/issues/whois/whois-studies-report-for-gnso-23mar1 0-en.pdf). This exploratory study would examine Whois data for a representative sample of gTLD domain names to classify the types of entities that register domains, including natural persons, various kinds of legal persons and Privacy and Proxy service providers. On 28 April 2011 the Council deferred consideration of the Whois Registrant Identification Study until the 9 June 2011 meeting and requested that any applicable motions in that regard be submitted not later than 1 June 2011. On 20 May 2011 a volunteer Whois studies group submitted to the GNSO Council revised Whois Registrant Identification Study Terms of Reference http://gnso.icann.org/issues/whois/tor-whois-registrant-id-studies-20may 11-en.pdf supporting Rationale http://gnso.icann.org/issues/whois/whois-registrant-id-study-rationale-2 0may11-en.pdf and Summary of Changes http://gnso.icann.org/issues/whois/summary-changes-whois-registrant-id-s tudy-tor-20may11-en.pdf Resolved; The Council requests that ICANN staff proceed with the Whois Registrant Identification Study as set forth in the revised Terms of Reference http://gnso.icann.org/issues/whois/tor-whois-registrant-id-studies-20may 11-en.pdf Further resolved, the Council asks staff to report back to the Council if the original estimate for the study of $150,000 USD is exceeded by greater than 20%. Further resolved, in recognition of the substantial amount of coordination needed to direct the research, that staff be given the discretion to manage this study serially or in parallel with the other Whois studies, with a goal of expediting completion of all of the studies as efficiently as possible. Motion 3: To Acknowledge the Receipt of the Policy Development Process Work Team Final Report and Initiate a Public Comment Period: Made by: Jeff Neuman Seconded by: Wolf-Ulrich Knoben WHEREAS, in October 2008, the GNSO Council established a framework (see GNSO Council Improvement Implementation Plan; (http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-impl ementation-plan-16oct08.pdf) for implementing the various GNSO Improvements identified and approved by the ICANN Board of Directors on 26 June 2008 (http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113182 <http://www.icann.org/en/minutes/resolutions-26jun08.htm> ) (http://www.icann.org/en/minutes/resolutions-26jun08.htm) WHEREAS, that framework included the formation, in January 2009, of two Steering Committees, the Operations Steering Committee (OSC) and the Policy Process Steering Committee (PPSC), to charter and coordinate the efforts of five community work teams in developing specific recommendations to implement the improvements; WHEREAS, the PPSC established two work teams, including the Policy Development Process Work Team (PDP-WT), which was chartered to develop a new policy development process that incorporates a working group approach and makes it more effective and responsive to ICANN's policy development needs; WHEREAS, the GNSO Council decided to terminate the PPSC on 28 April 2011 and instructed the PDP-WT to deliver its Final Report directly to the GNSO Council; WHEREAS, the PDP-WT submitted its Final Report, http://www.icann.org/en/announcements/announcement-31may11-en.htm, on 31 May 2011 to the GNSO Council; NOW THEREFORE, BE IT: RESOLVED that the GNSO Council acknowledges receipt of the PDP-WT Final Report as delivered by the PDP-WT and directs ICANN Staff to commence a thirty (30) day public comment period on this Final Report. RESOLVED FURTHER that the GNSO Council shall take action on the PDP-WT Final Report as soon as possible after the end of the public comment period. RESOLVED FURTHER that the GNSO Council recommends that a concise summary of the new Policy Development Process be drafted by ICANN Staff, following approval of the new PDP by the ICANN Board, in order to serve as a primer to the new Annex A of the ICANN Bylaws and PDP Manual for potential PDP WG members 2. Motion regarding the JAS milestone report Made by: Rafik Dammak Seconded by: Andrei Kolesnikov Amended by Jeff Neuman Whereas: The GNSO Council and ALAC established the Joint SO/AC Working Group (JASWG) on support for new gTLD applicants in April of 2010; and The Working Group released it Milestone Report posted for consideration by the Board, Chartering Organizations and at-large Community. This report documented the completion of work as defined in the orignal charter and requested an update to the Working Groups charter, and The GNSO and ALAC, separately, renewed the Working Groups charter with additional work item in February 2011, and The Joint SO/AC Working Group received and discussed the public comments, and The Joint SO/AC Working Group has completed the work as defined in its extended charter and published a second milestone report (https://community.icann.org/display/jaswg/JAS+Issues+and+Recommendation s#) on 8 May 2011 covering those chartered items (http://gnso.icann.org/resolutions/#20110113-1 <http://gnso.icann.org/resolutions/> ) entitled JAS Milestone Report. and The GNSO Council does not wish to delay the start of the new gTLD application process, and The GNSO Council does not wish to delay implementation of support programs for applicants from developing regions, RESOLVED: The GNSO Council thanks the members of the Joint SO/AC Working Group for its efforts and its dedication to completing the work on such a tight schedule, and The GNSO Council requests that the report be put out for community review as soon as possible, and The GNSO Council forwards the second JAS Milestone Report to the ICANN board for informational purposes to demonstrate the progress made by the JAS WG so that it may refer to that progress in their discussions with the GAC, The GNSO Council requests that ICANN staff begin assessing whether the recommendations are implementable, and The JAS Working Group continues working to deal with any issues that may arise in the upcoming review by the community, and That the JAS Working group publish their final report after this review process. Resolved further, that the GNSO Council instructs the GNSO Chair to communicate its decision to the ALAC Chair. Kind regards Wolf-Ulrich

1 0