Re: [alto] 5/3/2022 Meeting Minutes

Qin Wu <bill.wu@huawei.com> Wed, 18 May 2022 05:07 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 7904EC15EB28 for <alto@ietfa.amsl.com>; Tue, 17 May 2022 22:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 40HASLiF_292 for <alto@ietfa.amsl.com>; Tue, 17 May 2022 22:07:42 -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 2EE99C15E6DC for <alto@ietf.org>; Tue, 17 May 2022 22:07:42 -0700 (PDT)
Received: from fraeml706-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4L31BF0v49z6H7Kb for <alto@ietf.org>; Wed, 18 May 2022 13:04:37 +0800 (CST)
Received: from canpemm100005.china.huawei.com (7.192.105.21) by fraeml706-chm.china.huawei.com (10.206.15.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Wed, 18 May 2022 07:07:38 +0200
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm100005.china.huawei.com (7.192.105.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 18 May 2022 13:07:36 +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, 18 May 2022 13:07:36 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Danny Lachos <dlachos@benocs.com>, Jordi Ros Giralt <jros@qti.qualcomm.com>, "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] 5/3/2022 Meeting Minutes
Thread-Index: AdhqdS1EF0Ff9WHxQ3i2xvsH1z78UQ==
Date: Wed, 18 May 2022 05:07:36 +0000
Message-ID: <87529f12355a46eea974e31fa8441bc4@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_87529f12355a46eea974e31fa8441bc4huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/K2idmKVQEzMCOFdD3o2TKQrA4T0>
Subject: Re: [alto] 5/3/2022 Meeting Minutes
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.34
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, 18 May 2022 05:07:46 -0000

Hi, Danny:
Interesting PoC, any more details about your PoC introduction. I am wondering what technique you are using for data correlation, how these correlated information are consumed by the application? I assume these steps do not require extension to Network Map or Cost Map.

-Qin
发件人: alto [mailto:alto-bounces@ietf.org] 代表 Danny Lachos
发送时间: 2022年5月10日 2:38
收件人: Jordi Ros Giralt <jros@qti.qualcomm.com>; kaigao@scu.edu.cn; alto@ietf.org
主题: Re: [alto] ?==?utf-8?q? ?==?utf-8?q? 5/3/2022 Meeting Minutes


Hello Jordi, Kai, all



Thanks a lot for sharing,

I have a couple of quick comments/questions:



Regarding the OpenALTO meetings [0], I saw that Kai is currently working on integrate ALTO in DNS. If I do not wrong, it is supposed to use ALTO as a northbound interface to provide information about the domain name resolution to DNS clients, right?, if not, there is a chance to explain a little bit more about what is being done on ALTO/DNS?



Here at Benocs, we are also working with DNS information that is correlated with network traffic flows to obtain a multi-dimensional traffic information. In fact, we are implementing a PoC environment for the development of practical use cases. This PoC is able to read DNS traffic, network traffic flows, BGP information and then making correlations (real-time or batch processing).



In some point, could be interesting to find some kind of interception about what you/we are currently dealing in terms of technical and/or scientific challenges.


On 04.05.22 14:12, Jordi Ros Giralt wrote:
Thank you very much Jensen for taking meeting minutes yesterday.

For those who could not attend our call yesterday (and for our bookkeeping), here you will find them: https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-alto-2022.md

Going forward, you will also find minutes for the OpenALTO meetings being held weekly too (Mon, Wed and Thu) here: https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-openalto-2022.md. As you know, everyone is invited to attend these other meetings that focus on the implementation of the Standard, see the meeting coordinates in this previous link for days and zoom link.

This action resolves ticket https://github.com/ietf-wg-alto/wg-materials/issues/23

Thanks,
Jordi on behalf of ALTO WG


_______________________________________________

alto mailing list

alto@ietf.org<mailto:alto@ietf.org>

https://www.ietf.org/mailman/listinfo/alto

--

Best regards,



Dr.-Ing. Danny Lachos

BENOCS GMBH

www.benocs.com<http://www.benocs.com>



[0] https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-openalto-2022.md