IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 31 October 2011 12:25 UTC

Return-Path: <ibc@aliax.net>
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 59BF721F8C68 for <rtcweb@ietfa.amsl.com>; Mon, 31 Oct 2011 05:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level:
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 mmVEWL05Zsns for <rtcweb@ietfa.amsl.com>; Mon, 31 Oct 2011 05:25:53 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id D57B921F8C36 for <rtcweb@ietf.org>; Mon, 31 Oct 2011 05:25:52 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so5671015vcb.31 for <rtcweb@ietf.org>; Mon, 31 Oct 2011 05:25:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.7.12 with SMTP id b12mr2499843vcb.23.1320063952284; Mon, 31 Oct 2011 05:25:52 -0700 (PDT)
Received: by 10.220.184.6 with HTTP; Mon, 31 Oct 2011 05:25:52 -0700 (PDT)
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6CB8C4@inba-mail01.sonusnet.com>
References: <CALiegfkikmpi55ePUo=AQCQvorv4_6v2ByTCdL=V_=umcCEpUA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852235717390@ESESSCMS0356.eemea.ericsson.se> <3BBCA56E-CA6E-4585-8EBB-ED6EDFED789F@cisco.com> <4EADF511.2040403@alvestrand.no> <387F9047F55E8C42850AD6B3A7A03C6CB8C4@inba-mail01.sonusnet.com>
Date: Mon, 31 Oct 2011 13:25:52 +0100
Message-ID: <CALiegf=iV=d9b8TNRrv9dh-gUDMzFBdRbsaUhLHdrXBG55ieGg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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 12:25:53 -0000

2011/10/31 Ravindran Parthasarathi <pravindran@sonusnet.com>:
> Harald,
>
> As per F11 & F12 of draft-ietf-rtcweb-use-cases-and-requirements-06 ,
>
>   "F11             The browser MUST be able to transmit streams to
>                   several peers concurrently.
>
>   F12             The browser MUST be able to receive streams from
>                   multiple peers concurrently."
>
> The above browser requirement makes me to guess that it is possible to support SIP parallel forking sort of services in case proper JS APIs are provided (May be current form of peerconnection does not). Please let me know your opinion on this.

The above requirements don't say that a *single* PeerConnection MUST
be able to send and receive streams to/from several peers
concurrently. It just says that the *browser* MUST be able, and a way
to achieve that is by creating multiple concurrent PeerConnection
objects.




-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email