<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, "EmojiFont", "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Dear all,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">At the GAC session at ICANN61 today, the representative of Brazil reported on the moves to solve the .amazon issue after Amazon presented its compromise proposal at ICANN60. Soon after, the Amazon Cooperation Treaty
Organization (OCTA) decided to consider Amazon's proposal. An OCTA working group asked Amazon additional questions, and the replies were received on 5 March. They are now being analyzed by the working group, which hopes to to present its report to OCTA
before mid-April. <br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">OCTA consists of <span>Bolivia, Brazil, Colombia, Ecuador, Guyana, Peru, Suriname and Venezuela.</span><br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">The Board had inquired whether the GAC wanted to give it any additional information on the .amazon matter. In view of the ongoing contacts between OCTA goverments and Amazon, the GAC decided to reply that at this
time it has none. <br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">So there seems to be light at the end of the tunnel.<br>
</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Best,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Yrjö<br>
</p>
</div>
</body>
</html>