IETF Logo Mail Archive

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

David Singer <singer@apple.com> Fri, 12 December 2014 23:42 UTC

Return-Path: <singer@apple.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 865D61A017C for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 15:42:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qXaIxNFmHHE9 for <rtcweb@ietfa.amsl.com>; Fri, 12 Dec 2014 15:42:33 -0800 (PST)
Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E7141A0012 for <rtcweb@ietf.org>; Fri, 12 Dec 2014 15:42:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1418427753; x=2282341353; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=zfbARzHStaaEZK7f0wxr2aGWsynKhyzoZPI2ik8+hqk=; b=eGFLpsJWf2/daAe1h/8wbYEFd+k5Kslj9bu3jHKg63MsqVzRWQAdgj+hT6oxTUxr /4UuSkgIqa3Z0troBnE6DlqJZkg1fEsfEyAd0nYyR0Y4YEkpP6TG9bjObW6rQK9C SCCSZhrTe7UbG87UvKv6VPENhAhUfWIo15UbK7ZcEmXLv1DqlOcMc9lxwXontCOU XtXT2Fbwzt/Ss4cyoSj+wDKPNct/pbPvGr/7fK9ZLnxnarHumwylUgpaYHj0AK/F Ry2cwqZJqVZ84I5vYn7CUWiAjOHwO8TbA+6s4A4JmrdTt+Fpsil65DxOBdQq8aXg wa8I4sN3kTZ4dknuVHY6AA==;
Received: from relay7.apple.com (relay7.apple.com [17.128.113.101]) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id DB.64.12074.96D7B845; Fri, 12 Dec 2014 15:42:33 -0800 (PST)
X-AuditID: 11973e12-f79f86d000002f2a-e3-548b7d6910fd
Received: from marigold.apple.com (marigold.apple.com [17.128.115.132]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay7.apple.com (Apple SCV relay) with SMTP id 06.9D.06091.94D7B845; Fri, 12 Dec 2014 15:42:01 -0800 (PST)
Received: from singda.apple.com (singda.apple.com [17.201.24.241]) by marigold.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NGH00BCFTUWLJ70@marigold.apple.com> for rtcweb@ietf.org; Fri, 12 Dec 2014 15:42:32 -0800 (PST)
Content-type: text/plain; charset="windows-1252"
MIME-version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: David Singer <singer@apple.com>
In-reply-to: <92D0D52F3A63344CA478CF12DB0648AADF3607F5@XMB111CNC.rim.net>
Date: Fri, 12 Dec 2014 15:42:32 -0800
Content-transfer-encoding: quoted-printable
Message-id: <B26E4D5D-800A-4B55-BB36-9AFEDA925163@apple.com>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <D0AB64D8.3FA7A%mzanaty@cisco.com> <92D0D52F3A63344CA478CF12DB0648AADF360327@XMB111CNC.rim.net> <D0B07593.400EE%mzanaty@cisco.com> <92D0D52F3A63344CA478CF12DB0648AADF3607F5@XMB111CNC.rim.net>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.1993)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUi2FCYqptZ2x1icHUjn8Xaf+3sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKOD79GHPBXY6KTSdjGhi/s3UxcnJICJhIfLnxjAnCFpO4cG89 UJyLQ0hgH6PE5uMHmWGKJvydwQ6RmMQkcebPK6iq+UwSiz+eZe1i5OBgFtCTuH9RC6SBF8hs evKYCSQsLGArsfV6EEiYTUBV4sGcY4wgNqeAp8SP+5fYQWwWoPjj1S/B4swC2hJP3l0Am8gr YCPR8FwdYlMzk8TRJ3vA6kUE1CUuP7zADnGbrMS/i2fAbpMQuMsqcXP5ArYJjEKzEC6aheSi WUhWLGBkXsUolJuYmaObmWeil1hQkJOql5yfu4kRFKrT7YR2MJ5aZXWIUYCDUYmH90VqV4gQ a2JZcWXuIUZpDhYlcd7lbt0hQgLpiSWp2ampBalF8UWlOanFhxiZODilGhi7FkYFPi/K25Np +PVD3sNPS9S3PhUX6W1Vv5375ZL41/97ymP3red4tfTZ+pk8jfxO274/cvI72cqx2G/qzf8b fr5cMWGd0BujM716Jzg/TFTra9EJOdm+IFYpr+/Hl7DwM0I5ASk2YgmP9tW93lnS/FKCfcJC vhrjvJc5Bx16TUv+pYZMWKSsxFKckWioxVxUnAgACHgQrjYCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUi2FDcoutZ2x1isH4pt8Xaf+3sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKOD79GHPBXY6KTSdjGhi/s3UxcnJICJhITPg7gx3CFpO4cG89 UJyLQ0hgEpPEmT+voJz5TBKLP55l7WLk4GAW0JO4f1ELpIEXyGx68pgJJCwsYCux9XoQSJhN QFXiwZxjjCA2p4CnxI/7l8DmswDFH69+CRZnFtCWePLuAthEXgEbiYbn6hCbmpkkjj7ZA1Yv IqAucfnhBajbZCX+XTzDPoGRfxbCEbOQHDELydQFjMyrGAWKUnMSK831EgsKclL1kvNzNzGC Q6swdQdj43KrQ4wCHIxKPLwTkrtChFgTy4orcw8xSnAwK4nwWop3hwjxpiRWVqUW5ccXleak Fh9ilOZgURLnDXnXGCIkkJ5YkpqdmlqQWgSTZeLglGpg3KS6bWLwNyuzEq1n+1mq15Q8Pe/z syNXhe2H4sopU/hnXJTaX1LHeWvthtVKrO4XOuVl3uXxMrJEBwScjFVfGVA4fc6+DmVW55j9 WbxK2Q/jD/Re5MgWSLt0eFuW+8baHa/Nq6/rhCprnVY89kBfMd8gYZa7c76Y+jaZnOcrNdIk mlY0lnAqsRRnJBpqMRcVJwIADsXq4CkCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/2mlZP8YpbVqw_FpBGnGf82ujleg
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 23:42:34 -0000

> On Dec 12, 2014, at 11:13 , Gaelle Martin-Cocher <gmartincocher@blackberry.com> wrote:
> 
> Mandatory codec agility is even more important than specific mandatory codecs, but it may take the latter to force the former.
> [GMC] generally agree.  There is quite a few more options to the above one: Shall implement at least two codecs, one is a defined MTI, the other if up to you (or is in a list of recommended codecs). The second codec can be a future looking codec. Other option: browser and non-browser do not have the same number of codecs to implement. A third option is an asymmetry in the number of decoders and encoders.

Yes, indeed.  If your goal is to make sure everyone can negotiate, we don’t have to say what over, as long as the support is for more than one.

We could also split (as I said before) transmit and receive.  Encoders are harder to do well than decoders, generally. If everyone can decode multiple codecs, they only need to be able to encode one. This also exercises negotiation.

David Singer
Manager, Software Standards, Apple Inc.

v2.23.0 | Report a Bug | By Email