[NCSG-PC] Reminder Comment on GNSO Community Comment 2 (CC2) on New gTLD Subsequent Procedures

Rafik Dammak rafik.dammak at gmail.com
Sun May 28 12:04:56 EEST 2017


Hi all,

The comments were resolved, including the deletion suggested by Ed. With
the review done by Ayden, Stephanie, Matt, Ed  and myself and there was no
objection from the rest, I interpret that as we can submit the NCSG comment
on CC2. the working group will have its confcall tomorrow and there is an
update about community comments on the agenda, it will be good to submit
prior to that.
I attached the latest version that I will submit.

Best,

Rafik

2017-05-26 20:47 GMT+09:00 Ayden Férdeline <icann at ferdeline.com>:

> I can support this change.
>
> Ayden Férdeline
> Sent from ProtonMail Mobile
>
>
> On Fri, May 26, 2017 at 12:45 pm, Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
>
> Hi Ed,
>
> Thanks for the comment.
> I can delete that line since it won't change the meaning of what precedes
> it. I will wait for other members if they are fine with that change.
>
> Best,
>
> Rafik
>
> 2017-05-26 20:27 GMT+09:00 Edward Morris <egmorris1 at toast.net>:
>
>> Hi Rafik,
>>
>> I've made a suggested edit (although have not removed the line, pending
>> receipt of others views) in paragraph 7. Specifically calling for
>> contractual compliance in the ICANN environment traditionally has meant
>> zealous enforcement of alleged intellectual monopoly rights. Contracts
>> should be enforced: agreements are made to be honoured. That doesn't need
>> to be stated. Making a specific point calling for contractual compliance
>> plays into the IPC and CSG positions; I'd suggest that it is
>> counterproductive for the NCSG to specifically call for such action. The
>> line in question:
>>
>> *ensuring contractual compliance of the Registry Agreement is key to this
>> discussion as it enables a proper maintenance of what has been agreed
>> between the parties. *
>>
>> The rest of the document is a good compromise between competing views in
>> the NCSG on a variety of issues. I'm happy to support if the above line is
>> removed. Otherwise count me as an abstain: strict contractual compliance,
>> in ICANN-speak, is not something the NCSG should be calling for or
>> supporting.
>>
>> Ed
>>
>>
>>
>> ------------------------------
>> *From*: "Rafik Dammak" <rafik.dammak at gmail.com>
>> *Sent*: Friday, May 26, 2017 11:44 AM
>> *To*: "ncsg-pc" <ncsg-pc at lists.ncsg.is>, "Martin Pablo Silva Valent" <
>> mpsilvavalent at gmail.com>, "Poncelet Ileleji" <pileleji at ymca.gm>,
>> "Marilia Maciel" <mariliamaciel at gmail.com>, "Milan, Stefania" <
>> Stefania.Milan at eui.eu>, "Ayden Férdeline" <icann at ferdeline.com>,
>> "Matthew Shears" <matthew at intpolicy.com>, "Stephanie Perrin" <
>> stephanie.perrin at mail.utoronto.ca>, "Edward Morris" <egmorris1 at toast.net>,
>> "Juan Manuel Rojas" <jumaropi at yahoo.com>
>> *Subject*: Re: Reminder Comment on GNSO Community Comment 2 (CC2) on New
>> gTLD Subsequent Procedures
>>
>> Hi all,
>>
>> it is time to make a decision with regard to the CC2 comment
>> https://docs.google.com/document/d/133uzvDQI__EmNGhqiDkHW0Ev
>> fvKOwLE9m7ozNIZUVNY/edit. please review it and send your vote. we need
>> clear support here. if we can reach conclusion by Today 23:59UTC it will be
>> good since we also have to submit the SO/AC accountability comment.
>> @Avri did the staff start working on the comments report?
>>
>> Best,
>>
>> Rafik
>>
>> 2017-05-25 8:45 GMT+09:00 Rafik Dammak <rafik.dammak at gmail.com>:
>>>
>>> hi all,
>>>
>>> we need to finish reviewing and finalizing the CC2 comment. the public
>>> consultation ended this Monday, we don't have much time to extend. I
>>> suggested previously Wednesday as the deadline but I only saw a comment
>>> from Ayden in the NCSG list.
>>>
>>> I would like to ask all members of policy committee to review the draft
>>> and then share their positions about endorsing it or not. for those who
>>> make comments in the google doc, please suggest wording or new text, that
>>> would be helpful to solve them.
>>> Thanks,
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>> ---------- Forwarded message ----------
>>> From: Rafik Dammak <rafik.dammak at gmail.com>
>>> Date: 2017-05-22 9:01 GMT+09:00
>>> Subject: Comment on GNSO Community Comment 2 (CC2) on New gTLD
>>> Subsequent Procedures / Consultation and review
>>> To: "NCSG-DISCUSS at listserv.syr.edu " <NCSG-DISCUSS at listserv.syr.edu >,
>>> ncsg-pc <ncsg-pc at lists.ncsg.is>
>>>
>>>
>>> Hi all,
>>>
>>> Bruna kindly volunteered and drafted this response to the Community
>>> Comment consultation from the new gTLD subsequent procedures working group
>>> for NCSG https://docs.google.com/document/d/133uzvDQI__EmNGhqiDkHW0Ev
>>> fvKOwLE9m7ozNIZUVNY/edit. the details about the public consultation are
>>> here https://www.icann.org/public-comments/cc2-new-gtld-subs
>>> equent-procedures-2017-03-22-en.
>>>
>>> The deadline for submission is the 22nd May, so we have a short time to
>>> do so. I think we can attempt a late submission and hopefully be accepted
>>> by the working group. We should review, add comments, editing and be
>>> tidying up the document in the next 3 days and submitting by this Wednesday
>>> after endorsement by the policy committee. because of the time constraints,
>>> please add wording and edits when you make comments.
>>>
>>> looking forward your participation and asking those who were involved in
>>> the previous new gTLD policy discussion to jump in.
>>>
>>> Best,
>>>
>>> Rafik
>>>
>>
>> ______________________________ _________________
>> 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/20170528/eeb75594/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NCSGproposedCommentonCC2.pdf
Type: application/pdf
Size: 62459 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170528/eeb75594/attachment.pdf>


More information about the NCSG-PC mailing list