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

Qin Wu <bill.wu@huawei.com> Mon, 16 November 2020 14:14 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 7A1F73A1069 for <alto@ietfa.amsl.com>; Mon, 16 Nov 2020 06:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, 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 F1UccsI7Wm7v for <alto@ietfa.amsl.com>; Mon, 16 Nov 2020 06:14:37 -0800 (PST)
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 7C47A3A1060 for <alto@ietf.org>; Mon, 16 Nov 2020 06:14:37 -0800 (PST)
Received: from fraeml704-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CZWHz4K9Dz67D8K for <alto@ietf.org>; Mon, 16 Nov 2020 22:13:03 +0800 (CST)
Received: from fraeml704-chm.china.huawei.com (10.206.15.53) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 16 Nov 2020 15:14:35 +0100
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Mon, 16 Nov 2020 15:14:34 +0100
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.21]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0487.000; Mon, 16 Nov 2020 22:14:31 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, "alto@ietf.org" <alto@ietf.org>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
Thread-Topic: [alto] Meeting info for Nov 17, 2020
Thread-Index: Ada8IN9HSQbGw/jwQnSiq77nheibcg==
Date: Mon, 16 Nov 2020 14:14:30 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADB7F1C1@dggeml511-mbs.china.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.101.103]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADB7F1C1dggeml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/3bHdrZZSYsSOYwdhjqytTwA82PM>
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: Mon, 16 Nov 2020 14:14:39 -0000

Regarding the topic 3, I think investigating the configuration, management, and
operation of ALTO systems is interesting, I am wondering how network topology model in RFC8345
and TE topology model in RFC8795 can be translated into network map, property map, cost map?

Or use pub/sub mechanism to subscribe specific data source and publish the event notification to the ALTO server automatically,
Or translated TEDB and LSPDB directly into Network map or Cost map?

Luis’s draft provide a good use case for this, i.e., automatically derived ALTO information from southbound interface.
https://tools.ietf.org/html/draft-contreras-alto-service-edge-02
which also specify additional ALTO protocol extension for computing capability exposure and selection.

-Qin
发件人: alto [mailto:alto-bounces@ietf.org] 代表 kaigao@scu.edu.cn
发送时间: 2020年11月16日 21:18
收件人: alto@ietf.org; alto-weekly-meeting@googlegroups.com
主题: [alto] Meeting info for Nov 17, 2020


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