[{"author": "Robert Wilton", "text": "<p>This is the link to the note taking tool if you wish to have it in a different window: <a href=\"https://notes.ietf.org/notes-ietf-interim-2024-netmod-02-netmod\">https://notes.ietf.org/notes-ietf-interim-2024-netmod-02-netmod</a></p>", "time": "2024-02-06T14:06:21Z"}, {"author": "Robert Wilton", "text": "<p>I agree with meta-data in general being in <a href=\"http://YANG.next\">YANG.next</a>, but I'm less convinced of whether the immutable flag should become part of <a href=\"http://YANG.next\">YANG.next</a>, or just been kept separate.</p>", "time": "2024-02-06T14:38:03Z"}, {"author": "Jason Sterne", "text": "<p>From the draf: When the \"immutable\" YANG metadata annotation is used on all existing leaf-list instances, or if a leaf-list inherits immutability from an ancestor, it means that the leaf-list as a whole cannot change: entries cannot be added, removed, or reordered, in case the leaf-list is \"ordered-by user\".</p>", "time": "2024-02-06T14:57:19Z"}, {"author": "Robert Wilton", "text": "<p>You could potentially use two separate attributes.</p>", "time": "2024-02-06T14:59:55Z"}, {"author": "Robert Wilton", "text": "<p>+1 to Jason that the current attribute might be good enough.</p>", "time": "2024-02-06T15:00:32Z"}, {"author": "Robert Wilton", "text": "<p>It was Scott Mansfield who originally raised the issue, so we could ask him for the details of the particular problem case.  But their case was NACM.</p>", "time": "2024-02-06T15:02:57Z"}, {"author": "Robert Wilton", "text": "<p>They could represent it, but it just required a very convoluted policy.</p>", "time": "2024-02-06T15:03:15Z"}, {"author": "Kent Watsen", "text": "<p>Server \"MAY reject\" sounds right to me.  </p>\n<p>Specific server-behavior could be captured by capabilities...</p>", "time": "2024-02-06T15:37:27Z"}]