<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Wolf,<div><br></div><div>Just seen your message after responding to Steve's message in which I explained that I was copying you and Jeff so that you could each get feedback from your respective houses, but that for obvious reasons of confidentiality, I was not sending Steve's message to a public list such as the GNSO's before he says it's final and OK to be released.</div><div><br></div><div>So I think it's unfortunate that you have just done so.</div><div><br></div><div>The Council VCs are true representatives of their houses and I think there are times when you should act as direct conduits for any communication coming into the Council to each house.</div><div><br></div><div>I feel that in order to maintain good levels of trust and cooperation with others, there are times when the VCs should operate in this manner and that is why I ask you both to do in my earlier message.</div><div><br></div><div>Just wanted to clarify that. Thanks. I am not responding on the actual main part of your message, as I think you are absolutely correct to state your views and engage others. I just wish it had been done as an internal house discussion at this early stage.</div><div><br></div><div>Thanks,</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Stéphane Van Gelder<br>Directeur Général / General manager<br>INDOM Group NBT France</div><div>----------------<br>Head of Domain Operations</div></div><div>Group NBT</div></div></span></div></span></div></span></div></span></span>
</div>
<br><div><div>Le 11 mai 2012 à 08:21, <<a href="mailto:KnobenW@telekom.de">KnobenW@telekom.de</a>> <<a href="mailto:KnobenW@telekom.de">KnobenW@telekom.de</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=us-ascii" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19190">
<div style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<div dir="ltr" align="left"><font size="2" face="Arial"><span class="629595005-11052012">FYI.</span></font></div>
<div dir="ltr" align="left"><font size="2" face="Arial"><span class="629595005-11052012"></span></font> </div>
<div dir="ltr" align="left"><span class="629595005-11052012"><font face="Arial"><font size="2">I'm in particular concerned with Steve's asking the Sos/ACs for
"...major resolutions in the works that deserve to be dealt with in a public
Board meeting" although I understand a positive intention to engage the
community in the process of establishing the board agenda. However any criteria
to evaluate what "indeed" may be of major interest are missing here (e.g.
financial, organizational, policy related impact e.a.). Unsatisfying discussions
about the rationale may
follow.<!-- Converted from text/rtf format --><br></font></font></span></div>
<div><span class="629595005-11052012"><font size="2" face="Arial">I don't like that
the responsibility for the decision to hold a public board meeting is shifted to
any SO/AC. To avoid unsatisfying discussions it may be acceptable if the board
holds a public meeting in case of at least one (two, three...?) agenda items
filed by any AC/SO regardless its assessment.</font></span></div>
<div><span class="629595005-11052012"></span> </div>
<div><span class="629595005-11052012"></span><span lang="de"><font size="2" face="Courier New">Best regards</font></span> <br><span lang="de"><font size="2" face="Courier New">Wolf-Ulrich</font></span> </div>
<div> </div><br>
<blockquote style="MARGIN-RIGHT: 0px" dir="ltr">
<div dir="ltr" lang="de" class="OutlookMessageHeader" align="left">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>Von:</b> <a href="mailto:soac-infoalert-bounces@icann.org">soac-infoalert-bounces@icann.org</a>
[mailto:soac-infoalert-bounces@icann.org] <b>Im Auftrag von </b>Steve
Crocker<br><b>Gesendet:</b> Freitag, 11. Mai 2012 01:25<br><b>An:</b> Barbara
Ann Clay; Rod Beckstrom; Denise Michel; David Olive; Nick Tomasso; Diane
Schroeder; Filiz Yilmaz; Christopher Mondini; <a href="mailto:soac-infoalert@icann.org">soac-infoalert@icann.org</a>;
Icann-board ICANN<br><b>Cc:</b> Steve Crocker<br><b>Betreff:</b>
[Soac-infoalert] Draft blog post re Friday Board meetings, SO/AC reports,
etc.<br></font><br></div>
<div></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">Folks (Staff, SO and AC chairs, and
Board),</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">I want to follow up on the announcement that we're
wrapping up the ICANN meeting on Thursday evening. We got a lot of
feedback expressing concern, some of which will be allayed with more
information. Below is a draft of a blog entry I'd like to post as soon
as it's been properly coordinated. Please take a look and let me know if
there are flaws or missing pieces. (And if you know of someone I should
have included in this coordination cycle, pass this on and also let me
know.)</span></font></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">If I can get the relevant information re the SO and AC
reports, I'll add it in.</span></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Also, please let me know if there are indeed major
resolutions in the works that deserve to be dealt with in a public Board
meeting. If so, we will need to schedule a public Board meeting and I'll
need to adjust the wording of this blog posting.</span></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">Thanks,</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">Steve</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">==================================================================================================================================================</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">On April 30 I announced we will wrap up the ICANN
meeting on Thursday evening and not use Friday. (Some groups may choose
to use Friday for their own meetings; that's fine.) We have received
multiple inputs asking for clarification or suggesting this change has some
adverse consequences. The announcement was a bit light on details.
I wanted to get the decision out so everyone could adjust their travel
plans. Now I want to say a bit more about the changes.</span></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">In the past, we had three parts to the program on
Friday morning -- reports from the Board committees, reports from the chairs
of the Supporting Organizations and Advisory Committees, and a formal Board
meeting. Attendance during all parts of the morning have been very
light. There really has not been much actual utility for the community.
Also every day of meeting time is expensive, not just to ICANN but also
to the community. Like many people, I had been noticing that Friday
mornings were not well attended, and it was clear it was time to make a
change. Let me now go into a few details, and I will close with a
promise that if the changes we're making for Prague are not in the best
interests of everyone, we will continue to evolve the
schedule.</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">With respect to our Board meetings, the large majority
of the resolutions we approve are the regular pieces of business that are
known well in advance. The Board approves these resolutions without
fanfare. The substantive work is done via the Supporting Organizations
or via staff work, and the work is posted. </span></font><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Once in
while there are Board actions that have </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">some
controversy or drama. The XXX </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">decision
in San Francisco and the decision in </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Singapore
to move forward with the gTLD program </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">are the
two recent examples that come to </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">mind.
For matters of this import, we will hold </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">a public
Board meeting. In Singapore, we did </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">this at
the beginning of the week. This was a </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">big
improvement and really helped set a positive </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">tone for
the entire week. I think this is a </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">good
pattern, and I'm inclined to follow this </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">when it's
needed. I don't know how often we'll </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">have to
do this; I suspect it will be less than half the time.</span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">A closely related aspect of this change is we will no
longer be rushing through resolutions based on committee work or inputs during
the week. </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">We need to take </span><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">some time to develop the
proper </span></font><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">documentation. So, instead of trying to cap
the </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">week off with resolutions passed on the basis
of </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">the week's work, we will report on what's
come </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">up during the week, what happened between
the </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">last ICANN meeting and this one, and what
we </span><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">plan to do following this ICANN meeting. This is
in accordance with the recommendations of the Accountability and Transparency
Review Team, and is consistent with the changes we made some time ago to
provide more thorough documentation in the form of a rationale for each
resolution. These changes will have the benefit of providing time for
careful and considered work on each resolution and better documentation for
transparency and accountability.</span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Our vice chair, Bruce Tonkin, observes:</span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<blockquote style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px" class="webkit-indent-blockquote">
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">
<div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">An example of this approach was on the topic of
Conflicts of Interest in Dakar in October 2011. The Board listened to
the community during the week, and then in the public session on conflicts
Board members gave some feedback to the community on specific measures that
would be taken with respect to new gTLDs. After careful review by the
legal team and review by Board members, the Board held a meeting on 8 Dec
2011 and passed a resolution on management conflicts for new gTLDs.
The Board also passed other resolutions that resulted from the
discussion in Dakar.</span></font></div></div></span></div></blockquote>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">
<div>
<div><br></div></div></span></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">We have made some related changes in the coordination
of Board resolutions and the scheduling of Board meetings. I will report
on these changes in a separate posting.</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">We recognize the community wants to see the Board in
action and have the opportunity to interact with the Board. Toward this
end, we are making two additional changes. In the opening session on
Monday morning, I will include a summary of what has taken place since the
last meeting, and on Thursday afternoon the Board will report on what it has
heard during the week. The Board will continue to engage eagerly in the
public sessions, listening closely to the comments from the community and
responding to questions.</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span">At the beginning of this blog I mentioned the reports
from the SO and AC chairs and the reports from the Board committees. We
are still working out the arrangements for these and I will report separately
on the details. The SOs and ACs are the lifeblood of ICANN, and we want
to make sure they have greater, not lesser visibility.</span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div>
<div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Finally, as I noted above, we are working hard to be
both more effective and more efficient. If we need to continue to evolve
this process, we will.</span></div></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Thank you.</span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span"><br></span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Steve Crocker</span></div>
<div><span style="FONT-FAMILY: Cambria; FONT-SIZE: 16px" class="Apple-style-span">Chair, ICANN Board of Directors</span></div></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div>
<div><font class="Apple-style-span" face="Cambria"><span style="FONT-SIZE: 16px" class="Apple-style-span"><br></span></font></div></blockquote></div>
<span><ATT00001.c></span></blockquote></div><br></div></body></html>