Re: [rtcweb] confirming sense of the room: mti codec

Iñaki Baz Castillo <ibc@aliax.net> Sun, 14 December 2014 00:58 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 9A5E51A0389 for <rtcweb@ietfa.amsl.com>; Sat, 13 Dec 2014 16:58:54 -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 G_PIydH_7dWJ for <rtcweb@ietfa.amsl.com>; Sat, 13 Dec 2014 16:58:53 -0800 (PST)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFDD81A036A for <rtcweb@ietf.org>; Sat, 13 Dec 2014 16:58:53 -0800 (PST)
Received: by mail-qa0-f47.google.com with SMTP id s7so6684324qap.6 for <rtcweb@ietf.org>; Sat, 13 Dec 2014 16:58:53 -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=2zWlhjBbrAP7n9RecGO29zi9GVI8EUTGJEyoA66s0gs=; b=XozGQ39c1AoOTqp7UUmsvLlotbbvYXIeg33sbxGwdvqdr/o0H9VwWAoXx6HQY9wAQw a/CmlMw8IPGW4Bbmf2G17t5K1Yp0kdu5FW3fPW4tr7ZPHDfON0eoHO+5A/+8WnwIH9T3 f4kr8ohx89zWI4+NdfD/nvDxFGQLUuTjKUWpFPnru1LViozUEm8x8kOhrG1a2vua6IKF VjZtW5/OtYb8uNiVOPSNR/NAHWA3q39Y6vMfUG2xCsCA6MD3QKJ0pZxd0MY2GgmXVLLu Ti/be/W0I4RJFY+bNt1jpbu/rvZvXUwUolkUQ4ZoYqCNwbEjxEWVdaUwHlE02H0EX3Nd 6RCg==
X-Gm-Message-State: ALoCoQlJtefd/WA45u4bLuySRrfjoQFr3kNFG5VHzEf4NmlxftNuA43p05bOhcwaqda/pohifkjr
X-Received: by 10.229.37.136 with SMTP id x8mr44323552qcd.30.1418518732936; Sat, 13 Dec 2014 16:58:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.26.135 with HTTP; Sat, 13 Dec 2014 16:58:32 -0800 (PST)
In-Reply-To: <B52D8E91-5D96-4960-8DDE-DD970014DE5D@ieca.com>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <CALiegfmuO6m=FfSQ9b9i_cu+_0eUSbxTtMh0_9kNCk9BLf-iuA@mail.gmail.com> <548AD22D.7040104@it.aoyama.ac.jp> <548AFB1A.1040405@andyet.net> <548AFF76.1010003@nostrum.com> <CALiegfmH6hWp6nuArv8YyPcgq6SCd9x-dU0cxAaKJLrmb0hc_g@mail.gmail.com> <548B047F.9090704@nostrum.com> <56448CBD-FB31-4468-B449-497652FCAAEB@apple.com> <548B7EFF.5080105@andyet.net> <CALiegfkMUzQVOKk433d4TZtvenQWQwChYF2vc7HMED2s2wHZ5Q@mail.gmail.com> <B52D8E91-5D96-4960-8DDE-DD970014DE5D@ieca.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sun, 14 Dec 2014 01:58:32 +0100
Message-ID: <CALiegfnRvgDK4EnDBSn76YKktWLMjShsQRP6byCRqZC07WaVqw@mail.gmail.com>
To: Sean Turner <turners@ieca.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/MNC3uGw5QRRFKnXNpfy1T7stXcM
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] confirming sense of the room: mti codec
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: Sun, 14 Dec 2014 00:58:54 -0000

2014-12-13 17:36 GMT+01:00 Sean Turner <turners@ieca.com>om>:
> Just to be clear:  "No plan" does not mean that the requirement is immutable forever, just that we don't have a plan right now.  MTI requirements in IETF documents can always be updated, and they very frequently are.

That sounds good, but I'm still waiting for a response to my question
made yesterday:

>>  The rationale here is browser accommodation for very constrained "WebRTC compatible" devices, which will most typically be concerned with browser interoperation. The example that's been tossed around in this space is the "WebRTC doorbell" -- when someone rings the bell, you navigate to its interface using WebRTC, and stream an image from a small, embedded camera. In these kinds of very-low-cost devices, you're going to likely see hardware video encoding (e.g. do a web search for NVS2200), which will likely be one codec or another, but not both.
>>
>> The goal is continued browser support for such devices in perpetuity.

> May I know where in the WG chapter is that goal defined please?


If the above is a real goal of this WG (is it?) then that means that
future revisions should respect it ad aternum. This is: even if in the
future a new *good* video codec 100% RF appears, implementations MUST
still include both VP8 and H264 (and deal with patent/licensing
issues, which is a show stopper for certain players in the web
ecosystem).



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