Hi, Kai:

发件人: [email protected] [mailto:[email protected]]
发送时间: 2022年5月18日 19:05
收件人: Qin Wu <[email protected]>
抄送: Danny Lachos <[email protected]>; Jordi Ros Giralt 
<[email protected]>; [email protected]
主题: Re: RE: [alto] 5/3/2022 Meeting Minutes


Hi Qin, Danny and all,

Sorry I did not get the email from Danny and just saw this discussion. Please 
see my comments inline.

Best,

Kai

-----Original Messages-----
From:"Qin Wu" <[email protected]<mailto:[email protected]>>
Sent Time:2022-05-18 13:07:36 (Wednesday)
To: "Danny Lachos" <[email protected]<mailto:[email protected]>>, "Jordi Ros 
Giralt" <[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Cc:
Subject: RE: [alto] 5/3/2022 Meeting Minutes
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:[email protected]] 代表 Danny Lachos
发送时间: 2022年5月10日 2:38
收件人: Jordi Ros Giralt <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>
主题: 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?



There are two directions. One is to provide ALTO information through DNS and 
the other is to use ALTO to feed information to a DNS server. The first 
direction is definitely an interesting and potentially useful direction but we 
haven't got the man power to work on that. Right now we are using ALTO 
information to change the order of A records returned by a DNS server. The 
current proof-of-concept is to update the sort list option [1] based on ALTO 
cost map. Another approach in this direction is to change the preferences of A 
records of the same host name on the client side but we also haven't really 
started yet.

[Qin Wu] Based on the approach and use case you describe, I feel you are 
discussing the second direction, i.e., use ALTO to feed information to a DNS 
server and allow DNS server change the order of DNS A records, return the 
results to the DNS client, what am I missing?

To put the integration into a context, you may refer to the footprint paper 
(NSDI'16). The idea is to control user traffic through DNS remapping. However, 
I'm looking more in the case where the application is not in the same 
administrative domain as the underlying network provider, and the ALTO maps are 
constructed based on my NAI'21 paper instead of from the ISP.



[1] http://www.ipamworldwide.com/ipam/sortlist.html



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).



This sounds very interesting. Like Qin's comment, I would be very interested to 
hear more about the use cases and how you make the correlations.

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.



Certainly.
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

[email protected]<mailto:[email protected]>

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


_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to