- Bc-gnso - lists.icann.org

BC discussion of "final" Applicant guidebook, Thursday 18th November 2010 at 1500 UTC
by Steve DelBianco Nov. 18, 2010

Nov. 18, 2010

This is a reminder for the 18-Nov BC member call to discuss the new Applicant Guidebook. As an organizational tool, we prepared an outline and reference links (attached). Dial-in data appears below. Call is at 15:00 UTC (10am USA eastern time) on Thursday 18-Nov-2010 Module Assignments and agenda for the call: Module 1: Introduction to New gTLD Application Process and Fees. Berry Cobb, Ron Andruff Module 2: Evaluation Procedures. Greg Rattray, Jon Nevett, Adam Palmer Module 3: Dispute Resolution. John Berard, Mikey O’Connor Module 4: String Contention. Ron Andruff, Chris Chaplow Module 5: Transition to Delegation and registry agreement Fred Fellman and Elisa Cooper,Berry Cobb, Jon Nevett, Greg Rattray, Zahid Jamil ---- Dial-in Please find below dial in details for the Members call at Thursday 18th November 2010 at 1500 UTC. (10.00 AM Eastern and 16.00 Europe) Passcodes/Pin codes: Participant passcode: BC For security reasons, the passcode will be required to join the call. Country / Toll Numbers / 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 INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 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 SAUDI ARABIA 800-8-110087 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.

3 3

Cartagena Hotel List
by Chris Chaplow Nov. 17, 2010

Nov. 17, 2010

Dear BC Members, We are preparing the Annual BC members contact and will shortly send a draft for update. In the meantime if you are attending the Meeting in Cartagena please send an email to info(a)bizconst.org (not this public list) with your Cartagena Hotel name, date of arrival and departure, and cell phone number. This optional list will be circulated only amongst the members attending. The meetings(a)bizconst.org email list is also being morphed from a Washington meeting list to the Cartagena list but I will cover that in another email. Best regards, Chris Chaplow Managing Director Andalucía.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: <mailto:chris@andalucia.com> chris(a)andaluciaws.com Web: <http://www.andalucia.com/> www.andaluciaws.com

1 0

link -- the new applicant guidebook has been posted
by Mike O'Connor Nov. 17, 2010

Nov. 17, 2010

hi all, the new Guidebook is posted at; http://www.icann.org/en/announcements/announcement-2-12nov10-en.htm all us sub-section reviewers can get our pencils out. :-) by the way, is there a place i can go look up our *previous* comments about Module 3? that's the one i've volunteered to help review. it's easy to see the things that been changed, but i'd like to look at what we *wanted* changed to see what things didn't get in. 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

SSAC report 044 -- protecting domain-registrant accounts
by Mike O'Connor Nov. 16, 2010

Nov. 16, 2010

hi all, SSAC just published a pretty interesting report. here's the teaser: This is a report by the Security and Stability Advisory Committee (SSAC) describing measures a domain name registrant should consider to protect domain name registration accounts against misuse. In the report, SSAC recommends measures that organizations or individuals should consider to protect their domain name registration accounts and domain names against a range of threats that may result in temporary or permanent loss of domain name registrations and the possible, consequent loss or disruption of Internet presence. and here's the link -- http://www.icann.org/en/committees/security/sac044.pdf pretty darn nifty report 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

Announcement of agenda/program for Cartagena and notice regarding elections for Council Chair/V.Chair
by Marilyn Cade Nov. 16, 2010

Nov. 16, 2010

