[NCSG-PC] Open Public comments

[Robin Gross]

Absolutely, Rafik.  Thank you.  I’d like to encourage NCSG PC members to attend the NCSG’s CCWG ACCT discussion on 28 February (next Tuesday at 20:00 UTC ) so we can have a shared understanding of these issues and comments to be filed.

Best,
Robin


> On Feb 22, 2017, at 5:04 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
> 
> Hi Ed,
> 
> thanks for the response and suggestion. I added Robin in cc.
> I am happy if the group manage to cover any upcoming public comments from CCWG, while the NCSG PC still should follow closely and be ready for review and endorsement. 
> 
> @Robin can you please liaise with us for any CCWG ws2 related comments that NCSG needs to submit a statement on.
> 
> Best,
> 
> Rafik
> 
> 2017-02-23 9:44 GMT+09:00 Edward Morris <egmorris1 at toast.net <mailto:egmorris1 at toast.net>>:
> Hi Rafik,
>  
> On the Transparency public comments, as well as other public comments related to the CCWG - Accountability, might I suggest delegating that to Robin's Accountability group. There are going to be about a dozen public comments coming out of the CCWG over the next half year. It might be best to split those off of the general public comments and organise them initially within the NCSG Accountability group.  Robin's done a fantastic job organising our CCWG comments in the past - we have a call next Tuesday and that would probably be a good place to get started on it.
>  
> Just a suggestion - as Michael is a co-chair of the Transparency group and is part of the NCSG Accountability group that might be a resource we could use for informational purposes there.
>  
> Thanks for getting on top of all of these comments.
>  
> Best,
>  
> Ed
>  
>  
>  
> From: "Rafik Dammak" <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>
> Sent: Thursday, February 23, 2017 12:25 AM
> To: "ncsg-pc" <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>>
> Subject: [NCSG-PC] Open Public comments
>  
> Hi everyone,
>  
> From the Public Comments page, I picked the 3 consultations that seem relevant for us and we had some discussion about. this is kind of planning for us to cover public comments:
> GNSO Initial Report on the IGO-INGO Access to Curative Rights Protection Mechanisms Policy Development Process, https://www.icann.org/public-comments/igo-ingo <https://www.icann.org/public-comments/igo-ingo> , deadline 1 Mar 2017 
> At-Large Review: Draft Report,  https://www.icann.org/public-comments/atlarge-review-draft-report-2017-02-01-en <https://www.icann.org/public-comments/atlarge-review-draft-report-2017-02-01-en>, deadline 24 Mar 2017 
> Recommendations to Improve ICANN's Transparency, https://www.icann.org/public-comments/ccwg-acct-draft-recs-2017-02-21-en <https://www.icann.org/public-comments/ccwg-acct-draft-recs-2017-02-21-en> , deadline 10 Apr 2017 
> the first consultation is quite close, less than 1 week and the topic is important for us. We have an urgent need to get a volunteer to draft a quick comment. I am wondering if Kathy can jump in here. In any case, as PC we will have to act quickly if we get a statement to review.
>  
> for at-large review, I would like to volunteer Ayden since he followed the discussion closely and read the report. @Ayden can you please start drafting and share the document with the wider NCSG list for consultation?
>  
> for the last one, related to ICANN accountability work, it will be great to have someone involved in the CCWG to take the lead here. Maybe Matthew? 
>  
> while I am suggesting names among those in PC List, we can try to find other members take the lead or help.
>  
> in term of planning for future public comments, we can follow upcoming consultations here https://www.icann.org/resources/pages/upcoming-2012-02-25-en <https://www.icann.org/resources/pages/upcoming-2012-02-25-en> to get an idea about what is coming (dates are of course tentative).
>  
> there is also this separate page about "operational" public comments https://www.icann.org/public-comments-operational <https://www.icann.org/public-comments-operational> , something to follow more closely.
>  
> Best,
>  
> Rafik
>  
>  
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20170223/8ddf4985/attachment.htm>