[OPS-AREA]Re: [External] [NMOP] Re: [OPSAREA@I ETF126] IRTF/IETF OPS Transfer: Status & Exploring Collabor ation Opportunities [Commercial - Anyone]
Christopher Janz <[email protected]> Fri, 26 Jun 2026 08:40:50 +0000
| Newsgroups | gmane.ietf.ops,gmane.ietf.opsawg |
|---|---|
| Message-ID | <[email protected]> |
--===============2322846327604413293== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_b6c9cc47f26a4dd4a3b0943468fa223dhuaweicom_" --_000_b6c9cc47f26a4dd4a3b0943468fa223dhuaweicom_ Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable Hi Brad - I didn=1B$B!G=1B(Bt want to repeat the link from my original mess= age, but the draft is here: draft-janz-nmrg-ontology-reconciliation<https:/= /datatracker.ietf.org/doc/draft-janz-nmrg-ontology-reconciliation/>. It is = new, and will be presented in Vienna, with PoC(s). The idea is that cogniti= ve agents: (a) can reason, (b) can talk to each other, and (c) may be, or m= ay become, familiar with publicly available references. We show that such a= gents can establish or reconcile working communications models on their own= . My suggestion is that terminological references may usefully support inte= rpretation and disambiguation in that process without imposing any unnecess= ary rigidity or limitations, while the availability of the process itself m= ay reduce the need to standardize more =1B$B!H=1B(Bmachine-oriented=1B$B!I= =1B(B model artifacts. Perhaps our most useful =1B$B!H=1B(Bhuman design=1B$= B!I=1B(B work, and the forms of its outputs, will shift to a more abstracte= d key. This seems to be, after all, the general impact of cognitive AI. Best Chris From: Brad Peters <[email protected]> Sent: Thursday, June 25, 2026 8:53 PM To: Christopher Janz <[email protected]>; [email protected]= m; [email protected]; [email protected]; [email protected]; [email protected] Cc: [email protected] Subject: Re: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS Transfer= : Status & Exploring Collaboration Opportunities [Commercial - Anyone] Hi Chris, Spot on about data models versus information models. RFC 3444 still holds t= rue here, they definitely serve completely different purposes depending on = what you are trying to achieve. On the temporal side, dealing with fast-streaming state data versus slow-mo= ving graph data definitely points to a hybrid approach. Have you looked at = the Telefonica setup in the ETSI Common Information Model? Using a context = broker keyed on the same IRI looks like a practical way to bridge that gap. I must have missed the 'Ontology Reconciliation Draft' you mentioned (feel = free to provide a link). But parsing your point about agents reconciling wi= th 'no common data model assumed', I read that as absolutely requiring some= kind of higher-layer model to act as a shared anchor. They need that upper= layer to establish a common understanding, completely irrespective of the = specific data models sitting underneath. The real value for standardisation is moving up the abstraction stack to bu= ild that common vocabulary and terminology. We need that shared reference c= ore to provide cross-model linkage without forcing rigidity. There isn't a universally accepted standard information model for the netwo= rk right now, meaning there is limited ability to achieve a cognitive appro= ach. The question may be who creates and then governs this view of network = for the foreseeable future. Cheers. Brad ________________________________ From: Christopher Janz <[email protected]<mail= to:[email protected]>> Sent: Thursday, 25 June 2026 9:55 PM To: Brad Peters <[email protected]<mailto:[email protected]>>; = [email protected]<mailto:[email protected]> <Thomas.Graf@swis= scom.com<mailto:[email protected]>>; [email protected]<mailto:ops-ar= [email protected]> <[email protected]<mailto:[email protected]>>; [email protected]= <mailto:[email protected]> <[email protected]<mailto:[email protected]>>; nmop@ie= tf.org<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; nmrg@ir= tf.org<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <moha= [email protected]<mailto:[email protected]>> Subject: RE: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS Transfer= : Status & Exploring Collaboration Opportunities [Commercial - Anyone] EXTERNAL SENDER - Be cautious opening Links and Attachments Hi Brad, I agree with you on direction: AI-native autonomy and grounding probabilist= ic agents in something factual. I=1B$B!G=1B(Bd like to pull a bit more on t= he modeling thread. Data models and knowledge graphs are both concrete commitments to an ontolo= gy - one as schema, the other as schema populated with instances. So, it=1B= $B!G=1B(Bs really a question of purpose: which representation is best suite= d to a given objective. A data model commits meaning to a specific machine = form, which buys determinism and verifiability at the cost of flexibility -= a YANG module is the right artifact where a stable, high-volume interface = needs interop (config, telemetry subscriptions). A graph suits the cases wh= ere the questions are cross-domain and not knowable in advance - correlatin= g inventory, topology, alarms, telemetry, anomalies that no single system o= wns. Anomaly diagnosis I=1B$B!G=1B(Bd put on the graph side - mostly correlation= and traversal over heterogeneous, incompletely-anticipated evidence. But h= ybrid: link the fast telemetry rather than ingest it. Which is your tempora= l-gap design - graph for the slow-moving relationships, streamed models for= the fast state. But one might ask: what is the best focal point for standardization going f= orward? The emerging world is one in which systems are cognitive. In the pr= e-cognitive world, data models - a stable basis for system-to-system commun= ication - were the natural targets for standardization. Cognitive systems m= ay not require that basis a priori. Your YANG=1B$B"*=1B(BOWL compiler is, i= n effect, the first step - the =1B$B!H=1B(Blift=1B$B!I=1B(B portion - of a = mediation: making a model=1B$B!G=1B(Bs implicit ontology explicit. The onto= logy reconciliation draft I mentioned takes it from there, with two cogniti= ve agents reconciling their ontologies conversationally and generating dete= rministic translators, no common data model assumed. So, the effective question may be: if agents can converge on semantics and = lexicon by themselves - no initially shared data model, implicit ontologies= that may differ in various ways - what is most useful to standardize? My b= et is categorical ontologies and their terminologies - shared reference cor= es that ground, de-risk and speed automated mediation without imposing rigi= dity. Tellingly, a hard field problem cuts the same way: identity resolutio= n - deciding that several systems=1B$B!G=1B(B identifiers denote the same s= witch - is never solved by a rigid, complete data model (that only breeds t= ranslation tables and exception logic); it is made tractable by shared refe= rence semantics, which align the attributes you match on and move resolutio= n from the probabilistic regime toward the deterministic one. That speaks t= o where standardization earns its keep, not to dissolving entity resolution= , which stays implementation. Of course, purpose-optimized data models woul= d remain useful references and examples, and KGs are important system tools= - but the high-leverage standard artifacts may be moving up the abstractio= n stack, toward shared ontological cores rather than complete ontologies an= d fixed data structures. Best, Chris From: Brad Peters <[email protected]<mailto:bradpe= [email protected]>> Sent: Sunday, June 21, 2026 7:02 PM To: [email protected]<mailto:[email protected]>; ops-area@iet= f.org<mailto:[email protected]>; [email protected]<mailto:[email protected]>; n= [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [nmrg] Re: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS T= ransfer: Status & Exploring Collaboration Opportunities [Commercial - Anyon= e] Hi Thomas, Thank you for kicking off this discussion. The intersection of these workin= g groups aligns perfectly with the transition the industry is already makin= g: moving from AI-Enabled Network Operations to AI-Native Autonomous Operat= ions. To directly address your questions regarding how AI agents interact with Kn= owledge Graphs, Intent, and YANG data, I believe we must first distinguish = between automation and autonomy. Currently, most industry efforts focus on AI-enabled operations, essentiall= y using AI to assist human operators within legacy functional processes. Th= is places a layer of automation on top of existing silos (event/fault, perf= ormance, security, accounting). The fatal flaw here is that our current eve= nt/telemetry pipelines are fundamentally designed for human consumption. We= aggressively filter, aggregate, and discard high-frequency signals because= a human operator cannot process them. By doing so, we actively destroy the= granular context an AI needs. Creating a foundational model of the network and enriching it with state-ba= sed and fast-moving contextual data like streaming telemetry, is critical f= or providing AI agents with the information they need. We must shift from d= esign-time hardcoding to run-time enablement. Agents must be able to self-a= dapt while remaining grounded in factual reality, complete with the capabil= ity to safely test and evaluate insights before execution. AI-Native management is about true autonomy: operating on the network with = complete, unified context to produce an action with a high confidence inter= val. This is where the intersection of your mentioned topics becomes critic= al: * Grounding the Agent: LLMs are inherently probabilistic. To make deter= ministic, factual decisions, they require a grounding point. Knowledge Grap= hs (KGs) provide this definitive, end-to-end view of the network state. * Run-Time vs. Design-Time: Legacy automation embeds operational knowle= dge directly into the application code, creating a massive barrier to chang= e. A well-structured ontology allows us to separate the knowledge from the = application. Agents can infer and reason over the graph to adapt at run-tim= e rather than waiting for design-time code changes. * Bridging the Temporal Gap: A Knowledge Graph provides the determinist= ic baseline of slow-moving inventory and topological state. Real-time mecha= nisms like YANG-Push and gRPC provide the fast moving state and potentially= temporal (TSDB) data that overlays onto that graph. Together, they give th= e agent a complete slice of the operational environment to evaluate and tes= t proposed changes before execution. (Use of a context broker as per Telefo= nicia ETSI Common Information Model). This architectural shift is actively gaining traction. Just today, CommsDay= (an Australian Communication focused publication) highlighted a major Aust= ralian carrier rearchitecting their operations around a knowledge plane for= the reasons above. I presented on this exact challenge at the Broadband Fo= rum in March, specifically addressing the TM Forum autonomy ladder and the = "Knowledge Limit" that is hit at Level 3 if we rely on event-driven automat= ion rather than knowledge-driven autonomy. This links directly to, and is supported by, the previous IETF Knowledge Gr= aph team papers: * https://datatracker.ietf.org/doc/draft-mackey-nmop-kg-for-netops/ * https://datatracker.ietf.org/doc/draft-tailhardat-nmop-incident-manag= ement-noria/ Regarding "running code" and practical intersections, I have been developin= g a semantic compiler to translate IETF YANG models into OWL ontologies. Th= e goal is to layer additional semantics on top of the base models to suppor= t AI agents, integrating RFC9315 Operational Intent with TM Forum ontologie= s (like the TIO). You can view the current progress of bridging these domai= ns here: https://github.com/bradspau/Network-Ontology-Knowledge-Graphs. I believe exploring this semantic bridge, how IETF data models map to the o= ntologies required by systems for autonomous reasoning, would be a highly v= aluable agenda item for our joint discussions. Ultimately, this technology change demands a rethink of who is conducting t= he processes of the past. Are we still curating data for human limitations,= creating dashboards, and relying upon human interpretation? Or are agents = and systems now the primary receivers of data, responsible for producing te= sted operational insights and recommendations? Will be interesting to see how this unfolds with those that are current imp= lementers/developping. Cheers. Brad ________________________________ From: [email protected]<mailto:[email protected]> <Thomas.Gra= [email protected]<mailto:[email protected]>> Sent: Sunday, 21 June 2026 6:43 PM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:o= [email protected]>>; [email protected]<mailto:[email protected]> <[email protected]= g<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <nmop@ietf.= org<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <nmrg@irtf.= org<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <moha= [email protected]<mailto:[email protected]>> Subject: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS Transfer: St= atus & Exploring Collaboration Opportunities EXTERNAL SENDER - Be cautious opening Links and Attachments Dear NMRG, NMOP, OPSAWG and OPSAREA, First of all many thanks to Brad, Dan, Christopher, Alex, Qin and Bernard o= n their feedback. That=1B$B!G=1B(Bs a great start. I have been following this thread closely https://mailarchive.ietf.org/arch= /msg/nmop/gTPL1eBj5e3GMMt8qeUWmPP4oMg/ to understand wherever research and = industry adoption comes closer together, wherever there is interest for hav= ing a joint discussion and on what particular topic. What I observed so far is that we all share that AI in general and also AIO= ps research and adoption rate has dramatically increased. So far everybody = was very supportive on having a joint discussion. I would be interested to = have more feedback, especially also from those who think that it would not = bring much benefit with reasons why. >From what I observed, having an initial discussion on the following existin= g working group document topics and how they intersect * Network Digital Twin (https://datatracker.ietf.org/doc/html/draft-irt= f-nmrg-network-digital-twin-arch) * Intent-Based Networking (https://datatracker.ietf.org/doc/html/draft-= irtf-nmrg-ibn-usecases) * SIMAP (https://datatracker.ietf.org/doc/html/draft-ietf-nmop-simap-co= ncept) * YANG-Push to Message Broker integration (https://datatracker.ietf.org= /doc/html/draft-ietf-nmop-yang-message-broker-integration) and then having a discussions on the following raised questions perhaps: * Which AI agents capabilities are suitable for network management? * What is the impact of an AI network management process to YANG inform= ation, service, network and data modelling? * Is MCP (https://en.wikipedia.org/wiki/Model_Context_Protocol) a suita= ble protocol between AI agents and IETF network management data sources and= system components? * How does an AI agent interact with Network Digital Twin, Intent-Based= Networking, SIMAP, Knowledge Graphs and YANG data in Message Brokers? and move from there into some proposed work addressing these areas. And las= t but not least maybe wrapping up around running code. How experiments coul= d facilitate and exchange between both working groups. Alex brought up that= ANRW is once a year and perhaps on one or two other occasion the two worki= ng group could continuously actively exchange every year could be an intere= sting proposal. * Would that be a potential interesting agenda for everybody? * Did I miss anything or shall we focus more on a particular item? * Any particular discussion structure you would fancy? I also observed that authors authoring Knowledge Graph documents have voice= d wherever Knowledge Graph could be a topic of interest. I would love to se= e more discussions from other areas on this in particular how this intersec= ts with AIOps and AI assisted network management topics. I saw also that on= tologies have been mentioned, which I personally besides semantics believe = plays an important role with interacting with AI agents. As I am human, and not an AI agent, the observations and suggestions might = be unintentionally bias. So please feedback and comment. Best wishes Thomas From: Graf Thomas, SCS-INI-NET-VNC-E2E Sent: Monday, June 1, 2026 7:16 AM To: Nmop <[email protected]<mailto:[email protected]>>; [email protected]<mailto:nmrg@i= rtf.org> Cc: Mohamed Boucadair <[email protected]<mailto:mohamed.boucadai= [email protected]>>; nmrg-chairs <[email protected]<mailto:[email protected]= rg>>; Nmop-chairs <[email protected]<mailto:[email protected]>> Subject: FW: [OPSAREA@IETF126] IRTF/IETF OPS Transfer: Status & Exploring C= ollaboration Opportunities Dear NMRG and NMOP, Med approached me wherever I am willing to facilitate with the support of b= oth working group chairs a discussion between NMRG and NMOP on common inter= ests. Looking at the list of current adopted documents https://datatracker.ietf.org/group/nmrg/documents/ https://datatracker.ietf.org/wg/nmop/documents/ but also looking at AIOps related proposals https://github.com/IETF-OPS-AD/= misc/blob/main/ai-submissions-ietf125.md, and the related past side meeting= s in the network management domain, I see that the lifecycle on research an= d industry adoption of model and data driven network management becomes acc= elerated and therefore research and industry adoption comes more and more c= loser together. Looking at the bluesheets of IETF 125, I see that we had 10= 7 participants for NMRG and 115 for NMOP and 36 participants were attending= both NMRG and NMOP. Or in other words, I personally believe that both working groups have a lot= in common but also a also few things which makes them very unique and inte= resting to facilitate such a discussion. I might be wrong and therefore would like to get some feedback from both ma= iling lists first: * Would you agree that the lifecycle on research and industry adoption = of model and data driven network management becomes accelerated and therefo= re research and industry adoption comes more and more closer together? * Is there an interest at the NMRG and NMOP communities to have an exch= ange on currently adopted and future proposed work to identify synergies an= d common interests in both working groups and discuss how they could be add= ressed better? * Do you have a particular topic, set of documents or interest already = in mind? Best wishes Thomas From: [email protected]<mailto:[email protected]> <mo= [email protected]<mailto:[email protected]>> Sent: Monday, May 4, 2026 10:21 AM To: Graf Thomas, SCS-INI-NET-VNC-E2E <[email protected]<mailto:Thoma= [email protected]>>; [email protected]<mailto:[email protected]>; N= mop-chairs <[email protected]<mailto:[email protected]>> Cc: ops-ads <[email protected]<mailto:[email protected]>>; Dirk KUTSCHER <iet= [email protected]<mailto:[email protected]>> Subject: [OPSAREA@IETF126] IRTF/IETF OPS Transfer: Status & Exploring Colla= boration Opportunities Be aware: This is an external email. Hi all, I had several discussions recently with many IETF participants about the re= lationship between some work done in the IRTF and IETF. Specifically, I hea= rd several questions about the current mode of operation between NMRG and O= PS and whether/how activity transfer is happening between the two communiti= es. I do see a value in bringing some of these items from hallway discussio= n to our formal meetings :-) This can be the opportunity to explore between collaboration between the co= mmunities, and not rely only on the leadership level. See, for example, the= following excerpt form the NMRG Charter: =1B$B!H=1B(BThe IETF Operations and Management Area Directors are member= s of the NMRG mailing list and invited to NMRG meetings in order to ensure free flow o= f information in both directions, and to avoid duplication of work with th= e various IETF working groups.=1B$B!I=1B(B There are several WG/RG pairs that may be considered for collaboration (NMR= G/NMOP, MAPRG/IPPM, etc.) but I think that it would be better to scope the = discussion to a specific area. I suggest to focus this time on NMRG/NMOP. Thomas kindly accepted to drive a discussion on this topic in the IETF#126 = OPSAREA Session with some proposals to bridge both communities. Thomas is a= lso willing to collect feedback and coordinate between the NMRG/NMOP Chairs= , in particular. @NMOP/@NMRG Chairs: Would you be interested/willing to work with Thomas to = consolidate some discussion material? Thoughts and suggestions are welcome. Thank you. Cheers, Med ___________________________________________________________________________= _________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. --_000_b6c9cc47f26a4dd4a3b0943468fa223dhuaweicom_ Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-= jp"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <!--[if !mso]><style>v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style><![endif]--><style><!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:PMingLiU; panose-1:2 1 6 1 0 1 1 1 1 1;} @font-face {font-family:MingLiU; panose-1:2 1 6 9 0 1 1 1 1 1;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Aptos; panose-1:0 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"Trebuchet MS"; panose-1:2 11 6 3 2 2 2 2 2 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:"MS PGothic"; panose-1:2 11 6 0 7 2 5 8 2 4;} @font-face {font-family:"\@MS PGothic";} @font-face {font-family:"\@PMingLiU"; panose-1:2 1 6 1 0 1 1 1 1 1;} @font-face {font-family:"\@MingLiU"; panose-1:2 1 6 9 0 1 1 1 1 1;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:12.0pt; font-family:"PMingLiU",serif; mso-fareast-language:ZH-TW;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; font-size:12.0pt; font-family:MingLiU; mso-fareast-language:ZH-TW;} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas; mso-fareast-language:ZH-TW;} p.elementtoproof, li.elementtoproof, div.elementtoproof {mso-style-name:elementtoproof; margin:0in; font-size:12.0pt; font-family:"PMingLiU",serif; mso-fareast-language:ZH-TW;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} /* List Definitions */ @list l0 {mso-list-id:116871151; mso-list-template-ids:1843684724;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l0:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l0:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l0:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1 {mso-list-id:700975805; mso-list-template-ids:776757178;} @list l1:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l1:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l1:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l1:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2 {mso-list-id:835418731; mso-list-template-ids:936795818;} @list l2:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l2:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l2:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l2:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3 {mso-list-id:978607331; mso-list-template-ids:-1968256506;} @list l3:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l3:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l3:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l3:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4 {mso-list-id:1061173422; mso-list-template-ids:1224737056;} @list l4:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l4:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l4:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l4:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5 {mso-list-id:1261186323; mso-list-template-ids:-381921708;} @list l5:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l5:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l5:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l5:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6 {mso-list-id:1291012053; mso-list-template-ids:255257116;} @list l6:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l6:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l6:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l6:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7 {mso-list-id:1652294656; mso-list-template-ids:1048056890;} @list l7:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l7:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l7:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l7:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8 {mso-list-id:1702197353; mso-list-template-ids:1555364418;} @list l8:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l8:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l8:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l8:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9 {mso-list-id:2057730067; mso-list-template-ids:2061903888;} @list l9:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l9:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l9:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l9:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10 {mso-list-id:2090080112; mso-list-template-ids:-950527812;} @list l10:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l10:level2 {mso-level-number-format:bullet; mso-level-text:o; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:"Courier New"; mso-bidi-font-family:"Times New Roman";} @list l10:level3 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level4 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level5 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level6 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level7 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level8 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} @list l10:level9 {mso-level-number-format:bullet; mso-level-text:\F0A7; mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Wingdings;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea= k-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Hi Brad – I didn=1B$B!G=1B(Bt want to repeat the link from my = original message, but the draft is here: <a href=3D"https://datatracker.ietf.org/doc/draft-janz-nmrg-ontology-reconc= iliation/"> draft-janz-nmrg-ontology-reconciliation</a>. It is new, and will be present= ed in Vienna, with PoC(s). The idea is that cognitive agents: (a) can reaso= n, (b) can talk to each other, and (c) may be, or may become, familiar with= publicly available references. We show that such agents can establish or reconcile working communications= models on their own. My suggestion is that terminological references may u= sefully support interpretation and disambiguation in that process without i= mposing any unnecessary rigidity or limitations, while the availability of the process itself may reduce th= e need to standardize more =1B$B!H=1B(Bmachine-oriented=1B$B!I=1B(B model a= rtifacts. Perhaps our most useful =1B$B!H=1B(Bhuman design=1B$B!I=1B(B work= , and the forms of its outputs, will shift to a more abstracted key. This s= eems to be, after all, the general impact of cognitive AI.<o:p></o:p></span></p= > <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Best</span><span style=3D"font-size:11.0pt;font-family:"Calibri= ",sans-serif;mso-fareast-language:EN-US"><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span>= </p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;mso-fareast-language:EN-US">Chris<o:p></o:p></span><= /p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span>= </p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span>= </p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif">From:</span></b><span style=3D"font-size:11.0pt;= font-family:"Calibri",sans-serif"> Brad Peters <bradpeters=3D4= [email protected]> <br> <b>Sent:</b> Thursday, June 25, 2026 8:53 PM<br> <b>To:</b> Christopher Janz <[email protected]>; Thomas.Gra= [email protected]; [email protected]; [email protected]; [email protected]; nmrg@irt= f.org<br> <b>Cc:</b> [email protected]<br> <b>Subject:</b> Re: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS T= ransfer: Status & Exploring Collaboration Opportunities [Commercial - A= nyone]<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">Hi Chris,<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black"><o:p> </o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">Spot on about data models versus information models. RFC= 3444 still holds true here, they definitely serve completely different pur= poses depending on what you are trying to achieve.<o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">On the temporal side, dealing with fast-streaming state = data versus slow-moving graph data definitely points to a hybrid approach. = Have you looked at the Telefonica setup in the ETSI Common Information Model? Using a context broker keyed on the same IR= I looks like a practical way to bridge that gap.<o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">I must have missed the 'Ontology Reconciliation Draft' y= ou mentioned (feel free to provide a link). But parsing your point about ag= ents reconciling with 'no common data model assumed', I read that as absolutely requiring some kind of higher-layer model to act= as a shared anchor. They need that upper layer to establish a common under= standing, completely irrespective of the specific data models sitting under= neath.<o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">The real value for standardisation is moving up the abst= raction stack to build that common vocabulary and terminology. We need that= shared reference core to provide cross-model linkage without forcing rigidity.<o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black">There isn't a universally accepted standard information = model for the network right now, meaning there is limited ability to achiev= e a cognitive approach. The question may be who creates and then governs this view of network for the foreseeable future.<= o:p></o:p></span></p> </div> <div id=3D"Signature"> <div> <p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-famil= y:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal" style=3D"background:white"><span style=3D"font-size:= 11.0pt;font-family:"Arial",sans-serif;color:black">Cheers.<o:p></= o:p></span></p> <p class=3D"elementtoproof" style=3D"background:white"><b><span style=3D"fo= nt-size:11.0pt;font-family:"Arial",sans-serif;color:black"><br> Brad </span></b><span style=3D"color:black"><o:p></o:p></span></p> </div> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif;color:black"><o:p> </o:p></span></p> </div> <div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"> <hr size=3D"1" width=3D"98%" align=3D"center"> </div> <div id=3D"divRplyFwdMsg"> <div> <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif;color:black">From:</span></b><span style=3D"font-= size:11.0pt;font-family:"Calibri",sans-serif;color:black"> C= hristopher Janz <</span><a href=3D"mailto:christopher.janz=3D40huawei.co= [email protected]"><span style=3D"font-size:11.0pt;font-family:"Calibri= ",sans-serif">[email protected]</span></a= ><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif= ;color:black">><br> <b>Sent:</b> Thursday, 25 June 2026 9:55 PM<br> <b>To:</b> Brad Peters <</span><a href=3D"mailto:[email protected]= om.au"><span style=3D"font-size:11.0pt;font-family:"Calibri",sans= -serif">[email protected]</span></a><span style=3D"font-size:11.0pt;f= ont-family:"Calibri",sans-serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size= :11.0pt;font-family:"Calibri",sans-serif">[email protected]= m</span></a><span style=3D"font-size:11.0pt;font-family:"Calibri"= ,sans-serif;color:black"> <</span><a href=3D"mailto:Thomas.Graf@swisscom= .com"><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif">[email protected]</span></a><span style=3D"font-size:11.0pt;f= ont-family:"Calibri",sans-serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt= ;font-family:"Calibri",sans-serif">[email protected]</span></a><s= pan style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;co= lor:black"> <</span><a href=3D"mailto:[email protected]"><span style=3D"= font-size:11.0pt;font-family:"Calibri",sans-serif">ops-area@ietf.= org</span></a><span style=3D"font-size:11.0pt;font-family:"Calibri&quo= t;,sans-serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;f= ont-family:"Calibri",sans-serif">[email protected]</span></a><span = style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:= black"> <</span><a href=3D"mailto:[email protected]"><span style=3D"font-s= ize:11.0pt;font-family:"Calibri",sans-serif">[email protected]</spa= n></a><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:blac= k"> <</span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11= .0pt;font-family:"Calibri",sans-serif">[email protected]</span></a><s= pan style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;co= lor:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:blac= k"> <</span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11= .0pt;font-family:"Calibri",sans-serif">[email protected]</span></a><s= pan style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;co= lor:black">><br> <b>Cc:</b> </span><a href=3D"mailto:[email protected]"><spa= n style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">moh= [email protected]</span></a><span style=3D"font-size:11.0pt;font-fa= mily:"Calibri",sans-serif;color:black"> <</span><a href=3D"mai= lto:[email protected]"><span style=3D"font-size:11.0pt;font-fami= ly:"Calibri",sans-serif">[email protected]</span></a><= span style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;c= olor:black">><br> <b>Subject:</b> RE: [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF = OPS Transfer: Status & Exploring Collaboration Opportunities [Commercia= l - Anyone]<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-family:"Times New Roman&quo= t;,serif"> </span><o:p></o:p></p> </div> </div> <p><b><span style=3D"color:red">EXTERNAL SENDER </span></b><b><span style= =3D"font-family:"Times New Roman",serif;color:red">–</span>= <span style=3D"color:red"> Be cautious opening Links and Attachments</span>= </b><o:p></o:p></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Hi Bra= d,<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">I agre= e with you on direction: AI-native autonomy and grounding probabilistic age= nts in something factual. I=1B$B!G=1B(Bd like to pull a bit more on the modeling thread.<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Data m= odels and knowledge graphs are both concrete commitments to an ontology = 212; one as schema, the other as schema populated with instances. So, it=1B$B!G=1B(Bs really a question of purpose: which represe= ntation is best suited to a given objective. A data model commits meaning t= o a specific machine form, which buys determinism and verifiability at the = cost of flexibility — a YANG module is the right artifact where a stable, high-volume interface needs interop (config= , telemetry subscriptions). A graph suits the cases where the questions are= cross-domain and not knowable in advance — correlating inventory, to= pology, alarms, telemetry, anomalies that no single system owns.<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Anomal= y diagnosis I=1B$B!G=1B(Bd put on the graph side — mostly correlation= and traversal over heterogeneous, incompletely-anticipated evidence. But hybrid: link the fast telemetry rather than ingest it. Which is y= our temporal-gap design — graph for the slow-moving relationships, st= reamed models for the fast state.<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">But on= e might ask: what is the best focal point for standardization going forward= ? The emerging world is one in which systems are cognitive. In the pre-cognitive world, data models — a stable b= asis for system-to-system communication — were the natural targets fo= r standardization. Cognitive systems may not require that basis <i>a priori</i>. Your YANG=1B$B"*=1B(BOWL compiler is, in effect, the first= step — the =1B$B!H=1B(Blift=1B$B!I=1B(B portion — of a mediati= on: making a model=1B$B!G=1B(Bs implicit ontology explicit. The ontology re= conciliation draft I mentioned takes it from there, with two cognitive agen= ts reconciling their ontologies conversationally and generating deterministic translators= , no common data model assumed.<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">So, th= e effective question may be: if agents can converge on semantics and lexico= n by themselves — no initially shared data model, implicit ontologies that may differ in various ways — what is most u= seful to standardize? My bet is categorical ontologies and their terminolog= ies — shared reference cores that ground, de-risk and speed automated= mediation without imposing rigidity. Tellingly, a hard field problem cuts the same way: identity resolution — decidi= ng that several systems=1B$B!G=1B(B identifiers denote the same switch R= 12; is never solved by a rigid, complete data model (that only breeds trans= lation tables and exception logic); it is made tractable by shared reference semantics, which align the attributes you match on and= move resolution from the probabilistic regime toward the deterministic one= . That speaks to where standardization earns its keep, not to dissolving en= tity resolution, which stays implementation. Of course, purpose-optimized data models would remain useful references an= d examples, and KGs are important system tools — but the high-leverag= e standard artifacts may be moving up the abstraction stack, toward shared = ontological cores rather than complete ontologies and fixed data structures.<o:p></o:p></span></p> <p style=3D"margin-bottom:10.0pt;line-height:115%"><span style=3D"font-size= :11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Best,<= o:p></o:p></span></p> <p><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if">Chris<o:p></o:p></span></p> <p><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if"> <o:p></o:p></span></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p><b><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif">From:</span></b><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif"> Brad Peters <</span><a href=3D"mailto:brad= [email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">bradpeters=3D40nbnco.com.au@dmarc.= ietf.org</span></a><span style=3D"font-size:11.0pt;font-family:"Calibr= i",sans-serif">><br> <b>Sent:</b> Sunday, June 21, 2026 7:02 PM<br> <b>To:</b> </span><a href=3D"mailto:[email protected]"><span st= yle=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">Thomas.= [email protected]</span></a><span style=3D"font-size:11.0pt;font-family:&qu= ot;Calibri",sans-serif">; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt= ;font-family:"Calibri",sans-serif">[email protected]</span></a><s= pan style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;f= ont-family:"Calibri",sans-serif">[email protected]</span></a><span = style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><br> <b>Cc:</b> </span><a href=3D"mailto:[email protected]"><spa= n style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">moh= [email protected]</span></a><span style=3D"font-size:11.0pt;font-fa= mily:"Calibri",sans-serif"><br> <b>Subject:</b> [nmrg] Re: [External] [NMOP] Re: [OPSAREA@IETF126] IRT= F/IETF OPS Transfer: Status & Exploring Collaboration Opportunities [Co= mmercial - Anyone]<o:p></o:p></span></p> </div> <p><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if"> <o:p></o:p></span></p> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Hi Thoma= s,</span><span style=3D"font-size:11.0pt;font-family:"Calibri",sa= ns-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Thank yo= u for kicking off this discussion. The intersection of these working groups= aligns perfectly with the transition the industry is already making: movin= g from AI-Enabled Network Operations to AI-Native Autonomous Operations.</span><span style=3D"font-size:11.0pt;font-family:&= quot;Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">To direc= tly address your questions regarding how AI agents interact with Knowledge = Graphs, Intent, and YANG data, I believe we must first distinguish between = automation and autonomy.</span><span style=3D"font-size:11.0pt;font-family:= "Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Currentl= y, most industry efforts focus on AI-enabled operations, essentially using = AI to assist human operators within legacy functional processes. This place= s a layer of automation on top of existing silos (event/fault, performance, security, accounting). The fatal flaw here is t= hat our current event/telemetry pipelines are fundamentally designed for hu= man consumption. We aggressively filter, aggregate, and discard high-freque= ncy signals because a human operator cannot process them. By doing so, we actively destroy the granular context= an AI needs.</span><span style=3D"font-size:11.0pt;font-family:"Calib= ri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Creating= a foundational model of the network and enriching it with state-based and = fast-moving contextual data like streaming telemetry, is critical for provi= ding AI agents with the information they need. We must shift from design-time hardcoding to run-time enablement. Agents m= ust be able to self-adapt while remaining grounded in factual reality, comp= lete with the capability to safely test and evaluate insights before execut= ion.</span><span style=3D"font-size:11.0pt;font-family:"Calibri",= sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">AI-Nativ= e management is about true autonomy: operating on the network with complete= , unified context to produce an action with a high confidence interval. Thi= s is where the intersection of your mentioned topics becomes critical:</span><span style=3D"font-size:11.0pt;font-family= :"Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:black;margin-top:12.0pt;margin-botto= m:12.0pt;mso-list:l6 level1 lfo1"> <span style=3D"font-family:"Aptos",serif">Grounding the Agent:&nb= sp;LLMs are inherently probabilistic. To make deterministic, factual decisi= ons, they require a grounding point. Knowledge Graphs (KGs) provide this de= finitive, end-to-end view of the network state.</span><span style=3D"font-s= ize:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></= li></ul> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:black;mso-list:l7 level1 lfo2"><span= style=3D"font-family:"Aptos",serif">Run-Time vs. Design-Time:&nb= sp;Legacy automation embeds operational knowledge directly into the applica= tion code, creating a massive barrier to change. A well-structured ontology allows us to separate the knowledge from the application. Agents = can infer and reason over the graph to adapt at run-time rather than waitin= g for design-time code changes.</span><span style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif"><o:p></o:p></span></li></ul> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:black;mso-list:l4 level1 lfo3"><span= style=3D"font-family:"Aptos",serif">Bridging the Temporal Gap:&n= bsp;A Knowledge Graph provides the deterministic baseline of slow-moving in= ventory and topological state. Real-time mechanisms like YANG-Push and gRPC provide the fast moving state and potentially temporal = (TSDB) data that overlays onto that graph. Together, they give the agent a = complete slice of the operational environment to evaluate and test proposed= changes before execution. (Use of a context broker as per Telefonicia ETSI Common Information Model).</sp= an><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if"><o:p></o:p></span></li></ul> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">This arc= hitectural shift is actively gaining traction. Just today, CommsDay (an Aus= tralian Communication focused publication) highlighted a major Australian c= arrier rearchitecting their operations around a knowledge plane for the reasons above. I presented on this exact challen= ge at the Broadband Forum in March, specifically addressing the TM Forum au= tonomy ladder and the "Knowledge Limit" that is hit at Level 3 if= we rely on event-driven automation rather than knowledge-driven autonomy.</span><span style=3D"font-size:11.0pt;font= -family:"Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">This lin= ks directly to, and is supported by, the previous IETF Knowledge Graph team= papers:</span><span style=3D"font-size:11.0pt;font-family:"Calibri&qu= ot;,sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:black;mso-list:l3 level1 lfo4"><a hr= ef=3D"https://datatracker.ietf.org/doc/draft-mackey-nmop-kg-for-netops/"><s= pan style=3D"font-family:"Aptos",serif">https://datatracker.ietf.= org/doc/draft-mackey-nmop-kg-for-netops/</span></a><span style=3D"font-size= :11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li>= </ul> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:black;mso-list:l8 level1 lfo5"><a hr= ef=3D"https://datatracker.ietf.org/doc/draft-tailhardat-nmop-incident-manag= ement-noria/"><span style=3D"font-family:"Aptos",serif">https://d= atatracker.ietf.org/doc/draft-tailhardat-nmop-incident-management-noria/</s= pan></a><span style=3D"font-size:11.0pt;font-family:"Calibri",san= s-serif"><o:p></o:p></span></li></ul> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Regardin= g "running code" and practical intersections, I have been develop= ing a semantic compiler to translate IETF YANG models into OWL ontologies. = The goal is to layer additional semantics on top of the base models to support AI agents, integrating RFC9315 Operational Intent w= ith TM Forum ontologies (like the TIO). You can view the current progress o= f bridging these domains here: </span><a href=3D"https://github.com/bradspau/Network-Ontology-Knowledge-Gr= aphs"><span style=3D"font-family:"Aptos",serif">https://github.co= m/bradspau/Network-Ontology-Knowledge-Graphs</span></a><span style=3D"font-= family:"Aptos",serif;color:black">.</span><span style=3D"font-siz= e:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">I believ= e exploring this semantic bridge, how IETF data models map to the ontologie= s required by systems for autonomous reasoning, would be a highly valuable = agenda item for our joint discussions.</span><span style=3D"font-size:11.0p= t;font-family:"Calibri",sans-serif"><o:p></o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Ultimate= ly, this technology change demands a rethink of who is conducting the = processes of the past. Are we still curating data for human limitations, cr= eating dashboards, and relying upon human interpretation? Or are agents and systems now the primary receivers of data, responsible f= or producing tested operational insights and recommendations?</span><span s= tyle=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p><= /o:p></span></p> </div> <div style=3D"margin-top:12.0pt;margin-bottom:12.0pt"> <p><span style=3D"font-family:"Aptos",serif;color:black">Will be = interesting to see how this unfolds with those that are current implementer= s/developping. </span><span style=3D"font-size:11.0pt;font-family:&quo= t;Calibri",sans-serif"><o:p></o:p></span></p> </div> <div id=3D"x_Signature"> <p style=3D"background:white"><span style=3D"font-size:11.0pt;font-family:&= quot;Aptos",serif;color:black">Cheers.</span><span style=3D"font-size:= 11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p> <p style=3D"background:white"><b><span style=3D"font-size:11.0pt;font-famil= y:"Aptos",serif;color:black"><br> Brad </span></b><span style=3D"font-size:11.0pt;font-family:"Cali= bri",sans-serif"><o:p></o:p></span></p> </div> <p><span style=3D"font-family:"Aptos",serif;color:black"> </= span><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-s= erif"><o:p></o:p></span></p> <div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"> <hr size=3D"1" width=3D"98%" align=3D"center"> </div> <div id=3D"x_divRplyFwdMsg"> <p><b><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif;color:black">From:</span></b><span style=3D"font-size:11.0pt;font-fam= ily:"Calibri",sans-serif;color:black"> </span><a href=3D"mai= lto:[email protected]"><span style=3D"font-size:11.0pt;font-family:&= quot;Calibri",sans-serif">[email protected]</span></a><span sty= le=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:bla= ck"> <</span><a href=3D"mailto:[email protected]"><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">Thomas.Gr= [email protected]</span></a><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif;color:black">><br> <b>Sent:</b> Sunday, 21 June 2026 6:43 PM<br> <b>To:</b> </span><a href=3D"mailto:[email protected]"><span style=3D"= font-size:11.0pt;font-family:"Calibri",sans-serif">ops-area@ietf.= org</span></a><span style=3D"font-size:11.0pt;font-family:"Calibri&quo= t;,sans-serif;color:black"> <</span><a href=3D"mailto:ops-area@ietf= .org"><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif">[email protected]</span></a><span style=3D"font-size:11.0pt;font-fam= ily:"Calibri",sans-serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;f= ont-family:"Calibri",sans-serif">[email protected]</span></a><span = style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:= black"> <</span><a href=3D"mailto:[email protected]"><span style=3D"f= ont-size:11.0pt;font-family:"Calibri",sans-serif">[email protected]= </span></a><span style=3D"font-size:11.0pt;font-family:"Calibri",= sans-serif;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:blac= k"> <</span><a href=3D"mailto:[email protected]"><span style=3D"font-si= ze:11.0pt;font-family:"Calibri",sans-serif">[email protected]</span><= /a><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if;color:black">>; </span><a href=3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fon= t-family:"Calibri",sans-serif">[email protected]</span></a><span styl= e=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;color:blac= k"> <</span><a href=3D"mailto:[email protected]"><span style=3D"font-si= ze:11.0pt;font-family:"Calibri",sans-serif">[email protected]</span><= /a><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if;color:black">><br> <b>Cc:</b> </span><a href=3D"mailto:[email protected]"><spa= n style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif">moh= [email protected]</span></a><span style=3D"font-size:11.0pt;font-fa= mily:"Calibri",sans-serif;color:black"> <</span><a href= =3D"mailto:[email protected]"><span style=3D"font-size:11.0pt;fo= nt-family:"Calibri",sans-serif">[email protected]</spa= n></a><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-= serif;color:black">><br> <b>Subject:</b> [External] [NMOP] Re: [OPSAREA@IETF126] IRTF/IETF OPS = Transfer: Status & Exploring Collaboration Opportunities</span><span st= yle=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></= o:p></span></p> <p><span style=3D"font-size:11.0pt;font-family:"Calibri",sans-ser= if"> <o:p></o:p></span></p> </div> <p><b><span style=3D"color:red">EXTERNAL SENDER </span></b><b><span style= =3D"font-family:"Times New Roman",serif;color:red">–</span>= <span style=3D"color:red"> Be cautious opening Links and Attachments</span>= </b><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Dear NMRG, NMOP, OPSAWG and OPSAREA,</span><o:p></o:= p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">First of all many thanks to Brad, Dan, Christopher, = Alex, Qin and Bernard on their feedback. That=1B$B!G=1B(Bs a great start.</= span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">I have been following this thread closely </span><a href=3D"https://mailarchive.ietf.org/arch/msg/nmop/gTPL1eBj5e3GMM= t8qeUWmPP4oMg/"><span style=3D"font-size:10.0pt;font-family:"Trebuchet= MS",sans-serif;color:#467886">https://mailarchive.ietf.org/arch/msg/n= mop/gTPL1eBj5e3GMMt8qeUWmPP4oMg/</span></a><span style=3D"font-size:10.0pt;= font-family:"Trebuchet MS",sans-serif;color:#0E2841"> to understand wherever research and industry adoption comes closer together, = wherever there is interest for having a joint discussion and on what partic= ular topic.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">What I observed so far is that we all share that AI = in general and also AIOps research and adoption rate has dramatically incre= ased. So far everybody was very supportive on having a joint discussion. I would be interested to have more feedback, es= pecially also from those who think that it would not bring much benefit wit= h reasons why.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">From what I observed, having an initial discussion o= n the following existing working group document topics and how they interse= ct</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l10 level1 lfo6"><s= pan style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-ser= if">Network Digital Twin (</span><a href=3D"https://datatracker.ietf.org/do= c/html/draft-irtf-nmrg-network-digital-twin-arch"><span style=3D"font-size:= 10.0pt;font-family:"Trebuchet MS",sans-serif;color:#467886">https= ://datatracker.ietf.org/doc/html/draft-irtf-nmrg-network-digital-twin-arch<= /span></a><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS&qu= ot;,sans-serif">)</span><span style=3D"font-size:11.0pt;font-family:"C= alibri",sans-serif"><o:p></o:p></span></li><li class=3D"MsoNormal" sty= le=3D"color:#0E2841;mso-list:l10 level1 lfo6"><span style=3D"font-size:10.0= pt;font-family:"Trebuchet MS",sans-serif">Intent-Based Networking= (</span><a href=3D"https://datatracker.ietf.org/doc/html/draft-irtf-nmrg-i= bn-usecases"><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS= ",sans-serif;color:#467886">https://datatracker.ietf.org/doc/html/draf= t-irtf-nmrg-ibn-usecases</span></a><span style=3D"font-size:10.0pt;font-fam= ily:"Trebuchet MS",sans-serif">)</span><span style=3D"font-size:1= 1.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><l= i class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l10 level1 lfo6"><spa= n style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-serif= ">SIMAP (</span><a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf= -nmop-simap-concept"><span style=3D"font-size:10.0pt;font-family:"Treb= uchet MS",sans-serif;color:#467886">https://datatracker.ietf.org/doc/h= tml/draft-ietf-nmop-simap-concept</span></a><span style=3D"font-size:10.0pt= ;font-family:"Trebuchet MS",sans-serif">)</span><span style=3D"fo= nt-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></spa= n></li><li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l10 level1 l= fo6"><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",s= ans-serif">YANG-Push to Message Broker integration (</span><a href=3D"https= ://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-message-broker-integr= ation"><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS"= ,sans-serif;color:#467886">https://datatracker.ietf.org/doc/html/draft-ietf= -nmop-yang-message-broker-integration</span></a><span style=3D"font-size:10= .0pt;font-family:"Trebuchet MS",sans-serif">)</span><span style= =3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p= ></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">and then having a discussions on the following raise= d questions perhaps:</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l1 level1 lfo7"><sp= an style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-seri= f">Which AI agents capabilities are suitable for network management?</span>= <span style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"= ><o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:#0E2841;mso-= list:l1 level1 lfo7"><span style=3D"font-size:10.0pt;font-family:"Treb= uchet MS",sans-serif">What is the impact of an AI network management p= rocess to YANG information, service, network and data modelling?</span><spa= n style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><o:= p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list= :l1 level1 lfo7"><span style=3D"font-size:10.0pt;font-family:"Trebuche= t MS",sans-serif">Is MCP (</span><a href=3D"https://en.wikipedia.org/w= iki/Model_Context_Protocol"><span style=3D"font-size:10.0pt;font-family:&qu= ot;Trebuchet MS",sans-serif;color:#467886">https://en.wikipedia.org/wi= ki/Model_Context_Protocol</span></a><span style=3D"font-size:10.0pt;font-fa= mily:"Trebuchet MS",sans-serif">) a suitable protocol between AI agents and IETF network management data sou= rces and system components?</span><span style=3D"font-size:11.0pt;font-fami= ly:"Calibri",sans-serif"><o:p></o:p></span></li><li class=3D"MsoN= ormal" style=3D"color:#0E2841;mso-list:l1 level1 lfo7"><span style=3D"font-= size:10.0pt;font-family:"Trebuchet MS",sans-serif">How does an AI= agent interact with Network Digital Twin, Intent-Based Networking, SIMAP, = Knowledge Graphs and YANG data in Message Brokers?</span><span style=3D"font-size:11.0pt;font-family:&quo= t;Calibri",sans-serif"><o:p></o:p></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">and move from there into some proposed work addressi= ng these areas. And last but not least maybe wrapping up around running cod= e. How experiments could facilitate and exchange between both working groups. Alex brought up that ANRW is once a year and = perhaps on one or two other occasion the two working group could continuous= ly actively exchange every year could be an interesting proposal.</span><o:= p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l9 level1 lfo8"><sp= an style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-seri= f">Would that be a potential interesting agenda for everybody?</span><span = style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p>= </o:p></span></li><li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l= 9 level1 lfo8"><span style=3D"font-size:10.0pt;font-family:"Trebuchet = MS",sans-serif">Did I miss anything or shall we focus more on a partic= ular item?</span><span style=3D"font-size:11.0pt;font-family:"Calibri&= quot;,sans-serif"><o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"c= olor:#0E2841;mso-list:l9 level1 lfo8"><span style=3D"font-size:10.0pt;font-= family:"Trebuchet MS",sans-serif">Any particular discussion struc= ture you would fancy?</span><span style=3D"font-size:11.0pt;font-family:&qu= ot;Calibri",sans-serif"><o:p></o:p></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">I also observed that authors authoring Knowledge Gra= ph documents have voiced wherever Knowledge Graph could be a topic of inter= est. I would love to see more discussions from other areas on this in particular how this intersects with AIOps and AI as= sisted network management topics. I saw also that ontologies have been ment= ioned, which I personally besides semantics believe plays an important role= with interacting with AI agents.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">As I am human, and not an AI agent, the observations= and suggestions might be unintentionally bias. So please feedback and comm= ent.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Best wishes</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Thomas</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p><b>From:</b><span style=3D"font-family:"Times New Roman",serif= "> </span>Graf Thomas, SCS-INI-NET-VNC-E2E<br> <b>Sent:</b><span style=3D"font-family:"Times New Roman",serif">&= nbsp;</span>Monday, June 1, 2026 7:16 AM<br> <b>To:</b><span style=3D"font-family:"Times New Roman",serif">&nb= sp;</span>Nmop <<a href=3D"mailto:[email protected]"><span style=3D"color:#4= 67886">[email protected]</span></a>>; <a href=3D"mailto:[email protected]"><span style=3D"color:#467886">[email protected]= g</span></a><br> <b>Cc:</b><span style=3D"font-family:"Times New Roman",serif">&nb= sp;</span>Mohamed Boucadair <<a href=3D"mailto:mohamed.boucadair@orange.= com"><span style=3D"color:#467886">[email protected]</span></a>&= gt;; nmrg-chairs <<a href=3D"mailto:[email protected]"><span style=3D= "color:#467886">[email protected]</span></a>>; Nmop-chairs <<a href=3D"mailto:[email protected]"><span style=3D"col= or:#467886">[email protected]</span></a>><br> <b>Subject:</b><span style=3D"font-family:"Times New Roman",serif= "> </span>FW: [OPSAREA@IETF126] IRTF/IETF OPS Transfer: Status & E= xploring Collaboration Opportunities<o:p></o:p></p> </div> <p><span style=3D"font-family:"Aptos",serif"> </span><o:p></= o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Dear NMRG and NMOP,</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Med approached me wherever I am willing to facilitat= e with the support of both working group chairs a discussion between NMRG a= nd NMOP on common interests.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Looking at the list of current adopted documents</sp= an><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><a href=3D"https://datatracker.ietf.org/group/nmrg/documents/"><span sty= le=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-serif;colo= r:#467886">https://datatracker.ietf.org/group/nmrg/documents/</span></a><o:= p></o:p></p> <p><a href=3D"https://datatracker.ietf.org/wg/nmop/documents/"><span style= =3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-serif;color:= #467886">https://datatracker.ietf.org/wg/nmop/documents/</span></a><o:p></o= :p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">but also looking at AIOps related proposals </span><a href=3D"https://github.com/IETF-OPS-AD/misc/blob/main/ai-submissi= ons-ietf125.md"><span style=3D"font-size:10.0pt;font-family:"Trebuchet= MS",sans-serif;color:#467886">https://github.com/IETF-OPS-AD/misc/blo= b/main/ai-submissions-ietf125.md</span></a><span style=3D"font-size:10.0pt;= font-family:"Trebuchet MS",sans-serif;color:#0E2841">, and the related past side meetings in the network management domain, I see= that the lifecycle on research and industry adoption of model and data dri= ven network management becomes accelerated and therefore research and indus= try adoption comes more and more closer together. Looking at the bluesheets of IETF 125, I see that we had = 107 participants for NMRG and 115 for NMOP and 36 participants were attendi= ng both NMRG and NMOP.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Or in other words, I personally believe that both wo= rking groups have a lot in common but also a also few things which makes th= em very unique and interesting to facilitate such a discussion.</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">I might be wrong and therefore would like to get som= e feedback from both mailing lists first:</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l5 level1 lfo9"><sp= an style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-seri= f">Would you agree that the lifecycle on research and industry adoption of = model and data driven network management becomes accelerated and therefore research and industry adoption comes more and mo= re closer together?</span><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif"><o:p></o:p></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l2 level1 lfo10"><s= pan style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-ser= if">Is there an interest at the NMRG and NMOP communities to have an exchan= ge on currently adopted and future proposed work to identify synergies and common interests in both working groups and disc= uss how they could be addressed better?</span><span style=3D"font-size:11.0= pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <ul style=3D"margin-top:0in" type=3D"disc"> <li class=3D"MsoNormal" style=3D"color:#0E2841;mso-list:l0 level1 lfo11"><s= pan style=3D"font-size:10.0pt;font-family:"Trebuchet MS",sans-ser= if">Do you have a particular topic, set of documents or interest already in= mind?</span><span style=3D"font-size:11.0pt;font-family:"Calibri"= ;,sans-serif"><o:p></o:p></span></li></ul> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Best wishes</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841">Thomas</span><o:p></o:p></p> <p><span style=3D"font-size:10.0pt;font-family:"Trebuchet MS",san= s-serif;color:#0E2841"> </span><o:p></o:p></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p><b>From:</b> <a href=3D"mailto:[email protected]"><span style= =3D"color:#467886">[email protected]</span></a><span style=3D"fo= nt-family:"Times New Roman",serif"> </span><<a href=3D"ma= ilto:[email protected]"><span style=3D"color:#467886">mohamed.bo= [email protected]</span></a>><br> <b>Sent:</b><span style=3D"font-family:"Times New Roman",serif">&= nbsp;</span>Monday, May 4, 2026 10:21 AM<br> <b>To:</b><span style=3D"font-family:"Times New Roman",serif">&nb= sp;</span>Graf Thomas, SCS-INI-NET-VNC-E2E <<a href=3D"mailto:Thomas.Gra= [email protected]"><span style=3D"color:#467886">[email protected]</spa= n></a>>; <a href=3D"mailto:[email protected]"><span style=3D"color:#467886">nmrg-= [email protected]</span></a>; Nmop-chairs <<a href=3D"mailto:nmop-chairs@i= etf.org"><span style=3D"color:#467886">[email protected]</span></a>><= br> <b>Cc:</b><span style=3D"font-family:"Times New Roman",serif">&nb= sp;</span>ops-ads <<a href=3D"mailto:[email protected]"><span style=3D"co= lor:#467886">[email protected]</span></a>>; Dirk KUTSCHER <<a href=3D"= mailto:[email protected]"><span style=3D"color:#467886">[email protected]= </span></a>><br> <b>Subject:</b><span style=3D"font-family:"Times New Roman",serif= "> </span>[OPSAREA@IETF126] IRTF/IETF OPS Transfer: Status & Explo= ring Collaboration Opportunities<o:p></o:p></p> </div> <p><span style=3D"font-family:"Aptos",serif"> </span><o:p></= o:p></p> <table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"0" cellpadding= =3D"0" align=3D"left" width=3D"100%" style=3D"width:100.0%"> <tbody> <tr> <td style=3D"background:#CF4A0C;padding:5.0pt 2.0pt 5.0pt 2.0pt"></td> <td width=3D"100%" style=3D"width:100.0%;background:#FFF8E5;padding:5.0pt 4= .0pt 5.0pt 12.0pt"> <p style=3D"mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-w= rap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizon= tal:column;mso-height-rule:exactly"> <b><span style=3D"font-size:10.0pt;font-family:"Aptos",serif;colo= r:#222222">Be aware:</span></b><span style=3D"font-size:10.0pt;font-family:= "Aptos",serif;color:#222222"> This is an external email.</sp= an><span style=3D"font-size:10.0pt;font-family:"Times New Roman",= serif"><o:p></o:p></span></p> </td> </tr> </tbody> </table> <p><span style=3D"font-family:"Aptos",serif"> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">Hi all,</span><o:p><= /o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">I had several discus= sions recently with many IETF participants about the relationship between s= ome work done in the IRTF and IETF. Specifically, I heard several questions= about the current mode of operation between NMRG and OPS and whether/how activity transfer is happening between the tw= o communities. I do see a value in bringing some of these items from hallwa= y discussion to our formal meetings :-)</span><o:p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">This can be the oppo= rtunity to explore between collaboration between the communities, and not r= ely only on the leadership level. See, for example, the following excerpt f= orm the NMRG Charter:</span><o:p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New""> =1B$B!H= =1B(BThe IETF Operations and Management Area Directors are members of the N= MRG<br> mailing list and invited to NMRG meetings in order to ensure f= ree flow of<br> information in both directions, and to avoid duplication of wo= rk with the<br> various IETF working groups.=1B$B!I=1B(B</span><o:p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">There are several WG= /RG pairs that may be considered for collaboration (NMRG/NMOP, MAPRG/IPPM, = etc.) but I think that it would be better to scope the discussion to a spec= ific area. I suggest to focus this time on NMRG/NMOP.</span><o:p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">Thomas kindly accept= ed to drive a discussion on this topic in the IETF#126 OPSAREA Session with= some proposals to bridge both communities. Thomas is also willing to colle= ct feedback and coordinate between the NMRG/NMOP Chairs, in particular.</span><o:p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">@NMOP/@NMRG Chairs: = Would you be interested/willing to work with Thomas to consolidate some dis= cussion material? Thoughts and suggestions are welcome.</span><o:p></o:p></= p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">Thank you.</span><o:= p></o:p></p> <p><span style=3D"font-family:"Courier New""> </span><o:p></= o:p></p> <p><span style=3D"font-family:"Courier New"">Cheers,</span><o:p><= /o:p></p> <p><span style=3D"font-family:"Courier New"">Med</span><o:p></o:p= ></p> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">_= ___________________________________________________________________________= ________________________________<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">C= e message et ses pieces jointes peuvent contenir des informations confident= ielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">p= as etre diffuses, exploites ou copies sans autorisation. Si vous avez recu = ce message par erreur, veuillez le signaler<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">a= l'expediteur et le detruire ainsi que les pieces jointes. Les messages ele= ctroniques etant susceptibles d'alteration,<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">O= range decline toute responsabilite si ce message a ete altere, deforme ou f= alsifie. Merci.<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">&= nbsp;<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">T= his message and its attachments may contain confidential or privileged info= rmation that may be protected by law;<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">t= hey should not be distributed, used or copied without authorisation.<o:p></= o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">I= f you have received this email in error, please notify the sender and delet= e this message and its attachments.<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">A= s emails may be altered, Orange is not liable for messages that have been m= odified, changed or falsified.<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">T= hank you.<o:p></o:p></span></pre> </div> <div> <pre><span style=3D"font-size:10.0pt;font-family:"Courier New"">&= nbsp;<o:p></o:p></span></pre> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </div> </body> </html> --_000_b6c9cc47f26a4dd4a3b0943468fa223dhuaweicom_-- --===============2322846327604413293== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTLUFSRUEg bWFpbGluZyBsaXN0IC0tIG9wcy1hcmVhQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4g ZW1haWwgdG8gb3BzLWFyZWEtbGVhdmVAaWV0Zi5vcmcK --===============2322846327604413293==--