ANNOUNCEMENT OF GNSO SCHEDULE AND FULL ICANN PROGRAM: VISIT THE LINKS BELOW. GNSO SCHEDULE: THIS LINK WILL PROVIDE YOU WITH ONLY THE GNSO SPECIFIC EVENTS BUT DOES INCLUDE IMPORTANT INFORMATION FOR YOU TO PLAN YOUR SAT/SUN AND TUESDAY http://gnso.icann.org/meetings/gnso-draft-agenda-cartagena-26oct10-en.pdf FULL PROGRAM -- SATURDAY THROUGH FRIDAY http://cartagena39.icann.org/full-schedule DEAR BC MEMBERS Now that ICANN has finalized and posted the GNSO and full Cartagena program, the officers and councilors will be able to provide an annotated set of recommendations and requests for volunteers to cover different sessions during Cartagena meeting. In the meantime, three important announcements to stay tuned for: House Meetings/Council Chair and V.Chair elections: The Council Chair elections are proceeding. Further to the input of the BC members on last week's call, the BC members support Stephane and do not support Olga as Chair of the Council. The Councilors vote on the Council chair should reflect the BC members input and discussion about their concerns about one candidate and support for another. Zahid was on the call for the full discussion by members. V.Chair discussions are continuing, as noted in the briefing email provided by the chair, earlier. A call will be held later this week or early next week with the CSG leadership and councilors from the CSG to discuss the V.Chair candidates and strategy. There will be a House meeting on Sat/Sun, which will focus on election processes for the Board seat. A separate House meeting will be held when there is critical mass of officers and councilors from both SGs. BC members will be kept up to date on the developments of V.Chair candidates within the SG. During Cartagena, there will be a House discussion on this matter. At this point, it is not clear if the election will take place on site for V.Chair. If so, the CSG BC reps will ensure an update to BC Members. On V. Chair, the procedures are yet to be agreed, and that is work in progress with the CSG leadership and NCSG leadership. Meetings and Contact details during Cartagena: please send an updated version of name, date of arrival/departure, hotel, and onsite mobile, along with your priority topics to info(a)bizconst.org Donna will prepare a spreadsheet which only attendees will have, and which will allow us to reach each other. I am aware that a couple of folks have changed hotels so am asking that you just send to Donna. Once we get past the prep meeting, proposed for Dec. 1, at 10 a.m. EDT, we will no longer post any details of events or scheduling to the bc lists, but will start using meetings(a)bizconst.org for communications. Policy discussions and notices about decisions or any remote participation consultations will be posted to the usual list, so that you will not miss the policy or issues discussions, but won't be receiving any notices that are for logistical coordination. IF you have not signed up for meetings(a)bizconst.org, please email Chris Chaplow to be added. AGENDA PLANNING/SCHEDULE TIPS: Members Discussion of Cartagena meeting: Dec. 1: 10 a.m.EDT/Bridge to be sent out separately. In the meantime, I have provided some quick planning thoughts for your consideration: TUESDAY BREAKFAST: BC members in attendance are automatically included. IF you are bringing a business guest/potential member, you must let me know so I can get them included. Usual time: 8-10:00 a.m. I have added one potential agenda item: the importance of ICANN partnering with the CSG community regarding its role in the larger eco system of Internet /strengthening and improving ICANN's involvement with business. IPC AND ISPCP will contribute additional topic. CSG Agenda is being finalized: I have proposed RAA/WHOIS and MAPO as CSG topics. IPC and ISPCP will contribute topics. We may have guest speakers from staff. The meeting is being coordinated by IPC. Lunch: BC ONLY: The BC will provide a working lunch with a guest speaker. I have invited the new CTO, for a get acquainted session. This will not be a substantive discussion but a true get acquainted session. You will be asked to talk about yourself, your company/organization, and why ICANN matters to you/your membership. There will be other opportunities to do the issues thing. We are trying to first establish the kind of positive relationship we had with Doug Brent with Akrim. You must rsvp for that lunch. I have reserved lunch for 20 at this point. If he cannot attend, I'll schedule a different senior ICANN staff person or two for that same purpose. The lunch is quick, and will be members only. BC Agenda for afternoon meeting: If you have a topic you haven't contributed, please email to Chris Chaplow and Marilyn Cade. We will hear from the SSR working team among other topics of relevance to broader BC and ICANN, as well as GNSO policy and GNSO issues. A heavy percent of time will be policy /issues oriented. We will do some /as necessary administrative updates if essential. Remote access will be provided. The sessions will be transcribed and posted. Wednesday: BC Charter meeting : 1 hour: Members Only. Remote participation will be provided. This session will be a brief walk through of some improvements and clarification sections to the BC Charter. Draft language will be delivered 'just in time'. [sorry, but that is life inside the BC right now]. We will discuss topical areas and potential language. We will not approve language in this discussion period. This session is proceeded by a NomComm lunch, so you will all find lunch with the NomComm, which will include our own Mike Roberts and Chris Martin, our two appointed reps to the NomComm. The BC will also have a 20 minute slot with our reps on Tuesday, and it is during that time slot that you will have the opportunity to offer your guidance to your BC reps on the NomComm. Chris and Mike are returning to the NC, and so will be quite familiar with the NC challenges. Note; we haven't had as much interaction with the NC as we would have liked in the past, and I am pleased that ICANN has provided reasonable funding so that the reps can travel to the ICANN meeting to be involved in the community during the meeting, not just after the meeting. Recognition of past officers: Stay tuned for the time slot for this recognition of past/retiring officers/councilors. Please review the agenda and program. We will be providing more information on the program once the ExComm meets on Friday to discuss the priorities. And, we will be looking for volunteers to cover meetings when there are multiple events at the same time. Marilyn Cade BC Chair

