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

Eric Rescorla <ekr@rtfm.com> Wed, 03 July 2013 22:05 UTC

Return-Path: <ekr@rtfm.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 0E10211E80F6 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 15:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.085
X-Spam-Level:
X-Spam-Status: No, score=-102.085 tagged_above=-999 required=5 tests=[AWL=0.591, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ZAN-CFMQRlwp for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 15:05:38 -0700 (PDT)
Received: from mail-qe0-f47.google.com (mail-qe0-f47.google.com [209.85.128.47]) by ietfa.amsl.com (Postfix) with ESMTP id B07B121F9D9F for <rtcweb@ietf.org>; Wed, 3 Jul 2013 15:05:37 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id 1so417700qec.20 for <rtcweb@ietf.org>; Wed, 03 Jul 2013 15:05:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=DYPwaSxYoUUyGdguPl517BccnMDOJY1KcAkVOvH/Tng=; b=oIqYhL+kFVh7dVJjItPxo4HOJ2E+RAg4ghcNsa9jTi+trL2c8ndA1lrBm0BKS6KD3U YQOtVyGvKbxBbYYnxSxC+LHOfklDFLoLgckbTxPfDUB3x78oda98Y7I/+771NAmxqO6h 5Xm01GMsEhaTJCMJl1n0uyLLazj6hPo+Sc4f9Qs2EMzH7gFChni+RSEov9TMx0rZ19VG 6v65XZfXpIVBIJx5PSUXh2Shnv9Spt2bhS4qyq0hN7MTr47Zg968QL5SH1aziGvt5xeO 7ASWYj5v5m9mXbSbGnXEiCjiYNGHln5/kkNaifpRRZTAxerBZfbX4CwGGc2Xb3d1tghS 4o0A==
X-Received: by 10.229.173.202 with SMTP id q10mr864755qcz.64.1372889136981; Wed, 03 Jul 2013 15:05:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.48.234 with HTTP; Wed, 3 Jul 2013 15:04:56 -0700 (PDT)
X-Originating-IP: [74.95.2.173]
In-Reply-To: <CALiegfnDD8PAxZMfczV=cZtwx49XDT2+XiRhe5t88cT+xayz5g@mail.gmail.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> <CALiegfnDD8PAxZMfczV=cZtwx49XDT2+XiRhe5t88cT+xayz5g@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 03 Jul 2013 15:04:56 -0700
Message-ID: <CABcZeBMCGdY=LS0OG22aFdhwU2m_-H4_sHb15SAYBT7e2_4RLQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: multipart/alternative; boundary="001a1132eee653848704e0a2a900"
X-Gm-Message-State: ALoCoQktZbZ8f+FfWzZFblrqvDUuEOxrc1Gkvi2bXig8dTlWjs3ddRedVzsSYuTU9xCAPvmbQmU/
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: Wed, 03 Jul 2013 22:05:51 -0000

On Wed, Jul 3, 2013 at 2:42 PM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> So compatibility with SIP is important but compatibility with Jingle is
> just impossible. And this is supposed to be the API proposed to W3C...
>
Who said anything about impossible? It's a mechanical transformation
(see: http://xmpp.org/extensions/xep-0167.html).

Anyway, it's not like this feature is a surprise to anyone--well at
least anyone who was paying attention--it's been a feature of the
specification since before the WG was even formed. As I said
earlier, it was in the original WHATWG spec that Ian Hickson
wrote.

-Ekr