How to support seeking or should seeking be discouraged when server is using the PUBLISH to control the subscription?

[laiDisney]

From the application perspective, when the server is using the PUBLISH to start the playback, that means the server will take control of how and what to play at the client side. And it should work fine when the client has no requirement, the server can decide the ABR, which is the server-side ABR.

But what if the client has some functional requirements and needs to update/initialize another subscription, like the client needs to support the seeking function? We don't have a message for the client to request that the server send PUBLISH_DONE+PUBLISH to update/reinitialize the subscription. Or if the client sends UNSUBSCRIBE+Joining FETCH, it will break the control of the server publishing.

So my question would be:

• Should the seeking not be allowed when server PUBLISH?
• Or we should figure out a solution to support this?
• Or is there a solution that supports it without breaking the control of the server publishing?

[sharmafb]

The specification explicitly permits the subscriber to update a subscription regardless of who initiated it, using a SUBSCRIBE_UPDATE.