October 2009 - Bc-gnso - lists.icann.org

Ballot for a new BC Charter
by BC Secretariat Oct. 14, 2009

Oct. 14, 2009

Dear Members Ballot on revised BC Charter At the request of the BC Officers and with reference to the message below, I have today opened a 7-day voting period for the newly revised BC Charter. A majority approval vote means the new Charter will be adopted. A majority non-approval vote means the Charter will not be adopted. A ballot form is attached. Each member organisation has one vote. The vote should be placed by the principle BC contact for the membership organsiation or by notified proxy. I will apply weighted voting when I receive your ballot form. All ballots will be acknowledged. The voting period closes at midnight in your time zone on Monday 19 October 2009. Ballots cannot be accepted after this time. Best wishes Gary ---------------------------------------------------- We would like to ask all members to cast their vote in favour of the attached revised BC Charter. A definitive PDF version is attached. A Word version showing recent track changes is also provided for information. The Charter accommodates necessary changes for the re-structured GNSO in which the stakeholder groups provide representatives to the GNSO council. As such the BC will move from a situation in which its three GNSO representatives were also BC Officers, to a separation of these roles. There will be a new executive committee with a chair and two vice-chairs in addition to the two representatives to the GNSO Council. The Charter also includes other changes recommended by members and ICANN staff based on learning since the last Charter. The officers have done their best to accommodate all member perspectives given the diversity of those perspectives. The Board has requested Constituencies complete work on Charter revision by Seoul. Zahid Jamil Mike Rodenbaugh Philip Sheppard BC Officers

11 12

Orderly introduction of new TLDs
by Ron Andruff Oct. 14, 2009

Oct. 14, 2009

