Re: [rtcweb] Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)

Tim Panton <tim@phonefromhere.com> Mon, 14 November 2011 08:30 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 C1A3121F8D71 for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 00:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 ZlZaKDKPXMyo for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 00:30:52 -0800 (PST)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id 0E1FD21F8D70 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 00:30:51 -0800 (PST)
Received: from [10.161.77.185] (unknown [212.183.132.77]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id 44BD037A902; Mon, 14 Nov 2011 08:43:29 +0000 (GMT)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=utf-8
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <4EC04998.9070300@acm.org>
Date: Mon, 14 Nov 2011 08:30:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <47BA59C6-6827-4E03-AF79-251403925334@phonefromhere.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <CALiegfkWnRT8m4S9pXTxuLsc-p_bhkG3d=PX3qgiFFt5gW5yfw@mail.gmail.com> <CAD5OKxvQYVKOZF88WLCiRseg-qXQdOpKeDU_t9b-yA2GcDBT-w@mail.gmail.com> <CABcZeBOiPxz_swdaG6Aqoch1WAUtjNh4eOQy1QObCDXT_B8azg@mail.gmail.com> <CAD5OKxtp+LQBRCHgbWdJyrSRcpNQ82i64TJgGtGPrE7+GKcEog@mail.gmail.com> <4EBC3475.90706@alvestrand.no> <CAD5OKxu_-+ZRsqpUBkFSj=tYtOKG0pK3JoQTZHwQGMuBCnp0Gw@mail.gmail.com> <CAD5OKxuaWJ3SBv+0gac6EQy6-Lsb-LS_SBXk5FqObKy4mN6wNg@mail.gmail.com> <CCF4FC92-D5AA-43C8-A0B2-8041C9B8E1BD@edvina.net> <CAD5OKxs-pWwDBjwAu=mQVWRZa4H_YPpzQ31=0qxUUj-pJOErcg@mail.gmail.com> <A2DFC694-DBDF-4DB4-8DE0-DD638C7AF2BE@acmepacket.com> <CALiegfkU1qhLmhY9L373pF7j9zwHipFfu4mAuY49RDTNL7V5Vg@mail.gmail.com> <C11CACFE-FE5A-43F2-8B61-6ABC9965B7FC@acmepacket.com> <CAOJ7v-3w4t0oYKs+01srAmPGziYt6vVZNOQwbpZ7YWUFZtP20w@mail.gmail.com> <CAMujMTyDnS7UHzqHcr=VKD26n2NSmz8wmRUK0E1XomTT6Wujow@mail.gmail.com> <4EC04998.9070300@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: Miguel Casas-Sanchez <miguelecasassanchez@gmail.com>, "&lt, rtcweb@ietf.org&gt, " <rtcweb@ietf.org>
Subject: Re: [rtcweb] Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)
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: Mon, 14 Nov 2011 08:30:53 -0000

On 13 Nov 2011, at 22:50, Marc Petit-Huguenin wrote:

> On 11/13/2011 01:46 PM, Miguel Casas-Sanchez wrote:
>> İt is indeed very interesting to have interoperability with loads of systems,
>> but that should (personal opinion) be left to the applications, and not be
>> suggested in a standard that everyone will need to parse. So: keep standard lean
>> would be my vote (=leave dtmf out) try and focus on mandatory and really
>> nice-to-have features.
>> Miguel
> 
> I do not know why you and others are singling out DTMF.  I am no fan of building
> stuff around carriers needs myself, but DTMF is a codec, no more, no less.  Even
> the fast codec switching mechanism is not special - comfort noise use it too,
> and a system that would recognize music and dynamically switch between audio and
> MIDI would probably be considered innovative.

Which gives further weight to my argument that we should be exposing the codec
as  a javascript object , the we could have a generic 'notification from this codec instance'
callback, instead of doing all these legacy hacks as one-off special cases.

Tim.