Martin Stiemerling wrote:
It might help for session setup, but in my view, matching responses to the original requests gets only more complex: - for pipelining, the receiver *) must match via the pipelined-request id (which is just another reference id)The sessionId might be helpful for multiple sessions (Section 4.3. Session Identifiers). To pipeline multiple requests you can use the pipelining (Section 12. Pipelining Support).
- for established sessions, it must match via session id- for any 'ping' request, it probably must default by guessing since the two above don't match
in contrast to- forward the received response to the instance that used this CSeq number regardless of what it is and why it was sent
*) This receiver I'm referring to is the gatekeeper between the x state machines (sessions, keep alive timer, possibly the interleaved (de-)multiplexer) and the one control connection. I'd like to have it as simple as possible; It assigns CSeq numbers for outgoing requests and matches the response again.
ch _______________________________________________ mmusic mailing list mmusic at ietf.org https://www.ietf.org/mailman/listinfo/mmusic