[CCWG-ACCT] CCWG-ACCT request for information on CEP
Dr Eberhard W Lisse
el at lisse.na
Sat Apr 11 06:52:51 UTC 2015
I really find that using (uncommon) abbreviations, such as CEP for Cooperative Engagement Process without at least defining them, saves the author very little time but complicates understanding for the (casual) reader.
And I mention this because this ICANN abbreviatitis has irritated me for a long while.
That said, while I agree with you, and support your transparency request, the interactions of the IANA Functions Manager with ccTLD Managers (which is what I am interested in and concerened with) are as transparent as a concrete wall which gets clad in a lead lining when existing rights of an incumbent are affected.
This will have to change (process), through this CCWG. And we will also look at the way they do things (substance).
Even if being ignored, this is not negotiable come consensus call.
Sent from Dr Lisse's iPhone 6
> On Apr 10, 2015, at 21:14, Robin Gross <robin at ipjustice.org> wrote:
> Thanks Becky and Sam,
> Thanks for the information about the CEP process. I note a few proposed improvements to this process below.
> A party who files a CEP should not be required to keep those discussions confidential. While I understand a party may wish to have the process be confidential, there have been times, when this imposed confidentiality rule has been problematic. For example, NCSG participated in a CEP about how an ICANN policy was decided, and we requested that these CEP conversations be recorded and transcribed in the interests of transparency around the internal decision making process. This request was denied by ICANN. We also requested that our written submission to the CEP become part of the public record of the process and ICANN also refused to post the NCSG CEP submission to its website. So there are times when the imposed confidentially of the CEP is in great contrast to our promises about policy being made in a transparent fashion. A party's CEP written submission should be published at the option of the filer, who can waive his/her confidentiality if desired.
> We also need a much clearer process than "there will be discussions on unresolved issues" type statements that we currently have. The lack of any clear expectation on the part of someone going through this CEP process about what those discussions will entail and how to prepare for them has been an impediment to the process. The details of this engagement process need to nailed down more tightly so people know how this process is managed and what to expect. There is currently too much leeway for ICANN to dictate the terms of the CEP discussions on an ad hoc basis and this puts filers at an unfair advantage due to the lack of clarity.
> So these would be my suggested improvements to the CEP - more transparency and more clarity in the process.
> Thank you,
>> On Apr 10, 2015, at 12:35 PM, Samantha Eisner wrote:
>> Hi Becky - the Cooperative Engagement Process is set forth here:
>> ICANN is now publishing updates as it relates to items that are within the
>> CEP process, and those updates can be found on the IRP document page, at
>> the top (including archives) at
>> There is also a reference to the Cooperative Engagement Process within the
>> Bylaws on the IRP (Art IV, Section 3, paras 15-17)
>>> On 4/10/15, 6:19 AM, "Burr, Becky" <Becky.Burr at neustar.biz> wrote:
>>> Hello ICANN folks.
>>> As you probably know, I am serving on WP2, which is focused on reviewing
>>> and proposing reforms/enhancements to existing accountability mechanisms.
>>> One issue that has been raised, and about which there seem to be strong
>>> feelings, is the Constructive Engagement Process.
>>> Could you please point me to documentation for this process, and any
>>> rules, guidelines, principles applicable to it.
>>> Many thanks
>>> Sent from my iPad
>>> Accountability-Cross-Community mailing list
>>> Accountability-Cross-Community at icann.org
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Accountability-Cross-Community