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> Mon, 08 July 2013 17:15 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 9339021F977A for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 10:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.644
X-Spam-Level:
X-Spam-Status: No, score=-2.644 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Z38LV3o41jxD for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 10:15:24 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFAD21F972C for <rtcweb@ietf.org>; Mon, 8 Jul 2013 10:15:24 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id e10so2394080qcy.41 for <rtcweb@ietf.org>; Mon, 08 Jul 2013 10:15:23 -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=E93Z4/CMmoFiGNbRbJfeEdVBfyCgoIL1zQFCjkV/+2o=; b=S/yRiVgsIrmXEKNHqX3vKWyQMN5Zwq09vxiAjHFBqSQKXkUEBabsGNV4JxQpknVhMo 8fAclVGxBdQfXrG3fzwKqUErYjc0584sUBDIWjoQjoLXmDYK0KVFBDRgEz7RTGhnX2fh ztigjuPIvB5DP+sOuJGyJYVwrJhAgDpB2J3N5jqN/hlyKK/VWxMR7ufE9DkCOuOPacnD TLT+VcapiDzVLulZSgsunck03OPVYuIrB4WJvJwZRzyE/3hirUG8yqLH4dYKpf8DzeB6 8wWcQVGsE1yqdmjnT62xknvxlwgX9eg+kIxPxF0S9aqhbnhfFuZR0DgxMBm7t7vZCHgJ 0BJA==
X-Received: by 10.224.182.79 with SMTP id cb15mr19899628qab.48.1373303723648; Mon, 08 Jul 2013 10:15:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Mon, 8 Jul 2013 10:15:03 -0700 (PDT)
In-Reply-To: <57A15FAF9E58F841B2B1651FFE16D281057BD4@GENSJZMBX01.msg.int.genesyslab.com>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <57A15FAF9E58F841B2B1651FFE16D281057BD4@GENSJZMBX01.msg.int.genesyslab.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 8 Jul 2013 19:15:03 +0200
Message-ID: <CALiegfkya_RV32WLanZKnt-v0O9hW5W_sgydjKMKuZ0uy70w=w@mail.gmail.com>
To: Jim Barnett <Jim.Barnett@genesyslab.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnYPGYKa5ZarAd8dVev2ne035/tnIQyYsIGQ3VfGicP5GUm57AFBBhjBaYEHae6Fv6XpEgJ
Cc: "<rtcweb@ietf.org>" <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: Mon, 08 Jul 2013 17:15:29 -0000

2013/7/8 Jim Barnett <Jim.Barnett@genesyslab.com>;:
> As I recall the consensus, developers are supposed to be able to modify the
> SDP, but we needed to specify what parts of the SDP could be modified.  In
> other words, there might be some limits to what could be modified, but we
> haven’t yet determined/agreed on what they are.

At this rate, wasting so long time on extending SDP to fullfil WebRTC
requirements, it would be done within the next 3-4 years. SDP is the
main issue delaying WebRTC 1.0.


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