does the expiration of a token also apply to the ongoing SUBSCRIBE?

[gwendalsimon]

Let's say an end-user connects to a Relay with a token that expires in 60 minutes. What I understand is that, if the user emits a SUBSCRIBE 65 minutes later, then the Relay will reject the request. However, if the user sends a SUBSCRIBE to a track immediately after the connection, it got the stream. 60 minutes later, should the Relay abruptly stop the track delivery? It would require the Relay to keep trace of the finishing time of each ongoing track.

[wilaw]

As currently defined, the expiry time applies only to the initial connection. This means that if the client connects to the relay with a 60min token at 10:00, then the client can do all the subscribing that it wants, but at 11:00, the relay will terminate the connection, which will effectively end all tracks being published and or subscribed in that session.

[wilaw]

@gwendalsimon - with composite claims we can now set individual expiry times for connect as well as a subscribe actions, and we can set individual reval periods. Do these features satisfy your original concern?