[PC-NCSG] GNSO DT new ICANN meeting strategy

[Sam Lanfranco]

David hits on the key issue in the scheduling of the time during 
meetings: /"but don?t want the middle meeting, which is supposed to be 
the SO/AC focussed meeting, to have less actual time for SO/AC work."/ 
Here is where we dig our heals in and insist on shaping the schedule. It 
is our time, our labour, and our ICANN work to get done. What is 
valuable is our time, what we do with it, and what we accomplish. A 
meeting schedule is designed to facilitate that, and we are obliged to 
insist (if necessary) that there be a sensible schedule.

As for shorter or longer revised meetings, I have no personal views 
there other than to say the marginal costs of shorter are trivial, 
basically hotel nights and per diems, probably less than 10% of an 
anyhow smaller overall budget. As for smaller attendance, that is 
important and I don't want that to fall off the table since it is 
ICANN's, and our, gateway to greater presence and engagement with 
ICANN's and our constituencies in currently under engaged regions.

An aside on costs: While some may see covering our travel and (some) 
expenses as ICANN's /*perks to us*/, it is quite the opposite. That is 
ICANN's cost so that ICANN can extract/receive /*perks from us*/ in the 
form  our labour, skills and wisdom in ICANN's multistakeholder process. 
When my cousin sends a wine lobbyist to Washington D.C., he doesn't see 
the travel, accommodations and per diem as "perks", they are the costs 
to his operation of getting his (paid) labour in position to work. While 
there are always "free riders" and volunteers who gain private benefit 
(retainers, etc.) in any group like the ours, the core of the process is 
us providing ICANN with perks.

Sam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20150305/2423cb16/attachment.html>