Hi, Luis and all

Thanks for this effort. Jensen and Kai, I think your proposals make sense to 
me, maybe could be reflected on the shared spreadsheet?

I’ve Just added one more potential data source to the spreadsheet: LMAP 
(Large-Scale Measurement of Broadband Performance, RFC7594) network measurement 
results. That said, ALTO server can simply work as the LMAP collector and 
accept the report from the measurement agent which performs the measurement 
tasks as instructed by the LMAP controller.

PS. There is a draft 
(https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt) related to that, 
the authors plan to revive it very soon.

Best Regards,
Qiufang

From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jensen Zhang
Sent: Wednesday, April 26, 2023 8:29 AM
To: kai...@scu.edu.cn
Cc: IETF ALTO <alto@ietf.org>; Qin Wu <bill...@huawei.com>
Subject: Re: [alto] Proposed Agenda for Interims #2-5

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources 
listed in this collection, I am wondering if the following kinds of data 
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides route 
and provider related information attached to IP prefixes. It may be helpful for 
network/property map generation, or locating the network domain in multidomain 
settings.

2. Data plane information, e.g., routing and forwarding tables read from BGP 
looking glass server or other OAM tools. Although I see the "IETF TE Network 
topology" source can already provide routing information, it may focus on the 
control plane, e.g., routing policy, not the data plane.

3. Telemetry information, e.g., traceroute. It can get both routing and 
performance information. It may have some overlap with the performance metrics.

Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM <kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>> 
wrote:

Hi Luis and all,



Thanks for the effort. The information is really useful and comprehensive. I 
think it lays a very good foundation to discuss and proceed with potential ALTO 
extensions.



With the rationale that, in my opinion, sets the expectations for each data 
source, I am wondering whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.



I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.



Best,

Kai



-----Original Messages----
From:"LUIS MIGUEL CONTRERAS MURILLO" 
<luismiguel.contrerasmuri...@telefonica.com<mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" 
<mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>>, "IETF 
ALTO" <alto@ietf.org<mailto:alto@ietf.org>>
Cc: "Qin Wu" <bill...@huawei.com<mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5
Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

•         Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0

Please, feel free to access and check, all of you should be able to add/drop 
comments as well (let me know in case you need some permission for that). In 
the table we cover potential data sources, the rationale for considering them, 
existing reference work, as well as impacts on current ALTO. We hope this could 
be a basis for discussion for interim #3, but also to trigger discussions on 
the mailing list so we as WG can go to the interim with a more clear notion of 
the data sources and their implications.

Thanks

Best regards

Luis


De: alto <alto-boun...@ietf.org<mailto:alto-boun...@ietf.org>> En nombre de 
mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>
Enviado el: martes, 4 de abril de 2023 8:58
Para: IETF ALTO <alto@ietf.org<mailto:alto@ietf.org>>
CC: Qin Wu <bill...@huawei.com<mailto:bill...@huawei.com>>
Asunto: [alto] Proposed Agenda for Interims #2-5

Hi all,

Please find below the proposed agenda for the forthcoming interims

* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts
·         Reuse existing network resources to identify ALTO resources (e.g., 
BGP communities)
·         Proposals to fix the integration complexity and integration with data 
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts
·         Security/privacy isolation

Comments and suggestions are welcome.

Cheers,
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.

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente 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
_______________________________________________
alto mailing list
alto@ietf.org<mailto:alto@ietf.org>
https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Reply via email to