Hi Kai, You are touching relevant points.
First, regarding the idea of retrieving the topology from the controller. In the simpler case, since the controller will already have a topology processed from the information retrieved from the network, it can make sense to get it from the controller. So, ALTO can benefit from that, thus avoiding to process twice the same information. In the more complex situation, to could be the case that the SDN controller collects and aggregates information from different domains (even under the same administrative responsibility) then simplifying again the aggregation and processing of the overall topological information. Or even it could be the case where the SDN controllers builds a general view of a network leveraging partial views even collected through different protocols (e.g., BGP-LS, LLDP, etc). In summary, the benefit could come from simplifying the ALTO server processes, just retrieving what has been already aggregated and processed. However it is important what you say. Not all the information could be on the topology provided by the SDN controller. For instance, the subnets (IP prefixes) representing e.g. residential broadband users which are attached to border routers are not present in IETF Network Topology. These subnets should be obtained by means of BGP sessions with the route reflectors in the network. So, even though we can simplify the process of the ALTO server by retrieving the internals of the network from the controller (which is useful for building the cost map) we yet need to maintain BGP sessions with the RR for understanding the IP pools in each PIC (i.e. to build the network map). Finally going to your question about if it is useful to discuss gaps and constraints, my answer id definitely YES. Thanks so much for your comment, Luis De: [email protected] <[email protected]> Enviado el: martes, 25 de abril de 2023 16:55 Para: LUIS MIGUEL CONTRERAS MURILLO <[email protected]> CC: [email protected]; IETF ALTO <[email protected]>; Qin Wu <[email protected]> Asunto: Re: Re: [alto] Proposed Agenda for Interims #2-5 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" <[email protected]<mailto:[email protected]>> Sent Time:2023-04-18 06:23:51 (Tuesday) To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "IETF ALTO" <[email protected]<mailto:[email protected]>> Cc: "Qin Wu" <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>> En nombre de [email protected]<mailto:[email protected]> Enviado el: martes, 4 de abril de 2023 8:58 Para: IETF ALTO <[email protected]<mailto:[email protected]>> CC: Qin Wu <[email protected]<mailto:[email protected]>> 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 ________________________________ 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 [email protected] https://www.ietf.org/mailman/listinfo/alto
