On Jul 27, 2009, at 4:05 PM, Christer Holmberg wrote:
So, for session establishment, there is currently no difference between ACM and 4975 - if there is a TCP connection to a specific ACM currently specifies the usage of a=connection for session modifications, in accordance with comedia. So, IF we a=connection to work with relays, I guess we would need to provide the information to the relay inside the MSRP message.I'm not sure I follow--what would you conceptually be telling therelay? You would be telling that a session modification has occurred (the remote address hasn't changed), and whether the relay can continue to use the existing TCP connection for the session, or whether it should create a new one. Ie the client would tell the relay exactly what the client was told in the session modification SDP.
So, why would we ever need to explicitly signal (in SDP) that a relay (or an endpoint for that matter) needs to create a new connection instead of reusing an appropriate existing one?