Re: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections

Hi Christer,
I agree that parallel  and serial forking call flows can be solved with multiple PeerConnection model.

But going back to the original question you had -
>>> However, according the 3264, the ORDER of the m- lines also need to be kept the same.
>>> So, my question is: how can I ensure that the order of the m- lines in an Offer for a new PeerConnection is the same as in an Offer for an old PeerConnection?

The Jsep doc 4.1.4 setLocalDescription already implies that a new PeerConenction would use/support the old local description, and reading it, assumption is that the old description m-line ordering would not be changed.
It definitely didn't mention that we would send entirely new SDP on the new PeerConnection created…

We can call for clarification in the Jsep doc, but definitely not a issue as far as I see.

Thanks,
Vijaya

On 10/18/13 4:38 PM, "Christer Holmberg" <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

Again, it is not specific to parallel forking - it is also needed for SERIAL forking, in cases where you need to send updated Offers on early dialogs, and therefore cannot use PRANSWER.

I don't think I agree on that but I really want to spend my time on making sure we get the setLocal / setRemote text working for the simple case before we sort all this out.

This is how I understand it would work when discussing with Vijaya .

Now, if you don't agree, please then explain how you would implement the forking case I provided :)

Regards,

Christer

-----Alkuperäinen viesti-----
Lähettäjä: Cullen Jennings (fluffy) [mailto:fluffy@cisco.com]
Lähetetty: 18. lokakuuta 2013 22:12
Vastaanottaja: Christer Holmberg
Kopio: Suhas Nandakumar; rtcweb@ietf.org<mailto:rtcweb@ietf.org>
Aihe: Re: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections
On Oct 17, 2013, at 10:59 PM, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:
And, I'm not asking for a solution at this point, simply that we identify it as an issue that needs to be solved :)
So I sort of disagree on two points here.
I disagree that it needs to be solved - I'm not against solving it if anyone has an easy way but every time we talk about this the conclusions comes up people don't want to bother to fully solve the parallel forking problem in the first version of the webrtc. Speaking purely for myself, SIP parallel forking has not turned out to be extremely useful and has turned out to seriously complicate the use and extensions to the protocol - basically the HERFP problem - so I don't really care if webrtc takes on that problem or not.
Second, I suspect that Invite with replaces actually does solve this.
I certainly don't mind marking it as an issue but it's not clear to me that the WG thinks it is an issue that needs to be solved or that it an issue that is not solved. I've sort of been waiting to see the other "easy" stuff in JSEP / Bundle / Unified plan get sorted out and then figured we could go back and see what was possible or not with parallel forking in SIP.

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb