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

Wolfgang Beck <wolfgang.beck01@googlemail.com> Mon, 14 November 2011 10:37 UTC

Return-Path: <wolfgang.beck01@googlemail.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 1270B21F8D3A for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 02:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.936
X-Spam-Level:
X-Spam-Status: No, score=-2.936 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 pA7uN+2AnMjk for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 02:37:17 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 622A421F8CE0 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 02:37:17 -0800 (PST)
Received: by ggnr5 with SMTP id r5so802448ggn.31 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 02:37:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jqsxFu99Kh6fL/ZVP+zis1HB5nCUg/ve1BWCPa8CnaY=; b=v7N5hgtbryfNG4Vq9W1mnePWm9lX89vn0QgBsi/NbFCu32XCz6tT4M6Oao1VMFwgNn cPoqGfsY2TaxEXPPFwHUNBJef1gHiE1maufNUhdfnSL764FJMkZO+2nfJDyfdrAlVxuz qbNxHs74vNlw75l5tgpLIVHEEln9x/FHH9kzw=
MIME-Version: 1.0
Received: by 10.68.120.230 with SMTP id lf6mr12119252pbb.96.1321267036596; Mon, 14 Nov 2011 02:37:16 -0800 (PST)
Received: by 10.68.64.66 with HTTP; Mon, 14 Nov 2011 02:37:16 -0800 (PST)
In-Reply-To: <CAAJUQMg7RiTb46+fzvMcYAeu5DUct2g8s3X5M5DVQa+mrxfhRA@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> <CAAJUQMg7RiTb46+fzvMcYAeu5DUct2g8s3X5M5DVQa+mrxfhRA@mail.gmail.com>
Date: Mon, 14 Nov 2011 18:37:16 +0800
Message-ID: <CAAJUQMjzuCva4qvtm=jaJY6O2nTUC8CrLdjUbOVUyZTji+Szzg@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [rtcweb] Fwd: 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 10:37:18 -0000

If I recall this correctly, the DTMF payload type was made for a
specific scenario:
1. an analogue phone is connected to a (SIP) device
2. the user presses a key on her phone during a call.
3. The device detects the tone generated by the phone. Relaying it out
of band with some SIP message can lead to undesired effects: a bit of
the DTMF might have escaped the SIP device, was sent as G.711, and was
detected by the remote PSTN party. Now if the SIP message (eg INFO)
arrives and gets translated by a SIP-PSTN gateway into a DTMF tone,
the remote party will see two DTMF events instead of one.

The DTMF payload solves this.

As long as we don't want to attach POTS phones to the browser, outband
signalling of events should be sufficient. If we do connect POTS lines
to the browser, we have to talk about fax as well. Thankfully, modem
ports have disappeared from today's laptops and PCs.


Wolfgang Beck