Thanks Lorenzo. We got it working well.
", "time": "2025-07-24T10:01:30Z"}, {"author": "Lorenzo Miniero", "text": "Bravo Murillo! :clap:
", "time": "2025-07-24T10:01:53Z"}, {"author": "Sean Turner", "text": "Here's the PR we are discussing: https://github.com/wish-wg/webrtc-http-egress-protocol/pull/31/files
", "time": "2025-07-24T10:07:41Z"}, {"author": "Lorenzo Miniero", "text": "IIRC the outcome of the discussion at the time was that, ensuring clients supported both modes would ensure we wouldn't get in places where you could not get a WHEP session at all because each only implemented the other mode
", "time": "2025-07-24T10:10:00Z"}, {"author": "Lorenzo Miniero", "text": "I did read the draft and provide some feedback to Dan already
", "time": "2025-07-24T10:17:26Z"}, {"author": "Lorenzo Miniero", "text": "Discoverability might be nice to have, especially if we'll have HTTP people to look at it
", "time": "2025-07-24T10:19:00Z"}, {"author": "Lorenzo Miniero", "text": "I think Sergio wants this to pre-create WHEP endpoints before there's a publisher, and so you don't know in advance which codec will be used
", "time": "2025-07-24T10:21:34Z"}, {"author": "Mike Bishop", "text": "300 (Multiple Choices) might also be an option for the previous conversation.
", "time": "2025-07-24T10:21:38Z"}, {"author": "Lorenzo Miniero", "text": "Which is why he also preferred client offers, as the server could respond with all codecs
", "time": "2025-07-24T10:22:09Z"}, {"author": "Jonathan Lennox", "text": "Mike: there aren't multiple choices, it's an alternative to what the client offered.
", "time": "2025-07-24T10:24:47Z"}, {"author": "Jonathan Lennox", "text": "Is putting Expires on a 3xx weird?
", "time": "2025-07-24T10:24:52Z"}, {"author": "Mike Bishop", "text": "Well, the choices are what the client offered or what the server is counter-offering. But I guess that depends whether the server is willing to move forward with the client's original offer if requested, and I don't have that context.
", "time": "2025-07-24T10:26:01Z"}, {"author": "Jonathan Lennox", "text": "No, the reason the server does this response is that it's not willing to go with the client's offer
", "time": "2025-07-24T10:26:26Z"}, {"author": "Mike Bishop", "text": "Ah, okay.
", "time": "2025-07-24T10:26:48Z"}, {"author": "Mike English", "text": "Adding a JSON manifest layer for discovery seems like a fair bit more scope to take on
", "time": "2025-07-24T10:29:57Z"}, {"author": "Mike English", "text": "Not saying it might not be useful, but it might be a lot for this WG to take on
", "time": "2025-07-24T10:30:29Z"}, {"author": "Mike Bishop", "text": "@Jonathan, Expires is quasi-required on 304, but otherwise 3XX is mostly not discussed by RFC9111 beyond to say that redirects can be cached.
", "time": "2025-07-24T10:31:21Z"}, {"author": "Mike English", "text": "The draft deadline cut-off date for IETF 124 is 2025-10-20
", "time": "2025-07-24T10:34:43Z"}, {"author": "Dan Jenkins", "text": "thanks everyone
", "time": "2025-07-24T10:37:00Z"}, {"author": "Mike English", "text": "Thanks for keeping things moving, Dan!
", "time": "2025-07-24T10:37:56Z"}]