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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 14 November 2011 13:02 UTC

Return-Path: <christer.holmberg@ericsson.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 806BB11E829C for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 05:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level:
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 nuGntO--TYIj for <rtcweb@ietfa.amsl.com>; Mon, 14 Nov 2011 05:02:15 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id BEEEC11E81C4 for <rtcweb@ietf.org>; Mon, 14 Nov 2011 05:02:14 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-25-4ec111557b54
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 39.F6.09514.55111CE4; Mon, 14 Nov 2011 14:02:13 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.2]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Mon, 14 Nov 2011 14:02:12 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, Hadriel Kaplan <HKaplan@acmepacket.com>
Date: Mon, 14 Nov 2011 14:02:12 +0100
Thread-Topic: [rtcweb] Traffic should be encrypted. (Re: Let's define the purpose of WebRTC)
Thread-Index: AcyitKXEuKu5sSw6SwqQ4K60rhjOpwAF+tu8
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3925E7A6@ESESSCMS0356.eemea.ericsson.se>
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> <FCFB9735-FB48-45C1-9ADF-CA6DBE5299B1@acmepacket.com>, <CALiegfkstuyuRJWEvsU7EtHE5V41zavdrN0OZ1OSWtv022P16Q@mail.gmail.com>
In-Reply-To: <CALiegfkstuyuRJWEvsU7EtHE5V41zavdrN0OZ1OSWtv022P16Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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 13:02:15 -0000

Hi,

> My concern is that 75% of the traffic in this maillist is about making
> WebRTC capable to accomplish with SIP/PSTN requirements. And that is
> not so bad, but what is really bad is that there is no more. Nobody is
> proposing things that are currently unfeasible with SIP, so we are
l> imiting the posibilities of WebRTC to those provided by SIP protocol.
> The vision/scope of WebRTC is currently limited to what SIP provides.

People in this WG seem to make a default assumption that SIP restricts people from doing new cool things, "prevents innovation" etc.

But, maybe SIP actually CAN be used to do what people (or, at least 75% of them) want. Maybe SIP isn't such a bad protocol after all - which would be good news for those of us who have been working with it for a decade :)

Regards,

Christer