September 2009 - council - lists.icann.org

Formal Petition and Charter of the Proposed New City Top-Level Domain Constituency
by Robert Hoggarth 03 Nov '10

03 Nov '10

Dear GNSO Council Members; For your information, attached please find a copy of the Formal Petition and Charter of the proposed new City Top-Level Domain Constituency submitted by Dirk Krischenowski of dotBERLIN GmbH & Co. KG. This significant step represents the fourth formal new constituency petition submitted to the Board in the context of the new GNSO Improvements effort. The Staff will soon open a 30-day Public Comment Forum regarding the Petition which will extend into July. Any comments submitted in the Forum will be summarized for the Board's review. I have shared a copy of the attached documents with the Board and will be sending copies to the GNSO Constituencies leaders list as well. The document is now also posted on the GNSO Improvements web page at http://gnso.icann.org/en/improvements/newco-process-en.htm.@icann.org Please drop me a line if you have any questions or comments on this matter. Best regards, Rob Hoggarth Robert L. Hoggarth, Esq. Senior Policy Director ICANN 424 558 4805 robert.hoggarth(a)icann.org

1 1

NCA input to House placement
by Avri Doria 05 Oct '09

05 Oct '09

Hi, This note is to notify the council that I have worked with the 3 NCAs of the new council and have come up with their input to the council regarding their recommendation for assigning NCA Council Seats as required by the second bullet. This was an action that needed to be completed by 30 September. As a reminder, the Transition plan approved at the last meeting contains the following: ---- > For the period starting on 28 October 2009 and continuing only > through the 2010 ICANN Annual Meeting, the following procedure will > be used to assign NCAs to Council seats: > > • ICANN Staff should ensure that a Statement of Interest is > received from Andrey Kolesnikov and sent to the Council not later > than 30 September 2009. > > • Not later than 30 September 2009, new and existing NCAs will make > best efforts to collaborate and provide their input to the GNSO > Council regarding their recommendations for assigning NCA Council > seats. Such input should include any seating assignments that any of > the NCAs would individually be uncomfortable taking along with their > reasons. > > • Taking into consideration the input from the NCAs, if any, both > GNSO Council Houses and/or their respective Stakeholder Groups > should attempt to reach agreement on the seating for each of the > three NCAs for the first year of the new bicameral Council and > communicate the results to the Council not later than 7 October 2009. > > • If the GNSO Council Houses and/or their respective Stakeholder > Groups are unable to reach agreement, then the new, inexperienced > NCA will take the non-voting Council seat and random selection will > be used to assign the other two NCAs to Houses before the Council > meeting on 8 October 2009. > > • In the meeting scheduled for 8 October 2009, the Council will > acknowledge the results of this process and confirm that it was > properly conducted. > ----- In terms of the first point Glen is currently working with Andrey to get the required SOI completed In terms of the second point, we have recorded the output of the NCAs and make the following recommendations as input to further discussions: Contracted Parties House - Andrey Non contracted Parties House - Terry Independent non-voting - Olga The Process we followed: - First I created a doodle where each of them could indicate their preference. This was one of the 'yes-green, maybe-yellow, no-red' doodles. I set this up as hidden poll, so that consideration for each other's choices would not stand in the way of each of them stating, in the first instance, their personal preference. The idea was that once we saw the individual preferences, they could then negotiate a final list based on knowing what each other really wanted, or was willing, to do. I also made myself available for any of them who wanted to get more background information, but no one took me up on the offer. Note: I also told them that if they hated the idea of the poll we could start in another way, but I was looking for a way to reach a conclusion quickly. - The individual preferences, a snapshot of which is included below, showed that there was one possible solution from the beginning which would avoid any of them having to take a position they did not want. The results (depicted below): Olga and Andrey were both interested in the Contracted Parties House All three of them were willing to be placed in the Non-Contracted parties house. Terry indicated he was only willing to be placed the Non-contracted parties house Olga was the only one indicating willingness to take the Independent non voting role I suggested this as a starting position for their discussions, but also suggested they could ignore it, if they desired. - In the following conversation they all accepted the proposal, each for his/her own reasons: Andrey felt that his experience in managing a zone with 2.3 M domains, which is 99% compatible to a .COM environment, made him feel comfortable going into the Contracted Parties house. Terry felt that based on his experience in industry the Non Contracted parties house was the most appropriate. Olga was willing to take any of the roles, though she had a preference for the Contracted parties. - It is now up to the houses, to decide if they are willing to accept the input of the NCAs. If not, they will need to come up with another proposal. I invite the NCA's to add any comments to this they feel would be useful to the Houses in making their decision, but am not in any way obliging them to do so. I should mention that Andrey has been added to this list (as all newly appointed/elected council members will be), and I welcome him. Of course the incoming council members are observers on the list until 28 October. In keep with our normal processes, I invite the new council members to participate on the list as fully as they feel ready to with voting and the making of motions being the only exceptions. Regards, a.

