NCSG-DISCUSS Archives

NCSG-Discuss

NCSG-DISCUSS@LISTSERV.SYR.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Niels ten Oever <[log in to unmask]>
Reply To:
Niels ten Oever <[log in to unmask]>
Date:
Thu, 2 Jun 2016 09:53:38 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
+1 - anyone wants to redraft?

On 06/02/2016 04:57 AM, Dorothy K. Gordon wrote:
> Yes, a good start but with potentially unfortunate unintended consequences unless all of the elements raised; definition of terms, penalties, specifics for conference environments etc. are addressed. 
> 
> ----- Original Message -----
> From: "Wisdom Donkor" <[log in to unmask]>
> To: [log in to unmask]
> Sent: Wednesday, June 1, 2016 10:30:16 PM
> Subject: Re: Public Comments - Revisions to ICANN Expected Standards of Behaviors
> 
> +1 to Avri 
> 
> On Wednesday, June 1, 2016, Cheryl Langdon-Orr < [log in to unmask] > wrote: 
>> I also agree with Avri on this matter... 
>>
>> On 2 Jun 2016 6:49 am, "Tatiana Tropina" < [log in to unmask] > wrote: 
>>
>> + 1 to Avri, 
>> I think this is my problem with this public comment draft (and I left several comments about this in the doc). We do need more, but some of the issues require more time for elaboration. I don't think we can criticise ICANN for the fact that we haven't got more yet, when the document we are commenting on says that the work is in progress. 
>> So agree with the positive comment that will say that it's good start but there is definitely an important work to be done further. 
>> Cheers 
>> Tanya 
>> On 1 June 2016 at 19:24, avri doria < [log in to unmask] > wrote: 
>>>
>>> On 31-May-16 15:58, Mueller, Milton L wrote: 
>>>> From what I can read, I would not support the proposed policy. 
>>>
>>> I find myself agreeing with the comment that we will eventually need 
>>> something more. 
>>> And I think that RFC7704 is a good model. 
>>>
>>> But I think getting into that issue before we resolve wider 
>>> accountability issues WS2 (e.g. ombudsman, or SOAC accountabity) of the 
>>> CCWG-Accountabity is impracticable. I would suggest a statement that 
>>> said good start, lets go with this for now, and determine after WS2, 
>>> perhaps in next ATRT, whether more needs to be done. Some element of the 
>>> issue could probably also feed into WS2 work. 
>>>
>>> avri 
>>>
>>>
>>>
>>> --- 
>>> This email has been checked for viruses by Avast antivirus software. 
>>> https://www.avast.com/antivirus 
>>
>>
> 

-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                   678B 08B5 A0F2 636D 68E9

ATOM RSS1 RSS2