Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)

Sean Turner <turners@ieca.com> Tue, 04 November 2014 14:45 UTC

Return-Path: <turners@ieca.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 301231A8937 for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 06:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level:
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, 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 GTH7dN24EzOY for <rtcweb@ietfa.amsl.com>; Tue, 4 Nov 2014 06:45:25 -0800 (PST)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.93.205.23]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55D281A8949 for <rtcweb@ietf.org>; Tue, 4 Nov 2014 06:45:25 -0800 (PST)
Received: by gateway03.websitewelcome.com (Postfix, from userid 5007) id BCD15FAB5D42F; Tue, 4 Nov 2014 08:45:24 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway03.websitewelcome.com (Postfix) with ESMTP id A52CDFAB5D3B7 for <rtcweb@ietf.org>; Tue, 4 Nov 2014 08:45:24 -0600 (CST)
Received: from [173.73.121.234] (port=52068 helo=[192.168.1.7]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <turners@ieca.com>) id 1XlfMJ-0007H0-TV; Tue, 04 Nov 2014 08:45:24 -0600
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Turner <turners@ieca.com>
In-Reply-To: <D2990507-A6EF-499E-B8DA-AF53B3B972CD@cisco.com>
Date: Tue, 04 Nov 2014 09:45:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <872C77E0-99B3-4BBB-9F07-FD371CF6AD5C@ieca.com>
References: <98200BCB-ABC9-4BE0-B11D-B7AEC9F8B2A4@ieca.com> <494EFF62-0914-44B3-9073-F49858293347@gmail.com> <D2990507-A6EF-499E-B8DA-AF53B3B972CD@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 173.73.121.234
X-Exim-ID: 1XlfMJ-0007H0-TV
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([192.168.1.7]) [173.73.121.234]:52068
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 8
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Wc1He8HhJ-L104w1dW9_2Cv62wc
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] The MTI Codec Questions (what to ask and how to ask them)
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: Tue, 04 Nov 2014 14:45:26 -0000

On Nov 03, 2014, at 19:27, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:

> 
> On Nov 3, 2014, at 5:08 PM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
>> The questions below do not make it clear whether we are revisiting the MTI video codec issue or whether in addition the audio codec issue (on which we reached consensus) is also being reconsidered. Please clarify.
>> 
> 
> Bernard, I think I can safely say the chairs were only thinking about the video codec when this was written and that should have been clear on that. 
> 
> That said, there was consensus on 711 and opus being MTI but I think we would need to check carefully the status of if there was consensus that no other audio codecs would be be MTI. But this email was really meant to be about the video codecs. 

Definitely just about the video codecs.

spt