[SIP SIMPLE client] sylk is not relaying chat messages

Adrian Georgescu ag at ag-projects.com
Sat Apr 30 12:41:01 CEST 2011

It matters if privacy is concerned  as relaxing the checks one user could easily impersonate another and copy its private messages.


On Apr 30, 2011, at 12:31 PM, Juha Heinanen wrote:

> Juha Heinanen writes:
>> i don't know what the rfcs say about this, but it would seem to be
>> better to do matching of MSRP messages to the conference based on the
>> tags in these headers
>> To-Path: msrps://;tcp
>> From-Path: msrps://;tcp
>> instead of To URI.  those tags were in the invite/200 ok exchange when
>> user joined the conference and would thus uniquely identify the
>> conference.
> msrp RFC 4975 says:
> 7.3.  Receiving Requests
> The receiving endpoint MUST first check the URI in the To-Path to
> make sure the request belongs to an existing session.  When the
> request is received, the To-Path will have exactly one URI, which
> MUST map to an existing session that is associated with the
> connection on which the request arrived.
> the MSRP SEND examples in the rfc don't include From and To headers at
> all, only To-Path and From-Path.  so it should not matter what To URI is
> in the SIP INVITE that establishes msrp session.
> -- juha

More information about the SIPBeyondVoIP mailing list