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

Peter Thatcher <pthatcher@google.com> Mon, 08 July 2013 14:48 UTC

Return-Path: <pthatcher@google.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 06A2821F9CE7 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 07:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.962
X-Spam-Level:
X-Spam-Status: No, score=-1.962 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 rbq8be0cKMfF for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 07:48:41 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 39C9C21F9815 for <rtcweb@ietf.org>; Mon, 8 Jul 2013 07:48:41 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id 10so4158402pdc.19 for <rtcweb@ietf.org>; Mon, 08 Jul 2013 07:48:40 -0700 (PDT)
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; bh=1TG2mUrqV3WcdoJ3xXa68POk+nT6nSrXzNA799IVAJY=; b=bQL1UfBhVy7kIo8lL3C6nfkwpajihcr3+IkmLt32YXIqOYSuBqlxi8D7FlqWHfAvV2 cvnnzi9mciomzuDfUVz2ca3s6nINUY24JawkaNCOvhfC8yMRrGiRHDgMM50Q76CPrpwZ 67GNia7EGHuGS4hKmdyU9ekjbe6VBbfIVW/bdU5kHqkkj4o374hiQNieHS6jJjTAZS9E CpZFoDp0VaF0ZoeXBwpAiZ1IwHGi7hnqbdVCcdBGe9j5jJU9jISRR0rEz5UG2pZatOz8 gNkh2OBjwRIJnP+36+HWl4YCgJoApylVvgFDsLofqYW5RGxFGkLYV7Q3EnBJBxUqN7RX BPBg==
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:x-gm-message-state; bh=1TG2mUrqV3WcdoJ3xXa68POk+nT6nSrXzNA799IVAJY=; b=G7u7dSZzqoWmDHDl6K5MDyKk54XSQv8iBO1BEuDL1xax7WeMDzf/UbHMVQhRLFqf7t ZdZHIlDUJIzvBWoabNxyQTS+AQxXvne+m6UbTldtmXbm2TG2GvnBmLedg7e/wz9p4Raw ZHHuEDmmi63hsl9wxdApDJVd9l+/b/2/248wAi7ClRXRCcShLpN6r10UiDaDWkCH2PpF RRIwCB3S+I/TVaek/4Uefy5yJfYWSS3OEVIUslB2jq7SRaHhpNMZd2b42yj5l2AsYot6 9ZuruIGNKLfa27LG3KCoEkqtGGCteHpBGG9T01JlkoKIy1R406vuIV0tZpCaLIltnLps j9iQ==
X-Received: by 10.68.28.232 with SMTP id e8mr21924703pbh.94.1373294920829; Mon, 08 Jul 2013 07:48:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.169 with HTTP; Mon, 8 Jul 2013 07:47:59 -0700 (PDT)
In-Reply-To: <51DAD083.8000901@stpeter.im>
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> <8B58E2AB-09B7-4816-8BC4-B932030E2ED2@iii.ca> <CAJrXDUEZixeAsDc42WY-kZvrpA-p4s1sjET-qzxZ2VH9x7yc5Q@mail.gmail.com> <51DAD083.8000901@stpeter.im>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 8 Jul 2013 07:47:59 -0700
Message-ID: <CAJrXDUFaGM+7j8xyjxJ31ZOwDCbwdgivTw1hNjUXqEB9c7kkWw@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=bcaec520eacdedb8f904e1012343
X-Gm-Message-State: ALoCoQk9W3U1oVi3UDGwN1C0lraRcu3Re+EqQCrnqbVW5EiqtjDle73k2pkjMKYkNpV6fY04q8lVXb7scHwYuzYEQAVRxd3KEqh3vvMKmbjYafYcwaIOF1TJwxBQbALl/GQw+NCWofjSJRNhUsbJ6higsU+TE7mbwYxw9EQZ/fUoEKIv3XUEmd29HPm+qLBmZmdnoBi0h38H
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 14:48:42 -0000

On Mon, Jul 8, 2013 at 7:45 AM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> On 7/8/13 8:40 AM, Peter Thatcher wrote:
> > On Sun, Jul 7, 2013 at 8:40 PM, Cullen Jennings <fluffy@iii.ca
> > <mailto:fluffy@iii.ca>> wrote:
> >
> >
> >     On Jul 3, 2013, at 2:42 PM, Iñaki Baz Castillo <ibc@aliax.net
> >     <mailto:ibc@aliax.net>> wrote:
> >
> >     > So compatibility with SIP is important but compatibility with
> >     Jingle is just impossible.
> >
> >     The mapping of SDP to jingle is in the Jingle specs … I'm not
> >     express any opinion on this one way or another other but the authors
> >     of theses specs have always claimed Jingle fully mapped to and from
> SDP.
> >
> >
> > I think he meant "impossible without SDP munging", which I think is
> > undeniable.
>
> What do you mean by "SDP munging"?
>

I mean that if the JS wants to send Jingle XML over the wire, it has to
parse the SDP.  Then, when it receives Jingle XML, it has to serialize SDP.
  That parsing and serializing of SDP I call "munging".  We could come up
with better words for more specific activities, but that seems to be the
word everyone else uses, so it's what I've used.




>
> As we know, various things are being added to SDP. The Jingle specs have
> not necessarily been updated yet to track those changes, although
> proposals have been made on several points. If folks want to keep Jingle
> in sync, that work would need to happen at the XSF. Feel free to join
> the jingle@xmpp.org list if you have proposals:
>
> http://mail.jabber.org/mailman/listinfo/jingle
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>