Skip to content

Commit 5b1ec66

Browse files
authored
Reflow some long lines
1 parent 094d800 commit 5b1ec66

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

draft-ietf-moq-transport.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1500,10 +1500,11 @@ UNSUBSCRIBE Message {
15001500

15011501
## FETCH {#message-fetch}
15021502

1503-
A subscriber issues a FETCH to a publisher to request a range of already published
1504-
objects within a track. The publisher responding to a FETCH is responsible for retrieving
1505-
all available Objects. If there are gaps between Objects, the publisher omits them from the
1506-
fetch response. All omitted objects have status Object Not Available.
1503+
A subscriber issues a FETCH to a publisher to request a range of already
1504+
published objects within a track. The publisher responding to a FETCH is
1505+
responsible for retrieving all available Objects. If there are gaps between Objects,
1506+
the publisher omits them from the fetch response. All omitted objects have status
1507+
Object Not Available.
15071508

15081509
**Fetch Types**
15091510

@@ -1512,13 +1513,14 @@ There are two types of Fetch messages:
15121513
Standalone Fetch (0x1) : A Fetch of Objects performed independently of any Subscribe.
15131514

15141515
Joining Fetch (0x2) : A Fetch joined together with a Subscribe. A Joining Fetch
1515-
shares the same Subscribe ID as an already-sent Subscribe. A publisher receiving a Joining
1516-
Fetch should use properties of the associated Subscribe to determine the Track Namespace,
1517-
Track, StartGroup, StartObject, EndGroup, and EndObject for the Joining Fetch such that it is
1518-
contiguous with the associated Subscribe and begins Preceding Group Offset prior.
1519-
1520-
A Subscriber can use a Joining Fetch to, for example, fill a playback buffer with a certain
1521-
number of groups prior to the live edge of a track.
1516+
shares the same Subscribe ID as an already-sent Subscribe. A publisher receiving a
1517+
Joining Fetch should use properties of the associated Subscribe to determine the
1518+
Track Namespace, Track, StartGroup, StartObject, EndGroup, and EndObject for the
1519+
Joining Fetch such that it is contiguous with the associated Subscribe and begins
1520+
Preceding Group Offset prior.
1521+
1522+
A Subscriber can use a Joining Fetch to, for example, fill a playback buffer with a
1523+
certain number of groups prior to the live edge of a track.
15221524

15231525
A Fetch Type other than the above MUST be treated as an error.
15241526

0 commit comments

Comments
 (0)