search

moq-wg / moq-transport

draft-ietf-moq-transport
Other
84 stars 22 forks source link

Delivery timeout cannot be expressed per subgroup #606

Open fluffy opened 19 hours ago

fluffy commented 19 hours ago

TTL got moved into delivery timeout in subscribe OK but that lost the property to set a different timeout for different sub groups.

It is not clear where a max cache parameter can be in the protocol.

It is not clear interaction of max cache and delivery timeout in subscribe OK are both needed.

afrind commented 17 hours ago

I renamed the issue to reflect the primary issue with the current draft.

It is not clear where a max cache parameter can be in the protocol.

This is true, let's file a separate issue. My understanding is that it's useful in both SUBSCRIBE_OK and FETCH_OK - does that seem right?

It is not clear interaction of max cache and delivery timeout in subscribe OK are both needed.

My understanding is:

DELIVERY_TIMEOUT only applies to SUBSCRIBE (not FETCH) -- how long should a relay attempt to deliver an object before dropping/resetting. MAX_CACHE_DURATION tells a cache the max time to keep an object in cache (to serve via FETCH) before expiring it. A subsequent fetch after expiry would necessitate re-fetching from origin.

If that's right then having both in SUBSCRIBE_OK seems valid. If that's not right, let's file a separate issue for this too.