Re: [rtcweb] Interoperability between browsers (MTI Video)

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 16 March 2013 20:58 UTC

Return-Path: <bernard_aboba@hotmail.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 C759C21F8464 for <rtcweb@ietfa.amsl.com>; Sat, 16 Mar 2013 13:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level:
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 JkdDgiRieKVk for <rtcweb@ietfa.amsl.com>; Sat, 16 Mar 2013 13:58:06 -0700 (PDT)
Received: from blu0-omc2-s24.blu0.hotmail.com (blu0-omc2-s24.blu0.hotmail.com [65.55.111.99]) by ietfa.amsl.com (Postfix) with ESMTP id 46F0921F8463 for <rtcweb@ietf.org>; Sat, 16 Mar 2013 13:58:06 -0700 (PDT)
Received: from BLU404-EAS209 ([65.55.111.72]) by blu0-omc2-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 16 Mar 2013 13:58:06 -0700
X-EIP: [s2ybKojTdV/rmuF61U4hrjbyeJpdFrl4]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU404-EAS20940F539D932EDF3B15BBD93EE0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
References: <CAGgHUiQPNSOEtffncjXMozxPM70hL9N++sM=RkC6qVFGSFNREA@mail.gmail.com> <05D1DDF1-A153-41F2-9726-351AA22075C4@acmepacket.com>
From: Bernard Aboba <bernard_aboba@hotmail.com>
MIME-Version: 1.0 (1.0)
In-Reply-To: <05D1DDF1-A153-41F2-9726-351AA22075C4@acmepacket.com>
Date: Sat, 16 Mar 2013 16:58:07 -0400
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-OriginalArrivalTime: 16 Mar 2013 20:58:06.0047 (UTC) FILETIME=[F4EE2EF0:01CE2288]
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Interoperability between browsers (MTI Video)
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: Sat, 16 Mar 2013 20:58:06 -0000

On Mar 16, 2013, at 16:08, "Hadriel Kaplan" <HKaplan@acmepacket.com> wrote:

> I agree this would be better than nothing, as mentioned on the thread titled "Video Codec MTI & User Experience == 1".
> I also asked a few vendors after this week's meetings whether their existing devices support H.261, but they didn't know. 

[BA] H.261 is so old and moldy that most vendors ripped it out long ago.  I went through a dozen different video clients and couldn't find any that supported it (though H.263 was included in some cases).