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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 08 December 2014 17:45 UTC

Return-Path: <ibc@aliax.net>
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 51DBA1A1B76 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 2TchFb4CgZhO for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 09:44:21 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E2F61A1A23 for <rtcweb@ietf.org>; Mon, 8 Dec 2014 09:44:21 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id k15so3594901qaq.24 for <rtcweb@ietf.org>; Mon, 08 Dec 2014 09:44:20 -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:content-transfer-encoding; bh=/FCfss0I6Ulya7/wZR+MoUDrUdrN4DbA5EJtxX++VLE=; b=HG5JmNc5abpqUi2eDdWjKk/J7O2ymsX09kVo0r4AgqqEqKlVCMsfdr41pz9yAErdta /P59TswkK2GU3PfmvB2Ivpox+P2C4ZhGe8O1dKWINCf3ixHfbTHcEk8xn6a0R3rGC74L cLrxaozu3c842LBgFnZetM8Cx01TQmtYRr2/EOKdciYZyLss8iRW923Rnltp3jh1MD8X Pu2M4suvOSur8eM8uzp8kpi2vBh96JveykEPmyRh4an7/06hBz4SnWcSMU2eGWT/ZRJX x3m46Rs4fg7jaodsiIbuQEOUyksxM4YavBSjb9Z+LV64Bd3XDF1FWtzxZ9r1ISaJOc6U GlYQ==
X-Gm-Message-State: ALoCoQnTkhsWuZn974Tx9XtKOFRlE0UXsBmkGhXWYuHCK9ROlQBzqs6tuVcrjk5tWaoriV1WVgz1
X-Received: by 10.140.81.6 with SMTP id e6mr53415569qgd.90.1418060660275; Mon, 08 Dec 2014 09:44:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.26.135 with HTTP; Mon, 8 Dec 2014 09:43:59 -0800 (PST)
In-Reply-To: <CA+9kkMCGp+WdcFomT53qfC2xY8LPYWTtaYiLDBbQ-AZZG1dyOg@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>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 8 Dec 2014 18:43:59 +0100
Message-ID: <CALiegfmrA859s8Q-mBNLhfXQPXShiLHsghZ50-ZpjGbz=RT4hg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/KXWjRDy8xtqRsoL3ywEwc3cjIpQ
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:45:02 -0000

2014-12-05 20:55 GMT+01:00 Ted Hardie <ted.ietf@gmail.com>om>:
> This is fundamentally incorrect.  The IETF writes voluntary standards.  A
> MUST in an IETF standard is not an instruction to a company; it is a
> description of the expected behaviour of an interoperable implementation.
> You are not required to implement the standard at all.  At most, it is a
> description of what someone who claimed compliance to the standard is
> expected to have done.

Let's imagine I want to build a new open-source browser from scratch
in my spare time. Basically (if I was smart enough) I could conform
with all the W3C specs... Really? can I safely include VP8 and H264
(existing libraries or my own implementation of both) into my
open-source browser and publish the project and its source code?

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.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>