Re: [alto] Topic B - maintenance of ALTO protocol // RE: June 20, 2023 meeting minutes and discussion working links
mente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telefónica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relación establecida con el destinatario o con la entidad a la que está vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a privacidad@telefonica.com. Puede consultar información adicional sobre el tratamiento de sus datos en nuestra Política de Privacidad <https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/>. We inform you that the data controller is the Telefónica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to privacidad@telefonica.com. You may consult additional information on the processing of your data in our Privacy Policy <https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>. Informamos que o responsável pelo tratamento dos seus dados é a entidade do Grupo Telefónica vinculada ao remetente, a fim de manter o contato professional e administrar a relação estabelecida com o destinatário ou com a entidade à qual esteja vinculado. Você pode entrar em contato com o responsável do tratamento de dados e exercer os seus direitos escrevendo a privacidad@telefonica.com. Você pode consultar informação adicional sobre o tratamento do seus dados na nossa Política de Privacidade <https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/>. ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto -- Danny Lachos | Senior Network Engineer BENOCS GmbH, Berlin +49 305 7700 0417 dlac...@benocs.com www.benocs.com Visit us on LinkedIn:https://www.linkedin.com/company/benocs/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
Re: [alto] 5/3/2022 Meeting Minutes
Hello Kai, Qin, all,
Thanks a lot for your comments/answers,
See below more details about our PoC & correlation:
Given a set of applications/media services (e.g., Disney+, DAZN, etc.)
that use infrastructures (e.g., CDNs) for content distribution, a couple
of questions to try to solve with this PoC:
* What are those infrastructures and how much traffic is coming from them?
* What are those applications and how much traffic is coming from them?
Therefore, the main idea with the DNS and Netflow correlation (including
BGP) is to annotate the Netflow traffic with the domain name(s) they
came from.
Regarding DNS information, we are collecting A/4A records and CName records:
* A/4A records to map an IPv4/IPv6 address to a FQDN (Fully Qualified
Domain Name).
* CNAME records to map a FQDN to another FQDN.
Main technical/research challenges for this DNS/Netflow mapping include:
* Live processing with multiple DNS and Netflow pipes running in parallel
* Domain name and IP address aggregation
* Desynchronized Netflow/DNS streams, including different formats
* DNS records need to be tracked in order to know if they are still
valid or not
* Warm-up periods of more than 12 hours
* Recursive CNAME mapping (and sometimes endless)
* Recursive lookup of FQDNs is not always completed because we only
receive the “cache misses” in the DNS stream data
* ...
We are implementing our PoC environment to validate and obtain different
proposals and results.
This is a work-in-progress and we are fully open to discuss in more
details this project, and working together with people interested in
this topic.
btw, regarding how the correlated data is consumed by applications, it
is supposed to use the same approach like FlowDirector
(https://datatracker.ietf.org/meeting/112/materials/slides-112-alto-implementation-deployment-experience-update-01),
i.e., through ALTO-based interfaces, BGP-based interfaces, or
customized interfaces.
On 18.05.22 13:05, kai...@scu.edu.cn wrote:
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"
*Sent Time:*2022-05-18 13:07:36 (Wednesday)
*To:* "Danny Lachos" , "Jordi Ros Giralt"
, "kai...@scu.edu.cn" ,
"alto@ietf.org"
*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:alto-boun...@ietf.org] *代表 *Danny Lachos
*发送时间:*2022年5月10日2:38
*收件人:*Jordi Ros Giralt ; kai...@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?
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.
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
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 https://www.ietf.org/mailman/listinfo/alto -- Best regards, Dr.-Ing. Danny Lachos BENOCS GMBH www.benocs.com [0] https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-openalto-2022.md ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
Re: [alto] Call for adoption: draft-zhang-alto-oam-yang
Hello ALTOers I support the adoption of this draft On 07.04.22 15:54, Randriamasy, Sabine (Nokia - FR/Paris-Saclay) wrote: +1, Best regards Sabine *From:*alto *On Behalf Of *Qiao Xiang *Sent:* Thursday, April 7, 2022 11:17 AM *To:* Luis M. Contreras *Cc:* roland.sch...@telekom.de; draft-zhang-alto-oam-y...@ietf.org; IETF ALTO ; alto-cha...@ietf.org *Subject:* Re: [alto] Call for adoption: draft-zhang-alto-oam-yang Hi all, I support the adoption of this draft. Best Qiao On Thu, Apr 7, 2022 at 5:11 PM Luis M. Contreras wrote: Hi all, I support the adoption of this draft. Best regards Luis El mié, 6 abr 2022 a las 18:30, escribió: Hi, I support the adoption of the draft as a good starting point for further work. Best Regards Roland *Von:*mohamed.boucad...@orange.com *Gesendet:* Montag, 4. April 2022 12:14 *An:* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org *Cc:* alto-cha...@ietf.org *Betreff:* RE: Call for adoption: draft-zhang-alto-oam-yang Hi all, This is a reminder that this call for adoption is still running. Cheers, Qin & Med *De :* mohamed.boucad...@orange.com *Envoyé :* mercredi 23 mars 2022 14:45 *À :* alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org *Cc :* alto-cha...@ietf.org *Objet :* Call for adoption: draft-zhang-alto-oam-yang Hi all, As discussed during the IETF#113 meeting, this message initiates the call for adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG milestone: == Dec 2022 ALTO OAM Document/YANG Model == Please reply to this message indicating your support or objection to adopt the document. The call will run till 08 April 2022. Thank you Qin & Med _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto -- ___ Luis M. Contreras contreras.i...@gmail.com luismiguel.contrerasmuri...@telefonica.com Global CTIO unit / Telefonica ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto -- Qiao Xiang Professor, Xiamen University ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto -- Best regards, Dr.-Ing. Danny Lachos BENOCS GMBH www.benocs.com ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
Re: [alto] Meeting Info for Oct 5, 2021
Hello ALTOers, Finally, I am in Berlin Now here at Benocs, I will continue to participate in the WG discussions & weekly meetings Talk to you tomorrow On 04.10.21 16:26, kai...@scu.edu.cn wrote: Dear all, This is a friendly reminder that we will have our ALTO weekly meeting*at 9:00 am US EST (3:00 pm CET and 9:00 pm Beijing Time) on Tuesday, October 5, 2021.* * * *Reminder:* We will have 3 weekly meetings before the draft submission deadline (Oct 25) and 5-6 weekly meetings before IETF 112 (Nov 6-12). *Agenda:* - Planning of weekly meetings before IETF 112 - Trial editorial session for path vector *Bridge:* https://yale.zoom.us/my/yryang Best, Kai ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
