[council] GNSO Council Committee draft minutes 25 August 2005

["GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx>]

[To: council[at]gnso.icann.org]

Dear Council members,

Please find attached the draft minutes of the GNSO Council committee
teleconference held on 25 August 2005.

Please let me know what changes you would like made.

Thank you.
Kind regards,

Glen
--
Glen de Saint Géry
GNSO Secretariat - ICANN
gnso.secretariat[at]gnso.icann.org
http://gnso.icann.org

<!--#set var="bartitle" value="GNSO Council Teleconference Minutes"-->
<!--#set var="pagetitle" value="GNSO Council Teleconference Minutes"-->
<!--#set var="pagedate" value="25 August 2005"-->
<!--#set var="bgcell" value="#ffffff"-->
<!--#include virtual="/header.shtml"-->
<!--#exec cmd="/usr/bin/perl /etc/gnso/menu.pl 'GNSO Council Teleconference 
Minutes'"-->
<p><font face="Arial, Helvetica, sans-serif">25 August 2005 </font> </p>
<p><font face="Arial, Helvetica, sans-serif">Proposed <a 
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01302.html";>agenda</a>
 and <a 
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01315.html";>related
 documents</a> </font></p>
<p><font face="Arial, Helvetica, sans-serif"><b>List of attendees:</b><br>
  Philip Sheppard - Commercial &amp; Business Users C. <br>
  Marilyn Cade - Commercial &amp; Business Users C. <br>
  Grant Forsyth - Commercial &amp; Business Users C<br>
  Greg Ruth - ISCPC <br>
  Antonio Harris - ISCPC<br>
  Tony Holmes - ISCPC<br>
  Thomas Keller- Registrars<br>
  Ross Rader - Registrars   <br>
  Bruce Tonkin - Registrars <br>
  Ken Stubbs - gTLD registries <br>
  Philip Colebrook - gTLD registries <br>
  Cary Karp - gTLD registries <br>
  Lucy Nichols - Intellectual Property Interests C - absent - apologies - proxy 
to Niklas Lagergren<br>
  Niklas Lagergren - Intellectual Property Interests C<br>
  Kiyoshi Tsuru - Intellectual Property Interests C. - absent <br>
  Robin Gross - Non Commercial Users C. - absent - apologies - proxy to Norbert 
Klein<br>
  Norbert Klein - Non Commercial Users C.<br>
  Alick Wilson - Nominating Committee appointee <br>
  Maureen Cubberley - Nominating Committee appointee - absent  - apologies<br>
  Avri Doria -  Nominating Committee appointee 
  </font></p>
<p> <font face="Arial, Helvetica, sans-serif"> 16 Council Members<br>
  <br>
    <b>ICANN Staff</b><br>
  Olof Nordling - Manager, Policy Development Coordination   - absent - 
apologies <br>
  Maria Farrell - ICANN GNSO Policy Support Officer<br>
  Liz Williams - Senior Policy Counselor<br>
  Glen de Saint Géry - GNSO Secretariat <br>
  <br>
  <br>
  <b>GNSO Council Liaisons</b><br>
 Bret Fausett - acting ALAC Liaison<br>
 <br>
  Michael Palage - ICANN Board member <br>
  <br>
  <strong>Invited Guests - Constituency Officers</strong>  <br>
  Tim Ruiz - Registrar Constituency - Vice Chair
  <br>
  Bob Connelly - Registrar Constituency - Secretary <br>
  Marie Zitkova - gTLD Registries Constituency 
   - Chair<br>
   Steve Metalitz - 
  Intellectual Property Interests C - Executive Vice President<br> 
  <br>
  <a href="http://gnso-audio.icann.org/GNSO-Council-20050825.mp3";>MP3 Recording
  </a></font><font face="Arial, Helvetica, sans-serif"><br>
  <br>
    <b>Bruce Tonkin</b> chaired this teleconference. <br>
    <br>
    <strong>The topic of this committee meeting is the terms of reference for 
the review of the Generic  Names Supporting Organisation (GNSO) </strong><br>
  <br>
    <a 
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01302.html";>Approval
 of Agenda</a> <br>
    <strong>Marilyn Cade</strong>  requested planning for interaction with the 
ICANN Board to be added to the agenda. <br>
    <br>
    <strong>Item 1. Review the goals and expected outcomes of the GNSO review, 
at both<br>
the Council and constituency level<br>
    </strong></font><br>
<font face="Arial, Helvetica, sans-serif">The goal of the review is twofold and 
forms part of the <a 
href="http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#IV";>ICANN 
bylaws</a><br>
&quot;The goal of the review, to be undertaken pursuant to such criteria and 
standards as the Board shall direct, shall be to determine <br>
(i) whether that organization has a continuing purpose in the ICANN structure, 
and <br>
(ii) if so, whether any change in structure or operations is desirable to 
improve its effectiveness<br>
<br>
The criteria and standards of the review must be approved by the Board. The 
Board has asked the GNSO Council to prepare a terms of reference (TOR) with 
input from the Board that would be used to guide an outside consultant or 
independent person to conduct the review<br>
The TOR is due to be completed in time for adoption by the Board at the 
Vancouver meeting in December 2005.<br>
<br>
The goal and high order steps for developing the TOR were as follows: <br>
- the purpose of the current meeting is to inform the GNSO members  of the 
upcoming review<br>
- to gather input from the GNSO community<br>
- produce a draft TOR <br>
- submit TOR  to the Board<br>
- invite Board input to  the draft during a joint GNSO Council/ICANN Board 
teleconference on 8 September 2005<br>
- proposed final draft TOR  presented to the Board for approval <br>
</font><font face="Arial, Helvetica, sans-serif"><br>
  What outcomes is Council seeking?<br>
  <strong>Bruce Tonkin</strong> referred to the outcome of the <a 
href="http://www.gnso.icann.org/announcements/announcement-22dec04.htm";>2004 
GNSO Council review</a>  that stated that the GNSO Council  had a continuing 
role and proposed <a 
href="http://gnso.icann.org/reviews/gnso-review-sec4-22dec04.pdf";>20 
Recommendations</a> by which Council's  processes and procedures could be 
improved.<br>
  The GNSO Review based its work on 9 questions:<br>
  <br>
1. Policy Achievements<br>
<br>
</font><font face="Arial, Helvetica, sans-serif">2. Outreach, geographic 
diversity and transparency.<br>
</font><font face="Arial, Helvetica, sans-serif">Has the GNSO Council 
contributed to other ICANN core values such as outreach, bottom-up consensus 
based policy development, geographical diversity and transparency?<br>
<br>
</font><font face="Arial, Helvetica, sans-serif">3. Policy Development Process 
timelines<br>
  Are the timelines relevant?<br>
  <br>
</font><font face="Arial, Helvetica, sans-serif">4. Has there been effective 
ICANN staff support for policy development?</font></p>
<p><font face="Arial, Helvetica, sans-serif">5. Policy implementation and 
compliance<br>
</font><font face="Arial, Helvetica, sans-serif">After the completion of policy 
development has policy implementation, compliance and outcome been 
effective?</font></p>
<p><font face="Arial, Helvetica, sans-serif">6. Demand based raising of policy 
issues<br>
  Is the current mechanism of alerting the GNSO Council to new policy issues 
effective?<br>
  <br>
  7. Voting Pattern<br>
  Does the Council vote as a consensual body?</font></p>
<p><font face="Arial, Helvetica, sans-serif">8. Number of constituency 
representatives<br>
</font><font face="Arial, Helvetica, sans-serif">Has the presence of three 
rather than two representatives per constituency helped or hindered the GNSO 
Council?<br>
<br>
</font><font face="Arial, Helvetica, sans-serif">9. Communication to the ICANN 
Community<br>
</font><font face="Arial, Helvetica, sans-serif">Are the enabling mechanisms 
for GNSO Council outreach effective?<br>
</font><font face="Arial, Helvetica, sans-serif"><br>
  Council members and executive representatives from the constituencies were 
asked to express their views on  what  review  output would be useful  to 
increase constituencies' effectiveness. <br>
  <br>
  From a Council and constituency perspective,
seeking feedback on perceptions the ICANN community held and their expectations 
for the GNSO would provide a good slate of work to focus upon and continue 
improvement. Improved dialogue and information explaining ICANN which would 
facilitate people  joining the appropriate constituency or the At Large 
Advisory Committee and become involved in ICANN's activities. Timelines should 
be pragmatically established to meet the expectations in policy development 
work in the constituencies and the community in general. The diversity among 
the constituencies and the way they operated was a challenge to the policy 
development timelines.<br>
</font><font face="Arial, Helvetica, sans-serif"><br>
  <strong>Bruce Tonkin</strong> referred to the outcome of the <a 
href="http://gnso.icann.org/reviews/gnso-review-sec1-22dec04.pdf";>GNSO Review 
</a>which stated that:<br>
  </font> <font face="Arial, Helvetica, sans-serif">&quot;Changes are needed to 
the PDP timelines. There is a need to formalize current practice, not least to 
ensure that the GNSO operates in accordance with its own bylaws and procedures. 
The structure of the PDP needs to be maintained, but it needs to acknowledge 
that different policy issues require types of work and therefore different time 
frames.</font><font face="Arial, Helvetica, sans-serif">&quot;<br>
  Constituencies differed widely, e.g. Business Users and ISPs would be more 
consistent in a position than an organisation as diverse in perspective as the 
At Large, and some had regular secretarial help while others had a membership 
spread over the globe with no structured secretariat. In the case of the 
Registrar constituency, though the number of registrars involved or who voted 
on an issue at any one time was low compared to the constituency membership, 
the number of names or registrants those registrars served was a large section 
of the community. Constituencies should be examined from multiple dimensions 
and not only on a numerical membership basis.<br>
  An outcome of the review could be finding common methods and systems and 
learning  what some constituencies, and likewise the Council, did well, which 
could be translated into facilitating overall efficiency at the constituency 
level. <br>
  An ICANN bylaws requirements is to identify whether each constituency is 
meetings its objectives.  <br>
  <br>
  A Board member noted two important outcomes the process should achieve:<br>
  - What was the perception, outcome from the ICANN Board and the community of 
the GNSO process<br>
- How would the process be evaluated to produce the outcome.</font></p>
<p><font face="Arial, Helvetica, sans-serif">Recommendations with depth and 
breadth in the discussions better enabled the Board to make informed 
decisions.<br>
  <br>
  In summary <br>
  The goals of the review are to be found in the in the <a 
href="http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#IV";>ICANN 
bylaws Under Article IV,</a><br>
and the constituency description:<br>
&quot;
3. Each Constituency identified in <a 
href="http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#X-5";>paragraph
 1 of this Section (5)</a> shall maintain its recognition, and thus its ability 
to select GNSO Council representatives, only so long as it in fact represents 
the interests globally of the stakeholder communities it purports to represent, 
and shall operate to the maximum extent feasible in an open and transparent 
manner and consistent with procedures designed to ensure fairness. <br>
No individual or entity shall be excluded from participation in a Constituency 
merely because of participation in another Constituency. &quot; <br>
The GNSO council could be evaluated against whether the processes of the policy 
development process had been followed and a constituency could be evaluated 
against whether it was globally  representing the interests  of that community  
in an open and transparent manner.<br>
  <br>
  <strong>Item 2: Discuss the current draft document - receive input from 
Council<br>
members and constituencies</strong><br>
- specific drafting should be handled via the mailing list<br>
<br>
Feedback was requested on the Initial areas for the criteria review:<br>
- Representativeness<br>
- Authority<br>
 - Effectiveness <br>
 - Transparency<br>
 <br>
 The structure of the document should highlight the terms of reference by 
placing them up front and certain background sections  in an annex. <br>
 All prior documentation that has addressed the effectiveness of the supporting 
organisation should be incorporated into the TOR.  Previous discussions and 
papers have been captured in the <a 
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01316.html";>background
 document </a> It would be helpful to provide extracts of the original green 
and white papers and the recent evolution and reform report that address the 
GNSO (DNSO).<br>
  .<br>
 ICANN's bottom-up model is relatively unique with specific supporting 
organisations, in particular the GNSO council, developing policy which the 
Board may adopt or return for reconsideration.   The scope of the review should 
articulate the uniqueness of ICANN's  model and an independent reviewer would 
need to be directed and grounded in  the approach. <br>
 <br>
Concern was expressed about using terms such as, &quot;fairness&quot;, 
&quot;appropriateness&quot;, &quot;sufficient&quot; without tieing some 
criteria or stipulating, through the TOR, that the reviewer should be explicit 
in their choice, identification of and rational for comparators.<br>
Specific words  such as, &quot;fairness&quot; were in fact included in the 
bylaws, and terms could be defined as the work progresses.<br>
If the word &quot;fairness&quot; would be used in a submission to the Board, 
there should be an explanation of how it could be replaced and what was sought 
to be seen to be &quot;fair&quot;.<br>
<br>
  Measuring perception  and  focusing on the  GNSO's capability to support the 
concepts of fairness were different. Examine whether there are  structures in 
place that supported  those objectives such as,  policies and processes, rather 
than analysing or trying to quantify if the GNSO as a body was acting fairly. 
<br>
  The bylaws make provision for new constituencies to be formed and yet since 
the inception of the DNSO, no constituencies have been formed. The question 
should be asked whether that capability exists and whether the current 
structure was optimal to forming new constituencies. There was great diversity 
in the constituencies that was not apparent to outsiders. The GNSO was 
inherently designed to accommodate  counterbalancing viewpoints and many ICANN 
participants had interests at stake. <br>
  The review should take into account that the GNSO coexists in a larger world 
with two other supporting organisations and an At Large Advisory Committee. <br>
  <br>
  In summary, the challenge of the work lies in the quality of the  methodology
  used to do the analysis, the tools and the measures.<br>
  <br>
  <strong>Item 3: Discuss the involvement of the GNSO constituencies in the 
review,<br>
and identify what information will be needed from the constituencies to<br>
assist the external review</strong></font><font face="Arial, Helvetica, 
sans-serif"><br>
</font><font face="Arial, Helvetica, sans-serif"><br>
<strong>Comments on Methodology</strong><br>
  Concerns were expressed with regard to  anonymity and confidentiality of 
input and the question was whether  transparency, a characteristic of the GNSO 
processes should continue. There was general agreement that people should be 
accountable for their  contributions.  and that there should be open dialogue. 
The aim was continual improvement and that required open dialogue contrary to 
anonymous submission which killed open and transparent discussion, one of 
ICANN's strengths.<br>
  <br>
  Statistical analysis was not desirable for the 
  nature of the organisation however methodology needed certain facts. It was 
generally agreed that verbal interviews produced more response, and that it was 
not necessary to record these interviews or produce a full transcript. Care 
should be taken when summarising recordings or transcriptions to ensure that 
they conformed to what the interviewee said. The interviewee should have the 
option to confirm the accuracy of any written summary of a verbal interview. 
<br>
  <br>
  In summary, the general objective was to ascertain the general understanding 
of the Review goal and the type of outcome desired.<br>
  <br>
  <strong>OAB </strong><br>
  Prepare for the interaction with the ICANN Board on 8 September 2005. <br>
  <br>
  <strong>Next steps: </strong><br>
  - Further input  from Council members and constituencies on the terms of 
reference by COB Monday 29 August, 2005  <br>
  - The   GNSO Council 20 recommendations included as part  of the terms of 
reference (TOR).<br>
  - Create a fresh draft TOR to be sent to Board in the current format for 
joint GNSO Council/ICANN Board discussion 8 September, 2005 <br>
  - Second draft  TOR to be published for public comment. <br> 
  <br>
  </font><font face="Arial, Helvetica, sans-serif"><b>Bruce Tonkin</b> 
<b>declared 
            the GNSO meeting closed and thanked everybody for participating.<br>
The meeting ended: 16: 10 CET. </b></font></p>
<ul>
  <li> 
    <p><font face="Arial, Helvetica, sans-serif"><b>Next GNSO Council 
</b><strong>Teleconference Thursday 1 September 2005 at 12:00 UTC. </strong><br>
        <strong>Topic: New TLDs </strong><br>
      see: <a href="http://gnso.icann.org/calendar/";>Calendar</a><br>
    </font></li>
</ul>
<p>&nbsp;</p>
<font face="Arial, Helvetica, sans-serif">
<!--#include virtual="/footer.shtml"--> 
</font>