Re: [rtcweb] About defining a signaling protocol for WebRTC (or not)

Iñaki Baz Castillo <ibc@aliax.net> Thu, 15 September 2011 11:50 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 2E74521F8A95 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 04:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[AWL=0.027, 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 IRxOX3VINx09 for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 04:50:28 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3738421F8A6C for <rtcweb@ietf.org>; Thu, 15 Sep 2011 04:50:27 -0700 (PDT)
Received: by qyk32 with SMTP id 32so4926763qyk.10 for <rtcweb@ietf.org>; Thu, 15 Sep 2011 04:52:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.67.105 with SMTP id q41mr786335qci.216.1316087558648; Thu, 15 Sep 2011 04:52:38 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Thu, 15 Sep 2011 04:52:38 -0700 (PDT)
In-Reply-To: <0BF9ED5E-5B73-4316-AE95-0D85B73CBD19@phonefromhere.com>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <4E71927C.1090606@skype.net> <CALiegfnEaYVsZpKQOoVtT=2gGCzssX79pxLGo7H2Ez0GcMTG-A@mail.gmail.com> <0BF9ED5E-5B73-4316-AE95-0D85B73CBD19@phonefromhere.com>
Date: Thu, 15 Sep 2011 13:52:38 +0200
Message-ID: <CALiegfnE9G_vxXDha7pb57pmd=rovLOz=-uWTOirSPDV-pLyMg@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] About defining a signaling protocol for WebRTC (or not)
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: Thu, 15 Sep 2011 11:50:32 -0000

2011/9/15 Tim Panton <tim@phonefromhere.com>;:
> Are we saying that SDP is so impossible to parse that the only way to do it
> is with a pre-existing native library ?!? If not I think we can do that transformation
> (when needed) in JavaScript.

No, I just said that _maybe_ it wouldl be useful to provide such
parsing functions natively (given the fact that various protocol use
SDP bodies, as SIP and XMPP).

I'm fine with parsing SDP bodies in custom JavaScript code however :)

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