<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] Extra day
- To: Council <council@xxxxxxxxxxxxxx>
- Subject: [council] Extra day
- From: Rubens Kuhl <rubensk@xxxxxx>
- Date: Thu, 10 Mar 2016 13:00:36 +0000
- Authentication-results: mail.nic.br (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.br; s=dkim; t=1457614840; bh=1ErcsVJy/cmospL0DHo41+Kn+pigwuPzq8QE29FkNMY=; h=From:Subject:Date:To:From; b=XX9Vb0CYVl2K38IDPvE1HwozhzBryuiaqQPyipF3JlmtREHySSq/muo9wPG5Wd82l ikOXAAFCIabqKo9DIBVpV2GMLJVExOaB8l00RioQJHcsOaPClLZa7bexT1xHKblniM 9mQiUjJxSxgmkBVk5gSfDlunl8mbcPrOft7MX7oI=
- Dmarc-filter: OpenDMARC Filter v1.3.1 mail.nic.br 50DD0188FA6
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
Since there was not enough time during our wrap-session to discuss this, I'll
write my thoughts on this for Donna, Volker and the council to consider
I fully support Donna's position that we should reject this idea and focus most
days of a B meeting on policy. If ICANN is also doing outreach, those tracks
could run side-by-side instead of outreach taking an amount of days (even if
only 1) and leaving the others day to policy.
I also have to take exception with adding extra days; for those traveling from
distant regions, travel affordability is tied to booking flights and hotels
many months in advance. When days are added before or after a meeting, what
happens is that those that already booked end up either incurring in costs or
missing the added sessions. One of the good outcomes of the new meeting
strategy was we committing to a fixed schedule, and this is now at risk.
Rubens
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|