10 21

Board appointments to fill 3 non-commercial seats on the new Council
by Denise Michel 30 Sep '09

30 Sep '09

Dear Community Members, The Board has appointed the following individuals to serve as Non-Commercial Stakeholder Group (NCSG) representatives on the new GNSO Council: Mohammed Rafik Dammak – Tunisia Rosemary Sinclair – Australia Debra Hughes – United States Under the terms of the NCSG transitional charter approved by the Board on 30 July 2009, three of the six NCSG representatives on the new GNSO Council to be seated at the Seoul meeting were to be selected/appointed by the Board. The Board's Structural Improvements Committee (SIC) considered applications from a talented and diverse group of volunteers, conducted extensive due diligence, carefully reviewed the candidates, and recommended for full Board consideration a slate of three nominees to serve on the GNSO Council for the next two years. The individuals listed above were recommended by the SIC for Board appointment based on their combination of skills, experience, background, geographic location, knowledge and passion, with particular attention to their ability to help build non-commercial participation and contribute to the work of the GNSO. More (official) information can be found in the Board resolution that will be posted here <http://www.icann.org/en/minutes/>shortly. Staff will be following-up with these individuals to make the necessary arrangements for their participation. Regards, Denise Denise Michel ICANN Vice President Policy Development policy-staff(a)icann.org

1 0

FW: ICANN Signed Affirmation Agreement
by Denise Michel 30 Sep '09

30 Sep '09

Forwarding email to ensure delivery to ASO, ccNSO, GNSO, ALAC, RSSAC, SSAC. Please share with your community members as appropriate. Thank you. Denise Michel VP Policy ICANN =============================== Dear ICANN Community Members: It is my pleasure to inform you that ICANN has signed a permanent "Affirmation Agreement" www.icann.org <http://www.icann.org> with the U.S. Department of Commerce that replaces the "Joint Partnership Agreement," which expired on 30 September 2009. This permanent agreement between ICANN and the U.S. Government, which was approved by ICANN's Board and signed by me, affirms our mutual commitment to ICANN's bottom-up, consensus-driven model and oversight by the global Internet community. Details of the of Affirmation Agreement can be found on ICANN's homepage, but I wanted to call your attention, in particular, to the important role ICANN's Supporting Organisations and Advisory Committees have in ICANN's future. Under the Agreement, SO and AC representatives and ICANN's international stakeholders are recognized reviewers who can formally hold ICANN accountable. For example, from paragraph 9.2 of the Affirmation, with bold added for emphasis: The review will be performed by volunteer community members and the review team will be constituted and published for public comment, and will include the following (or their designated nominees): the Chair of the GAC, the CEO of ICANN, representatives of the relevant Advisory Committees and Supporting Organizations, and independent experts. Composition of the review team will be agreed jointly by the Chair of the GAC (in consultation with GAC members) and the CEO of ICANN. This is another step in an amazing trajectory of the Internet's role in encouraging openness, innovation, commerce and freedom. I, along with ICANN's Board and Staff, look forward to working with you to implement the Agreement. We appreciate your support in bringing ICANN to this important new step in its history. Warmly, Rod Beckstrom President and CEO ICANN Addressing the Global Internet ------ End of Forwarded Message

1 0

Affirmation of commitments between USA Dept of Commerce and ICANN
by Bruce Tonkin 30 Sep '09

30 Sep '09

