Skip to content

Commit 0e1b344

Browse files
authored
Group ID SHOULD increase with time (#749)
The text that came out of the Denver interim plus a short editorial sentence. Closes #727 Closes #587
2 parents ef25f68 + 5ac7f05 commit 0e1b344

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

draft-ietf-moq-transport.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -379,6 +379,12 @@ subscriber that does not want to receive the entire track can opt to receive onl
379379
the latest group(s). The publisher then selectively transmits objects based on
380380
their group membership. Groups can contain any number of objects.
381381

382+
Within a track, the original publisher SHOULD produce Group IDs which increase
383+
with time. Subscribers to tracks which do not follow this requirement SHOULD NOT
384+
use range filters which span multiple groups in FETCH or SUBSCRIBE. SUBSCRIBE and
385+
FETCH delivery use Group Order, so a FETCH cannot deliver Groups out of order
386+
and a subscription could have unexpected delivery order if Group IDs do not increase
387+
with time.
382388

383389
## Track {#model-track}
384390

0 commit comments

Comments
 (0)