<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] GNSO Council revised draft minutes 28 Nov. 05
- To: council@xxxxxxxxxxxxxx
- Subject: [council] GNSO Council revised draft minutes 28 Nov. 05
- From: "GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 14:23:25 +0100
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
[To: council[at]gnso.icann.org]
Dear Council Members,
Please find the revised draft minutes of the GNSO Council meeting held
in Vancouver on 28 November 2005.
Liz Williams has been added to the list of attendees.
I apologise for the version that is currently on the Council list, this
version will be easier to read.
Please let me know what other changes you would like made.
Thank you very much.
Kind regards,
Glen
--
Glen de Saint Géry
GNSO Secretariat - ICANN
gnso.secretariat[at]gnso.icann.org
http://gnso.icann.org
--- Begin Message ---
- Subject:
- From: <Enregistré par Microsoft Internet Explorer 5>
- Date: Wed, 21 Dec 2005 14:16:09 +0100
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--#set var="bartitle" value="GNSO Council Vancouver Meeting
Minutes"--><!--#set var="pagetitle" value="GNSO Council Vancouver Meeting
Minutes"--><!--#set var="pagedate" value="28 November 2005"--><!--#set
var="bgcell" value="#ffffff"--><!--#include virtual="/header.shtml"--><!--#exec
cmd="/usr/bin/perl /etc/gnso/menu.pl 'GNSO Council Vancouver Meeting
Minutes'"--><HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<P><FONT face="Arial, Helvetica, sans-serif">28 November 2005 </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">Proposed <A
href="http://gnso.icann.org/meetings/agenda-28nov05.shtml";>agenda and related
documents</A> </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><B>List of
attendees:</B><BR>Philip
Sheppard - Commercial & Business Users C. <BR>Marilyn Cade - Commercial
& Business Users C. <BR>Grant Forsyth - Commercial & Business Users C -
remote participation <BR>Greg Ruth - ISCPC - absent - apologies - proxy to Tony
Holmes<BR>Antonio Harris - ISCPC - proxy to Tony Holmes (joined meeting after
roll call) <BR>Tony Holmes - ISCPC<BR>Thomas Keller- Registrars <BR>Ross Rader
-
Registrars (joined meeting after roll call) <BR>Bruce Tonkin - Registrars
<BR>Ken Stubbs - gTLD registries<BR>Philip Colebrook - gTLD registries - remote
participation <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 - apologies - proxy to Niklas Lagergren
<BR>Robin
Gross - Non Commercial Users C.- remote participation <BR>Norbert Klein - Non
Commercial Users C.<BR>Alick Wilson - Nominating Committee appointee - remote
participation <BR>Maureen Cubberley - Nominating Committee appointee<BR>Avri
Doria - Nominating Committee appointee </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">17 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>Tina Dam - Chief gTLD Registry Liaison <BR>Diane
Schroeder - General Manager, Conferences, Administration & Finance <BR>Glen
de Saint Géry - GNSO Secretariat <BR><BR><BR><B>GNSO Council
Liaisons</B><BR>Suzanne Sene - GAC Liaison - absent - apologies <BR>Bret
Fausett
- acting ALAC Liaison - absent - apologies <BR><BR>Michael Palage - ICANN Board
member - absent - apologies <BR>Quorum present at 9: 12 PST.<BR><BR>Two MP3
recordings of the second part of the meeting (not very clear) <BR><A
class=moz-txt-link-freetext
href="http://gnso-audio.icann.org/GNSO-Council20051122.mp3";>http://gnso-audio.icann.org/GNSO-Council20051122.mp3</A>
<BR><A class=moz-txt-link-freetext
href="http://gnso-audio.icann.org/GNSO2-20051122;MP3.mp3";>http://gnso-audio.icann.org/GNSO2-20051122;MP3.mp3</A>
<BR><BR><BR><B>Bruce Tonkin</B> and <STRONG>Philip Sheppard</STRONG> chaired
this teleconference. <BR><BR><STRONG>Approval of
Agenda</STRONG><BR><BR><STRONG>Diane Schroeder</STRONG> addressed the meeting
informing the Council of an important time modification to the schedule for the
GNSO Public Forum and GNSO Council meeting on Friday 2 December 2005 in
Vancouver.<BR><BR><STRONG>Marilyn Cade</STRONG> proposed ending the meeting
early to prepare for the joint meeting with the ICANN Board in the afternoon.
<BR><BR><STRONG>Ken Stubbs</STRONG>, seconded by <STRONG>Marilyn Cade</STRONG>
proposed <STRONG>Philip Sheppard </STRONG>as chair for the election
process.<BR><BR>Motion carried unanimously<BR><STRONG>Decision 1: Philip
Sheppard chaired the GNSO Council meeting for the election process.
<BR><BR>I<FONT size=3>tem 3: Election of GNSO Council chair <BR>- Bruce Tonkin
has been nominated and seconded <BR>- term from 18 Nov 2005 until one month
after 2005 AGM (4 Jan 2006)</FONT></STRONG></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Philip Sheppard</STRONG>
proposed: <BR>Whereas Bruce Tonkin had been nominated by Ken Stubbs and
seconded
by Ross Rader as GNSO Council chair for the period from 18 November 2005 until
one month after 2005 AGM (4 January 2006)<BR>Recommended that Bruce Tonkin be
elected as GNSO Council chair for the period 18 November 2005 until one month
after the 2005 ICANN Annual General Meeting (4 January 2006). </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Philip Sheppard</STRONG>
called for a formal roll call vote.<BR><BR>The motion carried
unanimously.<BR>No
vote was recorded for Tony Harris who joined the meeting late. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Decision 2: Bruce Tonkin
was elected as GNSO Council chair for the period 18 November 2005 until one
month after the 2005 ICANN Annual General Meeting (4 January 2006).
</STRONG></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Philip Sheppard</STRONG>
formally handed the chair to <STRONG>Bruce Tonkin</STRONG>.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Item 4: Approval of
minutes<BR>- GNSO Council teleconference - 13 October 2005<BR>- GNSO Council
teleconference - 20 October 2005</STRONG></FONT><BR><BR><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Maureen Cubberley </STRONG>moved
the
adoption of the minutes.<BR>The motion carried. Niklas Lagergren
abstained</FONT><BR><BR><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Decision 3: The GNSO Council
minutes
of 13 October 2005 and 20 October 2005 were
adopted</STRONG></FONT>.<BR><BR><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Item 5: Evaluation of new gtlds
(.biz, .info etc as well as .travel,<BR>.jobs. .mobi etc)<BR>- <A
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01519.html";>update
on questions to structure the evaluation</A></STRONG></FONT><BR><BR><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Olof Nordling</STRONG> commented
that the </FONT><FONT face="Arial, Helvetica, sans-serif"><A
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01519.html";>document
</A>elaborated the need for further evaluation of recently introduced gTLDs and
proposed an approach for this, focused to inform ongoing work on policy aspects
regarding the introduction of new gTLDs. <BR>Discussions on an evaluation of
the
ongoing sTLD round were under way with the consultant that performed the main
evaluation of the “proof-of-concept” round for ICANN. It was recommended that
the GNSO Council stated that questions relating to selection criteria,
allocation methods and contractual conditions were of particular relevance in
this context. The document proposed a draft list of questions to this
end.<BR>The report was designed to give the GNSO Council the information
necessary to discuss and decide on ways to proceed with additional evaluation
aspects of assigned new TLDs. <BR><BR></FONT><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Maureen Cubberley </STRONG>referred
to page 8 of the <A
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01519.html";>report,</A>
'consideration for additional review', and commented that there was a need for
emphasis on the process of decision making that informed the evaluation. It was
essential to look at the content of the recent Request for Proposals (RFP) for
the sponsored round of gTLDs </FONT>.<BR><STRONG><BR><FONT
face="Arial, Helvetica, sans-serif">Bruce Tonkin</FONT></STRONG><FONT
face="Arial, Helvetica, sans-serif"> pointed out that the new gTLD process was
under discussion, and that the evaluation was driven by a process several years
ago. There were two issues, one, how to improve the process and the second,
should new gTLDs be introduced. <BR><BR><STRONG>Marilyn Cade</STRONG> noted
from
the Business Constituency’s perspective, that clear guidance was given for the
recent round of gTLDs to be sponsored. Sponsored was discussed in depth yet
there appeared to be a limited match in the case of some of the applicants.
Further guidance and criteria on ‘sponsored’was required.
<BR><BR><STRONG>Maureen Cubberley</STRONG> commented that ambiguities in the
RFP
led to the issue.<BR><BR><STRONG>Bruce Tonkin</STRONG> proposed that the
project
manager (Miriam Sapiro) produce a ‘lessons learnt’ paper, a quick follow up of
the report in terms of the outcome, which should not be wider but intended as
input to a subsequent wider process and that an "independent external review"
be
carried out by someone different from the project
manager.<BR><BR><STRONG>ACTION
</STRONG><BR>Council was encouraged to examine the list of questions and
provide
further questions to Miriam Sapiro. <BR>Further it was suggested that Miriam
Sapiro do a presentation at the GNSO Public Forum on Friday 2 December 2005.
<BR><BR><STRONG>Item 6: Policy Development Process for new gtlds<BR>- discuss
issues report<BR>- decide whether to commence a
PDP</STRONG><BR><BR><STRONG>Bruce Tonkin</STRONG> referred to the ICANN <A
href="http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#AnnexA";>Bylaws</A>.
<BR>Section 2. Creation of the Issue Report <BR></FONT><FONT
face="Arial, Helvetica, sans-serif">Within fifteen (15) calendar days after
receiving either (i) an instruction from the Board; (ii) a properly supported
motion from a Council member; or (iii) a properly supported motion from an
Advisory Committee, the Staff Manager will create a report (an "Issue Report").
Each Issue Report shall contain at least the following:<BR>Section 2. Creation
of the Issue Report had been completed<BR><BR></FONT><FONT
face="Arial, Helvetica, sans-serif">Section 2 e. A recommendation from the
Staff
Manager as to whether the Council should initiate the PDP for this issue (the
"Staff Recommendation"). Each Staff Recommendation shall include the opinion of
the ICANN General Counsel regarding whether the issue proposed to initiate the
PDP is properly within the scope of the ICANN policy process and within the
scope of the GNSO. In determining whether the issue is properly within the
scope
of the ICANN policy process, the General Counsel shall examine whether such
issue:<BR><BR>The staff manager, Olof Nordling had recommended that a PDP be
initiated.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Bruce Tonkin
</STRONG>proposed</FONT> <FONT face="Arial, Helvetica, sans-serif">that at the
current meeting the Council vote to commence a PDP.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Marilyn Cade</STRONG>,
seconded by <STRONG>Tom Keller</STRONG> proposed: <BR>Whereas, the GNSO Council
recognises that the review of the GNSO Council held in 2004 recommended that
the
PDP timelines be reviewed.<BR>The GNSO votes to initiate the PDP on new gTLDs.
The GNSO will develop a work program in consultation with the ICANN staff and
ICANN board that sets out a timeframe for work<BR><BR>The vote was by show of
hands. <BR>The motion carried unanimously. No abstentions
<BR><BR><STRONG>Decision 4: <BR>Whereas, the GNSO Council recognises that the
review of the GNSO Council held in 2004 recommended that the PDP timelines be
reviewed.<BR>The GNSO votes to initiate the PDP on new gTLDs. The GNSO will
develop a work program in consultation with the ICANN staff and ICANN board
that
sets out a timeframe for work<BR></STRONG></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Item 7: <A
href="http://gnso.icann.org/issues/tf-final-rpt-25oct05.htm";>WHOIS: <B>Final
task force report on a policy recommendation and advice on a procedure for
handling conflicts between a registrar/registry's legal obligations under
privacy laws and their contractual obligations to ICANN </B></A><BR><BR>- vote
on final recommendation as completed by the WHOIS task force on<BR>19
Oct</STRONG><BR><STRONG>Bruce Tonkin</STRONG> noted that the "advice" as set
forth was not consensus policy.<BR><STRONG>Niklas Lagergren</STRONG> stated
that
the task force Final Report was supported unanimously by the WHOIS task
force.<BR><STRONG>Ross Rader</STRONG>, a member of the task force raised a
procedural question that after the task force had already voted on the final
report, it should be made precise that reference was to the gTLD WHOIS service
and did not refer to the protocol, the RIR WHOIS service or the country code
WHOIS service. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Tom Keller
</STRONG>seconded by <STRONG>Niklas Lagergren</STRONG> proposed
that:<BR><BR></FONT><FONT face="Arial, Helvetica, sans-serif">The GNSO votes in
favour of the following consensus policy recommendation from the WHOIS task
force <BR><B><A
href="http://gnso.icann.org/issues/tf-final-rpt-25oct05.htm";>CONSENSUS POLICY
RECOMMENDATION</A></B> </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">In order to facilitate
reconciliation of any conflicts between local/national mandatory privacy laws
or
regulations and applicable provisions of the ICANN contract regarding the
collection, display and distribution of personal data via the gTLD Whois
service, ICANN should: </FONT></P>
<OL>
<LI>
<P><FONT face="Arial, Helvetica, sans-serif">Develop and publicly document a
procedure for dealing with the situation in which a registrar or registry can
credibly demonstrate that it is legally prevented by local/national privacy
laws or regulations from fully complying with applicable provisions of its
ICANN contract regarding the collection, display and distribution of personal
data via the gTLD WHOIS service. </FONT></P>
<LI>
<P><FONT face="Arial, Helvetica, sans-serif">Create goals for the procedure
which include: </FONT></P>
<OL type=a>
<LI><FONT face="Arial, Helvetica, sans-serif">Ensuring that ICANN staff is
informed of a conflict at the earliest appropriate juncture; </FONT>
<LI><FONT face="Arial, Helvetica, sans-serif">Resolving the conflict, if
possible, in a manner conducive to ICANN's Mission, applicable Core Values
and the stability and uniformity of the Whois system; </FONT>
<LI><FONT face="Arial, Helvetica, sans-serif">Providing a mechanism for the
recognition, if appropriate, in circumstances where the conflict cannot be
otherwise resolved, of an exception to contractual obligations to those
registries/registrars to which the specific conflict applies with regard to
collection, display and distribution of personally identifiable data via
the
gTLD WHOIS service; and </FONT>
<LI><FONT face="Arial, Helvetica, sans-serif">Preserving sufficient
flexibility for ICANN staff to respond to particular factual
</FONT></LI></OL></LI></OL>
<P><FONT face="Arial, Helvetica, sans-serif">The GNSO recommends the ICANN
staff
consider the advice given in the task force report as to a recommended
procedure.</FONT><FONT face="Arial, Helvetica, sans-serif"><BR><BR></FONT><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Bruce Tonkin </STRONG>called for
formal roll call vote.<BR><BR></FONT><FONT
face="Arial, Helvetica, sans-serif">The motion carried.<BR>26 Votes in support
<BR><BR>Abstention from </FONT><FONT face="Arial, Helvetica, sans-serif">Avri
Doria:<BR>Reason: Does not believe goes far enough in protecting privacy
</FONT><FONT face="Arial, Helvetica, sans-serif"></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Decision 5
</STRONG></FONT><STRONG><BR><FONT face="Arial, Helvetica, sans-serif">The GNSO
votes in favour of the following consensus policy recommendation from the WHOIS
task force <BR><A
href="http://gnso.icann.org/issues/tf-final-rpt-25oct05.htm";>CONSENSUS POLICY
RECOMMENDATION</A> </FONT></STRONG></P>
<P><STRONG><FONT face="Arial, Helvetica, sans-serif">In order to facilitate
reconciliation of any conflicts between local/national mandatory privacy laws
or
regulations and applicable provisions of the ICANN contract regarding the
collection, display and distribution of personal data via the gTLD WHOIS
service, ICANN should: </FONT></STRONG></P>
<OL>
<LI>
<P><STRONG><FONT face="Arial, Helvetica, sans-serif">Develop and publicly
document a procedure for dealing with the situation in which a registrar or
registry can credibly demonstrate that it is legally prevented by
local/national privacy laws or regulations from fully complying with
applicable provisions of its ICANN contract regarding the collection, display
and distribution of personal data via the gTLD WHOIS
service.</FONT></STRONG></P>
<LI>
<P><STRONG><FONT face="Arial, Helvetica, sans-serif">Create goals for the
procedure which include: </FONT></STRONG></P>
<OL type=a>
<LI><STRONG><FONT face="Arial, Helvetica, sans-serif">Ensuring that ICANN
staff is informed of a conflict at the earliest appropriate juncture;
</FONT></STRONG>
<LI><STRONG><FONT face="Arial, Helvetica, sans-serif">Resolving the
conflict, if possible, in a manner conducive to ICANN's Mission, applicable
Core Values and the stability and uniformity of the Whois system;
</FONT></STRONG>
<LI><STRONG><FONT face="Arial, Helvetica, sans-serif">Providing a mechanism
for the recognition, if appropriate, in circumstances where the conflict
cannot be otherwise resolved, of an exception to contractual obligations to
those registries/registrars to which the specific conflict applies with
regard to collection, display and distribution of personally identifiable
data via the gTLD WHOIS service; and </FONT></STRONG>
<LI><STRONG><FONT face="Arial, Helvetica, sans-serif">Preserving sufficient
flexibility for ICANN staff to respond to particular factual
</FONT></STRONG></LI></OL></LI></OL>
<P><STRONG><FONT face="Arial, Helvetica, sans-serif">The GNSO recommends the
ICANN staff consider the advice given in the task force report as to a
recommended procedure.<BR><BR></FONT></STRONG><FONT
face="Arial, Helvetica, sans-serif"><STRONG>Item 8: Policy development for
IDNs<BR>- <A
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01480.html";>discuss
background document</A><BR>- decide whether to formally request an issues
report<BR>section 1 - Raising an Issue<BR>section 2 - Creation of the Issue
Report</STRONG></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Bruce Tonkin
</STRONG>referred to the <A
href="http://www.gnso.icann.org/mailing-lists/archives/council/msg01480.html";>background
document </A>which listed the existing resolutions, workshops, and information
on the President’s Advisory Committee, of which Cary Karp was a member, and
suggested that the GNSO request the staff to produce an issues report on the
policy issues using the document as a basis.<BR></FONT><FONT
face="Arial, Helvetica, sans-serif">Bruce added that there should be clarity
for
the community what the policy aspects for the GNSO were.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Cary Karp</STRONG>
commented that attention should not only be to constrain 2nd level of the DNS,
the top level and the 3rd and 4th level of the DNS should also be considered.
If
control was invoked as a term of delegation the domain space could not be
policed, which means that anything not permitted should be folded into the
underlying possible standards. The first generation would be a normative
framework that expected anything to be done but allowed policy constraint to
guide. <BR><STRONG>Cary</STRONG> further clarified that internationalization
meant changing the system to make it useable in the polyglot world we live in
while making it work with Cambodia, for example, is localization. An Arabic
version of.com is a localization. The concern is the translated versions of the
gtld labels. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">Discussion followed on the motion
to be drafted. Due to the complexity of the topic and in order for constituency
discussion,<STRONG> Bruce Tonkin </STRONG>proposed tabling the following motion
to be voted on at the GNSO Council meeting on Friday 2 December
2005:<BR></FONT><BR><FONT face="Arial, Helvetica, sans-serif">Tabled
motion:</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">WHEREAS, the GNSO Council
recognises that one of the goals of ICANN to increase the internationalisation
of the domain name space.<BR></FONT><FONT
face="Arial, Helvetica, sans-serif">WHEREAS, the GNSO Council wishes to liaise
closely with the ccNSO with respect to the issue of localised IDN equivalents
of
existing gTLDs and ccTLDs, and for the purpose of jointly requesting an issues
report. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">The GNSO Council requests that the
staff produce an issues report on the policy issues associated with creating
internationalised equivalents of existing gTLDs, and second level domains
within
existing gTLDs. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">The GNSO also requests that the
staff liaise with the ccNSO to ensure that the policy issues associated with
internationalised versions of the existing ccTLDs can also be
considered.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Bruce Tonkin</STRONG>
proposed revisiting the process of the PDP on new gTLDs. and outlined the
proposed work:<BR></FONT><FONT face="Arial, Helvetica, sans-serif">January to
June <BR>- PDP on New gTLDs<BR>- PDP on IDNs<BR>- WHOIS task force - considered
to drain a lot of resources<BR><BR><STRONG>Bruce Tonkin</STRONG> noted that
with
respect to issues such as WHOIS that will likely need to evolve over several
years, it may be more efficient to spend a limited time on the issue each year,
rather than tie up GNSO community and staff resources for the whole year, e.g.
each year concentrate 3 months on an issue and spend 2 days face to face, then
leave it alone and pick it up again. </FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif">There was general agreement on:
</FONT><FONT face="Arial, Helvetica, sans-serif"><BR>- scheduling new gTLDs
work
program with significant face to face interaction time. <BR>- using new
technologies, such as wikis and blogs to encourage community participation<BR>-
setting up a group outside Council with expertise to support running a wiki on
the new gTLD issues for the community beyond the council. <BR></FONT><FONT
face="Arial, Helvetica, sans-serif">- creating a structured mechanism to gather
data </FONT><BR><BR><FONT face="Arial, Helvetica, sans-serif"><STRONG>Bruce
Tonkin</STRONG> recommended that the Council as a whole deal with the new gTLD
PDP using mailing lists, wiki, and a 2 day face to face meeting. Each new
effort
should take into account the GNSO Council review recommendations looking at
what
has gone before and what can be improved.<BR>The proposed IDN PDP would be
managed by a task force of experts and the constituencies should work on
identifying new people with particular skills.</FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><STRONG>Agenda Item
deferred:<BR>Item 8: WHOIS task force<BR>- progress on purpose and definitions
of contacts</STRONG></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><B>Bruce Tonkin</B> <B>declared
the
GNSO meeting closed and thanked everybody for participating.</B></FONT></P>
<P><FONT face="Arial, Helvetica, sans-serif"><B>The meeting ended: 11: 45 PST.
</B></FONT></P>
<UL>
<LI>
<P><FONT face="Arial, Helvetica, sans-serif"><B>Next GNSO Council meeting
</B><STRONG>in Vancouver, Friday 2 December 2005 at 10:30 PST
</STRONG><BR>see: <A
href="http://gnso.icann.org/calendar/";>Calendar</A></FONT><FONT
face="Arial, Helvetica, sans-serif"><BR></FONT></P></LI></UL>
<P> </P><FONT face="Arial, Helvetica, sans-serif"><!--#include
virtual="/footer.shtml"--></FONT></BODY></HTML>
--- End Message ---
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|