[{"author": "Scott Mansfield", "text": "sheesh...&nbsp;&nbsp;sorry.&nbsp;&nbsp;Having mic trouble again<br/>", "time": "2022-03-22T09:06:22Z"}, {"author": "Kent Watsen", "text": "bluetooth?<br/>", "time": "2022-03-22T09:06:55Z"}, {"author": "Scott Mansfield", "text": "I just wanted to make sure that Lou said Don Fedyk.&nbsp;&nbsp;I am also willing to help, have Rob send an email.<br/>", "time": "2022-03-22T09:06:56Z"}, {"author": "Lou Berger", "text": "yes<br/>", "time": "2022-03-22T09:07:22Z"}, {"author": "Scott Mansfield", "text": "@kent.&nbsp;&nbsp;it is &amp;#*$ bluetooth.&nbsp;&nbsp;Moving to wired dirty-buds<br/>", "time": "2022-03-22T09:07:30Z"}, {"author": "Bal\u00e1zs Lengyel", "text": "speak up please<br/>", "time": "2022-03-22T09:39:13Z"}, {"author": "Scott Mansfield", "text": "I didn't hear Tom very well.&nbsp;&nbsp;Was the point about listing conformance as part of the package?<br/>", "time": "2022-03-22T09:40:31Z"}, {"author": "Scott Mansfield", "text": "Got it... thanks to the chairs for listening to the chat.&nbsp;&nbsp;I got Tom's point now<br/>", "time": "2022-03-22T09:43:57Z"}, {"author": "Qin Wu", "text": "I hear echo back in the meeting when remote participant presents<br/>", "time": "2022-03-22T10:18:46Z"}, {"author": "Kent Watsen", "text": "I hear it also<br/>", "time": "2022-03-22T10:19:00Z"}, {"author": "J\u00fcrgen Sch\u00f6nw\u00e4lder", "text": "I assume this is an open room mike.<br/>", "time": "2022-03-22T10:19:31Z"}, {"author": "Lou Berger", "text": "@meetecho - can anything be done about the (minor) echo <br/>", "time": "2022-03-22T10:19:54Z"}, {"author": "Jeffrey Haas", "text": "The chairs are unable to mute the room mics.&nbsp;&nbsp;Someone in the room could do so manually.<br/>", "time": "2022-03-22T10:20:02Z"}, {"author": "Charles Eckel", "text": "did that help? I moved a mic<br/>", "time": "2022-03-22T10:20:19Z"}, {"author": "Qin Wu", "text": "still exist<br/>", "time": "2022-03-22T10:20:35Z"}, {"author": "J\u00fcrgen Sch\u00f6nw\u00e4lder", "text": "No change here.<br/>", "time": "2022-03-22T10:20:36Z"}, {"author": "Meetecho", "text": "We already reduced the capture gain quite a lot: the room there is quite large, and there is a different mixer configuration than in other rooms. We'll address it in the break. Hopefully it shouldn't be too unbearable for now!<br/>", "time": "2022-03-22T10:20:40Z"}, {"author": "Lou Berger", "text": "we can manage -- thank you!<br/>", "time": "2022-03-22T10:21:02Z"}, {"author": "Jeffrey Haas", "text": "I can expand at mic, but BFD has had a similar issue for RFC 9127-bis.&nbsp;&nbsp;Trivial change, painful process<br/>", "time": "2022-03-22T10:52:30Z"}, {"author": "Jeffrey Haas", "text": "Given available time, chairs can let me know if you'd like me to share that comment.<br/>", "time": "2022-03-22T10:53:51Z"}, {"author": "Jeffrey Haas", "text": "<a href=\"https://datatracker.ietf.org/doc/html/draft-ietf-bfd-rfc9127-bis-02\" rel=\"nofollow\">https://datatracker.ietf.org/doc/html/draft-ietf-bfd-rfc9127-bis-02</a><br/>", "time": "2022-03-22T10:54:33Z"}, {"author": "Joel Jaeggli", "text": "can copy the coment to the minutes<br/>", "time": "2022-03-22T10:54:59Z"}, {"author": "Lou Berger", "text": "sorry missed this comment until now<br/>", "time": "2022-03-22T10:55:03Z"}, {"author": "Kent Watsen", "text": "@Jeff that goes to importance of the problem.&nbsp;&nbsp;But what is the proposal?<br/>", "time": "2022-03-22T10:55:06Z"}, {"author": "Jeffrey Haas", "text": "I see Mahesh is in queue and will likely make similar comment.<br/>", "time": "2022-03-22T10:55:07Z"}, {"author": "Jeffrey Haas", "text": "Kent: \"suck less?\"<br/>", "time": "2022-03-22T10:55:38Z"}, {"author": "Jeffrey Haas", "text": "Short form is process is too heavy weight.<br/>", "time": "2022-03-22T10:56:28Z"}, {"author": "Bal\u00e1zs Lengyel", "text": "I don't seem to be able to modify the notes, so here are some comments also stated in voice:System:Balazs: Other SDOs like 3GPP and O-RAN are using system-created data nodes. Their design depends <br/>on them in some cases. Clients are not allowed to create these list entries.<br/>Until now the system is allowed to modify the running configuration. <br/>If we would prohibit this that would be a major non-backwards-comptible change.<br/>I object to that. It would also need a YANG 2.0 revision.<br/>Even if we would prohibit the system to modify running, it would be possible <br/>to work around it. <br/>The system instantiates an onboard client to do the changes AND the system <br/>prohibits the change for other clients.<br/>However this is just a more complicated way of stating that the system itself<br/>modifies running; we gain nothing but make the world more complicated.<br/>While I agree that system-created data nodes can be problematic sometimes it <br/>is a fact of lie, so we should not remove it.<br/>Immutable:3 potential use-cases for immutable:<br/>- invariant: once a leaf is created it cannot be changed<br/>- capabilities that are created by the systems and client cannot modify them. <br/>Is this better served by immutable or system data?<br/>- Immutable NACM rules that must stay in place to protect some parts of the <br/>configuration from any modification<br/>", "time": "2022-03-22T11:02:24Z"}, {"author": "Mahesh Jethanandani", "text": "Take a look at this set of diffs for what we had to do to update the module - <a href=\"https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-rfc9127-bis-02.txt\" rel=\"nofollow\">https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-rfc9127-bis-02.txt</a><br/>", "time": "2022-03-22T11:02:49Z"}]