[PC-NCSG] fw: [council] MOTION TO CREATE A DRAFTING TEAM TO FURTHER DEVELOP RECOMMENDATIONS TO IMPLEMENT THE GNSO'S NEW ROLES AND OBLIGATIONS UNDER THE REVISED ICANN BYLAWS

[Marilia Maciel]

I agree with the proposal. James G asked the PC to discuss the topic and I
suggested him to take to NCSG list. Whatever shape the discussions takes
from now on - small group working with councillors, etc - our SG members
will be aware and can potentially chime in.
M

On Fri, Jun 24, 2016 at 5:05 AM, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> wrote:

> I think leaving it in Council is a good idea, lets see if we can get the
> registrars to support the idea....and fast.  We have an opportunity to do a
> little lobbying at the COuncil dinner.  ANyone know where the BC sits on
> this issue?
>
> SP
>
> On 2016-06-23 22:48, Kathy Kleiman wrote:
>
> A belated response, Ed, that this is very concerning. I think it will wind
> up with things "stacked" in favor of the IPC. Sigh. I support your idea of
> leaving this matter in Council - and hope we can discuss it at the NCSG
> Policy session on Tuesday.
> Best, Kathy
>
> On 6/20/2016 2:03 PM, Edward Morris wrote:
>
> Hi everyone,
>
> Attached please find an IPC Motion to create a drafting team to develop
> GNSO responses to changes brought by the transition.
>
> This is a different approach that what has previously been discussed. What
> concerns me is the possibility under this plan for the NCSG to be
> inadequately represented on the proposed drafting team. It would appear to
> be an open call for volunteers with the following qualifications:
>
> -
>
>    1. The Drafting Team shall comprise volunteers from the GNSO community
>    who can demonstrate reasonable knowledge of or experience with the process
>    of revising the ICANN Bylaws.
>
>
> I might like that language if I were from a constituency composed
> principally of lawyers such as the IPC.
>
> I would prefer to have Council, working with staff, to make the needed
> changes. We have a fairly collegial working environment and the expertise
> to get this done in a fairly time efficient manner with full representation
> of all stakeholder groups. If we are going to farm this out I'd suggest we
> need to insist on equal representation of all stakeholder groups on the
> Drafting Team with appointments being made directly by the SG's themselves
> according to their own criteria.
>
> Thoughts?
>
> Best,
>
> Ed
>
>
>
>
>
> ------------------------------
> *From*: "Paul McGrady" <policy at paulmcgrady.com><policy at paulmcgrady.com>
> <policy at paulmcgrady.com>
> *Sent*: Monday, June 20, 2016 6:35 PM
> *To*: council at gnso.icann.org
> *Cc*: "Glen de Saint G?ry" <Glen at icann.org> <Glen at icann.org>,
> mary.wong at icann.org, "Heather Forrest" <Heather.Forrest at acu.edu.au>
> <Heather.Forrest at acu.edu.au>
> *Subject*: [council] MOTION TO CREATE A DRAFTING TEAM TO FURTHER DEVELOP
> RECOMMENDATIONS TO IMPLEMENT THE GNSO'S NEW ROLES AND OBLIGATIONS UNDER THE
> REVISED ICANN BYLAWS
>
>
> Dear Council Colleagues:
>
>
>
> As we all know, making the Empowered Community a reality is going to take
> a lot of effort by everyone.  To get us started in that process, attached
> please find a MOTION TO CREATE A DRAFTING TEAM TO FURTHER DEVELOP
> RECOMMENDATIONS TO IMPLEMENT THE GNSO?S NEW ROLES AND OBLIGATIONS UNDER THE
> REVISED ICANN BYLAWS which is being proposed by the IPC for consideration
> at the next GNSO Council meeting in Helsinki.  Safe travels!
>
>
>
> Best,
>
> Paul
>
>
>
> Paul McGrady
>
> GNSO Councilor for the IPC
>
> policy at paulmcgrady.com
>
>
>
>
>
>
> _______________________________________________
> PC-NCSG mailing listPC-NCSG at ipjustice.orghttp://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
>
>
> _______________________________________________
> PC-NCSG mailing listPC-NCSG at ipjustice.orghttp://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
>
> _______________________________________________
> PC-NCSG mailing list
> PC-NCSG at ipjustice.org
> http://mailman.ipjustice.org/listinfo/pc-ncsg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20160624/8cb24bb0/attachment.html>