<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=640532216-25072005><FONT face=Arial size=2>Dear
all,</FONT></SPAN></DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial size=2>Ahead of this week's
GNSO Council conference call(agenda item 2), please find below a summary of the
GNSO Public forum held in Luxembourg on 12 July.</FONT></SPAN></DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial size=2>All the best,
Maria</FONT></SPAN></DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=640532216-25072005><FONT face=Arial size=2>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; TEXT-ALIGN: center"
align=center><B style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Summary GNSO Public
Forum<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/><o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt; TEXT-ALIGN: center"
align=center><FONT size=3><?xml:namespace prefix = st1 ns =
"urn:schemas-microsoft-com:office:smarttags" /><st1:country-region
w:st="on"><st1:place w:st="on"><B style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond">Luxembourg</SPAN></B></st1:place></st1:country-region><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond">, 12
July 2005<o:p></o:p></SPAN></B></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Order of the meeting:<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT
size=3> </FONT></o:p></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.5in"><FONT
size=3><B style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond">1</SPAN></B><SPAN
style="FONT-FAMILY: Garamond"><SPAN
style="mso-tab-count: 1">
</SPAN>Overview from the chair of the Whois task force, Jordyn Buchanan on
developments since the last meeting in Mar del Plata (April 2005) and<SPAN
style="mso-spacerun: yes"> </SPAN>current and future issues for input from
the public forum.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT size=3><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond">2</SPAN></B><SPAN
style="FONT-FAMILY: Garamond"><SPAN
style="mso-tab-count: 1">
</SPAN>Open mike for comments on Whois work<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT size=3><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond">3</SPAN></B><SPAN
style="FONT-FAMILY: Garamond"><SPAN
style="mso-tab-count: 1">
</SPAN>Presentations from the chair of each of the constituencies of the GNSO
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT size=3><B
style="mso-bidi-font-weight: normal"><SPAN
style="FONT-FAMILY: Garamond">4</SPAN></B><SPAN
style="FONT-FAMILY: Garamond"><SPAN
style="mso-tab-count: 1">
</SPAN>Open mike for general comments<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>An email address was set up to allow
comments during and immediately after the public forum so that individuals had
more than one way to provide their input.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Most constituency statements are
available online at </FONT><A href="http://gnso.icann.org/"><FONT
size=3>http://gnso.icann.org/</FONT></A><FONT size=3> . <SPAN
style="mso-spacerun: yes"> </SPAN>This document summarises by topic the
discussion that took polace during the open mike session.<SPAN
style="mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Alternative enforcement mechanisms/graded
sanctions<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Jordyn Buchanan (Chair, WHOIS Task
Force; <st1:place w:st="on"><st1:City w:st="on">Register.com</st1:City>,
<st1:country-region w:st="on">USA</st1:country-region></st1:place>) encouraged
the GNSO to take up a policy development process to create enforcement
mechanisms in ICANN’s contracts to give the new compliance hires tools other
than terminating contracts. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin (Chair, GNSO Council;
Melbourne IT, <st1:country-region w:st="on"><st1:place
w:st="on">Australia</st1:place></st1:country-region>) agreed and noted that the
topic had been under council discussion for some time. The council would work
cooperatively with ICANN operational staff to see if there are sufficient
resources for a policy effort in that regard and also to provide suggestions to
start that process. The council would seek staff input on what sanctions would
be useful and then institute a PDP. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Support for GNSO Public Forum<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Two speakers – Thomas Roessler (W3C,
<st1:country-region w:st="on">Luxembourg</st1:country-region>) and Mark McFadden
(Secretary of the ISPCP Constituency; <st1:place w:st="on"><st1:City
w:st="on">University of Wisconsin</st1:City>, <st1:country-region
w:st="on">USA</st1:country-region></st1:place>) welcomed the open mike aspect of
the Public Forum and hoped it would become a regular feature.<SPAN
style="mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin responded with thanks
and said that the comments made during the public forum would be summarized and
presented to the board’s own public forum.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>.NET agreement<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bhavin Turakhia (Chair, Registrars
Constituency; <st1:place w:st="on"><st1:City
w:st="on">LogicBoxes.com</st1:City>, <st1:country-region
w:st="on">India</st1:country-region></st1:place>) said the .NET agreement was
not consistent with the PDP on the process for introducing new registry service
being dealt with by the GNSO.<SPAN style="mso-spacerun: yes"> </SPAN>He
hoped that the .NET agreement could be re-opened and modified and also that the
GNSO process is not undermined particularly regarding .COM and other registries
to which it should be applied.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Becky Burr (Independent consultant,
<st1:country-region w:st="on"><st1:place
w:st="on">USA</st1:place></st1:country-region>) said that she had represented
two sTLD applicants and had in this capacity done a comparison of the .MOBI and
.NET contr5acts to see if .NET had received any extra concessions.<SPAN
style="mso-spacerun: yes"> </SPAN>Aside from the price cap issue, the
modifications regarding consensus policy are inherent in the contract itself and
do nothing to change it.<SPAN style="mso-spacerun: yes"> </SPAN>Verisign
did not get anything that mobi or jobs didn’t get. The limitations there are
limitations on the fundamental bargain which is the definition of a consensus
policy.<SPAN style="mso-spacerun: yes"> </SPAN>Modifying the standards for
consideration of proposed registry services is not within the itemized list of
topics which may be the subject of policy making.<SPAN
style="mso-spacerun: yes"> </SPAN>Unless an issue goes to the stability
and security of the internet, it’s not going to be within the scope of consensus
policies.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin responded that there
were certainly differences about the merits of particular changes, and that not
all the changes that surprised people were material changes. The issue had been
that the changes were a surprise and there had been no opportunity to hear input
such as Becky’s.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><I
style="mso-bidi-font-style: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Later in the public forum the .NET issue was returned
to:<o:p></o:p></FONT></SPAN></I></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><I
style="mso-bidi-font-style: normal"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT
size=3> </FONT></o:p></SPAN></I></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Becky Burr said she understood
concerns about process but said that the difference between the contract posted
for public comment and the final contract was due to the critical process of
negotiating the contract.<SPAN style="mso-spacerun: yes"> </SPAN>If ICANN
had to publish a contract before it, get comments on it and award only that
contract, their hands would be tied in a negotiating sense.<SPAN
style="mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Jordyn Buchanan responded that this
was separate from posting material changes for review by the community prior to
the signature of the contract and acceptance by the board.<SPAN
style="mso-spacerun: yes"> </SPAN>It seems reasonable that final copies of
contracts be posted for community review prior to their signature as opposed to
posting a draft agreement that may be subject to significant changes.<SPAN
style="mso-spacerun: yes"> </SPAN>Regarding substance, many of the changes
made were ultimately not significant, but one of them – the limitation to apply
a consensus policy to registry services approval process – seems crazy to
suggest that it’s not a substantive change, especially as the GNSO Council has a
PDP underway on that very issue.<SPAN style="mso-spacerun: yes">
</SPAN>That PDP was also initiated at the request of ICANN staff so it is
bizarre to suggest now that somehow that’s not a policy issues.
<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin said that he had asked
ICANN’s general counsel to answer a question in the Council meeting to follow
about whether there should have been a PDP or not. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Marilyn Cade said that her memory was
that consensus policy, i.e. a requirement of consensus policy in order to change
contracts, was developed in order to ensure that burdensome policies not be
applied to the contracted parties without consensus policy.<SPAN
style="mso-spacerun: yes"> </SPAN>Change meant that in representing
business users there were safeguards in the ability to trust that no significant
changes would happen to protect users as well as affected parties. Any change in
the role or capability of consensus policy would be extremely troubling.
<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bret Fausett asked Becky Burr about
the value of having different registries subjected to different consensus
policies.<SPAN style="mso-spacerun: yes"> </SPAN>Or, if it’s the same
consensus policy, then why not move to some standardized
language?<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Becky Burr responded that we do have
standardized language about consensus policy and Marilyn seemed to be talking
about the pricing cap issue which should be taken off the table.<SPAN
style="mso-spacerun: yes"> </SPAN>The definition of consensus policy is in
the bylaws, and in addition to that is a definition of security and
stability.<SPAN style="mso-spacerun: yes"> </SPAN>Verisign had a
contractual limitation about consensus policy in its contract, including the
.NET contract, that was much narrower. We need to distinguish between policy and
consensus policy.<SPAN style="mso-spacerun: yes"> </SPAN>ICANN can develop
any policy it wants that applies to the way it operates – it can’t call all of
them consensus policies.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin said the changes had not
been explained by ICANN staff and suggested drawing a distinction between the
concern about process and whether the changes had merit or not.<SPAN
style="mso-spacerun: yes"> </SPAN>There is a difference between policy and
consensus policy. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3><SPAN style="mso-spacerun: yes"> </SPAN>Best practices/outreach and
information regarding string length of TLDs<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Ken Fockler (independent consultant,
<st1:place w:st="on"><st1:country-region
w:st="on">Canada</st1:country-region></st1:place>) asked if the GNSO was the
appropriate body to deal with doing outreach and education on string length
where (e.g. .info and .museum) the TLD string is longer than three
characters.<SPAN style="mso-spacerun: yes"> </SPAN>Ken asked if the issue
was a concern of the GNSO, whether it should be raised again and if it was still
a problem. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin responded that as
ICANN’s budget grows, so does the expectation for services such as information
and awareness raising on issues like this and also IDNs.<SPAN
style="mso-spacerun: yes"> </SPAN>He hoped the GNSO could create a best
practices area on its website that would spread information on issues like this
to application developers. <SPAN style="mso-spacerun: yes"> </SPAN>The
issues was of relevance and importance to the GNSO and had been analysed to some
degree by the ISPCP constituency. <SPAN
style="mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Tony Holmes (Council member, ISPCP
Constituency, British Telecom, <st1:country-region w:st="on"><st1:place
w:st="on">UK</st1:place></st1:country-region>) said that ISPs had taken part in
the dialogue that tried to resolve the problem but that it was difficult because
there wasn’t a particular body or trade association in the software world to get
the message out to.<SPAN style="mso-spacerun: yes"> </SPAN>The problem has
reduced, but more through osmosis than any particular action.<SPAN
style="mso-spacerun: yes"> </SPAN>Additional support is needed to get the
message of how to treat longer string length TLDs.<SPAN
style="mso-spacerun: yes"> </SPAN>This is a good time to discuss posting
this information on the ICANN website with ICANN
staff.<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bruce Tonkin suggested tying the
website work in as a specific measure to be undertaken in response to the
operational plan’s general aim to improve the website.<SPAN
style="mso-spacerun: yes"> </SPAN>He invited people to think about what
other elements could be included. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Bret Fausett (ALAC liaison to the
GNSO Council, <st1:country-region w:st="on"><st1:place
w:st="on">USA</st1:place></st1:country-region>) recalled that ICANN had issued
an advisory on the string length issue several years ago and suggested that
announcements of new TLDs (exceeding 3-letter strings) be accompanied by this
initial advisory.<SPAN style="mso-spacerun: yes"> </SPAN>This would keep
improving awareness of the issue.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Ken Stubbs (Registry Constituency
member of GNSO Council; <st1:place w:st="on"><st1:City
w:st="on">Afilias</st1:City>, <st1:country-region
w:st="on">USA</st1:country-region></st1:place>) said ICANN should work more
closely with the educational community in providing seminars for educators as
well as material in that area.<SPAN style="mso-spacerun: yes">
</SPAN>Relevant consortiums and trade associations might be identified and given
a point of contact at ICANN where a specific programme can be rolled
out.<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Tony Harris (ISPCP Constituency
member of the GNSO Council; CABASE, <st1:country-region w:st="on"><st1:place
w:st="on">Argentina</st1:place></st1:country-region>) suggested comptia.org as
one such association.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Maria Zitkova (Chair of Registry
Constituency; SITA, <st1:country-region
w:st="on">Switzerland</st1:country-region>) said she had been involved with the
issue and that following the <st1:City w:st="on"><st1:place w:st="on">Mar del
Plata</st1:place></st1:City> meeting, IANA published a list of all existing TLDs
on the IANA website in a simple text format that is downloadable by
applications.<SPAN style="mso-spacerun: yes"> </SPAN>This could also be
pointed to in any announcements.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Tony Holmes said the issue of
awareness should be prioritized with greater urgency than the category of
updating the website and posting additional information.<SPAN
style="mso-spacerun: yes"> </SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Strategic planning and operational
planning<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Mark McFadden said that there had
been in the past six months a significant partnership between the community and
the staff on strategic planning but that this had broken down in recent
weeks.<SPAN style="mso-spacerun: yes"> </SPAN>He asked the council to
respond to that breakdown and talk about how it will be repaired. He asked
councilors other than those involved in that partnership to speak to the issue.
<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Marilyn Cade responded to echo Mark’s
comment and note that the council take seriously the need to partner with staff
to continue the improvements to the process brought about in <st1:City
w:st="on"><st1:place w:st="on">Amsterdam</st1:place></st1:City> and after.<SPAN
style="mso-spacerun: yes"> </SPAN>The council should return to its
thinking that led to generating the <st1:City w:st="on"><st1:place
w:st="on">Amsterdam</st1:place></st1:City> forum on the strategic plan and
reestablish that leadership work within the cross supporting orgnaisation work
and work with the staff.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>The <st1:country-region w:st="on"><st1:place
w:st="on">US</st1:place></st1:country-region> Dept. of Commerce’s statement on
the relationship between ICANN and the USG<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Milton Mueller (Chair of the
Non-Commercial Constituency; <st1:place w:st="on"><st1:City w:st="on">Syracuse
University</st1:City>, <st1:country-region
w:st="on">USA</st1:country-region></st1:place>) asked if the council had any
reaction to or would like to express an opinion on the US Dept. of Commerce’s
recent statement. <o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>No Council member responded.
<o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B
style="mso-bidi-font-weight: normal"><SPAN style="FONT-FAMILY: Garamond"><FONT
size=3>Structural problems with ICANN<o:p></o:p></FONT></SPAN></B></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Ross Rader (Registrar Constituency
member of the GNSO Council; <st1:place w:st="on"><st1:City
w:st="on">Tucows</st1:City>, <st1:country-region
w:st="on">Canada</st1:country-region></st1:place>) asked Milton Mueller to
enlarge on his statement during the constituency reports that ICANN had
structural problems.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT size=3> </FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><FONT size=3>Milton Mueller said he meant the
tension between staff and GNSO regarding what is policy and what is part of the
contract.<SPAN style="mso-spacerun: yes"> </SPAN>There has always been an
intense amount of ambiguity, going very far back and the issue recurs every time
a significant policy decision is made. <st1:City w:st="on"><st1:place
w:st="on">Milton</st1:place></st1:City> had frequently viewed the staff as
having too much latitude to ignore policy directives from below – even though
ICANN promotes itself as a bottom-up organization -<SPAN
style="mso-spacerun: yes"> </SPAN>sometimes viewing that as cynical and
others as inherent to the structure of ICANN that management has certain
incentives while the GNSO has others. Bringing that back to the WSIS discussion,
there is not a clear separation – despite the report – that governments do
public policy and the private sector and civil society do technical
coordination.<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></FONT></SPAN></P>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-FAMILY: Garamond"><o:p><FONT
size=3> </FONT></o:p></SPAN></P></FONT></SPAN></DIV></BODY></HTML>