[{"author": "Sean Turner", "text": "

Hi... Currently in DISPATCH. Plan to run over about 1130. If the sessions is going quicker than planned please let me know so I sprint down to the do that lest presentation

", "time": "2022-07-25T14:00:13Z"}, {"author": "Kent Watsen", "text": "

ok sean

", "time": "2022-07-25T14:00:44Z"}, {"author": "Kent Watsen", "text": "

meetecho - we need in-room help

", "time": "2022-07-25T14:01:36Z"}, {"author": "Jeffrey Haas", "text": "

I think we've resolved the issues, so don't need meetecho?

", "time": "2022-07-25T14:03:13Z"}, {"author": "Kent Watsen", "text": "

Alex Feng - are you in-person or remote?

", "time": "2022-07-25T14:06:36Z"}, {"author": "Alex Huang Feng", "text": "

I am in person Kent

", "time": "2022-07-25T14:08:41Z"}, {"author": "Thomas Graf", "text": "

Alex and me are in person

", "time": "2022-07-25T14:09:21Z"}, {"author": "Kent Watsen", "text": "

I cannot hear alex

", "time": "2022-07-25T14:09:56Z"}, {"author": "Kent Watsen", "text": "

got it

", "time": "2022-07-25T14:10:10Z"}, {"author": "Robert Wilton", "text": "

If anyone can help take/correct notes at https://notes.ietf.org/notes-ietf-114-netconf?both that would be helpful.

", "time": "2022-07-25T14:25:31Z"}, {"author": "Kent Watsen", "text": "

Sean, we're about 25 mins from your preso

", "time": "2022-07-25T14:43:53Z"}, {"author": "Sean Turner", "text": "

excellent!

", "time": "2022-07-25T14:44:50Z"}, {"author": "Sean Turner", "text": "

I will plan to be there at the top of the hour

", "time": "2022-07-25T14:46:46Z"}, {"author": "Kent Watsen", "text": "

Seam, we're ~15 min from your preso

", "time": "2022-07-25T15:03:19Z"}, {"author": "Kent Watsen", "text": "

s/Seam/Sean/

", "time": "2022-07-25T15:03:54Z"}, {"author": "Kent Watsen", "text": "

Sean, your preso is imminent

", "time": "2022-07-25T15:14:07Z"}, {"author": "Jeffrey Haas", "text": "

slides must be from a parallel timeline.

", "time": "2022-07-25T15:26:35Z"}, {"author": "Mahesh Jethanandani", "text": "

https://github.com/netconf-wg/netconf-next/issues

", "time": "2022-07-25T15:26:44Z"}, {"author": "Mahesh Jethanandani", "text": "

Issues related to NETCONF-next and RESTCONF-next

", "time": "2022-07-25T15:27:44Z"}, {"author": "Kent Watsen", "text": "

https://github.com/netconf-wg/restconf-next/issues

", "time": "2022-07-25T15:31:18Z"}, {"author": "Kent Watsen", "text": "

https://github.com/netmod-wg/yang-next/issues

", "time": "2022-07-25T15:31:35Z"}, {"author": "Beno\u00eet Claise", "text": "

+1 to binary notif. This is the primary use case.

", "time": "2022-07-25T15:37:48Z"}, {"author": "Jeffrey Haas", "text": "

Density of information is the use case IMO

", "time": "2022-07-25T15:38:10Z"}, {"author": "Jan Lindblad", "text": "

Rob can answer

", "time": "2022-07-25T15:39:45Z"}, {"author": "Jeffrey Haas", "text": "

xpath filtering as it'd change for binary format is a large part of the protocol headache.

", "time": "2022-07-25T15:42:40Z"}, {"author": "Jan Lindblad", "text": "

There are currently three mechanisms defined for clients to figure out which modules a server supports. The YANG versioning work is adding a fourth. Draft draft-claise-opsawg-collected-data-manifest is proposing a fifth..

", "time": "2022-07-25T15:43:10Z"}, {"author": "Jan Lindblad", "text": "

I think a couple of the next issues might be worth working on. Is that yes or no?

", "time": "2022-07-25T15:43:57Z"}, {"author": "Jan Lindblad", "text": "

Maybe a poll for the individual proposals might be more interesting that a yes/no global answer?

", "time": "2022-07-25T15:44:25Z"}, {"author": "Jan Lindblad", "text": "

I was one of the people who did \"not raise hand\". It was an attempt at communicating that I think we should not do most of those things.

", "time": "2022-07-25T15:46:28Z"}]