<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] Potential Topics / Action Items for Wrap-up
- To: WUKnoben <wolf-ulrich.knoben@xxxxxxxxxxx>
- Subject: Re: [council] Potential Topics / Action Items for Wrap-up
- From: Mason Cole <mcole@xxxxxxxxxx>
- Date: Thu, 11 Apr 2013 11:27:12 +0800
- Cc: Wendy Seltzer <wendy@xxxxxxxxxxx>, Jonathan Robinson <jrobinson@xxxxxxxxxxxx>, GNSO Council List <council@xxxxxxxxxxxxxx>
- In-reply-to: <F459CEE2C1AF48B98DAE957DC5EA4B9E@WUKPC>
- List-id: council@xxxxxxxxxxxxxx
- References: <7wi006jo1ct3iowfl8os3ipl.1365644989891@email.android.com> <516623F0.3000808@seltzer.com> <F459CEE2C1AF48B98DAE957DC5EA4B9E@WUKPC>
- Sender: owner-council@xxxxxxxxxxxxxx
I think for the benefit of our time during our public meetings, we could plan
more carefully for the agenda by deciding whether or not a presentation is
necessary in that session. For example, if there's been a) a presentation
during the weekend session on an issue, and b) a work session on the same issue
during the week, where likely the same data was given, perhaps we could request
to dispense with another during our meeting. That doesn't entirely address
Wolf's correct point -- just something to consider.
Sent from my iPad
On Apr 11, 2013, at 11:08 AM, "WUKnoben" <wolf-ulrich.knoben@xxxxxxxxxxx> wrote:
>
> Good point, Wendy. However I'd like to take into consideration that the
> weekend sessions are GNSo sessions (not council only) including newcomers. We
> can't really expect all having dived into the reports in advance.
> Personally I appreciate a brief refreshment of my memory shortly before the
> discussion starts.
>
> Thanks
> Wolf-Ulrich
>
> -----Ursprüngliche Nachricht----- From: Wendy Seltzer
> Sent: Thursday, April 11, 2013 10:46 AM
> To: Jonathan Robinson
> Cc: GNSO Council List
> Subject: Re: [council] Potential Topics / Action Items for Wrap-up
>
>
> I'd like to suggest an update to our working methods: Let's get reports
> or slide-decks in writing in advance and begin at least the weekend
> sessions by taking the reports as read, starting directly with
> questions. It felt as though we spent a long time hearing summaries of
> reports rather than discussing issues with or consensus around them. I
> know I for one process information more thoroughly and more quickly in
> writing.
>
> To aid that, can we ask for a set of links in one place (or even better,
> a single page HTML or PDF) containing everything we're expected to read,
> for advance printing/downloading.
>
> Thanks,
> --Wendy
>
> On 04/10/2013 09:49 PM, Jonathan Robinson wrote:
>>
>> Wrap-up Session - Potential Topics to Cover
>>
>> * GNSO Council Board - Next steps?
>> * GNSO GAC / BGRI WG - Next Steps?
>> * ICANN Durban Meeting Organisation
>> * Response to / letter on EWG?
>> * Policy and Implementation
>> - Outcomes and next steps
>> - Letter from GNSO Council to other SO/ACs?
>> * GNSO Review
>> - Consider self-review
>> - Look at previous GNSO self-review work
>> - Understand link / overlap with ATRT2
>> - Seek update from Ray Plzak
>> * Motions due 8 business days before meeting
>> - Change operating procedures or fix existing ones
>> * Information channels for review of RAA / new gTLD agreement
>> * Privacy/proxy DT
>> * CWG - Where to next?
>> * Review of Motions for next session
>> * Template to request Issue Report
>> * Plural vs. Singular new gTLDs - Any GNSO Council Action / Steps to be
>> taken?
>> * Lack of interest on IDN issues - how to promote next steps / action
>> (Could staff ensure Council is continually appraised of developements?)
>>
>> Action Items:
>>
>> * GNSO Council Chair comment to public forum
>> * GNSO Council Chair to write to:
>> - Board / CEO re Council Policy Advice
>> - Other SO & AC leaders regarding Policy & Implementation
>> - Bruce Tonkin re previous GNSO review
>> - BGRI WG and/or GAC re tabulated summary of policy interaction points
>> Refer timing of motions to SCI (business vs calendar days, as well as time)
>> * GNSO Council Chair to contact Chairs of SO/ACs to ask for interest in
>> policy vs. implementation WG
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|