[nmop-kg-dt] Re: Meeting Summary for KG pre-IETF123 Design Team meeting

[IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <[e-mail]>]

Hi KG team,

Sorry, it took me a while to find and subscribe to the mailing list ...

From the minutes I see you proposed to have a follow-up meeting before the IETF. Did I miss the invite or the meeting has not been scheduled yet?.

Many thanks!

PD: For those of you who also happen to be die-hard NBA fans, this great team has the same name of another great player :D

Best regards,
Nacho.


From: Reshad Rahman <[e-mail]>
Date: Thursday, 3 July 2025 at 16:56
To: Benoit Claise <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, IGNACIO DOMINGUEZ MARTINEZ-CASANUEVA <[e-mail]>, [e-mail] <[e-mail]>, Brad Peters <[e-mail]>, Thomas Graf <[e-mail]>, BOUCADAIR Mohamed INNOV/NET <[e-mail]>
Subject: FW: Meeting Summary for KG pre-IETF123 Design Team meeting

AVISO/WARNING: Este correo electrónico se originó desde fuera de la organización. No haga clic en enlaces ni abra archivos adjuntos a menos que reconozca al remitente y sepa que el contenido es seguro / This email has been originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.



From: Meeting Summary with AI Companion <[e-mail]>
Date: Thursday, July 3, 2025 at 10:42 AM
To: Reshad Rahman <[e-mail]>
Subject: Meeting Summary for KG pre-IETF123 Design Team meeting
[Image removed by sender.]<https://urldefense.com/v3/__https:/zoom.com__;!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRFr7mbDSQ$>
Meeting summary for KG pre-IETF123 Design Team meeting (07/03/2025)
Quick recap

The team discussed a research roadmap focused on defining anomaly models in dynamic technical environments, including the development of a knowledge graph-based data platform and an open-source ontology. Lionel presented various algorithmic techniques for anomaly detection and root cause analysis, while explaining their framework for analyzing network data and demonstrating a semantic web-based approach for representing network knowledge. The group explored potential next steps for integrating their ontology model with existing ITF models and discussed practical use cases for their knowledge graph work, with plans to review shared links and schedule a follow-up meeting.

Next steps

  *   All team members: Review Noria ontology documentation and links shared by Lionel
  *   Design team: Prepare a brief update on knowledge graph investigation progress for the IETF Madrid Tuesday side meeting
  *   Michael/Dan: Prepare a simple BGP flapping use case to test against Noria ontology
  *   Michael/Benoit: Investigate integration of CMAP Yang models with Noria ontology's structural component
  *   Reshad: Schedule a follow-up meeting two weeks before IETF
  *   Lionel: Share demo link in the chat/via email for team review
  *   All team members: Subscribe to the design team mailing list
  *   All team members: Subscribe to the Antmob mailing list to track Antagonist tool updates

Summary
Dynamic Anomaly Model Research Roadmap

Lionel presented a research roadmap focused on defining anomaly models in dynamic technical environments, which includes producing a knowledge graph-based data platform and an ontology in RDF syntax. He discussed the development of an open-source ontology with four facets to represent network topology, functional concepts, operational dynamics, and procedural knowledge. Lionel also described a knowledge graph construction platform that combines various data sources, including descriptive datasets and event-based information, to enable querying and insights for practitioners.

Ecosystem Patching and Mapping Process

Lionel explained the process of patching and creating links in the ecosystem, which involves manual processes and automatic associations based on topology and rules. Reshad sought clarification on the patching process, and Lionel elaborated on the use of ontologies and common keys. Michael inquired about the logs being monitored and the mapping process, to which Lionel explained the use of an aggregator platform and rules for mapping patterns to ontologies.

Algorithmic Anomaly Detection Techniques

Lionel presented three families of algorithmic techniques for anomaly detection and root cause analysis: model-based design, process mining, and statistical learning. He explained how these techniques can be used synergistically to leverage their strengths and achieve broader coverage of detection cases. Lionel also discussed the importance of explainability and the need to combine logical and probabilistic approaches. The presentation included examples of how these techniques can be applied to real-world network incidents and how they can be used to enrich knowledge graphs with insights and probable causes.

Network Data Analysis Framework

Lionel presented a framework for analyzing network data, focusing on router information and network topology. He explained that they are using an Angular database to store and analyze data from millions of routers in France's national backbone network. The system can handle large-scale data ingestion and has been tested with various data sources, including syslog, flow records, and Yang push data. The framework includes adapters for different types of log telemetry and uses a generic "event record" concept to handle various types of data inputs.

Semantic Web Network Knowledge System

Lionel presented a semantic web-based approach for representing network knowledge, focusing on a graph-based system that logs everything and allows for post-processing. He explained that the system uses existing ontologies for various aspects like structural, functional, dynamic, and procedural knowledge, and demonstrated how it can handle versioning and provenance tracking through timestamped data. Reshad inquired about the system's ability to provide historical network state information, to which Lionel confirmed that entities in the graph can be tagged with provenance data and governance information, allowing for time-traveling queries of network states.

Project Integration and Mailing List

The team discussed next steps for their project, with Reshad encouraging everyone to subscribe to the newly created mailing list, which he will manage as chair. Michael suggested exploring the possibility of integrating Lionel's ontology model with existing ITF models, potentially using RDF and Yang conversions to enhance their structural and topological representations. The group agreed that this approach could provide a more comprehensive understanding of network resources and events, building on previous work with Raphael to automate model generation.

