[rtcweb] The importance of selecting a realistic mandatory video codec

Tim Panton <tim@phonefromhere.com> Sun, 01 April 2012 17:35 UTC

Return-Path: <tim@phonefromhere.com>
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 74B8C21F8B68 for <rtcweb@ietfa.amsl.com>; Sun, 1 Apr 2012 10:35:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 sIAmJFAdSgVR for <rtcweb@ietfa.amsl.com>; Sun, 1 Apr 2012 10:35:43 -0700 (PDT)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id D703221F8B66 for <rtcweb@ietf.org>; Sun, 1 Apr 2012 10:35:42 -0700 (PDT)
Received: from [192.168.157.66] (unknown [93.89.81.113]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id 1439E37A902 for <rtcweb@ietf.org>; Sun, 1 Apr 2012 18:44:50 +0100 (BST)
From: Tim Panton <tim@phonefromhere.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sun, 1 Apr 2012 18:35:40 +0100
Message-Id: <4C7C1012-7846-4D38-990E-605300F6EF32@phonefromhere.com>
To: rtcweb@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [rtcweb] The importance of selecting a realistic mandatory video codec
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: Sun, 01 Apr 2012 17:35:43 -0000

In the ITEF 83 meeting I put forward the importance of a common video codec, "even if it is a grotty one".
What I tried to convey and may not have got over is that it needs to be a codec that all the browser
vendors will actually deliver, ideally in their first production releases of RTCweb.

Whilst a common codec is desirable for interop, it isn't essential, there can/will be transcoding proxies
which will paper over the differences and RTCweb can still succeed.

However if we see widespread use of transcoding, we will lose 2 of RTCweb's most exciting properties.

1) True P2P - i.e. the case where ICE can negotiate a direct connection behind a big NAT
2) security for calls over untrusted networks.

I am looking at use-cases for RTCweb where these are very important properties - think disaster relief for example,
without them RTCweb will be significantly harder to deploy over adhoc mesh wifis where the connection to the internet is very low bandwidth (if it exists at all) but where the meshed nodes can cover quite a big area with
decent, if variable, throughput.

For these cases it is essential we mandate a codec that will be delivered by _everyone_ . I don't care which it is.

The same arguments go for a mandated audio codec 
- with the additional requirements that it needs to be resilient to
packetloss (probably have FEC) and able to dynamically adjust bitrate to cope with the mesh changing topology.

Tim.