[NCSG-PC] Statement on content regulation

[Tapani Tarvainen]

+1

On 30 October 2017 13.00.52 GMT+04:00, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
>Once again, I support the statement.
>
>Stephanie
>
>
>On 2017-10-30 04:58, Dr. Tatiana Tropina wrote:
>>
>> Support from me.
>>
>> Tanya
>>
>>
>> On 29/10/17 16:02, Rafik Dammak wrote:
>>> Thanks all, looking to hear from other PC members soon.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> 2017-10-29 18:15 GMT+09:00 Martin Pablo Silva Valent 
>>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>>:
>>>
>>>     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?).
>>>
>>>     But I have nothing to objection to the letter, I followed it in
>>>     NCUC and I think is good.
>>>
>>>     Cheers,
>>>     Martin
>>>
>>>     > On Oct 29, 2017, at 11:33 AM, Tapani Tarvainen
>>>     <ncsg at tapani.tarvainen.info <mailto:ncsg at tapani.tarvainen.info>>
>>>     wrote:
>>>     >
>>>     > Fine by me.
>>>     >
>>>     > Tapani
>>>     >
>>>     > On Oct 29 15:43, Rafik Dammak (rafik.dammak at gmail.com
>>>     <mailto:rafik.dammak at gmail.com>) wrote:
>>>     >>
>>>     >> Hi all,
>>>     >>
>>>     >> as you may know, there was a statement on content regulation
>>>     discussed at
>>>     >> NCUC level and there was a suggestion to make it an NCSG
>statement
>>>     >> https://docs.google.com/document/d/1voPCb3EIi__
>>>     <https://docs.google.com/document/d/1voPCb3EIi__>
>>>     >> umZ1b2RCwkWhyn9wjnLAkiWdenT1dOKo/edit.
>>>     >>
>>>     >> I would like to ask PC members to review it and get it
>>>     endorsed as NCSG
>>>     >> comment. if we got consensus around it, we can make a small
>>>     edit to replace
>>>     >> NCUC occurrences by NCSG. we should get this done within
>ICANN
>>>     meeting in
>>>     >> Abu Dhabi since there was initial consultation at NCUC level.
>>>     >>
>>>     >> as a reminder, we have our policy committee meeting this
>>>     afternoon at 17:00.
>>>     >>
>>>     >> Best,
>>>     >>
>>>     >> Rafik
>>>     > _______________________________________________
>>>     > NCSG-PC mailing list
>>>     > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>     > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>     _______________________________________________
>>>     NCSG-PC mailing list
>>>     NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

Tapani Tarvainen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20171030/25a5be83/attachment.htm>