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

Hadriel Kaplan <HKaplan@acmepacket.com> Sun, 13 November 2011 14:01 UTC

Return-Path: <HKaplan@acmepacket.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 1751F21F8BA4 for <rtcweb@ietfa.amsl.com>; Sun, 13 Nov 2011 06:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level:
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 jM1AGxX7CiB8 for <rtcweb@ietfa.amsl.com>; Sun, 13 Nov 2011 06:01:16 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6E85A21F8B9E for <rtcweb@ietf.org>; Sun, 13 Nov 2011 06:01:16 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 13 Nov 2011 09:01:15 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Sun, 13 Nov 2011 09:01:15 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Thread-Topic: [rtcweb] Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)
Thread-Index: AQHMogy0oPY+iIKWa0aledDcjGopdA==
Date: Sun, 13 Nov 2011 14:01:14 +0000
Message-ID: <FCFB9735-FB48-45C1-9ADF-CA6DBE5299B1@acmepacket.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> <CALiegfkehnLmWuqBPMRki=tJDTHmJ0e6M3RGX-mDBJNzcAA_DQ@mail.gmail.com>
In-Reply-To: <CALiegfkehnLmWuqBPMRki=tJDTHmJ0e6M3RGX-mDBJNzcAA_DQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3318F9BD11713249BBDB4ABAE97DBA10@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
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: Sun, 13 Nov 2011 14:01:17 -0000

On Nov 13, 2011, at 7:28 AM, Iñaki Baz Castillo wrote:

> 2011/11/13 Hadriel Kaplan <HKaplan@acmepacket.com>om>:
>> So long as the mechanisms needed to do so don't hurt WebRTC or force a specific architectural model, why do you care?
> 
> Some telcos in this WG (and I could find exact mails) would accept
> even if WebRTC uses a pure SIP stack.

I'm not sure we have the same understanding of the word "telco".  A "telco" for me is a telephone-company/telecommunications provider/communications service provider (wireless, landline, cable MSOs, etc.).  As far as I can tell, of the 482 members of this mailing list, there are about 32 with email addresses that imply they work for "telcos", and none of them have advocated embedding a SIP stack in the browser.  Lots of people on this mailing list work for companies that sell products to "telco's", but most of them do not advocate putting a SIP stack in the browser either.[1]

Also I really think you're being unfair to people who work for telco's.  I have personally spoken off-line with several of the "telco's" that monitor this mailing list, and all of them believed that whatever's needed to interwork to non-WebRTC must not hurt/degrade WebRTC.  For example most of them actually *want* SRTP to be used, and even think ICE is needed.  Of course they would also prefer to be able to interface to WebRTC with as least cost/complexity as possible, but they know it's not all going to be possible.


> and all of them ask for non mandatory
> SRTP.

I don't think that's a fair assessment.  I don't recall a single one of the people who work for telco's ask for non-mandatory SRTP, and even if one did he/she does not represent "all of them".


> Soon, they will also ask non mandatory ICE (they will argue "ICE
> mandatory to implement in WebRTC client, but not mandatory to use").
> DTMF's via RTP is just the less important subject. What I care is all
> the rest,

But DTMF was the topic of the email.


> and the fact that 75% of mails in this WG are about PSTN
> legacy interoperability.

No, they're not.  75% might be about SIP-related interoperability, but SIP is not just the PSTN.  The SRTP/RTP debate, for example, is not about the PSTN.  The forking debate is not about the PSTN.  The ICE and media consent debates were about both PSTN and Enterprise SIP.  The ROAP vs. real API debate was not about the PSTN nor even SIP.  The congestion control threads were not either.  The TURN URI scheme thread is not about it.  The data channel thread is not about it.  ...

-hadriel