Re: [rtcweb] H.261

Eric Rescorla <ekr@rtfm.com> Fri, 22 November 2013 20:18 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5391AE022 for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 12:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcU3VviUh1xv for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 12:18:15 -0800 (PST)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id AFBCD1AE25E for <rtcweb@ietf.org>; Fri, 22 Nov 2013 12:18:14 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id ca18so1278494wib.10 for <rtcweb@ietf.org>; Fri, 22 Nov 2013 12:18:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7auH295j4st3vlYQHW58jys/wgLBx+R7tpHAqSKzsxA=; b=DvyoMmhnNFkgWqtd1rL4+SltEo9SS5VG5vWhNLkFLJ0oKuQBWGTMKiL5+xc+xZ4jHN 2eImwoBrgrELrarsQlgYVa0my4bEp18fUmDgBSij32Jyz/jwCfeGxT9FABthyC9HOx49 7QT4GuDbnG92kkVs/Fy1FzSdUwcwXHwyaXc8hdZaVVnjMXCwjtstyzqphKWj//opuHpR uoivTRyBSGOCW6+3e6qolx0K5EBg9luJSFRwcI1JlI7yFlRAZs9ElgizRufWlhfpUefL 7P9kbg+j+eWASRA9w9iEwUEVdsigSM4kA9wSBcYDg2k4V03Cljf5+wE21N1kIedSaQ51 ivHA==
X-Gm-Message-State: ALoCoQk2CiFFQC1KfH66gCZ1GilVpmJK1NQ0JaHbK9j11LbK9TY6J167BYmPMBCl1eZUZTIcg5NE
X-Received: by 10.180.205.233 with SMTP id lj9mr4153906wic.24.1385151485857; Fri, 22 Nov 2013 12:18:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.152.137 with HTTP; Fri, 22 Nov 2013 12:17:25 -0800 (PST)
X-Originating-IP: [63.245.220.224]
In-Reply-To: <20131122201228.GA3245@audi.shelbyville.oz>
References: <CEB4350B.1E7B2%mzanaty@cisco.com> <20131122171020.GY3245@audi.shelbyville.oz> <7949EED078736C4881C92F656DC6F6C130EA9E66AF@ausmsex00.austin.kmvtechnologies.com> <528F9DAD.3030300@googlemail.com> <7949EED078736C4881C92F656DC6F6C130EA9E66DE@ausmsex00.austin.kmvtechnologies.com> <528FAAA8.8060807@googlemail.com> <7949EED078736C4881C92F656DC6F6C130EA9E66FE@ausmsex00.austin.kmvtechnologies.com> <20131122201228.GA3245@audi.shelbyville.oz>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 22 Nov 2013 12:17:25 -0800
Message-ID: <CABcZeBMm7BOkpenp+se+BuQLyr0nBpaeCRSsBYFvqbBsyb4CNA@mail.gmail.com>
To: Ron <ron@debian.org>
Content-Type: multipart/alternative; boundary="001a11c261284667c204ebc9b68d"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] H.261
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Nov 2013 20:18:16 -0000

On Fri, Nov 22, 2013 at 12:12 PM, Ron <ron@debian.org> wrote:

> On Fri, Nov 22, 2013 at 01:30:34PM -0600, Stefan Slivinski wrote:
> > No, this is taking things to extremes.  This codec hasn't been used in
> any
> > industry for 15 years.  The entire video conferencing industry uses
> H.264,
> > the broadcast industry uses H.264, the streaming video industry uses
> H.264,
> > facetime, skype both use H.264.  The list goes on and on.
>
> And this working group exists precisely _because_ the other solutions in
> existence today all have obvious failings.
>

Well, all technologies have failings--generally obvious ones--but it's
certainly
not correct that RTCWEB exists because of failings in the media codecs
used by previous solutions.

-Ekr