Re: [rtcweb] RTCWEB and emergency services

Harald Alvestrand <harald@alvestrand.no> Wed, 28 September 2011 06:58 UTC

Return-Path: <harald@alvestrand.no>
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 1E18B21F8C79 for <rtcweb@ietfa.amsl.com>; Tue, 27 Sep 2011 23:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.615
X-Spam-Level:
X-Spam-Status: No, score=-109.615 tagged_above=-999 required=5 tests=[AWL=0.983, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 2Qco7GOmDcyw for <rtcweb@ietfa.amsl.com>; Tue, 27 Sep 2011 23:58:11 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 65D8221F8C72 for <rtcweb@ietf.org>; Tue, 27 Sep 2011 23:57:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1D3C339E072; Wed, 28 Sep 2011 09:00:45 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGduCwbXBs29; Wed, 28 Sep 2011 09:00:43 +0200 (CEST)
Received: from [192.168.0.14] (c213-89-141-213.bredband.comhem.se [213.89.141.213]) by eikenes.alvestrand.no (Postfix) with ESMTPS id BD5E539E051; Wed, 28 Sep 2011 09:00:43 +0200 (CEST)
Message-ID: <4E82C61B.3070900@alvestrand.no>
Date: Wed, 28 Sep 2011 09:00:43 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
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>
In-Reply-To: <BLU152-W28C6CA1EDEEBDD0E78E9DB93F00@phx.gbl>
Content-Type: multipart/alternative; boundary="------------020508050509050700010606"
Cc: rtcweb@ietf.org
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 06:58:12 -0000

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....

On 09/28/2011 12:19 AM, Bernard Aboba wrote:
> > I agree. I don't know where this topic comes from, but IMHO it makes
> > no sense to consider a WebRTC provider a "usual" PSTN operator. It
> > would be a show-stopper.
>
> [BA] Agree.    Not sure where this topic comes from either, since I 
> didn't suggest this in my original post (in fact, I specifically noted 
> that emergency obligations would not apply to many RTCWeb applications).
>
> For example, a WebRTC application that does not provide the ability to 
> make or receive calls from the PSTN would not be classified as an 
> "inter-connected VoIP" provider and AFAIK would not currently have an 
> obligation to provide emergency services (at least within the US).
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb