Dear colleagues, the meeting minutes are collected here: https://notes.ietf.org/notes-ietf-124-nmop#. Please contribute and review.
", "time": "2025-11-03T19:31:45.000Z"}, {"author": "Holger Keller", "text": "Stream catalog vs. Data catalog/DT calls it data catalog, streaming is Not yet \u201eimpmemented\u201c everywhere
", "time": "2025-11-03T19:44:20.000Z"}, {"author": "Beno\u00eet Claise", "text": "Holger: \"data catalog\" made me think of the YANG catalog
", "time": "2025-11-03T19:45:19.000Z"}, {"author": "Mahesh Jethanandani", "text": "I would agree with Rob that it should be Standards Track.
", "time": "2025-11-03T19:56:30.000Z"}, {"author": "Robert Wilton", "text": "standards track because it is effectively defining an API (the sx:structure message) between two separate devices.
", "time": "2025-11-03T19:57:15.000Z"}, {"author": "Mahesh Jethanandani", "text": "Just want to make sure that the SIMAP side meeting is not covering any WG-related work.
", "time": "2025-11-03T20:21:26.000Z"}, {"author": "Reshad Rahman", "text": "My recollection is that it's for draft-havel-nmop-simap-yang i..e not a WG document yet
", "time": "2025-11-03T20:23:43.000Z"}, {"author": "Mahesh Jethanandani", "text": "Ok.
", "time": "2025-11-03T20:29:08.000Z"}, {"author": "Camilo Cardona", "text": "@thomas, also since you have a length limitation, maybe add a determination function using hashing to generate it for paths that are longer.. you will hit that limitation, I promise
", "time": "2025-11-03T20:52:51.000Z"}, {"author": "Holger Keller", "text": "@camilo, yes, we already changed naming Convention because of that. Feels like dos-times
", "time": "2025-11-03T20:55:24.000Z"}, {"author": "Camilo Cardona", "text": "Thanks @holger! :+1:
", "time": "2025-11-03T20:58:14.000Z"}, {"author": "Thomas Graf", "text": "@camilo and holger, we already discussed this and have raised an issue to be investigated: https://github.com/network-analytics/draft-netana-nmop-yang-message-broker-message-key/issues/2. In the document we used a conservative length and the hashing as solution is already on our minds. We intend to propose solutions in the next document version.
", "time": "2025-11-03T21:03:12.000Z"}, {"author": "Holger Keller", "text": ":+1:
", "time": "2025-11-03T21:03:36.000Z"}, {"author": "Adrian Farrel", "text": "Someone needs to ask ChatGPT where we should do the AI work
", "time": "2025-11-03T21:06:03.000Z"}, {"author": "Boris Khasanov", "text": "@Benoit - great comment!
", "time": "2025-11-03T21:06:55.000Z"}, {"author": "Omar Sultan", "text": "+1 on over-rotating on \u201cclosed loop\u201d
", "time": "2025-11-03T21:08:34.000Z"}]