<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] For your information - revised version of GNSO Operating Procedures available
- To: Council <council@xxxxxxxxxxxxxx>
- Subject: Re: [council] For your information - revised version of GNSO Operating Procedures available
- From: Amr Elsadr <aelsadr@xxxxxxxxxxx>
- Date: Wed, 15 Jul 2015 14:08:53 +0200
- In-reply-to: <D1CAA409.460D4%marika.konings@icann.org>
- List-id: council@xxxxxxxxxxxxxx
- References: <D1CAA409.460D4%marika.konings@icann.org>
- Sender: owner-council@xxxxxxxxxxxxxx
Hi,
Thank you very much for this, Marika. While we’re on the topic, I have a
question that I’m hoping you can help me figure out an answer to. Apart from
the processes the GNSO Council recommended be created, how would adoption of
the various principles detailed in the policy and implementation working group
final report take place (in the event that the ICANN board votes in favour of
adopting them)? Would these be reflected by changes in the ICANN bylaws?
Thanks again.
Amr
On Jul 14, 2015, at 11:33 AM, Marika Konings <marika.konings@xxxxxxxxx> wrote:
> Dear All,
>
> For your information, per the GNSO Council’s resolution of Buenos Aires (see
> http://gnso.icann.org/en/council/resolutions#20150624-2), an updated version
> of the GNSO Operating Procedures has been posted and is now in effect (see
> GNSO Operating Procedures v3.0). This version includes a new Annex III (see
> ANNEX III: Input Process Manual) that covers the GNSO Input Process and
> updates have been made to section 14 of the PDP manual (see ANNEX II Policy
> Development Process Manual) to reflect that the formation of Implementation
> Review Team (IRT) is mandatory following the adoption of GNSO policy
> recommendations by the ICANN Board, unless in exceptional circumstances the
> GNSO Council determines that an IRT is not required.
>
> Best regards,
>
> Marika
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|