In context of MSRP; How to tell if incoming connection request is of type TLS or TCP?
Prasun Bheri <[email protected]> Thu, 17 Jan 2013 13:45:52 +0530
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <CADUAairF4cSdAQR81=sT+_UdYZGa8pp-F5DBuZVvXPwbpc=HVw@mail.gmail.com> |
--===============2845320995777693532== Content-Type: multipart/alternative; boundary=f46d0447f2a8d76be404d3779c3e --f46d0447f2a8d76be404d3779c3e Content-Type: text/plain; charset=ISO-8859-1 Hello Group, In regards to TLS over MSRP. Scenario: There are two sessions between UE-A and UE-B, in which B chose to be active endpoint in both the sessions (a=setup:active), of which one session is over TLS and another is over TCP. Two incoming connection requests will arrive at A. What is the best approach for A to distinguish TLS request from TCP? In case of SIP its easy as there are separate ports for TCP and TLS. so the connection request will be identified based on the port upon which the request arrived. But for MSRP rfc 4975 doesn't recommend a different port, so both requests could arrive at same 2855 port. Thanks & Regards, Prasun Bheri --f46d0447f2a8d76be404d3779c3e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hello Group,<div><br></div><div style>In regards to TLS ov= er MSRP.=A0</div><div style><br></div><div style>Scenario:=A0</div><div sty= le>There are two sessions between =A0UE-A and UE-B, in which B chose to be = active endpoint in both the sessions (a=3Dsetup:active), of which one sessi= on is over TLS and another is over TCP.</div> <div style><br></div><div style>Two incoming connection requests will arriv= e at A.=A0</div><div style>What is the best approach for A to=A0distinguish= TLS request from TCP?</div><div style><br></div><div style>In case of SIP = its easy as there are separate ports for TCP and TLS. so the connection req= uest will be identified based on the port upon which the request arrived. B= ut for MSRP rfc 4975 doesn't recommend a different port, so both reques= ts could arrive at same 2855 port.=A0</div> <div style><br></div><div style>Thanks & Regards,</div><div style>Prasu= n Bheri</div><div style><br></div><div style><br></div><div style><br></div= ><div style><br></div><div style><br></div></div> --f46d0447f2a8d76be404d3779c3e-- --===============2845320995777693532== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list [email protected] https://www.ietf.org/mailman/listinfo/simple --===============2845320995777693532==--