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

Lorenzo Miniero <lorenzo@meetecho.com> Thu, 15 September 2011 12:05 UTC

Return-Path: <lorenzo@meetecho.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 97EDD21F8AAA for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 05:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.569
X-Spam-Level:
X-Spam-Status: No, score=-0.569 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MIME_8BIT_HEADER=0.3]
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 1CZrAxU2DO9R for <rtcweb@ietfa.amsl.com>; Thu, 15 Sep 2011 05:05:15 -0700 (PDT)
Received: from smtplq02.aruba.it (smtplq-out18.aruba.it [62.149.158.38]) by ietfa.amsl.com (Postfix) with SMTP id 4407721F8A70 for <rtcweb@ietf.org>; Thu, 15 Sep 2011 05:05:14 -0700 (PDT)
Received: (qmail 2056 invoked by uid 89); 15 Sep 2011 12:07:19 -0000
Received: from unknown (HELO smtp3.aruba.it) (62.149.158.223) by smtplq02.aruba.it with SMTP; 15 Sep 2011 12:07:19 -0000
Received: (qmail 31719 invoked by uid 89); 15 Sep 2011 12:07:19 -0000
Received: from unknown (HELO lminiero-acer) (lorenzo@meetecho.com@143.225.229.166) by smtp3.ad.aruba.it with SMTP; 15 Sep 2011 12:07:19 -0000
Date: Thu, 15 Sep 2011 14:02:48 +0200
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: =?ISO-8859-1?B?SfFha2k=?= Baz Castillo <ibc@aliax.net>
Message-ID: <20110915140248.4cc17977@lminiero-acer>
In-Reply-To: <CALiegfnE9G_vxXDha7pb57pmd=rovLOz=-uWTOirSPDV-pLyMg@mail.gmail.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> <CALiegfnE9G_vxXDha7pb57pmd=rovLOz=-uWTOirSPDV-pLyMg@mail.gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: smtp3.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq02.aruba.it 1.6.2 0/1000/N
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 12:05:16 -0000

Il giorno Thu, 15 Sep 2011 13:52:38 +0200
Iñaki Baz Castillo <ibc@aliax.net>; ha scritto:

> 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 don't understand the need for it to be SDP actually: Javascript
already has native and efficient ways to describe information (JSON,
XML), if SDP is what everybody wants then it would be easier to just
map SDP over them.

L.

-- 
Lorenzo Miniero, COB

Meetecho s.r.l.
Web Conferencing and Collaboration Tools
http://www.meetecho.com