1 0

Registry Code of Conduct in new gTLD Agreement
by Steve DelBianco Nov. 16, 2010

Nov. 16, 2010

Here's a follow-up to our policy discussion on last Thursday's call, in preparation for our Guidebook discussion this Thursday 18-Nov ( 10am eastern US time, dial-in to follow ) Now that vertical integration is permitted, we noted it was critical to have specific restrictions in the Code of Conduct section of the new Registry agreement. As Jon Nevett noted on the call, ICANN created a Code of Conduct as part of its 2001 agreement with NeuLevel to run the .biz gTLD. http://www.icann.org/en/tlds/agreements/biz/registry-agmt-appi-27apr01.htm There were several restrictions in the .biz code of conduct worth noting: 1. NeuLevel will not, directly or indirectly, show any preference or provide any special consideration to any registry operator or Registrars in the .biz Registry versus any other registry operator or Registrars 3. NeuLevel shall not in any way attempt to warehouse domain names. In addition, Registry Operator shall not attempt to register domain names in its own right, except for names designated for operational purposes in compliance with Subsection 3.6 of the Registry Agreement. In its Monthly Report to ICANN, NeuLevel shall include a list of all names designated for operational purposes. 5. Neither NeuLevel nor related entities shall have access to user data or proprietary information of a Registrar, except as necessary for registry management and operations. 6. NeuLevel will ensure that no user data or proprietary information from any Registrar is disclosed to related entities, except as necessary for registry management and operations. 7. Confidential information about NeuLevel's business services will not be shared with employees of any DNS registry operator or ICANN-Accredited Registrars, except (i) as necessary for registry management and operations or (ii) if such information is made available to all registry operator employees and Registrars on same terms and conditions. For comparison purposes, the new Registry agreement issued on Friday includes a new Code of Conduct (Specification 9). http://icann.org/en/topics/new-gtlds/draft-agreement-specs-clean-12nov10-en… SPECIFICATION 9* Registry Operator Code of Conduct [*Note: This draft Registry Operator Code of Conduct has been added to the form New gTLD Agreement pursuant to the ICANN Board resolution of 5 November 2010 regarding the question of cross-ownership of gTLD registries and ICANN-accredited registrars. ICANN encourages community input on the types of conduct that should be prohibited and/or mandated given the potential for cross-ownership of domain-name distribution channels.] 1. Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity (each, a “Registry Related Party”) to: a. directly or indirectly show any preference or provide any special consideration to any registrar; b. register domain names in its own right, except for names registered through an ICANN accredited registrar that are reasonably necessary for the management, operations and purpose of the TLD; c. have access to user data or proprietary information of a registrar utilized by or Affiliated with Registry Operator, except as necessary for management and operations of the TLD; or d. register names in the TLD or sub-domains of the TLD based upon a search of available names by any consumer (i.e., "front-running"). [Steve’s Note: Should we restrict other ways to do front-running, aside from Whois searches? The Registry sees nearly 100% of traffic for non-existing records. That means a Registry can see all non-registered domain names that are typed (or mis-tyed) by users, indicating potential names to acquire for themselves ] 2. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar reseller services, Registry Operator will, or will cause such Registry Related Party to, maintain separate books of accounts with respect to its registrar or registrar-reseller operations. 3. Registry Operator will, and will cause each Registry Related Party to, ensure that no user data or proprietary information from any registrar is disclosed to Registry Operator or any Registry Related Party, except as necessary for the management and operations of the TLD. 4. Registry Operator will not disclose confidential registry data or confidential information about its registry services or operations to any employee of any DNS services provider, except as necessary for the management and operations of the TLD. 5. Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to [an address to be provided by ICANN]. (ICANN may specify in the future that the reports be delivered by other reasonable means.) 6. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct.

1 0

RE: [bc-gnso] Member call Thursday
by john＠crediblecontext.com Nov. 15, 2010

Nov. 15, 2010

1 0

Member call Thursday
by Chris Chaplow Nov. 15, 2010

Nov. 15, 2010

Dear Members There is a BC members call primarily to discus response to Proposed Final New gTLD Applicant Guidebook on Thursday 18th November at 10.00 Eastern time, (15.00 UTC and 16.00 Europe) the following times: Dial-in details and agenda to follow. Reference http://www.icann.org/en/announcements/announcement-2-12nov10-en.htm best regards, Chris Chaplow Managing Director Andalucía.com S.L. Avenida del Carmen 9 Ed. Puertosol, Puerto Deportivo 1ª Planta, Oficina 30 Estepona, 29680 Malaga, Spain Tel: + (34) 952 897 865 Fax: + (34) 952 897 874 E-mail: <mailto:chris@andalucia.com> chris(a)andaluciaws.com Web: <http://www.andalucia.com/> www.andaluciaws.com

