Re: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened

Iñaki Baz Castillo <ibc@aliax.net> Thu, 20 June 2013 16: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 A82C621F9DF8 for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 09:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 mXlMkT-77wSq for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 09:15:35 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 55C1D21F9DED for <rtcweb@ietf.org>; Thu, 20 Jun 2013 09:15:34 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ci6so1071000qab.11 for <rtcweb@ietf.org>; Thu, 20 Jun 2013 09:15:33 -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=RN3h0LE4MRRtK+VA6Lw7yoEwSOWJINIxF8C1zeGzq9U=; b=P6r7y1rR0rKXVsBY2ZS7VHOVg+r9kI4XtH3RGwt00LNuwHfO94uBJPzMCYMuWnjBZQ MWnbe3aN0ZJAm7e/htRrSZwTy90I8UOtQvcYWrWhClkmq5roWrn1b7t1ujSimq/cv/mP /Udo1V56cEZU/AgcQUuEcmh8FAQUpnnMdneQOZhte4T6eEBpPbesVzLU1mklbExjA6rk 9DWSyTbntlCa1HyXWn8vVrKpZd3pVNVAKcygmbRd8FX3Je05p2+eOY/KXhcQYRuCCkOM KL1Xzxldi5o+VDEr5z8+YmUNX6fiAu9Z/I1gzIBL3rfHBAfs9hbJhXEwhg/X5kVmsUYe r9hw==
X-Received: by 10.49.35.108 with SMTP id g12mr1188394qej.86.1371744933546; Thu, 20 Jun 2013 09:15:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Thu, 20 Jun 2013 09:15:13 -0700 (PDT)
In-Reply-To: <51C3209B.1030501@alvestrand.no>
References: <CALiegfkajJPxWZTzjYssP91VW+StStLpxoxGCkjOLKDMUWc0rA@mail.gmail.com> <CA+9kkMDk2L3SBPC08WU_5RcL16-Wzv8Mocj3-Qzmxz2E24ERGg@mail.gmail.com> <51C0C1A0.9010107@nostrum.com> <CAJrXDUGqSvsosZJhcRR-kCwEX1g_wvPnSZPmmcNwggk+Z9WNCA@mail.gmail.com> <CABkgnnWfV=5xBaRqAddqUURThs9J4T4+0HK4Ux07VA51r5oC3Q@mail.gmail.com> <CAJrXDUFNGKvWHw-yqeApEdTeuqMNPTDxvdKZ2DuzANmcR2y2CQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C3AE500@ESESSMB209.ericsson.se> <CAJrXDUHCkQSLab2UuY_vWP3Gr8uh+++c9mDq5f4sCpuaK5aeLQ@mail.gmail.com> <51C1B907.8060508@hookflash.com> <CAJrXDUG06jvPvhfNwZ6Puzxj7E4XxELG_fU=S7B_c=tnC9eoNQ@mail.gmail.com> <78192824-A516-4376-8D4F-3B052ED47A0C@matthew.at> <CAJrXDUGOYc_Z_qWD7J0ZzVdfwYOacH_p5PjZEg5aP1LUetffMA@mail.gmail.com> <51C1F2E9.20405@hookflash.com> <51C1F5ED.9090308@matthew.at> <51C20FAA.4050701@hookflash.com> <CABkgnnWw9anT+h_hnF14nBChS73qpTb31hSM=p2KnGrcRPGRJA@mail.gmail.com> <51C3209B.1030501@alvestrand.no>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Thu, 20 Jun 2013 18:15:13 +0200
Message-ID: <CALiegfkEpwxNZL8TU0ofCzRB_Gza+NoSnZpGcM=tuYBOXmHsZQ@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmW0LX2gKaGd81sOFzOExIv2cnYZelpEpq7e1votjs2s8dVtIKBW+r15z1ndadTa4vuE4BU
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened
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, 20 Jun 2013 16:15:35 -0000

2013/6/20 Harald Alvestrand <harald@alvestrand.no>no>:
> I think interoperability with an application written to the implementations
> that are based on the current specifications (that is - a Javascript
> application that you could load into both Chrome and your demo of CU-RTCWeb,
> using a JS shim in your demo, and have them talk to each other) would be a
> pretty compelling argument.

Hi Harald, with all due respect:

So, it seems that the current SDP-based spec is God, and if somebody
wants to propose another alternative, it must be compatible with God,
regardless that God is not yet a proven standard and what some of us
are asserting is that God is bad, very bad. Am I right?

IMHO it would be much more interesting a JS demo that takes the SDP
generated by Chrome and "converts" it into a Jingle XML session
description (I mean XEP-0167), and that can interoperate (via XMPP
over WebSocket or whatever) with a XMPP/Jingle endpoint by
incrementally sending/receiving transport (ICE stuff) and media
capabilities (as XEP-0167 allows) in different XMPP messages.

And it would also be interesting a JS demo that interoperates with a
SIP gateway and is able to perform the "hold" / "unhold" feature so
widely extended in SIP world (via reINVITE with a=inactive/sendonly
and 200 "OK" with a=inactive/recvonly).

It seems that we must prove how bad SDP is while the fact is that
those in favour of the SDP-based model should demonstrate how
"flexible" and powerful it is. As far as we can see in the spec
development, SDP does not seem to be so good and hence it should be
questionable IMHO.

Just my opinion.

Best regards.

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