IETF Logo Mail Archive

Re: [rtcweb] RTCWEB needs an Internet Codec

Tim Panton <tim@phonefromhere.com> Fri, 31 August 2012 19:43 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 856F621F84B5 for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 12:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEUNYHYaLnT7 for <rtcweb@ietfa.amsl.com>; Fri, 31 Aug 2012 12:43:13 -0700 (PDT)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id AAB0921F847F for <rtcweb@ietf.org>; Fri, 31 Aug 2012 12:43:12 -0700 (PDT)
Received: from [10.0.2.85] (unknown [65.161.207.100]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id E768037A902; Fri, 31 Aug 2012 20:52:09 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5E40EA51-2ADD-4BAA-AF50-2C0995FEA138"
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <CAC8DBE4E9704C41BCB290C2F3CC921A162D2E9E@nasanexd01h.na.qualcomm.com>
Date: Fri, 31 Aug 2012 12:42:57 -0700
Message-Id: <DEA7D867-EA74-44A5-9446-9873682C4069@phonefromhere.com>
References: <p06240603cc63f3f41ca9@[99.111.97.136]> <503F46C5.2090607@alvestrand.no> <EDC0A1AE77C57744B664A310A0B23AE240CBCCD8@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <503F61CC.1010709@alvestrand.no> <CAC8DBE4E9704C41BCB290C2F3CC921A162D278D@nasanexd01h.na.qualcomm.com> <503FC188.5050003@mozilla.com> <CAC8DBE4E9704C41BCB290C2F3CC921A162D2AF2@nasanexd01h.na.qualcomm.com> <504016A9.5000805@mozilla.com> <CAC8DBE4E9704C41BCB290C2F3CC921A162D2E9E@nasanexd01h.na.qualcomm.com>
To: "Mandyam, Giridhar" <mandyam@quicinc.com>
X-Mailer: Apple Mail (2.1278)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCWEB needs an Internet 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: Fri, 31 Aug 2012 19:43:13 -0000

On 31 Aug 2012, at 10:25, Mandyam, Giridhar wrote:

> In addition, I don't view all use cases as being of equal importance (at least with initial implementations).  Conversational voice over cellular must work for WebRTC. 
All use cases are equal, but some are more equal than others ?

I think it is a _huge_ mistake to assume we know what will be important use cases for webRTC. 
The use case you cite is _very_ well served by adding a tel: url to a mobile web page and placing a 2g gsm call.

Tim.

v2.23.0 | Report a Bug | By Email