Re: [rtcweb] ~"I'd love it if patents evaporated...If not now, when"

cowwoc <cowwoc@bbs.darktech.org> Thu, 14 November 2013 05:21 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 7468A21E81B3 for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 21:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.151
X-Spam-Level:
X-Spam-Status: No, score=-4.151 tagged_above=-999 required=5 tests=[AWL=-0.553, BAYES_00=-2.599, 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 YG-EVPj1hHdY for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 21:21:07 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6737121E81B0 for <rtcweb@ietf.org>; Wed, 13 Nov 2013 21:21:07 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id x13so2057108ief.18 for <rtcweb@ietf.org>; Wed, 13 Nov 2013 21:21:06 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=dyIdEdfuxPR82AmKCeQ7EQ/3MlFyjuMF/LW2zNaHsaI=; b=iiW9KR5c7ROhrY0wfLOOo5UwYHs6V9dHergbLsQfEs8IMGxC8jQ/8zofhx9jAYioch Z1XfUkg++OkNGAZ5VPTlEUkoWgJF5FxjqVWHVfy7kLI1hdQN1fs3krLDmloNZaM6VOOT PJkIxx8yqmg1hSC14vIz5i3YTdWM7mJXcZInH9oCpeB9mZsTmovHrv/xcIICFGVizwt9 0zEFiXV9wt9EBoy+5L+eqirRbdLWNjaZA1w1whuMP9uIbnvEOe4YB5YaDO9vMV1cZCT2 wuLLryB5D+jg/UjRD+brllfoFQm12M+p1yssBBFOtQ6SOgN2tPet7QpvhHLwstT8yYAB Jn2A==
X-Gm-Message-State: ALoCoQmqH+DB+UGaSaWwd686y95HW9Sc3ycrZ2SMmO4lKGHQUvrzyyueE5tAVE5LDXY3UnCiU1ZE
X-Received: by 10.50.78.196 with SMTP id d4mr399255igx.2.1384406466758; Wed, 13 Nov 2013 21:21:06 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id ka5sm34585371igb.2.2013.11.13.21.21.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Nov 2013 21:21:05 -0800 (PST)
Message-ID: <52845DB0.6040501@bbs.darktech.org>
Date: Thu, 14 Nov 2013 00:20:48 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Michael Thornburgh <mthornbu@adobe.com>
References: <5282A340.7010405@gondwanaland.com> <20131113165526.GA13468@verdi> <5283E700.5090300@bbs.darktech.org> <CACKRbQf=x-wKUFemNhf4ZDwgZzqBFq=okUMw=BLCwaMmE7OJPw@mail.gmail.com> <5283FDF1.8030708@bbs.darktech.org> <D9D602D39A98E34D9C43E965BEC7439834E61DE3@nambx08.corp.adobe.com>
In-Reply-To: <D9D602D39A98E34D9C43E965BEC7439834E61DE3@nambx08.corp.adobe.com>
Content-Type: multipart/alternative; boundary="------------030804050309070006030602"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] ~"I'd love it if patents evaporated...If not now, when"
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: Thu, 14 Nov 2013 05:21:13 -0000

Really? I've never seen a single P2P video chat app in Flash. What 
specifically does "P2P for real time communication" actually mean?

Gili

On 13/11/2013 6:32 PM, Michael Thornburgh wrote:
>
> > The real revolution is P2P: massive cost savings, ease of deployment 
> and most importantly: cutting out the middle man. The status quo 
> (H.264 over Flash) does not do this.
>
> note: Flash has had P2P for real time communication since 2009.
>
> -michael thornburgh
>
> *From:*rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] *On 
> Behalf Of *cowwoc
> *Sent:* Wednesday, November 13, 2013 2:32 PM
> *To:* Kaiduan Xie
> *Cc:* rtcweb@ietf.org
> *Subject:* Re: [rtcweb] ~"I'd love it if patents evaporated...If not 
> now, when"
>
>
> I agree. I'm just pointing out that John's argument (quoted below) 
> doesn't make any sense. Choosing "no MTI" doesn't make Cisco any more 
> likely to implement VP8.
>
> If we choose "No MTI" we will end up with transcoding, plain and 
> simple. One crowd will only implement H.264. The other crowd will only 
> implement VP8. All the useless middlemen will rejoice, having killed a 
> technology that puts them out of business.
>
> Providing "video chat without a plugin" is not revolutionary. Flash is 
> already installed on 95% of the market. That's more people than WebRTC 
> can reach today, so we're not "liberating" those people from anything.
>
> The real revolution is P2P: massive cost savings, ease of deployment 
> and most importantly: cutting out the middle man. The status quo 
> (H.264 over Flash) does not do this.
>
> P2P cannot work unless 95% of clients can agree on a common codec. I 
> say again: start with H.261 and upgrade to VP8 or H.264. This way 
> everyone can be happy:
>
>   * The VP8 crowd can use VP8
>   * The H264 crowd can use H264
>   * The enterprise crowd can transcode
>   * If all of the above fails, we can fallback on H.261.
>
> Yes, this carries the burden of implementing H.261 but this is a 
> solved-problem. There are plenty of free implementations and is a much 
> easier problem to solve than getting the H.264 and VP8 crowd to agree 
> to implement each other's codec.
>
> Start with H.261 and replace it the moment you find something better. 
> Forcing us to transcode or drop video calls is not a solution.
>
> Gili
>
> On 13/11/2013 4:57 PM, Kaiduan Xie wrote:
>
>     "if an implementer gets sued they can simply drop the codec"
>
>     Thing is not that simple as "simply drop the codec", for some case
>     you still have to pay a lot of money.
>
>     /Kaiduan
>
>
>     On 13/11/2013 11:55 AM, John Leslie wrote:
>
>                 And I claim that both camps are actually more likely
>             to implement
>             (or allow extensions for) the other side's codec if it is
>             _not_ MTI,
>             simply because they can back out at the first sign of lawyers.
>