IETF Logo Mail Archive

Re: [alto] WG adoption call for draft-schott-alto-new-transport-01

Qin Wu <bill.wu@huawei.com> Wed, 08 June 2022 09:36 UTC

Return-Path: <bill.wu@huawei.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 30047C159483 for <alto@ietfa.amsl.com>; Wed, 8 Jun 2022 02:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugJnqhsxHgeq for <alto@ietfa.amsl.com>; Wed, 8 Jun 2022 02:36:30 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DD1BC139549 for <alto@ietf.org>; Wed, 8 Jun 2022 02:36:30 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LJ285608gz67jfG for <alto@ietf.org>; Wed, 8 Jun 2022 17:32:53 +0800 (CST)
Received: from canpemm500005.china.huawei.com (7.192.104.229) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 8 Jun 2022 11:36:25 +0200
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm500005.china.huawei.com (7.192.104.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 8 Jun 2022 17:36:24 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2375.024; Wed, 8 Jun 2022 17:36:24 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: WG adoption call for draft-schott-alto-new-transport-01
Thread-Index: Adh7GurTN05xaSsPQveYSmSAIyD+EA==
Date: Wed, 08 Jun 2022 09:36:24 +0000
Message-ID: <3b7595e1311e42eabaf9dc83f8943a6d@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: multipart/alternative; boundary="_000_3b7595e1311e42eabaf9dc83f8943a6dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/8CqkFV7F1GOD2bjry4i9eEl6eCA>
Subject: Re: [alto] WG adoption call for draft-schott-alto-new-transport-01
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.39
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, 08 Jun 2022 09:36:34 -0000

Hi, authors:
I have read the latest version of ALTO transport, here is a few clarification questions and comments:
1. What is the relationship between HTTP/2 connection and Transport queue? one to one?
Will information resources share the same transport queue?
2. What is the relationship between transport queue and incremental update queue? one to one mapping?
3. Will receivers share the same incremental update queue? or each receiver can join different incremental update queue? For the former case, how does new receiver know
or discover the existing incremental update queue? Information resource will provide hints for the receiver or the client?

4. How incremental push update is different from incremental update?

5. In Figure 2  should 'sq/rs' be 'tq/rs'?

6. Individual update is not present in the figure 2? would it be nice to clarify the
relation between incremental update and individual update? Is incremental udpate shared by multiple receivers?

7. Should this draft need to update RFC7285 since it introduce new functionalities such as transport queue, incremental update queue, receiver set?
8. Is there any open issues section to track issue tickets?

-Qin (without chair hat)
发件人: alto [mailto:alto-bounces@ietf.org] 代表 Qin Wu
发送时间: 2022年5月31日 19:11
收件人: alto@ietf.org
主题: [alto] WG adoption call for draft-schott-alto-new-transport-01

Hi folks,

This begins a 2 week WG Adoption Call for the following draft:

https://datatracker.ietf.org/doc/draft-schott-alto-new-transport/

Please indicate your support or objections by June 15th, 2022.

Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft.

Thanks,

-Qin/Med

v2.23.0 | Report a Bug | By Email