[NCSG-PC] Fwd: [council] REMINDER FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws

[Arsène Tungali]

I share your sentiment that staff should do it and have Council review and approve. Unless the drafting team has enough time, aside from everything else going on now. 

-----------------
Arsène Tungali,
about.me/ArseneTungali
+243 993810967
GPG: 523644A0
Goma, Democratic Republic of Congo

Sent from my iPhone (excuse typos)

> On Jun 12, 2018, at 3:52 AM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
> 
> 
> Hi ,
> 
> the staff sent reminder about next steps for GNSO new roles and responsabilities due to the ICANN accountability changes.
> I am fine with the staff listed actions with regard to guidelines, templates but they are also asking if we want to reinstate the bylaws drafting  team. so I am asking  
> @Farzaneh who was member if she thinks it is good idea to have the drafting team to work on that or just let the staff doing it. I am personally leaning for tasking the staff to do the it but lloking to hear others.
> at the end the work will come back to council to make decision and approve it.
> 
> Best,
> 
> Rafik
> 
> 
> ---------- Forwarded message ---------
> From: Julie Hedlund <julie.hedlund at icann.org>
> Date: mar. 12 juin 2018 à 04:24
> Subject: [council] REMINDER FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws
> To: council at gnso.icann.org <council at gnso.icann.org>
> 
> 
> Dear All,
> 
>  
> 
> Per the message below, this is a reminder to review the proposed next steps to be taken as outlined in the attached table to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws. Staff is seeking feedback on whether the Council is supportive of these proposed next steps or whether modifications should be considered.
> 
>  
> 
> Please note also that unless there are objections, staff could begin to work on the various templates that are identified in the attached table.
> 
>  
> 
> Best regards,
> 
> Julie
> 
> Julie Hedlund, Policy Director
> 
>  
> 
> From: council <council-bounces at gnso.icann.org> on behalf of Julie Hedlund <julie.hedlund at icann.org>
> Date: Wednesday, May 16, 2018 at 10:34 AM
> To: "council at gnso.icann.org" <council at gnso.icann.org>
> Subject: [council] FOR REVIEW: Proposed Next Steps re: GNSO Council's New Roles and Responsibilities Outlined in the Post-Transition Bylaws
> 
>  
> 
> Dear All,
> 
>  
> 
> Following the adoption by the GNSO Council of the revised GNSO Operating Procedures, as well as the proposed modifications to the ICANN Bylaws adopted by the ICANN Board of Directors on 13 May, staff has outlined in the attached table the additional proposed steps to be taken to ensure preparedness as well as facilitate the ability for the GNSO Council to act in relation to the new roles and responsibilities outlined in the post-transition Bylaws.
> 
>  
> 
> The GNSO Council is requested to review the proposed next steps and to provide feedback whether it is supportive of these proposed next steps or whether modifications should be considered.
> 
>  
> 
> Best regards,
> 
> Julie
> 
> Julie Hedlund, Policy Director
> 
>  
> 
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
> <GNSO Operational Procedures Template & Guidance List 15 May 2018.pdf>
> <smime.p7s>
> <smime.p7s>
> _______________________________________________
> 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/20180612/7691aff6/attachment.htm>