<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Texto sem Formatação Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.TextosemFormataoChar
{mso-style-name:"Texto sem Formatação Char";
mso-style-priority:99;
mso-style-link:"Texto sem Formatação";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="PT-BR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">Dear CCWG colleagues,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Thank you for the valuable comments. Please find bellow the inputs of the Brazilian Government to the issue of jurisdiction:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">'Jurisdiction' is one of the core issues to be dealt with in the CCWG-Accountability as it influences directly the way ICANN's accountability processes are structured and operationalized. The fact that ICANN today
operates under the legislation of the state of California grants the corporation certain rights but also imposes some limits with respect to the accountability mechanisms it can adopt.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Brazil is fully aware that at the present stage - when the CCWG is devoted to agreeing on recommendations that needs to be in place prior to the stewardship transition (WS1 recommendations) - this group should not
make decisions on possible 'alternatives of jurisdictions'. We believe this concern deserves a more profound and better grounded debate and should therefore be considered a priority of the WS2 debate.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">However, there are some immediate concerns with respect to this topic that needs to be either decided or at least made evident in the context of WS1:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">1) The present AoC between the government of the United States and ICANN makes direct references to the corporation's legal presence. As you are aware, paragraph 8 of the AoC requires ICANN to maintain its current
legal presence in the United States. Since AoC provisions are of immediate concern for the stewardship transition, it is expected that this group makes recommendations also on paragraph 8 (as ST #15 shows). In the view of the Brazilian Government, provisions
in paragraph 8 should be translated into a set of 'jurisdiction requirements' (stable environment, predictable regime, etc) and should not impose a specific national legislation.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">2) A permanent Independent Review Panel is being considered as an enhanced mechanism for independent third-party review. One of the main aspects to be taken into account when the details of the IRP are being sorted
out is its 'de facto' independence, which also raises concerns about 'jurisdiction'. The IRP should be a truly impartial body and no litigating party should potentially benefit from or be harmed by its specific legal presence in country A or Z.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">3) The CCWG has agreed on a working methodology which makes a clear separation between requirements and implementation. For Brazil, 'requirements' are understood as those accountability objectives required by the community
and 'implementation' are the specific mechanisms that needs to be in place in order to accomplish the requirements previously defined. While specifying those mechanisms, the CCWG should also clearly indicate those cases when requirements are partially met,
either because the group wasn't able to conceive a better structured process to that date or because ICANN's current legal presence imposes certain restrictions. This kind of clarity is in line with principle of 'transparency' under which this group operates
and will be essential for the following work of the CCWG.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">4) For the reason above, the legal analysis to be provided by the external law firm and the expert's group should already include considerations on jurisdictional limitations and options. Again: in that way, the CCWG
will be transparent by showing the eventual limitations of its recommendations and will be able to provide important input for WS2 or other future accountability recommendation work.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">5) In line with the points indicated above, we consider the framework proposed by Carlos Gutierrez and summarized by Mathieu Weill to be adequate for our discussion on this specific topic.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">See you soon!<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">Secretário Pedro Ivo Ferraz da Silva<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">Divisão da Sociedade da Informação (DI)<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">Ministério das Relações Exteriores - Brasil<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">T: + 55 61 2030-6609<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">Secretary Pedro Ivo Ferraz da Silva<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:PT-BR">Division of Information Society (DI)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:PT-BR">Ministry of External Relations - Brazil<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:PT-BR">T: + 55 61 2030-6609<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:PT-BR"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="mso-fareast-language:PT-BR"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="mso-fareast-language:PT-BR">-----Mensagem original-----<br>
De: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] Em nome de Mathieu Weill<br>
Enviada em: quinta-feira, 19 de março de 2015 17:55<br>
Para: Greg Shatan; Carlos Raúl Gutiérrez<br>
Cc: accountability-cross-community@icann.org<br>
Assunto: Re: [CCWG-ACCT] Call for requirement on the issue of jurisdiction</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dear Carlos, Dear Greg, Dear Colleagues,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I fully agree that we need to focus our work on work stream 1 issue, as was recalled during our last meeting. Still, it is important however that we can explain why a specific topic was considered relevant for a work stream.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Carlos, from your message, I understand that you suggest to identify the various layers of the jurisdiction issue. My understanding is that the following layers are mentioned in your messages :
<o:p></o:p></p>
<p class="MsoPlainText">- place and jurisdiction of incorporation<o:p></o:p></p>
<p class="MsoPlainText">- jurisdiction of places of physical presence<o:p></o:p></p>
<p class="MsoPlainText">- governing law for contracts<o:p></o:p></p>
<p class="MsoPlainText">- ability to sue and be sued in a specific jurisdiction<o:p></o:p></p>
<p class="MsoPlainText">- tax system<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I would recommend we use this framework to clarify the associated requirements. For instance, and I stress this is just personal brainstorming, for contracts, they need to be in a stable and predictable legal regime.
<o:p></o:p></p>
<p class="MsoPlainText">The place of incorporation should certainly be in a jurisdiction with strong corporate governance legislation, providing efficient accountability, but at the same time, enabling flexibility so that the multistakeholder model can be translated
into this legal framework. <o:p></o:p></p>
<p class="MsoPlainText">Places of physical presence need to provide stable labour legal frameworks(to hire staff), and some level of flexibility for visas (to accomodate international staff and travel by community members) Physical presence should also take
into account security concerns, both for the sake of staff as well as for operations.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This is the kind of requirement (the above list is non exhaustive and can be challenged) we should look at to determine our next steps on this question.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I hope this helps clarify and I encourage the colleagues who brought up this issue on the list to provide their input.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">best,<o:p></o:p></p>
<p class="MsoPlainText">Mathieu<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Le 18/03/2015 19:24, Greg Shatan a écrit :<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> I agree with Carlos that the issue(s) of "jurisdiction" are multi-layered. It's also important to realize that the term "jurisdiction" is used to mean several different things (place of incorporation, places of physical
presence, governing law, ability to sue and be sued, etc.), and discussions about jurisdiction often get jumbled up for this reason.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> However, I think there is a simple and more fundamental issue with regard to the discussion of "jurisdiction" (at least in the sense of "place of incorporation), before we even get to the substance of such a discussion..
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> It is very important for the CCWG to focus on Work Stream 1 items, since the IANA Transition is dependent on completion of these items. Discussion of ICANN's place of incorporation is a Work Stream 2 item and should
not be dealt with in any depth until Work Stream 1 is complete.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Put another way, the place of incorporation of ICANN will not be changing before the IANA Transition, and thus the possibility of such changes has no place in Work Stream 1. Furthermore, if the CCCWG were to advance
any plan as part of Work Stream 1 to change the place of incorporation of ICANN after the IANA Transition, this would be rejected by the NTIA and thus would be an immense waste of time.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> This is not to say that discussions of "jurisdiction" (in all of its meanings and layers) should not take place. Quite the contrary. These are valid and important topics, and they should be given a full and complete
airing. We just need to prioritize our work appropriately.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Greg Shatan<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> On Wed, Mar 18, 2015 at 1:38 PM, Carlos Raúl Gutiérrez <<a href="mailto:crg@isoc-cr.org"><span style="color:windowtext;text-decoration:none">crg@isoc-cr.org</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Dear Mathieu, <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> thank you for this invitation to comment. First of all I have to make a disclaimer that I`m not a lawyer and I feel that we a have a superb group of knowledgeable and expert lawyers around this issue and
I have little to add to their discussions. Sometimes i’m even afraid to open my mouth and get hit back with a strong legal defence attitude, as recently happened to me trying to make sense of the freedom of expression the way I understand it.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> So let me talk of my personal perception on how this issue has been handled, which has not been satisfactory from my perspective. And my excuses to all readers if I’m off the mark again.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> * The DNS is more global than ever, in different languages and scripts, with many new contracts in the languages (and jurisdictions?) of the new players in new areas of the World. And I think
this is very good for the globalisation of the Internet and in response of the search for competition, consumer trust and consumer choice, which for me are not only one of the 4 values of the AoC, but one of the most promising in terms of the future development
of the Internet.<o:p></o:p></p>
<p class="MsoPlainText"> * Every time the jurisdiction of the corporation itself is mentioned, I get the feeling that we get into a rather negative/defensive mode from different sides, particularly if people are sitting
in front of lawmakers. When I started studying public finance and taxation long time ago all important global US corporations where based in Delaware (of all places). Today some of the most important users of the DNS are based in Luxembourg or Ireland to the
chagrin of US Tax authorities. From my perspective until we don’t get an harmonised global tax system, private initiatives will be looking for the best balance between where do you business with whom, under or away from what jurisdiction. The recent case of
a Hong Kong Bank subsidiary in Switzerland is a cautionary tele to keep in mind.<o:p></o:p></p>
<p class="MsoPlainText"> * Then we have the scaremongers who worry not a bout watching soccer games, but about all the money its federation makes and does not get taxed and governed. i.e.FIFA.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Obviously between those extreme points of view is difficult to have an effective discussion on the "issue of jurisdiction” as you call it, without explaining if we are talking about the narrow issues of
the global DNS contracts the Board has to sign, or about the day to day operations of the Corporation, or the global accountability and transparency standards under which ALL (as per NetMundial Statement, section Roadmap) Internet entities should work, so
that the systems remains as it is today (and ICANNs luck to draw the ticket and become the guinea pig).<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> So my request is to please make clear on which layer are we talking about the jurisdiction issue and why is there a need for a change. For example<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> * Is the jurisdiction hindering the globalisation of the DNS because of legal paperwork?<o:p></o:p></p>
<p class="MsoPlainText"> * Is the jurisdiction hindering the operations of the corporation, from security and stability, COSTS (particularly for review and redress), tax, human resources, and other operational concerns?<o:p></o:p></p>
<p class="MsoPlainText"> * Is the jurisdiction hindering the global public good in terms of access (including cost of access for users), human rights, freedom of expression, competition, etc.?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> And you don’t have the 3 layers I have proposed, you can choose 6 different ones, but make it clear from the outset for the benefit of the "legally challenged", so there is wider participation in this very
interesting discussion.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Best luck in Istambul <o:p>
</o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Carlos Raúl Gutiérrez<o:p></o:p></p>
<p class="MsoPlainText"> _____________________<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> email: <a href="mailto:crg@isoc-cr.org">
<span style="color:windowtext;text-decoration:none">crg@isoc-cr.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"> Skype: carlos.raulg<o:p></o:p></p>
<p class="MsoPlainText"> +506 8335 2487 <<a href="tel:%2B506%208335%202487"><span style="color:windowtext;text-decoration:none">tel:%2B506%208335%202487</span></a>> (cel)<o:p></o:p></p>
<p class="MsoPlainText"> +506 4000 2000 <<a href="tel:%2B506%204000%202000"><span style="color:windowtext;text-decoration:none">tel:%2B506%204000%202000</span></a>> (home)<o:p></o:p></p>
<p class="MsoPlainText"> +506 2290 3678 <<a href="tel:%2B506%202290%203678"><span style="color:windowtext;text-decoration:none">tel:%2B506%202290%203678</span></a>> (fax)<o:p></o:p></p>
<p class="MsoPlainText"> _____________________<o:p></o:p></p>
<p class="MsoPlainText"> Apartado 1571-1000<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> San Jose, COSTA RICA<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> On Mar 18, 2015, at 11:02 AM, Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr"><span style="color:windowtext;text-decoration:none">mathieu.weill@afnic.fr</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Dear Colleagues,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> During our call yesterday we decided to engage with you to gather input on a requirement based approach to the issue of jurisdiction which has been raised.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> So far this issue has been raised when discussing some of the stress tests, the incorporation of the AoC into the Bylaws, as well as in generic discussions.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> What we are looking for to ensure we keep our discussion at the level of accountability and root it into stakeholder expectations, are descriptions of accountability requirements that lead
you (or some of you) to raise the question of jurisdiction. Topics such as applicable jurisdiction of Icann contracts have been raised so far for instance.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Thank you in advance for contributing to shaping this important aspect of our work. responses are expected before March 20th so that we can organize work in Istanbul.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Best<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> -- <o:p></o:p></p>
<p class="MsoPlainText"> *****************************<o:p></o:p></p>
<p class="MsoPlainText"> Mathieu WEILL<o:p></o:p></p>
<p class="MsoPlainText"> AFNIC - directeur général<o:p></o:p></p>
<p class="MsoPlainText"> Tél: +33 1 39 30 83 06 <<a href="tel:%2B33%201%2039%2030%2083%2006"><span style="color:windowtext;text-decoration:none">tel:%2B33%201%2039%2030%2083%2006</span></a>>
<o:p></o:p></p>
<p class="MsoPlainText"> <a href="mailto:mathieu.weill@afnic.fr">
<span style="color:windowtext;text-decoration:none">mathieu.weill@afnic.fr</span></a><o:p></o:p></p>
<p class="MsoPlainText"> Twitter : @mathieuweill<o:p></o:p></p>
<p class="MsoPlainText"> *****************************<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> Accountability-Cross-Community mailing list<o:p></o:p></p>
<p class="MsoPlainText"> <a href="mailto:Accountability-Cross-Community@icann.org">
<span style="color:windowtext;text-decoration:none">Accountability-Cross-Community@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">
<span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> Accountability-Cross-Community mailing list<o:p></o:p></p>
<p class="MsoPlainText"> <a href="mailto:Accountability-Cross-Community@icann.org">
<span style="color:windowtext;text-decoration:none">Accountability-Cross-Community@icann.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">
<span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">--<o:p></o:p></p>
<p class="MsoPlainText">*****************************<o:p></o:p></p>
<p class="MsoPlainText">Mathieu WEILL<o:p></o:p></p>
<p class="MsoPlainText">AFNIC - directeur général<o:p></o:p></p>
<p class="MsoPlainText">Tél: +33 1 39 30 83 06<o:p></o:p></p>
<p class="MsoPlainText"><a href="mailto:mathieu.weill@afnic.fr"><span style="color:windowtext;text-decoration:none">mathieu.weill@afnic.fr</span></a><o:p></o:p></p>
<p class="MsoPlainText">Twitter : @mathieuweill<o:p></o:p></p>
<p class="MsoPlainText">*****************************<o:p></o:p></p>
</div>
</body>
</html>