[alto] Meeting minutes for Oct 13, 2020

kaigao@scu.edu.cn Wed, 14 October 2020 02:57 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 4301C3A0D02 for <alto@ietfa.amsl.com>; Tue, 13 Oct 2020 19:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 sHbL_5fhxHMJ for <alto@ietfa.amsl.com>; Tue, 13 Oct 2020 19:57:18 -0700 (PDT)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 1EA193A0D9A for <alto@ietf.org>; Tue, 13 Oct 2020 19:57:17 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Wed, 14 Oct 2020 10:56:53 +0800 (GMT+08:00)
X-Originating-IP: [125.70.168.58]
Date: Wed, 14 Oct 2020 10:56:53 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
From: kaigao@scu.edu.cn
To: 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
Content-Type: multipart/alternative; boundary="----=_Part_154921_542295888.1602644213126"
MIME-Version: 1.0
Message-ID: <3561b503.aa44.1752509fd87.Coremail.kaigao@scu.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgCXW8X1aIZfiMCdAA--.16309W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQIJB138kkTXlQAAs4
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/B52x7UdFRIn0Ppkn6NXm6WrHBNo>
Subject: [alto] Meeting minutes for Oct 13, 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: Wed, 14 Oct 2020 02:57:21 -0000

Dear all,




In this week's meeting, we first went over the progress of 5 WG documents as follows:




- cost calendar: all co-authors have approved the publication

- unified property: 2 reviews received for WGLC and is under revision

- performance metrics: 3 reviews received for WGLC

- path vector: 1 review received and Luis proposes to give another review by Oct 26

- CDNI: held by WG




Chunshan gave a presentation on the proposed changes to the rechartering items [1], including cellular information, IB/OB signaling and transport protocol extensions. In particular, he shared information from 3GPP on IB/OB signaling, indicating that IB/OB signaling should be combined for cellular information exposure. It is suggested that Chunshan submits the proposed changes to the rechartering document and brings the issues to the ALTO mailing list to initiate discussions.




Sabine and Gang discussed the issues of exposing cellular information. Key questions include what information should be exposed, and how to handle the freshness of cellular information. The Tecent and CMCC team has already categorized some cellular information to 3 different levels and several categories. It is suggested to start with radio channel information.




Sabine proposed to gain a better understanding of the issue by answering the following questions:

- What metric is important to the quality of applications?

- To what extent is it possible to expose?

- Which time granularity is the ALTO client/server able to support?

- What decisions can a client make?




Gang mentioned that the time granularity depends on the transmission delay and the transmission protocol (whether it's IB or OB, signaling overhead). He also proposed to bring the issues to the mailing list to engage a broader audience.




The link to the meeting minutes is attached below [2].




Sabine, Gang, Chunshan: Please correct me if I missed or misinterpreted some points.




Best,

Kai




[1] https://docs.google.com/document/d/1qP9jf-CMXvNiEE3YAnApTczAE4QkBW23Q1Eg99uOaEQ/edit?usp=sharing

[2] https://docs.google.com/document/d/1H5HvSbOT54IPCniWi8Xrxive8q1UpV1ZyYda46P0-b0/edit?usp=sharing