Re: [Simple] MSRP-ACM vs existing SBCs (was Re: What ACM is all about [was: RE: MSRP-ACM compatibility)

["Christer Holmberg" <christer.holmberg at ericsson.com>]

Hi, 

>>Instead of "modify SBCs" I guess we should say "add MSRP specific
treatment of SDP to SBCs".
>
>No, I don't think that's completely correct.
>
>The TLS-related issues may well force SBCs to handle the media
differently than they handle other kinds of connections. I don't think
it's reasonable to restrict the solution space to "only those things 
>that can be achieved through SDP handling alone."

It is true that there are TLS related issues, but they may not be
specific to the ACM path modification part. We seem to have TLS issues
also for the pure comedia part.

Also, I am not sure they are even specific to MSRP. A user using TLS, no
matter for what media or signalling, must always have the correct
information regarding which certificate to use.

But, for ACM, as we have discussed, it is rather clear what the SBC
could do in order to make it work. It needs to make sure the user has
the correct certification information, both when the SBC terminates TLS
and when it treats TLS transparently.

I proposed some generic MSRP text about that, so SBCs which are to
support MSRP TLS would simply have to follow that also. Otherwise things
simply wouldn't work. 

Regards,

Christer