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

Hrishikesh Kulkarni <rishi@turtleyogi.com> Mon, 22 July 2013 19:58 UTC

Return-Path: <rishi@turtleyogi.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 5961811E8112 for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 12:58:30 -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 TckhxB5pmptk for <rtcweb@ietfa.amsl.com>; Mon, 22 Jul 2013 12:58:25 -0700 (PDT)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by ietfa.amsl.com (Postfix) with ESMTP id 809A021F8F07 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 12:58:25 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id s9so16570450iec.27 for <rtcweb@ietf.org>; Mon, 22 Jul 2013 12:58:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ZmOtcMPZWDwrlZJpH2rN4UjFypPvFRddNs0HgF3XTDI=; b=AhUl2Leew4jcfug4zUnKTxiMYC05ZLc6G/swRCNCIqCtrqe3UzYrQ71okpiEwZNRDS ERMajAWtELJoDKUbuPYxBBqUHKNvsmoIRVr4nq1FJ8kEVz8kuQh1KasYZ4nN7d/YwHFw 4sn7PN0W283s5u4XvAnq6YdOnGszBlMp11+s5ol2J9/RJaa95EGJlEzQlK8HAkyteBCi BroprYQC3VN2Dn4VDffZykSQ+WKiICX/54ot4pO4mdH0DHkHNA3Cfi6aJVPhOS2Xi86+ WyEdy3W1hxm+ERefkqSxhNFjQUw2hHK36nKr1bPxYj/wZkN5KpTagXEGQoRt83RVV+Y6 M4Lw==
MIME-Version: 1.0
X-Received: by 10.50.50.244 with SMTP id f20mr11064648igo.21.1374523104963; Mon, 22 Jul 2013 12:58:24 -0700 (PDT)
Received: by 10.64.240.72 with HTTP; Mon, 22 Jul 2013 12:58:24 -0700 (PDT)
X-Originating-IP: [122.166.88.77]
In-Reply-To: <981F1A4D-245A-4F50-9A9C-6F22F00D8AC1@westhawk.co.uk>
References: <51ED4A45.9000703@ik.nu> <CALiegfk1kUuezLSOqfLRnFC7gNWXgjerv9Q_mPKrR01zp3mdqQ@mail.gmail.com> <51ED651B.3000401@goodadvice.pages.de> <CAD5OKxumQ9+=UOch7oXAeju03gFX62m25cDfZwPgR0ET8aFDWQ@mail.gmail.com> <981F1A4D-245A-4F50-9A9C-6F22F00D8AC1@westhawk.co.uk>
Date: Tue, 23 Jul 2013 01:28:24 +0530
Message-ID: <CALFWOz4YL3wOC_03QBKrQ=NTBpZ_eW5pfHm+by9CL1sSVauqig@mail.gmail.com>
From: Hrishikesh Kulkarni <rishi@turtleyogi.com>
To: tim panton <thp@westhawk.co.uk>
Content-Type: multipart/alternative; boundary=047d7bd6be1268331d04e21f19e7
X-Gm-Message-State: ALoCoQkWPeOhyag6IJTKhL4yj5TrzFDE9WggMYLAOZb6BsQ604u1T/eqzu8hWZlMZB5jO5iTla2E
Cc: public-webrtc@w3.org, "rtcweb@ietf.org" <rtcweb@ietf.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 19:58:30 -0000

Yes. It took some effort on our server side for us to support Firefox with
DTLS (still incomplete) as compared to Chrome with vanilla signaling. I
believe we have long way to build interop in browsers: RTP, JS API and
maybe Signaling (with webserver). ScreenSharing policy is yet to be
resolved.

I see this discussion is stuck at JS API vs JS SDP API, while equally
important standards like screensharing policy are in queue.

regards,
Rishi


On Mon, Jul 22, 2013 at 11:49 PM, tim panton <thp@westhawk.co.uk> wrote:

>
> On 22 Jul 2013, at 18:45, Roman Shpount <roman@telurix.com> wrote:
>
> 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?
>
>
> As far as Phono is concerned - yes - but we had to do some work to make
> that happen, more
> work in fact than adding DTLS on the server side, which is (frankly)
> absurd.
>
> T.
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>