IETF Logo Mail Archive

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

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Fri, 18 October 2013 19:11 UTC

Return-Path: <fluffy@cisco.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 33FC611E8312 for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 12:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 2eW7ayQzwNCj for <rtcweb@ietfa.amsl.com>; Fri, 18 Oct 2013 12:11:50 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id E027D11E8310 for <rtcweb@ietf.org>; Fri, 18 Oct 2013 12:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1296; q=dns/txt; s=iport; t=1382123510; x=1383333110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=v+EBiiiKoBRFn3SSmBescws5uszelRWMjC4FI2sUDcY=; b=lbvAgrrbthQ7fFAh3qvZsUNqRDTVw/nem89paKY50LFBpKFfOG87fCc1 DmDUQkrbv0Q+JzrVF/5PPSC+vJTRyFSRrq54/lPMnNV1LbTn/sCt3imgZ nKYgo8Hbt3hmwWGQeu0Cwu11qtN9/iIwZMktbkSd+wbvkXS6hIKMD0s6W 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAKCHYVKtJXG8/2dsb2JhbABQCoMHgQq+JIEjFnSCJQEBAQMBeQULAgEIIiQyJQIEDgUIE4dlBsEIjhOBEAIxB4MfgQoDiQeLI44xhzWDJIIp
X-IronPort-AV: E=Sophos;i="4.93,524,1378857600"; d="scan'208";a="273925551"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 18 Oct 2013 19:11:49 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9IJBmtO026106 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Oct 2013 19:11:49 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Fri, 18 Oct 2013 14:11:47 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [rtcweb] JSEP: Order of m- lines in multiple PeerConnections
Thread-Index: AQHOzDXkSk4xBHAwQSOQDX27ZZb6/A==
Date: Fri, 18 Oct 2013 19:11:46 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123CBC74B@xmb-aln-x02.cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1C4AFB57@ESESSMB209.ericsson.se>, <CAMRcRGRJQ+6a7CnTxVixXpv+zYWLO69J=NeG0-h+SNRhnsTAEg@mail.gmail.com> <fxpfdprlgl8ik9kns46p8st0.1382072314943@email.android.com>
In-Reply-To: <fxpfdprlgl8ik9kns46p8st0.1382072314943@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1DC6A9C2310E404BB563CBCA7E8C77B9@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 19:11:56 -0000

On Oct 17, 2013, at 10:59 PM, Christer Holmberg <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.

v2.23.0 | Report a Bug | By Email