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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 18 June 2013 16:37 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 6189911E80E2 for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 09:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 XUp9Mjv6jht3 for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 09:37:33 -0700 (PDT)
Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id D6BBE11E80A2 for <rtcweb@ietf.org>; Tue, 18 Jun 2013 09:37:32 -0700 (PDT)
Received: by mail-qc0-f177.google.com with SMTP id n1so2395427qcx.8 for <rtcweb@ietf.org>; Tue, 18 Jun 2013 09:37:32 -0700 (PDT)
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:content-transfer-encoding:x-gm-message-state; bh=pgBhkzt5x8ZWZBpWKNYyxv8PhKw/pV5WR4agdpqfYR0=; b=KUaWHLFaHOp/d42NdotpcVAArXvwhyZSJIxjbDESYOGgVbNaCuhgEGmzM2R7tUC8p7 Gq4kp4XMqz2dRXekv9V7r96SMI0jnUJPrRQeInm3wqrvwRZx0n+LiOT/BTnsjm/wKq53 T0L2c/RiOFun1A41kqaIAtMBrxMr0NHM3bTtDINGq7Jw7MmyPm+BbDzlWTol2Bi5CP1r ZSgmZ1TpFqYsqwyuTzkUHVTbXvQLnEk/DNdfI5/sDXG+s/mqGcNqt6ltY0NW3hXCvD2/ B2XYmtB3zHTknpTcuHiepU87aaUPO7jUCC3BeGZvmCyNdhZ1spDGs6uuRk9GWl+HnhbE awmw==
X-Received: by 10.49.109.72 with SMTP id hq8mr28525566qeb.38.1371573452288; Tue, 18 Jun 2013 09:37:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Tue, 18 Jun 2013 09:37:12 -0700 (PDT)
In-Reply-To: <CAJrXDUGg98+NCbVzcDv-go+YFcPsfX=TaH9WscvUoSN63asHTg@mail.gmail.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CABkgnnUmRpanfpwryyiCUsOdMLzrd74n-4LXaj_AK3aLe0yQ8Q@mail.gmail.com> <CAJrXDUGnEwtsGZwUUqQgH0vDnMPy=XxqwQB9fpNcW9yQDhFt4w@mail.gmail.com> <CABkgnnVghXLu0ZdNkBkvLkqr=xgx6irWnyebU6rv+D45M+iaUg@mail.gmail.com> <CAJrXDUFkdfE2gfkRx6im3qNwjd3ObNv0tGO8O0vht146+A1kfQ@mail.gmail.com> <CALiegfmMWiEZDL4eCc6VSEsH1z8F6K5Xzz_-Z6hiKiD9yAap0Q@mail.gmail.com> <51C0269B.5070200@telecomitalia.it> <51C069CD.6000804@hookflash.com> <CALiegf=uENdToGPr1eRRgCOHY6kvoEy8-Aja8mhGWSp0Q=4D8w@mail.gmail.com> <CAJrXDUGg98+NCbVzcDv-go+YFcPsfX=TaH9WscvUoSN63asHTg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Tue, 18 Jun 2013 18:37:12 +0200
Message-ID: <CALiegfkSYW+8rnGiEyoapYYAkuANvQZhbj=L6UJgs+s4psV=9Q@mail.gmail.com>
To: Peter Thatcher <pthatcher@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQn62FO4I/AAga7oLIjjmcf8hCK3ltJAULwLxGfd7kuQ9PUq6aCdKB05CjP+WNiVKRYIHVsC
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 16:37:33 -0000

2013/6/18 Peter Thatcher <pthatcher@google.com>;:
> While I appreciate your desires to see a cleaner API (such that a JS app can
> choose not to use SDP), but I'd really like to keep this thread focused on
> the proposal made: the addition of two methods to PeerConnection that
> greatly improve the situation for adding streams.
>
> We are not proposing eliminating SDP altogether.  While such a proposal and
> discussion may have merit, that's not what we are proposing, so please start
> a separate thread to discuss it.

Yes Peter, you are right, sorry for that. I've opened a new thread.


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