IETF Logo Mail Archive

Re: [rtcweb] Finishing up the Video Codec document, MTI (again, still, sorry)

Martin Thomson <martin.thomson@gmail.com> Mon, 08 December 2014 17:49 UTC

Return-Path: <martin.thomson@gmail.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 F068C1ACD32 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 WgLLpsQ31PF2 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:49:40 -0800 (PST)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C52C1A1AAE for <rtcweb@ietf.org>; Mon, 8 Dec 2014 09:49:40 -0800 (PST)
Received: by mail-oi0-f47.google.com with SMTP id v63so3711665oia.6 for <rtcweb@ietf.org>; Mon, 08 Dec 2014 09:49:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=SDqW5utsUQxSDI0fDwARc/TByr0BqA8qNZN3oDYZUH8=; b=t0COnYq4Wl3XXvWnBON/M78v/gEUCUJ0kxnGMz4rIN+WtDblSAMsCUPmOJGyJJnVNv FPROTmFEZoSbHdkGlcS02TlwfZ9pINe0Spyrwce2plHRtLFtZca1QWCGRTdPdkBkBHdR p61K0df+GeuuVVoLJkNtfig0O1Twr6oE1ZaBh6Q8z/1w+BWMNHJACLb0Aye7Fddu900U Gjk3bfuasATyhVrif5l5iVQxSVaUyoiw1tcvMtPW/Cf8R+8B97bUx7FYWtbMHWqJ+Wwi 21wejdr5ORm3YoBW4aXN+iBInbqwFTOYmHt3ROxOX3JnqyXJRZ+HCft5HY0qRRKJeqqu w2+w==
MIME-Version: 1.0
X-Received: by 10.182.104.40 with SMTP id gb8mr20647546obb.61.1418060979796; Mon, 08 Dec 2014 09:49:39 -0800 (PST)
Received: by 10.202.115.4 with HTTP; Mon, 8 Dec 2014 09:49:39 -0800 (PST)
In-Reply-To: <CALiegfmrA859s8Q-mBNLhfXQPXShiLHsghZ50-ZpjGbz=RT4hg@mail.gmail.com>
References: <547511DB.5050100@nostrum.com> <54759A4C.6020806@gmail.com> <5476092D.4010406@nostrum.com> <15EF2452-2C2C-420B-B972-C37EACE57850@apple.com> <CALiegfkbiN1BAaJyrqOzUeYiViCGHcs6QaM7VVHwUzCUVAuKBw@mail.gmail.com> <32C6F602-6818-4A36-B18E-BF21774F6761@apple.com> <20141205035706.GB21150@hex.shelbyville.oz> <C56EF8F1-FE24-4DF9-9869-49795BD34AC1@apple.com> <CA+9kkMCGp+WdcFomT53qfC2xY8LPYWTtaYiLDBbQ-AZZG1dyOg@mail.gmail.com> <CALiegfmrA859s8Q-mBNLhfXQPXShiLHsghZ50-ZpjGbz=RT4hg@mail.gmail.com>
Date: Mon, 08 Dec 2014 09:49:39 -0800
Message-ID: <CABkgnnX+hNj8q=EoGbEeP0z-kprSYRaY=7i_WABCuKXnKNsx9w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/UIa_3Ymxq_hu3CsRhheH5tC1XDs
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Finishing up the Video Codec document, MTI (again, still, sorry)
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: Mon, 08 Dec 2014 17:49:42 -0000

On 8 December 2014 at 09:43, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> The "MUST implement VP8 and H264" is a break line in the W3C, meaning
> that from now on just big vendors (those who can deal with licensing
> stuff) can conform with the specifications. And that is no good at
> all.

To the extent that this is true, it is true already.  If you want to
create a competitive browser, you need significant resources.  At any
one time, you need to have about this much work in flight, even once
you reach parity: https://status.modern.ie/

However, calling out codecs as being special is ridiculous.  Firefox
manages, therefore this hypothetical new player could do the same
thing.

v2.23.0 | Report a Bug | By Email