<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body bgcolor="#FFFFFF" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Arial;color: #000000;font-size: 10pt;">
<div style="direction:ltr; font-family:Arial; color:#000000; font-size:10pt">
<div id="divRpF541213" style="direction:ltr"><span style="font-family:Arial; font-size:10pt">Dear all,</span></div>
<div>
<div style="direction:ltr; font-family:Arial; font-size:10pt">
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">I have been following carefully the discussions in the list. I do not intend to respond to the many points that were raised, but I think it is important to bear in mind the following, in preparation for tomorrowīs call:</div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">1 - Our rules of engagement provide that "In the absence of full consensus, the Chair(s) should allow for the submission of minority viewpoint(s) and these, along with the consensus view, shall be included in the report" </div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">This is exactly the situation we are experiencing here. There is no full consensus in regard to the report, as there are formal objections. Those who, similarly to Brazil, object to the report, should be allowed to submit their
minority viewpoint(s) and these shall be included in the report. It is as simple as that. Needless to say that those who have minority views should be free to choose the way they wish to make their views known, the rationale they are following, the reasons
why they canīt accept the proposed recommendations or why they think those recommendations are insufficient, etc. There is no pre-determined format or template to be followed. In other words, the drafting of the minority viewpoints should be the responsibility
of those those who hold such minority views and not be subject to collective deliberation. </div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">2 - I acknowledge, on the other hand, that the "Statement" we circulated last Saturday might have included elements that we may consider to withdraw or reformulate without undermining the essence of our reasoning. I would think
it would be appropriate, for example, for us to consider deletion of some portions of text included in the last paragraph of the first page of our "Statement" (Finally, Brazil objects to the portrayal of the report of a consensus document...") as they have
elicited unnecessary controversy in regard to the process. Similarly, we could entertain changing, <b>as per the results of discussions at the CCWG meeting</b>, the way we have presented recommendations we would like to have seen in the report (the absence
of which makes the whole report unacceptable to us), in order to make sure our document is duly formatted as a minority viewpoint and not be seen as additional input for further work at this stage. In that case, we could reformulate, for example, the introductory
paragraph of point 6 ("Brazil calls upon the CCWG to include in a final report on jurisdiction recommendations to the effect that..."</div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">3 - I wish to further clarify that both the Statement and its annex should be read as a single document. Both are needed to clarify the context and the substance of our objection. As stated above, however, we could agree to
change the final outline of the document as a whole provided it is duly included in the report as a minority view.</div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">4 - Finally, I should state that several comments that were posted on the list - some of them ironical or even outright disrespectful - seem to be guided by a very poor and narrow view of what should be the essence of the multistakeholder
approach to Internet governance. At this point, I would like to state that what takes place in ICANN - although unique - is not dissociated from the rest of the ecosystem. If we want to put in place and improve an operational environment in which all stakeholders
can exercise their roles and responsibilities, as per the Tunis Agenda for the Information Society, mutual respect and mutal recognition are needed. One of the main concerns that has guided our participation throughout this exercise was the attempt to explore
a formula that would be aligned with the principle of sovereign equality among States. This is an un-negotiable principle and we cannot endorse any framework (either at ICANN or beyond) that would not adequately address this topic. This is not incompatible
with maintaining ICANN's multistakeholder character nor should it be interpreted - as some maliciously do - as defending that ICANN becomes a government-led organisation. Finally, may I just recall that NETMundial, which Brazil is proud to have hosted, has
called for the process of globalization of ICANN should lead up to a "truly international and global organization". I donīt recall at the time no one ridiculing that notion nor saying it was unrealistic or politically unachievable. I assume there is a long
way towards that ultimate goal and that times are not favorable, however I would strongly advocate against losing sight of the vision that NETMundial provided us with. This should lead us to look into the challenges surrounding jurisdiction in a much bolder
and comprehensive way than we were able to do. Thatīs why, in essence, we cannot agree with a report that shows the way for some "quick fixes" that, although important, are not sufficient to meet the expectations that led to the incorporation of that particular
stream in WS2.</div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">Best regards,</div>
<div style="font-size:13.3333px"><br>
</div>
<div style="font-size:13.3333px">Benedicto</div>
<div><br>
</div>
</div>
</div>
<div><br>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-size:13px; font-family:Tahoma">
<div class="BodyFragment"><font size="2">
<div class="PlainText"><br>
</div>
</font></div>
</div>
</div>
</div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Verdana}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.msonormal0, li.msonormal0, div.msonormal0
{margin-right:0in;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.EmailStyle18
{font-family:"Calibri",sans-serif;
color:windowtext}
.MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style></div>
<br />--
<br />This message has been scanned for viruses and dangerous content by <br />
<a href="http://www.efa-project.org"><b>E.F.A. Project</b></a>, and is believed to be clean.
</body>
</html>