From: http://www.icann.org/en/announcements/announcement-30sep09-en.htm#affirm ation AFFIRMATION OF COMMITMENTS BY THE UNITED STATES DEPARTMENT OF COMMERCE AND THE INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS 1. This document constitutes an Affirmation of Commitments (Affirmation) by the United States Department of Commerce ("DOC") and the Internet Corporation for Assigned Names and Numbers ("ICANN"), a not-for-profit corporation. In recognition of the conclusion of the Joint Project Agreement and to institutionalize and memorialize the technical coordination of the Internet's domain name and addressing system (DNS)1, globally by a private sector led organization, the parties agree as follows: 2. The Internet is a transformative technology that will continue to empower people around the globe, spur innovation, facilitate trade and commerce, and enable the free and unfettered flow of information. One of the elements of the Internet's success is a highly decentralized network that enables and encourages decision-making at a local level. Notwithstanding this decentralization, global technical coordination of the Internet's underlying infrastructure - the DNS - is required to ensure interoperability. 3. This document affirms key commitments by DOC and ICANN, including commitments to: (a) ensure that decisions made related to the global technical coordination of the DNS are made in the public interest and are accountable and transparent; (b) preserve the security, stability and resiliency of the DNS; (c) promote competition, consumer trust, and consumer choice in the DNS marketplace; and (d) facilitate international participation in DNS technical coordination. 4. DOC affirms its commitment to a multi-stakeholder, private sector led, bottom-up policy development model for DNS technical coordination that acts for the benefit of global Internet users. A private coordinating process, the outcomes of which reflect the public interest, is best able to flexibly meet the changing needs of the Internet and of Internet users. ICANN and DOC recognize that there is a group of participants that engage in ICANN's processes to a greater extent than Internet users generally. To ensure that its decisions are in the public interest, and not just the interests of a particular set of stakeholders, ICANN commits to perform and publish analyses of the positive and negative effects of its decisions on the public, including any financial impact on the public, and the positive or negative impact (if any) on the systemic security, stability and resiliency of the DNS. 5. DOC recognizes the importance of global Internet users being able to use the Internet in their local languages and character sets, and endorses the rapid introduction of internationalized country code top level domain names (ccTLDs), provided related security, stability and resiliency issues are first addressed. Nothing in this document is an expression of support by DOC of any specific plan or proposal for the implementation of new generic top level domain names (gTLDs) or is an expression by DOC of a view that the potential consumer benefits of new gTLDs outweigh the potential costs. 6. DOC also affirms the United States Government's commitment to ongoing participation in ICANN's Governmental Advisory Committee (GAC). DOC recognizes the important role of the GAC with respect to ICANN decision-making and execution of tasks and of the effective consideration by ICANN of GAC input on the public policy aspects of the technical coordination of the Internet DNS. 7. ICANN commits to adhere to transparent and accountable budgeting processes, fact-based policy development, cross-community deliberations, and responsive consultation procedures that provide detailed explanations of the basis for decisions, including how comments have influenced the development of policy consideration, and to publish each year an annual report that sets out ICANN's progress against ICANN's bylaws, responsibilities, and strategic and operating plans. In addition, ICANN commits to provide a thorough and reasoned explanation of decisions taken, the rationale thereof and the sources of data and information on which ICANN relied. 8. ICANN affirms its commitments to: (a) maintain the capacity and ability to coordinate the Internet DNS at the overall level and to work for the maintenance of a single, interoperable Internet; (b) remain a not for profit corporation, headquartered in the United States of America with offices around the world to meet the needs of a global community; and (c) to operate as a multi-stakeholder, private sector led organization with input from the public, for whose benefit ICANN shall in all events act. ICANN is a private organization and nothing in this Affirmation should be construed as control by any one entity. 9. Recognizing that ICANN will evolve and adapt to fulfill its limited, but important technical mission of coordinating the DNS, ICANN further commits to take the following specific actions together with ongoing commitment reviews specified below: 9.1 Ensuring accountability, transparency and the interests of global Internet users: ICANN commits to maintain and improve robust mechanisms for public input, accountability, and transparency so as to ensure that the outcomes of its decision-making will reflect the public interest and be accountable to all stakeholders by: (a) continually assessing and improving ICANN Board of Directors (Board) governance which shall include an ongoing evaluation of Board performance, the Board selection process, the extent to which Board composition meets ICANN's present and future needs, and the consideration of an appeal mechanism for Board decisions; (b) assessing the role and effectiveness of the GAC and its interaction with the Board and making recommendations for improvement to ensure effective consideration by ICANN of GAC input on the public policy aspects of the technical coordination of the DNS; (c) continually assessing and improving the processes by which ICANN receives public input (including adequate explanation of decisions taken and the rationale thereof); (d) continually assessing the extent to which ICANN's decisions are embraced, supported and accepted by the public and the Internet community; and (e) assessing the policy development process to facilitate enhanced cross community deliberations, and effective and timely policy development. ICANN will organize a review of its execution of the above commitments no less frequently than every three years, with the first such review concluding no later than December 31, 2010. The review will be performed by volunteer community members and the review team will be constituted and published for public comment, and will include the following (or their designated nominees): the Chair of the GAC, the Chair of the Board of ICANN, the Assistant Secretary for Communications and Information of the DOC, representatives of the relevant ICANN Advisory Committees and Supporting Organizations and independent experts. Composition of the review team will be agreed jointly by the Chair of the GAC (in consultation with GAC members) and the Chair of the Board of ICANN. Resulting recommendations of the reviews will be provided to the Board and posted for public comment. The Board will take action within six months of receipt of the recommendations. Each of the foregoing reviews shall consider the extent to which the assessments and actions undertaken by ICANN have been successful in ensuring that ICANN is acting transparently, is accountable for its decision-making, and acts in the public interest. Integral to the foregoing reviews will be assessments of the extent to which the Board and staff have implemented the recommendations arising out of the other commitment reviews enumerated below. 9.2 Preserving security, stability and resiliency: ICANN has developed a plan to enhance the operational stability, reliability, resiliency, security, and global interoperability of the DNS, which will be regularly updated by ICANN to reflect emerging threats to the DNS. ICANN will organize a review of its execution of the above commitments no less frequently than every three years. The first such review shall commence one year from the effective date of this Affirmation. Particular attention will be paid to: (a) security, stability and resiliency matters, both physical and network, relating to the secure and stable coordination of the Internet DNS; (b) ensuring appropriate contingency planning; and (c) maintaining clear processes. Each of the reviews conducted under this section will assess the extent to which ICANN has successfully implemented the security plan, the effectiveness of the plan to deal with actual and potential challenges and threats, and the extent to which the security plan is sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the Internet DNS, consistent with ICANN's limited technical mission. The review will be performed by volunteer community members and the review team will be constituted and published for public comment, and will include the following (or their designated nominees): the Chair of the GAC, the CEO of ICANN, representatives of the relevant Advisory Committees and Supporting Organizations, and independent experts. Composition of the review team will be agreed jointly by the Chair of the GAC (in consultation with GAC members) and the CEO of ICANN. Resulting recommendations of the reviews will be provided to the Board and posted for public comment. The Board will take action within six months of receipt of the recommendations. 9.3 Promoting competition, consumer trust, and consumer choice: ICANN will ensure that as it contemplates expanding the top-level domain space, the various issues that are involved (including competition, consumer protection, security, stability and resiliency, malicious abuse issues, sovereignty concerns, and rights protection) will be adequately addressed prior to implementation. If and when new gTLDs (whether in ASCII or other language character sets) have been in operation for one year, ICANN will organize a review that will examine the extent to which the introduction or expansion of gTLDs has promoted competition, consumer trust and consumer choice, as well as effectiveness of (a) the application and evaluation process, and (b) safeguards put in place to mitigate issues involved in the introduction or expansion. ICANN will organize a further review of its execution of the above commitments two years after the first review, and then no less frequently than every four years. The reviews will be performed by volunteer community members and the review team will be constituted and published for public comment, and will include the following (or their designated nominees): the Chair of the GAC, the CEO of ICANN, representatives of the relevant Advisory Committees and Supporting Organizations, and independent experts. Composition of the review team will be agreed jointly by the Chair of the GAC (in consultation with GAC members) and the CEO of ICANN. Resulting recommendations of the reviews will be provided to the Board and posted for public comment. The Board will take action within six months of receipt of the recommendations. 9.3.1 ICANN additionally commits to enforcing its existing policy relating to WHOIS, subject to applicable laws. Such existing policy requires that ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information, including registrant, technical, billing, and administrative contact information. One year from the effective date of this document and then no less frequently than every three years thereafter, ICANN will organize a review of WHOIS policy and its implementation to assess the extent to which WHOIS policy is effective and its implementation meets the legitimate needs of law enforcement and promotes consumer trust. The review will be performed by volunteer community members and the review team will be constituted and published for public comment, and will include the following (or their designated nominees): the Chair of the GAC, the CEO of ICANN, representatives of the relevant Advisory Committees and Supporting Organizations, as well as experts, and representatives of the global law enforcement community, and global privacy experts. Composition of the review team will be agreed jointly by the Chair of the GAC (in consultation with GAC members) and the CEO of ICANN. Resulting recommendations of the reviews will be provided to the Board and posted for public comment. The Board will take action within six months of receipt of the recommendations. 10. To facilitate transparency and openness in ICANN's deliberations and operations, the terms and output of each of the reviews will be published for public comment. Each review team will consider such public comment and amend the review as it deems appropriate before it issues its final report to the Board. 11. The DOC enters into this Affirmation of Commitments pursuant to its authority under 15 U.S.C. 1512 and 47 U.S.C. 902. ICANN commits to this Affirmation according to its Articles of Incorporation and its Bylaws. This agreement will become effective October 1, 2009. The agreement is intended to be long-standing, but may be amended at any time by mutual consent of the parties. Any party may terminate this Affirmation of Commitments by providing 120 days written notice to the other party. This Affirmation contemplates no transfer of funds between the parties. In the event this Affirmation of Commitments is terminated, each party shall be solely responsible for the payment of any expenses it has incurred. All obligations of the DOC under this Affirmation of Commitments are subject to the availability of funds.