Dear fellow members, Prior to the close of the last round of comments on the DAG v2, RNA Partners submitted a comment that focused on the fact that ICANN is embarking on rolling out new TLDs without establishing some parameters around what a TLD is, i.e., a definition. The logic in favor of defining the TLD is simple: Applicants should be encouraged to expand the name space, but should not be allowed to cannibalize other registries. A case in point was the round of 2004, when Tralliance Corporation received the right to manage .TRAVEL we were restricted from marketing to any travel entities that would fall under .AERO, i.e. airports, airlines, etc. In the discussions that I have had with ICANN community leadership over the last weeks it appears that all support the logic of including two questions in the final AG: (1) what community do you intend to serve? and (2) how does your TLD differentiate itself from others in the DNS? Answers to these two questions that demonstrate added value to the DNS would ensure that only those TLDs which act in harmony with one another are added to the root, rather than allowing applicants that meet the current criteria in DAG v3 irrespective of the fact that they may overlap or undercut another registry. With some 24 gTLDs today, one might say there is relatively little concern about this horizon issue; however, 5-10 years out, without the protections we are recommending, new applicant registry operators would have no impediment to undermining successful TLDs by selecting names that would diminish an established domain space. That would be anything but an orderly introduction of new TLDs to the DNS. We have reached out the GAC in this regard, as their recent communication with ICANN appears to be inline with our concerns. I have included my email to the Canadian GAC representative below for your information. In the interest of full disclosure, RNA Partners management is intending to apply to manage .SPORT on behalf of the global sport community. I look forward to furthering this dialogue with you on the list and in Seoul. Thank you for your consideration in bringing this issue to an appropriate resolution. Kind regards, RA Ronald N. Andruff RNA Partners, Inc. 220 Fifth Avenue, 20th floor New York, New York 10001 www.rnapartners.com V: +1 212 481 2820 x 11 F: +1 212 481 2859 _____ From: Ron Andruff [mailto:randruff@rnapartners.com] Sent: 2009-10-09 18:24 To: 'Heather Dryden' Cc: 'Marilyn Cade'; Cherian Mathai Subject: Orderly introduction of new TLDs Importance: High Dear Heather, I am contacting you at the suggestion of Marilyn Cade as I, like you, am Canadian ;o) and a colleague of Marilyn's for some 10-years in the Business Constituency. I also note, in the interest of full disclosure, that my company will be applying to manage the .sport domain for the global sporting community. Marilyn and I have been discussing how to enroll ICANN in the notion of an orderly introduction of new gTLDs and were considering the GAC correspondence to ICANN Chair, Peter Dengate-Thrush of August 18th, 2009, in light of our concerns. I note that much of the contents of that letter are consistent with the Business Constituency position on new TLDs, as well as our personally-held position. The BC set forth the following principles regarding expanding the name space following the round of 2000: Five principles to determine future expansion Name space expansion should create added-value. Where there is added-value there will be user demand. In this way expansion will enhance choice, competition and be in the public interest. In a global market economy added-value means differentiation and a practical way to achieve this is if all new names meet five principles: 1 Differentiation a gTLD must be clearly differentiated from other gTLDs 2 Certainty a gTLD must give the user confidence that it stands for what it purports to stand for 3 Good faith a gTLD must avoid increasing opportunities for bad faith entities who wish to defraud users 4 Competition a gTLD must create added-value competition 5 Diversity a gTLD must serve commercial or non-commercial users Amongst several comments on DAG v 2, the BC noted the following: Module 1 1.1.2.7 We agree with the standard for confusingly similar gTLD strings, which will not be allowed if they are deemed "so similar that they create a probability of detrimental user confusion if more than one is delegated." But more detail is needed as to how ICANN will make this determination. Module 2 2.1.1.1The Standard for String Confusion is inaccurately limited to "visually" similar. Instead string confusion should be deemed to exist where they are "so similar - in sight, sound or meaning - that they create a probability of detrimental user confusion if more than one is delegated." I contacting you today because we would like to get a sense from you as to how we should engage with the GAC to ensure that ICANN, in fact, introduces new TLDs in an orderly and managed manner rather than its current position of throwing open the door without consideration of the consequences of their actions further down the road. In July 2009 we submitted a comment to DAG v2 that focused on the fact that ICANN is embarking on rolling out new TLDs without establishing some parameters around what a TLD is, i.e., a definition. The logic is simple: Applicants should be entitled to flesh out the name space, but should not be allowed to cannibalize other registries. Our comment is noted here: ICANN must re-confirm the definition of a 'top-level domain' * To: <e-gtld-evaluation@xxxxxxxxx> * Subject: ICANN must re-confirm the definition of a 'top-level domain' * From: "Ron Andruff" <randruff@xxxxxxxxxxxxxxx> Date: Tue, 21 Jul 2009 19:34:27 -0400 To avoid the useless squandering of time and financial resources of ICANN reviewers, staff and those of new TLD applicants, as well as to avoid the needless bogging down of the roll out of new TLDs with objections based upon (1) string confusion; (2) misappropriation of community; and (3) infringement on the rights of others, ICANN must define what a top-level domain is. We recommend that the definition should be "the apex of a well-defined human activity, a community or a sector"; the key word in that definition being "apex", which directly equates to the word "top" of "top-level domain". This area was well-addressed in the new TLD application process used in the last round of introductions of new TLDs, but is missing from the current Draft Applicant Guidebook ("DAG"). In the applications for the 2004 round of sponsored top-level domains, the first question [paraphrased] was: How does the proposed TLD add new value to the Internet? The second question was: How does an application differentiate from existing TLDs? And the third question asked: Which unmet needs does a proposed new TLD meet? ICANN staff cannot overlook or discard these core principles going forward unless it intends to unilaterally abandon the logical expansion of the domain name space that the ICANN community has worked so long and hard to establish from the outset of ICANN's existence. This would be tantamount to abandoning the bottom up principles upon which ICANN was built and stands today. Absent inclusion of this critical definition, ICANN would open the door to a proliferation of TLDs that would be miniature sub-segments of apex TLDs, which would lead to user confusion at best, and, without doubt, challenges from apex TLDs, unnecessary defensive registrations and pernicious compliance issues. A case in point would be that in the event .NYC is granted to a registry, and another five TLDs would be awarded for .BROOKLYN, .BRONX, .MANHATTAN, .STATENISLAND and .QUEENS (the five boroughs that comprise the City of New York), the cacophony of domain names for the same community would render the whole TLD process absurd. The second DAG is not clear on this issue and therefore we believe that this oversight needs to be rectified to ensure that these particular requirements from the 2004 introduction of new TLDs are included in the process guaranteeing that in all cases the anticipated TLD expansion first and foremost brings value to Internet users, and thus ICANN can avoid any circumstance where user confusion could arise. This issue can be addressed and clarified in the definition of "confusingly similar strings". The current definition should be expanded beyond the semantic equivalence to also address the diminution of a TLD. In rectifying this oversight in the third DAG, ICANN will not only avoid user confusion issues, but it will stop the loss of precious valuable resources that will undoubtedly be wasted on a myriad of objections that could have been clearly avoided from the start. We trust that ICANN appreciates that the logical expansion of the domain name space is at the heart of this process and that the critical issue we are raising is in the interest of all stakeholders in the new TLD process, but especially trademark holders, those with responsibility for Internet security and stability, ICANN compliance staff and, most importantly, Internet users both in the near term and those in the coming decades. In August, the .sport Policy Advisory Council ("PAC"), which represents the global sport community sent a letter <http://www.icann.org/correspondence/baumann-to-dengate-thrush-20aug09-en.pd f> to ICANN CEO and Chair to advise ICANN of the support and concerns of the international sports family, particularly with regard to diminution of .sport. Sport is concerned that such diminution would gravely undermine sport solidarity, which enables stronger federations to support those with less resources and capabilities. In short, the PAC has very real concerns that ICANN would approve .sport as well as .volleyball, .basketball and the like. As I mentioned at the start of this email, we believe that the GAC letter supports a position that calls for applicants to define their intended community as well as what differentiation they bring to the DNS, as examples of defining themselves (as was required in previous rounds). I would be most grateful if you could advise us as to how we best bring this forward for GAC consideration. I believe that the IP and ISP constituencies, as well as the BC, support establishing clarity around this issue and ensuring new TLDs are meaningful additions to the DNS (rather than creating a free-for-all). GAC support would ensure a logical expansion. Thank you in advance for taking the time to read this rather long mail (I apologize for that!) and for giving us direction as we look to Seoul to get consensus on this position. I look forward to your soonest response. FYI, as I will be traveling over the coming weeks leading up to Seoul, should you need to speak with me my cell is: +1 917 770 2693. Kind regards, RA Ronald N. Andruff RNA Partners, Inc. 220 Fifth Avenue, 20th floor New York, New York 10001 www.rnapartners.com V: +1 212 481 2820 x 11 F: +1 212 481 2859

