Skip to content

Clarify first object in event and media timeline track #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
suhasHere wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify first object in event and media timeline track #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions draft-ietf-moq-msf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1054,9 +1054,12 @@ The mime-type of a media timeline track MUST be specified as "application/json".

## Media Timeline track updating
The publisher MUST publish an independent media timeline in the first MOQT Object
of each MOQT Group of a media timeline track. The publisher MAY publish incremental
updates in the second and subsequent Objects within each Group. Incremental updates
only contain media timeline records since the last media timeline Object.
of each MOQT Group of a media timeline track. An independent media timeline object
MUST contain all media timeline records accumulated up to that point, allowing a
Copy link

@gwendalsimon gwendalsimon Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we force "all records up to that point"? It seems excessive, for very long stream (cricket games) and even worse for 24/7 channels. It would be good to have a kind of "horizon", and so we would let the publisher send only the XX latest records, corresponding to now - horizon. We could add an optional parameter specific to both timelines to express the horizon (either in ms or number of groups). If not, then we would assume infinite horizon.

Copy link
Contributor Author

@suhasHere suhasHere Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point @gwendalsimon
Also i wonder, the publisher application is the final decision maker. I wonder how would the marker help the subscriber to act on it ?

subscriber joining at any group boundary to receive the complete timeline history.
The publisher MAY publish incremental updates in the second and subsequent Objects
within each Group. Incremental updates contain only new media timeline records since
the previous media timeline Object in that Group.

# Event Timeline track {#eventtimelinetrack}
The event timeline track provides a mechanism to associate ad-hoc event metadata with
Expand Down Expand Up @@ -1098,9 +1101,12 @@ An event timeline track MUST carry:

## Event Timeline track updating
The publisher MUST publish an independent event timeline in the first MOQT Object
of each MOQT Group of an event timeline track. The publisher MAY publish incremental
updates in the second and subsequent Objects within each Group. Incremental updates
only contain event timeline records since the last event timeline Object.
of each MOQT Group of an event timeline track. An independent event timeline object
MUST contain all event timeline records accumulated up to that point, allowing a
subscriber joining at any group boundary to receive the complete event history.
The publisher MAY publish incremental updates in the second and subsequent Objects
within each Group. Incremental updates contain only new event timeline records since
the previous event timeline Object in that Group.

## Event timeline track examples

Expand Down