IETF Logo Mail Archive

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

David Singer <singer@apple.com> Wed, 10 December 2014 19:16 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 0BBFB1A8AA5 for <rtcweb@ietfa.amsl.com>; Wed, 10 Dec 2014 11:16:37 -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 DMp6uzkzNf7U for <rtcweb@ietfa.amsl.com>; Wed, 10 Dec 2014 11:16:28 -0800 (PST)
Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA1BE1A8AA9 for <rtcweb@ietf.org>; Wed, 10 Dec 2014 11:15:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1418238949; x=2282152549; 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=ckz0vMHdqPuLX2pKs3xguNFPifuPCIR5i75/hzIAjco=; b=XGETKk+OSdc3yAjFK170kDRPnG8d5WpZlS3u2yPI+AfzTjlsxyZtYKxMO5sj/3u5 p1sstOo437OkhuafEvjU6ewf10kKRWUGHHJchm/6+9icbCoEocCG0C+J5QWizTfW 7N+wxml8wCqRHCr7lqnbcTy/jC3TZeHMHtfg3ZoX1tFWDtQoQF2jjINRMUfIlX5v fLVNfpBSijt/qTgCFqsS+EshYIjWSSiGXqPOMSbKWYpKAMpkbU+w3HIuMHMNjcVH tETp7ZQcYqaDpaAulHVVqtZPj7uToYKAbXioNJQbLo2uSNrJRIH/ugBtunh4Jl0I IQfydDdFhfpA+7hgo/MF6Q==;
Received: from relay2.apple.com (relay2.apple.com [17.128.113.67]) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 55.89.18524.5EB98845; Wed, 10 Dec 2014 11:15:49 -0800 (PST)
X-AuditID: 11973e15-f79476d00000485c-71-54889be59175
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 relay2.apple.com (Apple SCV relay) with SMTP id 52.77.05858.EDB98845; Wed, 10 Dec 2014 11:15:42 -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 <0NGD008G5S6CWS50@marigold.apple.com> for rtcweb@ietf.org; Wed, 10 Dec 2014 11:15:49 -0800 (PST)
Content-type: text/plain; charset="utf-8"
MIME-version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: David Singer <singer@apple.com>
In-reply-to: <20141210012208.GK19538@hex.shelbyville.oz>
Date: Wed, 10 Dec 2014 11:15:48 -0800
Content-transfer-encoding: quoted-printable
Message-id: <E425BA63-1BF0-4E51-AC4E-453A9E04C60F@apple.com>
References: <E3FA0C72-48C5-465E-AE15-EB19D8D563A7@ieca.com> <CAPF_GTaJwaS9+9uSSGTC1+RqKb=uF8UQxsP4u5jPJiRi=88-Nw@mail.gmail.com> <CAOW+2dvGH6jEp072GxfQwZ=O_QaxZpTrq3bgd2A-gOMj2PL9ZQ@mail.gmail.com> <CABcZeBPw+JoXmHM_nH=ZF6zWfMpw_V1MLZU=hD6kac8qv_Z5eQ@mail.gmail.com> <CAOW+2dsv9W9_x+RroLdsAKyhNAFGGdCTm9P3BMf1_L0XzB8UBQ@mail.gmail.com> <20141210012208.GK19538@hex.shelbyville.oz>
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.1993)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FDorPt0dkeIwalHohZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEro/vNZeaCDq6KWXNfsjcwNnF0MXJySAiYSEz4/Z0JwhaTuHBv PVsXIxeHkMBeRoljL/vZYIoun1oHlZjEJNH2vZsRwpnPJPHtUjdQOwcHs4C6xJQpuSANvAJ6 Ek1PHoOFhQVsJbZeDwIJswmoSjyYc4wRJMwpYCHR/xBsLwtQeOG8NawgNrOAtsSTdxdYIabY SOz6epAJYlMrs8THjZ+ZQRIiAsISW1/1Qh0tK/Hv4hl2kCIJgaesEhNfNbNOYBSahXDRLCQX zUKyYwEj8ypGodzEzBzdzDwzvcSCgpxUveT83E2MoGCdbie6g/HMKqtDjAIcjEo8vCuutocI sSaWFVfmHmKU5mBREuc9shsoJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgbFnTXqjmMy1U396 fb7c/rKxInoR27lLvjVVyYHp52b/2LiV4c8Zz5x697dV6wJyTmf+suLYw/jHPylqi+mvnLrP dU8cC88dleTdfJV7jXV13yP7/VZ7a13qOWoaArIMf+5euMgj6tPvQ94/z51oa+pc5inhfeNG 4QY/xWfL75d97yuP9trILq/EUpyRaKjFXFScCAD740rVNwIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOLMWRmVeSWpSXmKPExsUi2FDcontvdkeIwceZ5hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEro/vNZeaCDq6KWXNfsjcwNnF0MXJySAiYSFw+tY4NwhaTuHBv PZDNxSEkMIlJou17NyOEM59J4tulbqYuRg4OZgF1iSlTckEaeAX0JJqePAYLCwvYSmy9HgQS ZhNQlXgw5xgjSJhTwEKi/yETSJgFKLxw3hpWEJtZQFviybsLrBBTbCR2fT3IBLGplVni48bP zCAJEQFhia2vepkgbpOV+HfxDPsERv5ZCEfMQnLELCRjFzAyr2IUKErNSaw00kssKMhJ1UvO z93ECA6uQucdjMeWWR1iFOBgVOLhXXG1PUSINbGsuDL3EKMEB7OSCG/I9I4QId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rw57xpDhATSE0tSs1NTC1KLYLJMHJxSDYzTNLSsCm/NOc+ouHoXX1N2 RqL0kY0/NwZEF95f0ztp2t4TmqXrGdm9TSS0/PLNcuU0rhwqu3mJP+vBA+P16RWakR/1m7UU ql8syPJk/p29WLVAdp1fGdOGvKlzNNjvs97w11vCl7rmy9lHIle9mDcsmd2df8XOcItOV7DQ 9Hv3X2RuvWH7jEGJpTgj0VCLuag4EQD4bufoKgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/gMlJkZUUtZYvg8w2mtqc80FYjQM
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: Wed, 10 Dec 2014 19:16:37 -0000

> On Dec 9, 2014, at 17:22 , Ron <ron@debian.org> wrote:
> 
> On Tue, Dec 09, 2014 at 05:03:34PM -0800, Bernard Aboba wrote:
>> My bad.
>> 
>> New question:  How can an endpoint that implements video but none of the
>> MTI codecs be construed as "WebRTC Compatible"?
> 
> And what about an endpoint that implements coffee making, but not audio?

ah, that’s different.

“I do video” —  but I chose a strange codec and I don’t interoperate with anyone else who does, only myself
   and
“I don’t do video at all”

are very different places to be.

If I build a web app that is a baby monitor (relays just the sound of the baby’s room) and doesn’t do video, I would hope that it could claim to be a webRTC endpoint, no?  Similarly for a silent surveillance camera — audio codec requirements are irrelevant because it doesn’t do audio at all.

The codec requirements are effectively conditional on supporting the media. I suppose we could state that, and suggest that a webRTC endpoint that does neither video nor audio is at best an odd duck, but I thought it was fairly obvious.

David Singer
Manager, Software Standards, Apple Inc.

v2.23.0 | Report a Bug | By Email