Re: [rtcweb] Making both VP8 and H264 MTI

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 08 November 2013 07:46 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 6C0E011E8193 for <rtcweb@ietfa.amsl.com>; Thu, 7 Nov 2013 23:46:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level:
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[AWL=-1.945, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 ZTdgbKqCD9oL for <rtcweb@ietfa.amsl.com>; Thu, 7 Nov 2013 23:46:10 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id B924211E821A for <rtcweb@ietf.org>; Thu, 7 Nov 2013 23:46:09 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id rA87jqNZ014495; Fri, 8 Nov 2013 16:45:52 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 493a_0c59_caf40650_4849_11e3_969a_001e6722eec2; Fri, 08 Nov 2013 16:45:51 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id EE441BF54D; Fri, 8 Nov 2013 16:45:51 +0900 (JST)
Message-ID: <527C96A6.5070008@it.aoyama.ac.jp>
Date: Fri, 08 Nov 2013 16:45:42 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: David Singer <singer@apple.com>
References: <CE9E91B2.1BEAA%mzanaty@cisco.com> <8EB7C7F2-105D-4CFB-AC06-F8BB331A4736@cisco.com> <5279339B.9040506@bbs.darktech.org> <E44893DD4E290745BB608EB23FDDB7620A108AAB@008-AM1MPN1-041.mgdnok.nokia.com> <CAMwTW+g+iHWCkoUonjYFi6OrSNcSQZX2X4GtKG5Ae4Ubzv0LtA@mail.gmail.com> <A869F270-C9B9-48EE-9A71-75BA9F2684EC@apple.com> <527A06EF.2070007@bbs.darktech.org> <527A0C4D.7020707@gmail.com> <527A15A3.2090006@bbs.darktech.org> <CA+E6M0mrrj+hKgxkXyvsd+J1yLVV0WAtM_MsNP4qcFkd8F15hA@mail.gmail.com> <9D0FB49D-EF67-4C21-A818-A611F9325EFF@apple.com> <527BAA17.40705@bbs.darktech.org> <99C1B7D8-7E90-4FF4-9F31-D18F2F4E4D40@apple.com>
In-Reply-To: <99C1B7D8-7E90-4FF4-9F31-D18F2F4E4D40@apple.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Making both VP8 and H264 MTI
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: Fri, 08 Nov 2013 07:46:16 -0000

On 2013/11/08 9:14, David Singer wrote:

> For a start, not everyone would have to transcode, only those cases where there the two ends implement only one, and different, codecs.
 > Secondly, I didn't say it was ideal, I I said it was better than 
saying nothing.
 > Third, if you implement both, you would never need to use a 
transcoder for this reason, but you nonetheless might use a bridge or 
intermediary for a whole host of other reasons.

Would Apple implement both? Would Google implement both?

(As I understand it, Mozilla will implement both.)

Regards,   Martin.