Re: [rtcweb] Background info about what is going on WebRTC / RTCWeb

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Tue, 18 September 2012 16:16 UTC

Return-Path: <fluffy@cisco.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 20E6C21E80F2 for <rtcweb@ietfa.amsl.com>; Tue, 18 Sep 2012 09:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsvqXS5AmpSZ for <rtcweb@ietfa.amsl.com>; Tue, 18 Sep 2012 09:16:10 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3225F21E80E7 for <rtcweb@ietf.org>; Tue, 18 Sep 2012 09:16:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1481; q=dns/txt; s=iport; t=1347984970; x=1349194570; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BwHtA0NWNLnc99QsU+igV0pz80tJyNO+oVeNS9a6Qk8=; b=lzc0fAZUsNzE91cCBLXDZ64vE6VqhwS9HElv4kVeFz6G7Wtztp+zLqFA DXy2dNITmNme4Ri5Edk6o76TumM75M4rAncNP60VGi21+RbDLJbojqvbY 3H60HBknPx0aF9a3JtH0ugUb5N7ittGFa+8Bvmtsxnncy1KjTs4BDQNE8 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EANqdWFCtJV2a/2dsb2JhbABFvD+BCIIgAQEBAgEBEgFmEAIBCEYyJQIEDgUih1UDBguaGpFKjnGLG4YQYAOVY4EUjSSBaYJmgWM0
X-IronPort-AV: E=Sophos;i="4.80,442,1344211200"; d="scan'208";a="122824884"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 18 Sep 2012 16:15:51 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8IGFnxX026902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 18 Sep 2012 16:15:49 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.26]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.001; Tue, 18 Sep 2012 11:15:48 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: Background info about what is going on WebRTC / RTCWeb
Thread-Index: AQHNlajJH6A/I7YTL0WO8AV0qbMwGZeQl+KA
Date: Tue, 18 Sep 2012 16:15:48 +0000
Message-ID: <703286B8-BF6E-4D08-A21A-1206FFC9D91F@cisco.com>
References: <A6961A8A-AF3D-4615-AA59-47F46F88968C@cisco.com>
In-Reply-To: <A6961A8A-AF3D-4615-AA59-47F46F88968C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.167]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19190.004
x-tm-as-result: No--27.384800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A7F4C336C4047A438253479D01AF34A1@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Background info about what is going on WebRTC / RTCWeb
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: Tue, 18 Sep 2012 16:16:11 -0000

On Sep 18, 2012, at 8:20 AM, Cullen Jennings <fluffy@cisco.com> wrote:

> 
> I get lots of questions from folks trying to understand what is going on in these working groups so I tried to put together a bit of a  presentation that is my best guess of what the system we are standardizing looks like and helps provide the background info that people can better understand and participate in some of the debates going on. You can find it at
> 
> http://vimeo.com/cullenfluffyjennings/rtcwebexplained
> 
> It is probably wrong in some ways and I know there are parts some folks would disagree with but it is just by best guess given the current information on hand. If anyone wants to use the slides or parts of this for some other presentation, just get drop and email. 
> 
> Cullen
> 

Because a few people asked, there is a VP8 version at 

http://dl.dropbox.com/u/17089001/RtcWeb/RtcWebTake1-360p.webm

PDF slides at http://dl.dropbox.com/u/17089001/RtcWeb/WebRTC_v8.pdf but be warned, they make no sense without a talk track to go with them. 

Cullen

<rant> I've got all the video tools from adobe, apple, and avid but to create this I had to grab the right check in of ffmpeg from the SVN for ffmeg, then apply a patch from some other page, then deal with CLI options that makes cisco router configuration look downright friendly and simple. Ask me how I love living on the bleeding edge … </rant>