1 0

DNSO Restricted Funds
by Glen de Saint Géry 30 Sep '09

30 Sep '09

Forwarded from ISPCP Constituency Kevin: As a result of the GNSO resolution at http://gnso.icann.org/resolutions/#200904 the remaining DNSO restricted funds are available for support of other ISPCP travelers. On behalf of the ISPCP constituency, I would like to request that $1,347.30 be transferred to the ISPCP general account via a check made out to the ISPCP Secretariat. It is possible to do this through a bank transfer if that is more convenient for you. Otherwise, I hope this simple request is enough to get us started officially! mark Mark McFadden, Secretariat ISPCP Constituency, ICANN secretariat(a)ispcp.info Y! IM: mcfadden AIM: McElmside Tw: McElmside Bkite: mcfadden Fb: Mark McFadden Dear requestor of DNSO restricted funds: I understand that you have been allocated US$3,327.30 of the remaining DNSO restricted funds for the purpose of funding or partially funding your travel costs to the Sydney meeting. (This amount is equal to one sixth of the total of $19,963.79 DNSO restricted funds). In order to execute the release of these funds, please provide a clear request for these funds indicating: * The amount in US$. * Who to pay Please attach this email, including the GNSO resolution below, to your request and copy the GNSO Council list <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>list to ensure accountability and transparency. Separately, please send to Michael Cashin atMichael.cashin(a)icann.org<mailto:Michael.cashin@icann.org>, the specific payment transaction information. If you have any questions, please call or email me at any time. Thank you Kevin Wilson CFO ICANN +1.323.868.0514 GNSO Resolution Whereas: At its meeting of September 25, 2008 the GNSO Council created the Travel Drafting Team (TDT) to work on proposals to optimize the allocation and the management of Travel Funding for the GNSO Constituencies. At a meeting held during the Mexico ICANN meeting in March 2009 between the TDT and members of ICANN staff, the TDT requested that all GNSO Constituencies receive Funding Slots for each of their elected Councilors at each one of the three yearly international ICANN meetings, with the understanding that it would then be up to each Constituency to allocate these slots according to their own internal processes. That request stemmed in part from the recognition of the significant, and ever increasing work loads, that GNSO Councilors face. Work which they carry out as unpaid volunteers. Since that meeting it has been identified that an amount of funds left over from the DNSO are available for use should the Council wish to provide additional Travel Funding to those GNSO Constituencies that no longer have enough credits left for their three slots for the final meeting of the fiscal year 2008, in Sydney. The funds identified are in the amount of 19,963.79 USD. Resolved: That the DNSO funds be distributed evenly across all six GNSO Constituencies in time for the Sydney meeting in June, with the express purpose of providing additional Travel Funding for those persons nominated by each Constituency as recipients to be of said Travel Support.

