<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Colleagues,<br>
<br>
Please consider this response as a contribution from Afnic,
definitely not from me as a co chair. The proposals below are
"strawman". <br>
<br>
<br>
<div class="moz-cite-prefix">Le 08/07/2015 22:45, Jan Aart Scholte a
écrit :<br>
</div>
<blockquote cite="mid:1436388340826.9440@globalstudies.gu.se"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; } @font-face {
font-family: Cambria;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0pt; font-family: "Times New Roman"; font-size: 12pt; } @font-face {
font-family: Wingdings;
}
@font-face {
font-family: SimSun;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: ArialMT;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0pt; font-family: "Times New Roman","serif"; font-size: 12pt; } a:link, span.MsoHyperlink { color: blue; text-decoration: underline; } a:visited, span.MsoHyperlinkFollowed { color: purple; text-decoration: underline; } p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph { margin: 0in 0in 0pt 0.5in; font-family: "Times New Roman","serif"; font-size: 12pt; } span.EmailStyle17 { color: rgb(31, 73, 125); font-family: "Calibri","sans-serif"; } .MsoChpDefault { font-size: 10pt; } ol { margin-bottom: 0in; } ul { margin-bottom: 0in; }--></style>
<p>Hello All</p>
<p> <br>
</p>
<p>Excellent, productive calls. Thank you, Leon. In response to
Paul's urgings for a practical agenda for action, the main
suggestions that I have taken from the first two conversations
are:</p>
<p> <br>
</p>
<p style="text-decoration: underline;">Workstream 1</p>
<p> </p>
<p>*to make explicit commitments regarding diversity (minimally
geographical, perhaps also cultural, linguistic, age and gender)
in the proposed new accountability bodies (in particular the
SO/AC community empowerment mechanism and the IRP)</p>
</blockquote>
I agree with Jan and would propose the following :<br>
- to set Icann into a continuous improvement path regarding
diversity, ATRT reviews could be expanded into <b>Accountability,
Transparency and Diversity Reviews. </b>The review team would be
tasked to assess and make recommenndations regarding diversity
across all Icann bodies. This is a simple step, that remains
flexible so that diversity remains focused on the goal of making
Icann as representative as possible of the wider Internet community.
<br>
<br>
- to protect against undue influence from 1 Region in the groups,
instead of imposing a strict 1 vote, 1 region rule, we could set a
limit that each SO or AC could appoint (to the community council or
review teams) <b>no more than 1/3 of its representatives from a
single Region</b>. This ensures in the community council that no
Region reaches by itself the 1/3 threshold which is sufficient to
block certain votes. <br>
<br>
<blockquote cite="mid:1436388340826.9440@globalstudies.gu.se"
type="cite">
<p> </p>
<p>*to indicate how SOs/ACs in holding the board accountable
through the new community empowerment mechanism are themselves
also sufficiently accountable in the exercise of these powers
(partly this might be demonstrated by listing relevant points
from existing SO/AC rules and procedures, partly it may be
secured with new measures such as the suggested MAR or adherence
to the INGO Accountability Charter)</p>
<p> </p>
</blockquote>
I also agree with Jan and others we should start by listing existing
mechanisms. The Mutual Accountability Roundtable is also an idea
which I fully support. <br>
<br>
I also would suggest that we set the continuous improvement loop in
motion in a more formal mannner. To that end, we could update the
Structural Reviews of SO/ACs (as defined in article IV of the
Bylaws) and transform them into <b>Structural Accountability and
Transparency Reviews of SO/ACs</b>, under the Board's supervision.
These reviews would lead to recommendations for imrpovements that
would have a similar status as the AoC review team recommendations
has to the Board (SO or AC MUST deliberate whether or not to
implement, and this decision can be challenged in front of the IRP).
<br>
<br>
I believe this would provide greater strength to the notion of
"Mutual Accountability", and remains a simple and flexible
recommendation, with very little complexity of implementation or
lead time. <br>
<br>
Best regards<br>
Mathieu<br>
<blockquote cite="mid:1436388340826.9440@globalstudies.gu.se"
type="cite">
<p style="text-decoration: underline;">Workstream 2</p>
<p> </p>
<p>*to include in the CCWG report (and carry over into the ICG
consolidated proposal) an itemised list of specific issues and
objectives regarding diversity, SO/AC accountability, and staff
accountability; progress towards these objectives to be
evaluated two years down the line as part of the IANA transition
review - this undertaking would seem to imply a continuation of
the CCWG Accountability or some successor construction</p>
<p> </p>
<p>No doubt others can articulate the points more precisely, but
it could be helpful to have a concise synthesis to move us
forward in the limited time available?</p>
<p> </p>
<p>Greetings</p>
<p> </p>
<p>Jan</p>
<p> </p>
<p> </p>
<p> </p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="width: 98%; display: inline-block;">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size: 11pt;"
color="#000000" face="Calibri, sans-serif"><b>Från:</b>
<a class="moz-txt-link-abbreviated" href="mailto:wp3-bounces@icann.org">wp3-bounces@icann.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:wp3-bounces@icann.org"><wp3-bounces@icann.org></a> för Paul
Twomey <a class="moz-txt-link-rfc2396E" href="mailto:paul.twomey@argopacific.com"><paul.twomey@argopacific.com></a><br>
<b>Skickat:</b> den 8 juli 2015 19:12<br>
<b>Till:</b> Sébastien Bachollet; <a class="moz-txt-link-abbreviated" href="mailto:wp3@icann.org">wp3@icann.org</a><br>
<b>Ämne:</b> Re: [Wp3] Final Report by ICANN Geographic
Regions Review Working Group</font>
<div> </div>
</div>
<div>Hi Sebastien<br>
<br>
I agree with other members of Wp3 on our last meeting that the
geographic diversity is only a priority for our work in the
next couple of weeks in ensuring that the customer review
bodies etc of the IANA transition model are forced to be
geographically diverse in their make-up.<br>
<br>
But the bigger strategic issue of ICANN always pushing itself
to be reflective of the Global Internet Community, including
geographically, as you point out has not had a time frame put
on it. I think the work of the WG upto June 2013 was fine in
its own context - but that context was limited. I am not
against the Board acting on the WG recommendations, but I do
worry that will be seen as the end of the matter - while I
think it is only the beginning. And I am worried that we
have little time to get ahead of this issue before it comes up
on us.<br>
<br>
I am interested to hear others' thoughts as to how we get this
issue on the practical agenda for action.<br>
<br>
<br>
Paul<br>
<br>
<div class="moz-cite-prefix">On 7/9/15 2:13 AM, Sébastien
Bachollet wrote:<br>
</div>
<blockquote type="cite">
<div>
<div>
<div>Hi Paul,</div>
<div>As you know</div>
<div>" the ICANN Board at its Public Meeting in Cairo
(November 2008)7 , authorized the formation of the
proposed working group. The Board subsequently
approved the Working Group’s Charter on 26 June
2009. »</div>
<div><br>
</div>
<div>The world has change since 2008/2009 and even since
the publication of the final report of the WG in June
2013.</div>
<div>ICANN is doing SO/AC reviews within a certain time
frame. The same for AoC reviews.</div>
<div>This one (one of the few with global remit) as no
timeframe.</div>
<div>It is time for the Board to act diligently on the
improvement proposed in this document.</div>
<div><br>
</div>
<div>But we may also add this review in the regular ones
or add this issue as an additional topic in another
one already discuss (like ATRT for example).</div>
<div><br>
</div>
<div>
<div><font class="Apple-style-span" color="rgb(0,0,0)"><font
class="Apple-style-span" face="Calibri">Sébastien
Bachollet</font></font></div>
<div><font class="Apple-style-span" color="rgb(0,0,0)"><font
class="Apple-style-span" face="Calibri">+33 6 07
66 89 33</font></font></div>
<div>Blog: <a moz-do-not-send="true"
href="http://sebastien.bachollet.fr">http://sebastien.bachollet.fr</a>/</div>
<div>Mail: <span class="Apple-style-span"
style="font-family: Calibri; font-size: 15px;">
Sébastien Bachollet <<a moz-do-not-send="true"
href="mailto:sebastien@bachollet.com">sebastien@bachollet.com</a>></span></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="border-width: 1pt medium medium; border-style:
solid none none; border-color: rgb(181, 196, 223)
currentColor currentColor; padding: 3pt 0in 0in;
text-align: left; color: black; font-family: Calibri;
font-size: 11pt;">
<span style="font-weight: bold;">De : </span><<a
moz-do-not-send="true"
href="mailto:wp3-bounces@icann.org">wp3-bounces@icann.org</a>>
on behalf of Paul Twomey <<a moz-do-not-send="true"
href="mailto:paul.twomey@argopacific.com">paul.twomey@argopacific.com</a>><br>
<span style="font-weight: bold;">Date : </span>mercredi
8 juillet 2015 10:46<br>
<span style="font-weight: bold;">À : </span><<a
moz-do-not-send="true" href="mailto:wp3@icann.org">wp3@icann.org</a>>,
Alice Jansen <<a moz-do-not-send="true"
href="mailto:alice.jansen@icann.org">alice.jansen@icann.org</a>>,
<<a moz-do-not-send="true"
href="mailto:pam.little@zodiac-corp.com">pam.little@zodiac-corp.com</a>><br>
<span style="font-weight: bold;">Objet : </span>Re:
[Wp3] Final Report by ICANN Geographic Regions Review
Working Group<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="margin: 0px 0px 0px 5px; padding: 0px 0px 0px
5px; border-left-color: rgb(181, 196, 223);
border-left-width: 5px; border-left-style: solid;">
<div>
<div bgcolor="#FFFFFF">Hi Alice<br>
<br>
I would also note that the working group responded
to the task it was given by the Board:
<br>
<meta name="Title" content="">
<p class="MsoNormal"><span style="font-family:
Helvetica;"><br>
"The Working Group was formed by the Board to </span></p>
<p class="MsoNormal"><span style="font-family:
Helvetica;">(1) identify the different purposes
for which ICANN’s Geographic Regions are used;
</span></p>
<p class="MsoNormal"><span style="font-family:
Helvetica;">(2) determine whether the uses of
ICANN’s Geographic Regions (as currently
defined, or at all) continue to meet
</span></p>
<p class="MsoNormal"><span style="font-family:
Helvetica;">the requirements of the relevant
stakeholders; and
</span></p>
<p class="MsoNormal"><span style="font-family:
Helvetica;">(3) submit proposals for community
and Board consideration relating to the current
and future uses and definition of the ICANN
Geographic Region"<br>
</span></p>
<p class="MsoNormal"><br>
There was no real discussion of the global
strategic challenges facing ICANN in a world where
Internet activity and power is shifting
dramatically away from the hubs of the late 1990s
which underlie ICANN's present structures.<br>
</p>
<p class="MsoNormal"><br>
The sections on page 15 talking about change in
number of regions say to reduce the number would
be too burdensome on travel for some members of
the community and to increase them will increase
the costs of the support. Hardly a strategic
analysis.<br>
</p>
<p class="MsoNormal"><br>
I think this issue is a very important one for the
strategic viability of ICANN and for that matter
the general acceptance of a single Root.<br>
</p>
<p class="MsoNormal"><br>
Paul<br>
<span style="font-family: Helvetica;"></span></p>
<meta name="Keywords" content="">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 2008">
<meta name="Originator" content="Microsoft Word
2008">
<link
href="file://localhost/Users/paultwomey/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml"
rel="File-List">
<style>
<!--
@font-face
{font-family:Cambria}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman"}
@page Section1
{margin:1.0in 1.25in 1.0in 1.25in}
-->
</style><br>
<br>
<br>
<div class="moz-cite-prefix">On 7/8/15 8:01 PM, Pam
Little wrote:<br>
</div>
<blockquote type="cite">
<meta name="Generator" content="Microsoft Word 14
(filtered medium)">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:SimSun}
@font-face
{font-family:SimSun}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:ArialMT}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;">Hi Alice,</span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;">I have a couple of
questions regarding this report.</span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"> </span></p>
<p class="MsoListParagraph" style="text-indent:
-0.25in; margin-left: 0.25in;"><span
style="color: rgb(31, 73, 125); font-family:
"Calibri","sans-serif";
font-size: 11pt;"><span>1.<span>
</span></span></span><span style="color:
rgb(31, 73, 125); font-family:
Calibri,sans-serif; font-size: 11pt;">The
report is dated June 2013 and it refers to
the ICANN Durban meeting. Could you clarify
what has been done since Durban?</span></p>
<p class="MsoListParagraph"><span style="color:
rgb(31, 73, 125); font-family:
Calibri,sans-serif; font-size: 11pt;"> </span></p>
<p class="MsoListParagraph" style="text-indent:
-0.25in; margin-left: 0.25in;"><span
style="color: rgb(31, 73, 125); font-family:
"Calibri","sans-serif";
font-size: 11pt;"><span>2.<span>
</span></span></span><span style="color:
rgb(31, 73, 125); font-family:
Calibri,sans-serif; font-size: 11pt;">Your
note mentioned: “It is intended that the
report will be submitted to the Board prior
to the Dublin meeting.” Could you clarify if
the following steps stated at para #87 on
page 24 of the report have been completed.
If not, what are the time lines for those:</span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"> </span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">“Before
these recommendations can be formally
transmitted to the ICANN Board,</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">the next
step in this process consists of a final
community review of the Final</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">Report
document and its recommendations by ICANN’s
various SO-AC structures.</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">Footnote
15 above outlines the specific process steps
for this review and</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">consideration
of the Working Group recommendations. The
Working Group has</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">determined
that community review should extend for a
full 90 calendar days after</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span
style="font-family: ArialMT,serif;">the
conclusion of the ICANN Public Meeting in
Durban.”</span><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"></span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;">Thank you.</span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;"> </span></p>
<p class="MsoNormal"><span style="color: rgb(31,
73, 125); font-family: Calibri,sans-serif;
font-size: 11pt;">Pam Little</span></p>
<div>
<div style="border-width: 1pt medium medium;
border-style: solid none none; border-color:
rgb(181, 196, 223) currentColor
currentColor; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-family: Tahoma,sans-serif;
font-size: 10pt;">From:</span></b><span
style="font-family: Tahoma,sans-serif;
font-size: 10pt;">
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:wp3-bounces@icann.org">wp3-bounces@icann.org</a>
[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:wp3-bounces@icann.org">mailto:wp3-bounces@icann.org</a>]
<b>On Behalf Of </b>Alice Jansen<br>
<b>Sent:</b> Wednesday, July 08, 2015
7:05 PM<br>
<b>To:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:wp3@icann.org">wp3@icann.org</a><br>
<b>Subject:</b> [Wp3] Final Report by
ICANN Geographic Regions Review Working
Group</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">Dear all,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">Further to the request
made on call #1, please find below the
link to the Final Report prepared by ICANN
Geographic Regions Review Working Group
for consideration by the ICANN Board (June
2013): <a moz-do-not-send="true"
href="https://www.icann.org/en/system/files/files/geo-regions-final-report-22jun13-en.pdf">https://www.icann.org/en/system/files/files/geo-regions-final-report-22jun13-en.pdf</a> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">It is intended that
the report will be submitted to the Board
prior to the Dublin meeting.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">Please note that this
document has been added to your WP3
reading list - <a moz-do-not-send="true"
href="https://community.icann.org/display/acctcrosscomm/Reading+List">https://community.icann.org/display/acctcrosscomm/Reading+List</a> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">May I also take this
opportunity to inform you that three
dedicated wiki pages have been created for
all three subgroups. These pages will be
the repositories for volunteers, documents
and reading lists.</span></p>
</div>
<ul type="disc">
<li class="MsoNormal" style="color: black;"><span
style="font-family: Calibri,sans-serif;
font-size: 10.5pt;">Diversity - <a
moz-do-not-send="true"
href="https://community.icann.org/display/acctcrosscomm/Diversity">https://community.icann.org/display/acctcrosscomm/Diversity</a></span>
</li>
<li class="MsoNormal" style="color: black;"><span
style="font-family: Calibri,sans-serif;
font-size: 10.5pt;">SO/AC accountability
- <a moz-do-not-send="true"
href="https://community.icann.org/pages/viewpage.action?pageId=53783727">https://community.icann.org/pages/viewpage.action?pageId=53783727</a></span>
</li>
<li class="MsoNormal" style="color: black;"><span
style="font-family: Calibri,sans-serif;
font-size: 10.5pt;">Staff accountability
- <a moz-do-not-send="true"
href="https://community.icann.org/display/acctcrosscomm/Staff+accountability">https://community.icann.org/display/acctcrosscomm/Staff+accountability</a></span>
</li>
</ul>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">Kind regards</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;">Alice </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:
black; font-family: Calibri,sans-serif;
font-size: 10.5pt;"> </span></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
wp3 mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wp3@icann.org">wp3@icann.org</a><a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp3">https://mm.icann.org/mailman/listinfo/wp3</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dr Paul Twomey
Managing Director
Argo P@cific
US Cell: +1 310 279 2366
Aust M: +61 416 238 501
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.argopacific.com">www.argopacific.com</a></pre>
</div>
</div>
_______________________________________________ wp3
mailing list <a moz-do-not-send="true"
href="mailto:wp3@icann.org">
wp3@icann.org</a> <a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/wp3">https://mm.icann.org/mailman/listinfo/wp3</a>
</blockquote>
</span></blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dr Paul Twomey
Managing Director
Argo P@cific
US Cell: +1 310 279 2366
Aust M: +61 416 238 501
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.argopacific.com">www.argopacific.com</a></pre>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wp3 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wp3@icann.org">wp3@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp3">https://mm.icann.org/mailman/listinfo/wp3</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: +33 1 39 30 83 06
<a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</body>
</html>