[{"author": "Will Law", "text": "

Impressive mascot commitment by the chairs.

", "time": "2025-11-06T14:31:49.000Z"}, {"author": "Alan Frindell", "text": "

#notachair

", "time": "2025-11-06T14:32:11.000Z"}, {"author": "Martin Duke", "text": "

@meetecho can we get the speaker video feed?

", "time": "2025-11-06T14:34:04.000Z"}, {"author": "Martin Duke", "text": "

thanks

", "time": "2025-11-06T14:35:15.000Z"}, {"author": "Alejandro Sede\u00f1o", "text": "

Also, slides are not visible on the lite client.

", "time": "2025-11-06T14:35:19.000Z"}, {"author": "Ali Begen", "text": "

yeah I had to switch to the full client.

", "time": "2025-11-06T14:36:21.000Z"}, {"author": "Jonathan Lennox", "text": "

I believe it's a screenshare not a slide deck; the lite client doesn't show screenshares

", "time": "2025-11-06T14:36:34.000Z"}, {"author": "Ted Hardie", "text": "

Is that a 3 pt font?

", "time": "2025-11-06T14:37:32.000Z"}, {"author": "Alejandro Sede\u00f1o", "text": "

That's unfortunate. I find things easier to read on my own display.

", "time": "2025-11-06T14:37:56.000Z"}, {"author": "Will Law", "text": "

JS to Webex - nice. Pandora wants her box back ..

", "time": "2025-11-06T14:39:39.000Z"}, {"author": "Mike English", "text": "

Sorry, I did also upload a copy of the slides. I'll ask the chairs to make sure those are available so people can read the small text.

", "time": "2025-11-06T14:43:45.000Z"}, {"author": "Jonathan Lennox", "text": "

I see them in the datatracker now, but I didn't when the presentation started

", "time": "2025-11-06T14:44:09.000Z"}, {"author": "Victor Vasiliev", "text": "

I don't think this works

", "time": "2025-11-06T14:44:48.000Z"}, {"author": "Victor Vasiliev", "text": "

moqt:// implies raw QUIC

", "time": "2025-11-06T14:44:59.000Z"}, {"author": "Mike English", "text": "

^

", "time": "2025-11-06T14:45:04.000Z"}, {"author": "Mike English", "text": "

Agree - this should be a WARP-specific scheme

", "time": "2025-11-06T14:45:20.000Z"}, {"author": "Victor Vasiliev", "text": "

I think the fragment would work too, but that's the general problem here (attempting to reuse things that already have meaning)

", "time": "2025-11-06T14:46:04.000Z"}, {"author": "Cullen Jennings", "text": "

+1 on update charter

", "time": "2025-11-06T14:50:55.000Z"}, {"author": "Victor Vasiliev", "text": "

I think our charter was good and we have in generally erred too much in deviating from the scope outlined in it

", "time": "2025-11-06T14:51:09.000Z"}, {"author": "Chris Lemmons", "text": "

I am disappointed in the performance of the \"Media over MOQ\" name. :)

", "time": "2025-11-06T14:51:26.000Z"}, {"author": "Ali Begen", "text": "

egarding the name, I prefer MOQ Streaming Format, only because it is simpler to say it

", "time": "2025-11-06T14:51:36.000Z"}, {"author": "Alan Frindell", "text": "

+1 Ali

", "time": "2025-11-06T14:51:46.000Z"}, {"author": "Mike English", "text": "

#momjoke

", "time": "2025-11-06T14:51:51.000Z"}, {"author": "Alan Frindell", "text": "

MOQT is inside baseball

", "time": "2025-11-06T14:51:51.000Z"}, {"author": "Ali Begen", "text": "

I can live with \"MSF\" and I like it.

", "time": "2025-11-06T14:52:14.000Z"}, {"author": "Jonathan Lennox", "text": "

M\u00e9decins Sans Fronti\u00e8res

", "time": "2025-11-06T14:52:19.000Z"}, {"author": "Chris Lemmons", "text": "

Heh, I'm not actually trying to take time on the bikeshed. It's fine. :)

", "time": "2025-11-06T14:52:25.000Z"}, {"author": "Ai Luo", "text": "

Are there timeline tracks for both video an d audio? Or just one timeline track?

", "time": "2025-11-06T14:53:28.000Z"}, {"author": "Ali Begen", "text": "

One

", "time": "2025-11-06T14:53:57.000Z"}, {"author": "Ted Hardie", "text": "

Just make MoQ not stand for anything, then you can have MMSF or whatever without impacting the ability to have other kinds of streams. As we mentioned yesterday, you could use MoQ as a substrate to the AT protocol \"firehose\". (That would be an event stream, not a media stream. )

", "time": "2025-11-06T14:54:00.000Z"}, {"author": "Rohan Mahy", "text": "

Ted Hardie said:

\n
\n

Just make MoQ not stand for anything, then you can have MMSF or whatever without impacting the ability to have other kinds of streams. As we mentioned yesterday, you could use MoQ as a substrate to the AT protocol \"firehose\". (That would be an event stream, not a media stream. )

\n
\n

Yes. Keep the brand, ignore the original meeting.

", "time": "2025-11-06T14:54:59.000Z"}, {"author": "Rohan Mahy", "text": "

Hi Everyone, Welcome to the Brand Engineering Task Force

", "time": "2025-11-06T14:55:12.000Z"}, {"author": "Jonathan Lennox", "text": "

Engineers naming things, always works out well

", "time": "2025-11-06T14:55:41.000Z"}, {"author": "Victor Vasiliev", "text": "

If we can name our format after a fish, we can name it after a chemical reaction

", "time": "2025-11-06T14:55:43.000Z"}, {"author": "Ali Begen", "text": "

My vote is on CMSF as it is similar to CMAF.

", "time": "2025-11-06T14:56:04.000Z"}, {"author": "Mike English", "text": "

Fire :fire: with the emoji, specifically? Can we put that in logs?

", "time": "2025-11-06T14:56:11.000Z"}, {"author": "Spencer Dawkins", "text": "

Nobody cares about the color of a bike shed until you set it on fire ...

", "time": "2025-11-06T14:56:27.000Z"}, {"author": "altanai", "text": "

CMSF isnt catchy enough .. my vote for Fire

", "time": "2025-11-06T14:56:36.000Z"}, {"author": "Alan Frindell", "text": "

Wow MSF vs Fire. Tell me which child you like best.

", "time": "2025-11-06T14:56:36.000Z"}, {"author": "Chris Lemmons", "text": "

Fire is significantly more... well... fire.

", "time": "2025-11-06T14:57:02.000Z"}, {"author": "GUPTA Manu", "text": "

Is there a github link for moqtest?

", "time": "2025-11-06T15:00:58.000Z"}, {"author": "Ted Hardie", "text": "

Now use your favorite search engine to find information about one or the other....

", "time": "2025-11-06T15:00:58.000Z"}, {"author": "Jonathan Lennox", "text": "

MSF also primarily finds things other than streaming formats

", "time": "2025-11-06T15:02:03.000Z"}, {"author": "Rohan Mahy", "text": "

If you google MSF, you will get a humanitarian org that I happen to be fond of. Might be hard to find what you are looking for unless you add moq or media

", "time": "2025-11-06T15:02:55.000Z"}, {"author": "Will Law", "text": "

Any 3-letter acronym we choose will have conflicts. We're not looking for a unique combination, just one where clarity is preserved. The context for MSF would probably make it clear if we are referring to
\nM\u00e9decins Sans Fronti\u00e8res or a streaming format.

", "time": "2025-11-06T15:05:40.000Z"}, {"author": "Ali Begen", "text": "

Agreed

", "time": "2025-11-06T15:07:22.000Z"}, {"author": "Victor Vasiliev", "text": "

Are \"private extensions\" just MOQT extensions that application chose to encrypt?

", "time": "2025-11-06T15:09:38.000Z"}, {"author": "Will Law", "text": "

No, we don;t need to wait for the whole payload. You can encrypt progressively.

", "time": "2025-11-06T15:13:30.000Z"}, {"author": "Alan Frindell", "text": "

i think they are key/value pairs, but the type space is entirely application specific, since the relay never sees the code points

", "time": "2025-11-06T15:13:31.000Z"}, {"author": "Jonathan Lennox", "text": "

Are you encrypting per-GOP or per-object?

", "time": "2025-11-06T15:13:54.000Z"}, {"author": "Magnus Westerlund", "text": "

Per object

", "time": "2025-11-06T15:14:39.000Z"}, {"author": "Jonathan Lennox", "text": "

Then I'm confused by the last question

", "time": "2025-11-06T15:14:59.000Z"}, {"author": "Magnus Westerlund", "text": "

is my understanding. So I don't think the delay is that problematic.

", "time": "2025-11-06T15:15:02.000Z"}, {"author": "Alan Frindell", "text": "

Or people should read and review the draft, file issues and work through them asynchronously :)