1 0

RE: [council] Topic for next Agenda was Re: [] Incoming Council members
by Tim Ruiz 30 Sep '09

30 Sep '09

> Board-GNSO-Staff Diner topic What about the new agreement/arrangement that is rumored to follow the expiration of the JPA? Seems we should have more details on that by Seoul, and likely a lot of questions. Tim -------- Original Message -------- Subject: [council] Topic for next Agenda was Re: [] Incoming Council members From: Avri Doria <avri(a)acm.org> Date: Tue, September 29, 2009 12:28 pm To: Council GNSO <council(a)gnso.icann.org> Hi, In terms of that agenda, I currently see two dominant issues: 1. Discussion of the contents of the yet to be approved letter form the Board to the GNSO asking for the GNSO to do some work related to the DAG and the IRT recommendations. 2. Any issues that still need to be dealt with in terms of completing the transition/restructuring. E.g. the assignment of NCAs to houses if that has not been completed yet (completion date is listed as 7 Oct) or any other issue that is pending. The agenda will come out this Thursday. If anyone on the council has any issues they think also need to be covered, please let me know. Also in terms of the Board-GNSO-Staff Diner topic - I am thinking that the contents of the yet to be seen letter might be just the thing. Does this sound reasonable? Any other suggestions? I am also thinking that this letter should be on the Wednesday Public Meeting agenda. thanks a. On 29 Sep 2009, at 12:46, Gomes, Chuck wrote: > I am anticipating that our agenda may be shorter than usual so I > think that it would be good if we have an agenda item at the > beginning to welcome the new Councilors and an agenda item at the > end allowing them to ask questions if they have any and if time > permits. Other than that it is probably best that the new > Councilors are there as observers unless there is a discussion topic > that specifically involves them. > > Chuck > >> -----Original Message----- >> From: owner-council(a)gnso.icann.org >> [mailto:owner-council@gnso.icann.org] On Behalf Of Avri Doria >> Sent: Tuesday, September 29, 2009 11:43 AM >> To: Council GNSO >> Subject: Re: [council] Incoming Council members was Re: [] >> NCA input to House placement >> >> >> Hi, >> >> Sorry if i was unclear. i was suggesting that they be there >> as observers. >> But I was not explicit in the part I wrote for that message, >> only in the part I included from a previous message. >> >> BTW, 'as observers' normally means, in a GNSO context, that >> they can participate just not vote or make motions. >> >> a. >> >> On 29 Sep 2009, at 11:35, Adrian Kinderis wrote: >> >>> I object to them joining as Councillors. >>> >>> They should be there as observers only. >>> >>> Sent from my iPhone >>> >>> On 30/09/2009, at 1:14, "Stéphane Van Gelder" >>> <stephane.vangelder(a)indom.co >>> m> wrote: >>> >>>> Seems fine to me. >>>> >>>> Stéphane >>>> >>>> >>>> Le 29/09/09 15:26, « Avri Doria » <avri(a)psg.com> a écrit : >>>> >>>>> >>>>> >>>>> On 29 Sep 2009, at 08:32, Avri Doria wrote: >>>>> >>>>>> I should mention that Andrey has been added to this list (as all >>>>>> newly appointed/elected council members will be), and I welcome >>>>>> him. Of course the incoming council members are >> observers on the >>>>>> list until 28 October. In keep with our normal >> processes, I invite >>>>>> the new council members to participate on the list as >> fully as they >>>>>> feel ready to with voting and the making of motions >> being the only >>>>>> exceptions. >>>>> >>>>> >>>>> I would like to suggest that incoming council members also be >>>>> invited to join the next Council call on on 8 October. >>>>> >>>>> Since this is not part of the normal process, I want to >> confirm that >>>>> there are no objections. >>>>> >>>>> thanks >>>>> >>>>> a. >>>>> >> >> >> >

