[NCSG-PC] Response to IPC/BC model

farzaneh badii farzaneh.badii at gmail.com
Fri Apr 6 02:21:10 EEST 2018


Rafik

Very good point. We should not submit to the email address they provided.
We can send it as a correspondence to the CEO, and use GDPR public comment
address. IPC/BC cannot come up with their own comment analysis and their
process. We have to make it clear that the only reason we are making the
comment is for ICANN and the rest of the community know what we think about
it.

Farzaneh

On Thu, Apr 5, 2018 at 4:09 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> Hi all,
>
> while still reviewing the draft as there were several changes lately, with
> regard to whom to send I don't think there are mutually exclusive options
> here. it can be sent to BCC and IPC, Goran and Cherine, to the ICANN GDPR
> dedicated mail address.  no problem here.
>
> but I would like that make clear that by sending this letter or de facto
> input to BC/IPC, are we stating implicitly or not that we will participate
> in their ad hoc process regarding the accreditation model from now on? this
> is something we have to be clear about when communicating with them,
>
> Best,
>
> Rafik
>
> 2018-04-06 8:03 GMT+09:00 Stephanie Perrin <stephanie.perrin at mail.
> utoronto.ca>:
>
>> The whole process is flawed, I think we should send it to the GDPR
>> address so that it is put on the web under community feedback on models.
>>
>> Stephanie
>> On 2018-04-05 18:36, Kathy Kleiman wrote:
>>
>> It seems a little funny to send me to send a copy directly to winterfeldt
>> law -- how about just the first email address?
>>
>> Also, perhaps we should publish our comment...
>>
>> Best, Kathy
>>
>> On 4/5/2018 6:30 PM, Ayden Férdeline wrote:
>>
>> They have asked that comments be sent to:
>>
>> stakeholders can provide written comments on the accreditation model
>> proposal to 3amcomments at gmail.com, with a copy to
>> internet at winterfeldt.law.
>>
>> I hope all comments will be publicly published. Feels a little odd simply
>> sending this to a Gmail account.
>>
>> Ayden
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On 6 April 2018 12:27 AM, Kathy Kleiman <kathy at kathykleiman.com>
>> <kathy at kathykleiman.com> wrote:
>>
>> Hi Ayden, Good question. I think we should send it to Cherine and Goran
>> and copy the email address in which Brian Winterfeldt and his law firm
>> asked for "comments.'
>>
>> *I can't seem to find that email address right now -- would you happen to
>> have it?*
>>
>> All on the PC, I'm downloading the document shortly for final check of
>> the citations and formatting. Google doc does not make indented citations
>> easy :-).  No more edits, please.  I'll have this over to Rafik and Farzi
>> shortly.
>>
>> Best, Kathy
>>
>> On 4/5/2018 6:17 PM, Ayden Férdeline wrote:
>>
>> I understand from the notifications from Google that changes are being
>> accepted, that work is still underway editing this document and getting it
>> into a submittable state. So I suppose now is the time to ask, who are we
>> sending this letter to? BC Chair and IPC President, with Goran and Cherine
>> in cc?
>>
>> -- Ayden
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On 4 April 2018 4:09 AM, Kathy Kleiman <kathy at kathykleiman.com>
>> <kathy at kathykleiman.com> wrote:
>>
>> Hi All,
>>
>> Tx to Ayden for his excellent edits, now incorporated (with a few
>> comments highlighting proposed rephrasing, Ayden). Tx also to Martin for
>> his review!
>>
>> Back to the PC to continue review...
>>
>> Best, Kathy
>>
>> On 4/3/2018 7:40 PM, Martin Pablo Silva Valent wrote:
>>
>> I am reading it now, but between Kathy and Ayden’s work, it looks good to
>> go. I’ll add my comments if any. So far, my full support.
>>
>> Cheers,
>> Martín
>>
>>
>> On 3 Apr 2018, at 20:38, Ayden Férdeline <icann at ferdeline.com> wrote:
>>
>> Hi,
>>
>> I have reviewed the document now and put forward some suggested edits.
>> Some are substantive changes but all are in the same spirit of the original
>> text.
>>
>> The formatting looks a bit odd; I hope the text alignments can be
>> corrected prior to submission.
>>
>> I think the conclusion lacks punch; but can’t think of what it is missing
>> at the moment...
>>
>> Best wishes,
>>
>> Ayden
>>
>> P.S. Thanks to those who drafted it
>>
>>
>> On Wed, Apr 4, 2018 at 01:24, Rafik Dammak <rafik.dammak at gmail.com>
>> wrote:
>>
>> Hi Farzaneh,
>>
>> thanks for this.
>> I would like to ask PC members to review it asap.
>>
>> Best,
>>
>> Rafik
>>
>> 2018-04-04 6:57 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>>
>> Hi all
>>>
>>> Im on a plane so let me know if the link below is correct. Kathy has
>>> written a response on ipc bc
>>>
>>> https://docs.google.com/document/d/16miuxuAYYgwUQHPde8N02W6G
>>> 84oibuV9m4W3ZTeI_SA
>>>
>>>
>>> We need to go through it asap and send it before their meeting.
>>>
>>> Please comment quickly and make sure you are on suggestion mode (i set
>>> it that way not sure it went through)
>>> --
>>>
>>> Farzaneh
>>>
>>> _______________________________________________
>>> 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
>>
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>>
>>
>>
>> _______________________________________________
>> NCSG-PC mailing listNCSG-PC at lists.ncsg.ishttps://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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20180405/34a42b88/attachment.htm>


More information about the NCSG-PC mailing list