2 2

Ballot for a new BC Charter
by Rick Anderson Oct. 13, 2009

Oct. 13, 2009

This is a ridiculous provision, a clumsy attempt at stifling discussion. My company would never agree to have its own actions and statements bound by the charter of an association it belongs to, no seripus business could or would. Let's just disband the BC and get on with the new CSG. We have stalled on that long enough, and it is where we need to apply our energies and focus. It has been a very long time since the BC was an effective means for the provision of our input to the BC, it has become a private fiefdom of a very small number of individuals. We vote against the adoption of this charter. cheers/Rick Rick Anderson EVP, InterBorder Holdings Ltd email: randerson(a)interborder.ca cell: (403) 830-1798 ----- Original Message ----- From: owner-bc-gnso(a)icann.org <owner-bc-gnso(a)icann.org> To: BC gnso <bc-gnso(a)icann.org> Sent: Tue Oct 13 07:59:15 2009 Subject: Re: [bc-gnso] Ballot for a new BC Charter Hello, I, and other members, had been under the impression that there would be a set period to review the new updated draft charter, to allow for another round of comments and revisions, before going to a vote. Yet, now the officers seem to be calling for a vote on a seriously flawed charter. My company cannot support the draft charter, and will leave the constituency if it is adopted. While this will cause glee to certain members who seek to stifle free speech that counters their positions and who wish to use the BC as a mechanism to further their extremist positions that are not reflective of businesses, I think all should actually re-read what you're agreeing to if you accept the charter. I previously submitted comments at: http://forum.icann.org/lists/bc-gnso/msg00376.html and many of the important concerns remain. In particular, referencing the latest draft: 1. Section 3.4.2 states membership can be reviewed if: "a member takes action, beyond mere internal communication of dissent, that contravenes an adopted position of the Constituency and thus would be pursuing interests that may not be aligned with the Constituency;" I said it before in my previous comments. This means that Constituency members would not be permitted to externally voice dissent or act against an adopted position of the BC. It's shocking that this provision survived a revision of the charter. Other constituencies do not have this provision, and for good reason. If a registrar or registry or IP holder feels strongly against something that their respective constituency votes for, they are not bound by that position as an organization --- they are free to submit their own comments to ICANN, or to the DOC/DOJ/NTIA, or to politicians, or in the courts if the matter is serious enough. The same holds for trade associations within the BC -- members of AIM, CADNA, ICA, ETNO, ICC, USCIB or WITSA are certainly not externally limited in their behaviour if they disagree with a position of their trade association. I don't see how *any* BC member can support 3.4.2, unless they are not actually reading the words that they're voting for, or they wish to engage in voluntary servitude. (2) There are so many other flaws in the charter, that one should simply re-read: http://forum.icann.org/lists/bc-gnso/msg00376.html most of which still ring true, despite the conference call we had. For example, positions all over the place are "appointed" instead of elected, use the "up to" language, deny an elected treasurer and secretary, is anti-free speech (truth is not important), etc. etc. Given the existing officers have failed to deliver an acceptable charter, I believe that the process going forward to create a new charter should consist of the formation of a committee of volunteer members (excluding the current officers) to draft a new charter. As a starting point, we (and I would volunteer to help take on the work) can use the City-Top Level Domain constituency charter, which was relatively balanced (although would need some modifications), see: http://gnso.icann.org/files/gnso/en/improvements/ctldc-petition-charter-red… Of course, after a new draft is prepared, the existing officers and all other members would be free to comment on it, before another round (or rounds) of revisions and ultimately a vote. Sincerely, George Kirikos 416-588-0269 http://www.leap.com/ On Tue, Oct 13, 2009 at 8:08 AM, BC Secretariat <secretariat(a)bizconst.org> wrote: > Dear Members > > Ballot on revised BC Charter > > At the request of the BC Officers and with reference to the message below, I > have today opened a 7-day voting period for the newly revised BC Charter. > > A majority approval vote means the new Charter will be adopted. A majority > non-approval vote means the Charter will not be adopted. > > A ballot form is attached. Each member organisation has one vote. The vote > should be placed by the principle BC contact for the membership organsiation > or by notified proxy. I will apply weighted voting when I receive your > ballot form. All ballots will be acknowledged. > > The voting period closes at midnight in your time zone on Monday 19 October > 2009. Ballots cannot be accepted after this time. > > Best wishes > Gary > ---------------------------------------------------- > > We would like to ask all members to cast their vote in favour of the > attached revised BC Charter. > A definitive PDF version is attached. > A Word version showing recent track changes is also provided for > information. > > The Charter accommodates necessary changes for the re-structured GNSO in > which the stakeholder groups provide representatives to the GNSO council. > As such the BC will move from a situation in which its three GNSO > representatives were also BC Officers, to a separation of these roles. > There will be a new executive committee with a chair and two vice-chairs in > addition to the two representatives to the GNSO Council. > The Charter also includes other changes recommended by members and ICANN > staff based on learning since the last Charter. > The officers have done their best to accommodate all member perspectives > given the diversity of those perspectives. > The Board has requested Constituencies complete work on Charter revision by > Seoul. > > Zahid Jamil > Mike Rodenbaugh > Philip Sheppard > > BC Officers This e-mail message and any attachments may contain confidential and/or privileged information intended only for the addressee. In the event this e-mail is sent to you in error, sender and sender’s company do not waive confidentiality or privilege, and waiver may not be assumed. Any dissemination, distribution or copying of, or action taken in reliance on, the contents of this e-mail by anyone other than the intended recipient is prohibited. If you have been sent this e-mail in error, please destroy all copies and notify sender at the above e-mail address. Computer viruses can be transmitted by e-mail. You should check this e-mail message and any attachments for viruses. Sender and sender’s company accept no liability for any damage caused by any virus transmitted by this e-mail. Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties. If you do not wish to communicate by e-mail, please notify sender. In the absence of such notification, your consent is assumed. Sender will not take any additional security measures (such as encryption) unless specifically requested.

