Re: [Simple] MSRP O/A refresh question

[Miguel Garcia <Miguel.Garcia at nsn.com>]

Paul:

I think you are assuming that a successful O/A always implies a TCP 
connection. I don't think this interpretation is correct. For example, 
it is possible that several MSRP sessions share the same TCP connection. 
There is some text below Figure 3 in RFC 4975.

So, if it is possible to have different MSRP sessions multiplexed over 
the same TCP connection, then it implies that not every O/A implies a 
new TCP connection.

In the case you expose, a new SDP O/A on an existing MSRP session does 
not imply a new TCP connection if the TCP connection still exists.

/Miguel

Paul Kyzivat wrote:
> While reviewing the latest version of the file transfer draft I 
> developed some doubts about MSRP that I want to check:
>
> RFC4975, section 8.4 talks about updated SDP offers. I want to double 
> check my interpretation of this section.
>
> Suppose Alice makes an initial offer to Bob for an MSRP session, and Bob 
> accepts. At that time Alice is required to do the Connect to Bob.
>
> Later, Bob has need to refresh the sip session with a reinvite, but has 
> no desire to change anything about the MSRP session. So Bob sends an 
> offer with an unchanged o-line. Alice doesn't want to change anything 
> either, and so answers with an unchanged o-line.
>
> By my reading, its required that Bob now connect to Alice. Even though 
> neither wants to change anything there is need to establish a new 
> connection, and presumably to drop the old one.
>
> Is that right???
>
> If not, where is some other behavior called out?
>
>     Thanks,
>     Paul
>
>
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www1.ietf.org/mailman/listinfo/simple

--
Miguel A. Garcia           tel:+358-50-4804586
Nokia Siemens Networks     Espoo, Finland



_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple