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

Peter Saint-Andre - &yet <peter@andyet.net> Mon, 15 December 2014 16:37 UTC

Return-Path: <peter@andyet.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 AFAEA1A6FC4 for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 08:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 2QYh1jEt8DLg for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 08:36:58 -0800 (PST)
Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABC251A797C for <rtcweb@ietf.org>; Mon, 15 Dec 2014 08:36:58 -0800 (PST)
Received: by mail-ig0-f176.google.com with SMTP id l13so5644815iga.15 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 08:36:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hXbHZtJpX4kZz5VQ+iR/M0eIq23hgESO6yDFfJ8oY34=; b=Q5HqpnYLx2/fOy10/RsEaf6RlF9ylME2iN9cS1FJcn8DGeP3Lncuhs63S2ibX271mO +nLCbXUva/pcp8/sRI4Eb+1VMK2kPZOIjNqlhDVv9M/jEA6UctHqQspL1msbwy2hVtnT G4p0aB4B2S1+0P1/qnuIlqyq8E1W5WHvYmcnIiB4SjLjHL+jJB4Y95I/AUbJaFoJ763B 5bjgrpTXMpE5TEKcoEfjGuCU4Dn2xfkwiYqKRMZRYO1sx+LA26bGqZ2AoMMSZkhEbYDv XqjQQj7m3OlLE4zSi4wQ4rSgOuq3h+fgo1bsc54xt+OhUZ+C8Go3+IZWyo3fjQqwyg1A e0Sw==
X-Gm-Message-State: ALoCoQkwVHlwnb0zINLp2egiCaOdaEzBoSKunuQRAkUhRZsxDIveq6htSkUZRR99wMA3logfSzDW
X-Received: by 10.50.66.200 with SMTP id h8mr18815321igt.20.1418661418032; Mon, 15 Dec 2014 08:36:58 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id mv6sm2206718igb.10.2014.12.15.08.36.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Dec 2014 08:36:57 -0800 (PST)
Message-ID: <548F0E28.8040503@andyet.net>
Date: Mon, 15 Dec 2014 09:36:56 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>, Sean Turner <turners@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> <CALiegfnRvgDK4EnDBSn76YKktWLMjShsQRP6byCRqZC07WaVqw@mail.gmail.com>
In-Reply-To: <CALiegfnRvgDK4EnDBSn76YKktWLMjShsQRP6byCRqZC07WaVqw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/5C5XDDucCkfDtzpbDQZ66TWbdGo
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: Mon, 15 Dec 2014 16:37:00 -0000

On 12/13/14, 5:58 PM, Iñaki Baz Castillo wrote:
> 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).

The IETF can *always* obsolete one RFC (e.g., one that says "dual-MTI 
for H.264 and VP8") with another RFC (e.g., one that says "no more 
dual-MTI for H.264 and VP8, we have much better options now"). That's a 
core aspect of the Internet Standards Process.

Peter

-- 
Peter Saint-Andre
CTO @ &yet
https://andyet.com/