Re: [alto] Meeting info for Nov 17, 2020

kaigao@scu.edu.cn Tue, 17 November 2020 08:15 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 DC53F3A0639 for <alto@ietfa.amsl.com>; Tue, 17 Nov 2020 00:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 LmFrgzKgCHZZ for <alto@ietfa.amsl.com>; Tue, 17 Nov 2020 00:15:28 -0800 (PST)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 8B10C3A0603 for <alto@ietf.org>; Tue, 17 Nov 2020 00:15:26 -0800 (PST)
Received: by ajax-webmail-app1 (Coremail) ; Tue, 17 Nov 2020 16:15:14 +0800 (GMT+08:00)
X-Originating-IP: [171.223.194.26]
Date: Tue, 17 Nov 2020 16:15:14 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
From: kaigao@scu.edu.cn
To: "Y. Richard Yang" <yry@cs.yale.edu>
Cc: "IETF ALTO" <alto@ietf.org>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.13 build 20200820(b2b8cba1) Copyright (c) 2002-2020 www.mailtech.cn mail
In-Reply-To: <CANUuoLqMrd2gqD3SLO4wUJroYdBHgrbt7N6poLR2LygO7r_RnA@mail.gmail.com>
References: <cea90ae.1742c.175d1340f16.Coremail.kaigao@scu.edu.cn> <CANUuoLqMrd2gqD3SLO4wUJroYdBHgrbt7N6poLR2LygO7r_RnA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=_Part_343026_1566180767.1605600914846"
MIME-Version: 1.0
Message-ID: <40634604.178e4.175d545ad9e.Coremail.kaigao@scu.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgAXn0aShrNfbhcnAQ--.33716W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQIDB138kka5SAAAsD
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/R7_1F9V1Ppq6-5bp6C_yFS55EAI>
Subject: Re: [alto] Meeting info for Nov 17, 2020
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 Nov 2020 08:15:31 -0000

Dear Richard and all, 

Please find below the paragraph on item 2. The texts are also uploaded to the google doc.

Best,
Kai

--------------------------------------------------

Protocol extension of the ALTO protocol over newer versions of HTTP. Existing extensions such as path vector and incremental updates need additional mechanisms to work around limitations of HTTP/1.x, leading to additional development complexities and data transmission. This extension is to define the data delivery of dependent ALTO objects, which unifies the base protocol, the path vector (multipart) extension, and the incremental update extension when they are transported using HTTP/2 and HTTP/3. 

2020-11-17 11:01:52"'Richard Yang'" <yry@cs.yale.edu>wrote;wrote:

Thanks a lot, Kai!


I saw from the WG mailing list the proposed paragraphs on items 1 and 5. It will be nice if the leads of 2-4 can post the initial proposals before the meeting soon...


Richard


On Mon, Nov 16, 2020 at 8:17 AM <kaigao@scu.edu.cn> wrote:


Dear all,

We will have the last meeting before the IETF 109 ALTO session at 9:00 am US EST (3 pm CET, 10 pm Beijing Time).

The purpose is to go over and finalize the recharter items. Given that some topics were not presented in the last meeting, I suggest we follow the order below:

1. General extensions

2. New transport

3. Operation automation

4. First hop

5. Multi-domain




Bridge: https://yale.zoom.us/my/yryang




Best,

Kai

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto





--

-- 
 =====================================
| Y. Richard Yang <yry@cs.yale.edu>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================