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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 18 October 2013 18:28 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 7F7DD11E82E9 for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 11:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.704
X-Spam-Level:
X-Spam-Status: No, score=-5.704 tagged_above=-999 required=5 tests=[AWL=0.545, 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 7AM+dPRL1Z8D for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 11:28:38 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0668511E81B8 for <rtcweb@ietf.org>; Fri, 18 Oct 2013 11:28:37 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-4b-52617dd48811
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 11.E1.16099.4DD71625; Fri, 18 Oct 2013 20:28:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.02.0328.009; Fri, 18 Oct 2013 20:28:36 +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///JBgYABCSOAgAAu1RD///ojgIAAUZtw
Date: Fri, 18 Oct 2013 18:28:35 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C4C3025@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> <7594FB04B1934943A5C02806D1A2204B1C4C2F12@ESESSMB209.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB123CBC204@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123CBC204@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.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvje6V2sQgg7sXTSw6JrNZrP3Xzu7A 5DHl90ZWjyVLfjIFMEVx2aSk5mSWpRbp2yVwZexYcZ214ABnxZp59g2M29i7GDk5JARMJOb8 6oSyxSQu3FvP1sXIxSEkcJhR4v37PiaQhJDAEkaJHweDuxg5ONgELCS6/2mDhEUEDCWa9swD K2EWUJe4s/gc2BxhAU+J6Qc72EHKRQS8JC5uFYMoj5L4vesLM4jNIqAq8eH5BBYQm1fAV+L9 usdMEGvvMEuc3N8ONpMTKPGj4w5YAyPQbd9PrYHaJS7x4eB1ZoibBSSW7DkPZYtKvHz8jxXC VpJYsf0SI0S9jsSC3Z/YIGxtiWULXzNDLBaUODnzCcsERrFZSMbOQtIyC0nLLCQtCxhZVjGy 5yZm5qSXG25iBEbHwS2/dXcwnjoncohRmoNFSZz3w1vnICGB9MSS1OzU1ILUovii0pzU4kOM TBycUg2MKXnmTyaGvzJf8NfkhkrtgbfXCguYrjBFml+YEPrpWMOlWK5LN5vmRX3Z2z/Zd/fL dVu1z559crTf5maQk9zhpsof2V/N5h7ODp8tdnfDhXyLFv4t2h+O/nSu6PHa2rnRW5nxXNgG z5eH136c6PVnerToOZ6Ut0KT8hQ+lxc+fMM78/sRm209y5RYijMSDbWYi4oTARAEOztcAgAA
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:28:43 -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. 
>> 
>
> Yah, I understand - that solution is basically the cloning proposal. 

No, because I would get NEW address properties.

But, the order of the m- lines (and the media sources etc they represent), and any property that 3264 does not allow to be changed, would have to be the same.

Regards,

Christer