Re: [rtcweb] Media forking solution for SIP interoperability (without a media gateway)

Cullen Jennings <fluffy@cisco.com> Mon, 31 October 2011 00:05 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 22A5C21F8BFB for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 17:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.343
X-Spam-Level:
X-Spam-Status: No, score=-106.343 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_MED=-4, 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 Y9UND-BUhPwQ for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 17:05:16 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B4B6521F8BF6 for <rtcweb@ietf.org>; Sun, 30 Oct 2011 17:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=553; q=dns/txt; s=iport; t=1320019514; x=1321229114; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=mLbmDc9VcqyQlTwlk8uNx2QUSJmml2AF2xZltKboTG0=; b=XRU7ptwk1ArxFZP+Tph5cYvyD545JvyRGZKpES5AB610H08zZ+89yOPJ S0v57jgTu+CrQ6pry74IRzaT4xcX6NC3amlbUkXuzRT5uDwUhuefcAip9 h6NTLzoyzcp4aFR2KUcbbeMOuNuCfXp9yjlZXejuJT99aRhNXbesmGxHF k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak0GAN7krU6rRDoG/2dsb2JhbABDJqkagQWBcgEBAQECARIBZgULC0ZXBi4Hh2CVSAGdG4ghYQSIBowIkX4
X-IronPort-AV: E=Sophos;i="4.69,428,1315180800"; d="scan'208";a="10119568"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 31 Oct 2011 00:05:14 +0000
Received: from sjc-vpn2-1232.cisco.com (sjc-vpn2-1232.cisco.com [10.21.116.208]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9V05Ds1024727; Mon, 31 Oct 2011 00:05:14 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="iso-8859-1"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852235717390@ESESSCMS0356.eemea.ericsson.se>
Date: Sun, 30 Oct 2011 12:41:24 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BBCA56E-CA6E-4585-8EBB-ED6EDFED789F@cisco.com>
References: <CALiegfkikmpi55ePUo=AQCQvorv4_6v2ByTCdL=V_=umcCEpUA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852235717390@ESESSCMS0356.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Media forking solution for SIP interoperability (without a media gateway)
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: Mon, 31 Oct 2011 00:05:17 -0000

On Oct 30, 2011, at 9:58 , Christer Holmberg wrote:

> In my opinion a better solution is to create a new PeerConnection for every new early dialog, which uses the *same* address/candidate parameters as the "parent" PeerConnection. 

Hmm we should talk about this - I have a hard time seeing how that is going to work. I was working on the assumption that  PeerConnection could deal with more than one offer/answer pair at a time. Given the current WebRTC API and something like ROAP - it seems like that should just work.