Re: [alto] ALTO Interim in lieu of IETF 107

Vijay Gurbani <vijay.gurbani@gmail.com> Tue, 17 March 2020 15:15 UTC

Return-Path: <vijay.gurbani@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B20473A074E for <alto@ietfa.amsl.com>; Tue, 17 Mar 2020 08:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5qom_AiyVSJh for <alto@ietfa.amsl.com>; Tue, 17 Mar 2020 08:15:53 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB2A93A05A0 for <alto@ietf.org>; Tue, 17 Mar 2020 08:15:52 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id i24so23135500eds.1 for <alto@ietf.org>; Tue, 17 Mar 2020 08:15:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=33QLdNuBdv7pZLQd3Qu1Rg84LP+kK5szJDhBjeBpRdU=; b=mTFyiAQbw6o3l13Gf+l2WC22AIWhaGjGIEja7pwn+cAMQNj5IRmcSbs/O9OCyAdvB3 VcwC/YAXoV+3yK9m+Vo8DsGN59lHPzMfSsN8E4TrR3tPuSI3UlCXgmHQTeo6z2sAHdt2 vB6EUXqosAvGnwGCBTutOeEK3bWI95TUd2bnaJbgOru3wRw20oRjn5KKUc4o0RYUQOmp EOO55bo/9G6oYZC3zkw0m2el9oK3/xRfBGxMyYrlnW8ysujMk3g0eN121dSLUrTrMDsD CRphWQHUUWxOl54O07jHVOGYfjP82WGzy7Kg+LgHYjX0RiD/YaaupdMh1SRgPORuQCyB a6mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=33QLdNuBdv7pZLQd3Qu1Rg84LP+kK5szJDhBjeBpRdU=; b=T+6xs9HdXHY9COEM9xDBdR0akUAUIvyEoRuJJxnpjxTx5iMSCPYwqmR6Zj4fXcRauR hJca63tdHH+w6CzPyXdxjMjBohRCgMNqIuw+yVA2liqdvczNdyL88TjhPlmJgQdAK7qB u0VnczqyA+/9CmzbSmvh6TWipqnqqKpJcdQs8bT5SDGj81gtcbaOD8LNWl4VDICPQFvm xZo6eWQxY+2g4O8z5/+fR1J1DNEqM10+vIxyEe48/1aAxdukdPQLcMgvyJ3XGDHrnU8Q /ARrpITN3S5IogBguemPhK7P8YBjc1q7YejJNfZfjvjEFrWusSjhscuhpmQ5L95XbKjL UmAQ==
X-Gm-Message-State: ANhLgQ1UlfRZOX8c5cGac5326y4LEmVZZM8xCG1cCRBaZ0tmIeyN+pok L0xspAJKJnNeyoYhzkysdoQfcafhyxvnigBz9p8PrvvY
X-Google-Smtp-Source: ADFU+vs3jshJ+W10xdv7xBuB6iy/iI/4TwFtS2Mozmlh5OvKNvK4KRAMUr6u9+ASAwStEWW2kLEbXRImH9EqatYfjW0=
X-Received: by 2002:a17:906:cec9:: with SMTP id si9mr4477864ejb.374.1584458150703; Tue, 17 Mar 2020 08:15:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMTW_Jhm5CZCd_Ws+7b+jaXadMiUqfbrODeCDUbgZ=AVD7j5Q@mail.gmail.com> <PR1PR07MB51002EF56B8AA2CDC87E5F6895F90@PR1PR07MB5100.eurprd07.prod.outlook.com>
In-Reply-To: <PR1PR07MB51002EF56B8AA2CDC87E5F6895F90@PR1PR07MB5100.eurprd07.prod.outlook.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Tue, 17 Mar 2020 10:15:37 -0500
Message-ID: <CAMMTW_JfUjzfqxyro5hcQZ2oLhq916EMr0D=QBTci6RTZKfA+g@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003bf7c605a10e69f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ZJRSrTXoxUQ5VE2EUuinpa5UQKY>
Subject: Re: [alto] ALTO Interim in lieu of IETF 107
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 15:16:11 -0000

All: Thanks for expressing your preference on the list.

The tally I get from the responses is below, and from this, Option 1 seems
to be the best.  We will go ahead and schedule an interim for Apr 21, 2020
7:00 AM US Central.

Option 1 (7:00am US Central / 5:00am US Pacific).  That option had 7 votes.

The next highest (6 votes) are for 9:00am US Central / 7:00am US Pacific
Time and 11:00am US Central / 9:00am US Pacific.

Thanks,

- vijay


*From:* alto <alto-bounces@ietf.org> *On Behalf Of *Vijay Gurbani

> *Sent:* Friday, March 13, 2020 6:59 PM
> *To:* IETF ALTO <alto@ietf.org>
> *Subject:* [alto] ALTO Interim in lieu of IETF 107
>
>
>
> All: The IESG has been working on coming up with a virtual interim
> schedule for WGs that would have met in Vancouver.  As the original
> schedule avoided WG and RG conflicts to the maximum extent possible, the
> virtual interim schedule has been created so that working groups and
> research groups can be reasonably sure that most participants will not have
> a conflict with another IETF interim meeting on the same day.
>
>
>
> For ALTO, IESG has suggested Tue, Apr 21.  We will plan to hold a virtual
> interim on that day.  While we can decide another day besides the IESG
> suggested one, I would hesitate to do so for a variety of reasons, the most
> important of which is that we will have to ensure that our chosen day does
> not conflict with other WGs, BoFs, and RGs, that WG list members may be
> interested in.  Thus, it seems safe to stay with the IESG suggested date of
> Apr 21, as that date has honored all of the WG/RG conflicts with ALTO.
>
>
>
> What we need to do soon (48 hours or so) is to agree on a specific time
> for Apr 21 so Jan and I can set the wheels in motion to schedule the
> virtual interim on Apr 21.
>
>
>
> Here are the options, please reply with your preferred option on the
> list.  Jan and I will collect all of the responses we receive by Sunday
> night, and choose the one that is most frequent by Mon AM.  I know Europe
> has not yet changed their clocks, so I will leave the times below in US
> Central time zone (which is now on daylight savings time).  So please
> adjust accordingly for your locale.  All times are for Apr 21, 2020.
>
>
>
> 0. 5:00am - 7:00am US Central
>
> 1. 7:00am - 9:00am US Central
>
> 2. 9:00am - 11:00am US Central
>
> 3. 11:00am - 1:00pm US Central
>
> 4. 1:00pm - 3:00pm US Central
>
> 5. 3:00pm - 5:00pm US Central
>
> 6. 5:00pm - 7:00 pm US central *
>
> 7. 7:00pm - 9:00pm US central *
>
> 8. 9:00pm - 11:00pm US Central  *
>
>
>
> * I will not be able to make these timeslots as they overlap with the
> class I teach.
>
>
>
> Thank you,
>
>
>
> - vijay
>