MOQ agenda highlights Required Request ID, MAX_REQUEST_UPDATES, and DELIVERY_TIMEOUT

Thread Snapshot

• List: moq@ietf.org
• Root subject: Monday's agenda is ready
• Representative message: [Moq] Re: Monday's agenda is ready
• Thread root: [Moq] Monday's agenda is ready
• Messages fetched in thread: 2
• Published: 2026-04-25
• Source: IETF Mailing List

Summary

Alan Frindell flagged Required Request ID, MAX_REQUEST_UPDATES, and DELIVERY_TIMEOUT in the latest MOQ meeting agenda and slide update. The slides are posted here: We're still waiting on some content so look for an upda…

Why It Matters

Agenda mail is a strong signal of where editor and chair attention is going next. This thread points implementers toward Required Request ID, MAX_REQUEST_UPDATES, and DELIVERY_TIMEOUT, which can affect request handling, timeout behavior, or other core transport semantics.

Notable Details

• #1608 Make Subgroup ID identical to first Object Id in the Subgroup
• #1519/#1603 Required Request ID
• #1613 Add MAX_REQUEST_UPDATES setup option and TOO_MANY_REQUEST_UPDATES
• #1605 Split DELIVERY_TIMEOUT into two types of timeout
• We're still waiting on some content so look for an update, or new slides
• from Victor on his Delivery Timeout proposal and Required Request ID

Source Excerpt

The slides are posted here: We're still waiting on some content so look for an update, or new slides from Victor on his Delivery Timeout proposal and Required Request ID