3 2

ALAC Coordinator for RAA DT(s)
by Alan Greenberg 30 Sep '09

30 Sep '09

Beau Brendler will be leading the effort for the ALAC. Alan

1 0

Ask a Question Direct to the Board in Seoul
by Glen de Saint Géry 29 Sep '09

29 Sep '09

http://www.icann.org/en/announcements/announcement-29sep09-en.htm Ask a Question Direct to the Board in Seoul 29 September 2009 An online question box where community members can ask questions directly to the ICANN Board and staff has opened today. The question box will take questions until Wednesday 14 October in preparation for the public forum at ICANN's international public meeting in Seoul on Thursday 29 October. Anyone can ask up to two questions or 50 words in length. The question can cover any topic related to ICANN and its work. Answers will be provided either during the public forum or emailed and published in the weeks following the meeting. You can find the form below as well as on the Seoul meeting website and the blog. Related links: Seoul question box: http://icann.wufoo.com/forms/seoul-question-box/ Sydney question box responses: http://www.icann.org/en/participate/sydney-public-forum-response-en.html Mexico City question box responses: http://www.icann.org/en/participate/mexico-city-public-forum-response.htm Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

RE: [council] Incoming Council members was Re: [] NCA input to House placement
by Tim Ruiz 29 Sep '09

