IETF MOQ WG: Thoughts on SWITCH
Martin Duke posted to the MOQ working group mailing list on May 26, 2026. Upon further reflection: In the upswitch case, make-before-break is one option; the other is to pick some future group and send the REQUEST_UPDAT…
Message Snapshot
- List:
moq@ietf.org - Thread subject: Thoughts on SWITCH
- Message subject: [Moq] Re: Thoughts on SWITCH
- Author: Martin Duke
- Published: 2026-05-26T18:08:54.000Z
- Source tag:
ietf-mailing-list - Message URL: Open in IETF Mail Archive
Summary
Martin Duke posted to the MOQ working group mailing list on May 26, 2026. Upon further reflection: In the upswitch case, make-before-break is one option; the other is to pick some future group and send the REQUEST_UPDAT…
Why It Matters
This message came from the public MOQ working group archive and captures active discussion, meeting coordination, or implementation feedback around Media over QUIC.
Message Excerpt
Upon further reflection: In the upswitch case, make-before-break is one option; the other is to pick some future group and send the REQUEST_UPDATE/SUBSCRIBE/Absolute Joining
Plain-Text Body
Upon further reflection:
In the upswitch case, make-before-break is one option; the other is to pick some future group and send the REQUEST_UPDATE/SUBSCRIBE/Absolute Joining FETCH trio for that future group. The consequences would be a couple of groups at less-than-possible bandwidth but would avoid any duplicates.
On Tue, May 26, 2026 at 10:33 AM Martin Duke martin.h.duke@gmail.com wrote: