<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Support from me.</p>
<p>Tanya <br>
</p>
<br>
<div class="moz-cite-prefix">On 29/10/17 16:02, Rafik Dammak wrote:<br>
</div>
<blockquote
cite="mid:CAH5sThkAzWw9ix5-k+7yek2aQ=W6d42kHazKZdpSkcE=10EYyw@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_extra">Thanks all, looking to hear from other
PC members soon.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Best,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Rafik<br>
<br>
<div class="gmail_quote">2017-10-29 18:15 GMT+09:00 Martin
Pablo Silva Valent <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:mpsilvavalent@gmail.com" target="_blank">mpsilvavalent@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I
support the statement, I even think we could go a little
further and mention the cases we see are live and
concerning us, like the alternative methods of right
protections mechanism that some registries/registrar are
implementing in new gTLDs, creating whole mechanism of
content control over DNS layer (should the be free to do
it?).<br>
<br>
But I have nothing to objection to the letter, I followed
it in NCUC and I think is good.<br>
<br>
Cheers,<br>
Martin<br>
<div class="m_8239454405952752280HOEnZb">
<div class="m_8239454405952752280h5"><br>
> On Oct 29, 2017, at 11:33 AM, Tapani Tarvainen
<<a moz-do-not-send="true"
href="mailto:ncsg@tapani.tarvainen.info"
target="_blank">ncsg@tapani.tarvainen.info</a>>
wrote:<br>
><br>
> Fine by me.<br>
><br>
> Tapani<br>
><br>
> On Oct 29 15:43, Rafik Dammak (<a
moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>)
wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> as you may know, there was a statement on
content regulation discussed at<br>
>> NCUC level and there was a suggestion to make
it an NCSG statement<br>
>> <a moz-do-not-send="true"
href="https://docs.google.com/document/d/1voPCb3EIi__"
rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/1voPCb3EIi__</a><br>
>> umZ1b2RCwkWhyn9wjnLAkiWdenT1dO<wbr>Ko/edit.<br>
>><br>
>> I would like to ask PC members to review it
and get it endorsed as NCSG<br>
>> comment. if we got consensus around it, we
can make a small edit to replace<br>
>> NCUC occurrences by NCSG. we should get this
done within ICANN meeting in<br>
>> Abu Dhabi since there was initial
consultation at NCUC level.<br>
>><br>
>> as a reminder, we have our policy committee
meeting this afternoon at 17:00.<br>
>><br>
>> Best,<br>
>><br>
>> Rafik<br>
> ______________________________<wbr>_________________<br>
> NCSG-PC mailing list<br>
> <a moz-do-not-send="true"
href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
> <a moz-do-not-send="true"
href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc"
rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
<br>
______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a moz-do-not-send="true"
href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a moz-do-not-send="true"
href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc"
rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br>
</body>
</html>