IETF Logo Mail Archive

Re: Saturday as start day

Eric Burger <eburger@standardstrack.com> Sat, 24 June 2017 21:04 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E30E71293F2 for <ietf@ietfa.amsl.com>; Sat, 24 Jun 2017 14:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.781
X-Spam-Level:
X-Spam-Status: No, score=-1.781 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, T_DKIM_INVALID=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXlYQolJYob5 for <ietf@ietfa.amsl.com>; Sat, 24 Jun 2017 14:04:08 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [23.235.223.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A159128D44 for <ietf@ietf.org>; Sat, 24 Jun 2017 14:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Type:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=n/fmTBZ/EkvKmdPLcKRpgL0HEDdHSlHfFFG0yNE7Clc=; b=RfI+OREOEofDUypy10fpEeWZr N6eKbL6QLJpQqSQkEO/Iq5huHIDzgyrHGRQjwgvchA+izZw06RkOzh5+im50PEBn0DJITaWJ4yoZ5 d79Qr3jLo5iQ1q0TfZRRYaYQBwYKR/DC2X4o5SSifmsthkqcZp5Quh7CBVwA7NM3ubRbY=;
Received: from ip68-100-197-40.dc.dc.cox.net ([68.100.197.40]:56809 helo=[192.168.10.25]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from <eburger@standardstrack.com>) id 1dOsDd-0003Sc-LE for ietf@ietf.org; Sat, 24 Jun 2017 14:04:08 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_378B9B58-ABC7-496C-8318-1042FEE67EBA"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Saturday as start day
Date: Sat, 24 Jun 2017 17:03:48 -0400
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org>
To: ietf@ietf.org
In-Reply-To: <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org>
Message-Id: <E01EDC06-5AEE-4957-AA46-DA87AF9D46C1@standardstrack.com>
X-Mailer: Apple Mail (2.3273)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sZEhO80SB3LuJipoH-E0ZOjrQzc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jun 2017 21:04:10 -0000

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.

> On Jun 23, 2017, at 1:39 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> 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@gmail.com> wrote:
> Alissa,
> 
>  On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.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.
> 
> Thanks,
> Bob
> 
> 
> 
>  If you have feedback about this change, please send it to ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.
> 
> 
> 
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

v2.23.0 | Report a Bug | By Email