", "time": "2025-11-06T15:15:57.000Z"}, {"author": "Alan Frindell", "text": "

Wait can't you do that with Prior Object ID Gap extension?

", "time": "2025-11-06T15:16:44.000Z"}, {"author": "Jordi Cenzano", "text": "

IMHO it makes a lot of sense to put whole GOP in a group. Since the B P frames does NOT makes sense without the I

\n

And if I'm NOT mistaken is what WARP is doing (or the initial implementation of it)

", "time": "2025-11-06T15:16:57.000Z"}, {"author": "Magnus Westerlund", "text": "

I think putting the whole GOP in one SFRAME do have a number of trade-offs. This is maybe something that needs more discussion. For one thing it will make the whole truncation at the end of a group fail if you have insufficinet transmission capacity.

", "time": "2025-11-06T15:19:58.000Z"}, {"author": "Magnus Westerlund", "text": "

However, I think this comes down to how ones streaming format functions and if it will work well or not.

", "time": "2025-11-06T15:21:44.000Z"}, {"author": "Alan Frindell", "text": "

I vibe coded an mlog visualizer. It's sort of half-done but it's in the moxygen repo

", "time": "2025-11-06T15:22:15.000Z"}, {"author": "Phillip Hallam-Baker", "text": "

JSON streaming is really inefficient if you want to move backwards

