[rtcweb] JS friendly codec compromise?

Zach Lym <zachlym@indolering.com> Tue, 01 April 2014 22:14 UTC

Return-Path: <indolering@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 350751A0A3E for <rtcweb@ietfa.amsl.com>; Tue, 1 Apr 2014 15:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y_9CTD6tUcVF for <rtcweb@ietfa.amsl.com>; Tue, 1 Apr 2014 15:14:31 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4217E1A0A29 for <rtcweb@ietf.org>; Tue, 1 Apr 2014 15:14:31 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id rr13so10472267pbb.25 for <rtcweb@ietf.org>; Tue, 01 Apr 2014 15:14:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=CN3n1KmEn0B5GJgJa+YO01zAQeiQfPXIoYd5HxCVEr8=; b=mUAL2ARphaGkPFp9Jzt38kgM3fElgRY4gUXI0LVYfY3lgC/43hHuftX5qQ+0yqD05X BG0KzkfMQvchFeUV9keFRIwsYyl07ppi3sNqItVHyRNMmTQffM5K2OAgc4snoUBM+lMs ANo5YSDgSoPTGG0M+HvPf8umk6768QDFsJgLBketyICPM1+B3TuHo9NdTTxROrmiPLcg 0YlUGFsJz0ek/1bOmVo6A/YCY4p1HrmgVQLwfGi+d53MUL8HjHB5iqi5RfkN8xsTzvQS LmPR8EWt7hueBYC6rrYgWcHdWgW9H4gajY6YNiggUoclKO/2MCHowRjyPMhwRtMK2l3R 51tA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=indolering.com; s=google; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=CN3n1KmEn0B5GJgJa+YO01zAQeiQfPXIoYd5HxCVEr8=; b=hRsAmC5JnsAZ2kPA5bw9E79CRy9O172AFCGw5TSr/2TojNtpwpl81BTPOY+/zLnsYu QvYSxfW7qwuMAxLcdluJjca+b8mUN4t0d9rSX0YH2XdtfUMzgxxpLZ1KU9Fz4AGZfWH3 l0JYqitfYk+MFYx1/YN4gmeVokbPveEA0Ve0k=
X-Received: by 10.66.176.143 with SMTP id ci15mr34151931pac.35.1396390467673; Tue, 01 Apr 2014 15:14:27 -0700 (PDT)
MIME-Version: 1.0
Sender: indolering@gmail.com
Received: by 10.70.64.194 with HTTP; Tue, 1 Apr 2014 15:13:47 -0700 (PDT)
From: Zach Lym <zachlym@indolering.com>
Date: Tue, 01 Apr 2014 15:13:47 -0700
X-Google-Sender-Auth: rr614pzkz7oBvwlfMmKFFyFJxM4
Message-ID: <CABWuLVey==ZNYog1iLkWiy3Ec6JkOASDPkjg-7BLLenvxf4q+w@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="047d7bd75160cb24c904f6027dd7"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/rwpTgiL2ErCNijkbOqQyE0zZw48
Subject: [rtcweb] JS friendly codec compromise?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 01 Apr 2014 22:14:34 -0000

After reviewing the discussion on the codec mandate (particularly h.261) I
was reminded of ORBX.js.

While I have my reservations regarding ORBX, the approach (a JS friendly
codec) would be more backwards compatible than h.261 and give better
performance.  If a "submarine" patent surfaces the codec can be altered and
clients can be "updated" on the next page refresh.

I should stress the "JS friendly" aspect of the codec, "VP8 like H.264 does
not parallelize as well via WebGL as ORBX does, so a "JS shim" is not going
to compete."  - Brendan Eich

Thank you,
-Zach Lym
P.S. For those who are not familiar with ORBX, it is a codec which is
decoded in JS and transmitted over websockets.  Their timeline (
http://render.otoy.com/newsblog/?p=317) mentions a FOSS encoder sometime
this summer, funding for a pure WebGL/CL encoder, and fee-free AMI's for
video transcoding.