<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] GNSO Council draft minutes-28 November 05
- To: council@xxxxxxxxxxxxxx
- Subject: [council] GNSO Council draft minutes-28 November 05
- From: "GNSO.SECRETARIAT@xxxxxxxxxxxxxx" <gnso.secretariat@xxxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 11:29:08 +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 draft minutes of the GNSO Council meeting held in
Vancouver on 28 November 2005.
Please let me know what 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
<!--#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'"-->
<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>
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> </li>
</ul>
<p> </p>
<font face="Arial, Helvetica, sans-serif">
<!--#include virtual="/footer.shtml"-->
</font>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|