Re: [alto] ALTO Interim in lieu of IETF 107
kaigao@scu.edu.cn Sat, 14 March 2020 02:11 UTC
Return-Path: <kaigao@scu.edu.cn>
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 3D82B3A0747 for <alto@ietfa.amsl.com>; Fri, 13 Mar 2020 19:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tRes-rX5Qi7y for <alto@ietfa.amsl.com>; Fri, 13 Mar 2020 19:11:23 -0700 (PDT)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 53D753A0746 for <alto@ietf.org>; Fri, 13 Mar 2020 19:11:22 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Sat, 14 Mar 2020 10:09:44 +0800 (GMT+08:00)
X-Originating-IP: [110.191.195.154]
Date: Sat, 14 Mar 2020 10:09:44 +0800
X-CM-HeaderCharset: UTF-8
From: kaigao@scu.edu.cn
To: Vijay Gurbani <vijay.gurbani@gmail.com>
Cc: IETF ALTO <alto@ietf.org>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.10a build 20190924(a4b591f1) Copyright (c) 2002-2020 www.mailtech.cn mail
In-Reply-To: <CAMMTW_Jhm5CZCd_Ws+7b+jaXadMiUqfbrODeCDUbgZ=AVD7j5Q@mail.gmail.com>
References: <CAMMTW_Jhm5CZCd_Ws+7b+jaXadMiUqfbrODeCDUbgZ=AVD7j5Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=_Part_11612_905464476.1584151784746"
MIME-Version: 1.0
Message-ID: <26d9f594.cf5.170d6cded2b.Coremail.kaigao@scu.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgBnNBLoPGxekNIMAA--.928W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQINB138kjhB+QAusU
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/oQnwFqyWLOmh0jidYce8jk-uYOw>
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: Sat, 14 Mar 2020 02:11:26 -0000
Hi Vijay, I prefer 0, 1, 7, and 8. 2 is also acceptable but less preferred. Best, Kai -----Original Messages----- From:"Vijay Gurbani" <vijay.gurbani@gmail.com> Sent Time:2020-03-14 01:58:35 (Saturday) To: "IETF ALTO" <alto@ietf.org> Cc: 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
- [alto] ALTO Interim in lieu of IETF 107 Vijay Gurbani
- Re: [alto] ALTO Interim in lieu of IETF 107 Y. Richard Yang
- Re: [alto] ALTO Interim in lieu of IETF 107 Martin Duke
- Re: [alto] ALTO Interim in lieu of IETF 107 Jensen Zhang
- Re: [alto] ALTO Interim in lieu of IETF 107 kaigao
- Re: [alto] ALTO Interim in lieu of IETF 107 Qiao Xiang
- Re: [alto] ALTO Interim in lieu of IETF 107(Inter… chunshxiong(熊春山)
- Re: [alto] ALTO Interim in lieu of IETF 107 Danny Alex Lachos Perez
- Re: [alto] ALTO Interim in lieu of IETF 107 Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
- Re: [alto] ALTO Interim in lieu of IETF 107 Vijay Gurbani