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

Roman Shpount <roman@telurix.com> Mon, 14 November 2011 14:49 UTC

Return-Path: <roman@telurix.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 1FCD511E821A for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 06:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level:
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 RKByKbtrjZu4 for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 06:49:11 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF7F611E819C for <rtcweb@ietf.org>; Mon, 14 Nov 2011 06:49:08 -0800 (PST)
Received: by yenq4 with SMTP id q4so3436152yen.31 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 06:49:08 -0800 (PST)
Received: by 10.68.120.230 with SMTP id lf6mr13461115pbb.96.1321282148041; Mon, 14 Nov 2011 06:49:08 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by mx.google.com with ESMTPS id f1sm48845317pba.7.2011.11.14.06.49.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 06:49:04 -0800 (PST)
Received: by pzk5 with SMTP id 5so9884355pzk.9 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 06:49:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.72.103 with SMTP id c7mr50229405pbv.1.1321282142940; Mon, 14 Nov 2011 06:49:02 -0800 (PST)
Received: by 10.68.7.33 with HTTP; Mon, 14 Nov 2011 06:49:02 -0800 (PST)
In-Reply-To: <CABRok6mq5W-BSNJuZvDrWKhTeedkJC9DMegNUSxHqMDSWmssBw@mail.gmail.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@inba-mail01.sonusnet.com> <1D062974A4845E4D8A343C653804920206D3B7FD@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A105@inba-mail01.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804691DA2@HKGMBOXPRD22.polycom.com> <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com> <CALiegfmM1PB=VAQjfh4rW3-3C8aumHdWy9nZxD0-BWBq9Kq_tg@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BA57@XMB-BGL-414.cisco.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> <CABRok6mJx+quBzdzRZ8fX774+kj-ABWJJvPB=P7=7R5s=ZA2Yg@mail.gmail.com> <CAOJ7v-3W36MGn+8UDo3C2WWtnzJQ4GcB8qkoXy5zucJxjmF1zw@mail.gmail.com> <CABRok6nYi4tg1wJt=0xbw6tkp8JDT4FEpxgW=Uhovx=j+w3=bA@mail.gmail.com> <CAOJ7v-3ju51yg8oP2czjESLcw3b_5ZuygfL-QreZ3aLvRW11AA@mail.gmail.com> <CABRok6nfFC8tc2uZG5AOxspPuOUA4JGvsVNHWPrC0xV8ay2KAQ@mail.gmail.com> <CAOJ7v-13_i-1nHR4==VXbdD=nRVzHDatq_bOo3-s-7Rj_yAWHQ@mail.gmail.com> <CABRok6mq5W-BSNJuZvDrWKhTeedkJC9DMegNUSxHqMDSWmssBw@mail.gmail.com>
Date: Mon, 14 Nov 2011 09:49:02 -0500
Message-ID: <CAD5OKxvVAZyph0O+dpRD3eEEPQko2UUX56Eyyko1cE-88Oeb-w@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Neil Stratford <neils@belltower.co.uk>
Content-Type: multipart/alternative; boundary=f46d041b47f6c72f8304b1b2f872
Cc: "<rtcweb@ietf.org>" <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 14:49:12 -0000

On Mon, Nov 14, 2011 at 6:48 AM, Neil Stratford <neils@belltower.co.uk>wrote;wrote:

> I'd prefer we didn't have a DTMF API and instead leave it up to the
> developer to send over the signalling channel (the usual sync arguments
> don't apply here if you are sending from an API), but if we do have an API
> it makes sense to use the most reliable transport available to carry it.
>

Even if WebRTC is not going to support RFC 4733 DTMF (I am not saying it
should not. I would strongly prefer it did.), we still need to deal with
timing sync between commands and media content. Imagine an application
which asks to press "Done" after recording is complete. If there is no
timing sync, "Done" command can arrive plus/minus half a second from the
end of an actual recording. This makes a lot of applications, like record a
greetings almost unusable. I think that even if WebRTC will support DTMF,
it would be useful to have some type of API which will allow to time sync
arbitrary signaling messages with media stream. One option would be to give
JavaScript access to media stream time stamp. Another option (less
preferred from my point of view) is to have a separate RTP payload that can
be used to transport arbitrary application messages.
_____________
Roman Shpount