", "time": "2025-11-06T15:28:53.000Z"}, {"author": "Phillip Hallam-Baker", "text": "

Much better way is to start and end the frame with a VARINT with a lngth indicator

", "time": "2025-11-06T15:29:17.000Z"}, {"author": "Phillip Hallam-Baker", "text": "

You write the last varint in reverse.

", "time": "2025-11-06T15:29:28.000Z"}, {"author": "Mike English", "text": "

I can do it

", "time": "2025-11-06T15:31:29.000Z"}, {"author": "Aman Sharma", "text": "

I could also work on keeping mLog up to date with MoQ.

", "time": "2025-11-06T15:31:58.000Z"}, {"author": "Alan Frindell", "text": "

THANK YOU

", "time": "2025-11-06T15:32:08.000Z"}, {"author": "Phillip Hallam-Baker", "text": "

I can work on it

", "time": "2025-11-06T15:32:08.000Z"}, {"author": "Victor Vasiliev", "text": "

I support the adoption for sure (I have an implementation-specific format, so I can't really use it though)

", "time": "2025-11-06T15:32:19.000Z"}, {"author": "Phillip Hallam-Baker", "text": "

I have a similar draft proposed to JOSE

", "time": "2025-11-06T15:32:20.000Z"}, {"author": "Lucas Pardue", "text": "

Just in case it wasn't clear. I do want to be actively involved in the draft, I just lack the cycles to attend all interims etc. Someone thst can do that would be a great help

", "time": "2025-11-06T15:33:45.000Z"}, {"author": "Aman Sharma", "text": "

I've submitted a bunch of PRs in the past to keep mLog up to date with draft-14, can continue to do so for subsequent drafts.

", "time": "2025-11-06T15:35:00.000Z"}, {"author": "Lucas Pardue", "text": "

Thank you very much Aman, it's been great

", "time": "2025-11-06T15:35:38.000Z"}, {"author": "Aman Sharma", "text": "

Not a problem!

", "time": "2025-11-06T15:35:45.000Z"}, {"author": "Ted Hardie", "text": "

His answer makes me think that shifting the name of one of property or parameter would be useful in making the doc easier to write and then read.

", "time": "2025-11-06T15:41:42.000Z"}, {"author": "Ted Hardie", "text": "

To me, the version indicates what parameters might be negotiated, but which ones are negotiated is done at setup.

", "time": "2025-11-06T15:44:19.000Z"}, {"author": "Alan Frindell", "text": "

Ted I'm not sure I've got your write vs read comment - what should we do to optimize readability

", "time": "2025-11-06T15:45:03.000Z"}, {"author": "Will Law", "text": "

We don't negotiate HTTP headers at request time., only the version. I see parallels here.

", "time": "2025-11-06T15:45:06.000Z"}, {"author": "Alan Frindell", "text": "

Should we also clarify that subscribers cannot specify properties -- only parameters

", "time": "2025-11-06T15:45:59.000Z"}, {"author": "Ted Hardie", "text": "

@Alan his previous slide on having one of them not start with P will make it clearer if we have folks drop down to acronyms to reference these. But it can be made readable either way.

", "time": "2025-11-06T15:46:14.000Z"}, {"author": "Ted Hardie", "text": "

@chairs please remind folks we have remote participants and that comments need to go to the mic, even if they sound trivial to the speaker.

", "time": "2025-11-06T15:50:26.000Z"}, {"author": "Martin Duke", "text": "

one weird thing here is that PUBLISH_NAMESPACE is sometimes a request and sometimes a response

", "time": "2025-11-06T15:55:10.000Z"}, {"author": "Martin Duke", "text": "

as is PUBLISH

", "time": "2025-11-06T15:55:13.000Z"}, {"author": "Alan Frindell", "text": "

it's not a response after the SUBSCRIBE_NAMESPACE PR

", "time": "2025-11-06T15:56:55.000Z"}, {"author": "Alan Frindell", "text": "

https://github.com/moq-wg/moq-transport/pull/1344

", "time": "2025-11-06T15:58:58.000Z"}, {"author": "Alan Frindell", "text": "

+1 Victor

", "time": "2025-11-06T15:59:58.000Z"}, {"author": "Alan Frindell", "text": "

1344 needs to happen to resolve a bunch of issues, the other messages might be optional

", "time": "2025-11-06T16:01:12.000Z"}, {"author": "Martin Duke", "text": "

I am a little sad that we could abolish REQUEST_ERROR and use RESET_STREAM, but we have the retry interval thing

", "time": "2025-11-06T16:01:59.000Z"}, {"author": "Alan Frindell", "text": "

oof, that's a good point

", "time": "2025-11-06T16:02:20.000Z"}, {"author": "Alan Frindell", "text": "

I think you can still send REQUEST_ERROR on response bidi stream

", "time": "2025-11-06T16:02:55.000Z"}, {"author": "Alan Frindell", "text": "

initially

", "time": "2025-11-06T16:02:59.000Z"}, {"author": "Martin Duke", "text": "

yes, but that makes me sad

", "time": "2025-11-06T16:03:44.000Z"}]