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 10:00 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 C4F9221F9E03 for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 03:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level:
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.008, 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 BszB6vNsuBK0 for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 03:00:03 -0700 (PDT)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA3321F9E5B for <rtcweb@ietf.org>; Tue, 18 Jun 2013 02:59:59 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id hu16so1981225qab.8 for <rtcweb@ietf.org>; Tue, 18 Jun 2013 02:59:59 -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=/91eB0hZTuQqN0bDPzIwK2Beh4CQqmlmdvqf8lFS7ig=; b=Mn1ZYKcshjpWHmIJNrogIOUj6bJd0Ynak+8c0uSe0NVNbmFG77YHHNMvS7rh7hZ6Ue 3RZ5rEvJImOCIfYhO+jPHT5bc+aCbtnsLT4cIG7T3h11LGmPN6zjaoOvtm+aKeBg7XFy zjUspl4S03jT/OyIDZrt7IewzVmOhqVYjwDekMe+BdqQTXthgFczJy/nOJhM4g+rp7YB WcNuyZ+x37aPC67B4wE4/5VTQocp0rBMlVL9xivmWy5wg9DD4n5Lcs6KOelpA1ZbBHRS Q8q+iZQKVXlPRFFZNjRkqswWhvKCh4hMxnYls1AuNfpbsRFSr/TMg6dvvpKZ689b5EAp 3EYA==
X-Received: by 10.49.14.161 with SMTP id q1mr9975655qec.50.1371549599599; Tue, 18 Jun 2013 02:59:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Tue, 18 Jun 2013 02:59:38 -0700 (PDT)
In-Reply-To: <51C02B4C.2090108@telecomitalia.it>
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> <CALiegf=dDAJAMaP5UeyUQeyqO-X-5wGgrELevuaQpWb6kPkHcw@mail.gmail.com> <51C02B4C.2090108@telecomitalia.it>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Tue, 18 Jun 2013 11:59:38 +0200
Message-ID: <CALiegfm_MWoBDsENr03RTnujYYfhtPm+zwvhjwkBck2WLinh6w@mail.gmail.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlUy6kv+ogkiHrtHbAgUiO3ZRer7+pNGRGvlznrAsT9KWUtk9GJte8nG2Ts8LgmfM/wynwO
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 10:00:03 -0000

2013/6/18 Enrico Marocco <enrico.marocco@telecomitalia.it>;:
>> Yes, that is basically a "PSTN call", no more. For sure, many people
>> have seen their mission accomplished with those demos ("we can enter
>> the PSTN from the web, we are done, WebRTC satisfy our needs !!!!").
>
> And even from the no-plan side of the fence that looks like a feature
> rather than a bug.

It's easy to build a spec based on "SIP interoperability" and then
make a "SIP intercommunication demo". Now the problem is that any
*future* custom signaling protocol on top of WebRTC must deal with O/A
and SDP limitations. WebRTC innovation subject to SIP model, forever.




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