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

Roman Shpount <roman@telurix.com> Mon, 22 July 2013 17:45 UTC

Return-Path: <roman@telurix.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 BB8E611E8140 for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 10:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 mwMAKWhb6vbN for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 10:45:46 -0700 (PDT)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4F40C11E812A for <rtcweb@ietf.org>; Mon, 22 Jul 2013 10:45:45 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id t59so6139616wes.6 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 10:45:45 -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:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=zl/eTam5GKqgrKHApUYZlp+ciU0amf/EiTs2VMZ5VVk=; b=dYIMiIdHJK0Z7ONulgOFodMcE5DZv6b7BFaxRmr2hkBpSJOo8qqGZmXIz/6e77blFi BCBjIyt+dKxMqGF6OGgySLM6xGUFFblPG/Ztjtmw6Nc9U9aHgQ7PSS1ELp/KGgFEDx09 tHPJ4JgoxgmVvaDmlTGiDCNPa5iPvt2bEEfrO9a3L0eF6aPayvfRK6A+VAZjP0VGEFg8 3sHojmkySVV6xQv0HDHoowSROgZeQaKf36M9zaEaG9K2d6w4nrqhAd+wST7o7JSm4r/7 5V6Y3NglUKImvCSHdL8IIT/3obfK9x0RoQndivnXETcFXZ9mXiZYNXEUvKpsyr+6zmD1 FeeA==
X-Received: by 10.180.107.71 with SMTP id ha7mr19058630wib.28.1374515145193; Mon, 22 Jul 2013 10:45:45 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [2a00:1450:400c:c00::22f]) by mx.google.com with ESMTPSA id fb2sm506266wic.4.2013.07.22.10.45.44 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 10:45:44 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id j13so1375999wgh.14 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 10:45:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.21.209 with SMTP id x17mr19112325wie.47.1374515143516; Mon, 22 Jul 2013 10:45:43 -0700 (PDT)
Received: by 10.216.221.202 with HTTP; Mon, 22 Jul 2013 10:45:43 -0700 (PDT)
In-Reply-To: <51ED651B.3000401@goodadvice.pages.de>
References: <51ED4A45.9000703@ik.nu> <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com> <51ED651B.3000401@goodadvice.pages.de>
Date: Mon, 22 Jul 2013 13:45:43 -0400
Message-ID: <CAD5OKxumQ9+=UOch7oXAeju03gFX62m25cDfZwPgR0ET8aFDWQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Philipp Hancke <fippo@goodadvice.pages.de>
Content-Type: multipart/alternative; boundary="047d7b874000de284f04e21d3e2b"
X-Gm-Message-State: ALoCoQl14EB7EQglxFyCaF+RvIr6iQX1DO+krDf0jYP3Zn70/bGSmQMEkk//CNdfnHr5rYcDEZ/b
Cc: XMPP Jingle <jingle@xmpp.org>, rtcweb@ietf.org, public-webrtc@w3.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:45:51 -0000

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?
_____________
Roman Shpount