2 2

by Zahid Jamil Nov. 13, 2010

Nov. 13, 2010

Dear Members, I have been informed by the ICANN Travel Staff that there are considerable challenges being faced facilitating visas for several nationalities. This stems from: The fact that Colombia does not have missions (especially those that process visa applications) in several developing countries The fact that the Colombian Foreign Office has not been forthcoming in streamlining visa applications in coordination with ICANN. This means the following for me: 1. In all its wisdom the Colombian Govt. has designated its INDIAN embassy for receiving Pakistani applications. Hence I first have to apply for an INDIAN visa (as a Pakistani). As a Pakistani it is extremely difficult to apply for Indian visa. The Indian Govt. may not be too convinced by my purpose for travelling to India and it is possible that visa is refused. In any case it can take up to 2 months to apply for an Indian visa. Then if I get an Indian visa I will need to physically fly to India and apply at the Colombian Embassy there and wait around until my visa is issued. Then return to Pakistan. Then fly to Colombia. 2. To attempt to apply in the UK, for instance, there is every possibility that even if they write to me that they are willing to accept my application, when I arrive and apply, they not reject my application asking me to fly to India instead. (ICANN had asked the SFO Colombian Embassy 3 times if they are willing to process visas in a group, to which they agreed but when ICANN staff flew to SFO, they were told that the Colombian Embassy staff was incorrect and so ICANN Staff had to fly back empty handed). Even if by some luck another Embassy such as the UK Embassy issues me a Colombian visa it is possible that when I arrive in Cartagena the immigration may take the view that the visa has been issued from the wrong office and refuse entry. (credit to ICANN they had even offered to fund a trip by participants to such third countries to apply for visas) 3. The Colombian Foreign Office has informed a frustrated ICANN staff that ICANN participants may be issued visas on arrival. However ICANN staff has correctly cautioned that it may be possible that since this irregular I could come across an immigration officer who may be unaware and so may refuse entry. In any case airlines would not let passengers board their flights unless they have visas and so I may find myself unable to board flights to Cartagena and find myself stranded in Miami, for instance (not a bad outcome either but doesnt get me to the meeting). And if you thought this was it there are other convoluted permutations to the problem faced by me and participants from other countries. Hence, I have taken the following decisions: · It is best that the travel support allocated to me as a BC Councillor instead be made available and be used for other BC participants. · It is best that I not travel for this meeting considering the confusion and uncertainty around visas and have chosen to make alternate commitments during that time. I hope that this experience demonstrates that by simply rotating meetings and having them at exotic locations does not necessarily assist in participation by developing countries. Since many developing countries do not have the capacity to maintain diplomatic missions all over the world and they need to prioritise, they tend to have more missions in developed countries than in developing countries. This by itself is a challenge for participation and ought to be considered before choosing ICANN meeting venues. Sincerely, Zahid Jamil Barrister-at-law Jamil & Jamil Barristers-at-law 219-221 Central Hotel Annexe Merewether Road, Karachi. Pakistan Cell: +923008238230 Tel: +92 21 35680760 / 35685276 / 35655025 Fax: +92 21 35655026 <http://www.jamilandjamil.com/> www.jamilandjamil.com Notice / Disclaimer This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of DNDRC, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of DNDRC is prohibited.

2 1

Re: [bc-gnso] link -- the new applicant guidebook has been posted
by Marilyn Cade Nov. 13, 2010

Nov. 13, 2010

Well, one place wld be in ICANN's posted comments. I suggest folks also look at what ICANN said "we" said in summaries. They often omit or "misunderstand". Is helpful to know that in case you are making similar points. Sent via BlackBerry by AT&T -----Original Message----- From: Mike O'Connor <mike(a)haven2.com> Date: Sat, 13 Nov 2010 20:54:54 To: <bc-gnso(a)icann.org> Subject: [bc-gnso] link -- the new applicant guidebook has been posted hi all, the new Guidebook is posted at; http://www.icann.org/en/announcements/announcement-2-12nov10-en.htm all us sub-section reviewers can get our pencils out. :-) by the way, is there a place i can go look up our *previous* comments about Module 3? that's the one i've volunteered to help review. it's easy to see the things that been changed, but i'd like to look at what we *wanted* changed to see what things didn't get in. 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.)

1 0