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

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Thu, 14 November 2013 05:52 UTC

Return-Path: <matthew.kaufman@skype.net>
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 3ACE521E81BC for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 21:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 ITeJs5rT5s3J for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 21:52:01 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) by ietfa.amsl.com (Postfix) with ESMTP id 133B221E81BB for <rtcweb@ietf.org>; Wed, 13 Nov 2013 21:51:56 -0800 (PST)
Received: from DM2PR03CA004.namprd03.prod.outlook.com (10.141.52.152) by BN1PR03MB282.namprd03.prod.outlook.com (10.255.200.21) with Microsoft SMTP Server (TLS) id 15.0.820.5; Thu, 14 Nov 2013 05:51:55 +0000
Received: from BN1AFFO11FD028.protection.gbl (2a01:111:f400:7c10::136) by DM2PR03CA004.outlook.office365.com (2a01:111:e400:2414::24) with Microsoft SMTP Server (TLS) id 15.0.820.5 via Frontend Transport; Thu, 14 Nov 2013 05:51:54 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD028.mail.protection.outlook.com (10.58.52.88) with Microsoft SMTP Server (TLS) id 15.0.815.5 via Frontend Transport; Thu, 14 Nov 2013 05:51:54 +0000
Received: from TK5EX14MBXC266.redmond.corp.microsoft.com ([169.254.2.187]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0158.002; Thu, 14 Nov 2013 05:51:22 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: cowwoc <cowwoc@bbs.darktech.org>
Thread-Topic: [rtcweb] ~"I'd love it if patents evaporated...If not now, when"
Thread-Index: AQHO3/GgARwJeGanTU6NKdKIjPn3QJojYmkAgABCxACAABGPAIAACcuAgAAQ9ACAAGEvAIAAB5PA
Date: Thu, 14 Nov 2013 05:51:21 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A4843D496817@TK5EX14MBXC266.redmond.corp.microsoft.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> <52845DB0.6040501@bbs.darktech.org>
In-Reply-To: <52845DB0.6040501@bbs.darktech.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.35]
Content-Type: multipart/alternative; boundary="_000_AE1A6B5FD507DC4FB3C5166F3A05A4843D496817TK5EX14MBXC266r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(479174003)(377454003)(24454002)(15975445006)(83072001)(76796001)(512954002)(76786001)(69226001)(15202345003)(33656001)(55846006)(63696002)(20776003)(74366001)(74706001)(56816003)(81816001)(54316002)(85306002)(77096001)(56776001)(19300405004)(59766001)(84326002)(77982001)(74876001)(16236675002)(81686001)(44976005)(83322001)(2656002)(19580405001)(74662001)(19580395003)(47736001)(49866001)(65816001)(50986001)(47976001)(81542001)(81342001)(31966008)(71186001)(80022001)(6806004)(87266001)(4396001)(47446002)(80976001)(74502001)(79102001)(66066001)(87936001)(53806001)(76482001)(54356001)(51856001)(46102001); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR03MB282; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0030839EEE
X-OriginatorOrg: skype.net
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:52:08 -0000

Chatroulette (the top trending search term for 2010 and featured on The Daily Show) used Flash and RTMFP to do peer-to-peer video chat. The original Tokbox and their original API was also based on Flash with RTMFP for P2P communications. I'm sure there's others.

Matthew Kaufman

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of cowwoc
Sent: Wednesday, November 13, 2013 9:21 PM
To: Michael Thornburgh
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] ~"I'd love it if patents evaporated...If not now, when"


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> [mailto:rtcweb-bounces@ietf.org] On Behalf Of cowwoc
Sent: Wednesday, November 13, 2013 2:32 PM
To: Kaiduan Xie
Cc: rtcweb@ietf.org<mailto: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.