1 0

Follow up from last week's conference call
by Liz Williams Oct. 13, 2009

Oct. 13, 2009

All Further to our discussion last week about how to make the leap from the current structure to a new one, I have re-circulated a straw man proposal I sent around a couple of months ago. It suggests a way forward which is easy to do, low impact on our systems and gives clear results quite quickly. The only thing that would need to change in the document are the actual dates -- I proposed end of July to have a new slate of volunteers/elected people in place by Seoul. That's not going to happen but it could happen anytime shortly afterwards. Liz

2 1

FW: ICANN News Alert -- Organizational Review: Extension of Three Public Comment Periods
by Mike Rodenbaugh Oct. 13, 2009

Oct. 13, 2009

Good news that comment periods are extended a few weeks, re the reviews of Security and Stability Advisory Committee (SSAC), Nominating Committee (NomComm) and the Board of Directors. If anyone thinks the BC should speak up in response to any or all of these reports, please advise the list and volunteer to help draft comments. Thanks, Mike Mike Rodenbaugh RODENBAUGH LAW 548 Market Street San Francisco, CA 94104 (415) <http://service.ringcentral.com/ringme/callback.asp?mbid=57178438,0,&referer…> 738-8087 http://rodenbaugh.com <http://rodenbaugh.com/> From: ICANN News Alert [mailto:communications@icann.org] Sent: Wednesday, October 07, 2009 4:32 PM To: icann(a)rodenbaugh.com Subject: ICANN News Alert -- Organizational Review: Extension of Three Public Comment Periods <http://www.icann.org/> ICANN News Alert http://www.icann.org/en/announcements/announcement-07oct09-en.htm _____ Organizational Review: Extension of Three Public Comment Periods 7 October 2009 As requested by Community Members, the deadlines of the three following public comment periods have been moved to the 22nd of November: SSAC review WG <http://www.icann.org/en/public-comment/#ssac-review-2009> draft report; NomCom review <http://www.icann.org/en/public-comment/#nomcom-review-2009> WG draft report; and Board review <http://www.icann.org/en/public-comment/#board-review-2009> draft final report. _____ Sign up for <http://www.icann.org/magazine/> ICANN's Monthly Magazine This message was sent from ICANN News Alert to icann(a)rodenbaugh.com. It was sent from: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601. You can modify/update your subscription via the link below. <http://www.icontact.com/a.pl/144186> Email Marketing by <http://www.icontact.com/a.pl/144186> iContact - Try It Free! http://app.icontact.com/icp/static/images/icons/email_manage_subscription.p… <http://app.icontact.com/icp/mmail-mprofile.pl?r=11033829&l=6333&s=PWHD&m=26…> Manage your subscription http://click.icptrack.com/icp/track.php?msgid=265793&act=PWHD&r=11033829&c=…