29 Sep '09

I agree with Adrian and with Chuck's suggestion below. Tim -------- Original Message -------- Subject: RE: [council] Incoming Council members was Re: [] NCA input to House placement From: "Gomes, Chuck" <cgomes(a)verisign.com> Date: Tue, September 29, 2009 11:46 am To: "Avri Doria" <avri(a)psg.com>, "Council GNSO" <council(a)gnso.icann.org> I am anticipating that our agenda may be shorter than usual so I think that it would be good if we have an agenda item at the beginning to welcome the new Councilors and an agenda item at the end allowing them to ask questions if they have any and if time permits. Other than that it is probably best that the new Councilors are there as observers unless there is a discussion topic that specifically involves them. Chuck > -----Original Message----- > From: owner-council(a)gnso.icann.org > [mailto:owner-council@gnso.icann.org] On Behalf Of Avri Doria > Sent: Tuesday, September 29, 2009 11:43 AM > To: Council GNSO > Subject: Re: [council] Incoming Council members was Re: [] > NCA input to House placement > > > Hi, > > Sorry if i was unclear. i was suggesting that they be there > as observers. > But I was not explicit in the part I wrote for that message, > only in the part I included from a previous message. > > BTW, 'as observers' normally means, in a GNSO context, that > they can participate just not vote or make motions. > > a. > > On 29 Sep 2009, at 11:35, Adrian Kinderis wrote: > > > I object to them joining as Councillors. > > > > They should be there as observers only. > > > > Sent from my iPhone > > > > On 30/09/2009, at 1:14, "Stéphane Van Gelder" > > <stephane.vangelder(a)indom.co > > m> wrote: > > > >> Seems fine to me. > >> > >> Stéphane > >> > >> > >> Le 29/09/09 15:26, « Avri Doria » <avri(a)psg.com> a écrit : > >> > >>> > >>> > >>> On 29 Sep 2009, at 08:32, Avri Doria wrote: > >>> > >>>> I should mention that Andrey has been added to this list (as all > >>>> newly appointed/elected council members will be), and I welcome > >>>> him. Of course the incoming council members are > observers on the > >>>> list until 28 October. In keep with our normal > processes, I invite > >>>> the new council members to participate on the list as > fully as they > >>>> feel ready to with voting and the making of motions > being the only > >>>> exceptions. > >>> > >>> > >>> I would like to suggest that incoming council members also be > >>> invited to join the next Council call on on 8 October. > >>> > >>> Since this is not part of the normal process, I want to > confirm that > >>> there are no objections. > >>> > >>> thanks > >>> > >>> a. > >>> > > >

1 0