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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 18 October 2013 18:03 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA7011E825D for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 11:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.678
X-Spam-Level:
X-Spam-Status: No, score=-5.678 tagged_above=-999 required=5 tests=[AWL=0.571, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xxe5ojYGwiKy for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 11:03:37 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 56D1911E826F for <rtcweb@ietf.org>; Fri, 18 Oct 2013 11:03:34 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-c0-526177f48ae2
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 3D.90.16099.4F771625; Fri, 18 Oct 2013 20:03:33 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0328.009; Fri, 18 Oct 2013 20:03:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections
Thread-Index: Ac69tBInSk4xBHAwQSOQDX27ZZb6/AMtSyPQAFcb2ID///JBgYABCSOAgAAu1RA=
Date: Fri, 18 Oct 2013 18:03:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4C2F12@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C4AFB57@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C4C0339@ESESSMB209.ericsson.se>, <C5E08FE080ACFD4DAE31E4BDBF944EB123CB8C15@xmb-aln-x02.cisco.com> <ji14uqv82eppr14das035mbh.1382072169019@email.android.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123CBA896@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123CBA896@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvje7X8sQggy2TOCw6JrNZrP3Xzu7A 5DHl90ZWjyVLfjIFMEVx2aSk5mSWpRbp2yVwZWy89oypoEuq4sStNSwNjFdEuhg5OSQETCTm 3LrNBGGLSVy4t56ti5GLQ0jgMKPE/OmPWSGcJYwSN179Zeli5OBgE7CQ6P6nDdIgImAo0bRn Hlgzs4C6xJ3F59hBbGEBT4npBzvYQcpFBLwkLm4Vgyj3kzh95ykzSJhFQFXi4IMckDCvgK9E 84O3UGuvMklsftDPCpLgBEos6b8ANpIR6Lbvp9ZArRKX+HDwOjPEzQISS/ach7JFJV4+/scK YStJLLr9GapeR2LB7k9sELa2xLKFr5khFgtKnJz5hGUCo9gsJGNnIWmZhaRlFpKWBYwsqxjZ cxMzc9LLDTcxAuPj4JbfujsYT50TOcQozcGiJM774a1zkJBAemJJanZqakFqUXxRaU5q8SFG Jg5OqQbG8AtOt89M3sNm9mjORr8TphYcj8+9Sz2flbCpYPotNnvO8KqV189piAX9Ybo2idPz WMp87RsqHZ99+Woqn21Yv2t3y3Rpvbyb2t5yKknWxo59pqz7Ey7sVTF4zbHx3qeS/pR+6Tfb 9xw4zBP/IcA9UN1z65kvrNsL1JNszBjvt/+fZbhiatMMJZbijERDLeai4kQAJMrT410CAAA=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 18:03:42 -0000

Hi,

> By Invite with replaces, I mean an INVITE in new SIP dialog that uses the replaces header ( http://www.ietf.org/rfc/rfc3891.txt ) with the context of the old SIP dialog. 
> That is supported and used for lots of cases by PBX that act as B2BUA because it becomes and effective way to do things like totally change the number m-lines. 
>
> Well, when creating a new Offer to use with invite with replaces, the number of m lines don't have to match at all. You are not even required to have the same media types. So it seems like that would do it. 

True, but I don't think one should have to do that.

The initial Offer, sent by PC#1, has reached remote entities R_1 and R_2, and both have sent an Answer. For R_2 I now want to create a new PC, PC#2, and send a new Offer with the address properties of PC#2. 

Regards,

Christer



On Oct 17, 2013, at 10:59 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi Cullen,
> 
> My question is how it would be done when creating the new PC, so I don't think replacing UPDATE with REPLACE would solve the problem :)
> 
> Also, the usage of a new PC can also be used for serial forking. But, that is not the issue.
> 
> Regards,
> 
> Christer
> 
> Sent from my Sony Ericsson Xperia arc S
> 
> "Cullen Jennings (fluffy)" <fluffy@cisco.com> wrote:
> 
> 
> Perhaps in the parallel forking section, we should replace UPDATE with "INVITE with replaces" . Would that work ?
> 
> Alternatively we could just remove the parallel forking section.
> 
> On Oct 16, 2013, at 5:16 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
>> Hi,
>> 
>> Any comments on this issue? I'd like to have some e-mail discussions before Vancouver.
>> 
>> I'd also like it to be listed as an issue - unless, of course, I have missed something, and it really isn't an issue :)
>> 
>> Regards,
>> 
>> Christer
>> 
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer Holmberg
>> Sent: 30. syyskuuta 2013 11:08
>> To: rtcweb@ietf.org
>> Subject: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections
>> 
>> Hi,
>> 
>> JSEP talks about the usage of multiple PeerConnection to support forking, i.e. for each new forked leg (SIP: early dialog) a new PeerConnection is created.
>> 
>> As has been indicated, as each new PeerConnection will have its own set of address properties, ICE properties etc, so a new Offer will have to be created and sent to inform the remote about the new properties.
>> 
>> So far so I good.
>> 
>> I also assume that the same camera/mic/etc sources are connection to each PeerConnection, so the number of m- lines in the Offer of the new PeerConnection should be the same.
>> 
>> 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?
>> 
>> Regards,
>> 
>> Christer
>> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb