IETF Logo Mail Archive

Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

Iñaki Baz Castillo <ibc@aliax.net> Mon, 22 July 2013 17:51 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 187C811E811F for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 10:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[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 1dhzFpjkn8Cb for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 10:50:55 -0700 (PDT)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD3111E8122 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 10:50:43 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id u12so3762338qcx.40 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 10:50:38 -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=inHUwQwgo14azRQm8mpT46lrosLTgK41FIMHZrAQ8mw=; b=FWh5h/o2EQZ08t5j9maUX/nWM25H88YOOOn8HQKVer4NU3FF7UgVrtIXLROHzOATVR WkOzeNMVZg30UB7leYqaFlODy6+d+90SE/9h8k9ZM6mL8/9HWvPwYKxUdTxTTSMtl0e7 YkeK3wNauziYq5QHPuK75Hl/KLoG2vG/9rFbRHxVLboXyxPE+EiAcpNfdn6nZlvyOUBP PqhjwDklwBvav0AnjAVHI25HTM3trywLAxwJqyIP4zG14HFDGbDbDwRgoW81/svSwy8z VHONJe6Ct+uS+0WStZ0PXuiZON6CwEZKN3hV3u0xyaW82TiBNc+fIfz5iVqSvrtiLknX +Wow==
X-Received: by 10.224.182.79 with SMTP id cb15mr35545818qab.48.1374515438059; Mon, 22 Jul 2013 10:50:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Mon, 22 Jul 2013 10:50:17 -0700 (PDT)
In-Reply-To: <CAD5OKxumQ9+=UOch7oXAeju03gFX62m25cDfZwPgR0ET8aFDWQ@mail.gmail.com>
References: <51ED4A45.9000703@ik.nu> <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com> <51ED651B.3000401@goodadvice.pages.de> <CAD5OKxumQ9+=UOch7oXAeju03gFX62m25cDfZwPgR0ET8aFDWQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 22 Jul 2013 19:50:17 +0200
Message-ID: <CALiegfmLO8PM+tsoJ0U0-+tB8m=o_ORZXP5qu3McMV-HeaRmcg@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkBq923/JlRVB7qxM9WO14iJLLfxdt/sE7hkuQU+aPjcb+okPxueyU5SMZ0AwTRq3R7sUG2
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>, XMPP Jingle <jingle@xmpp.org>
Subject: Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.
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, 22 Jul 2013 17:51:00 -0000

2013/7/22 Roman Shpount <roman@telurix.com>:
> On Mon, Jul 22, 2013 at 1:00 PM, Philipp Hancke <fippo@goodadvice.pages.de>
> wrote:
>>
>> I said this before, but since you insist on repeating your argument i'll
>> repeat mine: I have running code doing exactly that.
>>
>> It's hard work and there are some points where this is PITA, I have
>> discovered numerous bugs in chrome (and the jingle spec) along the way, but
>> it's certainly not unfeasible.
>>
>
> Out of curiosity, does the same code work with Firefox?

And will it work with Opera, IE and any other browser without adapting
the code to the SDP those browsers will produce? and will it remain
working in future versions of Chrome and other browsers?

If it was a real JS API and the browsers properly implement it, then
the answer to all these questions would be "yes". But since this is
about dealing with a SDP blob string that can be represented in many
"compatible" ways by different browsers, I don't see it clear
(regardless I don't doubt at all about the quality of the JS code
which seems really good).

Regards.


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

v2.23.0 | Report a Bug | By Email