[{"author": "Yingzhen Qu", "text": "

Hi, please help with the joint note taking: https://notes.ietf.org/notes-ietf-118-lsr

", "time": "2023-11-06T08:30:17Z"}, {"author": "Les Ginsberg", "text": "

Some folks are reporting audio only access is not working.

", "time": "2023-11-06T08:31:38Z"}, {"author": "Henk Smit", "text": "

Hi. I'm trying to listen in via the audio-only (free) option.
\nIt doesn't seem to work. I download the .m3u file, it starts VLC, but VLC can't connect.
\nIs the audio-only stream supposed to work? TIA.

", "time": "2023-11-06T08:32:25Z"}, {"author": "Lorenzo Miniero", "text": "

Les: checking, thanks for the heads up!

", "time": "2023-11-06T08:32:51Z"}, {"author": "Sasha Vainshtein", "text": "

Voice quality is very poor. Can something be done about that?

", "time": "2023-11-06T08:39:07Z"}, {"author": "Sasha Vainshtein", "text": "

I am watching via the full client, video stream is OK, but audio is not:wink:

", "time": "2023-11-06T08:40:23Z"}, {"author": "Henk Smit", "text": "

Audio-only works now. Just very low volume.

", "time": "2023-11-06T08:40:34Z"}, {"author": "Daniam Henriques", "text": "

@Sasha, switching to the old client resolved the audio issues for me

", "time": "2023-11-06T08:42:21Z"}, {"author": "Sasha Vainshtein", "text": "

How do I do that?

", "time": "2023-11-06T08:43:45Z"}, {"author": "Daniam Henriques", "text": "

Click three dots on the bottom, click switch to old client

", "time": "2023-11-06T08:45:19Z"}, {"author": "Sasha Vainshtein", "text": "

Tried that, no difference:face_with_raised_eyebrow:

", "time": "2023-11-06T08:46:02Z"}, {"author": "Sasha Vainshtein", "text": "

May I ask the presenters and the speakers at the mike to speak louder?

", "time": "2023-11-06T08:47:05Z"}, {"author": "Lou Berger", "text": "

Les is really loud for me

", "time": "2023-11-06T08:47:24Z"}, {"author": "Boris Khasanov", "text": "

indeed

", "time": "2023-11-06T08:47:41Z"}, {"author": "Christian Hopps", "text": "

he sounds great in the room

", "time": "2023-11-06T08:48:00Z"}, {"author": "Lou Berger", "text": "

Chairs mic seems low

", "time": "2023-11-06T08:48:18Z"}, {"author": "Lou Berger", "text": "

but workable

", "time": "2023-11-06T08:48:36Z"}, {"author": "Christian Hopps", "text": "

@meetecho I do not have a button next to the participant to hand them control

", "time": "2023-11-06T08:50:43Z"}, {"author": "Loa Andersson", "text": "

the speaker mike is faint, but I hear Les fine

", "time": "2023-11-06T08:50:45Z"}, {"author": "Lorenzo Miniero", "text": "

Christian: you need to click on their avatar, the controls will appear below them

", "time": "2023-11-06T08:51:19Z"}, {"author": "Lorenzo Miniero", "text": "

The document with the plus icon is the one to hand them control

", "time": "2023-11-06T08:51:35Z"}, {"author": "Lorenzo Miniero", "text": "

(the avatar in the participants list I mean)

", "time": "2023-11-06T08:51:49Z"}, {"author": "Nitsan Dolev Elfassy", "text": "

The specific microphone for commenters is hardly audible

", "time": "2023-11-06T09:02:30Z"}, {"author": "Tony Li", "text": "

Can we please replace 'PICS' with an IETF term?

", "time": "2023-11-06T09:04:20Z"}, {"author": "Les Ginsberg", "text": "

Fine with me - open to suggestion.

", "time": "2023-11-06T09:04:40Z"}, {"author": "Christian Hopps", "text": "

@lorenzo thanks i will try that

", "time": "2023-11-06T09:05:23Z"}, {"author": "Tony Li", "text": "

How about 'support'?

", "time": "2023-11-06T09:05:24Z"}, {"author": "Les Ginsberg", "text": "

As in \"IS-IS Support\"?

", "time": "2023-11-06T09:05:56Z"}, {"author": "Tony Li", "text": "

Yah

", "time": "2023-11-06T09:06:05Z"}, {"author": "Les Ginsberg", "text": "

Something like that seems fine.

", "time": "2023-11-06T09:06:17Z"}, {"author": "Christian Hopps", "text": "

isn't this useful for OSPF too?

", "time": "2023-11-06T09:06:37Z"}, {"author": "Les Ginsberg", "text": "

Could be - in which case you would have \"OSPF-Support\" module.

", "time": "2023-11-06T09:07:03Z"}, {"author": "Les Ginsberg", "text": "

Different modules.

", "time": "2023-11-06T09:07:19Z"}, {"author": "Christian Hopps", "text": "

I'm going to ponder the color of this shed and get back to the list later :-D

", "time": "2023-11-06T09:09:04Z"}, {"author": "Louis Chan", "text": "

But this pics model does not ensure interop

", "time": "2023-11-06T09:13:15Z"}, {"author": "Tony Li", "text": "

Nothing ensures interop except testing

", "time": "2023-11-06T09:14:03Z"}, {"author": "Les Ginsberg", "text": "

+1

", "time": "2023-11-06T09:14:13Z"}, {"author": "Louis Chan", "text": "

exactly...so the usability is less than expect4ed

", "time": "2023-11-06T09:14:30Z"}, {"author": "Tony Li", "text": "

? What is expected is exactly what is advertised: the ability to get supported features out of the management plane.

", "time": "2023-11-06T09:15:14Z"}, {"author": "Les Ginsberg", "text": "

It is not intended to \"guarantee interoperability\". It is to provide the operator with the info needed to know whether all routers in the network support a given feature. It does not replace interoperability testing.

", "time": "2023-11-06T09:15:34Z"}, {"author": "Sasha Vainshtein", "text": "

+1.

", "time": "2023-11-06T09:15:56Z"}, {"author": "Tony Li", "text": "

+1

", "time": "2023-11-06T09:16:13Z"}, {"author": "Robert Raszuk", "text": "

Is the definition of \"supported\" == enabled here or just there is code on the box which if enabled will support feature xyz ?

", "time": "2023-11-06T09:17:21Z"}, {"author": "Sasha Vainshtein", "text": "

The underlying assumption is that the vendor adding a new feature will also advertise its support.

", "time": "2023-11-06T09:17:42Z"}, {"author": "Louis Chan", "text": "

Even it the operator what is in the network, he can't run it without full testing with different versions of sw and different vendors...for RFP purpose, that might sound...but not useful for continual deployment scenario

", "time": "2023-11-06T09:17:57Z"}, {"author": "Christian Hopps", "text": "

@robert: the latter

", "time": "2023-11-06T09:18:05Z"}, {"author": "Les Ginsberg", "text": "

AS stated, protocol does not need to be configured to obtain the information - whether it is enabled isn't rtelevant here.

", "time": "2023-11-06T09:18:29Z"}, {"author": "Robert Raszuk", "text": "

Thx Chris, But this may be a bit tricky as feature X even if supported may require features Y & Z to actually run ... often Y & Z may be coming from outside of ISIS/OSPF too.

", "time": "2023-11-06T09:19:14Z"}, {"author": "Sasha Vainshtein", "text": "

@robert: If a supported feature has to be enabled, there should be a R/W knob to do that via YANG.

", "time": "2023-11-06T09:22:10Z"}, {"author": "Louis Chan", "text": "

In fact, it does not require to implement on a node. Just implement from a company web site perspective, keys to lookup are model#, sw version and license keys. same result.

", "time": "2023-11-06T09:24:08Z"}, {"author": "Robert Raszuk", "text": "

@Louis - pretty good point. In fact if you have modular software and download only features of the protocol which you actually need how useful this will be ?

", "time": "2023-11-06T09:26:01Z"}, {"author": "Tony Li", "text": "

Still useful. There are points within each feature that you would need.

", "time": "2023-11-06T09:26:52Z"}, {"author": "Tony Li", "text": "

See all of the attributes within the SR support container.

", "time": "2023-11-06T09:27:11Z"}, {"author": "Yingzhen Qu", "text": "

agreed with Tony, the RFC level module has more details than just saying \"I support RFC 8667\"

", "time": "2023-11-06T09:30:00Z"}, {"author": "Louis Chan", "text": "

Still useful...use cost vs benefit...vs simply workaround

", "time": "2023-11-06T09:30:00Z"}, {"author": "Louis Chan", "text": "

just cost vs benefit...typo

", "time": "2023-11-06T09:30:25Z"}, {"author": "Tony Li", "text": "

Orthogonal question: should anything within the support YANG tree be \"rw\"?

", "time": "2023-11-06T09:31:18Z"}, {"author": "Yingzhen Qu", "text": "

It should be \"read-only\" since it's OPS state.

", "time": "2023-11-06T09:32:02Z"}, {"author": "Tony Li", "text": "

That would seem more appropriate to me...

", "time": "2023-11-06T09:32:34Z"}, {"author": "Yingzhen Qu", "text": "

will add \"config false\"

", "time": "2023-11-06T09:32:40Z"}, {"author": "Tony Li", "text": "

Thx!

", "time": "2023-11-06T09:33:09Z"}, {"author": "Boris Khasanov", "text": "

@meetecho Can you pls increase sound level of the queue mic ?

", "time": "2023-11-06T10:03:21Z"}, {"author": "John Scudder", "text": "

(Also reported mic level to secretariat OOB)

", "time": "2023-11-06T10:03:42Z"}, {"author": "Lorenzo Miniero", "text": "

The AV team is already aware

", "time": "2023-11-06T10:04:13Z"}, {"author": "Louis Chan", "text": "

Just converting link loss to different colour would be a simple workaround

", "time": "2023-11-06T10:07:10Z"}, {"author": "Tony Li", "text": "

Changing color would not fix the oscillation

", "time": "2023-11-06T10:07:42Z"}, {"author": "Louis Chan", "text": "

yes...need damping then.

", "time": "2023-11-06T10:08:05Z"}, {"author": "Louis Chan", "text": "

which is unavoidable

", "time": "2023-11-06T10:08:17Z"}, {"author": "Tony Li", "text": "

Damping only bounds the frequency of oscillation

", "time": "2023-11-06T10:08:42Z"}, {"author": "Louis Chan", "text": "

loss is also a function of time.

", "time": "2023-11-06T10:09:10Z"}, {"author": "Tony Li", "text": "

Not always... You can have a pattern sensitivity, for example.

", "time": "2023-11-06T10:10:06Z"}, {"author": "Louis Chan", "text": "

for wireless link, interference is unpredictable.

", "time": "2023-11-06T10:10:44Z"}, {"author": "Louis Chan", "text": "

so thus loss

", "time": "2023-11-06T10:11:04Z"}, {"author": "Tony Li", "text": "

Not everything in the world is a wireless link.

", "time": "2023-11-06T10:11:38Z"}, {"author": "Nitsan Dolev Elfassy", "text": "

In light of the variance of loss the solution seems non deterministic

", "time": "2023-11-06T10:13:10Z"}, {"author": "Tony Li", "text": "

Given the mess in IDR, would it be better to hold off on this until there is a CT/CAR resolution?

", "time": "2023-11-06T10:22:20Z"}, {"author": "Lou Berger", "text": "

mic worked fine

", "time": "2023-11-06T10:28:22Z"}, {"author": "Liyan Gong", "text": "

@Shraddha\uff0c

", "time": "2023-11-06T10:32:00Z"}, {"author": "Liyan Gong", "text": "

1.When will neighbor router add the lsa to the stale list ? the draft description is confusing. It seems that it describe two possible timings, but i think whatever the timing, it will result in the failure of the solution.appreciate if you could explain it in detailed.
\n1)After receving dd(self originated by sender but with lower sequence number): for the scenario 1(route delete, common scenarios of external routes) , neighbor router has no chance to add the las to the stale list.
\n2)When receiving request(self originated by requester), But the neighbor may have been in FULL state before then.

", "time": "2023-11-06T10:32:03Z"}]