2 1

MP3 recording GNSO Council teleconference, Thursday, 8 October 2009
by BC Secretariat Oct. 9, 2009

Oct. 9, 2009

Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 8 October 2009. http://audio.icann.org/gnso/gnso-council-20091008.mp3 on page http://gnso.icann.org/calendar/index.html#oct Happy listening!

1 0

Invitation to attend Registry/Registrar Separation Models conference call on 19 October, 2009 at 14:00 UTC.
by BC Secretariat Oct. 9, 2009

Oct. 9, 2009

Title: Interactive Session on Registry/Registrar Separation Models When: Monday, 19 October, 2009 Time: 14:00 to 17:00 UTC Dear ICANN Community Member: You are cordially invited to participate in a public, interactive, conference call discussion on registry/registrar separation models. This session has been scheduled to provide ample opportunity for community input on registry-registrar separation requirements in new gTLDs, and to respond to several requests for more public sessions on this topic. If you are unable to attend this session, there will be another opportunity to discuss this topic at the "Registry/Registrar Separation Discussion" forum on Monday, 26 October, 15:00 - 16:30, at the ICANN Seoul meeting. Recordings and presentations from both of these events will be publicly posted. Alternatively, you may choose to send your comments on this issue to the version 3 Draft Applicant Guidebook public forum, which is open through 22 November 2009. Session Details: As space is limited, this is an invitation-only event. If you would like to attend, please RSVP via email to <rrseparationwebinar(a)icann.org> prior to COB on October 14, 2009 to secure your place. An email reminder will be sent to registered individuals before the event with all log-in and dial-in details. Please DO NOT reply to this email or RSVP to ICANN Staff members. IMPORTANT – call for additional presenters! If you or a community representative wish to present at this session, please email Carole Cornell <carole.cornell(a)icann.org> and Kurt Pritz <kurt.pritz(a)icann.org>no later than 13 October 2009. Please include in this email a paragraph describing your proposed presentation, your (short) biography and, if possible, a photo. Each prospective presenter will be notified by 14 October whether their presentation can be accommodated, and presenters also will receive details on speaking time and other requirements. All presentations must be submitted to carole.cornell(a)icann.org by 16 October 2009. Since the conference call time is limited, presentation slots will be given to the Registrar and Registry Constituencies, and remaining slots will be offered first to representatives for the At-Large Advisory Committee, the Non-Commercial Stakeholder Group, and the Commercial Stakeholder Group. After presenters are set, a detailed agenda and information on speakers will be distributed. The session is scheduled for three hours and will be conducted in English only. During the conference call, slides will be presented via Adobe Connect, a dial-in conference bridge will be provided for audio, and questions may be submitted using the Q&A function of Adobe Connect. All questions and answers received, as well as the audio recording of the session and materials used during the presentation, will be posted on ICANN’s website. Session Description: The initial agenda is included below. This session will focus on models for proposed structural/organizational separation requirements. Multiple models will be presented and discussed, and opportunities for Q&A will be provided. Interactive Session on Registry-Registrar Separation. Initial Agenda Moderator: Joe Sims Presenters: Steve Salop and others to be determined. ICANN is soliciting presentations that will be made according to the agenda and rules below. If there are more offers of presentations than there is time permitted than representatives from the registrar constituency, registry constituency and the community at-large will be given a preference. Agenda and conduct of the session will follow these lines: Dr. Steve Salop will make an introduction: briefly describing the subject matter and describing the results of recent consultations with certain registries and registrars. Joe Sims will describe the rules for participating in the session. A presenter will describe a model for proposed structural/organization separation requirement. Each presentation should include slides and last about 20 minutes. The model should: (1) define and address organizational separation requirements (co-ownership or affiliation); (2) structural separation requirements; (3) if the model proposes that co-ownership be permitted, describe what limits or restrictions should be placed on the affiliated parties; (4) also describe the benefits or harms avoided to registrants through the proposed model. After each presentation, the presenter will answer questions. The moderator or Steve Salop may ask clarifying questions. Session attendees can ask questions through the interactive format by typing in questions. All questions are actually posed by the moderator who will read the questions typed in by the participants and, depending on volume, select from them. Selection will be based on asking at least a representative sample of all questions. This will be followed by another presentation. It is anticipated that there will be 4-5 presentations. Initial Speaker Information: Joe Sims – Moderator is a Senior Antitrust Partner, Jones Day. Steve Salop – Professor of Law and Economics, Georgetown University Law Center; former Associate Director for Special Projects and Industry Analysis, Bureau of Economics, US Federal Trade Commission; former Economist at Civil Aeronautics Board/Federal Reserve Board; prolific author and speaker. We are looking forward to your participation. Regards, Denise Michel, Vice President, Policy Kurt Pritz, Senior Vice President, Services

