Skip to content

Allow unknown ranges in a FETCH response #1331

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
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Allow unknown ranges in a FETCH response #1331

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
383dd4f
RFC: Allow unknown ranges in a FETCH response
afrind Oct 22, 2025
d82164b
Update draft-ietf-moq-transport.md
afrind Oct 23, 2025
9c2120a
Merge branch 'main' into afrind-fetch-with-unknown-ranges
afrind Dec 1, 2025
2161ff3
Fixup reset stream code
afrind Dec 1, 2025
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
22 changes: 13 additions & 9 deletions draft-ietf-moq-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2255,10 +2255,6 @@ INVALID_JOINING_REQUEST_ID(0x32):
: In response to a Joining FETCH, the referenced Request ID is not an
`Established` Subscription.

UNKNOWN_STATUS_IN_RANGE(0x33):
: In response to a FETCH, the requested range contains an object with unknown
status.

## SUBSCRIBE {#message-subscribe-req}

A subscription causes the publisher to send newly published objects for a track.
Expand Down Expand Up @@ -2761,9 +2757,11 @@ A publisher MUST send fetched groups in the requested group order, either
ascending or descending. Within each group, objects are sent in Object ID order;
subgroup ID is not used for ordering.

If an Original Publisher receives a FETCH with a range that includes an object with
unknown status, it MUST return REQUEST_ERROR with code UNKNOWN_STATUS_IN_RANGE.

If a Publisher receives a FETCH with a range that includes an object with
unknown status (e.g. a Relay has temporarily lost contact with the Original
Publisher and does not have the Object in cache), it can choose to reset the
FETCH data stream with UNKNOWN_OBJECT_STATUS, or indicate the range of unknown
Objects and continue serving other known Objects.

## FETCH_OK {#message-fetch-ok}

Expand Down Expand Up @@ -3524,6 +3522,10 @@ DELIVERY_TIMEOUT (0x2):
SESSION_CLOSED (0x3):
: The publisher session is being closed.

UNKOWN_OBJECT_STATUS (0x4):
: In response to a FETCH, the publisher is unable to determine the Status
of the next Object in the requested range.

### Fetch Header {#fetch-header}

When a stream begins with `FETCH_HEADER`, all objects on the stream belong to the
Expand Down Expand Up @@ -3551,7 +3553,7 @@ format:
[Extensions (..),]
Object Payload Length (i),
[Object Status (i),]
[Object Payload (..),]
[Object Payload (..)]
}
~~~
{: #object-fetch-format title="MOQT Fetch Object Fields"}
Expand Down Expand Up @@ -3588,6 +3590,9 @@ the prior Object, the Subscriber MUST close the session with a
The Extensions structure is defined in {{object-extensions}}.

The Object Status field is only present if the Object Payload Length is zero.
FETCH responses have a special Object Status `UNKNOWN` (0x5). When Object
Status is `UNKNOWN`, all Objects between the last serialized Object, if any, and
this one, inclusive, have `UNKNOWN` status, rather than `Object Does Not Exist`.

When encoding an Object with a Forwarding Preference of "Datagram" (see
{{object-properties}}), the Publisher treats it as having a Subgroup ID equal to
Expand Down Expand Up @@ -3901,7 +3906,6 @@ TODO: register the URI scheme and the ALPN and grease the Extension types
| UNINTERESTED | 0x20 | {{message-request-error}} |
| PREFIX_OVERLAP | 0x30 | {{message-request-error}} |
| INVALID_JOINING_REQUEST_ID | 0x32 | {{message-request-error}} |
| UNKNOWN_STATUS_IN_RANGE | 0x33 | {{message-request-error}} |

### PUBLISH_DONE Codes {#iana-publish-done}

Expand Down