Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

Peter Thatcher <pthatcher@google.com> Tue, 18 June 2013 05:49 UTC

Return-Path: <pthatcher@google.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 B3DEA21F9DCE for <rtcweb@ietfa.amsl.com>; Mon, 17 Jun 2013 22:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 v1S6Nh2hxfHK for <rtcweb@ietfa.amsl.com>; Mon, 17 Jun 2013 22:48:59 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id C25BC21F9DCD for <rtcweb@ietf.org>; Mon, 17 Jun 2013 22:48:59 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so3529073pbc.10 for <rtcweb@ietf.org>; Mon, 17 Jun 2013 22:48:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=tdWPjvqM1/f5Jq9xYBnWfyGv5dvuctPlf1wd/XmgtyM=; b=AfZIduBzlUrzRuhWBhN/Ripp4/JxynknZ6GvIGbREMZZEFtTZPuN1iCCyDSUjAhhng uhRfP3C7uCXbX+GO675pR5sijN304kKND62f+iI9JaRfGXTF7gOslzP+IC96gwlEpmym p5zAN8bUJnAaUSdJYuSjskWoUERcMlIHvDCj03CJ6+o8DagK4M5zU7zJiY3s2AN9NeT7 6t+oTEjD5ip9ItFMZ3AeqOOVML61oO8xH6y5/VHMx9136GvDqha7YMp8N4qAsMedO+9v NNenlLZvJCpqeGQ0B585M95Jj7f3P8jPNsDT9gIKt2E7zmYjYcllHQ79DSv2YPhP+Q5T ZzMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=tdWPjvqM1/f5Jq9xYBnWfyGv5dvuctPlf1wd/XmgtyM=; b=Jl6bY2MB5pq5DpjWyB8IZ3sE61NfDqZJbKgvybsOT7rL7NIzB+wuSqreIgw4fT14Hp Cc9wPvxUAEBDmkm+005RaV4JwsJGIYl6M/UDdI/x8Zo5Xtd5hymqRbJV17HKa+FcHGwS WZEUsvJmSjywohti5pYPo4ati0nduwlH0AU8+fXSWeYtlaJoxKDn2P/B2FPrN/0gCu1i l1OcIHnetLFmUjbCDPJkHsYmgIGONimqbxGkefmTBOkkJoB+dcOyre4O6rJEece6DqUJ jew89Wkr1XruThz3BWtluDnJjdBXuSD7dggSfSmm0BcxScKuwEpqkjPJD3CD7W9MgcsW E9SA==
X-Received: by 10.68.69.108 with SMTP id d12mr15786420pbu.187.1371534539338; Mon, 17 Jun 2013 22:48:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.88.8 with HTTP; Mon, 17 Jun 2013 22:48:19 -0700 (PDT)
In-Reply-To: <CALiegfkZcXrNR3CXY--d4ObZMV2z7NEpgdyVHtVtROVtDQsT6A@mail.gmail.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CABkgnnUmRpanfpwryyiCUsOdMLzrd74n-4LXaj_AK3aLe0yQ8Q@mail.gmail.com> <51BF5F00.90705@jitsi.org> <CABkgnnWTvJYG1_HQWz3pZw633rgadeKzx472MTzzFMuq073RgQ@mail.gmail.com> <CALiegfkZcXrNR3CXY--d4ObZMV2z7NEpgdyVHtVtROVtDQsT6A@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 17 Jun 2013 22:48:19 -0700
Message-ID: <CAJrXDUGPTg2+QWX5r+Uieap3TH4tKHOXaHy7AMNcxzQcP8Lrcw@mail.gmail.com>
To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=0015174989ee03db0a04df674579
X-Gm-Message-State: ALoCoQldaf+n4xNec71dbBVmWqazrLsQ6JoShuf8Zv+ht9SSykgQEOewBH4Tj+h+rbC2IiK57WHrT05G/u99cYqOZcwj4ZyJQnQX8HBAu8n9FELyl2cKvN9zKdp6EsTwJDMnYU6n0TU1teWel1epAvDZH4m+JSuRaxx4xmfRGoYjJep/0vXVXfGPkIIGf+hzitPcXep4Y9QP
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
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: Tue, 18 Jun 2013 05:49:00 -0000

We're being very explicit that this isn't intended to blow up the WG like
comment 22 does.  It's merely adding two methods to PeerConnection that
allows JS apps to optionally avoid the issues of adding many media streams
to SDP.  We're focusing on making the smallest change that can bring the
biggest value, not rewriting all of WebRTC from scratch.


On Mon, Jun 17, 2013 at 2:56 PM, Iñaki Baz Castillo <ibc@aliax.net>; wrote:

> 2013/6/17 Martin Thomson <martin.thomson@gmail.com>;:
> > On 17 June 2013 12:09, Emil Ivov <emcho@jitsi.org>; wrote:
> >> So here's your chance: could you please share your view of how this
> would
> >> look if done properly?
> >
> > Actually, it would look very similar to this.  For everything.  No SDP
> > anywhere.  It's comment 22.
> >
> > It's in the archives of the webrtc list:
> >
> http://lists.w3.org/Archives/Public/public-webrtc/2012Oct/att-0076/realtime-media.html
>
> +1
>
>
> What is the aim of NoPlan? The draft says "This document does not
> question the use of SDP and the Offer/Answer model". Why? It should
> question it since it treats SDP as if it was a silly and unmanageable
> binary blob. It is like "we must live with SDP because it is
> mandatory, but let's try to ignore it as much as possible". If so, why
> don't ignore SDP entirely?
>
> However NoPlan is the best we have if, finally, SDP is mandated in WebRTC.
>
> I think it is time to write two lists:
>
> 1) Advantages of using SDP in WebRTC.
>
> 2) Dissadvantages of using SPD in WebRTC.
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>;
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>