IETF Logo Mail Archive

Re: [rtcweb] On the topic of MTI video codecs

Peter Saint-Andre <stpeter@stpeter.im> Wed, 30 October 2013 19:19 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7006021E8088 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 12:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.044
X-Spam-Level:
X-Spam-Status: No, score=-102.044 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NikRPV+0urGf for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 12:19:09 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 80A8221E8106 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 12:19:04 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.104]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A287B4010C; Wed, 30 Oct 2013 13:19:03 -0600 (MDT)
Message-ID: <52715BA6.9070608@stpeter.im>
Date: Wed, 30 Oct 2013 13:19:02 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Leon Geyser <lgeyser@gmail.com>, Adam Roach <adam@nostrum.com>
References: <527147FF.5010506@nostrum.com> <CAGgHUiRH81UAmLaan=MRGuk-RoJBuCJ7SsuB5516TiZcNi8FFA@mail.gmail.com> <52715051.1090206@nostrum.com> <CAGgHUiRCdnL6doBDjXSFuYwdcqPiJKR1961h6GigjKCORvXv+w@mail.gmail.com>
In-Reply-To: <CAGgHUiRCdnL6doBDjXSFuYwdcqPiJKR1961h6GigjKCORvXv+w@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] On the topic of MTI video codecs
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Oct 2013 19:19:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/30/13 1:08 PM, Leon Geyser wrote:

> The future is uncertain.

This we can all agree on.

The codecs we have today won't last forever, and new codecs will be
developed and deployed. H.264 matters for immediate interoperability,
but we simply can't know what will enable interoperability 5 or 10 or
15 years from now. Presumably an update to the relevant RFC will need
to happen at that point. Assuming that, in the uncertain future, the
IETF and W3C still exist. ;-)

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJScVumAAoJEOoGpJErxa2pY+MQAJHqYpzqT/sbVbrJzOHnv2tB
lBzspA+DGQOMKUZS/p3NqCOEhhdChq2GsO4K4CwdRJxETwA3sEO204rt3xZcddOc
PWObmeTI2Z9EDXzwLS/BMDpS0hrBeCSZoZ+6JP6cbDI+lLYTMnhYB/9WtFa6T6Ws
S3iWiZlPrEu5KOKVKls6RYtyjdFx/Wbyfq+Oh/ZW826PS5w+Ullp9D9qyIviPhaw
q+K4L9MR28m63ufQXPlsbeBqLtZRkQZOmnHvZQfiCkPyqMhIcqniR9i1kRL8+wOh
ga7ztQKyu1cUKsFYacFZU44hsJAF8tzhGXLm/83/5X+ffM12nMpTg8ZEDQ+HXJ+G
sqvBxgGu0Yl7ErgXxH06kD3W/GKhjNQEYMowMiP6Kop8DrQyH1noqNkt/0DV6dEs
jn8iPjBfXemq8W1anV7ffA7Y0JLjotrTNKdP+O5EIrVFw1Q0hPl744C28phBPvtu
lJRsJ2/HiLvQsrTQf7rRZcf111DodKHJTvzJcGlE33pEUlXwxAPVWqBvwmIWLCal
6PlZ+5cF2fS5x+K3R+71OMc0LxWDzzla3gA4mRbjWm7253VhRo2QdPVT8aO1giP2
cbodgo1lTQ1sZtoKbG9tTi4xxX58IBP84OyoPgJdI8IilVehr5ILwniuKuggqU/B
f+hTRtDlTZxkJTQb+9Cz
=+szN
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email