<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [gnso-policyimpl-wg] A new twist to Implementation Review Teams
- To: Alan Greenberg <alan.greenberg@xxxxxxxxx>, "GNSO-policyimpl-wg@xxxxxxxxx" <GNSO-policyimpl-wg@xxxxxxxxx>
- Subject: RE: [gnso-policyimpl-wg] A new twist to Implementation Review Teams
- From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
- Date: Thu, 5 Feb 2015 19:37:53 +0000
Good observation Alan. Do you think that we should consider adding something
to the report in this regard? I think your observation would make a good
comment regarding the implementation framework in the report.
Chuck
-----Original Message-----
From: owner-gnso-policyimpl-wg@xxxxxxxxx
[mailto:owner-gnso-policyimpl-wg@xxxxxxxxx] On Behalf Of Alan Greenberg
Sent: Wednesday, February 04, 2015 9:33 PM
To: GNSO-policyimpl-wg@xxxxxxxxx
Subject: [gnso-policyimpl-wg] A new twist to Implementation Review Teams
We have had a lot of discussion about
Implementation Review Teams and particular who leads them. The consensus was
that they are led by the GDD person responsible for the implementation project.
The appended thread demonstrates a little problem that arose in the ThickWhois
IRT. GNSO Policy Staff (and the GNSO Vice-chair charged with meeting
scheduling) spend an inordinate amount of time finding slots for meetings that
minimize overlaps. I am guessing that the Thickwhois IRT was scheduled by GDD
without that level of consultation and resulted with the IRT meeting
overlapping with the GNSO Wrap-up.
Nothing particularly onerous but it demonstrates yet another way aspect of the
need for coordination following the transfer of responsibility when the GNSO
hands the project over to the GDD.
Alan
>From: Fabien Betremieux <fabien.betremieux@xxxxxxxxx>
>To: "gnso-impl-thickwhois-rt@xxxxxxxxx"
><gnso-impl-thickwhois-rt@xxxxxxxxx>
>Date: Wed, 4 Feb 2015 18:21:27 +0000
>Subject: Re: [Gnso-impl-thickwhois-rt] "thick" WHOIS IRT F2F in
>Singapore
>
>
>Dear colleagues,
>
>Unfortunately, we will not able to move the meeting without potentially
>creating new conflicts, including for the Implementation Project Team
>and other supporting staff. We apologize for this inconvenience.
>
>I am sure you can appreciate the complexity of the planning endeavor
>and the care that was given to avoid conflicts as much as possible.
>
>Here is how I propose we mitigate the impact of the conflicts that were
>reported:
>- we will discuss the update on the legal review in the first half hour
>of the meeting so that it does not conflict with the GNSO Wrap-up
>Meeting
>- we will provide recordings and transcripts
>- and we will provide an opportunity for all to contribute to the
>discussion in the week after the meeting.
>
>The agenda of our meeting as well as material for your consideration
>will follow.
>
>Thank you for your comprehension and participation.
>--
>Fabien Betremieux
>Sr. Registry Services & Engagement Manager Global Domains Division,
>ICANN
>
>
>
>
>
>
>On 1/28/15, 10:18 PM, "Fabien Betremieux" <fabien.betremieux@xxxxxxxxx>
>wrote:
>
> >Dear Colleagues,
> >
> >Thank you Amr for raising this concern.
> >
> >I am interested to know if this is creating a conflict for anybody
> >else in the IRT so that we can look into potential mitigations strategies.
> >
> >Moving the session may be very difficult because as it is already an
> >outcome of a complex multi-variable optimization exercise, but we
> >could also consider other solutions, including for example arranging
> >the agenda so that the affected participants can take part in what is
> >the most important to them and they can possibly catch up on the
> >recording later for the rest.
> >
> >Please let me know as soon as possible, and by the end of this week
> >at the latest.
> >
> >Thanks in advance
> >
> >--
> >Fabien Betremieux
> >Sr. Registry Services & Engagement Manager Global Domains Division,
> >ICANN
> >
> >
> >
> >
> >On 1/28/15, 4:39 PM, "Amr Elsadr" <aelsadr@xxxxxxxxxxx> wrote:
> >
> >>Hi,
> >>
> >>I just noticed that the IRT©ös meeting in Singapore partly overlaps
> >>with the GNSO wrap up meeting. That is unfortunate.
> >>
> >>Thanks.
> >>
> >>Amr
> >>_______________________________________________
> >>Gnso-impl-thickwhois-rt mailing list
> >>Gnso-impl-thickwhois-rt@xxxxxxxxx
> >>https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt
>
>
>_______________________________________________
>Gnso-impl-thickwhois-rt mailing list
>Gnso-impl-thickwhois-rt@xxxxxxxxx
>https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|