----- Original Message ----- From: "Eric Burger" <eburger@xxxxxxxxxxxxxxxxxx> To: <ietf@xxxxxxxx> Sent: Saturday, June 24, 2017 10:03 PM On the one hand, I won’t be working on Saturday. On the other hand, as someone on a limited budget (read university) paying for someone else (read student) to go to the IETF, that Saturday night stay has a big impact on airfare. So long as we don’t have Saturday creep in as a ‘regular’ IETF working day, I’m for the change. <tp> Eric I am not sure which way round your comment on budgets is intended but for me, staying over for a Saturday night makes the transatlantic airfare much cheaper so I always travel on Saturday even if there is nothing to do on Sunday (except deal with jetlag). Friday travel is busy and congested, especially next month in the holiday season, so I would never travel on Friday. Tom Petch > On Jun 23, 2017, at 1:39 AM, Tobias Gondrom <tobias.gondrom@xxxxxxxxxxx> wrote: > > I also agree. This is good idea. > (with my individual hat on... ;-) ) > Best regards, Tobias > > On June 21, 2017 8:46:57 PM GMT+08:00, Bob Hinden <bob.hinden@xxxxxxxxx> wrote: > Alissa, > > On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@xxxxxxxxxx> 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. > > Thanks, > Bob > > If you have feedback about this change, please send it to ietf@xxxxxxxx, or exceptionally to iesg@xxxxxxxx, by July 5, 2017.