It can also pose interesting issues pertaining to travel.
—Tom
On Jun 21, 2017:9:53 AM, at 9:53 AM, Christian Huitema
<huitema(_at_)huitema(_dot_)net> wrote:
On 6/21/2017 5:46 AM, Bob Hinden wrote:
Alissa,
On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa(_at_)cooperw(_dot_)in>
wrote:
Hi all,
Based on a suggestion from Paul Hoffman, the IESG believes it would be
beneficial to denote the official start of IETF meetings to be on Saturday
rather than Sunday, starting with IETF 100. We believe this would be
sensible given that events such as the hackathon and code sprint start on
Saturday, and may make it easier for some participants to get travel
approval to attend those events. This change would be reflected in the
dates posted on the IETF web site and sent out in email announcements. We
are not proposing any changes in terms of the scheduling of any
meeting-related events, the full availability of the meeting network
starting on Sunday, the opening of on-site registration, or the meeting fee.
I think this is a fine idea, essentially formalizing what has happened
informally. I suspect once in effect it will push the network to be
deployed earlier, but given current Saturday events, that was also probably
going to happen at some point.
Matching reality is always a fine idea. But there might be a problem
with that reality...
If you have feedback about this change, please send it to
ietf(_at_)ietf(_dot_)org, or exceptionally to iesg(_at_)ietf(_dot_)org, by
July 5, 2017.
The problem is that we now are expected to have work going non stop from
Saturday to Friday. 7 full days. Maybe I am just old, but that does not
look healthy.
-- Christian Huitema