Re: [rtcweb] RTCWEB and emergency services

Randell Jesup <randell-ietf@jesup.org> Wed, 28 September 2011 14:34 UTC

Return-Path: <randell-ietf@jesup.org>
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 0903121F8D56 for <rtcweb@ietfa.amsl.com>; Wed, 28 Sep 2011 07:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599]
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 H2B8OaSo4iac for <rtcweb@ietfa.amsl.com>; Wed, 28 Sep 2011 07:34:17 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 3F73421F8C9C for <rtcweb@ietf.org>; Wed, 28 Sep 2011 07:34:17 -0700 (PDT)
Received: from pool-173-49-141-165.phlapa.fios.verizon.net ([173.49.141.165] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1R8vFx-0006tu-Cu for rtcweb@ietf.org; Wed, 28 Sep 2011 09:37:05 -0500
Message-ID: <4E833031.3060008@jesup.org>
Date: Wed, 28 Sep 2011 10:33:21 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <BLU152-W318BAE2CE0C609B1BB45CD93F30@phx.gbl>, <CA+9kkMA5zZe7D+2F_MmfJgkJCS9CRpDMN3zn=uTjMina-pGaAw@mail.gmail.com>, <BLU152-W39115E9C2A50B4A634789093F00@phx.gbl>, <CA+9kkMBAy2AXi+DwKjqJOr1yFaXYiG96iDPi1oZGuU6HwbBDkA@mail.gmail.com>, <CALiegfmbTL6e1HW95QzAt-AYgMUu3sEyyR4SgRuMrNAVMqibmQ@mail.gmail.com> <BLU152-W28C6CA1EDEEBDD0E78E9DB93F00@phx.gbl> <4E82C61B.3070900@alvestrand.no>
In-Reply-To: <4E82C61B.3070900@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] RTCWEB and emergency services
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: Wed, 28 Sep 2011 14:34:18 -0000

On 9/28/2011 3:00 AM, Harald Alvestrand wrote:
> I'm waiting for the draft to read in context, but what I hear Bernard 
> saying is:
>
> "IF the RTCweb service falls within the scope of 911 regulations
> THEN here are some things it needs to consider...."
>
> Some RTCWeb services will certainly not fall within the scope of 911 
> regulations.
> If someone creates a service where it does matter (sets out to emulate 
> a phone perfectly in the browser, for instance) they may very well 
> find themselves in a situation where they do become subject to 
> regulation, and in that case, the implementor may have benefit from 
> reading Bernard's draft (or the document that eventually results from it).
>
> All other service implementors can disregard it.
>
> I hope....

I hope too.  I'll note that in the US the FCC has a history of changing 
the rules on 911 compliance (and other legal requirements like intercept 
(CALEA)).

VoIP was originally excluded; then it was included only for calls to the 
PSTN, then it was included for all calls if your "network" was attached 
to the PSTN (even if the call was totally on-net).  (This refers to 
CALEA.)  There's even been talk of extending it to non-PSTN-connected 
networks like XBox Live.

So I wouldn't assume that there won't (now or in the future) be a 
requirement for application developers to support either 911 or CALEA 
(in the US) or the equivalent in other countries.  And the requirement 
already exists for anyone who wants to connect an WebRTC client to the 
PSTN in the US.

As far as *we're* concerned, I think it just means we should make sure 
some basic functionalities are available to the applications so *they* 
can comply - and I think that's what Bernard is addressing.


For example, see
http://paranoia.dubfire.net/2011/02/deconstructing-calea-hearing.html
(Good article, BTW)

    Voice services that do not connect to the public telephone network.
    Google and Facebook both offer in-network audio chat to their users
    (Google also offers video). Microsoft's XBox 360 service, Blizzard
    and several other online video game platforms allow users to insult
    each other chat while they play against other users online. At least
    from published information, I'm not aware of any one of these
    companies offering interception capabilities -- and so law
    enforcement agencies almost certainly want access to this

I'll also note that browser<->browser WebRTC communication currently 
won't be covered by the CALEA requirement-to-decrypt even if the service 
provider's network attaches to the PSTN because (if we're using DTLS) 
the keys aren't known to the provider (or the app).

-- 
Randell Jesup
randell-ietf@jesup.org