Re: [rtcweb] No Plan - but what's the proposal

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Thu, 06 June 2013 07:14 UTC

Return-Path: <silviapfeiffer1@gmail.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 E85AC21F96FE for <rtcweb@ietfa.amsl.com>; Thu, 6 Jun 2013 00:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 oF540nehq-nd for <rtcweb@ietfa.amsl.com>; Thu, 6 Jun 2013 00:14:31 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 601D521F9704 for <rtcweb@ietf.org>; Thu, 6 Jun 2013 00:14:27 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so4044511obc.23 for <rtcweb@ietf.org>; Thu, 06 Jun 2013 00:14:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=0aewtvWHcdcte5z3eVCAc6/SaW9dPQMfgT6iDcadOoU=; b=MwPWaxDVLYmmn5WRS75i6yTJPGXHKk5AXJ33JMXVI36uqUY2uyvka5rX0ePi2nRey2 8rMF6yuj9lVKsDGvdDMBL2hLRvv8zm0O9MYNJGYvFok54WvHkgnqnQR2jgC+BbM+mzeF q10V2upjbYwtAPZXdp33tregeFIbHUM4EZ3ks07cxaAsyN31Xz144Z3t3sTdNoYkfqow k2c8Z+XSGj5NzbcGGOk3aIuExXtfLt2d7Jr8NNsjsrxQSkb66hS0W8Zi1n5w211IUwcJ CilRZCcGcL+JBezsrim0IFTlch0rjbhpv4/fasvGzlpyajIdnxNnsL++WUjcZkpnVjN9 e8Dg==
X-Received: by 10.182.246.198 with SMTP id xy6mr17407204obc.1.1370502866260; Thu, 06 Jun 2013 00:14:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.116.71 with HTTP; Thu, 6 Jun 2013 00:14:06 -0700 (PDT)
In-Reply-To: <13444A29-86C6-4D69-964D-AE9A5BA7BB4A@iii.ca>
References: <51A65017.4090502@jitsi.org> <C3639EB3-0F44-4893-88DA-BB9F9C96A116@iii.ca> <51A8EB7F.6000506@jitsi.org> <72B58042-78E3-4759-B3CD-204B82A38447@iii.ca> <51ACF998.5030202@jitsi.org> <CALiegf=pJtdL2A6V7bprZ_F=V39Fadb+kRw3yfO+6+MFVZ9x2A@mail.gmail.com> <5ED2CC48-1514-4C00-AEE8-A334EB67A6F4@iii.ca> <51AF5784.3060307@jitsi.org> <13444A29-86C6-4D69-964D-AE9A5BA7BB4A@iii.ca>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 6 Jun 2013 17:14:06 +1000
Message-ID: <CAHp8n2ngefdpyNMLw+5Mb0Lkk4pWFC5Yc_+xt+StDYD_6HgZrg@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No Plan - but what's the proposal
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: Thu, 06 Jun 2013 07:14:32 -0000

On Thu, Jun 6, 2013 at 3:41 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>
> I've trying to help you explain and I keep asking for an example but I don't think we have had a complete example yet. I know you think there is a complete example so let me try and be more specific so perhaps we can get to the bottom of the disconnect.
>
> Let me try to be specific.
>
> Say an application running on Alice's browser want to generate an offer that says the browser is ready to send and receive 2 streams of video and 1 stream of audio look like? Imagine that one of the video streams is a document camera running at high res but low frame rate while the other is video of the speaker running at a higher frame rate.  What exactly does the SDP passed from the browser to the JS applications look like.  I agree the applications can do whatever it wants to communicate the relevant data to the far end so I don't care about  the signaling protocol or JSON  that JS app can send across the wire. But next question, can the far end start sending media immediately to the browser? Finally the far end does something that causes the applications to generate an SDP answer from the JS applications to Alice's browser. I want and example of that that looks like in the cases where the far end a) accepted all the video streams and b) rejected some but not all of the video streams.
>
> If we can get an simple example like this sorted out, then perhaps it will be easy to extrapolate to the ones in the say the use case document and start looking at things like number of round trips and audio clipping.


Wouldn't that simply be multiplexed over one PeerConnection in the
browser using addStream()? I have an application like that working. I
can dig out the SDP packets that the browser sends in this case, if
you are interested.

Regards,
Silvia.