@@ -1518,7 +1518,6 @@ from to the corresponding Subscribe message (hereafter "the Subscribe").
15181518
15191519The following values are used :
15201520
1521- * ContentExists: whether we have any objects and therefore a Largest Group ID and Largest Object ID for the track 
15221521* Resolved Subscribe Start Group: 
15231522  * For Subscribes with Filter Type LatestObject or LatestGroup, this is equal to Largest Group ID. 
15241523  * For Subscribes with Filter Type AbsoluteStart or AbsoluteRange, this is equal to the StartGroup field of the Subscribe message 
@@ -1528,6 +1527,10 @@ The following values are used:
15281527  * For Subscribes with Filter Type AbsoluteStart or AbsoluteRange, this is equal to the StartObject field of the Subscribe message 
15291528* Preceding Group Offset: A field in the Joining Fetch message indicating the relative offset from the start of the Subscribe 
15301529
1530+ 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 
1531+ the Joining Fetch upstream or to watch until the Joining Fetch can be resolved locally. However it is handled, the Resolved Subscribe Start values 
1532+ for a Joining Fetch MUST correspond to the Subscribe within the same session so the Fetch and Subscribe can be contiguous and non-overlapping. 
1533+ 
15311534Using that information and the following algorithm, these values are computed :
15321535
15331536* Fetch Start Group: The StartGroup for the Fetch 
@@ -1538,9 +1541,6 @@ Using that information and the following algorithm, these values are computed:
15381541
15391542The publisher receiving a Joining Fetch computes the fetch range as follows :
15401543
1541- If ContentExists is not 1 and Largest Group ID and Largest Object ID are not available, a relay SHOULD 
1542- forward the Fetch with the 0x2 Fetch Type upstream. 
1543- 
15441544* Fetch Start Group: Resolved Subscribe Start Group - Preceding Group Offset 
15451545* Fetch Start Object: 0 
15461546
0 commit comments