Network Configuration and Connectivity Challenges

The group discussed network configuration and connectivity issues, with Brad explaining their focus on both active devices and passive network components across a large geographical area of 9 million square kilometers. They addressed challenges with cable outages, power provider issues, and the complexity of determining root causes across multiple distribution areas. Lionel mentioned using a similar model for outside plant management, while b00598843 raised a question about the universality of Lionel's approach, to which Lionel responded that it was a unique ontology but could potentially be adapted for other use cases.

Project-Itf Integration Strategy Discussion

The group discussed the relationship between their project and the ITF (Internet Technical Forum), with Lionel explaining that their work should complement rather than compete with the ITF. Michael suggested replacing the structural part of their model with auto-generated models from the ITF, particularly using the SEPA model as a bridge between BSS/OSS systems and the ITF world. Lionel confirmed that their ontology (currently at version 0.4) allows for controlled evolution with backward compatibility, and he explained that different versions can be used by instantiating specific versions when colleagues work with the ontology.

Cmap RDF Experiment Discussion

The team discussed switching to Cmap's RDF version as a potential first experiment, with Lionel highlighting its structural output and existing use cases. Michael expressed concerns about whether this would be a theoretical exercise or practical, requiring lab resources and mappings. The group considered borrowing resources from a digital maps hackathon, with Lionel noting the availability of fake network topology data and transformation rules. Benoit emphasized the importance of evaluating if the ontology meets their needs before considering standardization, while Dan suggested starting with a simple network topology and potentially linking to ITF models.

Ontology Generation and Model Integration

The team discussed a project involving the generation of ontologies from Yang schema data, with Michael presenting their approach and its potential integration with ITF models. They explored the possibility of using Antagonist for network anomaly detection and discussed the need to address configuration issues in Cmap. Dan volunteered to work on the project during the upcoming hackathon, though there were concerns about timing and availability. The team agreed to continue developing the concept, with a focus on creating dynamic relationships between Cmap models and other ITF models.

Knowledge Graph Use Case Discussion

The team discussed focusing on practical use cases for their knowledge graph work rather than document merging, with Dan suggesting BGP flapping and PE loss as simple test cases that could be demonstrated in a lab environment. Reshad clarified that the design team's goal is to identify problems to solve rather than create a final solution, noting that an RFC may not be the appropriate output for this work. The team agreed to review the links Lionel shared about Noriao and to schedule a follow-up meeting, with Michael offering to start at 9 or 10 PST, while Reshad will serve as chair and coordinate the next steps.
AI-generated content may be inaccurate or misleading. Always check for accuracy.
Please rate the accuracy of this summary.
[Image removed by sender. feedback good]<https://equinix.zoom.us/meeting/summary/feedback?meetingId=xtQOHviqSnCDkHc0EPyLLw%3D%3D&email=cnJhaG1hbkBlcXVpbml4LmNvbQ==&feedback=good>[Image removed by sender. feedback bad]<https://equinix.zoom.us/meeting/summary/feedback?meetingId=xtQOHviqSnCDkHc0EPyLLw%3D%3D&email=cnJhaG1hbkBlcXVpbml4LmNvbQ==&feedback=bad>
Share summary<https://equinix.zoom.us/user/meeting/summary?meetingId=xtQOHviqSnCDkHc0EPyLLw%3D%3D&summaryId=mss_a2l3rcn4SSi9XSBlGtD2Zg&openDialog=true> Edit<https://equinix.zoom.us/user/meeting/summary?meetingId=xtQOHviqSnCDkHc0EPyLLw%3D%3D&summaryId=mss_a2l3rcn4SSi9XSBlGtD2Zg&fileId=-lrels6sQrqa7biNJTTUVQ>
Best,
Zoom
[Image removed by sender. Twitter]<https://urldefense.com/v3/__https:/twitter.com/zoom__;!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRH6cfIbuA$>
[Image removed by sender. LinkedIn]<https://urldefense.com/v3/__https:/www.linkedin.com/company/zoom-video-communications/__;!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRFRcOAPnQ$>
[Image removed by sender. Blog]<https://blog.zoom.us/>
+1.888.799.9666
©2025 Zoom Communications, Inc.
Visit zoom.com<https://urldefense.com/v3/__https:/zoom.com__;!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRFr7mbDSQ$>
55 Almaden Blvd<https://urldefense.com/v3/__https:/www.google.com/maps/place/55*Almaden*Blvd,*San*Jose,*CA*95113/@37.3328541,-121.897097,17z/data=!3m1!4b1!4m5!3m4!1s0x808fcca40adf3cb7:0x5a2d33d3593e0a33!8m2!3d37.3328541!4d-121.8949083__;KysrKysr!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRHFcLYu6A$>
San Jose, CA 95113<https://urldefense.com/v3/__https:/www.google.com/maps/place/55*Almaden*Blvd,*San*Jose,*CA*95113/@37.3328541,-121.897097,17z/data=!3m1!4b1!4m5!3m4!1s0x808fcca40adf3cb7:0x5a2d33d3593e0a33!8m2!3d37.3328541!4d-121.8949083__;KysrKysr!!PcPv50trKLWG!2M8mSK87VhIm-qK6Xy5csCtxkERbVTPLuJEb71TYSgC9UOJaGAqUSNfY10OXmI-Q-YkjzVd9nRHFcLYu6A$>


________________________________

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