1 0

Members in Seoul
by BC Secretariat Oct. 8, 2009

Oct. 8, 2009

Dear Members I currently have confirmation of attendance in Seoul from the following: Zahid Jamil Mike Rodenbaugh Philip Sheppard Liz Williams Marilyn Cade Jarkko Ruuska and Ritva Siren Steve DelBianco Martin Sutton Ron Andruff Phil Corwin Mike McKeehan Jim Baskin If any other members are planning to be in Seoul please let me know. I will draw up a final list next week. Best wishes Gary

1 0

Seoul agendas update
by Philip Sheppard Oct. 8, 2009

Oct. 8, 2009

The following have now been agreed with our CSG colleagues. A specific mailing on the outreach cocktail will follow. ---------------------------------------- Tuesday 27 October 08.00 - 10.00 CSG breakfast with Board Topic 1 - Unresolved issues for new gTLDs: outcome of IRT recommendations & anti-malicious conduct provisions (lead IPC) Topic 2 - Affirmation of Commitments - what it means (lead BC) CSG 10.30 - 12.30 1. Unresolved issues for new gTLDs: outcome of IRT recommendations, anti-malicious conduct provisions, economic studies Q&A Kurt Pritz and Doug Brent (lead IPC) 2. R&R separation and other competitive issues - do we have a joint view? (lead ISP) 3. Admin: How do we work towards policy and other coordination within the CSG? (lead BC) BC 14.00 - 16.30 Admin 1. New Charter and functioning of exec comm: do we have enough volunteers? 2. How to address the fact that larger BC members are not contributing to an archived e-mail list 3. New secretariat and possible ICANN services 4. Organisation of ICANN meetings: new ways of working Policy 5. Contractual compliance role in addressing malicious conduct as part of the new gTLD program - Q&A with David Giza, ICANN Compliance 6 . Progress on anti-abuse mechanisms 7 . Follow -up on CSG/Board topics ------------------------------------- Wednesday 28 October 18.00 - 19.00 BC outreach cocktail - Athenee room - members and friends

