@@ -1521,7 +1521,6 @@ from to the corresponding Subscribe message (hereafter "the Subscribe").
15211521
15221522The following values are used :
15231523
1524- * ContentExists: whether we have any objects and therefore a Largest Group ID and Largest Object ID for the track 
15251524* Resolved Subscribe Start Group: 
15261525  * For Subscribes with Filter Type LatestObject or LatestGroup, this is equal to Largest Group ID. 
15271526  * For Subscribes with Filter Type AbsoluteStart or AbsoluteRange, this is equal to the StartGroup field of the Subscribe message 
@@ -1531,6 +1530,10 @@ The following values are used:
15311530  * For Subscribes with Filter Type AbsoluteStart or AbsoluteRange, this is equal to the StartObject field of the Subscribe message 
15321531* Preceding Group Offset: A field in the Joining Fetch message indicating the relative offset from the start of the Subscribe 
15331532
1533+ Note : If a relay does not yet have LatestGroup and LatestObject for a given track, it may choose to either forward both the Subscribe and 
1534+ the Joining Fetch upstream or to watch until the Joining Fetch can be resolved locally. However it is handled, the Resolved Subscribe Start values 
1535+ for a Joining Fetch MUST correspond to the Subscribe within the same session so the Fetch and Subscribe can be contiguous and non-overlapping. 
1536+ 
15341537Using that information and the following algorithm, these values are computed :
15351538
15361539* Fetch Start Group: The StartGroup for the Fetch 
@@ -1541,9 +1544,6 @@ Using that information and the following algorithm, these values are computed:
15411544
15421545The publisher receiving a Joining Fetch computes the fetch range as follows :
15431546
1544- If ContentExists is not 1 and Largest Group ID and Largest Object ID are not available, a relay SHOULD 
1545- forward the Fetch with the 0x2 Fetch Type upstream. 
1546- 
15471547* Fetch Start Group: Resolved Subscribe Start Group - Preceding Group Offset 
15481548* Fetch Start Object: 0 
15491549
0 commit comments