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

Peter Saint-Andre - &yet <peter@andyet.net> Fri, 12 December 2014 14:26 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 5FBD51A878C for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 06:26:40 -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 9ziIhGT_EDrm for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 06:26:38 -0800 (PST)
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B3CE1A876F for <rtcweb@ietf.org>; Fri, 12 Dec 2014 06:26:36 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id rp18so7020688iec.11 for <rtcweb@ietf.org>; Fri, 12 Dec 2014 06:26:35 -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=AiBhx/MjdgFYcHtabOGeRMlP9LFa0B9E3d29E72KBv8=; b=JByg9Qcw8ABcYLK/c00gFMM92GjAJaKX6Dk8RNnjeyPmIa2QeO2E5y9Wr9dKMf4dNK zo+Pq28vAgW66AmGPb3IrYMmqxei4Towfxd8dFdIxmwV5ZxxVHEAH4g8/Yv3EWSnl9UU m2bE/PBfNvH5hLOpuN79yBX5YibQgxl4x//EC0cxMr60Dq1VLg7QUChU/ycHyJ1vnk/R owDSStbaM8RE7pV8UA0hdDVwwicjXUwifIfxC4FsQGou45iV04JRJaRhi8u1SRUaLEft S6SQ2Txf9ZTfVdRJYgs3QUovYJF/poUsiyXhXIHhL5GNyHLNHzzhdQv7OoXquob/sl83 R5Jw==
X-Gm-Message-State: ALoCoQkwdlwArSDyDT/PmXYitio0Atq33RZVDwPfW/BFM2jlmFMM/V1iJRbfy9Le14Pe8VnFz2NU
X-Received: by 10.42.251.68 with SMTP id mr4mr16398289icb.94.1418394395782; Fri, 12 Dec 2014 06:26:35 -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 a68sm697706ioe.18.2014.12.12.06.26.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Dec 2014 06:26:35 -0800 (PST)
Message-ID: <548AFB1A.1040405@andyet.net>
Date: Fri, 12 Dec 2014 07:26:34 -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?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>, =?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>
In-Reply-To: <548AD22D.7040104@it.aoyama.ac.jp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/yZimps_-Wu8kuv-8gMUFDBk5sW0
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: Fri, 12 Dec 2014 14:26:40 -0000

On 12/12/14, 4:31 AM, "Martin J. Dürst" wrote:
> On 2014/12/12 20:14, Iñaki Baz Castillo wrote:
>> Question: If the World gets a new "Opus for video" codec, will this WG
>> make it MTI for WebRTC at the same time it removes both VP8 and H264
>> from the list of MTI codecs?
>
> 1) This is a good question. I wish I knew :-).
>
> 2) This is conditional on a hypothetical event in the future ("Opus for
> video"). At that point, this WG may no longer exist. Or it may do
> whatever it pleases (as long as it is within its charter).

Sure, but that can all happen through normal IETF processes (form a new 
WG, write an I-D that obsoletes this dual-MTI solution, etc.).

IMHO it would still be good to address some aspects of the various 
possible scenarios that I mentioned here:

http://www.ietf.org/mail-archive/web/rtcweb/current/msg13754.html

I have it on my to-do list to draft some text.

Peter

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