IETF Logo Mail Archive

Re: [rtcweb] H.261

David Singer <singer@apple.com> Fri, 22 November 2013 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 DCEC11AE1FE for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 15:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.427
X-Spam-Level:
X-Spam-Status: No, score=-7.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, 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 0XeFyxyFZeSH for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 15:42:31 -0800 (PST)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9ED1AE1FD for <rtcweb@ietf.org>; Fri, 22 Nov 2013 15:42:31 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset="windows-1252"
Received: from relay4.apple.com ([17.128.113.87]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MWO0085UV58UI11@mail-out.apple.com> for rtcweb@ietf.org; Fri, 22 Nov 2013 15:42:24 -0800 (PST)
X-AuditID: 11807157-b7ff46d000001540-42-528febe05d97
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id D7.B6.05440.0EBEF825; Fri, 22 Nov 2013 15:42:24 -0800 (PST)
Received: from singda.apple.com (singda.apple.com [17.197.32.11]) by spicerack.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MWO000YJV6OFO50@spicerack.apple.com> for rtcweb@ietf.org; Fri, 22 Nov 2013 15:42:24 -0800 (PST)
From: David Singer <singer@apple.com>
In-reply-to: <528FC497.2080804@googlemail.com>
Date: Fri, 22 Nov 2013 15:42:24 -0800
Content-transfer-encoding: quoted-printable
Message-id: <A3A17126-2DA7-4D41-A2CE-8580BC2FEAE4@apple.com>
References: <CEB4350B.1E7B2%mzanaty@cisco.com> <20131122171020.GY3245@audi.shelbyville.oz> <7949EED078736C4881C92F656DC6F6C130EA9E66AF@ausmsex00.austin.kmvtechnologies.com> <528F9DAD.3030300@googlemail.com> <7949EED078736C4881C92F656DC6F6C130EA9E66DE@ausmsex00.austin.kmvtechnologies.com> <528FAAA8.8060807@googlemail.com> <7949EED078736C4881C92F656DC6F6C130EA9E66FE@ausmsex00.austin.kmvtechnologies.com> <528FC497.2080804@googlemail.com>
To: Maik Merten <maikmerten@googlemail.com>
X-Mailer: Apple Mail (2.1822)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FCsofvgdX+QwedT6hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoEr4/LFF2wFx9grtn3eyNzA2MnWxcjBISFgIrHyblIXIyeQKSZx 4d56oDAXh5DAZCaJrRPbWSCc1UwST05tYgJpYBbQk7h/UQukgRfIvNV8nxnEFhaQlthy6S4j iM0moCrxYM4xMJsTpGbfc1YQmwUofuvCPzYQm1lAXWLp5AYoW1viybsLrBAzbSRmts1kh9h7 hFni85X9YAkRoKLWU8fYIS6Vldj9/DvzBEaBWQgnzUJy0iwkYxcwMq9iFChKzUmsNNFLLCjI SdVLzs/dxAgOu8LwHYz/llkdYhTgYFTiAdreFyTEmlhWXJl7iFGCg1lJhFf5YH+QEG9KYmVV alF+fFFpTmrxIUZpDhYlcd63L4BSAumJJanZqakFqUUwWSYOTqkGRvN/d49Vh8TN2CaSePBd 6rvXSWZsXzpu7q7/sv5gr6sEaytfzrmzXzMXHnnQsWr9psVLkm6KcT23vqWpULUj9gMv5wrh b4vMY7PvfXopyWnOunnuk+mC074cafR4xNRcO0u++0h+gepqB9M2vcM/4uT23g8vmCkue2j/ t1RlezWrGTnXF2b9uafEUpyRaKjFXFScCADJE8DLNwIAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] H.261
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, 22 Nov 2013 23:42:33 -0000

On Nov 22, 2013, at 12:54 , Maik Merten <maikmerten@googlemail.com> wrote:

> And again, H.261 is only considered as fallback option to establish basic video interoperability as no single high-performance video codec can be agreed on. It would only kick into action in situations when the alternative would be "no video at all". This fallback option has to be implementable without relevant restrictions.

I rather suspect that many, given a choice between:
a) deliver crappy video using H.261, with the unstated implication to the users at the two ends that they really need to find something that will interoperate on something better
and
b) tell the users directly that they don’t have a video codec in common, and to get video they need to find something that will interoperate

would actually prefer (b).  It’s less work, more direct, and more honest.

David Singer
Multimedia and Software Standards, Apple Inc.

v2.26.15 | Report a Bug | By Email | System Status