Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

Iñaki Baz Castillo <ibc@aliax.net> Wed, 03 July 2013 21:35 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 D956E11E8259 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 14:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.641
X-Spam-Level:
X-Spam-Status: No, score=-2.641 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 p3pfjWfvNlvF for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 14:35:53 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id C5A2D11E80EA for <rtcweb@ietf.org>; Wed, 3 Jul 2013 14:35:49 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i13so3874346qae.6 for <rtcweb@ietf.org>; Wed, 03 Jul 2013 14:35:49 -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:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=5K3iO+9yu9/WYVDR+0eAxtQbdJNZ0OsVfUKFRlTw3vI=; b=QDoRuVcY9dwWtUXlzraKq1sWFmHsv+vNK8qmv62KTofaq6yuwyd/b0is2iqSl0F80G r5RWpnHdMEWm5g5M2GiNfKplX/Ei4Z/8uWt4JWQEJHrRlCL99LKdIBBw3tFxKQRE9H+s cD8x1nwAVjo78CPK23hBheeCMapJV/J4QI8wBHpaVpwvyY7KGH8aW0en1e6JNIzEPcn3 DQDifMN7OxU4ctn/LFCJBI6RCiymFgtZbMYUxSJb6TQg7AgKbdk+c8pefVQG7iVS5Oba Mv5rrp9/fmgJHCkuomMUHn0mSUrAQdBZ9HkpW+SMQ7kwF30d75JC3Adl8Jm3G98y7Fi8 TlsQ==
MIME-Version: 1.0
X-Received: by 10.224.114.207 with SMTP id f15mr6235583qaq.115.1372887348951; Wed, 03 Jul 2013 14:35:48 -0700 (PDT)
Received: by 10.49.72.132 with HTTP; Wed, 3 Jul 2013 14:35:48 -0700 (PDT)
Received: by 10.49.72.132 with HTTP; Wed, 3 Jul 2013 14:35:48 -0700 (PDT)
In-Reply-To: <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com>
Date: Wed, 3 Jul 2013 23:35:48 +0200
Message-ID: <CALiegfmwG8tbL45ZXv5bkWgMMv+RkhJLJRvtHHVA1QzVmNoqmg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Peter Thatcher <pthatcher@google.com>
Content-Type: multipart/alternative; boundary=047d7bdc7de8c04ba904e0a23e2d
X-Gm-Message-State: ALoCoQlPvrcl7rx6te6JgQF5jpgSjqYMNDcVFNf/WbOFrW3XPf8JqHDqz7gPMnWsjFq2KfhiCIov
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
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: Wed, 03 Jul 2013 21:35:59 -0000

El 03/07/2013 23:26, "Peter Thatcher" <pthatcher@google.com>; escribió:
>

> Along with that, is "use Jingle for signalling" included in your set of
"most of the use cases"?

+1 good question. Hope there is a so good answer for it. Is it?

BTW not just Jingle but any (future?) media signaling protocol not based on
atomic full SDP blob exchange. Could somebody explain me how to do that
without mangling the SDP blob generated by PC?