1 0

Webinar calling for comments on proposed redesign of GNSO.ICANN.ORG web site
by Chris Chaplow Oct. 7, 2009

Oct. 7, 2009

Thank you to Berry A. Cobb, Zahid Jamil, Mike O'Connor, Ayesha HASSAN, and Marilyn Cade for expressing interest in this subject. If you or any other BC members would like to take part in the Webinar please RSVP to Gisella Gruber-White: Email: gisella.gruber-white(a)icann.org. Best regards, Chris Chaplow CCT member -----Mensaje original----- De: owner-gnso-osc-ccc(a)icann.org [mailto:owner-gnso-osc-ccc@icann.org] En nombre de Glen de Saint Géry Enviado el: miércoles, 07 de octubre de 2009 20:39 Para: gnso-osc-ccc(a)icann.org Asunto: [gnso-osc-ccc] Webinar calling for commnets on proposed redesign of GNSO.ICANN.ORG web site Dear All, Please take part in the Webinar organized to call for Comments on the proposed redesign of GNSO.ICANN.ORG web site on Wednesday 14 October at 1300 UTC http://gnso.icann.org/announcement/announcement-07oct09-en.htm As part of the GNSO Improvements Project, one of the tasks given the Operations Steering Committee's (OSC's) Communications Coordination Team (CCT) was to make the GNSO web site "more usable." The CCT has expedited progress on this task and, after extensive research with GNSO users and the ICANN community, has developed a proposed re-design of gnso.icann.org. The CCT's research indicates that the three most common user tasks on the GNSO site are: trying to find a document; managing activities via the Master Calendar; and seeking to learn the latest regarding a policy issue. The CCT proposed redesign to GNSO.ICANN.ORG simplifies those three tasks, and also makes the site friendlier to newcomers. Scott Pinzon and Ken Bour, ICANN Staff supporting the CCT, are presenting an overview and some wireframe diagrams of the proposed redesign. The goal is to gain your input, advice, and suggestions on further refinements. The overview will describe: .What it means to move from a static website to a dynamic website .The reasoning behind the proposed changes .Whose input influenced the proposed changes .Proposed new features, such as the Acronym Helper .How non-English content could be handled .Where to send comments and suggestions The webinar will be held on Wednesday 14 October at 1300 UTC using Adobe Connect and the dial-in bridge. All are welcome to participate, but members of the GNSO are especially encouraged to participate. To make sure that there are enough lines, please RSVP to Gisella Gruber-White: Email: gisella.gruber-white(a)icann.org. Dial-in details and the Adobe Connect room details will then be forwarded to you. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0